Bug 890774 - [abrt] bibus-1.5.1-7.fc17: connections.py:187:__init__:OperationalError: (2002, "Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)")
Summary: [abrt] bibus-1.5.1-7.fc17: connections.py:187:__init__:OperationalError: (200...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bibus
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1d601133387de85801ddd3f6598...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-29 22:12 UTC by Wouter
Modified: 2013-08-01 10:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 10:48:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: executable (25 bytes, text/plain)
2012-12-29 22:12 UTC, Wouter
no flags Details
File: dso_list (32 bytes, text/plain)
2012-12-29 22:12 UTC, Wouter
no flags Details
File: environ (1.84 KB, text/plain)
2012-12-29 22:12 UTC, Wouter
no flags Details
File: smolt_data (3.47 KB, text/plain)
2012-12-29 22:12 UTC, Wouter
no flags Details
File: backtrace (7.16 KB, text/plain)
2012-12-29 22:12 UTC, Wouter
no flags Details
File: core_backtrace (328 bytes, text/plain)
2012-12-29 22:12 UTC, Wouter
no flags Details

Description Wouter 2012-12-29 22:12:19 UTC
Description of problem:
After starting BiBus I tried to establish a connection with the local MySQL database, by connecting to it using the window that popped up in the Bibus environment. Then this error came up.

Version-Release number of selected component:
bibus-1.5.1-7.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        python /usr/share/bibus/bibus.py
kernel:         3.6.10-2.fc17.x86_64


Potential duplicate bug: 766954

Comment 1 Wouter 2012-12-29 22:12:22 UTC
Created attachment 670242 [details]
File: executable

Comment 2 Wouter 2012-12-29 22:12:24 UTC
Created attachment 670243 [details]
File: dso_list

Comment 3 Wouter 2012-12-29 22:12:25 UTC
Created attachment 670244 [details]
File: environ

Comment 4 Wouter 2012-12-29 22:12:27 UTC
Created attachment 670245 [details]
File: smolt_data

Comment 5 Wouter 2012-12-29 22:12:29 UTC
Created attachment 670246 [details]
File: backtrace

Comment 6 Wouter 2012-12-29 22:12:31 UTC
Created attachment 670247 [details]
File: core_backtrace

Comment 7 Fedora End Of Life 2013-07-04 03:20:51 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2013-08-01 10:48:28 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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