The forum

I wanted to point out a couple of problems i had:

Edited by Alex64k

I have dark themes in KDE, like yours, and its just the theme.

That version is REALLY out of date, and I dont know why Ubuntu hasnt updated it in their repos. We dont support it anymore, and it shouldnt be used. Apparently, you can add the repos that we have listed into 13.04, and they should work, but the deb should work no matter what.

Now, that notwithstanding, it very well could be something that was caused by not setting up that minimal install right. Not saying that you did, but mine is build with the 12.04.2 minimal install, with pure KDE, and its fine and dandy. I think it may have just been a fluke.

Regardless, Anytime something like this happens, you want to completely remove POL via your package manager, and (after backing up your games if needed!) remove ~/.PlayOnLinux/

Then reinstall POL from the newest version on our download page.

Keep in mind that ANY Ubuntu release that is NOT an LTS, like 8.04, 10.04, and 12.04, should be considered beta, as they are not always stable, and are mostly experimental, regardless of their class as being finished products. I see more problems with non-LTS releases than LTS when it comes to Ubuntu. Just something to keep in mind. (im probably going to start a flame war with that one. lol)

All of that package manager stuff..... Id be willing to bet that it has to do something with that build or incomplete installs/downloads of packages (or maybe how apt-get is dealing with broken packages?) Idont know.

I tried again and i can easily re-produce it. This is the error:

root@ubuntu:~/Desktop# dpkg -i PlayOnLinux_4.2.1.deb
(Reading database ... 140468 files and directories currently installed.)
Preparing to replace playonlinux 4.1.1-1 (using PlayOnLinux_4.2.1.deb) ...
Unpacking replacement playonlinux ...
Setting up playonlinux (4.2.1) ...
gconf-schemas is /usr/sbin/gconf-schemas
Processing triggers for man-db ...
Processing triggers for desktop-file-utils ...
Processing triggers for gconf2 ...

(gconftool-2:3357): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
//bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.

The following errors comes up constantly now. I made a backup of my system folders again so now i can try to restore it and fix this error. If i don't do that, there is no way for me to fix this error using apt or dpkg. (as i written already last time i had to re-format).

Edited by Alex64k

bump: anyone having more information about this issue?

It has to be something that you are doing or the way your system is set up, because I have never seen a gconf error like this when installing it.

Hows about, completely remove POL, and reinstall using the package manager (install the repos in the Download section or install the DEB in the package manager).

Both times i installed Ubuntu 13.04 x64 using the "mini.iso" disk image, then i installed kde-full.

Id be willing to bet my next paycheck that you are building your system wrong. No offense, but that is the only thing that sticks out in your posts.

You need to try a regular version of Kubuntu (not a mini.iso build with KDE full). Just a regular Kubuntu 12.04.2 download (ONLY install LTS versions). The combo of 13.04 mini and however youre building it has to be breaking something on the system.

So, yeah. Try Kubuntu 12.04.2 LTS, not mini.iso, and try again. It should work like that.

Edited by RoninDusette

I'm not sure, but I don't see a problem of "db corruption" here, and quite probably nothing related directly to PlayOnLinux either.

What seems to be happening is that some recently installed package modified gconf configuration files, and the handling has been deferred to gconf triggers, that handle those changes in batches.
Problem is, the trigger tries to run some GUI, and since you switched to root user, it doesn't have access to the X server (nor your D-Bus session), and fails.
Since deferred work failed, its kept for later tries.

I'm not sure it will work, but personally at that point I'd try a gksu apt-get -f install or gksudo apt-get -f install as your normal user.
gksu and gksudo do what's necessary to run a program as root yet keep X server access.

Edited by petch

I am not building any system, just download the ubuntu server iso, press F4, select "minimal install", press enter, when you're up and running install kde-full. It's the same as the mini.iso install and it's not some alien configuration, it's just a normal ubuntu. I know the package is missing curl from the dependencies, is it missing anything else you assume must be always installed? As i said before, the error comes up if and only if i install POL from either the .deb file or from the repository. As soon as i remove it, the error goes away. I am sure it's POL causing the issue, i'm trying to understand why and how. Have you got any lead that might help me out?

I didnt say that it did. I just said that if not put together correctly, a mini.iso build can cause issues down the line, plus youre running an experimental linux version.

I'm sorry but it's hardly possible to put it together in a wrong way, since it's all automated by aptitude. And i'm pretty sure Canonical tests the ubuntu server installation disk, which means they have tested the minimal install procedure (documented and supported).

