[Linux] Crash on v1.0.25+
complete
J Sherwani (Pop Team)
Please try the snap/deb/rpm to see if one of them works. We are investigating this.
Log In
J Sherwani (Pop Team)
complete
Great! I’m marking this complete, but if anyone has any issues, please post them here and we can re-open.
J Sherwani (Pop Team)
We just released a fix (v1.0.43) — please try it out and report back!
E
Eric Christeson
J Sherwani (Pop Team): This release doesn't crash! Thanks for your diligent work on this bug and pushing out a fix so quickly after the cause was narrowed down.
J
Jordan Robinson
J Sherwani (Pop Team): Works great! Thanks for all your hard work on this one!
J Sherwani (Pop Team)
Thanks for the detailed feedback everyone! Thanks to your sleuthing, we’re now able to reproduce the bug and should hopefully have a fix out within a few days’ time. Sorry it’s taken this long (we don’t have multiple monitors handy in our WFH setups, but have found creative ways around the issue).
C
Christian Hujer
Fresh install of screen on a fresh install of Kubuntu 20.04: Same issue, segfault after splash. Snap 102, Screen version 1.0.42.
C
Christian Hujer
The workaround described by James Vogel did not work for me. But I have evidence that this is related to a multi-monitor configuration. I have four screens:
• HDMI-0, 3840×2160+0+0
• HDMI-1, 3840×2160+11520+0
• DP-0, 3840×2160+3840+0 (primary)
• DP-2, 3840×2160+7680+0
In this configuration, screen segfaults.
When I reduce this to:
• DP-0, 3840×2160+3840+0 (primary)
then screen doesn't segfault.
C
Christian Hujer
With this configuration:
• DP-0, 3840×2160+0+0
• DP-2, 3840×2160+3840+0
(HDMI displays disabled)
screen does not segfault.
C
Christian Hujer
With this configuration:
• HDMI-0, 3840×2160+0+0
• DP-0, 3840×2160+3840+0 (primary)
• DP-2, 3840×2160+7680+0
screen does not segfault.
But when enabling HDMI-1 again, with this xrandr:
• HDMI-0, 3840×2160+0+0
• HDMI-1, 3840×2160+11520+0
• DP-0, 3840×2160+3840+0 (primary)
• DP-2, 3840×2160+7680+0
screen still segfaults.
C
Christian Hujer
With this configuration:
• HDMI-0, 3840×2160+0+0
• HDMI-1, 3840×2160+11520+0
(Huge gap in canvas)
No segfault.
C
Christian Hujer
With this configuration:
• HDMI-1, 3840×2160+7680+0
• DP-0, 3840×2160+0+0 (primary)
• DP-2, 3840×2160+3840+0
Screen starts.
For me, it seems as if screen segfaults as soon as there are more than 3 active displays.
C
Christian Hujer
BTW this means that the information that a specific version of screen started to segfault MAY be a red herring! I have in between connected a 4th screen as well, and the version of screen that I deemed working in the past may be faulty in the same way as well.
J
Jared Biel
I'm trying to use screen.so version 1.0.42 via the AUR (https://aur.archlinux.org/packages/screen-desktop/) and am experiencing this same issue. If there's any troubleshooting data that I could post I'm happy to do so.
J
James Vogel
I just circled back to this again same issue with latest
J
James Vogel
New information! I just ran arandr and disabled both monitors (so I am only using 1 monitor) and ran this with no segfault. J Sherwani (Pop Team)
J
James Vogel
Christian Hujer Eric Christeson Jordan Robinson i think theres a weird state thing going on with screen for all of us, probably from installing debs and snaps and reinstalling etc. Luckily I think I found a workaround.
- uninstall deb and snap
- install latest snap
- arandr/xrandr yourself down to 1 monitor
- start screen and login (yay no segfault!)
- quit screen
- change monitors back to multi monitor
- start screen again (yay no segfault!)
Screen seems to be working and fully operational for me, though the state thing makes no sense unless it writes somewhere other than ~/.config/Screen cause I have nuked that dir many times.
Hope it fixes your problem like it fixed mine!
v1.0.41
J
Jordan Robinson
James Vogel: Wow nice work! That seems to fix it if I go up to two monitors, but sadly it does still segfault if I go up to three.
Interestingly, even if I add the third monitor while screen is running, the act of adding the monitor (through arandr) seems to kill screen.
J Sherwani (Pop Team) Is a three monitor configuration supported? I'm now wondering if I'm encountering a different bug, since before this it would break no matter what.
J
James Vogel
Jordan Robinson: I have three and it's not segfaulting interestingly enough
J
Jordan Robinson
James Vogel Thanks for your reply, it made me wonder what was different and I did a bit of investigation.
It looks like it crashes if the monitors are in the second configuration attached. The first configuration works.
My primary monitor is a laptop screen so it has a smaller resolution.
I think this is likely a different bug though, perhaps it tries to get the top left point and fails.
J Sherwani (Pop Team) would you want this created as a separate bug?
E
Eric Christeson
Jordan Robinson: James Vogel nice work. I tried un-docking my laptop and it runs fine. I re-docked the laptop while running screen and the program crashed with the same message. My 3-monitor layout is slightly different. All the same resolution, but still strange.
J
James Vogel
for reference.. here is my setup. and this works...
Center monitor is primary.
Middle monitor is 2k
the sides are both 1080p
J Sherwani (Pop Team)
Merged in a post:
[Linux] v1.0.27: relocation error
m
matt katz
Screen fails to launch after upgrade to v1.0.27.
screen: v1.0.27
snap,snapd: 2.44-3-1
distro: Arch Linux 5.4.33
step to reproduce:
$ sudo snap remove screen; sudo snap install screen --classic; screen
screen removed
screen 1.0.27 from Screen, Inc. (screen) installed
/snap/screen/87/screen/Screen: relocation error: /var/lib/snapd/snap/screen/87/screen/../usr/lib/x86_64-linux-gnu/libp11-kit.so.0: symbol nanosleep version GLIBC_2.2.5 not defined in file libpthread.so.0 with link time reference
C
Christian Hujer
I also tried the .deb 1.0.39 and it also segfaults at start after the slapsh window.
C
Christian Hujer
For me, the snap as of today (Snap 99, screen versoin 1.0.39) still segfaults at start after the splash window.
J Sherwani (Pop Team)
Merged in a post:
[Linux] Segmentation fault at start
C
Christian Hujer
Screen segmentation faults at start.
Version: screen-desktop 1.0.26
OS: Kubuntu 18.04.4 LTS
The window appears but then disappears the moment the segmentation fault happens.
Note: I've just installed screen-desktop 1.0.26 after uninstalling 1.0.19.
Load More
→