Adept database locked advised run dpkg need superuser priv?

Superuser privileges means running the command with sudo, in that case:

sudo dpkg --configure -a

Mr. Braden,

MANY thanks. Being a 'novice' at this, some terms are foreign to me and quite often can't be found in the help or docs. When I ran that command, I got this, which I assume did the trick as now 'adept' is happy with me. ;-)
-greg
-----------------------------------------------------------------------
greg@greglt1:~$ sudo dpkg --configure -a
Password:
Setting up vmware-player-kernel-modules-2.6.20-15 (2.6.20.5-15.20) ...

Setting up vmware-player-kernel-modules (2.6.20.15.14) ...
greg@greglt1:~$
------------------------------------------------------------------------
-----Original Message-----
>From: Kjell Braden <email address hidden>
>Sent: Apr 21, 2007 3:33 AM
>To: <email address hidden>
>Subject: Re: [Question #5301]: Adept database locked advised run dpkg need superuser priv?
>
>Your question #5301 on kde-systemsettings in ubuntu changed:
>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301
>
> Status: Open => Answered
>
>Kjell Braden proposed the following answer:
>Superuser privileges means running the command with sudo, in that case:
>
>sudo dpkg --configure -a
>
>_______________________________________________________________________
>If this answers your question, please go to the following page to let us
>know that it is solved:
>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301/+confirm?answer_id=0
>
>If you still need help, you can reply to this email or go to the
>following page to enter your feedback:
>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301

I don't know if I can include this additional 'quirk' in Adept, but if something (just about anything) goes awry, it will not restart except in read-only mode or not at all, just times out and halts. Restarting PC gets it going again.
-greg-

-----Original Message-----
>From: Kjell Braden <email address hidden>
>Sent: Apr 21, 2007 3:33 AM
>To: <email address hidden>
>Subject: Re: [Question #5301]: Adept database locked advised run dpkg need superuser priv?
>
>Your question #5301 on kde-systemsettings in ubuntu changed:
>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301
>
> Status: Open => Answered
>
>Kjell Braden proposed the following answer:
>Superuser privileges means running the command with sudo, in that case:
>
>sudo dpkg --configure -a
>
>_______________________________________________________________________
>If this answers your question, please go to the following page to let us
>know that it is solved:
>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301/+confirm?answer_id=0
>
>If you still need help, you can reply to this email or go to the
>following page to enter your feedback:
>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301

As far as I have understood it is not a only problem with adept, but with the system (x-server?) not removing a lock-file. I have tried this many times by now (though so far not in Feisty), and found that this fixes the problem:

sudo rm /var/lib/dpkg/lock

sudo dpkg --configure -a

What we both experienced was Bug [48625]. The status seems to be 'Fix Released', so unless you still run Dapper 6.06, I would suggest it was reopened.

Just a small edit:
Bug [48625] is related to this problem, but only addresses a specific part of it.

According to another reply, this is actually Bug [48625] which others are experiencing.
I ran the recommended command you suggested but it made no difference. The other answer suggested an additional command:

sudo rm /var/lib/dpkg/lock
sudo dpkg --configure -a

-greg

-----Original Message-----
>From: pcaddict44 <email address hidden>
>Sent: Apr 21, 2007 4:24 PM
>To: <email address hidden>
>Subject: Re: [Question #5301]: Adept database locked advised run dpkg need superuser priv?
>
>Your question #5301 on kde-systemsettings in ubuntu changed:
>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301
>
>You gave more information on the question:
>I don't know if I can include this additional 'quirk' in Adept, but if something (just about anything) goes awry, it will not restart except in read-only mode or not at all, just times out and halts. Restarting PC gets it going again.
>-greg-
>
>
>-----Original Message-----
>>From: Kjell Braden <email address hidden>
>>Sent: Apr 21, 2007 3:33 AM
>>To: <email address hidden>
>>Subject: Re: [Question #5301]: Adept database locked advised run dpkg need superuser priv?
>>
>>Your question #5301 on kde-systemsettings in ubuntu changed:
>>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301
>>
>> Status: Open => Answered
>>
>>Kjell Braden proposed the following answer:
>>Superuser privileges means running the command with sudo, in that case:
>>
>>sudo dpkg --configure -a
>>
>>_______________________________________________________________________
>>If this answers your question, please go to the following page to let us
>>know that it is solved:
>>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301/+confirm?answer_id=0
>>
>>If you still need help, you can reply to this email or go to the
>>following page to enter your feedback:
>>https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301

Hey Greg.

I originally didn't notice that the reason for the crash was the use of Automatix2. What did you install and have you tried using Automatix2 to uninstall those things again?

After having done this, run the previously posted commands and see if it works.

Well, I'm kinda starting over as the system had become unstable. I will go thru the scenario with automatix & advise. Biggest challenge to me right now is 'disaster recovery' I.e., how to go back if something 'gets broken' (I guess that's the current term for this platform - there are several terms we use when Win-doze goes kaput, some of them quite 'colorful'). I'm very anxious to throw off the shackles of Win-doze and get Linux to work on my 4 PC's and a laptop. I will keep you posted.

In the interim, are there any resources (books/URL's) you might recommend as learning tools?

Thanks for all your help.

-greg

-----Original Message-----
From: "Nicolai" <email address hidden>
To: "<email address hidden>" <email address hidden>
Sent: 4/24/07 12:28 AM
Subject: Re: [Question #5301]: Adept database locked advised rundpkg need superuser priv?

Your question #5301 on kde-systemsettings in ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301

    Status: Open => Answered

Nicolai proposed the following answer:
Hey Greg.

I originally didn't notice that the reason for the crash was the use of
Automatix2. What did you install and have you tried using Automatix2 to
uninstall those things again?

After having done this, run the previously posted commands and see if it
works.

_______________________________________________________________________
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301/+confirm?answer_id=6

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301

Hey.

If you reinstall (I assume it will be the Feisty release), then I would first of all advice you _not_ to use Automatix or Easyubuntu. It has already been denounced by the developers, so they would most likely refuse a bug-report about using it.
If you need video and music codecs then this site will supply you with the necessary information:

https://help.ubuntu.com/community/RestrictedFormats

The documentation pages also have articles about installing graphics drivers etc.

Nicolai M

Nicolai,
Thanks again. Well fortunately, I hadn't gotten around to trying the
automatix reinstall so I'm safe on that score. And yes, it was
primarily for the various codecs that I was thinking of using it. I'll
take your advice gladly, with my thanks to you for such a great job
supporting the product. And yes, I'm using Feisty/KDE.

..now if I could only get printing to work, I'd be home free <sigh>.

-greg

Nicolai wrote:
> Your question #5301 on kde-systemsettings in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301
>
> Status: Open => Answered
>
> Nicolai proposed the following answer:
> Hey.
>
> If you reinstall (I assume it will be the Feisty release), then I would first of all advice you _not_ to use Automatix or Easyubuntu. It has already been denounced by the developers, so they would most likely refuse a bug-report about using it.
> If you need video and music codecs then this site will supply you with the necessary information:
>
> https://help.ubuntu.com/community/RestrictedFormats
>
> The documentation pages also have articles about installing graphics
> drivers etc.
>
> Nicolai M
>
> _______________________________________________________________________
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301/+confirm?answer_id=8
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/5301
>
>

Ahh, another Kubuntu user. I was beginning to feel somewhat alone amongst the regular Ubuntus. ;)
I started on Kubuntu almost ten months ago now, so with the Feisty release going so smoothly (in my case) I thought it was about time that I thanked the community by helping new users get through some of the obstacles I originally experienced.

I haven't tried printing in Feisty yet, but Edgy simply required going to the 'Printers' setting in 'system settings' while you had to open adept and install the necessary ppd (printer driver) in Dapper.

Trying the Edgy method first wouldn't harm your system. But if it doesn't work, you could try installing the driver yourself. Personally, my printer is a HP, which meant I had to install 'hpijs-ppds' and 'hp-ppd'

If you need some general information about printing i would suggest these two sites:

https://help.ubuntu.com/community/Printers
www.linuxprinting.org/ <- I believe this was how I found my printer-driver's name back in Dapper.

I'm glad to have been of help. If you need any further help, you can always contact me on my Jabber-ID: <email address hidden>

Regards,
Nicolai

Hi again,

Yes, I've settled on 'K' just due to the easier/friendlier interface. It
also seems to have more software avail but that may be a mis-impression on
my part. Suffice it to say, it just appealed to me after having
experimented with 'U' (Feisty), MEPIS, MANDRIVA, KNOPPIX, FEDORA et al.
It's amazing how better one version is at detecting the peripherals than
another. Where 'U' had some difficulty setting up my wirelss on the
laptop, 'K' found it easily and works great. But when I tried installing
'K' on my Dell E521, the video went into deep space and I had to shut down
the PC for fear of damaging the video adapter or the flatpanel. Mandriva
loaded fine with no video issues. Go figger. The other issue I'm dealing
with is 'dual booting' with VISTA on the E521. So far, I've got everybody
showing in the Vista Bootloader, but selecting Linux gets me nada. I'm
using Easy BCD and Acronis. I think I'm pointing to the wrong location for
the Linux loader..gotta experiment further on that. At least Vista still
plays contentedly.

Now on to printing:

I'm using the HP OfficeJet K80 All-in-One. Even using the 'HP Tools'
(HPLIP) and after the printer is 'detected' and shows "OK" status, I get
errors when trying to print. I'll have to spend some time tomorrow with
the information you provided links to and go thru the setup again. I have
tried CUPS directly, tried using the hpijs driver and hpppd but still no
help. It seems Linux needs to mature a lot more in the printer area to
compete with the setup ease of XP and VISTA (sorry to say). I also have a
Dell photo 924 which setup easily in XP and VISTA but even the Linux
Foundation shows that the 924 is 'a fishing weight' (or similar) in terms
of getting it to work in Linux.

One note, I do not use JetDirect. Both printers are on one of my network
machines and are shared. I can print to them from anywhere on the network
under XP/VISTA. Once I get the HP working locally, I want to take the next
big step and see if I can get it recognized by other network machines. I'm
not sure how to approach that. I can see the host machine via SAMBA no
sweat and copy/move folders/files. Not sure how to get printing to work
yet. More homework needed.

I just KNOW I'm gonna have to find some 'textbooks' on Linux to bone up on
the basics. Years ago I used Zenix at a company I worked for, but that was
so long ago I've forgotten everything I learned <sigh>.

Thanks again for the assist. I'll let you know how my 'experiments' work
out by tomorrow night.

Regards,

-greg

> [Original Message]
> From: Nicolai <email address hidden>
> To: <email address hidden>
> Date: 4/24/2007 3:41:11 PM
> Subject: Re: [Question #5301]: Adept database locked
advised rundpkg needsuperuser priv?
>
> Your question #5301 on kde-systemsettings in ubuntu changed:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01
>
> Status: Open => Answered
>
> Nicolai proposed the following answer:
> Ahh, another Kubuntu user. I was beginning to feel somewhat alone amongst
the regular Ubuntus. ;)
> I started on Kubuntu almost ten months ago now, so with the Feisty
release going so smoothly (in my case) I thought it was about time that I
thanked the community by helping new users get through some of the
obstacles I originally experienced.
>
> I haven't tried printing in Feisty yet, but Edgy simply required going
> to the 'Printers' setting in 'system settings' while you had to open
> adept and install the necessary ppd (printer driver) in Dapper.
>
> Trying the Edgy method first wouldn't harm your system. But if it
> doesn't work, you could try installing the driver yourself. Personally,
> my printer is a HP, which meant I had to install 'hpijs-ppds' and 'hp-
> ppd'
>
> If you need some general information about printing i would suggest
> these two sites:
>
> https://help.ubuntu.com/community/Printers
> www.linuxprinting.org/ <- I believe this was how I found my
printer-driver's name back in Dapper.
>
> I'm glad to have been of help. If you need any further help, you can
> always contact me on my Jabber-ID: <email address hidden>
>
> Regards,
> Nicolai
>
> _______________________________________________________________________
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01/+confirm?answer_id=10
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01

Okay, having spent some <continued frustrating> additional hours trying to
get printing to function, here where things stand:

1). In HPLIP
 A). HP Officejet K80 is detected on USB bus;
 B). "Status" (simulated LCD window) shows 'printer idle';
 C). But actual printer status (in left column) indicates an error 'X'.

2). Selected Model is HP Officejet K80
 A). Driver: Foomatic/hpijs

If I send print jobs to the K80 they just 'hang' - status shows them in the
queue but nothing ever happens.

That's about it. Why is it so difficult to get something so simple as
printing to work?

-greg-

> [Original Message]
> From: Nicolai <email address hidden>
> To: <email address hidden>
> Date: 4/24/2007 3:41:11 PM
> Subject: Re: [Question #5301]: Adept database locked
advised rundpkg needsuperuser priv?
>
> Your question #5301 on kde-systemsettings in ubuntu changed:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01
>
> Status: Open => Answered
>
> Nicolai proposed the following answer:
> Ahh, another Kubuntu user. I was beginning to feel somewhat alone amongst
the regular Ubuntus. ;)
> I started on Kubuntu almost ten months ago now, so with the Feisty
release going so smoothly (in my case) I thought it was about time that I
thanked the community by helping new users get through some of the
obstacles I originally experienced.
>
> I haven't tried printing in Feisty yet, but Edgy simply required going
> to the 'Printers' setting in 'system settings' while you had to open
> adept and install the necessary ppd (printer driver) in Dapper.
>
> Trying the Edgy method first wouldn't harm your system. But if it
> doesn't work, you could try installing the driver yourself. Personally,
> my printer is a HP, which meant I had to install 'hpijs-ppds' and 'hp-
> ppd'
>
> If you need some general information about printing i would suggest
> these two sites:
>
> https://help.ubuntu.com/community/Printers
> www.linuxprinting.org/ <- I believe this was how I found my
printer-driver's name back in Dapper.
>
> I'm glad to have been of help. If you need any further help, you can
> always contact me on my Jabber-ID: <email address hidden>
>
> Regards,
> Nicolai
>
> _______________________________________________________________________
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01/+confirm?answer_id=10
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01

The reason as I see it is fairly simple; manpower. Many of the companies focus primarily on Windows-compatibility, meaning the drivers in many cases have to be made from scratch. Compatibility seems to improve fairly significantly between each release. Dapper was tough for me, Suse 9.3 and 10.0 beforehand were in my case nightmarish, and Fedora Core 3 so absurdly impossible, that I didn't even use it. Somehow I'm actually surprised it didn't scare me away. At least I've never had an ATI-card. :)

I share your frustration though, I very recently had to make a computer able to write in NTFS (Windows) drives, and because of one simple mistake it took me more than an hour.

In my case printing was a fairly seamless process (HP Deskjet 3940). I just had to remember that I shouldn't keep OpenOffice open while setting up the printer. At least in my case OpenOffice doesn't notice the changes and still tries to send to a generic printer, if it hasn't been closed down after the setup. That doesn't seem to be your problem, though.

I've never used HPLIB myself. My process is (assuming you use a USB-connection)

K -> System settings -> Printers - > Add -> Add printer/class -> Next -> Local printer (Parallel, Serial, USB) -> Next -> HP Deskjet 3900 (the one that didn't say USB 1) -> Next -> HP -> Deskjet 3940 HPIJS -> Next -> Test

If this doesn't work, then I must admit I really am at a complete loss with this one. My apparent suggestions would to assure that the printer still works on a Windows machine (it might be jammed or similar). Other than that, you might need to either make a new question here (so other people notice it) or to try the forum.

Hi Nicolai,

I would have responded earlier but the Internet backbone went down (for
some of lucky ones) here in Pennsylvania
so I've been 'off the air' for 24 hrs.

Don't think OpenOffice is an issue. I'll try that method you sugg'd and
see what's what. The printer is a HP K80
All-In-One (OfficeJet) and yes, it works fine in Windows as does the Dell
Photo 924 Inkjet. I'll keep flailing at
it and put up a problem report if still no progress <sigh>.

I'm just now experimenting with Jabber so you may get something from me
there. Which Client do you find the
best? Seems like there are a lot of them!

Rgds,

-greg-

> [Original Message]
> From: Nicolai <email address hidden>
> To: <email address hidden>
> Date: 4/26/2007 5:03:06 PM
> Subject: Re: [Question #5301]: Adept database
lockedadvised rundpkg needsuperuser priv?
>
> Your question #5301 on kde-systemsettings in ubuntu changed:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01
>
> Status: Open => Answered
>
> Nicolai proposed the following answer:
> The reason as I see it is fairly simple; manpower. Many of the companies
> focus primarily on Windows-compatibility, meaning the drivers in many
> cases have to be made from scratch. Compatibility seems to improve
> fairly significantly between each release. Dapper was tough for me, Suse
> 9.3 and 10.0 beforehand were in my case nightmarish, and Fedora Core 3
> so absurdly impossible, that I didn't even use it. Somehow I'm actually
> surprised it didn't scare me away. At least I've never had an ATI-card.
> :)
>
> I share your frustration though, I very recently had to make a computer
> able to write in NTFS (Windows) drives, and because of one simple
> mistake it took me more than an hour.
>
> In my case printing was a fairly seamless process (HP Deskjet 3940). I
> just had to remember that I shouldn't keep OpenOffice open while setting
> up the printer. At least in my case OpenOffice doesn't notice the
> changes and still tries to send to a generic printer, if it hasn't been
> closed down after the setup. That doesn't seem to be your problem,
> though.
>
> I've never used HPLIB myself. My process is (assuming you use a USB-
> connection)
>
> K -> System settings -> Printers - > Add -> Add printer/class -> Next ->
> Local printer (Parallel, Serial, USB) -> Next -> HP Deskjet 3900 (the
> one that didn't say USB 1) -> Next -> HP -> Deskjet 3940 HPIJS -> Next
> -> Test
>
> If this doesn't work, then I must admit I really am at a complete loss
> with this one. My apparent suggestions would to assure that the printer
> still works on a Windows machine (it might be jammed or similar). Other
> than that, you might need to either make a new question here (so other
> people notice it) or to try the forum.
>
> _______________________________________________________________________
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01/+confirm?answer_id=13
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
>
https://answers.launchpad.net/ubuntu/+source/kde-systemsettings/+question/53
01

Hi pcaddict44!
I had similar symptoms while trying to print to a HP LaserJet 1022 connected via USB. The was detected and its LED started blinking after submitting a job, but nothing was ever printed. In my case this was an issue with the USB 2.0 driver ehci-hcd and a specific USB 2.0 hub. If this hub was either disconnected or the printer was attached to the hub instead of the mainboard connectors, it suddenly worked.
There is a bug report somewhere in launchpad that suggests that unloading the ehci-hcd module should also work, but I didn't want to switch back to the slower USB 1.1 and just disconnected that hub.