Any idea why

  kwrite filename.ext 2>/dev/null &

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

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

(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

(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. :(

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

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