so I was using email and clicked on a link last night. the chrome window came up, I started to move my mouse to the window, and the mouse froze.. for about 10 seconds, I moved it and it froze again. After a few rounds of this I went to a terminal window to see what is going on. I did my usual"sudo su" and typed in my password.. came back invalid.. after 3 times doing this ( usuing the same password I just logged in with) it locked me out. So I logged out, logged in with XFCE4, ran another terminal, and was successful doing the same sudo su command. Today I am logged back in with no problems SO far.. looking at syslog I see... about that time: Sep 19 20:32:56 pauls-server kernel: [43919.230270] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.243176] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.257043] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.271533] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.285273] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.299263] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.313130] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.327245] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71 Sep 19 20:32:56 pauls-server kernel: [43919.341235] logitech-djreceiver 0003:046 D:C52B.00ED: can't reset device, 0000:00:12.2-4.1/input2, status -71
then this: Sep 19 20:33:07 pauls-server mtp-probe: checking bus 1, device 58: "/sys/devices /pci0000:00/0000:00:12.2/usb1/1-4/1-4.1" Sep 19 20:33:07 pauls-server mtp-probe: bus: 1, device: 58 was not an MTP device Sep 19 20:33:11 pauls-server kernel: [43934.494398] hub 1-4:1.0: port 1 disabled by hub (EMI?), re-enabling... then more Sep 19 20:33:23 pauls-server mtp-probe: bus: 1, device: 60 was not an MTP device Sep 19 20:33:38 pauls-server kernel: [43961.355985] hub 1-4:1.0: port 1 disabled by hub (EMI?), re-enabling... Sep 19 20:33:38 pauls-server kernel: [43961.356351] usb 1-4.1: USB disconnect, d evice number 60 Sep 19 20:33:43 pauls-server kernel: [43966.244265] logitech-djreceiver 0003:046 D:C52B.0106: can't reset device, 0000:00:12.2-4.1/input2, status -110 Sep 19 20:33:43 pauls-server kernel: [43966.478324] usb 1-4.1: new full-speed US B device number 61 using ehci-pci
it seems to be doing the same thing over & over.. Sep 19 20:34:07 pauls-server kernel: [43990.008344] hub 1-4:1.0: port 1 disabled by hub (EMI?), re-enabling... Sep 19 20:34:07 pauls-server kernel: [43990.008708] usb 1-4.1: USB disconnect, d evice number 64 Sep 19 20:34:11 pauls-server kernel: [43994.752472] logitech-djreceiver 0003:046 D:C52B.011A: can't reset device, 0000:00:12.2-4.1/input2, status -110 Sep 19 20:34:12 pauls-server kernel: [43994.978539] usb 1-4.1: new full-speed US B device number 65 using ehci-pci
and it goes on & on for a few minutes doing this can't reset.... what happened???
Running TDE R14 here on Debian Sid, with binutils (and gcc-4.7) installed from earlier Jessie and held.
In Jessie binutils 2.23 has arrived: http://packages.debian.org/search?keywords=binutils&searchon=names&s...
binutils 2.23 causes the entire TDE to be removed in sid and will probably now also for Jessie.
One of many examples:
Package: kdesktop-trinity Source: tdebase-trinity
Depends: binutils (>= 2.22), binutils (<< 2.23), libacl1 (>= 2.2.51-8), libart-2.0-2 (>= 2.3.18), libc6 (>= 2.1.3), libfontconfig1 (>= 2.10.0), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.1.1), libgl1-mesa-glx | libgl1, libice6 (>= 1:1.0.0), libidn11 (>= 1.13), libjpeg8 (>= 8c), libkonq4-trinity (>= 4:14.0.0-r1184), libpcre3 (>= 8.10), libr0, libsm6, libstdc++6 (>= 4.1.1), libtqt3-mt (>= 4:14.0.0-r172), libtqtinterface, libx11-6, libxau6, libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxext6, libxrender1, libxss1, tdelibs14-trinity, zlib1g (>= 1:1.1.4), tdebase-trinity-bin (= 4:14.0.0-r1184-0debian8.0.0+pr54), eject, xdg-user-dirs
To hold binutils and gcc-4.7 seems the only solution at the moment.
**********
David
On Saturday 21 of September 2013 13:00:05 David Hare wrote:
Running TDE R14 here on Debian Sid, with binutils (and gcc-4.7) installed from earlier Jessie and held.
In Jessie binutils 2.23 has arrived: http://packages.debian.org/search?keywords=binutils&searchon=names&s... l§ion=all
binutils 2.23 causes the entire TDE to be removed in sid and will probably now also for Jessie.
One of many examples:
Package: kdesktop-trinity Source: tdebase-trinity
Depends: binutils (>= 2.22), binutils (<< 2.23), libacl1 (>= 2.2.51-8), libart-2.0-2 (>= 2.3.18), libc6 (>= 2.1.3), libfontconfig1 (>= 2.10.0), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.1.1), libgl1-mesa-glx | libgl1, libice6 (>= 1:1.0.0), libidn11 (>= 1.13), libjpeg8 (>= 8c), libkonq4-trinity (>= 4:14.0.0-r1184), libpcre3 (>= 8.10), libr0, libsm6, libstdc++6 (>= 4.1.1), libtqt3-mt (>= 4:14.0.0-r172), libtqtinterface, libx11-6, libxau6, libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxext6, libxrender1, libxss1, tdelibs14-trinity, zlib1g (>= 1:1.1.4), tdebase-trinity-bin (= 4:14.0.0-r1184-0debian8.0.0+pr54), eject, xdg-user-dirs
To hold binutils and gcc-4.7 seems the only solution at the moment.
David
It is unfortunate that tdelibs were built just a few days ago => shortly before the change binutils. Dependence on such a particular version of binutils is due to improved backtrace function (bfd library).
I'm just preparing a new patch for tdelibs. That would be a native reason for another rebuild tdelibs.
Slavek --
Running TDE R14 here on Debian Sid, with binutils (and gcc-4.7) installed from earlier Jessie and held.
In Jessie binutils 2.23 has arrived: http://packages.debian.org/search?keywords=binutils&searchon=names&s...
binutils 2.23 causes the entire TDE to be removed in sid and will probably now also for Jessie.
One of many examples:
Package: kdesktop-trinity Source: tdebase-trinity
Depends: binutils (>= 2.22), binutils (<< 2.23), libacl1 (>= 2.2.51-8), libart-2.0-2 (>= 2.3.18), libc6 (>= 2.1.3), libfontconfig1 (>= 2.10.0), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.1.1), libgl1-mesa-glx | libgl1, libice6 (>= 1:1.0.0), libidn11 (>= 1.13), libjpeg8 (>= 8c), libkonq4-trinity (>= 4:14.0.0-r1184), libpcre3 (>= 8.10), libr0, libsm6, libstdc++6 (>= 4.1.1), libtqt3-mt (>= 4:14.0.0-r172), libtqtinterface, libx11-6, libxau6, libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxext6, libxrender1, libxss1, tdelibs14-trinity, zlib1g (>= 1:1.1.4), tdebase-trinity-bin (= 4:14.0.0-r1184-0debian8.0.0+pr54), eject, xdg-user-dirs
To hold binutils and gcc-4.7 seems the only solution at the moment.
David
Good, I'm glad it finally arrived in Jessie. :-) Now I can fix the problem with sid as well.
Tim
-
David Hare -
Paul Cartwright -
Slávek Banko -
Timothy Pearson