Now if you are too busy and don't have the time to help me debug the problem it's ok, i can understand, but please stop blaming the installation because it's neither custom nor "put together" by me. It's using the standard apt-get install procedure that canonical has designed and you also support with your repository. Also, the fact that installing POL gives the issue and uninstall it fixes it clearly means it's something inside the .deb package.

Again, i'm grateful for your support and your efforts, but you're kind of not showing any respect toward me since you keep implying it's my fault or making up that it's the installation (which, by the way, not only runs completely fine, but i've also tested this more than 4 times on 4 different systems - so i can say once again that you should rule out a broken system case).

As a side note, you can get a similar system with the standard disk just by uninstalling the meta-package ubuntu-desktop/xubuntu-desktop/kubuntu-desktop and install kde-full/xfce4/gnome.
If something is missing, then the .deb should contain the dependency and make aptitude install the rest but it's crearly not working (again, like with curl).

@petch: then it's POL that triggers the gconf configuration files, because in my tests it's the POL .deb file that causes the problems. Can that warning be ignored?

Edited by Alex64k

I'm sorry but it's hardly possible to put it together in a wrong way, since it's all automated by aptitude. And i'm pretty sure Canonical tests the ubuntu server installation disk, which means they have tested the minimal install procedure (documented and supported).

13.04 is an experimental version. LTS releases are not. There are bugs. It happens. I see them all of the time from Ubuntu Unity, as well.

Now if you are too busy and don't have the time to help me debug the problem it's ok, i can understand, but please stop blaming the installation because it's neither custom nor "put together" by me. It's using the standard apt-get install procedure that canonical has designed and you also support with your repository.

Nice attitude.....

Canonical did not invent apt-get, and apt-get is just package management. The people that put the repos together are humans, and in experimental repos, they have more issues than LTS versions.

Also, the fact that installing POL gives the issue and uninstall it fixes it clearly means it's something inside the .deb package.

So far, you are the only user I have seen report this, and you are using a non-standard build. I know it can be an issue, because I have run into issues like this when putting together an OS from the mini.iso. Im not guessing; Ive wasted many hours working on stuff, only to reinstall to a regular LTS version and have it work as it should.

Again, i'm grateful for your support and your efforts, but you're kind of not showing any respect toward me since you keep implying it's my fault or making up that it's the installation

Look, dude. Im not implying anything; simply offer a suggestion on what can be causing it, from experience.

(which, by the way, not only runs completely fine, but i've also tested this more than 4 times on 4 different systems - so i can say once again that you should rule out a broken system case).

Its obviously not completely fine, otherwise we wouldnt be having this conversation. haha. :)

Did you do mini.iso installs or 13.04 installs on those other ones that you tested? Again, you are the only user that has this problem at all.

For example, the following systems I have install PlayOnLinux on, from either deb or repo, work as prescribed:

mini.iso 12.04.2 LTS 64 bit with KDE pure
Kubuntu 12.04.2 LTS 64 bit (just regular kubuntu)
Ubuntu 12.04.2 LTS 64 bit (replaced Unity with Cinnamon)
Xubuntu 12.04.2 LTS 32 bit (my friends music laptop)
Ubuntu 12.04 LTS 32 bit with gnome-panel

And quite a few others. The only time I have seen issues like what you are showing is when I first tried to build my OS from mini.iso, and learned that its harder than it looks at first.

Notice that there are 2 different packages. kubuntu-desktop and kde-full. kubuntu-desktop is designed to run with the Ubuntu kernel releases, among other things.

If something is missing, then the .deb should contain the dependency and make aptitude install the rest but it's crearly not working (again, like with curl).

Any time that installing a deb from the command line does not work because of missing deps, you need to use:

[code]
sudo apt-get -f install
[/code]

to clean up those missing dependencies. Also, curl not being in the dep list is a known issue, and will be fixed, but you can install it very easy.

Edited by RoninDusette

Also, the fact that installing POL gives the issue and uninstall it fixes it clearly means it's something inside the .deb package.

A very common cause of broken future installs can be broken installs. Lets say your internet goes down right in the middle of an install; the next time you install, there will be errors most of the time. Just FYI. :)

You'd better not install standalone packages using dpkg -i, because it's a too low level tool: if you ask it to install a package it will, but not fetch nor install required dependencies as needed.
If you really don't want to go the full "add PoL repository, use apt-get" way, have a look at gdebi (gdebi-core, for command-line usage), this one will take care of the dependencies.
Maybe it's the root issue, but it's hard to tell.