It dies when you right click

Bug #119799 reported by Theodotos Andreou
2
Affects Status Importance Assigned to Milestone
treeline (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When you are editing an entry in the left side and you attempt to right click the program dies with this message:
Segmentation fault (core dumped)

You can successfully copy and paste test in the right side though

Revision history for this message
Vincent Legout (vlegout) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems. <http://wiki.ubuntu.com/DebuggingProcedures> Thanks!

Changed in treeline:
status: Unconfirmed → Needs Info
Revision history for this message
Theodotos Andreou (theodotos) wrote :

I 'll try to be more specific. The treeline app has two panels, left and right. The left one is used to display the titles of your tasks and the other one it has the complete content of them. When you try to paste some more text to the title of a task, in the left panel (the text is highlighted and the cursor is blinking), as soon as you right click the program dies. You can safely paste text in the right panel so it is not an issue of functionality. But if you accidentaly right click in the left panel during editing text the program will die and if your work is not saved you are going to loose it.

Revision history for this message
Theodotos Andreou (theodotos) wrote :

Oh and I forgot to mention that I am using Kubuntu Feisty. If you need more info on my setup let me know.

Revision history for this message
Vincent Legout (vlegout) wrote :

Please try to obtain a debug backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.
What is the version of the package you are running ?

Revision history for this message
Theodotos Andreou (theodotos) wrote :
Download full text (9.4 KiB)

It is notable that when using gdb to run the program it didn't die but froze instead

Version:
----------
apt-cache showpkg treeline
Package: treeline
Versions:
1.0.0b-1 (/var/lib/apt/lists/cy.archive.ubuntu.com_ubuntu_dists_feisty_universe_binary-i386_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/cy.archive.ubuntu.com_ubuntu_dists_feisty_universe_binary-i386_Packages
                  MD5: 7b8f855e2adc1a7a10908f8ef7d85ce3

Reverse Depends:
Dependencies:
1.0.0b-1 - python (2 2.3) python-support (2 0.2) python-qt3 (0 (null)) aspell (16 (null)) ispell (0 (null))
Provides:
1.0.0b-1 -
Reverse Provides:

Backtrace:
-------------
cat gdb-treeline.py.txt
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run /usr/share/treeline/treeline.py
Starting program: /usr/bin/python /usr/share/treeline/treeline.py
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210648368 (LWP 21592)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Qt: gdb: -nograb added to command-line options.
         Use the -dograb option to enforce grabbing.
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging...

Read more...

Vincent Legout (vlegout)
Changed in treeline:
status: Needs Info → Confirmed
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.