Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JWM crashes Xorg server at first attempt using Move menu item #410

Closed
willbprog127 opened this issue Sep 12, 2017 · 3 comments
Closed

JWM crashes Xorg server at first attempt using Move menu item #410

willbprog127 opened this issue Sep 12, 2017 · 3 comments
Labels

Comments

@willbprog127
Copy link

willbprog127 commented Sep 12, 2017

Here's an interesting one for you...

Using example.jwmrc and the latest git version (d664eba), JWM crashes Xorg to the virtual terminal with the following steps:

  • Start X and JWM
  • Click on JWM's root window / desktop to bring up JWM's menu
  • Choose 'Terminal' (Xterm must be installed)
  • When terminal window comes up, do NOT move or resize it with the mouse
  • Right-click the terminal's title bar and choose 'Move'
  • The small move coordinates pop-up shows briefly then...
  • Xorg will crash to the terminal

This happens right after Xorg and JWM starts. I've tried it after using JWM for a while and it works properly, so it's something to do with maybe garbage initial values or something.

I will build with Debug enabled and see if I get any other output beyond Xorg's typical stuff.

Thanks! 😄

ℹ️ Gentoo Linux 64-bit * Xorg 1.19.3 * AMD Radeon HD 6670 * 16 GB RAM

@willbprog127
Copy link
Author

willbprog127 commented Sep 12, 2017

Here is the debug output when the crash happens:

Program received signal SIGSEGV, Segmentation fault.
UpdateDesktop (now=0x7fffffffd700) at move.c:847
847        currentClient->state.status |= STAT_HIDDEN;

joewing added a commit that referenced this issue Sep 30, 2017
…-window

Fix crashes Xorg server at first attempt using Move menu item (#410)
@joewing joewing added the bug label Sep 30, 2017
@joewing
Copy link
Owner

joewing commented Sep 30, 2017

This should be fixed as of snapshot 1645 (thanks @rdnvndr!)

@willbprog127
Copy link
Author

@rdnvndr @joewing Thank you so much! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants