Bug 23170 - KBibTeX fails to start without environment variables set
Summary: KBibTeX fails to start without environment variables set
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-12 11:59 CEST by Yuri Chornoivan
Modified: 2018-06-14 09:50 CEST (History)
2 users (show)

See Also:
Source RPM: kbibtex-0.8-0.git20180527.1.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Yuri Chornoivan 2018-06-12 11:59:51 CEST 
Description of problem: It is impossible for me to start the new version of KBibTeX without setting some environment variables

export QT_PLUGIN_PATH=/usr/lib64/qt5/plugins
export LD_LIBRARY_PATH=/usr/lib64
export KDEDIRS=/usr

as it is written here:

https://userbase.kde.org/KBibTeX/Development#Installation

Version-Release number of selected component (if applicable): 0.8-0.git20180527


How reproducible: always


Steps to Reproduce:
1. Press Alt+F2
2. Type 'kbibtex'
3. Press Enter

An immediate crash occurs. The same thing can be observed when starting from Konsole.

Thanks for fixing this bug.
Marja Van Waes 2018-06-12 13:38:05 CEST

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 1 David GEIGER 2018-06-12 16:10:49 CEST 
It's strange this issue!

Can you give me the output of:

$ rpm -qa |grep kbibtex

CC: (none) => geiger.david68210

Comment 2 Yuri Chornoivan 2018-06-12 17:40:41 CEST 
(In reply to David GEIGER from comment #1)
> Can you give me the output of:
> 
> $ rpm -qa |grep kbibtex

Sure. But only when I can reach the machine again 2018-06-14). Thanks for your patience.
Comment 3 Yuri Chornoivan 2018-06-14 09:15:57 CEST 
lib64kbibtex0-0.8-0.git20180527.1.mga7
kbibtex-0.8-0.git20180527.1.mga7
Comment 4 Yuri Chornoivan 2018-06-14 09:50:41 CEST 
It seems that after reboot it does not crash on startup anymore (just crashes with every .bib file opened). So it is invalid.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.