Options on screen are mixed up

Bug #1163740 reported by Digulla-hepe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

To reproduce:

1. start "ubuntu-bug" from the console (without any options)
2. A new window "Apport" will open (I'm on KDE if that matters)
3. Select "Security related problems" and click "OK"
4. Select "Other problem" and click "OK"

I now get the message:

"This is expected as there is no "tty" allocated when running commands directly via ssh. ..."

It seems like options on the screen don't match the code executed. It's as if someone reordered the options on screen without updating the code that processes the selections.

To add insult to injury, the app crashes when I click on "OK":

Application: Apport KDE (python3.2mu), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6 QWidget::~QWidget (this=0xb6dae0, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1630
#7 0x00007fc3cfba1759 in ?? () from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so
#8 0x00007fc3cfb95976 in ?? () from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so
#9 0x00007fc3d0011cd4 in ?? () from /usr/lib/python3/dist-packages/sip.cpython-32mu.so
#10 0x00007fc3d00135b9 in ?? () from /usr/lib/python3/dist-packages/sip.cpython-32mu.so
#11 0x000000000046e617 in ?? ()
#12 0x00000000004d6ff9 in ?? ()
#13 0x000000000046e6af in ?? ()
#14 0x00000000004cb403 in ?? ()
#15 0x00000000004cb4b7 in PyDict_SetItem ()
#16 0x000000000049a924 in _PyModule_Clear ()
#17 0x000000000050a864 in PyImport_Cleanup ()
#18 0x000000000041b95c in Py_Finalize ()
#19 0x000000000041ba32 in Py_Exit ()
#20 0x000000000042c35f in ?? ()
#21 0x000000000087e9e0 in ?? ()
#22 0x0000000000b00fb0 in ?? ()
#23 0x00000000008bb960 in ?? ()
#24 0x0000000000000000 in ?? ()

Revision history for this message
Patrick Wigmore (patrick-wigmore) wrote :
affects: apport → apport (Ubuntu)
Revision history for this message
Benjamin Drung (bdrung) wrote :

Thanks for reporting this bug and sorry for taking so long to address it. The bug is tracked in bug #1967965 and therefore I mark it as duplicate of that bug.

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.