Hi,
I can't reproduce this bug with 1.11.1-1 in intrepid, so I
am closing it as fixed.
Thanks,
James
** Changed in: roxterm (Ubuntu)
Status: Confirmed => Fix Released
--
Segmentation fault when started with the --directory option
https://bugs.launchpad.net/bugs/227685
You received thi
** Changed in: roxterm (Ubuntu)
Importance: Undecided => Medium
--
Segmentation fault when started with the --directory option
https://bugs.launchpad.net/bugs/227685
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Setting this to Confirmed since i can confirmed this bug on my side.
Some changes to the Test Case
The way to reproduce:
1. start roxterm
2. open another terminal and start roxterm the following way: roxterm
--directory=/usr
The problem seems to arise if there is another instance of roxterm
run
Here are the Backtrace and Vlagrind log as described in the wiki page.
** Attachment added: "roxterm-gdb-valgrind.tar.bz2"
http://launchpadlibrarian.net/14369678/roxterm-gdb-valgrind.tar.bz2
--
Segmentation fault when started with the --directory option
https://bugs.launchpad.net/bugs/227685
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report.
In your case, the command for step 3 should
Here is the output of the command:
# apt-cache policy roxterm
roxterm:
Installed: 1.8.0-1
Candidate: 1.8.0-1
Version table:
*** 1.8.0-1 0
500 http://ftp.lug.ro hardy/universe Packages
100 /var/lib/dpkg/status
I attached a strace log of the crash. I don't know what to make o
Not reproducible on a fresh installation of the roxterm package.
Could you check if your roxterm package is the lastest by typing the
following in the terminal? After which, paste the output here. Thanks
sudo apt-cache policy roxterm
** Changed in: roxterm (Ubuntu)
Status: New => Incompl
