Ubuntu
unity package

when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen

Bug #1374390 reported by Balazs Pere on 2014-09-26

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?) screen appears to unlock. I tried to reinstall unity, unity-services, lightdm, unity-greeter, but nothing has changed.

Remark: I have two other machines, one of them works correctly, but on the other the locking (Ctrl+Alt+l) doesn't work.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Sep 26 12:35:49 2014
DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:108d]
InstallationDate: Installed on 2013-10-15 (345 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007)
MachineType: ASUSTeK COMPUTER INC. X202E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-18 (161 days ago)
dmi.bios.date: 06/20/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X202E.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X202E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X202E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Sep 26 12:10:59 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 12380
vendor AUO
xserver.version: 2:1.15.1-0ubuntu2.1

Tags:

Revision history for this message

Balazs Pere (perebal-sze) wrote on 2014-09-26:

BootDmesg.txt Edit (78.0 KiB, text/plain; charset="utf-8")
BootLog.txt Edit (6.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (32.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (341 bytes, text/plain; charset="utf-8")
DpkgLog.txt Edit (448.3 KiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (45.7 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (2.3 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (6.0 KiB, text/plain; charset="utf-8")
LightdmGreeterLogOld.txt Edit (7.5 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (23.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (551 bytes, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (4.3 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (100 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (147.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (322.9 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (612 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (44.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (27.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.7 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (6.8 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (421 bytes, text/plain; charset="utf-8")

Revision history for this message

Balazs Pere (perebal-sze) wrote on 2014-09-29:

Sorry, there's no bug.

dconf reset -f /

solved the problem, although it is not the most elegant solution.

Changed in unity (Ubuntu):
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntuunity package