Bug 16506

Summary:	Running kwrite as root throws tons of "QSqlQuery::exec: database not open"
Product:	Mageia	Reporter:	Frédéric "LpSolit" Buclin <LpSolit>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	bittwister2, mageia
Version:	5
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Frédéric "LpSolit" Buclin 2015-07-31 02:25:41 CEST

Running kwrite as root throws tons of "QSqlQuery::exec: database not open". This problem is new in Mageia 5 (never got this message in Mageia 1-4). Pretty annoying as I call kwrite from a shell a lot to write code.

David Walser 2015-07-31 16:43:23 CEST

CC: (none) => mageia
Assignee: bugsquad => lmenut

Comment 1 Frédéric "LpSolit" Buclin 2015-08-26 13:19:27 CEST

Any idea why

  kwrite filename.ext 2>/dev/null &

has no effect? 2>/dev/null is supposed to suppress these errors.

Comment 2 Rémi Verschelde 2015-08-26 13:22:54 CEST

I guess those are warnings and not errors, so they are printed to stdout.

Comment 3 Bit Twister 2015-08-26 14:10:13 CEST

(In reply to Frédéric Buclin from comment #1)
> Any idea why
> 
>   kwrite filename.ext 2>/dev/null &
> 
> has no effect? 2>/dev/null is supposed to suppress these errors.

Running 64 bit install without the error. 

The only other change that I know about was I have told kde to 
 Disable all debug output in my user account. 

Run "kdebugdialog" in your user account, check mark Disable all debug output, Apply, OK

Then in a root terminal:

mkdir -p ~/.kde4/share/config/
and copy your user account's /home/xxx/.kde4/share/config/kdebugrc to
/root/.kde4/share/config/kdebugrc

If you do the above, log out/into root and still have the problem. try
   export $(dbus-launch)
and see if kwrite still has the problem.

CC: (none) => bittwister2

Comment 4 Frédéric "LpSolit" Buclin 2015-08-27 13:02:14 CEST

(In reply to Bit Twister from comment #3)
> Run "kdebugdialog" in your user account, check mark Disable all debug
> output, Apply, OK

Yeah, I did that already, but this doesn't help.


> If you do the above, log out/into root and still have the problem. try
>    export $(dbus-launch)
> and see if kwrite still has the problem.

Also doesn't help. The messages are still there. :(

Luc Menut 2016-08-25 16:47:36 CEST

Assignee: lmenut => kde

Comment 5 Frédéric "LpSolit" Buclin 2017-04-16 22:54:40 CEST

I cannot reproduce this issue anymore, neither in mga5 nor in cauldron.

Resolution: (none) => FIXED
Status: NEW => RESOLVED