[Touch-packages] [Bug 1566164] [NEW] When returning from suspend, my external Apple monitor is not detected, and nothing I do seem to enable it. Rebooting makes everything work as it should. This was
*** This bug is a duplicate of bug 1565667 *** https://bugs.launchpad.net/bugs/1565667 Public bug reported: This is data from after the suspend, with the problem apparent. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 BootLog: 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: Tue Apr 5 08:21:06 2016 DistUpgraded: 2016-03-23 14:48:41,527 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 3.19.0-32-generic, x86_64: installed acpi-call, 1.1.0, 4.2.0-32-generic, x86_64: installed acpi-call, 1.1.0, 4.2.0-35-generic, x86_64: installed acpi-call, 1.1.0, 4.4.0-15-generic, x86_64: installed acpi-call, 1.1.0, 4.4.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-03-02 (399 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150302) MachineType: LENOVO 20BS006BMD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic root=UUID=9b319f2a-5004-42c0-8e66-6eca970f9885 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-03-23 (12 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET25W (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS006BMD dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BS006BMD:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS006BMD:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS006BMD dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 4 10:22:19 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1049 vendor LGD xserver.version: 2:1.18.1-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial ** This bug has been marked a duplicate of bug 1565667 When returning from suspend, my external Apple monitor is not detected, and nothing I do seem to enable it. Rebooting makes everything work as it should. This was not a problem on 15.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1566164 Title: When returning from suspend, my external Apple monitor is not detected, and nothing I do seem to enable it. Rebooting makes everything work as it should. This was not a problem on 15.10. Status in xorg package in Ubuntu: New Bug description: This is data from after the suspend, with the problem apparent. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 BootLog: 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: Tue Apr 5 08:21:06 2016 DistUpgraded: 2016-03-23 14:48:41,527 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 3.19.0-32-generic, x86_64: installed acpi-call, 1.1.0, 4.2.0-32-generic, x86_64: installed acpi-call, 1.1.0, 4.2.0-35-generic, x86_64: instal
[Touch-packages] [Bug 1560000] Re: installing UITK files during build fails with Qt 5.6
The earlier suggested packaging side MP is no longer needed, a change that fixes the generation of the wrapper.sh was found. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/156 Title: installing UITK files during build fails with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Somehow building UITK with Qt 5.6 does an infinite loop of sorts as seen at https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-011/+build/9368814/+files /buildlog_ubuntu-xenial-amd64.ubuntu-ui- toolkit_1.3.1896+16.04.20160316.2-0ubuntu1~fix3~disabletests1_BUILDING.txt.gz (recommended to wget + gunzip, might kill browser). All architectures are affected. It seems to happen also locally, and even without debuild or such when doing eg fakeroot make install (fakeroot here is the important bit). If UITK is already built, the problem does not go away even if dowgrading to Qt 5.5. But a qmake run with Qt 5.5 would seem like to fix the issue. More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547152] Comment bridged from LTC Bugzilla
--- Comment From praveen.pan...@in.ibm.com 2016-04-05 01:28 EDT---
Hi try to verify the patch on ltrace source (yeterday build) seems me works
fine but i am able to apply "patch allowing loop or breakpoint disabling
failure" only first patch got hung while applying .
Log:
root@ubuntu:~/ltrace-0.7.3# ltrace ps
__libc_start_main(1, 0x34a5e508, 0x34a5e518, 0x34a5e5a0
__cxa_atexit(0x10017850, 0, 0, 0x34a5e5a0) = 0
strrchr("ps", '/') = nil
setlocale(LC_ALL, "")= "en_US.UTF-8"
bindtextdomain("procps-ng", "/usr/share/locale") = "/usr/share/locale"
textdomain("procps-ng") = "procps-ng"
memset(0x34a5dfd0, '\0', 152)= 0x34a5dfd0
sigfillset(~<31-32>) = 0
sigaction(SIGSYS, { 0x10003e90, ~<31-32>, 0x, 0x },
nil) = 0
look_up_our_self(0x10030f50, 0x34a5de48, 0, 8) = 0
ioctl(1, 1074295912, 0x34a5dee0) = 0
isatty(1)= 1
getenv("COLUMNS")= nil
__strncpy_chk(0x34a5de28, 0x100181c8, 7, 16) = 0x34a5de28
__strdup(0x34a5de28, 0x100181c8, 7, 0x6e6b6e75) = 0x1002dff1060
strcasecmp("unknown", "os390") = 6
geteuid()= 0
getpagesize()= 65536
uptime(0, 0, 0, 0) = 0x7a33c
dcgettext(0, 0x10018380, 5, 0x1002dff1080) = 0x10018380
strcmp("ucmd", "pid")= 5
malloc(48) = 0x1002dff17b0
get_pid_digits(0x1002dff1ce0, 110, 119, 124) = 5
strlen("PID")= 3
mmap(0, 0x4, 3, 34) = 0x3fff9480
mprotect(0x3fff9483, 0x1, 0, 34) = 0
time(0) = 1459833894
meminfo(0x57034c26, 0x57034c26, 0, 34) = 0x3fff951143a0
openproc(96, 0, 0, 0)= 0x1002dff1d40
readproc(0x1002dff1d40, 0x100307f0, 0, 0x3fff95090160) = 0x100307f0
strcpy(0x3fff94800090, "PID")= 0x3fff94800090
fwrite(" PID", 5, 1, 0x3fff950917c8)= 1
PID TTY TIME CMD
__snprintf_chk(0x3fff94800090, 240, 1, -1) = 4
dev_to_tty(0x3fff94800090, 240, 0xe500, 1511)= 4
escape_command(0x3fff94800090, 0x100307f0, 0x2, 0x34a5de04) = 5
1511 hvc0 00:00:00 login
1643 hvc0 00:00:00 bash
12917 hvc0 00:00:00 ltrace
12918 hvc0 00:00:00 ps
closeproc(0x1002dff1d40, 0x100307f0, 0x8000, 1) = 0x3fff95090ce0
__fpending(0x3fff950917c8, 0, 1, 0) = 0
ferror(0x3fff950917c8) = 0
fclose(0x3fff950917c8) = 0
+++ exited (status 0) +++
root@ubuntu:~/ltrace-0.7.3# ltrace ls
__libc_start_main(1, 0x33c37178, 0x33c37188, 0x33c37210
strrchr("ls", '/') = nil
setlocale(LC_ALL, "")= "en_US.UTF-8"
bindtextdomain("coreutils", "/usr/share/locale") = "/usr/share/locale"
textdomain("coreutils") = "coreutils"
__cxa_atexit(0x1000fa50, 0, 0, 115) = 0
isatty(1)= 1
getenv("QUOTING_STYLE") = nil
ioctl(1, 1074295912, 0x33c36920) = 0
getopt_long(1, 0x33c37178, "abcdfghiklmnopqrstuvw:xABCDFGHI:"...,
0x10025ab8, -1) = -1
__errno_location() = 0x3fffa6ca6bf0
malloc(56) = 0x10020db1030
memcpy(0x10020db1030,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 56) =
0x10020db1030
strlen(".") = 1
opendir(".") = 0x10020db5ca0
readdir(0x10020db5ca0) = 0x10020db5cd0
memset(0x10020db1140, '\0', 192) = 0x10020db1140
realloc(0x10020db1140, 38400)= 0x10020dbe960
closedir(0x10020db5ca0) = 0
free(0) =
_setjmp(0x10040640, 3, 0x44, 0x3fffa6bc0d38) = 0
strcoll("proc.h", "zero.o") = -10
__ctype_get_mb_cur_max() = 6
fwrite_unlocked("aclocal.m4", 1, 10, 0x3fffa6bc17c8) = 10
__overflow(0x3fffa6bc17c8, 9, 10, 0xfbad2a84) = 9
aclocal.m4 expr.lo library.lo proc.h
backend.h expr.o library.o proc.lo
breakpoint.hfetch.c libtoolproc.o
breakpoints.c fetch.h ltrace read_config_file.c
breakpoints.lo fetch.lo ltrace.1 read_config_file.h
breakpoints.o fetch.o ltrace.conf.5 read_config_file.lo
callback.h filter.c ltrace-elf.c read_config_file.o
common.hfilter.h ltrace-elf.h README
config filter.lo
[Touch-packages] [Bug 1553090] Re: Binding loops in implicitWidth with OTA 10 landing
** Branch linked: lp:~zsombi/ubuntu-ui-
toolkit/fixAbstractButtonBindingLoop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1553090
Title:
Binding loops in implicitWidth with OTA 10 landing
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
The simple code
import QtQuick 2.4
import Ubuntu.Components 1.3
AbstractButton {
implicitWidth: childrenRect.width
implicitHeight: childrenRect.height
Label {
id: titleLabel
text: "HOLA CARACOLA"
}
}
is giving
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
with the OTA 10 landing as of today.
This works fine without that landing and i think it's valid code that
should not be giving out warnings like this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1553090/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553090] Re: Binding loops in implicitWidth with OTA 10 landing
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1553090
Title:
Binding loops in implicitWidth with OTA 10 landing
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
The simple code
import QtQuick 2.4
import Ubuntu.Components 1.3
AbstractButton {
implicitWidth: childrenRect.width
implicitHeight: childrenRect.height
Label {
id: titleLabel
text: "HOLA CARACOLA"
}
}
is giving
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitWidth"
file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop
detected for property "implicitHeight"
with the OTA 10 landing as of today.
This works fine without that landing and i think it's valid code that
should not be giving out warnings like this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1553090/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386767] Re: single tap causes many letters sometimes
I've tried hard to reproduce the problem, but no luck :-( If I see this again, I'll report back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1386767 Title: single tap causes many letters sometimes Status in Canonical System Image: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Sometimes, a single key press in OSK causes multiple keys to appear. It is hard to reproduce, but here is what I just did that caused it: * I installed with --wipe brand new rtm krillin image 133. * In Welcome Wizard, I selected English as my language and completed to normal shell. * in System Settings > Languages, I selected Spanish as display language, which caused a reboot * On reboot, I entered the scopes "dashboard" (not the "dashboard" scope, but the place where you see Favorites v All and a search field) * I tapped the search field, which display the OSK. (Note, the keyboard layout is still English.) * In OSK, I tapped the globe key to switch layouts and chose Spanish Now, I got weird double keys on single presses. Bad enough to be unusable. However, after switch OSK back to English and back to spanish I don't get them, so I wonder whether it has to do with switching the system's runtime locale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1386767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442169] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1442169 Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() Status in cups package in Ubuntu: Confirmed Bug description: ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-daemon 2.0.2-1ubuntu3 ProcVersionSignature: Error: [Errno 2] File o directory non esistente: '/proc/version_signature' Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CupsErrorLog: W [09/Apr/2015:15:58:06 +0200] CreateProfile failed: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Date: Sat Apr 4 11:48:06 2015 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2014-10-23 (167 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lpstat: device for Canon-LBP-5975: socket://192.168.1.130 device for EPSON-Epson-Stylus-Photo-P50: usb://EPSON/Stylus%20Photo%20P50?serial=4C43514B3031353929 MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: EPSON-Epson-Stylus-Photo-P50: Epson Stylus Photo P50 - CUPS+Gutenprint v5.2.10 Canon-LBP-5975: Canon LBP-3460 Foomatic/pxlmono (recommended) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fca89173984 : cmpq $0x0,(%rdi) PC (0x7fca89173984) ok source "$0x0" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() UpgradeStatus: Upgraded to vivid on 2015-03-31 (8 days ago) UserGroups: dmi.bios.date: 05/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0307 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0307:bd05/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1442169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566128] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()
*** This bug is a duplicate of bug 1442169 *** https://bugs.launchpad.net/bugs/1442169 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1442169, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1566128/+attachment/4624071/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1566128/+attachment/4624074/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1566128/+attachment/4624084/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1566128/+attachment/4624086/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1566128/+attachment/4624087/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1566128/+attachment/4624088/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1566128/+attachment/4624089/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1442169 cupsd crashed with SIGSEGV in avahi_entry_group_free() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1566128 Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() Status in cups package in Ubuntu: New Bug description: this bug happened during booting, the reason i issued it in a new report is i'm using newer version of ubuntu (16.04 beta) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Tue Apr 5 02:50:48 2016 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2016-02-14 (50 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: device for Hewlett-Packard-HP-LaserJet-200-color-M251nw: hp:/net/HP_LaserJet_200_color_M251nw?ip=192.168.1.10 MachineType: ASUSTeK COMPUTER INC. N56JRH Papersize: letter PpdFiles: Hewlett-Packard-HP-LaserJet-200-color-M251nw: HP LaserJet 200 color M251 Postscript (recommended) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic root=UUID=aa8788b1-b021-4f12-aea1-7f5628ad49c2 ro quiet splash pcie_aspm=force acpi_osi= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic root=UUID=aa8788b1-b021-4f12-aea1-7f5628ad49c2 ro quiet splash pcie_aspm=force acpi_osi= SegvAnalysis: Segfault happened at: 0x7f5c18765954 : cmpq $0x0,(%rdi) PC (0x7f5c18765954) ok source "$0x0" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() UpgradeStatus: Upgraded to xenial on 2016-04-03 (1 days ago) UserGroups: dmi.bios.date: 09/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56JRH.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56JRH 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.:bvrN56JRH.202:bd09/02/2014:svnASUSTeKCOMPUTERINC.:pnN56JRH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56JRH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56JRH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1566128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510048] Re: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1510048 Title: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: I dont know anything ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Sun Oct 25 19:04:12 2015 DuplicateSignature: package:lightdm:1.14.2-0ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-06-20 (127 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=ashwin autologin-user-timeout=0 autologin-session=lightdm-autologin RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: lightdm Title: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-07-02 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1510048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531404] Re: nonexistent partition in /dev, & lsblk/disk util misbehaving with randomized disks
[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: util-linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1531404 Title: nonexistent partition in /dev, & lsblk/disk util misbehaving with randomized disks Status in util-linux package in Ubuntu: Expired Bug description: I have two 2T disks with no partition table and which have been filled with random data. GNU parted shows nothing on this disk: GNU Parted 3.2 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Error: /dev/sda: unrecognised disk label Model: ATA WDC WD2002FAEX-0 (scsi) Disk /dev/sda: 2000GB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags: but when I check with `lsblk`, I see one disk with partitions and the other without: Code: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk └─sda2 8:2 0 1.6T 0 part NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb 8:16 0 1.8T 0 disk and the Disks utility agrees (see: http://ibin.co/2SQv4KbH06Mz). Also, /dev/disk/by-id contains an entry pointing to sda and one pointing to sda2. So it really does think there's a second partition there. Thinking there was something wrong, I re-filled the disks with random data. Now sda is properly (in the Disks utility as just an "unknown disk"), but sdb shows a second partition, and identically to how sda was showing it before (ie the Disks utility output is the same with 181GB at the beginning and 128GB at the end). I am running all this from the Ubuntu Gnome 15.10 installer disk. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-08-31 (130 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: util-linux 2.26.2-6ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Tags: wily Uname: Linux 4.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1531404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433945] Re: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1433945 Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: ошибка при обработке пакета lightdm (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 1 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 19 10:46:38 2015 DuplicateSignature: package:lightdm:1.12.3-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-06 (12 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1433945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518759] Re: package lightdm 1.16.5-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1518759 Title: package lightdm 1.16.5-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: I was trying to update terminator using the following commands sudo add-apt-repository ppa:gnome-terminator sudo apt-get update sudo apt-get install terminator Having said that I'm not sure this directly related. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Mon Nov 23 09:25:00 2015 DuplicateSignature: package:lightdm:1.16.5-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-06-26 (514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: lightdm Title: package lightdm 1.16.5-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-28 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1518759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525072] Re: package lightdm 1.16.6-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1525072 Title: package lightdm 1.16.6-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in lightdm package in Ubuntu: Fix Released Bug description: Настраивается пакет lightdm (1.16.6-0ubuntu1) … insserv: warning: script 'K01smfpd' missing LSB tags and overrides insserv: warning: script 'smfpd' missing LSB tags and overrides insserv: There is a loop between service ondemand and urandom if started insserv: loop involving service urandom at depth 4 insserv: loop involving service hwclock at depth 3 insserv: There is a loop between service ondemand and udev if started insserv: loop involving service udev at depth 1 insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on ondemand and therefore on system facility `$all'
[Touch-packages] [Bug 1544270] Re: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1544270 Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: Updating system after new install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lightdm 1.17.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Wed Feb 10 15:03:17 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-02-10 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: lightdm Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1544270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535484] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1535484 Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: e: subprocess installed post-removal script returned error exit status 1package lightdm 1.10.6-0ubuntu1 failed to install/upgrad ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: lightdm: Purge Architecture: i386 Date: Sat Jan 16 17:35:42 2016 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subprocess installed post-removal script returned error exit status 1 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2013-02-07 (1075 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2016-01-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1535484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491008] Re: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: podproces zainstalowany skrypt pre-removal zwrócił kod błędu 10
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1491008 Title: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: podproces zainstalowany skrypt pre-removal zwrócił kod błędu 10 Status in lightdm package in Ubuntu: Fix Released Bug description: im using proposed ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5 Uname: Linux 3.19.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 Date: Tue Sep 1 16:32:00 2015 DuplicateSignature: package:lightdm:1.14.2-0ubuntu1.1:podproces zainstalowany skrypt pre-removal zwrócił kod błędu 10 ErrorMessage: podproces zainstalowany skrypt pre-removal zwrócił kod błędu 10 InstallationDate: Installed on 2015-05-31 (93 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: lightdm Title: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: podproces zainstalowany skrypt pre-removal zwrócił kod błędu 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1491008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292990] Re: lightdm overrides dh_installinit in debian/rules and shouldn't
** Branch linked: lp:lightdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1292990 Title: lightdm overrides dh_installinit in debian/rules and shouldn't Status in lightdm package in Ubuntu: Fix Committed Bug description: The debian/rules for lightdm includes the following: override_dh_installinit: dh_installinit --no-start This appears to have been in place since the beginning of the package's history, with no reason given. And the result of this override is that if you install lightdm on a running system, lightdm will not be automatically started at install time like it should be. Please drop this override from the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1292990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495931] Re: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-removal asennettu palautti virhetilakoodin 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Committed ** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1495931 Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-removal asennettu palautti virhetilakoodin 1 Status in lightdm package in Ubuntu: Fix Released Bug description: My laptop just stopped booting to graphical environment ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 Date: Tue Sep 15 14:20:25 2015 DuplicateSignature: package:lightdm:1.14.2-0ubuntu1:aliprosessi komentotiedosto post-removal asennettu palautti virhetilakoodin 1 ErrorMessage: aliprosessi komentotiedosto post-removal asennettu palautti virhetilakoodin 1 InstallationDate: Installed on 2014-11-27 (292 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: lightdm Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-removal asennettu palautti virhetilakoodin 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1495931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1298297] Re: Shutting lid on laptop locks the computer, even though action is set to none
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298297 Title: Shutting lid on laptop locks the computer, even though action is set to none Status in unity package in Ubuntu: Confirmed Bug description: I am using my laptop with an external display. When I want to close the built-in display, while working on the external, the computer is locked for no reason. Settings > Power > Lid = Do nothing is selected on both on battery and when plugged in. I would expect nothing to happen when I close the built-in display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 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: Thu Mar 27 11:25:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21cf] InstallationDate: Installed on 2014-03-26 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1) MachineType: LENOVO 42433ZG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=c3c7f36f-ca42-443e-819f-5553fe3d040a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET64WW (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 42433ZG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn42433ZG:pvrThinkPadT520:rvnLENOVO:rn42433ZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42433ZG dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 26 18:39:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16561 vendor LEN xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470696] Re: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1470696 Title: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in lightdm package in Ubuntu: Fix Released Bug description: Начались проблемы после установки драйверов принтера "панасоник кх- мб2051" с официального сайта панасоник. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 Date: Thu Jul 2 07:48:42 2015 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2015-05-18 (44 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: lightdm Title: package lightdm 1.14.2-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: Upgraded to vivid on 2015-05-20 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1470696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316913] Re: wrong keybord layout at system start
** No longer affects: lightdm ** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1316913 Title: wrong keybord layout at system start Status in unity-greeter package in Ubuntu: Confirmed Bug description: my system is set to german by default (De). When starting thunderbird and writing a new mail my keyboard is in qwerty mode. i must click on the De icon in the task bar to set it to qwertz mode. When updates need to be veriyfied with password i get wrong password - clicking the de icon in task bar sets it to german. thanks! ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1316913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467262] Re: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1467262 Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 Status in lightdm package in Ubuntu: Fix Released Bug description: urgent ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Sun Jun 21 02:05:01 2015 DuplicateSignature: package:lightdm:1.14.2-0ubuntu1:sub-processo script post-installation instalado retornou estado de saída de erro 1 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2015-04-30 (52 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: lightdm Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1467262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292990] Re: lightdm overrides dh_installinit in debian/rules and shouldn't
** Changed in: lightdm (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1292990 Title: lightdm overrides dh_installinit in debian/rules and shouldn't Status in lightdm package in Ubuntu: Fix Committed Bug description: The debian/rules for lightdm includes the following: override_dh_installinit: dh_installinit --no-start This appears to have been in place since the beginning of the package's history, with no reason given. And the result of this override is that if you install lightdm on a running system, lightdm will not be automatically started at install time like it should be. Please drop this override from the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1292990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467329] Re: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1467329 Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: Looks similar to bug #1433945 and bug #1424460, but those are different package versions. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 AptOrdering: lightdm: Install liblightdm-gobject-1-0: Install lightdm: Configure liblightdm-gobject-1-0: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 21 17:59:16 2015 DuplicateSignature: package:lightdm:1.14.2-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=oem autologin-user-timeout=0 autologin-session=lightdm-autologin RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: lightdm Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-06-14 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1467329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430566] Re: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1430566 Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in lightdm package in Ubuntu: Fix Released Bug description: update-rc.d: error: insserv rejected the script header dpkg: error al procesar el paquete unattended-upgrades (--configure): el subproceso instalado el script post-installation devolvió el código de salida de error 1 Se encontraron errores al procesar: lightdm unattended-upgrades E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 AptOrdering: lightdm: Configure virtualbox: Configure virtualbox-qt: Configure virtualbox-dkms: Configure unattended-upgrades: Configure Architecture: amd64 Date: Tue Mar 10 18:09:23 2015 DuplicateSignature: package:lightdm:1.12.2-0ubuntu1:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-03-07 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1430566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424460] Re: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1424460 Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: trying to install updates on ubuntu 14.10, reports package installation failed ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Sat Feb 21 21:10:43 2015 DuplicateSignature: package:lightdm:1.12.2-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-11-12 (102 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1424460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453778] Re: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1453778 Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 Status in lightdm package in Ubuntu: Fix Released Bug description: Everything what I wanted to install reported a problem util-linux What should I do now? ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 AptOrdering: util-linux: Configure lightdm: Configure unattended-upgrades: Configure Architecture: amd64 Date: Sun May 10 20:40:03 2015 DuplicateSignature: package:lightdm:1.12.3-0ubuntu1:podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2015-03-17 (54 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1461): WARNING **: Failed to load user image: Otwarcie pliku "/home/rozztocz/.face" się nie powiodło: Nie ma takiego pliku ani katalogu g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1455): WARNING **: Failed to load user image: Otwarcie pliku "/home/rozztocz/.face" się nie powiodło: Nie ma takiego pliku ani katalogu SourcePackage: lightdm Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1453778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473805] Re: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1473805 Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10 Status in lightdm package in Ubuntu: Fix Released Bug description: I run xfce in CharletOS and i had install Gnome desktop enviroment, i do something with Gnome and save, then when i return xfce and reinstall lightDM it crash problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: lightdm: Purge Architecture: amd64 Date: Sun Jul 12 23:10:59 2015 DpkgTerminalLog: Removing lightdm (1.10.5-0ubuntu1.1) ... DuplicateSignature: package:lightdm:1.10.5-0ubuntu1.1:subprocess installed pre-removal script returned error exit status 10 ErrorMessage: subprocess installed pre-removal script returned error exit status 10 InstallationDate: Installed on 2015-07-05 (7 days ago) InstallationMedia: ChaletOS 14.04 - Release amd64 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=canfdk autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1473805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490202] Re: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1490202 Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: Automatically reported by my system after installing vivid and a few standard packages after install. Might be as a result of muting tom tom login sound on greeter. Have no real idea why this bug report was called. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 AptOrdering: ubuntu-desktop: Purge lightdm: Purge NULL: ConfigurePending Architecture: amd64 Date: Sat Aug 29 23:35:18 2015 DuplicateSignature: package:lightdm:1.14.2-0ubuntu1:subprocess installed post-removal script returned error exit status 1 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2015-08-28 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: lightdm Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1490202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502380] Re: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1502380 Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: Ubuntu 14.04.3 LTS lightdm: Installed: 1.10.5-0ubuntu1.1 Candidate: 1.10.5-0ubuntu1.1 Version table: *** 1.10.5-0ubuntu1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.0-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Package sends me into log in loop. Tried to reconfigure, received error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16 Uname: Linux 3.16.0-50-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 AptOrdering: lightdm: Purge Architecture: amd64 Date: Fri Oct 2 22:19:25 2015 DuplicateSignature: package:lightdm:1.10.5-0ubuntu1.1:subprocess installed post-removal script returned error exit status 1 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2015-04-29 (156 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: lightdm Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1502380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503209] Re: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocesso script pre-removal instalado retornou erro do status de saída 10
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1503209 Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocesso script pre-removal instalado retornou erro do status de saída 10 Status in lightdm package in Ubuntu: Fix Released Bug description: X.Org X Server 1.17.1 Release Date: 2015-02-10 [87.826] X Protocol Version 11, Revision 0 [87.826] Build Operating System: Linux 3.19.0-28-generic i686 Ubuntu [87.826] Current Operating System: Linux islamaro 3.7.0-7-generic #15-Ubuntu SMP Sat Dec 15 16:34:21 UTC 2012 i686 [87.826] Kernel command line: root=UUID=10a7c4f1-e125-4d3d-ab86-e1d555ea628f ro locale=pt_PT quiet splash [87.826] Build Date: 11 September 2015 10:31:05AM [87.826] xorg-server 2:1.17.1-0ubuntu3.1 (For technical support please see http://www.ubuntu.com/support) [87.826] Current version of pixman: 0.32.6 [87.826] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [87.826] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [87.826] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 6 10:01:45 2015 [95.719] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [99.619] (==) No Layout section. Using the first Screen section. [99.619] (==) No screen section available. Using defaults. [99.619] (**) |-->Screen "Default Screen Section" (0) [99.619] (**) | |-->Monitor "" [99.619] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [99.619] (==) Automatically adding devices [99.619] (==) Automatically enabling devices [99.619] (==) Automatically adding GPU devices [ 100.557] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 100.557] Entry deleted from font path. [ 100.620] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 100.620] (==) ModulePath set to "/usr/lib/i386-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules" [ 100.620] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 100.620] (II) Loader magic: 0xb7752700 [ 100.620] (II) Module ABI versions: [ 100.620] X.Org ANSI C Emulation: 0.4 [ 100.620] X.Org Video Driver: 19.0 [ 100.620] X.Org XInput driver : 21.0 [ 100.620] X.Org Server Extension : 9.0 [ 100.620] (II) xfree86: Adding drm device (/dev/dri/card0) [ 100.622] (--) PCI:*(0:0:2:0) 8086:27a2:1179:ff00 rev 3, Mem @ 0xd020/524288, 0xc000/268435456, 0xd030/262144, I/O @ 0x1800/8 [ 100.622] (--) PCI: (0:0:2:1) 8086:27a6:1179:ff00 rev 3, Mem @ 0xd028/524288 [ 100.622] (II) LoadModule: "glx" [ 100.817] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 100.923] (II) Module glx: vendor="X.Org Foundation" [ 100.923] compiled for 1.17.1, module version = 1.0.0 [ 100.923] ABI class: X.Org Server Extension, version 9.0 [ 100.923] (==) AIGLX enabled [ 100.923] (==) Matched intel as autoconfigured driver 0 [ 100.923] (==) Matched intel as autoconfigured driver 1 [ 100.923] (==) Matched modesetting as autoconfigured driver 2 [ 100.923] (==) Matched fbdev as autoconfigured driver 3 [ 100.923] (==) Matched vesa as autoconfigured driver 4 [ 100.923] (==) Assigned the driver to the xf86ConfigLayout [ 100.923] (II) LoadModule: "intel" [ 100.924] (WW) Warning, couldn't open module intel [ 100.924] (II) UnloadModule: "intel" [ 100.924] (II) Unloading intel [ 100.924] (EE) Failed to load module "intel" (module does not exist, 0) [ 100.924] (II) LoadModule: "modesetting" [ 100.924] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 100.991] (II) Module modesetting: vendor="X.Org Foundation" [ 100.991] compiled for 1.17.1, module version = 1.17.1 [ 100.991] Module class: X.Org Video Driver [ 100.991] ABI class: X.Org Video Driver, version 19.0 [ 100.991] (II) LoadModule: "fbdev" [ 100.992] (WW) Warning, couldn't open module fbdev [ 100.992] (II) UnloadModule: "fbdev" [ 100.992] (II) Unloading fbdev [ 100.992] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 100.992] (II) LoadModule: "vesa" [
[Touch-packages] [Bug 1297936] Re: After upgrade 12.04->14.04 lightdm fails to start
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1297936 Title: After upgrade 12.04->14.04 lightdm fails to start Status in lightdm package in Ubuntu: Fix Released Bug description: I upgraded this Kubuntu laptop using the command "do-release-upgrade -d" from 12.04 to 14.04. After the reboot, the splash screen did not disappear and lightdm didn't start. Running the command "start lightdm" (as root), I got the error message "start: Job failed to start", which wasn't really helpful. I also tried the command "/etc/init.d/lightdm start" and now there was some more information: [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.9.13, UID=0 PID=2635 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-lightdm-kde-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Using Xephyr for X servers [+0.00s] DEBUG: Registered seat module xlocal [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Registered seat module surfaceflinger [+0.01s] DEBUG: Adding default seat [+0.01s] DEBUG: Seat: Starting [+0.01s] DEBUG: Seat: Creating greeter session [+0.01s] DEBUG: Seat: Failed to find session configuration lightdm-gtk-greeter [+0.01s] DEBUG: Seat: Failed to create greeter session * Starting X display manager lightdm [ OK ] Even though there was the "[ OK ]" displayed in the last line, lightdm didn't start. Due to the message "Failed to find session configuration lightdm-gtk-greeter" I supposed that the package lightdm-gtk-greeter was missing. And indeed after I installed that package (+ dependencies), lightdm started. As this is a test-upgrade I could return to the original 12.04 system. On that partition was a file /etc/lightdm/lightdm.conf from 2012 with this contents: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=Lubuntu Obviously this was a leftover of a previous test with the lubuntu- desktop. While I had uninstalled lightdm and most of the other Lubuntu packages, this configuration file was not removed for some reason. And during the upgrade I was not asked if the config file should be replaced but the file stayed untouched. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.219 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Mar 26 17:26:05 2014 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2014-03-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1297936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1309479] Re: package lightdm 1.10.0-0ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1309479 Title: package lightdm 1.10.0-0ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: I was installing the update to the newest release of kubuntu trusty tahr using the muon update manager, it ran all night but when it tried to update the lightdm it reported a but and the muon update manager screen is frozen so I can not see any more details of the error message. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 18 07:08:34 2014 DuplicateSignature: package:lightdm:1.10.0-0ubuntu3:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-01-02 (106 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: lightdm Title: package lightdm 1.10.0-0ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322991] Re: package lightdm 1.8.6-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1322991 Title: package lightdm 1.8.6-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: while updating from ubuntu 12.10 to 13.04 ProblemType: Package DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-51.76-generic 3.5.7.33 Uname: Linux 3.5.0-51-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun May 25 17:16:36 2014 DuplicateSignature: package:lightdm:1.8.6-0ubuntu1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True SourcePackage: lightdm Title: package lightdm 1.8.6-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to saucy on 2014-05-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1322991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296002] Re: keyboard not working on login screen
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1296002 Title: keyboard not working on login screen Status in unity-greeter package in Ubuntu: New Bug description: I installed a Thinkpad R61 with Trusty 14.04 from Edubuntu 32 bit. After reboot and every time the keyboard on the login screen does not work, but i can login on TTY and via Onboard. . Edubuntu 14.04 beta1 32 bit --- ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-02 (19 days ago) InstallationMedia: Edubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140224.1) Package: lightdm 1.9.12-0ubuntu1 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-19-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1296002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300680] Re: lightdm crashed with SIGSEGV in munmap()
Closing assumed fixed. ** Information type changed from Private to Public ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1300680 Title: lightdm crashed with SIGSEGV in munmap() Status in lightdm package in Ubuntu: Fix Released Bug description: I was starting the pc ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 Date: Mon Mar 31 23:17:03 2014 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2014-03-30 (1 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=starky autologin-user-timeout=0 autologin-session=lightdm-autologin ProcCmdline: lightdm --session-child 12 15 ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fcf645fe70e <_dl_fini+430>: mov0x8(%rax),%r12 PC (0x7fcf645fe70e) ok source "0x8(%rax)" (0x7fcf60d43e70) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: munmap () at ../sysdeps/unix/syscall-template.S:81 _dl_unmap (map=map@entry=0x13a98d0) at ../sysdeps/x86_64/tlsdesc.c:139 _dl_close_worker (map=map@entry=0x13a98d0) at dl-close.c:639 _dl_close (_map=0x13a98d0) at dl-close.c:773 _dl_catch_error (objname=0x13a6a40, errstring=0x13a6a48, mallocedp=0x13a6a38, operate=0x7fcf619bb0e0 , args=0x13a98d0) at dl-error.c:187 Title: lightdm crashed with SIGSEGV in munmap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1300680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302966] Re: lightdm crashed with signal 5 in g_main_context_new()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1302966 Title: lightdm crashed with signal 5 in g_main_context_new() Status in lightdm package in Ubuntu: Fix Released Bug description: I have powered on the pc as usual, the screen shown only the mouse cursor, the rest was black. I have tryied to restart lightdm service (ctrl-at-f1, login, sudo lightdm restart), but the drawer shown only "labels", no input or buttons was displayed, only the baloon with the login name and the background. ctlr-alt-f(x) does not worked anymore Using ctrl-alt-canc i have rebooted the machine, at the first login the error report apperaed. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.14-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 Date: Sat Apr 5 10:12:03 2014 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-12-27 (98 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 5 SourcePackage: lightdm StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_dbus_connection_call_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: lightdm crashed with signal 5 in g_main_context_new() UpgradeStatus: Upgraded to trusty on 2014-03-29 (6 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1302966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404353] Re: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1404353 Title: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in lightdm package in Ubuntu: Fix Released Bug description: Running automatic update encountered this error. I don't know any more details, sorry. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 Date: Fri Dec 19 17:26:44 2014 DuplicateSignature: package:lightdm:1.10.3-0ubuntu2:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2013-08-08 (498 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu SourcePackage: lightdm Title: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2014-04-20 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1404353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164793] Re: Lightdm shows black screen during login
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1164793 Title: Lightdm shows black screen during login Status in lightdm package in Ubuntu: Fix Released Bug description: While logging in, Lightdm shows a black screen when transitioning to the Ubuntu desktop. This is a regression, as in previous Ubuntu releases, the wallpaper that was shown at login time was always shown until the desktop was usable, without blanking out. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Thu Apr 4 19:53:02 2013 LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1164793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1244989] Re: LightDM won't load: Stopping startpar bridge for notification of upstart job start/stop
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1244989 Title: LightDM won't load: Stopping startpar bridge for notification of upstart job start/stop Status in lightdm package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Bug description: Installed the Ubuntu 14.04 "Trusty Tahr" daily image (21-Oct-2013 13:57) into Virtualbox 4.2.18 r88780 and it won't load LightDM, I switched to tty1 and I see the following message: Stopping startpar bridge for notification of upstart job start/stop On several lines alternating between `[start]` and `[stop]` messages at the end. If I use `sudo lightdm restart` it just brings up a blank screen. I didn't have this specific problem when I was running the Saucy development branch. When I try to use `sudo lightdm restart` I get the error: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions? and I get a blank screen again. Guest: lightdm 1.8.2 1851 MB of RAM Host: Pentium Dual-Core CPU E5200 @ 2.50GHz 4GB (3.7GiB) DDR2 RAM + 1.8GiB Swap nVidia GeForce 7100 (512MB GRAM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1244989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164753] Re: boots to a black screen with a cursor
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1164753 Title: boots to a black screen with a cursor Status in lightdm package in Ubuntu: Fix Released Bug description: After the splash screen on boot, I get taken to a black screen which has an active cursor. I have to switch to tty1 (or another tty) and run the following: sudo service lightdm restart Then I get taken to the lightdm login screen. I'm not sure why it isn't starting properly, happy to help diagnose though. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Fri Apr 5 11:25:51 2013 InstallationDate: Installed on 2012-04-26 (343 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to raring on 2013-02-22 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1164753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275632] Re: package lightdm 1.8.4-0ubuntu1 failed to install/upgrade: 설치한 pre-removal 스크립트 하위 프로세스가 오류 10번을 리턴했습니다
** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1275632 Title: package lightdm 1.8.4-0ubuntu1 failed to install/upgrade: 설치한 pre- removal 스크립트 하위 프로세스가 오류 10번을 리턴했습니다 Status in lightdm package in Ubuntu: Fix Released Bug description: I try to install cuda package, but I failed. After I failed, panel and window frame was disappeared. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 AptOrdering: lightdm: Purge Architecture: i386 Date: Mon Feb 3 14:09:52 2014 DuplicateSignature: package:lightdm:1.8.4-0ubuntu1:설치한 pre-removal 스크립트 하위 프로세스가 오류 10번을 리턴했습니다 ErrorMessage: 설치한 pre-removal 스크립트 하위 프로세스가 오류 10번을 리턴했습니다 InstallationDate: Installed on 2013-01-30 (369 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) LightdmConfig: [SeatDefaults] user-session=plasma-active greeter-session=unity-greeter MarkForUpload: True SourcePackage: lightdm Title: package lightdm 1.8.4-0ubuntu1 failed to install/upgrade: 설치한 pre-removal 스크립트 하위 프로세스가 오류 10번을 리턴했습니다 UpgradeStatus: Upgraded to saucy on 2013-10-24 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1275632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1159099] Re: X fails on boot, but starting lightdm afterwards works
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1159099 Title: X fails on boot, but starting lightdm afterwards works Status in lightdm package in Ubuntu: Fix Released Bug description: This was fixed before, but it came back lately... Error in log is: [ 4.748] (EE) No devices detected. [ 4.748] Fatal server error: [ 4.748] no screens found ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 23 11:31:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fb] InstallationDate: Installed on 2013-02-16 (34 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130216) MachineType: LENOVO 2353CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=bb7483c9-09ca-49c5-9cb5-fd6ecf814340 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2353CTO dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Sat Mar 23 11:04:20 2013 xserver.configfile: default xserver.devices: xserver.errors: No devices detected. No devices detected. Please also check the log file at "/var/log/Xorg.0.log" for additional information. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1159099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1250039] Re: dual-screen monitor setup regressed
Closing assumed fixed. ** No longer affects: lightdm (Ubuntu) ** Changed in: unity-greeter (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1250039 Title: dual-screen monitor setup regressed Status in unity-greeter package in Ubuntu: Fix Released Bug description: For a few weeks in trusty I had following with my dual screen setup: one screen with mouse pointer had normal login screen the other screen, with background picture + ubuntu logo overlay And if i move mouse pointer across they change - the other one becomes active/background-only. This awesome behaviour has regressed, I know get: one screen always with normal login screen the other one stays always black, but does display white mouse pointer if i move to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1250039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270948] Re: System fails to boot to greeter screen
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1270948 Title: System fails to boot to greeter screen Status in lightdm package in Ubuntu: Fix Released Bug description: This bug report may be related/associated with Bug #1268113, which I have also opened, as I only ever see this problem immediately after that problem has occurred. So, after my laptop has hung with the problem described in bug #1268113, I am forced to power-cycle my laptop. Occasionally (but not always) on that first power-on after hitting that problem, I experience *this* problem, where the laptop fails to boot to the greeter screen. Text consoles (CTL-ALT-F1 etc) are available, and my system is apparently up and running, but the graphical console (CTL-ALT-F7) remains black, and never gets as far as the greeter screen. I ran apport-bug to collect this information in the hope that it may be useful. I have guessed plymouth as the problem package, but feel free to redirect me as appropriate. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 20:59:05 2014 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth InstallationDate: Installed on 2014-01-03 (17 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 3626AZ8 MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/Ubuntu-RootVol ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/1f199eb6-b2ad-4014-9f8d-41954bf1a417,lvm=Ubuntu quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/Ubuntu-RootVol ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/1f199eb6-b2ad-4014-9f8d-41954bf1a417,lvm=Ubuntu quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET70WW (1.40 ) dmi.board.name: 3626AZ8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3626AZ8:pvrThinkPadX201:rvnLENOVO:rn3626AZ8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3626AZ8 dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1270948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243519] Re: since upgrade to 13.10, login screen displays Light Display Manager as its own user
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1243519 Title: since upgrade to 13.10, login screen displays Light Display Manager as its own user Status in lightdm package in Ubuntu: Fix Released Bug description: Since upgrading to Ubuntu 13.10, Light Display Manager has been listed as its own user account on the login screen. I have found a manual workaround on a forum which involves adding user "lightdm" to the list of 'hidden-users' in /etc/lightdm/lightdm.conf, but this should still be addressed, perhaps through a software patch. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 23 00:04:07 2013 InstallationDate: Installed on 2013-08-31 (52 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to saucy on 2013-10-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1243519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270436] Re: Systems stops booting when using Lightdm
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1270436 Title: Systems stops booting when using Lightdm Status in lightdm package in Ubuntu: Fix Released Bug description: When I attempt to install and boot using lightdm, the system stops at startpar-bridge and will not advance into boot. I switched to kdm and system boots properly. This bug reared it's ugly head after installation of nvidia-331 from the Ubuntu repo's. This into 14.04 Kubuntu. System:Host: Pats-Main Kernel: 3.13.0-4-generic x86_64 (64 bit) Desktop: KDE 4.12.1 Distro: Ubuntu 14.04 trusty Machine: System: Gigabyte product: N/A Mobo: Gigabyte model: 990FXA-UD3 version: x.x Bios: American Megatrends version: F2 date: 07/15/2013 CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) Clock Speeds: 1: 1400.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 1400.00 MHz 5: 1400.00 MHz 6: 1400.00 MHz Graphics: Card: NVIDIA GF116 [GeForce GTX 550 Ti] X.Org: 1.14.5 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1600x900@60.0hz, 1600x900@60.0hz GLX Renderer: GeForce GTX 550 Ti/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 331.20 Audio: Card-1: NVIDIA GF116 High Definition Audio Controller driver: snd_hda_intel Sound: ALSA ver: k3.13.0-4-generic Card-2: Logitech driver: USB Audio Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 74:d4:35:56:ed:09 Drives:HDD Total Size: 1064.2GB (15.4% used) 1: id: /dev/sda model: SanDisk_SDSSDRC0 size: 32.0GB 2: id: /dev/sdb model: SanDisk_SDSSDRC0 size: 32.0GB 3: id: /dev/sdc model: ST31000528AS size: 1000.2GB Partition: ID: / size: 49G used: 6.5G (14%) fs: ext4 ID: /home size: 917G used: 147G (17%) fs: ext4 ID: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap RAID: Device-1: /dev/md0 - active raid: 0 components: online: sda1 sdb1 Device-2: /dev/md1 - active raid: 0 components: online: sdb2 sda3 Sensors: System Temperatures: cpu: 21.4C mobo: N/A gpu: 32C Fan Speeds (in rpm): cpu: N/A Info: Processes: 207 Uptime: 20 min Memory: 1260.1/7950.1MB Client: Shell (bash) inxi: 1.9.17 Please ask if you need other info ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sat Jan 18 09:24:40 2014 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1270436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1177083] Re: package lightdm 1.6.0ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1177083 Title: package lightdm 1.6.0ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: during do-upgrade-release from 12.10 to 13.04 lightdm install failled during post-install script. Gave Error return code 1. unknown cause. Stopped the upgrade process. Now in an unknown 12.10/13.04 release state. Please resolve and help recovery from this. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon May 6 12:48:13 2013 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-08-08 (270 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter greeter-show-manual-login=true MarkForUpload: True SourcePackage: lightdm Title: package lightdm 1.6.0-0ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to raring on 2013-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1177083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242216] Re: package lightdm 1.8.2-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1242216 Title: package lightdm 1.8.2-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in lightdm package in Ubuntu: Fix Released Bug description: When upgrading from 13.04 (raring) to 13.10 (saucy), the graphical upgrade failed. After looking at the error messages from apt-get, it appears that lightdm was not correctly configured. This is the workaround I applied before rebooting: # killall lightdm # apt-get remove --purge lightdm # apt-get install desktop-ubuntu (and select lightdm as the display manager) ProblemType: Package DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 AptOrdering: python-appindicator: Install lightdm: Configure python-appindicator: Configure ubuntu-desktop: Configure Architecture: amd64 Date: Sun Oct 20 01:58:55 2013 DuplicateSignature: package:lightdm:1.8.2-0ubuntu1:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2010-10-13 (1102 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu autologin-user=johan MarkForUpload: True SourcePackage: lightdm Title: package lightdm 1.8.2-0ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1242216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176605] Re: package lightdm 1.6.0-0ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1176605 Title: package lightdm 1.6.0-0ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in lightdm package in Ubuntu: Fix Released Bug description: One of the package scripts (either lightdm.postinst, lightdm.postrm, lightdm.preinst or lightdm.prerm) stumbled upon the /var/lib/lightdm/.gvfs mount point. After manually unmounting it the upgrade went fine. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 AptOrdering: lightdm-gtk-greeter: Install lightdm: Configure lightdm-gtk-greeter: Configure Architecture: amd64 Date: Sun May 5 19:09:19 2013 DpkgTerminalLog: Entpacken von lightdm-gtk-greeter (aus .../lightdm-gtk-greeter_1.5.1-0ubuntu1_amd64.deb) ... lightdm (1.6.0-0ubuntu2.1) wird eingerichtet ... chown: Zugriff auf »/var/lib/lightdm/.gvfs“ nicht möglich: Keine Berechtigung dpkg: Fehler beim Bearbeiten von lightdm (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2011-10-13 (569 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu MarkForUpload: True SourcePackage: lightdm Title: package lightdm 1.6.0-0ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to raring on 2012-04-17 (383 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1176605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270436] Re: Systems stops booting when using Lightdm
Sounds like a driver issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1270436 Title: Systems stops booting when using Lightdm Status in lightdm package in Ubuntu: Fix Released Bug description: When I attempt to install and boot using lightdm, the system stops at startpar-bridge and will not advance into boot. I switched to kdm and system boots properly. This bug reared it's ugly head after installation of nvidia-331 from the Ubuntu repo's. This into 14.04 Kubuntu. System:Host: Pats-Main Kernel: 3.13.0-4-generic x86_64 (64 bit) Desktop: KDE 4.12.1 Distro: Ubuntu 14.04 trusty Machine: System: Gigabyte product: N/A Mobo: Gigabyte model: 990FXA-UD3 version: x.x Bios: American Megatrends version: F2 date: 07/15/2013 CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) Clock Speeds: 1: 1400.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 1400.00 MHz 5: 1400.00 MHz 6: 1400.00 MHz Graphics: Card: NVIDIA GF116 [GeForce GTX 550 Ti] X.Org: 1.14.5 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1600x900@60.0hz, 1600x900@60.0hz GLX Renderer: GeForce GTX 550 Ti/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 331.20 Audio: Card-1: NVIDIA GF116 High Definition Audio Controller driver: snd_hda_intel Sound: ALSA ver: k3.13.0-4-generic Card-2: Logitech driver: USB Audio Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 74:d4:35:56:ed:09 Drives:HDD Total Size: 1064.2GB (15.4% used) 1: id: /dev/sda model: SanDisk_SDSSDRC0 size: 32.0GB 2: id: /dev/sdb model: SanDisk_SDSSDRC0 size: 32.0GB 3: id: /dev/sdc model: ST31000528AS size: 1000.2GB Partition: ID: / size: 49G used: 6.5G (14%) fs: ext4 ID: /home size: 917G used: 147G (17%) fs: ext4 ID: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap RAID: Device-1: /dev/md0 - active raid: 0 components: online: sda1 sdb1 Device-2: /dev/md1 - active raid: 0 components: online: sdb2 sda3 Sensors: System Temperatures: cpu: 21.4C mobo: N/A gpu: 32C Fan Speeds (in rpm): cpu: N/A Info: Processes: 207 Uptime: 20 min Memory: 1260.1/7950.1MB Client: Shell (bash) inxi: 1.9.17 Please ask if you need other info ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sat Jan 18 09:24:40 2014 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1270436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246016] Re: After login the login manager is shown again
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1246016 Title: After login the login manager is shown again Status in lightdm package in Ubuntu: Fix Released Bug description: After logging in the screen blanks (text is very shortly visible but not readable to me) after which the login screen is shown again. X doesn't seem to crash if I interpreted /var/log/Xorg.0.log correctly. The solution was to rename .kde and logging in again. /var/log/syslog shows Pulseaudio related warning but these seem unrelated since uninstalling pulseaudio did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Tue Oct 29 20:01:51 2013 InstallationDate: Installed on 2012-04-26 (550 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to raring on 2013-10-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1246016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1165091] Re: Time in lightdm has not updated to BST
Closing assumed fixed. ** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu) ** Changed in: unity-greeter (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1165091 Title: Time in lightdm has not updated to BST Status in unity-greeter package in Ubuntu: Fix Released Bug description: Since change from GMT to BST the clock in Unity has updated correctly and automatically but the clock in lightdm still displays the previous time. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Fri Apr 5 17:26:00 2013 InstallationDate: Installed on 2013-03-02 (34 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130302) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1165091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1161463] Re: lightdm crashed with SIGSEGV in __GI___libc_realloc()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1161463 Title: lightdm crashed with SIGSEGV in __GI___libc_realloc() Status in lightdm package in Ubuntu: Fix Released Bug description: rebooted after update, upgrade, dist-upgrade this morning user name was displayed correctly but password area did not appear log off log in dm dialogue was correct; user name and password area active logged in successfully ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 28 10:09:41 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-03-25 (2 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7feaaaca4b88 : mov%r8,0x8(%rsp) PC (0x7feaaaca4b88) ok source "%r8" ok destination "0x8(%rsp)" (0x7fff6e5acff8) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: realloc () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 ?? () ?? () ?? () Title: lightdm crashed with SIGSEGV in realloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1161463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100989] Re: lightdm doesn't ask for password if you clear users password and then recreate it
12.10 is end of life. ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1100989 Title: lightdm doesn't ask for password if you clear users password and then recreate it Status in lightdm package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. do a default install of ubuntu 12.10 2. log in (note that you need to enter your password 3. open User Accounts 4. click "password" 5. set action to "Log in without a password" - NOT "auto login" which does something different. 6. ok the dialog, log out, restart computer. This action clears the user's password. Their password is now effectively null. 7. When you reach the greeter once again, you have to click on "login" but you will not be asked for a password. At this point it is not possible to give yourself a password again due to another bug. https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070449 So we work around it: 8. open a terminal and "passwd" 9. Note it doesn't ask for your existing password, because there isn't one. Enter a new password. 10. restart the computer once more. When you reach the greeter you can login without entering the password you just set. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Thu Jan 17 22:21:33 2013 InstallationDate: Installed on 2013-01-17 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1100989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1093313] Re: plymouth-stop.conf needs "instance" because it may need to be run multiple times
12.10 is end of life.
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1093313
Title:
plymouth-stop.conf needs "instance" because it may need to be run
multiple times
Status in lightdm package in Ubuntu:
Invalid
Bug description:
PRETTY_NAME="Ubuntu quantal (12.10)"
VERSION="12.10, Quantal Quetzal"
Package: plymouth
Origin: Ubuntu
Maintainer: Ubuntu Developers
Architecture: i386
Version: 0.8.4-0ubuntu3
Currently, the init job plymouth-stop will only run once during the bootup
sequence, but in cases where the user has installed more than one display
manager, it will need to be run more than once.
Consider this example.
xdm is installed and made the default-display-manager.
plymouth-stop is called on stopped rc RUNLEVEL=[2345] (JOB is rc),
xdm runs and Xorg starts.
lightdm is then installed but xdm is left as the default-display-
manager.
plymouth-stop is now called on starting lightdm (JOB is lightdm) but
the case statement results in exit 0 with no action as lightdm is
expected to take care of stopping plymouth.
However in the lightdm init configuration file, the lightdm job stops
without doing anything because lightdm is not the default-display-
manager.
The boot sequence continues and xdm finally gets to run. plymouth is
still running and is never stopped because plymouth-stop has already
run and is only allowed to run once.
In some cases this prevents the Xorg server from starting with
"setversion 1.4 failed" and " [drm] failed to set drm interface
version, Kernel modesetting setup failed', presumably because
plymouth is hogging the virtual console on which X is to be started.
Thus the problem is rectified by allowing plymouth-stop to be run
multiple times for each display manager installed by adding the line
instance${JOB}
to the plymouth-stop.conf file.
This may cure some bug reports that other users have reported of
plymouth not stopping when running other display managers eg slim
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1093313/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1161268] Re: lightdm crashed with SIGSEGV in _int_realloc()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1161268 Title: lightdm crashed with SIGSEGV in _int_realloc() Status in lightdm package in Ubuntu: Fix Released Bug description: I got this problem after reboot. First I got the login screen but now place to type my password (the shaded area had not got an input field). I also tried the lightdm service to stop and start, but stop reported unknown instance. I had to kill process X "by hand" to recover. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 Date: Thu Mar 28 09:30:32 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2012-03-01 (391 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0xb720d0ce <_int_realloc+14>: call 0xb72c15e3 <__x86.get_pc_thunk.bx> PC (0xb720d0ce) ok source "0xb72c15e3" (0xb72c15e3) ok destination "(%esp)" (0xbf4d4ff0) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: _int_realloc (av=av@entry=0xb7343440 , oldp=oldp@entry=0x97df3d0, oldsize=oldsize@entry=24, nb=nb@entry=16) at malloc.c:4124 __GI___libc_realloc (oldmem=0x97df3d8, bytes=8) at malloc.c:2984 ?? () from /lib/i386-linux-gnu/libgcrypt.so.11 ?? () from /lib/i386-linux-gnu/libgcrypt.so.11 gcry_realloc () from /lib/i386-linux-gnu/libgcrypt.so.11 Title: lightdm crashed with SIGSEGV in _int_realloc() UpgradeStatus: Upgraded to raring on 2013-03-05 (22 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1161268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1068396] Re: Usernames are not remembered after reboot
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1068396 Title: Usernames are not remembered after reboot Status in lightdm package in Ubuntu: Fix Released Bug description: $ cat /etc/lightdm/lightdm.conf [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter greeter-show-manual-login=true allow-guest=false My computer is hooked up to an Active Directory domain via Likewise-Open, and I have no problems logging in with my AD username. If I logout to return to the login screen, then I see my username in the list alongside the local admin user. If I reboot the computer, then I see that my AD username has disappeared from the users list on the login screen, and only the local admin user account is shown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 11:20:53 2012 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1068396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in lightdm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in lightdm source package in Quantal: Won't Fix Status in linux source package in Quantal: Won't Fix Status in lightdm source package in Raring: Won't Fix Status in linux source package in Raring: Won't Fix Status in lightdm source package in Saucy: Won't Fix Status in linux source package in Saucy: Won't Fix Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1148935] Re: lightdm crashed with SIGSEGV in check_stopped()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1148935 Title: lightdm crashed with SIGSEGV in check_stopped() Status in lightdm package in Ubuntu: Fix Released Bug description: Lightdm crashes on boot on Ubuntu Raring. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2 Uname: Linux 3.8.0-10-generic x86_64 ApportVersion: 2.9-0ubuntu2 Architecture: amd64 Date: Wed Mar 6 09:12:55 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-03-03 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130303) MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x410518: mov0x28(%rax),%ecx PC (0x00410518) ok source "0x28(%rax)" (0xaad2) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: lightdm crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1148935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1153798] Re: after upgrade from 12.10 to 13.04 beta, the X11 login screen does not use the specified background
Closing assumed fixed.
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)
** Changed in: unity-greeter (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1153798
Title:
after upgrade from 12.10 to 13.04 beta, the X11 login screen does not
use the specified background
Status in unity-greeter package in Ubuntu:
Fix Released
Bug description:
I am running ubuntu with XFCE, and here is the content of my /etc/xdg
/xdg-xubuntu/lightdm/lightdm-gtk-greeter.conf
#
# background = Background file to use, either an image path or a color (e.g.
#772953)
# theme-name = GTK+ theme to use
# icon-theme-name = Icon theme to use
# font-name = Font to use
# xft-antialias = Whether to antialias Xft fonts (true or false)
# xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
# xft-hintstyle = What degree of hinting to use (hintnone, hintslight,
hintmedium, or hintfull)
# xft-rgba = Type of subpixel antialiasing (none, rgb, bgr, vrgb or vbgr)
# show-language-selector (true or false)
# show-indicators = semi-colon ";" separated list of allowed indicator
modules (e.g. indicator-sound.so)
#
[greeter]
background=/lib/plymouth/themes/xubuntu-logo/xubuntu-greybird.png
theme-name=Bluebird
icon-theme-name=elementary-xfce
font-name=Droid Sans 10
xft-antialias=true
xft-dpi=96
xft-hintstyle=slight
xft-rgba=rgb
show-language-selector=true
show-indicators=
The login screen, after the upgrade, does not use the background
specified above, but rather shows one of my desktop background ("one
of" -- dual monitor) stretched to the whole screen.
The file /lib/plymouth/themes/xubuntu-logo/xubuntu-greybird.png is
there.
Curiously, changing "theme-name=Bluebird" to "theme-name=Blackbird"
does have an effect, so the config file is being read on startup.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lightdm 1.4.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Tue Mar 12 01:51:36 2013
InstallationDate: Installed on 2012-11-19 (112 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
LightdmConfig:
[SeatDefaults]
user-session=ubuntu
greeter-session=lightdm-gtk-greeter
LightdmGreeterLog: ** (lightdm-gtk-greeter:1581): WARNING **: Failed to load
user image: Failed to open file '/home/kman/.face': No such file or directory
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1548): WARNING **: Failed to
load user image: Failed to open file '/home/kman/.face': No such file or
directory
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to raring on 2013-03-08 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1153798/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1157160] Re: lightdm fails to start after upgrade to quantal
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1157160 Title: lightdm fails to start after upgrade to quantal Status in lightdm package in Ubuntu: Fix Released Bug description: After upgrade to quantal a few days ago the grphical environment fails to start when the computer boots. I've tried switching to a VT (which works) and starting lightdm myself. If I use `sudo lightdm` and redirect the output to a file this works. If I use `sudo service lightdm start` this fails. The system will boot up fine if I edit the grub command line and remove $vt_handoff from the end ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Tue Mar 19 08:15:33 2013 InstallationDate: Installed on 2011-08-29 (567 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2013-03-12 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1157160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164515] Re: lightdm crashed with SIGSEGV in realloc()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1164515 Title: lightdm crashed with SIGSEGV in realloc() Status in lightdm package in Ubuntu: Fix Released Bug description: ubuntu 13.04 booting from usb ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 Date: Sat Mar 30 15:11:03 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2012-04-30 (338 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0xb728a0ce:call 0xb733e5e3 PC (0xb728a0ce) ok source "0xb733e5e3" (0xb733e5e3) ok destination "(%esp)" (0xbf1ceff0) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 realloc () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libgcrypt.so.11 ?? () from /lib/i386-linux-gnu/libgcrypt.so.11 gcry_realloc () from /lib/i386-linux-gnu/libgcrypt.so.11 Title: lightdm crashed with SIGSEGV in realloc() UpgradeStatus: Upgraded to raring on 2012-10-18 (168 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1164515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1159938] Re: lightdm crashed with SIGSEGV in seat_real_stop()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1159938 Title: lightdm crashed with SIGSEGV in seat_real_stop() Status in lightdm package in Ubuntu: Fix Released Bug description: upgrade to 13.04 and X is'nt start, but after restore xorg.conf X start with error ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic i686 ApportVersion: 2.9.2-0ubuntu4 Architecture: i386 Date: Mon Mar 25 21:29:11 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2012-11-25 (120 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x8057f83: mov0x14(%eax),%ebx PC (0x08057f83) ok source "0x14(%eax)" (0xaabe) not located in a known VMA region (needed readable region)! destination "%ebx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () ?? () g_cclosure_marshal_VOID__VOIDv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: lightdm crashed with SIGSEGV in g_cclosure_marshal_VOID__VOIDv() UpgradeStatus: Upgraded to raring on 2013-03-24 (1 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1159938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1160137] Re: lightdm crashed with SIGSEGV in seat_real_stop()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1160137 Title: lightdm crashed with SIGSEGV in seat_real_stop() Status in lightdm package in Ubuntu: Fix Released Bug description: Occasionally when cold booting Xubuntu 13.04 pre-release, my laptop (HP DM1Z) boots to only a terminal, and I have to issue a command (sudo service lightdm start) to load lightdm and XFCE. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu4 Architecture: amd64 Date: Mon Mar 25 20:27:42 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-03-08 (17 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x410462: mov0x24(%rax),%esi PC (0x00410462) ok source "0x24(%rax)" (0xaace) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: lightdm crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to raring on 2013-03-08 (17 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1160137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1170482] Re: LightDM refuses to load
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1170482 Title: LightDM refuses to load Status in lightdm package in Ubuntu: Fix Released Bug description: I installed nvidia-current and when I rebooted I got the error: 'failure to write byte: broken pipe' (or similar), rebooted and now I just get a blank screen (switched to tty2, reloaded lightdm several times, still won't work). This is probably a problem with either lightdm, xorg or nvidia-current. System Specs: Fully updated Ubuntu 12.04.2 "Precise Pangolin" LTS 64-bit lightdm1.2.3-0ubuntu2 nvidia-current304.88-0ubuntu-0.0.2 xorg1:7.6+12ubuntu2 Intel Pentium M (Dual-Core) @ 2.5GHz Nvidia GeForce 7050 (256MB GRAM) 4GB DDR2 RAM ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-27.46~precise1-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Thu Apr 18 20:52:25 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1170482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1161580] Re: lightdm crashed with SIGSEGV in _int_realloc()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1161580 Title: lightdm crashed with SIGSEGV in _int_realloc() Status in lightdm package in Ubuntu: Fix Released Bug description: Ubuntu Release: Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 uname -a: Linux lucas-Inspiron-5520 3.8.0-14-generic #24-Ubuntu SMP Fri Mar 22 19:45:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Package details lightdm: Installed: 1.5.2-0ubuntu1 Candidate: 1.5.2-0ubuntu1 Version table: *** 1.5.2-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 28 05:58:51 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-01-16 (70 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter autologin-user= MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f01a5d509d0:mov%rbx,-0x28(%rsp) PC (0x7f01a5d509d0) ok source "%rbx" ok destination "-0x28(%rsp)" (0x7fff23384fe0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 realloc () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 ?? () ?? () Title: lightdm crashed with SIGSEGV in realloc() UpgradeStatus: Upgraded to raring on 2013-01-23 (63 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1161580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162331] Re: lightdm crashed with SIGSEGV
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1162331 Title: lightdm crashed with SIGSEGV Status in lightdm package in Ubuntu: Fix Released Bug description: je ne sais pas ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sat Mar 30 20:17:58 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-03-26 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130326) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fa1f8b918d0:mov%rbx,-0x20(%rsp) PC (0x7fa1f8b918d0) ok source "%rbx" ok destination "-0x20(%rsp)" (0x7fff368f7ff8) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 ?? () ?? () ?? () Title: lightdm crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1162331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162523] Re: lightdm crashed with SIGSEGV in realloc()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1162523 Title: lightdm crashed with SIGSEGV in realloc() Status in lightdm package in Ubuntu: Fix Released Bug description: Sometimes it hides the password field, then after a few minutes crash. Other times it just hides the password field and sits there. Each way, when you reboot the machine, the error above (lightdm crashed with SIGSEGV in realloc()) is raised and reported here. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 Date: Sun Mar 31 12:06:58 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-02-28 (30 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130228) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0xb72ce0ce:call 0xb73825e3 PC (0xb72ce0ce) ok source "0xb73825e3" (0xb73825e3) ok destination "(%esp)" (0xbf2a0ff0) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 realloc () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libgcrypt.so.11 ?? () from /lib/i386-linux-gnu/libgcrypt.so.11 gcry_realloc () from /lib/i386-linux-gnu/libgcrypt.so.11 Title: lightdm crashed with SIGSEGV in realloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1162523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1174391] Re: LightDM doesn't start
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1174391 Title: LightDM doesn't start Status in lightdm package in Ubuntu: Fix Released Bug description: I'm using Ubuntu 13.04 dev with lightdm 1.6.0-0ubuntu2.1 0. On booting my system it will change to console 7 and the screen does go black. But after a few seconds this process stops and I'm seeing just text on console 7. Trying to manually start lightdm will result in the same behavior. If I'm installing GDM all is working fine. In the attachments is my Xorg.0.log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1174391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564721] Re: Unity8-dash render time is too high, causing frame skipping
** Description changed: Unity8-dash render time is too high, causing frame skipping On a 60Hz display you have 16.6ms per frame. So to keep things running smoothly your render time should be much lower than 16.6ms. $ restart unity8-dash MIR_CLIENT_PERF_REPORT=log MIR_CLIENT_FORCE_SWAP_INTERVAL=0 $ tail -f ~/.cache/upstart/unity8-dash.log MAKO: [2016-04-01 11:38:54.086901] perf: : 69.00 FPS, render time 13.96ms, buffer lag 29.76ms (3 buffers) [2016-04-01 11:38:55.103637] perf: : 73.81 FPS, render time 13.00ms, buffer lag 27.33ms (3 buffers) [2016-04-01 11:38:56.111953] perf: : 67.46 FPS, render time 14.19ms, buffer lag 30.60ms (3 buffers) ARALE: [2016-04-01 11:41:43.467067] perf: : 52.31 FPS, render time 18.54ms, buffer lag 61.60ms (3 buffers) [2016-04-01 11:41:44.491750] perf: : 53.71 FPS, render time 18.01ms, buffer lag 37.43ms (3 buffers) [2016-04-01 11:41:45.504621] perf: : 55.33 FPS, render time 17.53ms, buffer lag 37.03ms (3 buffers) Note(1): I have used MIR_CLIENT_FORCE_SWAP_INTERVAL=0 because it works around a problem with the Android platform's MIR_CLIENT_PERF_REPORT=log being rounded up to the next frame interval. It also has the nice - benefit of showing peak frame rate possible on a device (e.g. 69 FPS on + benefit of showing peak frame rate possible on a device (e.g. 73 FPS on mako above). Note(2): Yes you can use the same benchmark on 'unity8' instead of 'unity8-dash' however the results will be inaccurate -- limited and rounded to whole frames due to bug 1369763. Note(3): This is all possibly related to bug 1494795. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1564721 Title: Unity8-dash render time is too high, causing frame skipping Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Unity8-dash render time is too high, causing frame skipping On a 60Hz display you have 16.6ms per frame. So to keep things running smoothly your render time should be much lower than 16.6ms. $ restart unity8-dash MIR_CLIENT_PERF_REPORT=log MIR_CLIENT_FORCE_SWAP_INTERVAL=0 $ tail -f ~/.cache/upstart/unity8-dash.log MAKO: [2016-04-01 11:38:54.086901] perf: : 69.00 FPS, render time 13.96ms, buffer lag 29.76ms (3 buffers) [2016-04-01 11:38:55.103637] perf: : 73.81 FPS, render time 13.00ms, buffer lag 27.33ms (3 buffers) [2016-04-01 11:38:56.111953] perf: : 67.46 FPS, render time 14.19ms, buffer lag 30.60ms (3 buffers) ARALE: [2016-04-01 11:41:43.467067] perf: : 52.31 FPS, render time 18.54ms, buffer lag 61.60ms (3 buffers) [2016-04-01 11:41:44.491750] perf: : 53.71 FPS, render time 18.01ms, buffer lag 37.43ms (3 buffers) [2016-04-01 11:41:45.504621] perf: : 55.33 FPS, render time 17.53ms, buffer lag 37.03ms (3 buffers) Note(1): I have used MIR_CLIENT_FORCE_SWAP_INTERVAL=0 because it works around a problem with the Android platform's MIR_CLIENT_PERF_REPORT=log being rounded up to the next frame interval. It also has the nice benefit of showing peak frame rate possible on a device (e.g. 73 FPS on mako above). Note(2): Yes you can use the same benchmark on 'unity8' instead of 'unity8-dash' however the results will be inaccurate -- limited and rounded to whole frames due to bug 1369763. Note(3): This is all possibly related to bug 1494795. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1564721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564351] Re: Unity8 stuck on hint "Long swipe from the left edge to open the Today scope" and can't close it. Desktop left unusable.
** Summary changed: - "Swipe from the left edge to open the launcher" - do not work on the desktop + Unity8 stuck on hint "Long swipe from the left edge to open the Today scope" and can't close it. Desktop left unusable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1564351 Title: Unity8 stuck on hint "Long swipe from the left edge to open the Today scope" and can't close it. Desktop left unusable. Status in Canonical System Image: New Status in unity8 package in Ubuntu: In Progress Bug description: Can not unlock my desktop, swipe is not work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.12+16.04.20160330-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 31 19:29:50 2016 InstallationDate: Installed on 2016-03-11 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1564351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1001221] Re: 12.04 black screen with blinking cursor when switching users
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1001221 Title: 12.04 black screen with blinking cursor when switching users Status in lightdm package in Ubuntu: Fix Released Bug description: When switching users on 12.04 it will sometimes just go to a black screen with a cursor. The user switching to is not logged in yet. Expected behavior: Click current user up top> from the drop-down click the user wanting to log in > brought to the lightdm log in screen and log that user in Instead: Click current user up top> from the dropdown click the user wanting to log in > brought to a black screen with a blinking cursor From here, you cannot type or initiate any keyboard shortcuts other than Ctrl +Alt+F(1-6) to reach tty1 etc, or Ctrl+Alt+F7 to return to the user that you were originally trying to switch from. Ctrl+Alt+F8 will bring you back to the black screen. This happens pretty often so I should be able to test anything needed. Thanks! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Fri May 18 08:00:55 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1001221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1071693] Re: php5-mysql missing from metapackage lamp-server^
** Changed in: lightdm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1071693 Title: php5-mysql missing from metapackage lamp-server^ Status in lightdm package in Ubuntu: Invalid Bug description: When I installed the meta package lamp-server^, the package php5-mysql was not included. It should be included so that php works with mysql out of the box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1071693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1058498] Re: system halt and reboot does not work when lightdm is opened several times
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1058498 Title: system halt and reboot does not work when lightdm is opened several times Status in lightdm package in Ubuntu: Fix Released Bug description: Bug tested against the KDE flavour of lightdm, with lightdm-kde- greeter. Do not know if it occurs with standard lightdm. Steps to reproduce : DO : open your first session using lightdm. DO : now, while the first session is opened, open a second user session, again using lightdm (for example with the switch user command from KDE menu). DO : close the second user session using the "disconnect" command from KDE menu. Note that lightdm is not killed from the second X started while it should, just as KDM did. DO : now, from the first session, shutdown the computer. EXPECT : the computer should be shut down. ACTUAL : actually lightdm hangs after the session is closed, and user is forced to shutdown manually using the command line from a terminal. The same problem occurs if the user restarted lightdm using service lightdm restart command. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: i386 Date: Sat Sep 29 09:07:25 2012 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-26 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1058498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 954388] Re: after logging in I see for a while a screen with random colors and figures which looks like a dump of the memory
Closing assumed fixed. Sounds like a driver issue. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/954388 Title: after logging in I see for a while a screen with random colors and figures which looks like a dump of the memory Status in lightdm package in Ubuntu: Fix Released Bug description: After logging in I see the random colours and figures which looks like the dump of the memory. I am using Ubuntu 12.04 on my sony VPCS11M9R with Nvidia 310m. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 21:51:57 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120306) SourcePackage: lightdm UpgradeStatus: Upgraded to precise on 2012-03-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/954388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 886415] Re: No GUI for disabling guest account access
** No longer affects: lightdm (Ubuntu) ** No longer affects: lightdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/886415 Title: No GUI for disabling guest account access Status in gnome-control-center package in Ubuntu: Triaged Status in unity-control-center package in Ubuntu: Triaged Bug description: Given the tendancy to clone the MacUI, it would appear Ubuntu is missing an equivalent option to disable guest access. In OS X 10.7, you'll find it in a "Security and Privacy" control panel. I'm reporting this against LightDM as the file I had to edit to remove it was /etc/lightdm/lightdm.conf by adding the line: allow-guest=false Not allowing the target audience (people who don't (want to) know how to use the linux command prompt) to turn off guest access doesn't feel right. As it's kind of treated as an account of sorts (albeit temporary), I'd suggest in Ubuntu that perhaps it should be added to the "User Accounts" control panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/886415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 884083] Re: strange behavoir of menus in lightdm with gksu
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/884083 Title: strange behavoir of menus in lightdm with gksu Status in lightdm package in Ubuntu: Fix Released Bug description: Using lightdm on 11.10, I find that either I am confused by the behavior of gksu and menus or there is a bug somewhere. Here's an example... From a terminal, $ gksu -u someotheruser firefox Tools/Addons, download and insert 'foxyproxy standard'. Exit firefox $ gksu -u someotheruser firefox The Tools menu now contains sub-menu 'FoxyProxy Standard' as expected. Leave it running &, from another terminal, $ firefox Tools menu shows the FoxyProxy submenu, even though it is not installed for this user. Exit both firefox apps. $ firefox Tools menu nolonger has FoxyProxy (as it should not). $ gksu -u someotheruser firefox Tools menu nolonger has FoxyProxy (it should). This occurs when running lightdm. Due to a different bug (Bug #866083) I was forced to move back to gdm. In gdm, this behavoir is not seen and gksu/menus behave as expected. Looks like a lightdm bug to me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/884083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 952192] Re: After installing Linux kernel 3.2.9, purple stuck on the screen
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/952192 Title: After installing Linux kernel 3.2.9, purple stuck on the screen Status in lightdm package in Ubuntu: Fix Released Bug description: After installing Linux kernel 3.2.9, stuck on the purple. grafik card : asus eah3650 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Mar 11 12:07:52 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/952192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 918072] Re: Selecting other session in login screen doesn't do anything
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/918072 Title: Selecting other session in login screen doesn't do anything Status in lightdm package in Ubuntu: Fix Released Bug description: I think this is in lightdm. This is from a live session, and may not be indicative of a real installation. For the last while I've been unable to change sessions from the login screen. I will select a different desktop environment (gnome-shell, Unity 2d, anything) and log in. It will just log me into a Unity (3d) session. I notice that if I select a different session, type the username, and press enter, the dot is back on the original "Ubuntu" setting instead of my selected option. It seems like as soon as I press enter that my selection is erased and reverted. I believe this is a regression because it used to work earlier in this cycle. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.0.6-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1 Uname: Linux 3.2.0-9-generic x86_64 ApportVersion: 1.90-0ubuntu2 Architecture: amd64 CasperVersion: 1.298 Date: Wed Jan 18 05:21:39 2012 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120117) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/918072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 963553] Re: Please keep historical copies of log files in /var/log/lightdm
There's rotation there now. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/963553 Title: Please keep historical copies of log files in /var/log/lightdm Status in lightdm package in Ubuntu: Fix Released Bug description: It would be very nice if lightdm kept at least 1 historical copy of the logs in /var/log/lightdm. When X, libdrm or mesa hit an assertion it would only go to stderr for the X process and not the X log and we relied on GDM keeping 3 previous logs for each to post mortem debug issues involving that, but lightdm overwrites the logs on the next startup so the traces have disappeared when someone can actually file the bug. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 23 19:09:54 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac (20110427.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to precise on 2012-01-09 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/963553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 978215] Re: xscreensaver locks the screen when changing user
Don't use xscreensaver anymore.. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/978215 Title: xscreensaver locks the screen when changing user Status in lightdm package in Ubuntu: Invalid Bug description: In Lubuntu 12.04, when I choose to switch user, I arrive on the LightDM screen. If I reconnect on my account, the screen is locked and I have to type my password. This is useless because to reconnect on my account, I've already type my password In LightDM. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xscreensaver 5.15-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu5 Architecture: i386 Date: Tue Apr 10 19:38:52 2012 InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120201.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/978215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1064312] Re: lightdm crashes. No login screen after reboot / reset.
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1064312 Title: lightdm crashes. No login screen after reboot / reset. Status in lightdm package in Ubuntu: Fix Released Bug description: I'm on VMware Workstation 8 and 9. Not tested on physical machine. I'm having this issue since Alpha 1, but I always waited for a fix... till now. The first boot is fine (not always), but when I reboot or reset the VM, the bug appears. The symptoms are random. Sometimes you get a blinking cursor (_), or a lonely [ OK ] in the screen, or "Checking battery state... [ OK ]". Workaround: Login into console (Ctrl+Alt+F1) as root and enter "service lightdm start" twice. Then, the login screen appears. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 18:44:03 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1064312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 949777] Re: lightdm crashed with SIGSEGV in plymouth_run_command()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/949777 Title: lightdm crashed with SIGSEGV in plymouth_run_command() Status in lightdm package in Ubuntu: Fix Released Bug description: Apport notified that lightdm crashed. I didn't do nothing special. I use Ubuntu 12.04, lightdm 1.1.6-0ubuntu1. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.6-0ubuntu1 ProcVersionSignature: Uname: Linux 3.2.9-custom-14 i686 ApportVersion: 1.94.1-0ubuntu1 Architecture: i386 Date: Wed Mar 7 22:32:57 2012 ExecutablePath: /usr/sbin/lightdm InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120218) ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () ?? () g_cclosure_marshal_VOID(int0_t, void) () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: lightdm crashed with SIGSEGV in g_cclosure_marshal_VOID() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/949777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1044173] Re: Lightdm shows desktop artifacts when logging in
Closing assumed fixed. Sounds like a driver issue. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1044173 Title: Lightdm shows desktop artifacts when logging in Status in lightdm package in Ubuntu: Fix Released Bug description: This started yesterday -- when logging in, instead of showing a smooth transition displaying the wallpaper, lightdm now shows artifacts of desktop applications from before logging out. This includes private info, such as photos, partial webpages open, etc. This seems to be a recurring bug, as I've seen similar issues in 11.10 and 12.04. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Thu Aug 30 22:03:17 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1044173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1060886] Re: lightdm does not pass Xserver DPI setting to gnome-session
Closing assumed fixed. The solution wouldn't have been in lightdm anyway. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1060886 Title: lightdm does not pass Xserver DPI setting to gnome-session Status in lightdm package in Ubuntu: Fix Released Bug description: While most desktop users start gnome-session through lightdm login, lightdm does not pass DISPLAY DPI setting in /etc/X11/xorg.conf to the started gnome-session. I can see relative keywords in /var/log/Xorg.0.log indicating DPI setting is adopted by Xserver, and I see big font size in the unity-greeter interface indicating larger DPI setting in xorg.conf take effects. However inside the desktop, DPI is reset to default (96,96) with no reason. Further I use xrandr to set DPI to a larger value but see no effect. Using xpdyinfo shows DPI is still (96,96). So does gnome just abandoned the display dpi feature in the application level? or is it mandatory to set dpi always to (96,96) by gnome? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu5 Uname: Linux 3.6.0-030600-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CheckboxSubmission: dc89d7045010e30edab47e64ddffb63e CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Wed Oct 3 17:31:57 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-16 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1060886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1070655] Re: 12.04 LTS Hangs on login
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1070655 Title: 12.04 LTS Hangs on login Status in lightdm package in Ubuntu: Fix Released Bug description: Recently upgraded my laptop from Ubuntu 10.04 LTS to 12.04 LTS. Everything seemed to go well, system booted into 12.04, albeit very slowly. Was able to login no problem. Then shutdown. On next reboot ran into problem where system hangs at login. Get to splash screen with request for user password and have mouse control at that point, but when I enter my password the system stops responding. Ultimately I have to force a shutdown with the power button. The behavior is somewhat erratic in that sometimes the password request disappears along with the banner at top, other times it does not. Ocassionally I can succesfully login, after severl tries over the course of a hafl hour or more. Seems to be just happenstance. Have noticed a few things. First time after I upgraded and loggen in there was a login sound. Now the sound is muted, every time. My GRUB default kernel is 3.2.0-31. If I use GRUB I can usually login using the next kernel down the list, 2.6.32-43. I also have kernal 3.2.0-32 on the machine, but it does not show up in GRUB. I can't explain why not I can send along whatever log files you want, just need to know where to find them ... and succesfully login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1070655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 891083] Re: ubuntu wont log out/shut down
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/891083 Title: ubuntu wont log out/shut down Status in Session Menu: Confirmed Status in indicator-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Fix Released Bug description: logout: $ /usr/lib/indicator-session/gtk-logout-helper --logout ** (gtk-logout-helper:31585): DEBUG: Dialog type: logout ** (gtk-logout-helper:31585): DEBUG: Showing dialog to ask for user confirmation ** (gtk-logout-helper:31585): DEBUG: Dialog return response: 'okay' ** (gtk-logout-helper:31585): DEBUG: Asking Session manager to 'Logout' ** (gtk-logout-helper:31585): WARNING **: SessionManager action failed: Logout has been locked down ** (gtk-logout-helper:31585): DEBUG: Falling back to using ConsoleKit for action ** (gtk-logout-helper:31585): WARNING **: Unable to fallback to ConsoleKit for logout as it's a session issue. We need some sort of session handler. ** (gtk-logout-helper:31585): DEBUG: Finished action, quiting shutdown: $ /usr/lib/indicator-session/gtk-logout-helper --shutdown ** (gtk-logout-helper:5226): DEBUG: Dialog type: shutdown ** (gtk-logout-helper:5226): DEBUG: Showing dialog to ask for user confirmation ** (gtk-logout-helper:5226): DEBUG: Dialog return response: 'okay' ** (gtk-logout-helper:5226): DEBUG: Asking Session manager to 'RequestShutdown' ** (gtk-logout-helper:5226): DEBUG: Finished action, quiting release:11.10 indicator-session 0.3.7.1-0ubuntu1.1 what i expected: to be able to log out/shut down from unity bar what happened instead:nothing ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: indicator-session 0.3.7.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Nov 16 18:34:08 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: indicator-session UpgradeStatus: Upgraded to oneiric on 2011-11-13 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/891083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1070526] Re: Can't select any desktop except unity
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1070526 Title: Can't select any desktop except unity Status in lightdm package in Ubuntu: Fix Released Bug description: Whichever desktop environment is selected in lightdm you always end up in Unity! I've tried with LXDE, XFCE, Gnome and KDE but all I ever get is unity. Steps: In the login screen click the small Ubuntu logo Select a desktop environment, not Unity Enter you password Click the > to login Result: You get logged straight into Unity Expected Result: To be logged into the desktop environment selected. Versions: Ubuntu 12.10 fully updated lightdm 1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1070526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1060228] Re: dm-tool lock + alt-ctrl-f7
There is nothing LightDM can do to stop you switching VTs. It requests the session is locked using logind/ConsoleKit and then it's up to the session to lock itself. ** No longer affects: lightdm ** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1060228 Title: dm-tool lock + alt-ctrl-f7 Status in lightdm package in Ubuntu: Invalid Status in Gentoo Linux: Unknown Bug description: Ubuntu 12.04.1 lightdm 1.2.1-0ubuntu1 lightdm-gtk-greeter 1.1.5-0ubuntu1 * Run... dm-tool lock Press alt-ctrl-f7 Now I'm back in without a password. Same with switch-to-greeter I don't know if it's supposed to be this way or it's a security problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1060228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1043077] Re: upstart restarts DM to quickly
We don't use upstart anymore. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1043077 Title: upstart restarts DM to quickly Status in lightdm package in Ubuntu: Invalid Bug description: I am filing this against upstart since it seems to affect both lightdm and gdm. Basically, if I run: sudo service lightdm restart then it will fail with an "X Server already on display 0" message (in gdm logs) It appears that upstart is respawning the DM before the current X session has shutdown completely. If I instead do sudo service lightdm stop sudo service lightdm start it works perfectly. This is 100% reproducible on my 12.10 VM and happens around 1:5 times on my 12.10 installation on real machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1043077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1061149] Re: boot occasionally hangs while "Checking battery state..."
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1061149 Title: boot occasionally hangs while "Checking battery state..." Status in landscape-client package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This is a bit of an odd environment, but I've recently noticed that boot will occasionally hang just after "Checking battery state...". I don't know for sure it's /etc/acpi/power.sh that's hanging, but that seems like the most likely culprit. This is an up-to-date 12.10 guest running in VMware Fusion 5.0.1 (825449) on OS X 10.6.8. I've disabled the splash screen so I can watch the boot process. ctrl-C (and other keystrokes) seems to be echoed back to the console, but has no effect. When I send ctrl-alt-delete (via the VMware "Virtual Machine" menu item), I see "acpid exiting" and the machine shuts down and reboots. It usually successfully reboots after this, but not always. I suppose not surprisingly, this seems related to power status pass-through. If you go to VMware's settings->Other->Advanced and turn off "Pass power status to VM" then it seems like boot never hangs. Note though that I have had this setting enabled for ages, and enabling doesn't guarantee that the boot will hang. But it never seems to hang with the setting disabled. --- ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 12.10 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120709.1) Package: pm-utils PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Tags: quantal running-unity Uname: Linux 3.5.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.6.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barry 3957 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=d0d87984-8662-4d52-a2e5-fbb9dd3493e7 InstallationDate: Installed on 2012-07-10 (132 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120709.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=175800e0-cc7f-4820-8df3-7ae1df07f80e ro ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 RelatedPackageVersions: linux-restricted-modules-3.7.0-2-generic N/A linux-backports-modules-3.7.0-2-generic N/A linux-firmware 1.97 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: raring running-unity Uname: Linux 3.7.0-2-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/02/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1061149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1050462] Re: Unlock screen sends password to active session
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050462 Title: Unlock screen sends password to active session Status in lightdm package in Ubuntu: Fix Released Bug description: I've observed a very odd behavior a couple of times now when unlocking the screen. Basically, the password gets entered into the unlock dialog and also goes to whatever the active application is. I've observed it happen once when I typed the wrong password, and once with the right password. Since this isn't terribly clear, let me explain what happened. I was running a chat client and had an IM window up. I walked away from the computer for a few hours. I came back later and tried to unlock the screen. On the first attempt I entered a different password on accident (let's say I typed 'WrongPassword', followed by enter). On the second attempt, I realized my error and entered the correct password. I got in, but soon discovered that my first attempt went though to the IM window. So I ended up IM'ing 'WrongPassword' to a friend (luckily this was someone I trust). The timestamp on the IM lined up with the first login attempt. The second time I observed this, it was on the first password attempt (I typed the right password this time). The difference here is that it only picked up the last few characters from my password, and the active application was a terminal window instead of an IM window. I'm running Ubuntu 12.04 AMD64 and using GNOME3 (maybe that has something to do with it?). I talked to a coworker who had experianced a similar issue (also using GNOME3). I have a third system, also 12.04, AMD64 with GNOME 3 which has not had the issue (this particular machine gets locked and unlocked much more frequently). Does anyone have any Ideas? I'd be happy to post hardware details if you think they are relavent. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1054627] Re: upgrade to quantal; couldn't log in anymore; did not migrate my unity-2d pref properly
quantal end of life. ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1054627 Title: upgrade to quantal; couldn't log in anymore; did not migrate my unity- 2d pref properly Status in lightdm package in Ubuntu: Invalid Bug description: Hi, upgraded to quantal. unity-2d got removed; logging in through lightdm always returned to login prompt; couldnt switch my preferred session. had to install fluxbox to make the session selectionm mechanism reappear and then select ubuntu explicitely. after that I can now log into Ubuntu session on quantal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1054627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059928] Re: Lightdm [Kubuntu) not displaying user thumbnail photos
Is this still applicable? ** No longer affects: lightdm ** Changed in: lightdm (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1059928 Title: Lightdm [Kubuntu) not displaying user thumbnail photos Status in accountsservice package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Incomplete Bug description: On the Kubuntu login screen (I'm assuming lightdm?), there are just generic pictures for users. I expected it to display my photo along with my user name, as I configured in System Settings -> Account Details -> Change your image. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 1 21:53:35 2012 EcryptfsInUse: Yes InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1059928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1064061] Re: Lightdm doesn't start if /usr/share/lightdm/remote-sessions is missing
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1064061 Title: Lightdm doesn't start if /usr/share/lightdm/remote-sessions is missing Status in lightdm package in Ubuntu: Fix Released Bug description: Symptoms: - Screen goes black after booting and showing the plymouth ubuntu logo and stays black or - screen keeps switching back and forth between text and greaphics mode instead of showing the login screen How to trigger: - Take a system that has lightdm installed - Install gdm - select "gdm" as the new login manager - purge lightdm - restart the system - install lightdm-gtk-greeter (which automatically installs lightdm again) - select "lightdm" as login manager - restart the system Somehow the directories /usr/share/lightdm/remote-sessions and its parent directory /usr/share/lightdm get lost during this sequence and aren't created anew when lightdm is installed. How to recover in the case the problem has been triggered accidentally: - start the system in recovery mode - grab a root console - create the missing directory by typing mkdir -p /usr/share/lightdm/remote-sessions Did manage to trigger this problem twice on my computer since I switched to the developer's version of quantal (64 Bit). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu1 Uname: Linux 3.6.0-999-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 22:46:00 2012 EcryptfsInUse: Yes SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1064061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063103] Re: lightdm crashes when running a full screen Webex
Closing assumed fixed. Sounds like a driver / X issue anyway. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1063103 Title: lightdm crashes when running a full screen Webex Status in lightdm package in Ubuntu: Fix Released Bug description: I am running Ubuntu 12.04 LTS on my production machine which is a Dell E 4300 laptop. For emails and Webex, I have a VMware Workstation 9 installed which is running Windows XP professional 32 bit Often, when I am in full screen in Workstation and have Webex running fullscreen, if I need to click back to my second monitor (Ubuntu Desktop) the screen briefly flickers and lightdm crashes. Generallu Firefox is the only application that is running on Ubuntu at that moment and all Windows menubars etc dissappears and there is no way to gain access back to the desktop or the applications other than a restart of the machine aby hitting the Alt+Clrt+F1 and logging in and issuing a "reboot" command A sudo /etc/init.d/lightdm restart does not fix the issue. This is consistently being hit in 2 out of three Webex sessions ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30 Uname: Linux 3.2.0-32-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sun Oct 7 10:05:36 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1063103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063797] Re: Second monitor flickery and unusable
Closing assumed fixed. Sounds like a driver issue anyway. ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1063797 Title: Second monitor flickery and unusable Status in lightdm package in Ubuntu: Fix Released Bug description: After boot or after log out, my second monitor is flickery and unusable at the login screen. The mouse won't move from the primary monitor to the secondary. After login the secondary monitor works fine. In 12.04 the secondary monitor would show a clone of the primary monitor which it could be doing currently but the screen doesn't display correctly for me to know. lspci reports my graphics card as: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device 2008 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 Kernel modules: i915 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 15:00:29 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-25 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1063797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 902698] Re: lightdm crashed with SIGSEGV in check_stopped()
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Triaged => Fix Released ** Changed in: lightdm (Ubuntu Precise) Status: Triaged => Fix Released ** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm (Ubuntu Precise) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/902698 Title: lightdm crashed with SIGSEGV in check_stopped() Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Fix Released Bug description: Bug last reported on 2011/9/14 with "Fix Released" stated but seems to have happened again in 12.04 alpha ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: lightdm 1.0.6-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4 Uname: Linux 3.2.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Dec 11 11:25:45 2011 ExecutablePath: /usr/sbin/lightdm InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: lightdm ProcEnviron: PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x411138: mov0x28(%rax),%ecx PC (0x00411138) ok source "0x28(%rax)" (0xaad2) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: lightdm crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to precise on 2011-12-04 (6 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/902698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1047500] Re: on screen keyboard doesn't work for password field
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1047500 Title: on screen keyboard doesn't work for password field Status in unity-greeter package in Ubuntu: Confirmed Bug description: Get to logon screen Enable on screen keyboard Attempt to type password into OSK Observe no dots appearing in the password field. Note that you can still use a physical keyboard. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Fri Sep 7 17:25:51 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120102) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1047500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
