package won't install

[tomcloyd]

Don't know if this is a software or post-installation issue. I got a notification to upgrade a package, and tried, with this result (in Muon) -

Package: /var/cache/apt/archives/libcv2.1_2.1.0-natty~ppa1_i386.deb
Error: trying to overwrite '/usr/share/opencv/lbpcascades/lbpcascade_frontalface.xml', which is also in package libcvaux2.2-data 2.2.0-maverick~ppa3

Can anyone tell me what the problem is, and if possible the soluton?

[Tanner1294]

Re: package won't install

Did it ask for yours or an administrators password when the package manager opened up?

[tomcloyd]

Re: package won't install

Did it ask for yours or an administrators password when the package manager opened up?

I was initially puzzled by this question, sensible though it is. Then I realized that I've never had a password on my personal account, only on the admin account, and it was that one I was giving it. So, I assigned a password to my pers. acct., and reran Muon. This time, the admin. password wouldn't make it happy, but the user acct. password did. That doesn't seem right at all. How could that be? (I still got the same error, though.)

Is it possible that the system notification version of Muon is running out of the admin. acct., but when I launch it from KMenu it's running out of user acct.? Makes some sense, but I find that when I click the sys-tray notification icon, the password it wants is still user acct., and the update still won't run.

Something's not right here, it seems.

It gets worse. I ran sudo muon, and it still asked for a password, and accepted only my user acct. password. Now I'm really confused. I assigned the user acct. password via System settings >...user management. I thought I was accessing my user account - "tomc" - but what was affected was my admin password. Major muddle here. Need to try to rethink this. Meanwhile I've changed my password back to what I expect it to be for admin level access.

[Snowhog]

Re: package won't install

Muon launches without requiring the administrator password (which is your password, if you were the user that installed Kubuntu). When you elect to install/uninstall a package, or want to configure software sources, you are then prompted for the password.

[tomcloyd]

Re: package won't install

Ah, yes it does, unlike Synaptic, which is what I've been using.

I'm still muddled about this user account password thing, as opposed to the admin. access password. I don't see a way to put a password on a user account which is separate from the admin. password, unless THAT is set at OS installation and cannot be changed after that (which seems like a bad idea). In System settings, the admin password and the user account password seem to be one and the same. I cannot make sense of this just now.

Yeah, just tried it out. There's no way to give my "tomc" acct a password without it's becoming the admin password which is then requested the next time I try to access user management.

So what if I had multiple user accounts? I don't need to know this, as I'll not likely ever have this situation, but I don't see how this gets handled. Must be in the docs, which I've not needed to study (relative to THIS anyway) so far.

Meanwhile, Muon still won't install that package.

[Snowhog]

Re: package won't install

*buntu does not use a separate Administrator user account - it's locked by default (See RootSudo)

[Tanner1294]

Re: package won't install

So what if I had multiple user accounts?

I've had multiple user accounts before but not using System Settings to create and add passwords to them. I did it all through a terminal which I suggest you use if you want to change passwords. To change a password of a specific account just type

sudo passwd insertusernamehere

then it will ask for the admin password, and have you enter the new password for the account twice.

In System settings, the admin password and the user account password seem to be one and the same. I cannot make sense of this just now

This may be true at the moment. This is probably a result of never having changed or set the Root accounts password. Whenever I install a Linux distro on my computer I use the command above on the Root account so that it has it's own more secure password. This way, if anything happens and I'm not able to access my own account I can still log into Root (via a terminal, tty, or KDE/GNOME). If you give the Root account it's own password, maybe it will make the password seperate from your own accounts.

[KeithZG]

Re: package won't install

In case others hadn't clarified, the default *buntu way is each user has a password, and certain users can use "sudo" or "kdesudo"---ie. Super User Do. Generally, when it's asking you for your password, that's what it's asking for. There is no "Administrator" by default; that role is the "root" user, and in *buntu its locked out to start with, unless you've decided otherwise during installation or afterwards (I tend to enable the root account on all my machines, give it a very complex password, then almost never use it).

So when you're fiddling with administrative settings, it's generally prompting you for your password since you have sudo privileges and thus except for some VERY rare circumstances your password unlocks anything that's admin-restricted.

But back to your problem at hand; looks like it's just a simple package conflict in that an older package had purview over an installed file, but now a different package "owns" it; since a file can't really be controlled by two different packages at once it doesn't want to continue. Both files are from PPAs, so they aren't actually from the main Kubuntu repos...that's the crux of the problem.

As soon as you install software from outside the repos, you've gotta look out for such conflicts: stuff outside of the official repos doesn't get as closely audited, and definitely isn't as tested to see if it conflicts with other packages. Nothing in the official repos should ever unnecessarily conflict, but if you have different peoples' PPAs there's not really any easy way for them to know that if someone installs stuff from both random strangers' PPAs that something will go wrong, and often it's a low priority problem anyways. That is to say, every person running a Personal Package Archive is off doing their own things, so there isn't the kind of coordination that would prevent problems like this, thus to a large degree it's up to you (and the forums, I suppose!) to avoid and/or fix these conflicts.

Firstly, my question would be which PPAs you're using (and have used; the package that's already installed seems to be from the 10.10 era). Secondly, if you try uninstalling the libcvaux2.2-data package, does it actually say anything else would be removed as well? It's possible it's a lingering dependency from something you installed in the past that isn't actually needed anymore, in which case you could simply get rid of the package and voila, problem solved