Re: Control key problem
Em Terça 27 Dezembro 2005 22:45, o André Wöbbeking escreveu: > On Monday 26 December 2005 19:55, Halestino Pimentel wrote: > > Em Segunda 26 Dezembro 2005 18:46, o André Wöbbeking escreveu: > > > Did you also configure X11 to use 105 keys layout? > > > > Yes. Here's the xorg.conf part that defines my keyboard: > > > > Section "InputDevice" > > Identifier "Generic Keyboard" > > Driver "keyboard" > > Option "CoreKeyboard" > > Option "XkbRules" "xorg" > > Option "XkbModel" "pc105" > > Option "XkbLayout" "pt" > > EndSection > > Is maybe the "pt" layout broken? I've tried with the "us" layout and got the same problem. > > > Also strange is that a while ago the key start behaving normally > > without any configuration and now she's back to her problematic > > behavior. I'm using my right control key, but I'm really not used to. > > Did you also try to disable KDE's key handling (layout and xkb)? Yes. And Xkb in KDE is always disabled with me. > > > Cheers, > André Regards, Halestino
Re: Control key problem
On Monday 26 December 2005 19:55, Halestino Pimentel wrote: > Em Segunda 26 Dezembro 2005 18:46, o André Wöbbeking escreveu: > > Did you also configure X11 to use 105 keys layout? > > Yes. Here's the xorg.conf part that defines my keyboard: > > Section "InputDevice" > Identifier "Generic Keyboard" > Driver "keyboard" > Option "CoreKeyboard" > Option "XkbRules" "xorg" > Option "XkbModel" "pc105" > Option "XkbLayout" "pt" > EndSection Is maybe the "pt" layout broken? > Also strange is that a while ago the key start behaving normally > without any configuration and now she's back to her problematic > behavior. I'm using my right control key, but I'm really not used to. Did you also try to disable KDE's key handling (layout and xkb)? Cheers, André
Re: Control key problem
Em Terça 27 Dezembro 2005 21:36, o David Pastern escreveu: > On Wed, 2005-12-28 at 07:33 +1100, Halestino Pimentel wrote: > > All options are disabled and the problem still persists. > > > > Best regards, > > > > Halestino > > Out of curiousity, does the problem persist: > > 1. If you boot into single user mode (ie. no X)? > No. In tty1 to tty6 there isn't any problem. > 2. If you plug in an external keyboard? > I can't test that option 'cause I don't have any external keyboard with me. Perhaps only after tomorrow. > My guess is it's an X issue, try doing a dpkg-reconfigure whilst in > single user mode on these packages: > > x11-common > xserver-xorg > xserver-common > I reconfigured all packages and changing some options but the problem persists :-( > Does the problem persist in other desktop environments, ie. Gnome, XFCE > etc? > No. Just in KDE. In Gnome, the key behaves just fine. > That's about all I can honestly think of trying/checking, hopefully it > sheds some more light on the problem. > All contributions help. Thanks. > Dave One more strange discovery: - when I'm editing some text, if I want to jump between words (using CRTL_right + left (or right) cursor key) the cursor stays in the same place blinking (ab)normally. If I use the Shift key with left (or right) cursor key selecting some text and start pressing the CONTROL-left key I begin to select word by word, which is normal. Unpressing the shift key, but still pressing CONTROL_left and left (or right) cursor key, the CONTROL_left key behaves normally making the cursor jump to the beginning of the next word which is the expected behavior. If I release the CONTROL_left key, and press it again, the cursor stays still again :-( Seems like the Shift key is responsible for "unblocking" the CONTROL_left key. Is there any bad configuration in Control Center that I could have made? Halestino
Re: KDE froze 1/2 way through startup after upgrade
On Sat, Dec 24, 2005 at 12:37:22PM +0100, Florian Kulzer wrote:
> Hello Ross,
>
> Ross Boylan wrote:
> >I just upgraded from KDE 3.3 -> 3.4 in testing. Before the upgrade I
> >did /etc/init.d/kdm stop, and after /etc/init.d/kdm start.
> >Things looked OK, and I logged in. The window that shows progress in
> >starting up the session showed up, and reached 50%. Then it just sat
> >there.
>
> Did you upgrade /etc/kde3/kdm/kdmrc to the package maintainer's new
> version? There were substantial changes going from 3.3 to 3.4, and
> certain commands in a user's .bash_profile can now hang KDE during
> startup. See /usr/share/doc/kdm/NEWS.Debian.gz for more info.
/etc/kde3/kdm/kdmrc was upgraded. It didn't even ask a question,
presumably because I hadn't touched it.
>
> As a first step to narrow down our search I would suggest that you
> create a new "clean" user and see if you can start KDE when you log in
> as that user. Then we know immediately if the problem is something in
> your regular user's $HOME or if we have to look elsewhere.
I am able to login as a new user. On the first try I got a message
"Error while initializing the sound driver
device /dev/dsp can not be opened (permission denied)"
I added the new user to the audio group and logged in again. This
time I didn't get the error. However, no sound is working, and the
problem appears to be below the KDE or arts level. Even with arts
suspended xmms didn't produce any sounds (I also tried to adjust all
the mixer controls).
>
> >It doesn't seem to be using any CPU. I did not hear any sound, and
> >I'm not sure the sound was working even before the upgrade. I have a
> >2.4 kernel with alsa, both custom built.
>
> There are a number of command-line tools for alsa, e.g. alsamixer,
> alsaconf, alsactl, speaker-test. These might be helpful to see if there
> is anything wrong with your sound system. You can also check if you get
> any error messages when you restart alsa-utils. ("invoke-rc.d alsa-utils
> restart" as root)
The only messages from the restart were "shutting down" and "starting up."
>
> >.xsession-errors on the account I logged into ends with
> >
> >kbuildsycoca: WARNING: '/usr/share/applications/mplayer.desktop' specifies
> >undefined mimetype/servicetype 'video/x-ms-wmx'
> >kbuildsycoca: WARNING: '/usr/share/applications/mplayer.desktop' specifies
> >undefined mimetype/servicetype 'video/x-ms-wvx'
> >DCOP Cleaning up dead connections.
>
> These should all be harmless.
>
> >libhal.c 767 : org.freedesktop.DBus.Error.ServiceDoesNotExist raised
> >"Service "org.freedesktop.Hal" does not exist"
>
> That seems to indicate that you do not have the package "hal" installed,
> or that the hal-daemon is not running. As far as I know KDE works fine
> without this Hardware Abstraction Layer, it is just a "nicer" way to
> keep track of and interact with the various hardware components of your
> system.
>
Thanks for the info.
[...]
> >kmix: ERROR: Mixer_ALSA::setEnumIdHW(25), errno=-22
>
> That looks like kmix (KDE audio mini-mixer) is doing something wrong
> with alsa. You can try to (re)move the kmix configuration files in
> ~/.kde/share/config/ (everything that starts with "kmix" and ends with
> "rc") and see if the problem goes away.
I had already done that before the original report. I get different
> errors, but still no startup.
> A somewhat harsher approach
> would be to temporarily rename /usr/bin/kmix and replace it with a
> symlink to /bin/true ("do nothing, successfully"). This is a rather
> nasty hack and no permanent solution, but it could prove that kmix is
> indeed the reason for your problem. (However, this might fail if the KDE
> startup procedure expects that kmix returns more parameters than just
> "success".)
>
> I hope this helps.
>
> Regards,
>Florian
>
>
I don't need the sound working, though that would be nice. I would
like to be able to login to KDE, however :)
I appreciate your help.
Ross
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Control key problem
Em Terça 27 Dezembro 2005 09:31, o José Couto escreveu: > On Monday 26 December 2005 18:45, Halestino Pimentel wrote: > > Em Segunda 26 Dezembro 2005 15:28, o André Wöbbeking escreveu: > > > On Monday 26 December 2005 12:50, Halestino Pimentel wrote: > > > > Hi all, > > > > > > > > I have a HP Pavilion DV4285EA laptop and I'm with a problem: when KDE > > > > starts, my left control key acts strange. For example: > > > > - the left CONTROL key don't react to a CONTROL+C; > > > > - in Konsole, to open a new command line, if I issue, in order, > > > > (left)CONTROL+ALT+N nothing happens, but if I issue, in order, > > > > ALT+(left)CONTROL+N, a new command line is open; > > > > With the right CONTROL key, there isn't any problem. > > > > This problem only occurs in KDE, since in tty1-6 the all CONTROL keys > > > > work 100%. > > > > The keyboard model configured in Control Center is Pc with 105 keys > > > > (Intl) generic and the keyboard map is pt. I tried other models and > > > > the probem persists. > > > > > > Did you configure any XKB options in control center? You can also run > > > xev to see which key code is generated by your CONTROL key. > > > > > > > > > Cheers, > > > André > > > > Hi André, > > > > Thanks for your answer. XKB options in control center are not configured. > > Running xev I've got the following output: > > > > - For my right control key (which works fine): > > > > KeyPress event, serial 31, synthetic NO, window 0x421, > > root 0x46, subw 0x0, time 20056922, (70,-13), root:(530,238), > > state 0x0, keycode 109 (keysym 0xffe4, Control_R), same_screen YES, > > XLookupString gives 0 bytes: > > XmbLookupString gives 0 bytes: > > XFilterEvent returns: False > > > > KeyRelease event, serial 31, synthetic NO, window 0x421, > > root 0x46, subw 0x0, time 20056976, (70,-13), root:(530,238), > > state 0x4, keycode 109 (keysym 0xffe4, Control_R), same_screen YES, > > XLookupString gives 0 bytes: > > > > - For my left control key (the problematic key): > > > > FocusOut event, serial 31, synthetic NO, window 0x421, > > mode NotifyGrab, detail NotifyAncestor > > > > FocusIn event, serial 31, synthetic NO, window 0x421, > > mode NotifyUngrab, detail NotifyAncestor > > > > KeymapNotify event, serial 31, synthetic NO, window 0x0, > > keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > > > Kind of strange: seems like the behavior of a mouse... > > Can you interpret this result? > > Halestino, > > Try to disable any Accessibility option in control center. > > Regards. All options are disabled and the problem still persists. Best regards, Halestino
Re: The GTK Qt engine needs to be patched.
On Monday 19 December 2005 08:02, Jan De Luyck wrote: > On Saturday 10 December 2005 19:55, Matt Sicker wrote: > > Since this is a package more useful to KDE users than GNOME users, I > > thought this would be an appropriate place to mention this. > > > > The gtk2-engine-gtk-qt package is not patched to fixed the black menus > > bug. Here is the patch for 0.6: > > I've rebuild gtk2-engines-gtk-qt with this fix, works like a charm. Package > is available from http://debian.kcore.org/, use at own risk. It didn't eat > my laptop tho :p This package is built against kdelibs4c2a (>= 4:3.5.0-1), and I don't want to install kde from experimental. Does anybody know if there's a package available for unstable or testing? Thanks for any hint, Johannes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Control key problem
On Monday 26 December 2005 18:45, Halestino Pimentel wrote: > Em Segunda 26 Dezembro 2005 15:28, o André Wöbbeking escreveu: > > On Monday 26 December 2005 12:50, Halestino Pimentel wrote: > > > Hi all, > > > > > > I have a HP Pavilion DV4285EA laptop and I'm with a problem: when KDE > > > starts, my left control key acts strange. For example: > > > - the left CONTROL key don't react to a CONTROL+C; > > > - in Konsole, to open a new command line, if I issue, in order, > > > (left)CONTROL+ALT+N nothing happens, but if I issue, in order, > > > ALT+(left)CONTROL+N, a new command line is open; > > > With the right CONTROL key, there isn't any problem. > > > This problem only occurs in KDE, since in tty1-6 the all CONTROL keys > > > work 100%. > > > The keyboard model configured in Control Center is Pc with 105 keys > > > (Intl) generic and the keyboard map is pt. I tried other models and > > > the probem persists. > > > > Did you configure any XKB options in control center? You can also run > > xev to see which key code is generated by your CONTROL key. > > > > > > Cheers, > > André > > Hi André, > > Thanks for your answer. XKB options in control center are not configured. > Running xev I've got the following output: > > - For my right control key (which works fine): > > KeyPress event, serial 31, synthetic NO, window 0x421, > root 0x46, subw 0x0, time 20056922, (70,-13), root:(530,238), > state 0x0, keycode 109 (keysym 0xffe4, Control_R), same_screen YES, > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False > > KeyRelease event, serial 31, synthetic NO, window 0x421, > root 0x46, subw 0x0, time 20056976, (70,-13), root:(530,238), > state 0x4, keycode 109 (keysym 0xffe4, Control_R), same_screen YES, > XLookupString gives 0 bytes: > > - For my left control key (the problematic key): > > FocusOut event, serial 31, synthetic NO, window 0x421, > mode NotifyGrab, detail NotifyAncestor > > FocusIn event, serial 31, synthetic NO, window 0x421, > mode NotifyUngrab, detail NotifyAncestor > > KeymapNotify event, serial 31, synthetic NO, window 0x0, > keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > Kind of strange: seems like the behavior of a mouse... > Can you interpret this result? Halestino, Try to disable any Accessibility option in control center. Regards.
