k3bsetup show an emty dialog

*** Bug 23311 has been marked as a duplicate of this bug. ***

I have same problem on Italian version

(In reply to comment #0)
> opening k3bsetup or selecting "Settings -> K3b Setup" one is presented with
> and empy dialog box with no options.
>
> ether k3bsetup should not exist and error should not indicate one should
> change something in k3bsetup, or the dialog should be back.

I can confirm this with breezy, k3b version 0.12.2-0ubuntu2. It is not a sudo problem, since
when I execute it under 'ssh -X root@localhost', the problem remains.

I am experiencing the same problem with k3bsetup showing an empty dialog. I have tried to run k3bsetup from
the terminal with sudo k3bsetup, or kdesu k3bsetup with the same results.
I am running Kubuntu 5.10, Kernel 2.6.12.16, KDE 3.4.3.

I am also having another problem with K3B which may or may not be related, I don't know yet:
When I try to erase a CDRW disc, after starting K3B from a terminal with sudo or kdesu, the erasing dialog
appears and K3B becomes unresponsive.

I am also having this problem. It could be quite a major bug as it seems to
limit cd writing functionality (at least on my system) I cannot get k3b to function.

I'm also using k3b 0.12.2 on KDE 3.4.3 with kernel 2.6.12-9-686 and see a blank
dialogue when I run k3bsetup or kdesu k3bsetup. When I run k3b or kdesu k3b a
dialogue appears asking me to run k3bsetup2 (not k3bsetup) but clicking the
button to run k3bsetup2 does nothing.

(In reply to comment #0)
> opening k3bsetup or selecting "Settings -> K3b Setup" one is presented with
> and empy dialog box with no options.
>
> ether k3bsetup should not exist and error should not indicate one should
> change something in k3bsetup, or the dialog should be back.

Agreed. I'm having the same problem. It renders K3b useless.

I've got the same problem in dapper.
Version (0.12.10).

I also see the same problem.

Sorry - didn't specify, in breezy...

I am also experiencing this problem on Dapper, k3b version 0.12.10. when running k3b normally.

If I run sudo k3b, instead I get
kdesu: cannot connect to X server :0
in the terminal when going to k3bsetup.

It is not a problem of using gnome.
I use Dapper (did not have that problem in Breezy) and installed kubuntu-desktop also. But strangely enough, even in KDE the menu is empty.

I confirm this bug using k3b 0.12.10-0ubuntu4

That's what I got running k3b->setttings->k3b setup

I ran it from command line: k3bsetup

Session management error: Authentication Rejected, reason : None of the authenti cation protocols specified are supported and host-based authentication failed
Session management error: Authentication Rejected, reason : None of the authenti cation protocols specified are supported and host-based authentication failed
kbuildsycoca running...

As I am seeing the exact same thing ("blank dialog") with other kcmshell modules, I gather it has nothing to do with k3b, but something is wrong with kcmshell.

I ran a loop through all kcmshell modules and took a screenshot of them to see how many are affected.

On my system, three modules came up blank: k3bsetup2, backgound and keyboard. Try it yourself with `kcmshell background`.

There are no indications on stdout of any problems. Something is terribly amiss.

I'm using Kubuntu Breezy.

Here's the screenshot loop, in case someone finds those kinds of things interesting:

    kcmshell --list | grep -v "The following modules" | (while read MODULE STUFF; do echo $MODULE; { kcmshell $MODULE & }; sleep 3; import -window 0x2200007 $MODULE.png; killall kcmshell; done; )

This is not a bug with kcmshell. It is due to the kubuntu_01_hide_k3bsetup.diff patch, adding NoDisplay=true to the .desktop file for k3bsetup2 so it doesn't show in the K menu.

I am releasing a version with a new patch that modifies the Category instead of adding NoDisplay=true so it is not shown in the K Menu while still working with kcmshell.

in
/usr/share/applnk/Settings/System/k3bsetup2.desktop
change the line
NoDisplay=True
to
NoDisplay=False

If k3b still complains about insufficient cdrecord privilieges when you try to burn, see my notes in bug 32039