Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
evolution autocompletion locks up X
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
jle
n00b
n00b


Joined: 02 Mar 2005
Posts: 6

PostPosted: Fri Mar 04, 2005 4:42 pm    Post subject: evolution autocompletion locks up X Reply with quote

Has anyone had a problem with autocompletion in evolution (2.0.2 and up) locking up X to where you can type anything or use the mouse buttons (cursor still moves)? The only way I can get out of this is to ssh into the machine and kill evolution, after which I can continue to work. If I don't have access to another machine, I have to power cycle the machine.

I probably should leave well enough alone, but I emerge world about once a month or so. I had been running fine for the past year. Sometime in February, evolution started locking up on me. I can move the mouse but keyboard clicks and mouse clocks have no effect, except that I can use alt and arrow keys to move to a different workspace. It only happens when evolution is doing an autocomplete on the email address that I am typing in the To: field. I've tried all versions 2.0.2 and up to 2.0.4. I had 2.0.2 installed before I emerged world in mid February, which updated a lot of packages. Before than I had no problems. Also, in January, emerge world automatically updated me to Xorg. Since I believe that things worked ok with 2.0.2 and before the world emerge in mid February, but now 2.0.2 still locks up, my conclusion is that there is something else that is also partly to blame for the evolution lockup.

I could try to go back to earlier version of various packages, which ones I don't know - maybe going back to XFree86, previous versions of gnome, etc. The problem is that there are a lot of packages, and I may never hit the right combinations to isolate the problem. I'm not even sure how to get back to where I was at the beginning of January. I backup up my data, but I don't typically backup all my system files (I'll probably start doing that....)

Oh, and here is another thing. If I turn off autocompletion in the preferences, everything works fine, but it still autocompletes! I would have thought that if I turn off the autocomplete, it wouldn't even bringup up any completion choices. THe annoying thing now is that when I start up evolution after turning on the laptop, autocomplete is turned on again. How do I turn the autocompletion off so that the next time evolution starts up autocompletion is not on?

Also, and this may be better for another thread in a different forum, but since mid-February, I've been getting total lockup with blank screen just after booting and before the nvidia splash screen comes up (did I mention I was using nvidia?). When I look at /var/log/messages, the messages stops with

Quote:

agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode


THen the next thing I see is where the system starts to boot up again after I power cycle it. Could there be any connection to this problem starting up at the same time as the autocompletion freeze problem showing up?

I've done a search on the web and on these forums. There is some stuff about autocompletion being broken in version 1.something, but that is more than a year old. I've tried several attempts at searching the evolution bug reports, but I turned up nothing having to do with autocompletion (I can't claim that I did the searches properly).


Here are the versions of various packages:

Xorg : 6.8.0-r4
gnome : 2.4.0
evolution : tried 2.0.2 to 2.0.4
glibc: 2.3.4.20040808-r1
glib : 2.4.8
kernel : gentoo-dev-sources-2.6.10-r6
nvidia-kernel : 1.0.6629-r1
nvidia-glx : 1.0.6629-r1

Here is my xorg.conf:

Code:

# $XdotOrg: xc/programs/Xserver/hw/xfree86/xorgconf.cpp,v 1.2 2004/04/23 19:20:02 eich Exp $
#
# Copyright (c) 1994-1998 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# $XConsortium: XF86Conf.cpp /main/22 1996/10/23 11:43:51 kaleb $

# **********************************************************************
# This is a sample configuration file only, intended to illustrate
# what a config file might look like.  Refer to the XF86Config(4/5)
# man page for details about the format of this file. This man page
# is installed as /usr/share/man/man5/xorg.conf.5x
# **********************************************************************

# The ordering of sections is not important in version 4.0 and later.

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath   "/usr/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

    # For XFS, uncomment this and comment the others
    # FontPath   "unix/:-1"
    FontPath   "/usr/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/Type1/"
    FontPath    "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

#    ModulePath   "/usr/lib/modules"

EndSection

# **********************************************************************
# Module section -- this is an optional section which is used to specify
# which run-time loadable modules to load when the X server starts up.
# **********************************************************************

Section "Module"

# This loads the DBE extension module.

    Load   "dbe"
    Load   "glx"

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.

    Load        "extmod"
#    SubSection   "extmod"
#   Option   "omit xfree86-dga"
#    EndSubSection

# This loads the Type1 and FreeType font modules

    Load   "type1"
    Load   "freetype"

EndSection


# **********************************************************************
# Server flags section.  This contains various server-wide Options.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option   "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option   "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option   "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option   "DontZoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option   "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option   "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option   "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option   "AllowNonLocalModInDev"

# Set the basic blanking screen saver timeout.

#    Option   "blank time"   "10"   # 10 minutes

# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

#    Option   "standby time"   "20"
#    Option   "suspend time"   "30"
#    Option   "off time"   "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option   "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier   "Keyboard1"
    Driver   "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris), comment
# out the above line, and uncomment the following line.

#    Option   "Protocol"   "Xqueue"

# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.

    Option   "AutoRepeat"   "250 3"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

#    Option   "Xleds"   "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    Option   "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option   "XkbModel"   "pc102"
#    Option   "XkbModel"   "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option   "XkbModel"   "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option   "XkbModel"   "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
#    Option   "XkbLayout"   "de"
#
# or:
#
#    Option   "XkbLayout"   "de"
#    Option   "XkbVariant"   "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
#    Option   "XkbOptions"   "ctrl:swapcaps"


# These are the default XKB settings for xorg
#

#    Option   "XkbModel"   "pc101"
#    Option   "XkbLayout"   "us"
    Option   "XkbModel"   "pc104"
    Option   "XkbLayout"   "us"
#    Option   "XkbVariant"   ""
#    Option   "XkbOptions"   ""

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier  "Mouse1"
    Driver      "mouse"
    Option      "Protocol"    "PS/2"
    Option      "Device"      "/dev/psaux"
    Option      "Emulate3Buttons" "yes"
EndSection


Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
   Identifier  "DevInputMice"
   Driver      "mouse"
   Option       "Protocol" "IMPS/2"
   Option       "Device" "/dev/input/mice"
   Option       "ZAxisMapping" "4 5"
   Option       "Emulate3Buttons" "yes"
EndSection

Section "InputDevice"
   Identifier   "Synaptics"
   Driver      "synaptics"
   Option      "Protocol" "/dev/psaux"
   Option      "Device" "/dev/input/mice"
   Option      "TapButton1" "0"
   Option      "TapButton2" "0"
   Option      "TapButton3" "0"
   Option      "SHMConfig" "on"
EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"


    Identifier "MyMonitor"
    VendorName "Dell"
    ModelName  "UXGA LCD"

    # be sure to replace these values with values appropriate for your
    # monitor!
    HorizSync    31.5 - 90.0
    VertRefresh  59.0 - 85.0


EndSection

# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"

    Identifier  "NV AGP"
    VendorName  "nvidia"
    Driver   "nvidia"
    # update this with the PCI id of your card.  Consult the output
    # of the 'lspci' command.  The BusID is usually optional when
    # only using one graphics card.
    BusID       "PCI:1:0:0"

EndSection



# **********************************************************************
# Screen sections.
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.

Section "Screen"
    Identifier "Screen AGP"
    Device      "NV AGP"
    Monitor     "MyMonitor"
    DefaultColorDepth 24
    Subsection "Display"
        Depth       24
        Modes       "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
    EndSubsection

EndSection



# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"
    Identifier  "AGP"
    Screen      "Screen AGP"
#    InputDevice "Mouse1" "CorePointer"
    InputDevice "Synaptics" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
    InputDevice "DevInputMice" "AlwaysCore"
EndSection



Since I have a workaround, I'm not too desparate, but it is annoying. And it has been a big time kill, and I'm not sure if I learned much from this.... If anyone sees anything simple that I could try, I'd appreciate any recommendations.

John
Back to top
View user's profile Send private message
jle
n00b
n00b


Joined: 02 Mar 2005
Posts: 6

PostPosted: Sun Mar 06, 2005 7:31 pm    Post subject: Workaround found.... Reply with quote

Well, I guess no one else has had this problem, but in case anyone does, here is a workaround for me. I found that alt-tab still works. When I cycle through the windows, it will come back to the message compose window and the focus is back and everything works fine from that point on - until you hang up the next time evolution tries to do an autocomplete. So, what is happening is that the focus has gone somewhere and moving my mouse, mous clicks, or key presses do not bring back the focus, except for the alt-tab keys. Anyway, hope this helps the next person that sees the same problem.

After having emerged/unmerged countless number of things, I think I finally have figured out that it has something to do with the combination of sawfish and evolution. There is something else affecting this since sawfish version hasn't changed in a long while and everything was working fine until mid February when I did an emerge world. When I tried another window manager (fvwm), it didn't hang (let's not get into a debate about which window manager is the best).

Since I have no other answers, I guess I'll either live with this workaround, or if I'm desparately looking to avoid doing real work, I'll reinstall from scratch when I have a couple of days to kill to see if that gets rid of the problem altogether.

John
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum