Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Emacs segfault with libX11 update

  1. #1

    Default Emacs segfault with libX11 update

    The update of libX11 from 1.6.5-lp151.3.3-x86_64 to 1.6.5-lp151.4.3.1-x86_64 causes emacs using X11 windowing to segfault. emacs -nw functions without problems. It's unclear whether this is a problem with upstream (emacs or X11) or with the build details.

    Two workarounds: use "-nw" to disable window use, and run emacs in terminal mode
    revert libX11 back to 151.3.3.

  2. #2
    Join Date
    Sep 2012
    Posts
    5,853

    Default Re: Emacs segfault with libX11 update

    Quote Originally Posted by rjhorniii View Post
    Two workarounds: use "-nw" to disable window use, and run emacs in terminal mode
    revert libX11 back to 151.3.3.
    You need to submit bug report on https://bugzilla.opensuse.org

  3. #3

    Cool Re: Emacs segfault with libX11 update

    Quote Originally Posted by rjhorniii View Post
    The update of libX11 from 1.6.5-lp151.3.3-x86_64 to 1.6.5-lp151.4.3.1-x86_64 causes emacs using X11 windowing to segfault. emacs -nw functions without problems. It's unclear whether this is a problem with upstream (emacs or X11) or with the build details.

    Two workarounds: use "-nw" to disable window use, and run emacs in terminal mode
    revert libX11 back to 151.3.3.
    I experience the same problem here. On start-up, emacs segfaults. I noticed, however, the following:
    1. emacs does work when I start it as root.
    2. emacs does work if I start it using another user account (on the same laptop).

    I tried the following, but to no avail:
    1. I removed the .emacs and .emacs.d configuration files.
    2. I removed .Xauthority
    3. I emptied the ~/.cache directory.

    No succes, though. I have no idea whre to look further.

    Another observation, which may or may not have anything to do with it. When I booted into KDE after the update, the desktop settings (icons, background) were just gone!

    Any suggestions?

    Regards
    Bertwim

  4. #4
    Join Date
    Sep 2012
    Posts
    5,853

    Default Re: Emacs segfault with libX11 update

    Quote Originally Posted by bwvb View Post
    Any suggestions?
    What was not clear in "you need to submit bug report"?

  5. #5

    Default Re: Emacs segfault with libX11 update

    Quote Originally Posted by arvidjaar View Post
    What was not clear in "you need to submit bug report"?
    With the additional info, others can have suggestions, ideas, etc. Just saying "file a bug" is too simple an answer for a problem that is so fresh.

    I feel that if one cannot contribute, it is good practice to keep silent.

    Cheers!

  6. #6

    Default Re: Emacs segfault with libX11 update

    Quote Originally Posted by rjhorniii View Post
    The update of libX11 from 1.6.5-lp151.3.3-x86_64 to 1.6.5-lp151.4.3.1-x86_64 causes emacs using X11 windowing to segfault. emacs -nw functions without problems. It's unclear whether this is a problem with upstream (emacs or X11) or with the build details.

    Two workarounds: use "-nw" to disable window use, and run emacs in terminal mode
    revert libX11 back to 151.3.3.

    I had the same issue with emacs-26.3-lp152.327.38.x86_64. I reverted libX to 1.6.5-lp152.4.5 and everything works fine.


    Code:
     emacs 
    Fatal error 11: Segmentation fault
    Backtrace:
    /usr/bin/emacs[0x51323b]
    /usr/bin/emacs[0x4f93a7]
    /usr/bin/emacs[0x51179e]
    /usr/bin/emacs[0x5119b8]
    /usr/bin/emacs[0x511a2c]
    /lib64/libpthread.so.0(+0x132d0)[0x7fe6f4f172d0]
    /usr/bin/emacs[0x4dbe9a]
    /usr/bin/emacs[0x4dc277]
    /usr/bin/emacs[0x4dcec4]
    /usr/bin/emacs[0x570876]
    /usr/bin/emacs[0x56f820]
    /usr/bin/emacs[0x5aa150]
    /usr/bin/emacs[0x571f43]
    /usr/bin/emacs[0x56f79b]
    /usr/bin/emacs[0x5aa150]
    /usr/bin/emacs[0x571f43]
    /usr/bin/emacs[0x56f79b]
    /usr/bin/emacs[0x571502]
    /usr/bin/emacs[0x5707b5]
    /usr/bin/emacs[0x56f820]
    /usr/bin/emacs[0x5aa150]
    /usr/bin/emacs[0x571f43]
    /usr/bin/emacs[0x56f79b]
    /usr/bin/emacs[0x5aa150]
    /usr/bin/emacs[0x571f43]
    /usr/bin/emacs[0x56f79b]
    /usr/bin/emacs[0x5aa150]
    /usr/bin/emacs[0x571f43]
    /usr/bin/emacs[0x56f79b]
    /usr/bin/emacs[0x5aa150]
    /usr/bin/emacs[0x571f43]
    /usr/bin/emacs[0x56f79b]
    /usr/bin/emacs[0x5aa150]
    /usr/bin/emacs[0x571f43]
    /usr/bin/emacs[0x5723a3]
    /usr/bin/emacs[0x57188a]
    /usr/bin/emacs[0x5738fb]
    /usr/bin/emacs[0x4f97a2]
    /usr/bin/emacs[0x56e9de]
    /usr/bin/emacs[0x4fa5bc]
    /usr/bin/emacs[0x56e94d]
    ...
    Segmentation fault (core dumped)

  7. #7

    Default Re: Emacs segfault with libX11 update

    [QUOTE=mikesol;2953972]I had the same issue with emacs-26.3-lp152.327.38.x86_64. I reverted libX to 1.6.5-lp152.4.5 and everything works fine.


    Thanks. I did the same and it works again.

    Regards
    Bw

  8. #8

    Default Re: Emacs segfault with libX11 update

    A quick workaround is the start via ssh X11 forwarding:

    >ssh -X localhost emacs

  9. #9

    Default Re: Emacs segfault with libX11 update

    I have the same problem, and emacs is absolutely vital for me.
    Reverting the X11 update worked, but this was supposedly a security update. What am I risking by not doing it?

    I tried to submit a bug report but couldn't figure out how to.

  10. #10
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    14,271
    Blog Entries
    3

    Default Re: Emacs segfault with libX11 update

    It seems to have already been reported as Bug 1175028.
    openSUSE Leap 15.2; KDE Plasma 5.18.5;

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •