desktop sharing won't start after upgrading to 18.04

Bug #1790249 reported by Martha Bourgois
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned
unity-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

First time destop sharing was started the system detected a problem which was reported -- so there should be some info for you there already.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mat 1234 F.... pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Sep 1 11:17:29 2018
HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668
InstallationDate: Installed on 2017-02-12 (565 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:07dc Intel Corp.
 Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GIGABYTE GB-BACE-3000
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago)
dmi.bios.date: 03/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MZBSWAP-00
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.x
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.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: GB-BACE-3000
dmi.product.version: 1.x
dmi.sys.vendor: GIGABYTE

Revision history for this message
Martha Bourgois (mat.bourgois) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this issue go away if you boot back in to the prior kernel?

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Martha Bourgois (mat.bourgois) wrote :

Well, the remote support was setup under 16.04 so Desktop Sharing must have behaved properly then.
Whether its behavior has changed between the setup and upgrading I don't know, but why would it?
Anyway, I will boot back wen next I get a chance.

Revision history for this message
Martha Bourgois (mat.bourgois) wrote :

system won't give me a chance to boot back to the prior kernel as you can see from attached photo.

After all that unreadable stuff scrolling past, it goes straight to the home screen (with automatic login).

Revision history for this message
Humphrey van Polanen Petel (hpvpp) wrote :

My current kernel is 4.15.0-34.
Booting back into the previous kernel 4.15.0-33 gives the same behavior: Desktop Sharing won't start.

Perhaps the system error happening shortly after the first attempt is related. See attached.

Revision history for this message
Martha Bourgois (mat.bourgois) wrote :

Managed to boot back to prior kernel (I got some help).

Problem is still happening.

In fact, after the icon in the launchbar stopped pulsating and disappeared the system came up syaing that an error occurred. I hope you got it, but the title was "unity-control-center crashed with signal 5 in g_settings_bind_with_mapping()"

And, as an aside, the mouse wasn't clicking, but we could still use the keyboard.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Do you use Unity or GNOME?

Revision history for this message
Martha Bourgois (mat.bourgois) wrote :

When I upgraded, I accepted the default of "lightdm" (if I remember correctly). I presume that means Unity, because the system looks exactly the way it was before the upgrade.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

I guess it's time to migrate to GDM/GNOME.

Revision history for this message
Martha Bourgois (mat.bourgois) wrote :

I am 93 years old and I am used to the way it is now and I do not appreciate being pushed. Have some respect.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

It's a suggestion.
Unity stacks are now less maintained, as Ubuntu changes its default desktop to GNOME.

Revision history for this message
Martha Bourgois (mat.bourgois) wrote :

I am on LTS so I am ensured of maintenance.

Revision history for this message
Martha Bourgois (mat.bourgois) wrote :

I am on LTS and therefore ensured of maintenance.

Revision history for this message
Khurshid Alam (khurshid-alam) wrote :

It's a duplicate on this bug https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027

I did provide a PPA for unity-control-center and unity-settings-daemon. Although it may require an update.

Please add the PPA (https://code.launchpad.net/~unity7maintainers/+archive/ubuntu/unity7-desktop), update and install unity-control-center and unity-settings-daemon.

See thread here: https://community.ubuntu.com/t/testing-of-sharing-panel-in-u-c-c-bionic/4215

Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.