Calibre 2.16 install failure

signum · 01-18-2015, 01:55 PM

OS: Kubuntu 12.04
Calibre: trying to install 2.16

This morning I updated my Kubuntu with the latest patches. Nothing seemed out of order. Among other things, the updates replaced the kernel, Firefox, Flash and several ssl/ssh modules. Re-booted as required and attempted to install the latest Calibre.

The install *seemed* to go OK, but when I tried to try it out by typing "calibre" from the CLI, it returned a command prompt and then:
----------
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-xxxxxxxx" is owned by uid 1000
instead of uid 0
----------
where xxxxxxxx is my login name and 1000 is the uid of xxxxxxxx.
At this point it hung. No disk light flashing, no cpu time being run up as reported by "top," no new command prompt. I had to ^c to get out of it.

Attempts to download again, remove the old install, etc., all wound up with about the same result. I don't know where the error truly lies, or what to do next. The problem *could* be in the OS security updates, or maybe something about 2.16 itself. I haven't tried re-installing an older Calibre release. I assume that option is still available.

Ideas?

Thanks

kovidgoyal · 01-18-2015, 09:44 PM

Run

calibre-debug -g

Though your issues are almost certainly OS related. I suggest deleting that directory in /var/tmp that KDE is complaining about.

signum · 01-18-2015, 10:45 PM

@Kovid

Thank you for your quick and accurate reply. I think it's fixed now. I noticed that other programs were behaving strangely, so I did a cold boot into safe mode, ran "fsck" across all disk filesystems, continued with a "normal" boot, and, amazingly, everything started working right. A couple of programs were taking longer than usual to start up, but they eventually started. I'm guessing they were repairing (or rebuilding) some disk damage that fsck couldn't handle.

I hadn't seen any evidence of hardware failure before.

01-18-2015, 01:55 PM	#1
signum Zealot Posts: 119 Karma: 64428 Join Date: Aug 2011 Device: none	Calibre 2.16 install failure OS: Kubuntu 12.04 Calibre: trying to install 2.16 This morning I updated my Kubuntu with the latest patches. Nothing seemed out of order. Among other things, the updates replaced the kernel, Firefox, Flash and several ssl/ssh modules. Re-booted as required and attempted to install the latest Calibre. The install seemed to go OK, but when I tried to try it out by typing "calibre" from the CLI, it returned a command prompt and then: ---------- kbuildsycoca4 running... Error: "/var/tmp/kdecache-xxxxxxxx" is owned by uid 1000 instead of uid 0 ---------- where xxxxxxxx is my login name and 1000 is the uid of xxxxxxxx. At this point it hung. No disk light flashing, no cpu time being run up as reported by "top," no new command prompt. I had to ^c to get out of it. Attempts to download again, remove the old install, etc., all wound up with about the same result. I don't know where the error truly lies, or what to do next. The problem could be in the OS security updates, or maybe something about 2.16 itself. I haven't tried re-installing an older Calibre release. I assume that option is still available. Ideas? Thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PRS-505 PRS+ Install Failure	ElsieC	Sony Reader Dev Corner	9	03-08-2012 02:13 PM
Windows 7 Install Failure	drneals	Calibre	1	08-14-2010 04:54 PM
Calibre launch failure	marcaronson408	Calibre	4	07-23-2010 08:43 PM
calibre and windows 7 failure	ibm650	Calibre	10	07-23-2009 07:38 PM
calibre failure to install	whymany	Calibre	3	10-03-2008 09:04 PM

01-18-2015, 09:44 PM	#2
kovidgoyal creator of calibre Posts: 45,160 Karma: 27110894 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Run calibre-debug -g Though your issues are almost certainly OS related. I suggest deleting that directory in /var/tmp that KDE is complaining about.

01-18-2015, 10:45 PM	#3
signum Zealot Posts: 119 Karma: 64428 Join Date: Aug 2011 Device: none	@Kovid Thank you for your quick and accurate reply. I think it's fixed now. I noticed that other programs were behaving strangely, so I did a cold boot into safe mode, ran "fsck" across all disk filesystems, continued with a "normal" boot, and, amazingly, everything started working right. A couple of programs were taking longer than usual to start up, but they eventually started. I'm guessing they were repairing (or rebuilding) some disk damage that fsck couldn't handle. I hadn't seen any evidence of hardware failure before.

Advert