Description of problem: For kernel 3.4.24-netbook-2.mga2 on my laptop called Toshiba Satellite L755-1DR, I know that I'm NOT using any special kind of GTK-theme & I'm not using any Backports-medias. If I have the original settings in Pidgin & I use the protocols Facebook, Google Talk, MSN, XMPP and Yahoo I can't see any output when I've typed on my keyboard. It's as if they are hidden or as if the keyboard just stops working when I type in Pidgin. Otherwise it works perfectly fine. Version-Release number of selected component (if applicable): 2.10.6 How reproducible: Now and then. Steps to Reproduce: 1. Install Pidgin 2.10.6. 2. Run Pidgin. 3. Add all the above mentioned protocols. 4. Connect to them. 5. Open any chat-window.
CC: (none) => kristoffer.grundstrom1983
Created attachment 3280 [details] LSHW-output
Created attachment 3281 [details] LSMOD-output
Created attachment 3282 [details] LSPCIDRAKE-output
Created attachment 3283 [details] Error-output from Pidgin's menu
I'm using Gnome.
Created attachment 3284 [details] Login-output from Terminal.
This only happens if you have all the protocols added & enabled. I have tested the issue on each and everyone of them.
(In reply to comment #7) > This only happens if you have all the protocols added & enabled. > > I have tested the issue on each and everyone of them. My bad. I see this issue now when I only use Jabber-protocol.
can't reproduce (gnome too)
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
(In reply to comment #9) > can't reproduce (gnome too) (In reply to comment #4) > Created attachment 3283 [details] > Error-output from Pidgin's menu If it's NOT a hardware-issue since it works perfectly fine otherwise where the fudge is the real cause??
Hi Damien (looks like you're maintaining all the packages that have bug reports :)), I let you see what you can do with this bug report.
Keywords: (none) => TriagedStatus: UNCONFIRMED => NEWCC: (none) => stormiAssignee: bugsquad => mageiaEver confirmed: 0 => 1
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD