Hi there.
Every once in a while, my task switching routine (edit in Kate, compile
in Konsole, debug in another Konsole session over ssh) gets disrupted
when some random window I have in the background gains focus when I alt-tab.
I guess it's meant to remind me that I have other windows open, but I'd
rather it didn't do that.
Is there a way to turn it off?
Thanks in advance,
Philip Ashmore
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???
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
I recently upgraded to 3.5.13.2 and discovered the SAK.
Since then I *sometimes* have big issues after waking up from s2ram on
my laptop: the alt+ctrl+del does not work at all and I cannot login to
my session anymore.
The problem looks like random.
Any clue for that? (I spent one hour searching the list with no
success)
Nicolas
Has anyone successfully installed the Trinity Desktop in Debian Testing?
I managed to follow the wiki directions for Debian 7.1.0 without any
glitches, however there are no /etc/apt/sources.list entries for Jessie.
Any suggestions will be much appreciated.
Thanks in advance.
Hi All,
I assume that any desktop manager, such as GDM for example, can be used
with TDE, instead of trinity-kdm?
The reason I ask is I'm having problems getting xming working from a
Win7 pc (just getting blank, black screen) and I always found gdm more
user friendly.
Cheers,
Mike.
--
Hi, I Installed Trinity using the instructions at
http://www.trinitydesktop.org/wiki/bin/view/Documentation/OpenSUSEBinaryIns…
but
it does not work out of the box this way.
I'm hoping someone with write privileges can add these steps to the wiki
In /etc/profile:
Change the lines pointing to /opt/kde3 to /opt/trinity so the binaries will
be in the PATH
In /etc/sysconfig/displaymanager:
Change DISPLAYMANAGER to say DISPLAYMANAGER=/opt/trinity/bin/kdm
using just kdm doesn't work, even with PATH set correctly.
Also, openSUSE 11.4 repository is broken, there were some dependency issues
with the trinity-desktop package. I'll look into that again later.
Thank you!
this comes up on any automake builds. Too new.
root [ /sources/kde/ktorrent-trinity-3.5.13.2/build ]# make -f
../admin/Makefile.common
*** YOU'RE USING automake (GNU automake) 1.14.
*** TDE requires automake 1.6.1 or newer
make: *** [cvs] Error 1
root [ /sources/kde/ktorrent-trinity-3.5.13.2/build ]#
After a plug on the Debian mailing list I got the following reply (which many
of you may already have seen):
<quote>
Alas, Trinity's Debian repo does not appear to work for Jessie.
</quote>
I'm sure that some of you must be running Jessie - or are we all waiting for
14 to bed in on Wheezy, Stable, first?
Lisi
