You are not logged in.
Ever since upgrading and installing the following packages (see below), I've been experiencing unusual behavior when using 'tabs' in Firefox & Pidgin, which NEVER occurred prior to the upgrade.
Issue:
1) In Firefox, if there are several tabs with websites opened, clicking on one of them will sometimes close it (the "tab", not the program) completely.
2) In Firefox, when clicking on the 'Go Back One Page' arrow (<=) OR 'Reload Current Page', another tab will randomly pop up, containing the same web site as the current tab while performing this operation.
3) In Firefox, simply going to certain websites invokes a pop up tab containing the same web site info.
4) In Pidgin, similar issue as in (1). If there are several tabs opened with different channels, clicking on one of them will sometimes close it (the "tab") completely.
All of the above are random occurrences happening very often.
It's difficult to pinpoint which package upgrade is the culprit as quite a few have been upgraded. For sure, these unusual events began to occur after the following upgrade:
----------------------------------------------------------
[2010-09-28 20:36] Running 'pacman -Syu'
[2010-09-28 20:36] synchronizing package lists
[2010-09-28 20:36] starting full system upgrade
[2010-09-28 20:40] upgraded nss (3.12.7-1 -> 3.12.8-1)
[2010-09-28 20:40] upgraded xulrunner (1.9.2.10-1 -> 1.9.2.10-2)
[2010-09-29 11:33] Running 'pacman -Syu'
[2010-09-29 11:33] synchronizing package lists
[2010-09-29 11:33] starting full system upgrade
[2010-09-29 11:41] upgraded cairo (1.8.10-1 -> 1.10.0-2)
[2010-09-29 11:41] upgraded libgl (7.8.2-1 -> 7.8.2-3)
[2010-09-29 11:41] upgraded intel-dri (7.8.2-1 -> 7.8.2-3)
[2010-09-29 11:42] upgraded k3b (2.0.1-2 -> 2.0.1-3)
[2010-09-29 11:42] upgraded mesa (7.8.2-1 -> 7.8.2-3)
[2010-09-29 11:42] upgraded qt (4.6.3-1 -> 4.7.0-2)
[2010-09-29 11:42] upgraded xf86-input-evdev (2.4.0-2 -> 2.5.0-1)
[2010-09-29 11:42] upgraded xf86-input-joystick (1.5.0-2 -> 1.5.0-3)
[2010-09-29 11:42] upgraded xf86-input-keyboard (1.4.0-2 -> 1.4.0-3)
[2010-09-29 11:42] upgraded xf86-input-synaptics (1.2.2-2 -> 1.3.0-1)
[2010-09-29 11:42] upgraded xf86-video-fbdev (0.4.2-1 -> 0.4.2-2)
[2010-09-29 11:42] upgraded xf86-video-intel (2.12.0-1 -> 2.12.0-3)
[2010-09-29 11:42] upgraded xf86-video-vesa (2.3.0-2 -> 2.3.0-3)
[2010-09-29 11:42] upgraded xkeyboard-config (1.8-1 -> 1.9-1)
[2010-09-29 11:42] installed xorg-server-common (1.9.0-1)
[2010-09-29 11:42] upgraded xorg-server (1.8.1.902-1 -> 1.9.0-1)
----------------------------------------------------------
Using KDE 4.5.1 on a x86_64 Genuine Intel(R) CPU 575 @ 2.00GHz GenuineIntel GNU/Linux laptop. Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (Intel GM45 Chipset).
Anyone else experiencing something similar after these package upgrades? Thanks.
Last edited by ejmarkow (2011-05-11 02:03:32)
Offline
You can try downgrading e.g. xulrunner to see if it helps with your firefox problems.
Offline
@karol: The package "xulrunner" most likely isn't the conflicting one as this bug is affecting a common component (tabs) in two programs (FireFox & Pidgin). My guess would be either 'xorg-server, qt, or xf86-input-synaptics'. I already removed all unused packages from my cache by using "pacman -Sc". Thanks for the suggestion.
Last edited by ejmarkow (2010-10-01 13:00:48)
Offline
Firefox uses gtk on my system, not qt ;P IIRC Pidgin uses it too. But gtk2 hasn't changed for months. <shrugs>
Offline
Firefox uses gtk on my system, not qt ;P IIRC Pidgin uses it too. But gtk2 hasn't changed for months.
Firefox and Pidgin both use gtk on mine as well, but they must function within the QT framework (KDE). This is why I mentioned QT as a possible culprit. I've been thinking along the same lines as you with Gtk2. Perhaps these latest package upgrades somehow slightly broke Gtk2? I'm not sure, only bouncing ideas around.
Last edited by ejmarkow (2010-10-01 13:05:49)
Offline
That's why I suggested downgrading a package here and there to see what makes you system tick. Just don't break it more than it is now ;P
When your firefox and pidgin crash, are there any error messages? Check the xorg log too.
Offline
When your firefox and pidgin crash, are there any error messages? Check the xorg log too.
Firefox & Pidgin aren't actually crashing, just behaving very abnormally when it comes to using the "tabs" in both programs. The most common issue is when using my touchpad to point & click on a given tab, and very often, it completely closes instead of displaying the current website (in FF) or channel (in Pidgin). Also, as I said in my original message, when clicking on 'Go Back One Page' (back arrow button) OR 'Reload Current Page' in FF, this for some reason invokes opening another tab with the same website on it. So, again, it all has to do with the behavior of the "tabs" in both pieces of software.
All of this never happened prior to the package upgrades listed.
Last edited by ejmarkow (2010-10-01 13:47:24)
Offline
Ah, sorry, I thought "close completely" = unexpected crash.
Offline
Here's a possibility, could the latest synaptics upgrade be the issue when it comes to pointing and clicking on "tabs"?
[2010-09-29 11:42] upgraded xf86-input-synaptics (1.2.2-2 -> 1.3.0-1)
Keep in mind, my synaptics touchpad seems to be working fine at the moment. However, look at a fragment of my current Xorg.log, there are several errors (EE):
------------------
[ 35.524] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6)
[ 35.524] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 35.524] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 35.524] (II) LoadModule: "synaptics"
[ 35.524] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 35.526] (II) Module synaptics: vendor="X.Org Foundation"
[ 35.526] compiled for 1.9.0, module version = 1.3.0
[ 35.526] Module class: X.Org XInput Driver
[ 35.526] ABI class: X.Org XInput driver, version 11.0
[ 35.526] (II) Synaptics touchpad driver version 1.3.0
[ 35.526] (**) Option "Device" "/dev/input/event6"
[ 35.526] (--) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5592
[ 35.526] (--) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4916
[ 35.526] (--) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 35.526] (--) SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 35.526] (--) SynPS/2 Synaptics TouchPad: buttons: left right
[ 35.527] (**) Option "TapButton1" "1"
[ 35.527] (**) Option "TapButton2" "2"
[ 35.527] (**) Option "TapButton3" "3"
[ 35.527] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 35.527] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 35.527] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
[ 35.527] (**) SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 35.527] (**) SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[ 35.527] (**) SynPS/2 Synaptics TouchPad: AccelFactor is now 0.037
[ 35.527] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 35.527] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 35.527] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 35.527] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 35.527] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 35.527] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 35.527] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 35.527] (II) Synaptics touchpad driver version 1.3.0
[ 35.527] (EE) SynPS/2 Synaptics TouchPad no synaptics event device found
[ 35.527] (**) Option "Device" "/dev/input/mouse0"
[ 35.527] (--) SynPS/2 Synaptics TouchPad: invalid x-axis range. defaulting to 1615 - 5685
[ 35.528] (--) SynPS/2 Synaptics TouchPad: invalid y-axis range. defaulting to 1729 - 4171
[ 35.528] (--) SynPS/2 Synaptics TouchPad: invalid pressure range. defaulting to 0 - 256
[ 35.528] (--) SynPS/2 Synaptics TouchPad: invalid finger width range. defaulting to 0 - 16
[ 35.528] (**) Option "TapButton1" "1"
[ 35.528] (**) Option "TapButton2" "2"
[ 35.528] (**) Option "TapButton3" "3"
[ 35.548] (EE) Query no Synaptics: 6003C8
[ 35.548] (--) SynPS/2 Synaptics TouchPad: no supported touchpad found
[ 35.548] (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
[ 35.548] (EE) PreInit failed for input device "SynPS/2 Synaptics TouchPad"
[ 35.548] (II) UnloadModule: "synaptics"
------------------
Note: I do not use a xorg.conf file in /etc/X11. Everthing is configured automatically, as has been the case prior to these latest upgrades.
Last edited by ejmarkow (2010-10-04 10:37:13)
Offline
That's what I was asking about: are there any error messages :-)
I don't think it's related though. Are those messages gone if you downgrade?
Please, use [ code ] tags for pasting code.
Last edited by karol (2010-10-01 14:14:53)
Offline
Just to chime in, I'd check out with xev whether there are 'ghosts' clicks (perhaps of the middle mouse or right-mouse button).
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Note: I do not use a xorg.conf file in /etc/X11. Everthing is configured automatically, as has been the case prior to these latest upgrades.
I think you'll find the config files in /etc/X11/xorg.conf.d/*.conf.
Offline
have you tried with a new profile to confirm this behaviour?
Offline
@karol: As I said before, I no longer have the previous package in cache, it's gone so I can't downgrade for now. In /etc/X11/xorg.conf.d/, I temporarily renamed 10-synaptics.conf and rebooted just to test out my touchpad - it still works with the same issues.
@ngoonee: I'll have to test for ghost clicks. This was never an issue prior to the recent upgrades. Besides, there is still the problem with new tabs appearing in FF when 'refreshing' or 'going back one page' (those are unrelated to a mouse / touchpad). I still think a package(s) upgrade changed this.
@kgas: See my comment to karol. I deleted the conf file and rebooted. The same issues remain.
Offline
Try editing /etc/X11/xorg.conf.d/10-evdev.conf and commenting out the evdev touchpad catchall section and then restoring your 10-synaptics.conf
Offline
Old packages should be here http://arm.konnichi.com/search/
Edit: Just renaming it doesn't necessarily fix it - if you move it out of that folder, that's a sure way.
Last edited by karol (2010-10-01 15:44:47)
Offline
Dunno if it helps, but since no-one mentionned it... it looks like those problematic left mouse button clicks behave like middle mouse button clicks. Might it be a hardware problem? (Have you tried with a mouse?)
Offline
Ok, just as I thought earlier, the conflicting upgrade packages have been identified...it's xorg-server and related xf86~ packages! For me personally, the issue is resolved by reverting back to the previous packages, however, either a fix upstream is necessary, or only the need to recompile by the Arch developers. Here is what I've done:
Reinstalled the following old, and removed the new (They all must be done together for dependency reasons):
xf86-video-intel (2.12.0-1 / 2.12.0-3)
xf86-video-vesa (2.3.0-2 / 2.3.0-3)
xf86-video-fbdev (0.4.2-1 / 0.4.2-2)
xf86-input-evdev (2.4.0-2 / 2.5.0-1)
xf86-input-joystick (1.5.0-2 / 1.5.0-3)
xf86-input-keyboard (1.4.0-2 / 1.4.0-3)
xf86-input-synaptics (1.2.2-2 / 1.3.0-1)
xorg-server (1.8.1.902-1 / 1.9.0-1)
xorg-server-common (1.9.0-1) [*Only Removed, not reinstalled]
I've been intensely testing both Firefox & Pidgin for the previously noted issues, and they no longer occur or exist. If anyone should have similar issues, you have the solution. This is something that just doesn't 'crash', but must be looked at closely. I hope others eventually find the same issue with these latest xorg packages, because it is real problem.
I would like to thank @karol for kindly providing me with a link ("konnichi") to an archive containing older packages. This came in most handy!
A bug report will be filed by me tomorrow (or sooner), for sure.
Note my Xorg.log now (less two errors):
---------------
[ 52.082] SynPS/2 Synaptics TouchPad no synaptics event device found
[ 52.082] (**) Option "Device" "/dev/input/mouse0"
[ 52.082] (**) Option "TapButton1" "1"
[ 52.082] (**) Option "TapButton2" "2"
[ 52.082] (**) Option "TapButton3" "3"
[ 52.102] Query no Synaptics: 6003C8
[ 52.102] (--) SynPS/2 Synaptics TouchPad: no supported touchpad found
[ 52.102] (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
[ 52.102] (EE) PreInit failed for input device "SynPS/2 Synaptics TouchPad"
[ 52.102] (II) UnloadModule: "synaptics"
---------------
Last edited by ejmarkow (2010-10-04 10:38:10)
Offline
Glad you got it working.
As you've probably noticed, there are many threads regarding the shiny new xorg 1.9 ;P
That server with some older packages is not really a secret http://wiki.archlinux.org/index.php/Dow … ckages#ARM :-)
Offline
@karol: Thanks again for suggesting to downgrade and test the older packages! This is exactly what I've done and was able to pinpoint the conflicting packages. Note that no adjustments to any config files were necessary, only a downgrade to the older xorg packages and that resolved it all.
This thread won't be marked "SOLVED" because the xorg packages still need to be fixed.
Last edited by ejmarkow (2010-10-01 21:03:52)
Offline
@karol: Thanks again for suggesting to downgrade and test the older packages! This is exactly what I've done and was able to pinpoint the culprit packages. Note that no adjustments to any config files were necessary, only a downgrade to the older xorg packages and that resolved it all.
This thread won't be marked "SOLVED" because the xorg packages still need to be fixed.
I suggest you create a script to up/downgrade the needed packages and take care of dependencies. You can check once in a while if the new xorg got fixed or is it still not working for you.
You may want to open a bug report or two.
Offline
A bug report will be filed by me tomorrow (or sooner), for sure.
Already previously mentioned.
Offline
ejmarkow wrote:A bug report will be filed by me tomorrow (or sooner), for sure.
Already previously mentioned.
I'm terribly sorry. I do have issues with my eyes, but recently it seems I've turned into a mole.
Ah, old age.
Offline
Bug Report has been filed: https://bugs.archlinux.org/task/21024
Offline
Performed the following upgrade today:
xf86-input-evdev: (2.4.0-2 => 2.5.0-1)
xf86-input-joystick: (1.5.0-2 => 1.5.0-3)
xf86-input-keyboard: (1.4.0-2 => 1.4.0-3)
xf86-input-synaptics: (1.2.2-2 => 1.3.0-1)
xf86-video-fbdev: (0.4.2-1 => 0.4.2-2)
xf86-video-intel: (2.12.0-1 => 2.12.0-3)
xf86-video-vesa: (2.3.0-2 => 2.3.0-3)
xorg-server-common: 1.9.2-1
xorg-server: (1.8.1.902-1 => 1.9.2-1)
The mentioned issue still persists. I want to add, cursor movement is slightly choppy and lagging, this holds true for original issue reported as well. Downgraded once again (same downgrade) and problem goes away. Bug report remains with this additional info.
Last edited by ejmarkow (2010-11-04 09:55:45)
Offline