[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922353

Title:
  Overview sometimes fails to appear or disappear in 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  XWayland session starts, then quits.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  XWayland session starts, then quits.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908527] [NEW] Core Dumps

[Stephen Allen]

Public bug reported:

Since this is from the Universe repo, should I report this upstream
instead of here? Please advise. App was fine 24 hours ago, so recent
updates might have a bearing on this.

Running from a shell:

:~$ tootle
[INFO 08:17:28.652378] Application.vala:156: Tootle version: 0.2.0
[INFO 08:17:28.652391] Application.vala:158: Kernel version: 5.9.15-xanmod1
[INFO 08:17:28.665785] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 08:17:28.665865] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 08:17:28.667197] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 08:17:28.669197] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public:local
[INFO 08:17:28.670017] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public
[INFO 08:17:29.642091] Watchlist.vala:23: Reloading
[INFO 08:17:29.642104] Watchlist.vala:34: Watching for 0 users and 0 hashtags
**
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Bail out! 
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Aborted (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: tootle 0.2.0-2ubuntu1
Uname: Linux 5.9.15-xanmod1 x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Dec 17 08:18:52 2020
InstallationDate: Installed on 2020-04-25 (235 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: tootle
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy third-party-packages wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908527

Title:
  Core Dumps

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902938] [NEW] Tootle Core Dump

[Stephen Allen]

Public bug reported:

When run from terminal:

tootle
[INFO 14:53:00.814180] Application.vala:156: Tootle version: 0.2.0
[INFO 14:53:00.814200] Application.vala:158: Kernel version: 5.9.1-xanmod1
[INFO 14:53:00.826796] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 14:53:00.828244] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 14:53:00.830316] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public:local
[INFO 14:53:00.831146] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public
[INFO 14:53:01.828317] Watchlist.vala:23: Reloading
[INFO 14:53:01.828339] Watchlist.vala:34: Watching for 0 users and 0 hashtags
**
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Bail out! 
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Aborted (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: tootle 0.2.0-2ubuntu1
Uname: Linux 5.9.1-xanmod1 x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Wed Nov  4 14:53:57 2020
InstallationDate: Installed on 2020-04-25 (192 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: tootle
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902938

Title:
  Tootle Core Dump

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1876497] Re: clamtk scan checks ' Show Hidden Files ' checkbox automatically

[Stephen Allen]

I'm using the distro version from Ubuntu Focal.

Actually the problem is solved up for me — Don't know when, (I don't use
manual directory scans often) but when running one last night, I didn't
have hidden items showing afterwards.

On Mon, Aug 17, 2020 at 6:05 AM Dave M <1876...@bugs.launchpad.net>
wrote:

> @Stephen Allen (stephen-d-allen),
>
> Are you using snaps or debs? I'm wondering if the snap structure is
> different and would account for you not having it in that location.
>
> Can you try something like:
>
> sudo dpkg -L clamtk
>
> Thanks,
> Dave M
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1876497
> <https://mailtrack.io/trace/link/d6aa519db0fa9e10714aa160478253f01323183a?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1876497=1758692=d4c2d6c9b3b1d783>
>
> Title:
>   clamtk scan checks ' Show Hidden Files ' checkbox automatically
>
> Status in ClamTk:
>   Confirmed
> Status in clamtk package in Ubuntu:
>   Confirmed
>
> Bug description:
>   every time i perform a ' Scan a directory ' scan via ClamTK the hidden
>   files in the Home folder become automatically visible.
>
>   the ' Show Hidden Files ' checkbox gets automatically checked.
>
>   am running 'buntu fossa 20.04.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/clamtk/+bug/1876497/+subscriptions
> <https://mailtrack.io/trace/link/a6827340b752b31934aecdb1113babb2645874fa?url=https%3A%2F%2Fbugs.launchpad.net%2Fclamtk%2F%2Bbug%2F1876497%2F%2Bsubscriptions=1758692=0aaafa3474ffdec0>
>


-- 
"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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876497

Title:
  clamtk scan checks ' Show Hidden Files ' checkbox automatically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1876497] Re: clamtk scan checks ' Show Hidden Files ' checkbox automatically

[Stephen Allen]

Yeah ... not there either. I'll get back to it later on this evening.

On Sun, Aug 16, 2020 at 10:30 AM Dave M <1876...@bugs.launchpad.net>
wrote:

> Ok, on Ubuntu 18.04 it's this:
>
> /usr/share/perl5/ClamTk/
>
> I don't have 20.04 installed yet.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1876497
> 
>
> Title:
>   clamtk scan checks ' Show Hidden Files ' checkbox automatically
>
> Status in ClamTk:
>   Confirmed
> Status in clamtk package in Ubuntu:
>   Confirmed
>
> Bug description:
>   every time i perform a ' Scan a directory ' scan via ClamTK the hidden
>   files in the Home folder become automatically visible.
>
>   the ' Show Hidden Files ' checkbox gets automatically checked.
>
>   am running 'buntu fossa 20.04.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/clamtk/+bug/1876497/+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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876497

Title:
  clamtk scan checks ' Show Hidden Files ' checkbox automatically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876497] Re: clamtk scan checks ' Show Hidden Files ' checkbox automatically

[Stephen Allen]

On Ubuntu LTS 20.04 I don't have that path - see screengrab. Thanks.


** Attachment added: "screengrab of my Perl5 directory"
   
https://bugs.launchpad.net/clamtk/+bug/1876497/+attachment/5401948/+files/Aug16-2020.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876497

Title:
  clamtk scan checks ' Show Hidden Files ' checkbox automatically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876497] Re: clamtk scan checks ' Show Hidden Files ' checkbox automatically

[Stephen Allen]

Yes, me too. I also have the issue of the contextual menu items not
showing up for ClamTK in Nautilus file manager. Does that affect any
others?

** Changed in: clamtk
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876497

Title:
  clamtk scan checks ' Show Hidden Files ' checkbox automatically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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-CRITICAL **: 21:08:09.86

[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 Ubuntu
Bugs, which is subscribed to 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)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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-CRITICAL **: 21:08:0

[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 Ubuntu
Bugs, which is subscribed to 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)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867080

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 875543] Re: [Dell Inspiron 2500] Can't eject cd rom : Inappropriate ioctl for device

[Stephen Allen]

I have this problem too. It can also be a mechanical problem, which in
my case I believe it is as the above commands all do what ejecting
manually via the button does. The rubber band driving the pulley to open
the door do wear out and need to be replaced. Since the price of DVD
drives has plummeted in recent years, it appears they are made more
cheaply.

The door wants to open, it just can't because of the pulley band
slipping due to wear and tear.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875543

Title:
  [Dell Inspiron 2500] Can't eject cd rom : Inappropriate ioctl for
  device

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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-CRITICAL **: 21:08:09.

[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 Ubuntu
Bugs, which is subscribed to 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)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866995

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867017

Title:
  Cursor Invisible, but there.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867017

Title:
  Cursor Invisible, but there.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866995

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801954] Re: flameshot won't start on 18.04

[Stephen Allen]

Same on Ubuntu 19.10 - It was working up until recently however. Error
I'm given is: 'Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.'

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801954

Title:
  flameshot won't start on 18.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838863] [NEW] gui-ufw Won't Launch in Wayland Session

[Stephen Allen]

Public bug reported:

Output when launching from terminal:

sudo gufw
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.593:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.593:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.593:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.593:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.593:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.593:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.594:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.594:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.594:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.594:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)'
failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:4144): Gdk-CRITICAL **: 22:15:00.594:
gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:4144): Gtk-CRITICAL **: 22:15:00.594:

[Bug 1838863] Re: gui-ufw Won't Launch in Wayland Session

[Stephen Allen]

Works OK in an X-session. I'm running Ubuntu Gnome-Vanilla Wayland
session when this segfault occurs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838863

Title:
  gui-ufw Won't Launch in Wayland Session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1838863/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836481

Title:
  Every Backup Is A Complete Backup

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

[Stephen Allen]

Yes it does accept focus but doesn't activate. Did a Cold Boot up this
afternoon and the problem doesn't occur - seems only to happen on warm
reboots. I'll look at the other bug in the am my time. Bedtime now.

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

> Also, this sounds contradictory:
>
> "GDM3 accepts focus but won't accept any input either from keyboard or
> mouse."
>
> You can't set focus without using a keyboard or mouse. So can you
> clarify what that means?
>
> ** Changed in: gdm3 (Ubuntu)
>Status: New => Incomplete
>
> --
> 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
>
> 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.

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

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 927636] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Stephen Allen]

Worked for a couple of iterations but soon went back.

On Sun, Apr 1, 2018 at 7:55 AM bart <927...@bugs.launchpad.net> wrote:

> dpkg-reconfigure plymouth seems to have solved the problem for me
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/927636
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in Plymouth:
>   Confirmed
> Status in plymouth package in Ubuntu:
>   Triaged
>
> Bug description:
>   Ubuntu 12.04 LTS (development branch)
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 12.04
>   Package: plymouth 0.8.2-2ubuntu28
>   ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
>   Uname: Linux 3.2.0-14-generic x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 1.91-0ubuntu1
>   Architecture: amd64
>   Date: Mon Feb  6 07:03:15 2012
>   DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
>   ExecutablePath: /sbin/plymouthd
>   MachineType: Foxconn AMD HDZS01
>   ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic
> root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
>   ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
>   ProcEnviron: PATH=(custom, no user)
>   ProcFB: 0 VESA VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic
> root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
>   SegvAnalysis:
>Segfault happened at: 0x7effe6b50ea0 :
> cmpl   $0x1,(%rdi)
>PC (0x7effe6b50ea0) ok
>source "$0x1" ok
>destination "(%rdi)" (0x) not located in a known VMA region
> (needed writable region)!
>   SegvReason: writing NULL VMA
>   Signal: 11
>   SourcePackage: plymouth
>   StacktraceTop:
>script_obj_deref_direct () from /lib/plymouth/script.so
>script_obj_as_custom () from /lib/plymouth/script.so
>script_execute_object () from /lib/plymouth/script.so
>script_lib_plymouth_on_update_status () from /lib/plymouth/script.so
>?? ()
>   TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
>   Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 04/19/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A93F1022
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: AHD1S
>   dmi.board.vendor: Foxconn
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA93F1022:bd04/19/2011:svnFoxconn:pnAMDHDZS01:pvrTobefilledbyO.E.M.:rvnFoxconn:rnAHD1S:rvr:
>   dmi.product.name: AMD HDZS01
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: Foxconn
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/plymouth/+bug/927636/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 927636] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Stephen Allen]

Still occurring, even after today's plymouth update (Vanilla Gnome).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758677

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758677

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758677

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758677

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 927636] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Stephen Allen]

Didn't work for me on Bionic. However since this mornings massive update
(Bionic) didn't get it on subsequent reboot. So, keeping fingers crossed ...

On Fri, Mar 23, 2018 at 10:35 AM Milan Jovanovic 
wrote:

> I can confirm that after doing dpkg-reconfigure plymouth the issue is
> not appearing (no errors showing)
>
> 
>
> $ apt-cache policy plymouth
> plymouth:
>   Installed: 0.9.3-1ubuntu2
>   Candidate: 0.9.3-1ubuntu2
>   Version table:
>  *** 0.9.3-1ubuntu2 500
> 500 http://rs.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
> 100 /var/lib/dpkg/status
>
> 
>
> $ lsb_release -rd
> Description:Ubuntu Bionic Beaver (development branch)
> Release:18.04
>
> 
>
> 4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC 2018
>
> 
>
> Still, not sure if related to this, the cursor still dissapearing on the
> login screen.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/927636
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in Plymouth:
>   Confirmed
> Status in plymouth package in Ubuntu:
>   Triaged
>
> Bug description:
>   Ubuntu 12.04 LTS (development branch)
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 12.04
>   Package: plymouth 0.8.2-2ubuntu28
>   ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
>   Uname: Linux 3.2.0-14-generic x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 1.91-0ubuntu1
>   Architecture: amd64
>   Date: Mon Feb  6 07:03:15 2012
>   DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
>   ExecutablePath: /sbin/plymouthd
>   MachineType: Foxconn AMD HDZS01
>   ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic
> root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
>   ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
>   ProcEnviron: PATH=(custom, no user)
>   ProcFB: 0 VESA VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic
> root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
>   SegvAnalysis:
>Segfault happened at: 0x7effe6b50ea0 :
> cmpl   $0x1,(%rdi)
>PC (0x7effe6b50ea0) ok
>source "$0x1" ok
>destination "(%rdi)" (0x) not located in a known VMA region
> (needed writable region)!
>   SegvReason: writing NULL VMA
>   Signal: 11
>   SourcePackage: plymouth
>   StacktraceTop:
>script_obj_deref_direct () from /lib/plymouth/script.so
>script_obj_as_custom () from /lib/plymouth/script.so
>script_execute_object () from /lib/plymouth/script.so
>script_lib_plymouth_on_update_status () from /lib/plymouth/script.so
>?? ()
>   TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
>   Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 04/19/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A93F1022
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: AHD1S
>   dmi.board.vendor: Foxconn
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA93F1022:bd04/19/2011:svnFoxconn:pnAMDHDZS01:pvrTobefilledbyO.E.M.:rvnFoxconn:rnAHD1S:rvr:
>   dmi.product.name: AMD HDZS01
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: Foxconn
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/plymouth/+bug/927636/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758306

Title:
  Cannot switch mouse primary button in GCC

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 733453] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Stephen Allen]

This is still happening and has been for some time- well since I reported
'me too'.

On Sat, Mar 17, 2018 at 3:40 AM baptiste z <733...@bugs.launchpad.net>
wrote:

> 18.04 since 2 days, 2 bugs.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/733453
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in plymouth package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Binary package hint: plymouth
>
>   Never had this bug until 11.04 alpha so, I don't think it's related to
>   the 4 other bugs listed.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 11.04
>   Package: plymouth 0.8.2-2ubuntu17
>   ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
>   Uname: Linux 2.6.32-25-generic x86_64
>   Architecture: amd64
>   CrashCounter: 1
>   Date: Fri Mar 11 13:56:40 2011
>   DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
>   ExecutablePath: /sbin/plymouthd
>   InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64
> (20100427.1)
>   PccardctlIdent:
>Socket 0:
>  no product info available
>   PccardctlStatus:
>Socket 0:
>  no card
>   ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
>   ProcEnviron: PATH=(custom, no user)
>   ProcFB:
>0 VGA16 VGA
>1 radeondrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic
> root=UUID=fc67adba-b727-4218-8c1d-5798ca183c73 ro quiet splash
>   SegvAnalysis:
>Segfault happened at: 0x7fd33952afe0 :
> cmpl   $0x1,(%rdi)
>PC (0x7fd33952afe0) ok
>source "$0x1" ok
>destination "(%rdi)" (0x726f207465792079) not located in a known VMA
> region (needed writable region)!
>   SegvReason: writing unknown VMA
>   Signal: 11
>   SourcePackage: plymouth
>   StacktraceTop:
>script_obj_deref_direct () from /lib/plymouth/script.so
>script_obj_as_custom () from /lib/plymouth/script.so
>script_execute_object () from /lib/plymouth/script.so
>script_lib_plymouth_on_message () from /lib/plymouth/script.so
>?? () from /lib/plymouth/script.so
>   TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
>   Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>   UpgradeStatus: Upgraded to natty on 2011-03-10 (0 days ago)
>   UserGroups:
>
>   dmi.bios.date: 10/15/2007
>   dmi.bios.vendor: Acer
>   dmi.bios.version: V3.10A
>   dmi.board.name: Navarro
>   dmi.board.vendor: Acer
>   dmi.board.version: N/A
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnAcer:bvrV3.10A:bd10/15/2007:svn:pn:pvrV3.10A:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
>   dmi.product.version: V3.10A
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/733453/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/733453

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 733453] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Stephen Allen]

~gcjuan worked for me. Also ~wstlmn issue happened to me as well. Seems
to have fixed that issue as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/733453

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1750247] Re: Kodi segfaults when playing any video

[Stephen Allen]

Marked status as 'fix released' due to the bug not present anymore.
Thank-you.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750247

Title:
  Kodi segfaults when playing any video

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749878] Re: GDM doesn't accept mouse clicks

[Stephen Allen]

@Jouni Mettala

Your suggestion worked!

After enabling 'WaylandEnable=false'. Thanks for figuring this out,
didn't think of looking there myself.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749878

Title:
  GDM doesn't accept mouse clicks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1749878] Re: GDM doesn't accept mouse clicks

[Stephen Allen]

If you mean is Wayland installed and an option in GDM? Yes, correct. I'll
try your suggestion and report back. Thanks!

On Sun, Feb 18, 2018 at 10:45 AM Jouni Mettala 
wrote:

> But your GDM is still using Wayland, Right?
>
> I had to edit /etc/gdm3/custom.conf and uncomment line:
> WaylandEnable=false
>
> After that mouse worked in GDM greeter too.
>
> I managed to reproduce this on another computer by using bionic-proposed
> main universe repository.
> Maybe this is bug in gnome-session or related package.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1749878
>
> Title:
>   GDM doesn't accept mouse clicks
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in libinput package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I waited 48 hrs before reporting in the event that it was only
>   temporary as things can be in a state of flux with a developmental
>   version with updates often.
>
>   Anyway, after one of the recent updates for me, I couldn't change the
> session in the GDM session selector. Had to use the keyboard + return key
> to login. No biggie as I don't change sessions often.
>   I'm currently running vanilla gnome. This behaviour exists with the
> recent Ubuntu Kernel too (In case one is wondering about the custom kernel
> I'm running, if it's the problem).
>
>   Thank-you.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.26.2.1-2ubuntu2
>   ProcVersionSignature: Ubuntu
> 4.13.0-32201802110420.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-32201802110420-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Thu Feb 15 21:37:17 2018
>   InstallationDate: Installed on 2018-01-19 (27 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/1749878/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749878

Title:
  GDM doesn't accept mouse clicks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1749878] Re: GDM doesn't accept mouse clicks

[Stephen Allen]

That's interesting @JouniMettala - I'm getting it on Gnome-Vanilla on
Xorg.

On Sun, Feb 18, 2018 at 4:35 AM Jouni Mettala 
wrote:

> I noticed this bug in Gnome with Wayland. Selected Gnome with Xorg and
> mouse buttons work. GDM session selector was affected so I had to change
> session with keyboard.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1749878
>
> Title:
>   GDM doesn't accept mouse clicks
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in libinput package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I waited 48 hrs before reporting in the event that it was only
>   temporary as things can be in a state of flux with a developmental
>   version with updates often.
>
>   Anyway, after one of the recent updates for me, I couldn't change the
> session in the GDM session selector. Had to use the keyboard + return key
> to login. No biggie as I don't change sessions often.
>   I'm currently running vanilla gnome. This behaviour exists with the
> recent Ubuntu Kernel too (In case one is wondering about the custom kernel
> I'm running, if it's the problem).
>
>   Thank-you.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.26.2.1-2ubuntu2
>   ProcVersionSignature: Ubuntu
> 4.13.0-32201802110420.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-32201802110420-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Thu Feb 15 21:37:17 2018
>   InstallationDate: Installed on 2018-01-19 (27 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/1749878/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749878

Title:
  GDM doesn't accept mouse clicks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1750247] Re: Kodi segfaults when playing any video

[Stephen Allen]

I'll be happy to further any other information needed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750247

Title:
  Kodi segfaults when playing any video

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1750247] [NEW] Kodi segfaults when playing any video

[Stephen Allen]

Public bug reported:

Since an update on late Friday/early Saturday morning Feb.16-17, 2018. I
can play video outside of Kodi in gnome-mpv and vlc.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kodi 2:17.6+dfsg1-1
ProcVersionSignature: Ubuntu 
4.13.0-32201802110420.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-32201802110420-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Feb 18 09:29:28 2018
InstallationDate: Installed on 2018-01-19 (30 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: kodi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic kodi

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750247

Title:
  Kodi segfaults when playing any video

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1680884] Re: inputlircd assert failure: *** buffer overflow detected ***: /usr/sbin/inputlircd terminated

[Stephen Allen]

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

Any idea when this sw is going to be fixed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680884

Title:
  inputlircd assert failure: *** buffer overflow detected ***:
  /usr/sbin/inputlircd terminated

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749878] Re: GDM doesn't accept mouse clicks

[Stephen Allen]

@Daniel van Vugt:

OK Installed the downgrade. The only difference is that the mouse cursor
isn't visible at all. Prior, using the up-to-date version, the cursor
was shown, would move but wouldn't respond to clicks. HTH

** Attachment added: "Screengrab"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1749878/+attachment/5056714/+files/Screenshot-20180216101050-743x295.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749878

Title:
  GDM doesn't accept mouse clicks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749878] Re: GDM doesn't accept mouse clicks

[Stephen Allen]

Oops sorry, didn't completely answer number 1/  Yes, regular mouse not a
trackpad.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749878

Title:
  GDM doesn't accept mouse clicks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749878] Re: GDM doesn't accept mouse clicks

[Stephen Allen]

Hi Daniel, thanks for the response.

1. No, not a touchpad. This is a workstation with regular MSFT type
keyboard.

2. Sure, will downgrade libinput and report back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749878

Title:
  GDM doesn't accept mouse clicks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749878] [NEW] GDM doesn't accept mouse clicks

[Stephen Allen]

Public bug reported:

I waited 48 hrs before reporting in the event that it was only temporary
as things can be in a state of flux with a developmental version with
updates often.

Anyway, after one of the recent updates for me, I couldn't change the session 
in the GDM session selector. Had to use the keyboard + return key to login. No 
biggie as I don't change sessions often.
I'm currently running vanilla gnome. This behaviour exists with the recent 
Ubuntu Kernel too (In case one is wondering about the custom kernel I'm 
running, if it's the problem).

Thank-you.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.26.2.1-2ubuntu2
ProcVersionSignature: Ubuntu 
4.13.0-32201802110420.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-32201802110420-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 15 21:37:17 2018
InstallationDate: Installed on 2018-01-19 (27 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 gdm

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749878

Title:
  GDM doesn't accept mouse clicks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1745703] Re: package libc-bin 2.26-0ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Stephen Allen]

Marked this as invalid. Despite 'Need-Restart' restarting system
services that according to it required that - A reboot seems to have
stopped the cascade of error message apport was firing up. I had even
logged out as user after the upgrade and before all the error messages.

So, as the submitter this particular bug should be closed. Perhaps I
shouldn't be as hasty next time, apport fires up. Note to self: Try
trouble shooting *deeper* Steve.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745703

Title:
  package libc-bin 2.26-0ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1745703] [NEW] package libc-bin 2.26-0ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Stephen Allen]

Public bug reported:

'apt upgrade -f' didn't seem to fix it.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libc-bin 2.26-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Mon Jan 22 20:43:23 2018
Dependencies:
 gcc-7-base 7.3.0-1ubuntu1
 libc6 2.26-0ubuntu3
 libgcc1 1:7.3.0-1ubuntu1
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-01-19 (7 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7
SourcePackage: glibc
Title: package libc-bin 2.26-0ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-from-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745703

Title:
  package libc-bin 2.26-0ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742769

Title:
  Pulse Audio Won't Run After BionicBeaver Update

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742769

Title:
  Pulse Audio Won't Run After BionicBeaver Update

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738503

Title:
  Cannot Install SNAPS from Gnome-Software Bionic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741822

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740564] Re: gthumb crashed with SIGSEGV in gth_browser_get_location()

[Stephen Allen]

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

Is #1698672 being private, why I couldn't find via a search?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740564

Title:
  gthumb crashed with SIGSEGV in gth_browser_get_location()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740059] Re: Kodi Sound is Distorted

[Stephen Allen]

As of this morning ET, Ubuntu pulled in some updates, which appear to
have fixed the problem. Therefore I'm going to close for now - hopefully
this doesn't regress. Cheers.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740059

Title:
  Kodi Sound is Distorted

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740059] [NEW] Kodi Sound is Distorted

[Stephen Allen]

Public bug reported:

Since the upgrade to 'Bionic Beaver', Kodi sound has been distorted. I
downgraded to Artful to check it's Kodi and sound is fine there. So this
time I did a clean install of Bionic (last time I upgraded to Bionic I
used the same home directory as I had for Artful and Debian distros
prior, so I wanted to rule out a corruption via config file). Still,
badly distorted audio in clean install. This is on metal btw, not
hypervisor.

Audio is fine in gnome-mpv, gnome-movie-player, and VLC.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kodi 2:17.3+dfsg1-5build2
ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7
Uname: Linux 4.14.0-13-generic x86_64
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 25 19:59:41 2017
InstallationDate: Installed on 2017-12-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: kodi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 bionic kodi wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740059

