[Nepomuk] Nepomuk linked to shutdown problems and file system corruption in Ubuntu (was Fwd: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

[Tim Josling]

I'm not sure the mechanism, but I can assure you that on next boot-up
the system typically does actually report file system corruption.
Though so far I have not lost any data that I know of.

The problem does still occur if the user waits patiently for the time-out.

Tim Josling

On Tue, Feb 12, 2013 at 4:44 PM, Simeon Bird <bladud at gmail.com> wrote:
> Thanks. See also KDE bug https://bugs.kde.org/show_bug.cgi?id=303287
>
> "File system corruption" is a little extreme though - from the bug report it
> seems that the user was just impatient and hit reset before the drive
> unmounted. It may still be a real bug needing fixing though. I asked
> something in the launchpad.
>
>
> On 11 February 2013 17:15, Tim Josling <tim.josling at gmail.com> wrote:
>>
>> Just to let you know that the word is out that to prevent file system
>> corruption in Ubuntu, you need to turn off nepomuk. See below. The
>> problem is triggered if you use Kalarm, even if you shut Kalarm down,
>> nepomuk stays alive and seems to prevent file systems from being
>> unmounted on shutdown.
>>
>> Thought you guys might be interested.
>>
>> Tim Josling
>>
>> ---------- Forwarded message ----------
>> From: Nelly <1053783 at bugs.launchpad.net>
>> Date: Mon, Feb 11, 2013 at 8:32 PM
>> Subject: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after
>> having had KAlarm opened; with package info.
>> To: tim.josling at gmail.com
>>
>>
>> I also have this bug.
>> I use KAlarm and my computer with Ubuntu 12.04 (Gnome desktop) took
>> several minutes to shutdown.
>>
>> Link http://ubuntuforums.org/showthread.php?t=1764048 gave me the hint
>> how to solve this problem. This link contains methods to prevent te
>> starting up of nepomuk and akonadi in 3 steps.
>> If you don't want to use KAlarm, it might be safe to apply all three
>> steps. However, doing so, KAlarm could not be used. It asked to
>> start-up akonadi first. So I tried what would happen if I only used
>> the two steps preventing the (complete) start-up of nepomuk, and that
>> worked great. KAlarm works and Ubuntu 12.04 shuts down within a few
>> seconds. The steps to apply are:
>>
>> 1. Add the following lines to ~/.kde/share/config/nepomukserverrc (and
>> their sections if they don't exist) (change the value from "true" to
>> "false" if they do exist and are set on "true";
>>
>> [Basic Settings]
>> Start Nepomuk=false
>>
>> [Service-nepomukmigration1]
>> autostart=false
>>
>> [Service-nepomukstrigiservice]
>> autostart=false
>>
>> 2. Remove the file /usr/share/autostart/nepomukcontroller.desktop, if it
>> exists.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1053783
>>
>> Title:
>>   Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with
>>   package info.
>>
>> Status in “gnome-session” package in Ubuntu:
>>   Confirmed
>>
>> Bug description:
>>   In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes -
>> but only on occasions when I have opened - and then quit - KAlarm.
>>   A window pops up Stating that, 'A Program is still running'; Unknown
>> (not responding); and, there are 3 buttons to choose: 'Lock Screen',
>> 'Cancel' and 'Shutdown Anyway'.
>>
>>   Initial report was Bug #1053779 but had no package information.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 12.04
>>   Package: gnome-session-bin 3.2.1-0ubuntu8
>>   ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
>>   Uname: Linux 3.2.0-30-generic-pae i686
>>   NonfreeKernelModules: nvidia
>>   ApportVersion: 2.0.1-0ubuntu13
>>   Architecture: i386
>>   Date: Fri Sep 21 13:22:35 2012
>>   ExecutablePath: /usr/bin/gnome-session
>>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release
>> i386 (20120423)
>>   ProcEnviron:
>>    LANGUAGE=en_AU:en
>>    PATH=(custom, no user)
>>    LANG=en_AU.UTF-8
>>    SHELL=/bin/bash
>>   SourcePackage: gnome-session
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions
>> _______________________________________________
>> Nepomuk mailing list
>> Nepomuk at kde.org
>> https://mail.kde.org/mailman/listinfo/nepomuk
>
>