Code: Select all
uname -a
Linux debian 3.2.0-2-amd64 #1 SMP Fri Jun 1 17:49:08 UTC 2012 x86_64 GNU/Linux
root@debian:/home/wayne# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.Well...... Not really fixed, as I have to unplug/replug on every boot to get mouse/keyboard working.GeneC wrote: I am running the latest Liquorix kernel.
Today
Added Siduction RepoUpgradedCode: Select all
gene@zordon:~$ inxi -r Repos: Active apt sources in file: /etc/apt/sources.list deb http://mirror.csclub.uwaterloo.ca/linuxmint-packages/ debian main upstream import backport romeo deb http://security.debian.org/ testing/updates main contrib non-free #"Debian Security" deb http://http.us.debian.org/debian/ unstable main contrib non-free #"SID" deb http://www.deb-multimedia.org sid main non-free #"SID Multimedia - NEW" deb http://packages.siduction.org/siduction/ unstable main contrib non-free #"Siduction" deb http://packages.siduction.org/razorqt/ unstable main #"Siduction-RazorQT" Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list deb http://dl.google.com/linux/chrome/deb/ stable main #"Chrome" Active apt sources in file: /etc/apt/sources.list.d/liquorix.list deb http://liquorix.net/debian/ sid main #"Liquorix"Re-bootCode: Select all
Commit Log for Fri Jun 8 06:21:21 2012 Upgraded the following packages: initscripts (2.88dsf-22.1) to 2.88dsf-26 sysv-rc (2.88dsf-22.1) to 2.88dsf-26 sysvinit (2.88dsf-22.1) to 2.88dsf-26 sysvinit-utils (2.88dsf-22.1) to 2.88dsf-26
Mouse Cursor and keyboard frozen...
Tried Greg's suggestion. ....Unplugged/Replugged- Mouse/Keyboard (both USB2)...
That worked. First time for that....
Thanks for finding that bug report. I notice in the report that people mention the problem is having /run be a symlink to /var/run. If the /run link is removed and an actual directory put in its place then some users on that thread are stating that it works fine. Am I understanding that correctly? Anybody here tried that?craigevil wrote:The actual bug:
#669949 - sysvinit: Break X11: no more mouse and keyboard - Debian Bug report logs - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669949
Either downgrade to testing version, or add the sidcution repo and install their fixed packages.
deb http://packages.siduction.org/razorqt/ unstable main
apt-get update && apt-get dist-upgrade
should install the fixed packages as they are a higher version than the packages in the 'official' Debian sid repo.
Get rid of:GeneC wrote:Well...... Not really fixed, as I have to unplug/replug on every boot to get mouse/keyboard working.GeneC wrote: I am running the latest Liquorix kernel.
Today
Added Siduction RepoUpgradedCode: Select all
gene@zordon:~$ inxi -r Repos: Active apt sources in file: /etc/apt/sources.list deb http://mirror.csclub.uwaterloo.ca/linuxmint-packages/ debian main upstream import backport romeo deb http://security.debian.org/ testing/updates main contrib non-free #"Debian Security" deb http://http.us.debian.org/debian/ unstable main contrib non-free #"SID" deb http://www.deb-multimedia.org sid main non-free #"SID Multimedia - NEW" deb http://packages.siduction.org/siduction/ unstable main contrib non-free #"Siduction" deb http://packages.siduction.org/razorqt/ unstable main #"Siduction-RazorQT" Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list deb http://dl.google.com/linux/chrome/deb/ stable main #"Chrome" Active apt sources in file: /etc/apt/sources.list.d/liquorix.list deb http://liquorix.net/debian/ sid main #"Liquorix"Re-bootCode: Select all
Commit Log for Fri Jun 8 06:21:21 2012 Upgraded the following packages: initscripts (2.88dsf-22.1) to 2.88dsf-26 sysv-rc (2.88dsf-22.1) to 2.88dsf-26 sysvinit (2.88dsf-22.1) to 2.88dsf-26 sysvinit-utils (2.88dsf-22.1) to 2.88dsf-26
Mouse Cursor and keyboard frozen...
Tried Greg's suggestion. ....Unplugged/Replugged- Mouse/Keyboard (both USB2)...
That worked. First time for that....
Code: Select all
Repos: Active apt sources in file: /etc/apt/sources.list
deb http://ftp-mirror.internap.com/pub/debian/ unstable main contrib non-free
deb-src http://ftp-mirror.internap.com/pub/debian/ unstable main contrib non-free
deb http://ftp-mirror.internap.com/pub/debian/ experimental main contrib non-free
deb http://www.deb-multimedia.org/ sid main non-free
deb http://dl.google.com/linux/chrome/deb/ stable main
deb http://dl.google.com/linux/musicmanager/deb/ stable main
deb http://download.jitsi.org/deb/ unstable/
deb http://packages.siduction.org/razorqt/ unstable main
deb http://liquorix.net/debian/ sid mainI can confirm that this solves the problem of the not responding mouse and keyboard.cooleric1234 wrote: I notice in the report that people mention the problem is having /run be a symlink to /var/run. If the /run link is removed and an actual directory put in its place then some users on that thread are stating that it works fine. Am I understanding that correctly? Anybody here tried that?
I used this method a long time ago...to correct an error message at shutdowngcp wrote:I notice in the report that people mention the problem is having /run be a symlink to /var/run. If the /run link is removed and an actual directory put in its place then some users on that thread are stating that it works fine.
In Aptosid and in pure Debian itself, /run is a Directory and /var/run is a link to /run.Brian49 wrote:I take it that this /run - /var/run move is a suggested workaround; it surely can't be the basic cause of the problem with the package updates.
...this was the moment i googled about /run to solve the error messages at shutdown...Regulus74 wrote: I used this method a long time ago...to correct an error message at shutdown
gcpgcp wrote:I can confirm that this solves the problem of the not responding mouse and keyboard.cooleric1234 wrote: I notice in the report that people mention the problem is having /run be a symlink to /var/run. If the /run link is removed and an actual directory put in its place then some users on that thread are stating that it works fine. Am I understanding that correctly? Anybody here tried that?
1) as root, delete the link /run
2) make a directory /run
3) reboot
/var/run will automagically change to a link.
initscripts sysv-rc sysvinit sysvinit-utils are version 2.88dsf-26
(with other known bugs reported by apt-listbugs)
another fix is to downgrade these packages...
Code: Select all
eric@crlsns ~ $ sudo apt-get -s --reinstall install sysvinit -t unstable
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reinstallation of sysvinit is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
eric@crlsns ~ $ sudo apt-get -s install sysvinit -t unstable
Reading package lists... Done
Building dependency tree
Reading state information... Done
sysvinit is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.Code: Select all
eric@crlsns ~ $ sudo apt-cache policy sysvinit
sysvinit:
Installed: 2.88dsf-26.1
Candidate: 2.88dsf-26.1
Version table:
*** 2.88dsf-26.1 0
100 /var/lib/dpkg/status
2.88dsf-26 0
990 http://ftp.debian.org/debian/ unstable/main amd64 Packages
Just for future reference see item 6.3.6 below for installing .debs on an unbootable system.GeneC wrote:For me, I have learned that running SID I have to make frequent backups with Clonezilla. Ten Minutes to clone a partition, and about the same to restore.
Sometimes you can fix a borked installation, sometimes, not so easy. Some times you don't want to mess around and get back on quickly. That's the time to restore partition with Clonezilla. That's what i did with my above problem.
That is not helping you though, sorry.
To fix it?
I really have no idea. Wish I did.
Perhaps someone has a fix for you.
Look at some of the other forum links on the first post.
http://forums.linuxmint.com/viewtopic.php?f=198&t=70230
If I come across something. I will let you know with a post here.
GregE wrote:Just for info. It appears that whether you suffered from the /run issue or not is simply a matter of how old your install is. The default Debian layout changed. Mine was fine because I started again on my new shiny SSD only recently. The fun of a rolling release.
maybe try the packages that craigevil suggested above - from Siduction. Or just replug keyboard amd mouse for a few days and wait for another update.Brian49 wrote:Can I see if I've got this clear, please? On my system, /run is already an unlinked directory and /var/run is a link to /run. But I get the keyboard/mouse issue when I update the "sysv" packages. So it looks as if the suggested workaround is already in place here, but isn't mitigating the problem.