I too hit this bug after upgrade today. /var/run is not in my
/etc/fstab. Can you point me to the new bug? I'll submit my relevant
info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
See https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/811441
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X - incomplete migration to
I had the exact same issue documented here on upgrade from 11.04 to 11.10.
Removing the existing /var/run and /var/run/lock and replacing with sym links
as per #76 fixed it.
The impact of this was a total lack of system (wireless) networking
coming up - this gives a ! minute pause during boot,
Tom,
Please file a new bug report against the 'initscripts' package in Ubuntu
using the command 'ubuntu-bug initscripts' and include a copy of
/var/log/dist-upgrade/apt-term.log from the affected system, and
subscribe me to the resulting bug.
After you upgraded, did you reboot? If your system
mountall 2.28 and above include the /run mount, so marking this task as
resolved.
** Changed in: mountall (Ubuntu Oneiric)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:ubuntu/udev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X - incomplete migration to
/run
To manage notifications
Looks like bug #811441 might be a difference facet of the same
transition problem from /var/run to /run. The fix suggested here work
for that bug too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
#27 fixed my keyboard too, however my laptop Synaptic mouse is still
unusable even with a dist-upgrade of today (which means I also have the
#62 problem)... FYI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So, it is fixed? Can i use lightdm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X - incomplete migration to
/run
To manage notifications
I confirm, following Steve's suggestions all works great
Like Eduard, my problems began with a cups postinst failed upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric]
Hi, I'm in the same Eduard's situation, I think from 3-4 days ago.
Do you have a clean workaround steps?
I've only to remove /var/run, link /var/run to /run and remove /var/lock
?
And what about /var/lock? link to what?
--
You received this bug notification because you are a member of Ubuntu
I found the the root cause for the init script reordering and reported
it in #811675. Actually my system was broken several days before this
bug, but the brokenness showed up only due to the umountrootfs script
not being executed on reboot.
--
You received this bug notification because you are a
Davide,
The problem with removing /var/run and /var/lock and making them
symlinks yourself is that this breaks all the various things that access
sockets in either of these directories. If you do this on a desktop
system, your desktop will be broken until reboot, and may not even shut
down
Hi All,
The package update fixes my original VM that caused me to report this -
thanks all!
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not
The versions are:
mountall2.30
initscripts 2.88dsf-13.10ubuntu4
/var/run is not a symlink but a real directory on my harddisk (root
filesystem).
One further info: During installation of the upgrade, it looked like
that not all postinst scripts were executed properly because of the
Eduard Hasenleithner [2011-07-15 6:27 -]:
One further info: During installation of the upgrade, it looked like
that not all postinst scripts were executed properly because of the cups
postinst script failing.
This should be fixed in cups 1.4.7-1ubuntu1.
Could it be that the /var/run
Martin,
No, it's set up in an upstart job, so you need to reboot after
the upgrade.
Now that is strange, I rebooted already several times, but the situation
did not change. Maybe there is a chicken-and-egg problem of upstart not
triggering the symlink creation because there are still old (pid,
On Fri, Jul 15, 2011 at 08:05:25AM -, Eduard Hasenleithner wrote:
No, it's set up in an upstart job, so you need to reboot after
the upgrade.
Now that is strange, I rebooted already several times, but the situation
did not change. Maybe there is a chicken-and-egg problem of upstart not
I did the update/dist-upgrade but the situation did not change.
No, /etc/init.d/umountroot should unconditionally nuke /var/run on
reboot.
So I would suspect it does not get executed at all
Is your /etc/init.d/umountroot the unmodified version from the
package?
I didn't change it, md5sum is
On Fri, Jul 15, 2011 at 05:40:12PM -, Eduard Hasenleithner wrote:
Is your /etc/init.d/umountroot the unmodified version from the
package?
I didn't change it, md5sum is 36d5098f8a3965dce172a1c8f75e1429.
This is the correct md5sum.
Do the symlinks /etc/rc0.d/S60umountroot and
Do the symlinks /etc/rc0.d/S60umountroot and /etc/rc6.d/S60umountroot
exist?
Yes they do. Question: Do I remember correctly that the symlinks with S
are used for starting, and those with K for stopping? If that is the
case, why is start a No-op in the umountroot script?
--
You received this
On Fri, Jul 15, 2011 at 07:30:54PM -, Eduard Hasenleithner wrote:
Do the symlinks /etc/rc0.d/S60umountroot and /etc/rc6.d/S60umountroot
exist?
Yes they do. Question: Do I remember correctly that the symlinks with S
are used for starting, and those with K for stopping? If that is the
/shutdown.log is not created, so the umountrootfs is not executed at
all. Considering how fast the system reboots, I'm not sure if any script
from rc6.d is executed, but that is hard to tell since I have a SSD. I'd
be happy if somebody would help me finding the root cause for this in my
system.
Sorry for the further interruption, I think I found the reason:
the reboot script has the name S01reboot in rc6.d, so it gets executed before
S01umountroot. No clue why that could be.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On my oneiric install /var/run is not mounted anymore, but its contents go to
the root filesystem. When rebooting, on my system
* the dbus daemon does not start anymore because of the pid file from the
previous start,
* X11 does not start anymore because of the missing dbus daemon, and
* on the
Eduard,
What versions of initscripts and mountall do you have installed? If you
have upgraded initscripts, /var/run should have already been converted
to a symlink pointing at /run, and there should be no problem. Is
/var/run a symlink or a real directory on your system?
If you're seeing this
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X - incomplete migration to
/run
To manage notifications about
** Changed in: udev (Ubuntu Oneiric)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage
** Branch linked: lp:~ubuntu-core-dev/ubuntu/oneiric/udev/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications
This bug was fixed in the package udev - 172-0ubuntu2
---
udev (172-0ubuntu2) oneiric; urgency=low
* extras/cdrom_id/60-cdrom_id.rules: Revert hd* hack for powerpc; this
already is, or should be fixed in the powerpc kernel configuration to use
the SCSI interface. (Confirmed
Please correct me if I'm wrong, but I think base-files is ok now, as it
ships /run. What we need now is mountall actually putting a tmpfs mount
there, thus I add a mountall task.
** Package changed: base-files (Ubuntu Oneiric) = mountall (Ubuntu
Oneiric)
** Changed in: mountall (Ubuntu Oneiric)
As the udev safety belt is uploaded now, the remainder of the /run
transition (mountall and initramfs-tools, AFAICS) are not as urgent any
more. But still keeping targetted at oneiric, as we do want to finish
this or completely roll back, so keeping priority high.
** Changed in: mountall (Ubuntu
wow this bug is really nasty for not so experienced users, because they
get locked out of their system, but they shouldn´t install oneiric in
devstages either... Hope this patch gets distributed to the mirrors
soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Discussed with Steve. I'll take care of the initramfs-tools merge.
Debian's 0.99 version properly supports creating /run in the initramfs,
and moving it over to the actual system.
** Changed in: initramfs-tools (Ubuntu Oneiric)
Status: Triaged = In Progress
** Changed in: initramfs-tools
** Branch linked: lp:ubuntu/initramfs-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X - incomplete migration to
/run
To manage
** Description changed:
I've been running oneiric in a kvm guest for a while and updated it an
hour or so ago; the keyboard and mouse are not working in lightdm at all
- but if I log in remotely and chvt 1 the keyboard works in the console.
The VM is a kvm guest running on a natty
This bug was fixed in the package initramfs-tools - 0.99ubuntu1
---
initramfs-tools (0.99ubuntu1) oneiric; urgency=low
* Merge with Debian unstable. See 0.98.8ubuntu1 for remaining Ubuntu
changes. This version creates /run in the initramfs, and moves it over to
the running
I'm on this boat too... There's anything I can do or provide to help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications
Workaround for me was:
Copy /etc/X11/xorg.conf.failsafe to /etc/X11/xorg.conf
(Replaced gfx driver to mine)
Disabled HAL
Section ServerFlags
Option AutoAddDevices False
EndSection
Added a section for keyboard explicitly (for mouse it was not needed)
Section InputDevice
udevd complains about write permissions to /run/udev but even with chmod go+w
it does.
Is udev started before the fs is remounted rw?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
** Bug watch added: Debian Bug tracker #633441
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633441
** Also affects: udev (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633441
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Gentoo too it appears:
http://forums.gentoo.org/viewtopic-p-6740252.html?sid=d7f8891c41d1e31aa462d516e25c4345
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse
@Dave, thanks for downgrading all those components to help isolate the
change. Can you confirm that you are booting into the old X server?
$ apt-cache policy xserver-xorg-core
If it downgraded correctly it should show version 2:1.10.2-1ubuntu1.
Also post your Xorg.0.log and dmesg from after
Ok, nevermind my post #22. A bit more digging has revealed the problem
is this:
upgrade base-files 2011-07-08 01:23:13
6.3ubuntu2 6.3ubuntu4
There is a plan to transition from /var/run to /run, according to this
plan:
See comment #6 on this bug:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/807974
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in
That's a negative. Just downgraded to 6.3ubuntu1 and no joy.
However, I can confirm the xorg.conf workaround from comment #20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric]
I worked around it by doing a mv /run/udev /run/udev.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about this
@Bryce,
downgrading the whole system doesn't help, either. So maybe it's caused
by a removed or newly installed package or configuration file.
$ dpkg -l *udev* | grep ^.i
ii libgudev-1.0-01:167-0ubuntu3
GObject-based wrapper library
Confirming #27 with latest base-files. Likely the reason why downgrading
alone didn't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
mv /run/udev /run/udev.old worked for me, too!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about this bug go to:
at boottime I get the error:
udevd[363]: error: runtime directory '/run/udev' not writable, for now
falling back to /dev/.udev'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
The boottime error is a different bug, as pointed in comment #10
The tip given by #27 worked, and I believe the issue started for me
after I updated udev to 172-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marc Deslauriers' workaround in #27 did the trick for me, too. Thanks a
lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage
I can also comfirm that renaming (or deleting) the directory /run/udev is a
workaround.
So simply, having the directory /run/udev is problematic right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, all of /run seems to be a broken concept. None of the files
are in my dpkg database (using dpkg -S on them).
Where does /run come from?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Package base-files creates that directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about this bug go to:
Jason, /run is the new standard location for /var/run; one is currently
a symlink to the other. Nothing in there _should_ show up in dpkg, as
it's typically mounted as a tmpfs (i.e., ram only).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ijust did fix from #27 I still get udev error but keyboard and mouse are
working again. An odd thing just happened when Iapplied the fix it also
fixed my sound that was not working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
I've been running oneiric in a kvm guest for a while and updated it an
hour or so ago; the keyboard and mouse are not working in lightdm at all
- but if I log in remotely and chvt 1 the keyboard works in the console.
The VM is a kvm guest running on a natty
Ditto the above, re laptop.
mv /run/udev worked for me.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications
Great thanks for workaround in #27, worked for me. I was particularly
desperate, for I am testing Ubuntu on a laptop, and here I cannot re-
plug keyboard (however, pressing alt+sysrq+R and then alt+ctrl+f1 got me
to tty, from where I was able to installlaunch links2 to get to this
bug report),
According to
https://launchpadlibrarian.net/74981481/udev_172-0ubuntu1.diff.gz the
newly included changes are quite wide.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric]
** Changed in: base-files (Ubuntu Oneiric)
Status: New = Triaged
** Changed in: base-files (Ubuntu Oneiric)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I didn't lose my mouse like most people, but I did lose my keyboard. My
mouse freaked out, was flickering all over the screen and pressing both
mouse buttons (Laptop touchpad not mouse). After finally resolving
that, then my keyboard was no longer working, but the touchpad was
working fine.
Effectively, rename /run/udev to /run/udev.old solves the issue!
Still funny that an empty directory create such an issue ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric]
Merge proposal for a (temporary) fix:
https://code.launchpad.net/~rsalveti/ubuntu/oneiric/base-files/run-transition/+merge/67444
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
I've created a PPA with the proposed fix here:
https://launchpad.net/~bryce/+archive/lime
Can someone who is able to reproduce the issue still, verify that with
the above PPA the issue is fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
#27 worked for me to! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about this bug go to:
Initial testing shows the merge proposal from rsalveti I posted above
does not fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To
I'm working on getting the package installed from the PPA, I'll let you
know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage
To trivially reproduce the problem:
sudo dpkg -i /var/cache/apt/archives/base-files_6.3ubuntu4_i386.deb (or amd64)
sudo dpkg-reconfigure udev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
if sysvinit and initramfs-tools are going to take awhile to update
(which they probably will since its a very complex merge) perhaps
removing /run in the base-files postinst is the way to go? This should
be affecting 100% of upgraded systems now that there is a udev upgrade
today and is very
On Mon, Jul 11, 2011 at 11:36:38PM -, Robert Hooker wrote:
if sysvinit and initramfs-tools are going to take awhile to update
(which they probably will since its a very complex merge) perhaps
removing /run in the base-files postinst is the way to go? This should
be affecting 100% of
Oneiric Alpha 2 updated as of 11 July. No keyboard, no mouse.
No /run/udev either, so mv /run/udev /run/udev.old didn't work.
So I booted in recovery mode:
mkdir /run/udev
mv /run/udev /run/udev.old
Rebooted and Alpha 2 is up with keyboard mouse
Jerry
--
You received this bug
Nothing to do with udev, it just causes the initramfs to be rebuilt.
What happens is that apparently due to the recently uploaded base-files
there is now a /run directory, which might get partially populated
during runtime. Apparently during initramfs time, udev uses /dev/.udev,
but then when
I'll add some robustifications to udev while the transition is in
progress, to handle this case more gracefully.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Changed in: udev (Ubuntu Oneiric)
Importance: Undecided = High
** Changed in: udev (Ubuntu Oneiric)
Thanks Martin.
I could work again with the command:
rm -rf /run/udev
yeah mv didn't make any success... on my Thinkpad needed completely
removing. Thanks!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: udev (Ubuntu Oneiric)
Importance: High
Status: New
** Changed in: udev (Ubuntu Oneiric)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
** Changed in: udev (Ubuntu Oneiric)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
** Description changed:
I've been running oneiric in a kvm guest for a while and updated it an
hour or so ago; the keyboard and mouse are not working in lightdm at all
-
I've also run into this bug this morning when upgrading a Natty system
to this release. I can get the mouse to work again by unplugging and
re-plugging it (it's a USB mouse). This is using gdm as the session
manager, lightdm doesn't seem to work for me but I haven't poked at it
hard either.
My
This looks to be a udev bug. The udev log in the original post contains
/dev/input/event* notifications, but these don't have the various
IS_INPUT tags set, so X won't look at them. It's possible that these
tags get set later, but by then X will have already rejected those
devices as not input.
I ran into the same problem, updating from natty. Because of this bug, I
downgraded the system to natty again, but the problem persists (running
2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64).
Downgrading was performed by creating the following file, followed by
running
** Changed in: udev (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about
Similar bugs:
bug 807538
bug 807291
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about this bug go to:
Yeuch this is slow going; not hit anything that fixes it yet - so far:
dpkg -i udev_171-0ubuntu3_i386.deb libudev0_171-0ubuntu3_i386.deb
libgudev-1.0-0_1%3a171-0ubuntu3_i386.deb
upgrade udev 2011-07-08 01:21:43 171-0ubuntu3
171-0ubuntu4
Hey Bryce, just chiming in with a me too on this one... Let me know if I
can be of any help. My system was a natty system that started showing
this behavior immediately after distro upgrade yesterday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I tried starting X with --verbose 99 - the following looks relevant:
(II) config/udev: ignoring device /dev/input/event0 without property ID_INPUT
set
(II) config/udev: ignoring device /dev/sr0 without property ID_INPUT set
(II) config/udev: ignoring device /dev/bsg/1:0:0:0 without property
Log file shows no input devices. Possibly some issue with udev.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications
bug 807291 seems to confirm this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about this bug go to:
Thanks for your report.
Do you know after which package update the problem started ?
Could you please attach the file /var/log/apt/history.log
Thanks in advance
** Changed in: xorg (Ubuntu)
Importance: Undecided = Medium
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You
Hi,
Here are the contents of my history.log - there were quite a few things that
got updated - I'd also installed the -dbgsym for the xserver just before which
updated the xserver-xorg-core package:
-
Start-Date: 2011-07-08 01:09:34
Commandline: apt-get install
*** This bug is a duplicate of bug 807291 ***
https://bugs.launchpad.net/bugs/807291
** This bug has been marked a duplicate of bug 807291
Mouse and keyboard unresponsive until re-plugged in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** This bug is no longer a duplicate of bug 807291
Mouse and keyboard unresponsive until re-plugged in
** Changed in: xorg (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: xorg (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member
Hmm, from that list only the new linux-image seems likely. And that's
easy enough to prove/disprove - reboot, hold down the left shift to
bring up grub, and boot into a prior kernel version. If it works
properly then, that points to the kernel.
The history.log is interesting, but the dpkg.log
The older kernels (3.0-1 and 2.6.39 something) also don't work, so not that.
One thing I've had ever since I first upgraded that vm to OO is that during
boot I get the message:
error: runtime directory '/run/udev' not writeable, for now falling back
.
that's very early on (initrd?) -
** Attachment added: dpkg.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/807306/+attachment/2198167/+files/fiddle2-dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
** Attachment added: the previous dpkg.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/807306/+attachment/2198168/+files/fiddle2-dpkg.log.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Jul 08, 2011 at 10:44:31PM -, Dave Gilbert wrote:
The older kernels (3.0-1 and 2.6.39 something) also don't work, so not that.
One thing I've had ever since I first upgraded that vm to OO is that during
boot I get the message:
error: runtime directory '/run/udev' not
On Fri, Jul 08, 2011 at 10:44:31PM -, Dave Gilbert wrote:
dpkg-log's below.
Thanks for that. So, attached is the tabulated list of upgraded
packages. Quite a few actually, although few that have to do with
input, and only a small number of X packages.
Still, I would suggest testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[oneiric] Keyboard mouse not working in X
To manage notifications about this bug go to:
100 matches
Mail list logo
