** Attachment added: "21-Jan-2015 package upgrades I did afterwards"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316/+attachment/4305468/+files/aptitude-upgrade.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Attachment added: "21-Jan-2015 what was running when it happened"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316/+attachment/4305465/+files/done-it-again.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "21-Jan-2015 output from top"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316/+attachment/4305467/+files/top-output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I also had it happen again after installing the ppa. More info to
follow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password f
1. Do you use a multi-head setup? -- yes
If yes, using just one monitor fixes the issue? -- Sorry, I need them
both, can't test
2. Can you reproduce all the time? -- No, it only seems to happen after
several weeks of uptime.
3. Do you use ldap? -- I tried to, but couldn't get it working.
https:
Update installed. Will need to wait several weeks to see if the problem
recurrs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407523
Title:
Unity in lockscreen mode does not allow password entry
Will do. Thanks for the awesomely fast response!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407523
Title:
Unity in lockscreen mode does not allow password entry
To manage notifications about th
** Attachment added: "Output from dmidecode"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1407523/+attachment/4292112/+files/dmidecode.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407
System info:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
# uname -a
Linux grst01 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l unity
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407523
Title:
Unity in lockscreen mode does not allow password entry
To manage noti
I'm associating unity-services because it appears (from inspecting
running processes) that unity-panel-service is the thing that is
failing. However I would not be surprised to find it's really a bug in
compiz, or the NVidia driver.
Need guidance on what to do next to debug.
** Package changed:
Public bug reported:
Sometimes, when I come back to my computer after locking it, the
password field is not displayed. This means I cannot enter the password,
and I have to do an ungraceful shutdown of my X session.
It only happens when the workstation has been running for a while
(usually a few
This is almost certainly the same device reported in Bug #33 where I
have added my own report. I suggest the two bugs should be merged.
** Tags added: trusty
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because yo
Tried to follow the above instructions to use apport-collect, but I
guess apport-collect is not the reporting tool this year. So I tried the
same command using ubuntu-bug instead.
root@grpc192:~# apport-collect -p xserver-xorg-input-evdev 33
You need to run 'sudo apt-get install python-apport'
** Attachment added: "dmidecode output"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/33/+attachment/4115747/+files/dmidecode.txt
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because y
root@grpc192:~# lsinput
/dev/input/event0
bustype : BUS_HOST
vendor : 0x0
product : 0x1
version : 0
name: "Power Button"
phys: "PNP0C0C/button/input0"
bits ev : EV_SYN EV_KEY
/dev/input/event1
bustype : BUS_HOST
vendor : 0x0
product : 0x1
version : 0
n
No, sorry. I'm going to run the upgrade to Dapper soon, so it's probably
best to write it off as unconfirmed. I haven't had that crash again
since, and I suspect that something I've installed or upgraded has
either fixed it or masked the problem.
On Thu, 2006-08-10 at 22:49 +, Carthik Sharma
17 matches
Mail list logo
