Bug 551146 - [abrt] crash detected in backintime-kde-0.9.26-3.fc12
Summary: [abrt] crash detected in backintime-kde-0.9.26-3.fc12
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: backintime
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b43f9840
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-29 06:48 UTC by Jason Farrell
Modified: 2010-05-27 19:23 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-27 19:23:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (516 bytes, text/plain)
2009-12-29 06:48 UTC, Jason Farrell
no flags Details

Description Jason Farrell 2009-12-29 06:48:29 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Click the 'Exclude' tab
2. Click the 'Add' button (not 'Add file' or 'Add folder)
3. Attempt to add a pattern to exclude list. e.g.: "*.Trash-*" or "*.bak"
4. Click Ok

Comment: crashes when adding a pattern to the exclude list.

backtrace
-----
Summary: TBb43f9840 settingsdialog.py:418:on_btn_exclude_add_clicked:TypeError: add_exclude_() takes exactly 2 arguments (1 given)

Traceback (most recent call last):
  File "/usr/share/backintime/kde4/settingsdialog.py", line 418, in on_btn_exclude_add_clicked
    self.add_exclude_(  )
TypeError: add_exclude_() takes exactly 2 arguments (1 given)

Local variables in innermost frame:
pattern: *.Trash-*
ret_val: (PyQt4.QtCore.QString(u'*.Trash-*'), True)
self: <settingsdialog.SettingsDialog object at 0x2bde518>

cmdline: python /usr/share/backintime/kde4/app.py 
component: backintime
executable: /usr/share/backintime/kde4/app.py
kernel: 2.6.31.9-174.fc12.x86_64
package: backintime-kde-0.9.26-3.fc12
uuid: b43f9840

Comment 1 Jason Farrell 2009-12-29 06:48:31 UTC
Created attachment 380750 [details]
File: backtrace

Comment 2 Tim Jackson 2010-05-27 19:23:39 UTC
Thank you for the report. As advised by the backintime authors, this has been reported in the upstream bugtracker:
https://bugs.launchpad.net/backintime/+bug/586506


Note You need to log in before you can comment on or make changes to this bug.