https://bugs.kde.org/show_bug.cgi?id=370325

            Bug ID: 370325
           Summary: Choqok 1.6 segfaults before displaying any window
           Product: choqok
           Version: unspecified
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: mehrdad.mom...@gmail.com
          Reporter: sombrag...@sombragris.org
                CC: scarp...@kde.org

Using Choqok 1.6.0 under 
KDE Frameworks 5.25.0
Qt 5.7.0 (built against 5.7.0)
running on Linux, Slackware64-current

Choqok 1.6.0 compiles ok but it segfaults shortly after OAuth is invoked for
twitter. No window manages to display.

Below is the console output:

[eduardo:~/build/slackbuilds/choqok]$ choqok
org.kde.choqok: Choqok  1.6.0
org.kde.choqok: 
org.kde.choqok: 
org.kde.choqok: 
org.kde.choqok: 
org.kde.choqok.lib: 
org.kde.choqok.lib: 
org.kde.choqok.lib: 
org.kde.choqok.lib: ("Account_****")
org.kde.choqok.lib: "Account_****"
org.kde.choqok.lib: Loading Plugin: "choqok_twitter"
org.kde.choqok.lib: 
org.kde.choqok.twitterapi: 
org.kde.choqok.twitter: 
org.kde.choqok.lib: Successfully loaded plugin ' "choqok_twitter" '
org.kde.choqok.lib: Finding: "*****"
org.kde.choqok.lib: 
org.kde.choqok.lib: 
org.kde.choqok.lib: Wallet successfully opened.
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.lib: 
org.kde.choqok.twitterapi: 
org.kde.choqok.lib: 
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.lib: 
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.twitterapi: UsingOAuth: true
org.kde.choqok.twitterapi: 
Segmentation fault
[eduardo:~/build/slackbuilds/choqok]$

Previously, 1.5 ran OK.

Thanks, 

Eduardo

Reproducible: Always

Steps to Reproduce:
1. Run choqok
2. The program segfaults.
3.

Actual Results:  
Segfault before there is even a window displayed

Expected Results:  
Program should run correctly

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to