lxterminal crashed with SIGSEGV from pcmanfm

Bug #1678308 reported by Dirk Heumann
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxterminal (Ubuntu)
New
Medium
Unassigned

Bug Description

Tried to press F4 in pcmanfm showing an USB stick path. No lxterminal started, it crashed.
The same happened when I tried to start a terminal via the menu
   "Tools"-->"Open current folder in Terminal F4"

1) $ lsb_release -rd
Description: Ubuntu Zesty Zapus (development branch)
Release: 17.04

2) $ apt-cache policy lxterminal
lxterminal:
  Installed: 0.3.0-1
  Candidate: 0.3.0-1
  Version table:
 *** 0.3.0-1 500
        500 http://ftp5.gwdg.de/pub/linux/debian/ubuntu zesty/universe amd64 Packages
        100 /var/lib/dpkg/status

3) I expect that the "lxterminal" starts.

4) No "lxterminal" appeared. Starting "lxterminal" via ALT-F2 worked.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: lxterminal 0.3.0-1
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Mar 31 22:13:06 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/lxterminal
InstallationDate: Installed on 2013-10-30 (1248 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: lxterminal -e
SegvAnalysis:
 Segfault happened at: 0x55940afcca54: cmpb $0x2d,(%rdi)
 PC (0x55940afcca54) ok
 source "$0x2d" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: lxterminal
StacktraceTop:
 ()
 ()
 ()
 __libc_start_main (main=0x55940afc8930, argc=2, argv=0x7ffff19455e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff19455d8) at ../csu/libc-start.c:291
 ()
Title: lxterminal crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip heumann lpadmin lxd plugdev sambashare sudo vboxusers

Revision history for this message
Dirk Heumann (dirk-heumann) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x000055940afcca54 in terminal_new.constprop ()
 #1 0x000055940afcd958 in lxterminal_initialize ()
 #2 0x000055940afc8a02 in main ()
StacktraceTop:
 terminal_new.constprop ()
 lxterminal_initialize ()
 main ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in lxterminal (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote : Re: [Bug 1678308] [NEW] lxterminal crashed with SIGSEGV from pcmanfm

What if you navigate to the path in terminal and then try to open a new terminal? Which path is this and which USB device? The output of `lsusb` and assuming this is a block device, `lsblk` might be useful.
--
       @wxl | polka.bike
C563 CAC5 8BE1 2F22 A49D
68F6 8B57 A48B C4F2 051A

Revision history for this message
Dirk Heumann (dirk-heumann) wrote :

I started "lxterminal &" from the terminal in the USB path
  /media/dirk/32GB_USB3_Dirk
successfully, and this works from everywhere.

Trying to start lxterminal from another path within "pcmanfm" did not work too from any path, so it is not the USB device.

When I did this on another computer with the same USB drive, this worked, what baffled me a bit.

Therefore I tried to start lxterminal via "Tools"-->"Run a Command in Current Folder...".
This worked also on this computer from everywhere.

I do not know if there is a wrong default terminal settings (I use xfce, lxde, mate, unity) in different "real" - no VM - Ubuntu 17.04 machines.

Revision history for this message
Dirk Heumann (dirk-heumann) wrote :

After I tried "lubuntu" instead of 'lxde" as desktop manager, all worked like expected.

Then I tried it from pcmanfm within 'xfce', 'ubuntu', which failed too. Starting via "Tools"-->"Run a Command in Current Folder..." worked always.

Revision history for this message
Dirk Heumann (dirk-heumann) wrote :

I solved the problem, when I replaced inside of
  ~/.config/libfm/libfm.conf
the line
  terminal=lxsession-default-terminal %s
by
  terminal=lxterminal %s
.

Thank you very much Walter! Your questions did push me to dig much deeper and to solve the problem in the end.
  Inside of Unity I got the following meessage when starting 'pcmanfm .&' in a terminal:
  $ pcmanfm .&
  ** (pcmanfm:14802): WARNING **: Couldn't register with accessibility bus: Did
  not receive a reply. Possible causes include: the remote application did not
  send a reply, the message bus security policy blocked the reply, the reply
  timeout expired, or the network connection was broken.

  ** (pcmanfm:14802): WARNING **: terminal lxsession-default-terminal isn't known,
  consider report it to LibFM developers
  $
This was the hint needed to solve the issue.
What I do not understand: Why did it work in 'lubuntu'?

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.