segmentation fault upon start of putty, pterm, etc

Bug #1718054 reported by Ldx
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
putty (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10

putty:
  Installato: 0.70-1
  Candidato: 0.70-1
  Tabella versione:
 *** 0.70-1 500
        500 http://it.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
        100 /var/lib/dpkg/status

"putty" executable and its companions like "pterm", installed from the standard software package as above, give immediately "segmentation fault" when launched from command line (launching via Gnome shell simply nothing happens).

Tried to compile putty from source with gtk-3 libraries, compile and build are ok but as soon as I launch putty, I get again segmentation fault.

Aldo

Tags: artful
Revision history for this message
Ldx (a-giove) wrote :

Installed .DEB packages of Putty from Ubuntu 16.04, work flawlessly.

tags: added: artful
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in putty (Ubuntu):
status: New → Confirmed
Revision history for this message
Orso (dev00) wrote :

same problem here, segmentation fault from console and nothing happens when launching from desktop shortcut

Revision history for this message
Dennis M. Punjabi (denpun) wrote :

Can confirm issue

Temporary workaround but possibly insecure ??

1) Ensure you can sudo and run commands

2) Run: sudo -u <currently_logged_in_to_gui_username> putty

Revision history for this message
Ldx (a-giove) wrote :

Dennis, I followed you suggestion and tried to run with sudo the 0.70 executable and it works without crashing. On the terminal I got this:

$ sudo -u MY_NAME ./putty

(putty:29025): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(putty:29025): Gtk-WARNING **: Allocating size to GtkScrollbar 0x5608c2896480 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

Revision history for this message
Dennis M. Punjabi (denpun) wrote :

Hi,

TBH I am not too sure. I have not looked at the code. Maybe there is a fallback/default size. I think those are just GTK warnings and not the root cause of or related to the segfault/crash.

This bug I think is a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/putty/+bug/1720905

Maybe there you can find more information you are looking for?

Also try here:
https://bugs.launchpad.net/ubuntu/+source/putty

Dennis

Revision history for this message
Ldx (a-giove) wrote :

Dennis, I also think that those console warnings have probably no relationship with the crash.

The other bug you mentioned appears similar, and it's Wayland-related. I'll try to restart the session in XOrg and check if it will happen or not.

However, that bug is a duplicate of this one, since this was filed in september, bug #1720905 in october... :-)

I'll let you know.
Aldo

Revision history for this message
Ldx (a-giove) wrote :

Just restarted session under Xorg, and Putty 0.70 works fine. So the behaviour is the same of the other bug you mentioned; I'll subscribe that one and leave some comments there.

Thank you
Aldo

Revision history for this message
Ivemex (ivemex) wrote :

sudo -u MY_NAME putty

works

Revision history for this message
Dennis M. Punjabi (denpun) wrote :

@Aldo,
Hi,
>> However, that bug is a duplicate of this one, since this was filed in september, bug #1720905 in october... :-)

I did notice that and I actually meant "similar to". Sorry. :)

I also did not want to mark the other one as a duplicate of this because it had some useful info and when one is marked a a duplicate of the other, it gets tucked/hidden away...sort of.

@Ivemex,
Thanks for confirmation.

----

Happy bug reporting/fixing! :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.