Title:
  Kodi Sound is Distorted

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738503

Title:
  Cannot Install SNAPS from Gnome-Software Bionic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615732

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1551951] Re: synaptic does not run over gnome wayland session

[Stephen Allen]

Create a script containing those commands, make it executable and run it
via the 'startup' switch each time you login. Works for me as a temp
standby, until fixed properly by the developers.

On Tue, Nov 7, 2017 at 2:56 AM Wolf Rogner  wrote:

> fine but how can one set this automatically.
> It cannot be added to .profile nor .bash_rc (will not execute)
>
> If I have to enter this command manually after each boot on every
> machine I need a new pair of runners.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1705955).
> https://bugs.launchpad.net/bugs/1551951
>
> Title:
>   synaptic does not run over gnome wayland session
>
> Status in synaptic:
>   New
> Status in synaptic package in Ubuntu:
>   Confirmed
> Status in synaptic package in Debian:
>   New
>
> Bug description:
>   Synaptic does not run over gnome wayland session. After sudo login
>   interface it simply not appear.
>
>   This messages are shown at the Terminal when try to run it manually:
>
>   etm@etm-SVS151290X:~$ synaptic
>   Gtk-Message: GtkDialog mapped without a transient parent. This is
> discouraged.
>
>   (synaptic:5335): GLib-GObject-WARNING **: invalid cast from
> 'GdkWaylandDisplay' to 'GdkX11Display'
>   Falha de segmentação (imagem do núcleo gravada)
>   etm@etm-SVS151290X:~$ sudo synaptic
>   [sudo] senha para etm:
>   No protocol specified
>   Failed to connect to Mir: Failed to connect to server socket: Arquivo ou
> diretório não encontrado
>   Unable to init server: Não foi possível conectar: Conection refused
>
>   (synaptic:5361): Gtk-WARNING **: cannot open display: :0
>   etm@etm-SVS151290X:~$
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: synaptic 0.83
>   ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
>   Uname: Linux 4.4.0-9-generic x86_64
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Tue Mar  1 17:57:20 2016
>   InstallationDate: Installed on 2015-11-10 (112 days ago)
>   InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151108)
>   SourcePackage: synaptic
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/synaptic/+bug/1551951/+subscriptions
>
-- 

This email is printed from 100% recycled mobile electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551951

Title:
  synaptic does not run over gnome wayland session

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1712089] Re: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused

[Stephen Allen]

It's a bug in the individual packages, not Wayland.

On Fri, Oct 27, 2017 at 7:05 PM steve lubbs <1712...@bugs.launchpad.net>
wrote:

> A Complaint: The work-arounds given here no longer function after the
> recent updates. WTF! How about fixing this requirements-related bug so I
> can partition my new drive? Barring that give me an Ubuntu-supported
> path back to 17.04 that doesn't involve my losing all my data.
>
> A Suggestion: provide a configuration option to turn this behavior off
> in setup. It would still be annoying but at least we would be able to
> get our work done. Oh, and how about ASSIGNING someone to fix the bloody
> bug???
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1705955).
> https://bugs.launchpad.net/bugs/1712089
>
> Title:
>   Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not
>   connect: Connection refused
>
> Status in synaptic package in Ubuntu:
>   Triaged
>
> Bug description:
>   List of pkexec'ed applications is located in bug 1713313.
>   List of packages which use su-to-root and gksu/gksudo is located in bug
> 1713311.
>
>
> -
>   pkexec'ed applications may be healed with "xhost +si:localuser:root"
> placed in XDG autostart as follows:
>
>   cat <   [Desktop Entry]
>   Name=xhost
>   Comment=Fix graphical root applications
>   Exec="xhost +si:localuser:root"
>   Terminal=false
>   Type=Application
>   EOF
>
>
> -
>
>   Posting here what gnome says about porting to wayland, and their
>   tests:
>
>   GNOME Applications under Wayland
>   GTK+ has a Wayland backend. If it was enabled at compile-time, you can
> run a GTK+ application under Wayland simply by:
>
>   GDK_BACKEND=wayland gnome-calculator
>   Applications that use Clutter or clutter-gtk also need the Clutter
> Wayland backend enabled:
>
>   GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese
>
>   https://wiki.gnome.org/Initiatives/Wayland/Applications
>
>   ==> so hope the settings are well set at compile time; maybe a
>   rebuilt to get sure all apps are ok.
>
>
> 
>
>   With the today packages upgrade, switching from X11 to wayland,
>   synaptic refuse to load/open:
>
>   from the icon into the dash-to-dock, nothing happen
>   from the terminal:
>
>   sudo synaptic
>   [sudo] password for oem:
>   Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
> Connection refused
>
>   (synaptic:2154): Gtk-WARNING **: cannot open display: :0
>
>   Previous days already have switching some packages to wayland, but
>   synaptic was still working. Its only with the today upgrades, after a
>   cold reboot, that synaptic gui is broken.
>
>   Today possibly sources problem:
>
>   Unpacking console-setup-linux (1.142ubuntu7) over (1.142ubuntu5) ...
>
>   Unpacking console-setup (1.142ubuntu7) over (1.142ubuntu5) ...
>
>   Unpacking keyboard-configuration (1.142ubuntu7) over (1.142ubuntu5)
>   ...
>
>   Unpacking gnome-session-bin (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21)
>   ...
>
>   Unpacking gdm3 (3.25.90.1-0ubuntu2) over (3.25.90.1-0ubuntu1) ...
>
>   Unpacking libgdm1 (3.25.90.1-0ubuntu2) over (3.25.90.1-0ubuntu1) ...
>
>   Unpacking gir1.2-gdm-1.0 (3.25.90.1-0ubuntu2) over
>   (3.25.90.1-0ubuntu1) ...
>
>   Unpacking ubuntu-session (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21)
>   ...
>
>   Unpacking gnome-session (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21) ...
>   ...
>   Unpacking gnome-session-common (3.24.1-0ubuntu22) over
> (3.24.1-0ubuntu21) ...
>   Setting up keyboard-configuration (1.142ubuntu7) ...
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: synaptic 0.84.2
>   ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
>   Uname: Linux 4.12.0-12-generic x86_64
>   ApportVersion: 2.20.6-0ubuntu6
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Mon Aug 21 16:21:47 2017
>   EcryptfsInUse: Yes
>   SourcePackage: synaptic
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1712089/+subscriptions
>
-- 

This email is printed from 100% recycled mobile electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712089

Title:
  Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not
  connect: Connection refused

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1712089] Re: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused

[Stephen Allen]

Thanks a lot! I've got a script that I run on each login to fix that.

On Sun, Oct 22, 2017 at 8:01 PM Mark <1712...@bugs.launchpad.net> wrote:

> According to https://bugzilla.redhat.com/show_bug.cgi?id=1274451 there
> are no plans for Wayland to support running graphical applications as
> root so that bug has been closed as WONTFIX. The correct fix is for
> Synaptic, and other graphical apps needing root, to be rewritten to run
> the GUI as a normal user and to use "polkit" for the parts where they
> need root access.
>
>
> ** Bug watch added: Red Hat Bugzilla #1274451
>https://bugzilla.redhat.com/show_bug.cgi?id=1274451
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1705955).
> https://bugs.launchpad.net/bugs/1712089
>
> Title:
>   Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not
>   connect: Connection refused
>
> Status in synaptic package in Ubuntu:
>   Triaged
>
> Bug description:
>   List of pkexec'ed applications is located in bug 1713313.
>   List of packages which use su-to-root and gksu/gksudo is located in bug
> 1713311.
>
>
> -
>   pkexec'ed applications may be healed with "xhost +si:localuser:root"
> placed in XDG autostart as follows:
>
>   cat <   [Desktop Entry]
>   Name=xhost
>   Comment=Fix graphical root applications
>   Exec="xhost +si:localuser:root"
>   Terminal=false
>   Type=Application
>   EOF
>
>
> -
>
>   Posting here what gnome says about porting to wayland, and their
>   tests:
>
>   GNOME Applications under Wayland
>   GTK+ has a Wayland backend. If it was enabled at compile-time, you can
> run a GTK+ application under Wayland simply by:
>
>   GDK_BACKEND=wayland gnome-calculator
>   Applications that use Clutter or clutter-gtk also need the Clutter
> Wayland backend enabled:
>
>   GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese
>
>   https://wiki.gnome.org/Initiatives/Wayland/Applications
>
>   ==> so hope the settings are well set at compile time; maybe a
>   rebuilt to get sure all apps are ok.
>
>
> 
>
>   With the today packages upgrade, switching from X11 to wayland,
>   synaptic refuse to load/open:
>
>   from the icon into the dash-to-dock, nothing happen
>   from the terminal:
>
>   sudo synaptic
>   [sudo] password for oem:
>   Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
> Connection refused
>
>   (synaptic:2154): Gtk-WARNING **: cannot open display: :0
>
>   Previous days already have switching some packages to wayland, but
>   synaptic was still working. Its only with the today upgrades, after a
>   cold reboot, that synaptic gui is broken.
>
>   Today possibly sources problem:
>
>   Unpacking console-setup-linux (1.142ubuntu7) over (1.142ubuntu5) ...
>
>   Unpacking console-setup (1.142ubuntu7) over (1.142ubuntu5) ...
>
>   Unpacking keyboard-configuration (1.142ubuntu7) over (1.142ubuntu5)
>   ...
>
>   Unpacking gnome-session-bin (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21)
>   ...
>
>   Unpacking gdm3 (3.25.90.1-0ubuntu2) over (3.25.90.1-0ubuntu1) ...
>
>   Unpacking libgdm1 (3.25.90.1-0ubuntu2) over (3.25.90.1-0ubuntu1) ...
>
>   Unpacking gir1.2-gdm-1.0 (3.25.90.1-0ubuntu2) over
>   (3.25.90.1-0ubuntu1) ...
>
>   Unpacking ubuntu-session (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21)
>   ...
>
>   Unpacking gnome-session (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21) ...
>   ...
>   Unpacking gnome-session-common (3.24.1-0ubuntu22) over
> (3.24.1-0ubuntu21) ...
>   Setting up keyboard-configuration (1.142ubuntu7) ...
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: synaptic 0.84.2
>   ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
>   Uname: Linux 4.12.0-12-generic x86_64
>   ApportVersion: 2.20.6-0ubuntu6
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Mon Aug 21 16:21:47 2017
>   EcryptfsInUse: Yes
>   SourcePackage: synaptic
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1712089/+subscriptions
>
-- 

This email is printed from 100% recycled mobile electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712089

Title:
  Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not
  connect: Connection refused

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1712089] Re: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused

[Stephen Allen]

Affects Bleachbit too. Ubuntu 11.10 vanilla gnome-session.

On Fri, Oct 6, 2017 at 6:25 AM Norbert <1712...@bugs.launchpad.net>
wrote:

> @matej
> please describe when and why GNU Octave needs root access.
> You can post answer here, or mark bug 1713313 as affecting Octave package
> (use "Also affects distribution/package" link) with corresponding comment.
>
> ** Description changed:
>
> + The full list of pkexec'ed applications is located in bug 1713313. It is
> + long.
> +
>   Posting here what gnome says about porting to wayland, and their tests:
>
>   GNOME Applications under Wayland
>   GTK+ has a Wayland backend. If it was enabled at compile-time, you can
> run a GTK+ application under Wayland simply by:
>
>   GDK_BACKEND=wayland gnome-calculator
>   Applications that use Clutter or clutter-gtk also need the Clutter
> Wayland backend enabled:
>
>   GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese
>
>   https://wiki.gnome.org/Initiatives/Wayland/Applications
>
>   ==> so hope the settings are well set at compile time; maybe a
>   rebuilt to get sure all apps are ok.
>
>
> 
>
>   With the today packages upgrade, switching from X11 to wayland, synaptic
>   refuse to load/open:
>
>   from the icon into the dash-to-dock, nothing happen
>   from the terminal:
>
>   sudo synaptic
>   [sudo] password for oem:
>   Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
> Connection refused
>
>   (synaptic:2154): Gtk-WARNING **: cannot open display: :0
>
>   Previous days already have switching some packages to wayland, but
>   synaptic was still working. Its only with the today upgrades, after a
>   cold reboot, that synaptic gui is broken.
>
>   Today possibly sources problem:
>
>   Unpacking console-setup-linux (1.142ubuntu7) over (1.142ubuntu5) ...
>
>   Unpacking console-setup (1.142ubuntu7) over (1.142ubuntu5) ...
>
>   Unpacking keyboard-configuration (1.142ubuntu7) over (1.142ubuntu5) ...
>
>   Unpacking gnome-session-bin (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21)
>   ...
>
>   Unpacking gdm3 (3.25.90.1-0ubuntu2) over (3.25.90.1-0ubuntu1) ...
>
>   Unpacking libgdm1 (3.25.90.1-0ubuntu2) over (3.25.90.1-0ubuntu1) ...
>
>   Unpacking gir1.2-gdm-1.0 (3.25.90.1-0ubuntu2) over (3.25.90.1-0ubuntu1)
>   ...
>
>   Unpacking ubuntu-session (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21) ...
>
>   Unpacking gnome-session (3.24.1-0ubuntu22) over (3.24.1-0ubuntu21) ...
>   ...
>   Unpacking gnome-session-common (3.24.1-0ubuntu22) over
> (3.24.1-0ubuntu21) ...
>   Setting up keyboard-configuration (1.142ubuntu7) ...
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: synaptic 0.84.2
>   ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
>   Uname: Linux 4.12.0-12-generic x86_64
>   ApportVersion: 2.20.6-0ubuntu6
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Mon Aug 21 16:21:47 2017
>   EcryptfsInUse: Yes
>   SourcePackage: synaptic
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1705955).
> https://bugs.launchpad.net/bugs/1712089
>
> Title:
>   Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not
>   connect: Connection refused
>
> Status in synaptic package in Ubuntu:
>   Triaged
>
> Bug description:
>   The full list of pkexec'ed applications is located in bug 1713313. It
>   is long.
>
>   Posting here what gnome says about porting to wayland, and their
>   tests:
>
>   GNOME Applications under Wayland
>   GTK+ has a Wayland backend. If it was enabled at compile-time, you can
> run a GTK+ application under Wayland simply by:
>
>   GDK_BACKEND=wayland gnome-calculator
>   Applications that use Clutter or clutter-gtk also need the Clutter
> Wayland backend enabled:
>
>   GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese
>
>   https://wiki.gnome.org/Initiatives/Wayland/Applications
>
>   ==> so hope the settings are well set at compile time; maybe a
>   rebuilt to get sure all apps are ok.
>
>
> 
>
>   With the today packages upgrade, switching from X11 to wayland,
>   synaptic refuse to load/open:
>
>   from the icon into the dash-to-dock, nothing happen
>   from the terminal:
>
>   sudo synaptic
>   [sudo] password for oem:
>   Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
> Connection refused
>
>   (synaptic:2154): Gtk-WARNING **: cannot open display: :0
>
>   Previous days already have switching some packages to wayland, but
>   synaptic was still working. Its only with the today upgrades, after a
>   cold reboot, that synaptic gui is broken.
>
>   Today possibly sources problem:
>
>   Unpacking console-setup-linux 

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624317

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1705955] Re: Running Synaptic Package Manager as superuser via terminal results in the following error on Ubuntu Artful (17.10) Daily Build

[Stephen Allen]

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

I'm not running Wayland. In GDM I checked, it isn't selected. So if it is
running Wayland, there is a bug in GDM. I had tried it on Wayland, but then
went back to using XWindows.

On Tue, Jul 25, 2017 at 5:51 PM Julian Alarcon 
wrote:

> *** This bug is a duplicate of bug 1551951 ***
> https://bugs.launchpad.net/bugs/1551951
>
> ** This bug has been marked a duplicate of bug 1551951
>synaptic does not run over gnome wayland session
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1705955
>
> Title:
>   Running Synaptic Package Manager as superuser via terminal results in
>   the following error on Ubuntu Artful (17.10) Daily Build
>
> Status in synaptic package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Running synaptic as superuser on Ubuntu Artful Daily Build results in
>   an error specifying the following:
>
>   kacey@kacey-VirtualBox:~$ sudo synaptic
>   No protocol specified
>   Unable to init server: Could not connect: Connection refused
>
>   (synaptic:9311): Gtk-WARNING **: cannot open display: :0
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: synaptic 0.84.2
>   ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
>   Uname: Linux 4.11.0-10-generic x86_64
>   ApportVersion: 2.20.6-0ubuntu4
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Sun Jul 23 15:05:28 2017
>   InstallationDate: Installed on 2017-07-23 (0 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170720)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: synaptic
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1705955/+subscriptions
>
-- 

This email is printed from 100% recycled mobile electrons.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705955

Title:
  Running Synaptic Package Manager as superuser via terminal results in
  the following error on Ubuntu Artful (17.10) Daily Build

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636514

Title:
  nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 Ubuntu
Bugs, which is subscribed to 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.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 973096] Re: Nvidia driver causes xorg crash

[Stephen Allen]

I rolled back to 11.10 . Couldn't take it anymore. First I tried an
ATI/AMD card but didn't know too much about the card - I think it might
have been 10+ years old. Should have done more research. Long story
short - I busted 12.04 trying to get it to work. So instead of re-
installing 12.04 I just re-installed 11.10 . Sorry for tapping out guys
but I have a stable system with Unity and Compiz. Really NVIDIA??? Next
computer will not have an NVIDIA card (if I can help it). Just giving up
on NVIDIA - not Ubuntu. Not really noticing missing any features of
12.04 - Or am I ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973096

Title:
  Nvidia driver causes xorg crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 973096] Re: Nvidia driver causes xorg crash

[Stephen Allen]

Still waiting for that July Nvidia update. Did anybody check out Nixie's
video talking about how Linus Torvalds flips off Nvidia? One of those
videos that make you go, huuummm???. We all have time, money and sweat
involved in this issue. Lets keep the conversation alive. I will drop
another email to Mike over at Nvidia to see if he has heard anymore
about the July Update.

Has anyone swapped out their video card to something other than Nvidia?
Any positive experiences with other video cards using Unity and 12.04?

I will report back to the group if/when I here from Mike.

Stephen

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973096

Title:
  Nvidia driver causes xorg crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 999984] Re: System returns randomly to login screen after updating nvidia driver to 295.49

[Stephen Allen]

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


Hello Group,

I received an email from Mike at Nvidia regarding random logouts
.
.
.
.
Hi Stephen,

Thanks for the additional information.

This problem has been reported and Engineering is actively investigating
the issue. We aim to fix this for our upcoming 304.x driver in July, but
as you know schedules can change.

I have added myself to the bug report so I will be notified when this is
fixed, and I will notify you at that time.

So if it is acceptable with you, I will close this support case and will
inform you when the fix is available.

Best regards,
Mike
.
.
.


I hope that this information is helpful.

Stephen

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/84

Title:
  System returns randomly to login screen after updating nvidia driver
  to 295.49

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 992795] Re: random logouts especially while watching flash videos

[Stephen Allen]

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


Hello Group,

I received an email from Mike at Nvidia regarding random logouts
.
.
.
.
Hi Stephen,

Thanks for the additional information.

This problem has been reported and Engineering is actively investigating
the issue. We aim to fix this for our upcoming 304.x driver in July, but
as you know schedules can change.

I have added myself to the bug report so I will be notified when this is
fixed, and I will notify you at that time.

So if it is acceptable with you, I will close this support case and will
inform you when the fix is available.

Best regards,
Mike
.
.
.


I hope that this information is helpful.

Stephen

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992795

Title:
  random logouts especially while watching flash videos

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 973096] Re: Nvidia driver causes xorg crash

[Stephen Allen]

Hello Group,

I received an email from Mike at Nvidia regarding random logouts
.
.
.
.
Hi Stephen,

Thanks for the additional information.

This problem has been reported and Engineering is actively investigating
the issue. We aim to fix this for our upcoming 304.x driver in July, but
as you know schedules can change.

I have added myself to the bug report so I will be notified when this is
fixed, and I will notify you at that time.

So if it is acceptable with you, I will close this support case and will
inform you when the fix is available.

Best regards,
Mike
.
.
.


I hope that this information is helpful.

Stephen

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973096

Title:
  Nvidia driver causes xorg crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 999984] Re: System returns randomly to login screen after updating nvidia driver to 295.49

[Stephen Allen]

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

On 6/22/12 I contacted Nvidia through there website via chat (chatted
with a guy named Mo). I asked (among other things) if they were even
aware of the problem. He referred to there Linux Group and said they
would contact me. I referenced a few of the Lauchpad Bug Report
Websites. I will keep the group informed if/when I get an email back.

Today I received an email from Jurjen (I don't know if he works for
Nvidia or is just a concerned party like the rest of us but) he wrote...

.
.
.

There is even an internal bug number at nvidia for this bug with number
970240.

Since yesterday Nvidia posted an update that they where able to reproducure the 
crash and looking into it.
Please see http://www.nvnews.net/vbulletin/showthread.php?t=176404

Kind regards,
.
.
.


I hope that this is helpful. I will keep the group informed if I hear anything 
else.

I hope everyone is enjoying their summer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/84

Title:
  System returns randomly to login screen after updating nvidia driver
  to 295.49

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 992795] Re: random logouts especially while watching flash videos

[Stephen Allen]

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

On 6/22/12 I contacted Nvidia through there website via chat (chatted
with a guy named Mo). I asked (among other things) if they were even
aware of the problem. He referred to there Linux Group and said they
would contact me. I referenced a few of the Lauchpad Bug Report
Websites. I will keep the group informed if/when I get an email back.

Today I received an email from Jurjen (I don't know if he works for
Nvidia or is just a concerned party like the rest of us but) he wrote...

.
.
.

There is even an internal bug number at nvidia for this bug with number
970240.

Since yesterday Nvidia posted an update that they where able to reproducure the 
crash and looking into it.
Please see http://www.nvnews.net/vbulletin/showthread.php?t=176404

Kind regards,
.
.
.

I hope that this is helpful. I will keep the group informed if I hear
anything else.

I hope everyone is enjoying their summer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992795

Title:
  random logouts especially while watching flash videos

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 973096] Re: Nvidia driver causes xorg crash

[Stephen Allen]

This bug is in it's own league. It is not just the Logging Off issue for
me. It is also a dual monitor issue and System Settings shows me as a
Laptop when I am running a Desktop. Has anyone personally seen a bug
through to its fixed conclusion on this website? I am just not seeing
any progress. A statement from Nvidia would be nice so we all can wait
in peace. So I am wondering if these bugs get fixed in an update ie one
day update manager will be the ubuntu bug messiah and magically fix the
bug? Is that the way it works? Or do I have to be more proactive and
look for and apply the bug fixes? Seriously considering going back to
11.10 where things worked. Never - Never - never (since i have been
using ubuntu from version 8) have I ever lost work or time because of a
nasty bug like this one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973096

Title:
  Nvidia driver causes xorg crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 992795] Re: random logouts especially while watching flash videos

[Stephen Allen]

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

I just contacted Nvidia through there website via chat (chatted with a
guy named Mo). I asked (among other things)  if they were even aware of
the problem. He referred to there Linux Group and said they would
contact me. I referenced a few of the Lauchpad Bug Report Websites. I
will keep the group informed if/when I get an email back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992795

Title:
  random logouts especially while watching flash videos

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 973096] Re: Nvidia driver causes xorg crash

[Stephen Allen]

I just contacted Nvidia through there website via chat (chatted with a
guy named Mo). I asked (among other things)  if they were even aware of
the problem. He referred to there Linux Group and said they would
contact me. I referenced a few of the Lauchpad Bug Report Websites. I
will keep the group informed if/when I get an email back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973096

Title:
  Nvidia driver causes xorg crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 990357] Re: X randomly restarts

[Stephen Allen]

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

This bug is in it's own league. Has anyone personally seen a bug through
to its fixed conclusion on this website? There are so many different Bug
Report (#'s) for the same issue. I also have a problem with duel
monitors and I am just not seeing any progress. So I am wondering if
these bugs get fixed in an update ie one day update manager will be the
ubuntu bug messiah and magically fix the bug? Is that the way it works?
Or do I have to be more proactive and look for and apply the bug fixes?
Seriously considering going back to 11.10 where things worked. Never -
Never - never (since i have been using ubuntu from version 8) have I
ever lost work or time because of a nasty bug like this one. Is there a
way you can pay for a working ubuntu 12.04? Anybody care to comment?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990357

Title:
  X randomly restarts

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs