** Changed in: gsynaptics (Ubuntu)
Assignee: hainz (beloysov) = Sohrab Bharucha (sohrab)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/132627
Title:
GSynaptics couldn't initialize.
To manage
Get the following error... set 'SHMConfig' 'true' in xorg.conf or XF86Config
to use GSynaptics when opening Touchpad. How do I apply this fix? I have no
idea; only know how to install deb packages and do not know how to use terminal.
My e-mail is: joh...@inetmatrix.com
--
GSynaptics
Gsynaptics were specifically for synaptics based touchpads, IIRC. Can
you please try and install gpointing-device-settings with your universe
repositories enabled.
gpointing-device-settings |1.3.1-2 | karmic/universe | source, amd64, i386
gpointing-device-settings |1.3.2-2 |
I have just installed this on 3 separate devices, and all 3 were
successful and working, One Alps touchpad, and 2 SynPS/2 Synaptic
Touchpads.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm having this issue on a new gateway on ubuntu 10.04
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I still have this issue on 10.4
Dell Inspiron 11z (Elantech touch pad)
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
machine: xubuntu 9.10, Dell Inspiron 11z
My touchpad works, but I try to delay or disable tap while I type.
I had no entry for touch in xorg. I added 2 sections and included the
SHMConfig line and also added /etc/hal/fdi/policy/shmconfig.fdi but it
didn't help - GSynaptics, touchfreeze and
** Changed in: gsynaptics (Ubuntu)
Assignee: (unassigned) = hainz (beloysov)
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
No answer received, closing as Fix Released
** Changed in: gsynaptics (Ubuntu)
Status: Confirmed = Fix Released
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Also no problems in Karmic...
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It doesn't work in Netbook Remix Hardy, on a Sylvania Meso G.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
rick,
Please attache the out put of the following comands:
cd /var/lib/acpi-support/; grep '.' *-* ~/laptop
uname -a ~/uname-a
cat /proc/version_signature ~/version_signature
sudo lspci -vvnn ~/lspci-vvnn
Thanks for your time,
Chris
--
GSynaptics couldn't initialize.
It works in Jaunty.
https://help.ubuntu.com/community/SynapticsTouchpad#shmconfig
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Fixed in Jaunty adding
Option SHMConfig true
as the last line of Section InputDevice
Section InputDevice
Identifier Synaptics Touchpad
Driver synaptics
Option SendCoreEvents true
Option Device /dev/psaux
Option
Hi all, I have this bug too on a Japanese computer: NEC LL550/H .
I also had the mad touchpad bug (move and clicks alone) which can be solved
by adding i8042.nomux=1 in the /boot/grub/menul.lst
Regards
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this
SOME ONE, FIX THIS BUG! This mouse pad is evil Fix the bug
so I can disable the evil double tap feature!!! ITS
EIIL EVIL
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a
Well with a confirmed status it is definitely going to be addressed! :-)
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Mr. UNOwen,
I see that someone has already marked this as confirmed, I second the motion.
On the EEE 701 I was able to fix it the way that I suggested to you, But on a
1000 eee I could not get it to work. I couldn't get it to work on a eee 900
either.
I will look into the other bug that you
So will this bug be fixed
Thanks
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Mr. UNOwen,
Tomorrow I will get my hands on a Triple E 1000h. I will report back to
you what I am able to find. On three separate dell devices, I have
followed: https://help.ubuntu.com/community/SynapticsTouchpad#shmconfig
This corrected it on all three. Unfortunately the EEE 1000h is not mine,
Thanks a lot!
Also while you still have your hands on a 1000h can you check out the bug
below...
https://bugs.launchpad.net/ubuntu/+bug/314190
Also FYI, I have the ha model and not the h model... don't know if
it'll impact anything, but I'm just letting you know...
Also if you have the time,
I have the same problem on my eee pc 1000ha, but that didn't work. So
far none of the solutions worked
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thanks Endolith, I was having the same issue In Intrepid on my Dell XPS
1730. Worked like a charm adding: /etc/hal/fdi/policy/shmconfig.fdi
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which
if you used another computer to install your os on an external hard drive, or
changed any physical components of your computer, and you are having a hard
time with your SMHconfig, or touch pad.
use this command in terminal, it worked great for me
sudo dpkg-reconfigure -phigh xserver-xorg
and
Same issue for me when I upgraded my netbook to intrepid but following
the instructions in the link by Endolith did not work for me.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Mine is a Dell Inspiron 8600. Gsynaptics stopped working after
upgrading to Intrepid, and works again since following the shmconfig.fdi
instructions.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Got it working following these instructions:
https://help.ubuntu.com/community/SynapticsTouchpad#shmconfig
This should be made automatic.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which
Confirmed that adding SHMConfig back into xorg.conf does not fix the
problem, despite the dialog box.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Adding options psmouse elantech=1 to /etc/modprobe.d/options doesn't
work, either. Mouse is unresponsive and Touchpad settings still won't
open.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs,
For those still having the problem: try something:
In Terminal, type synclient TouchPadOff=1
If you're told, Can't access shared memory area. SHMConfig disabled?,
then I just got through the same problem (on my EEE 1000H running Ubuntu
8.04 hardy). I located a way to get it working:
additionally:
The alert in intrepid still refers to xorg.conf which isn't used anymore. So
before this bug is fixed, it would be useful if the alert refers to the hal
configuration and not the xorg.conf file.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You
Are you sure that SHMConfig setting is being applied? In recent Xservers
using just section InputDevice is not enough, you have to link it from
ServerLayout. Something like this (taken from gsynaptics README.Debian):
Section InputDevice
Identifier Synaptics Touchpad
Driver synaptics
Bug still present in Intrepid Ibex Beta. After installation of
GSynaptics and setting SHMConfig true in /etc/X11/xorg.conf, same
error message as above is still displayed.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are
I am also facing the same problem. After proper installation of GSynaptics i
am getting the error
GSynaptics couldn't initialize.
You have to set 'SHMConfig' 'true' in xorg.conf or XF86Config to use GSynaptics
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You
But what to do if I do not have this touchpad section in my xorg.conf?
I have installed my Ubuntu while no touchad was connected so it was
generated without it!
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member
I have added the section with no luck. I got the message even when I
logout my session.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/15693370/xorg.conf
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are
, 05 May 2008 03:28:58 -
Subject: [Bug 132627] Re: GSynaptics couldn't initialize.
Something has changed in the LTS Hardy. Sometimes I get thenott
old message: GSynaptics couldn't initialize. You have to set
'SHMConfig' 'true' in xorg.conf or XF86Config to use GSynaptics
Other times I
Something has changed in the LTS Hardy. Sometimes I get thenott old message:
GSynaptics couldn't initialize.
You have to set 'SHMConfig' 'true' in xorg.conf or XF86Config to use GSynaptics
Other times I get a warning that synclient is being used and I get a window with
three tabs. The first is
Confirm that this still doesn't work in the Hardy final.
As this is bugging everybody over a year I think that it's time to get this
fixed.
After all it's just a line of code that needs to be added to xorg.conf
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You
I'm also bitten by this bug. Is there any workaround?
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
confirm that this still doesnt work in the hardy beta. Same error
message was recieved. Have been trying to enable vertical scrolling
since Gutsy but no luck.
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member
** Changed in: gsynaptics (Ubuntu)
Status: New = Confirmed
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Confirm that this occurred in Gutsy and still occurs in Alpha 6.
Also, there is a discrepancy between the gsynaptics error message,
which asks if SHMConfig is set to true while the help.ubuntu.com
directions on synaptics prescribes that it be set to on. Either
way gsynaptics cannot initialize.
I
Still occurs in Hardy Alpha 6 with this error message: GSynaptics couldn't
initialize.
You have to set 'SHMConfig' 'true' in xorg.conf or XF86Config to use
GSynaptics.
Screenshot attached.
** Attachment added: gsynaptics.png
http://launchpadlibrarian.net/12497743/gsynaptics.png
--
Attaching my xorg.conf
** Attachment added: xorg.conf
http://launchpadlibrarian.net/10528656/xorg.conf
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
This issue is occurring in gutsy as well. I am attaching my Xorg.0.log
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/10528652/Xorg.0.log
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a member of
Durmant,
If you are still having this problem would you please attach your
xorg.conf and Xorg.0.log?
Seiti,
xorg.conf should exist in /etc/X11
Search for a section that looks like this (or add it if it doesn't exist):
Section InputDevice
Identifier Synaptics Touchpad
Silly question, but: where is the xorg.conf file? I had to remove it
from /etc/X11/ after last update to make X start and run. So where do I
set SHMConfig to true?
--
GSynaptics couldn't initialize.
https://bugs.launchpad.net/bugs/132627
You received this bug notification because you are a
48 matches
Mail list logo
