next boot after using fslint X fails to start

Bug #1184488 reported by Erike Magegere
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fslint (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

^^ This is a kubuntu problem ***
I used fslint to clean up some of my 1000's of pictures. On the next boot the desktop (two monitors) was black and the toolbars did not exist. I hav a many boot system 13.04 (3.8.0-22,21,&19), 12.10(3.5.0-28) & a fresh 13.04(3.8.0-19). it fails on all as I have a separate home partition. System recover was done by copying all the hidden files from a spare 13.04 system. On the latest incident i only restored .kde .kde4 and from .config eveolution, kde.org and natulius and the desktop came back.

Revision history for this message
Pádraig Brady (p-draigbrady) wrote :

Did you clean those pictures by deletion?
I suspect you selected a "dotfile" for deletion in error

Revision history for this message
Erike Magegere (erike4) wrote : Re: [Bug 1184488] Re: next boot after using fslint X fails to start

all my pictures are on a different drive. I thought the same thing as
fslint starts with home/eric (ny directory). So i was very careful to
start by deleting that file from the scan area. but when I rebooted x
failed again. Is there some way I can since I have narrowed the "bad" dot
or config file down to f files/directories can you give me the command for
a diff and I can fry the system and see what has been clobbered.

On 27 May 2013 08:11, Pádraig Brady <email address hidden> wrote:

> Did you clean those pictures by deletion?
> I suspect you selected a "dotfile" for deletion in error
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1184488
>
> Title:
> next boot after using fslint X fails to start
>
> Status in “fslint” package in Ubuntu:
> New
>
> Bug description:
> ^^ This is a kubuntu problem ***
> I used fslint to clean up some of my 1000's of pictures. On the next
> boot the desktop (two monitors) was black and the toolbars did not exist.
> I hav a many boot system 13.04 (3.8.0-22,21,&19), 12.10(3.5.0-28) & a
> fresh 13.04(3.8.0-19). it fails on all as I have a separate home
> partition. System recover was done by copying all the hidden files from a
> spare 13.04 system. On the latest incident i only restored .kde .kde4 and
> from .config eveolution, kde.org and natulius and the desktop came back.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/fslint/+bug/1184488/+subscriptions
>

Revision history for this message
Pádraig Brady (p-draigbrady) wrote :

Well if you wanted to compare dotfiles in 2 dirs you could:

diff <(ls -1d ~/.* | sort) <(ls -1d backup/.* | sort)

When fslint runs you can also auto deselect all files in /home/....
using the selection functions. Or you could select those
to and scan the list to see if fslint has selecte/highlighted anything you didn't expect

Revision history for this message
Erike Magegere (erike4) wrote :

Pádraig Thank you for your help. I made a home partition in a spare
partition
and which contained all the . files and .directories. and mounted it with
fstab.
After a reboot Dropbox tried to come up and complained as the dropbox file
was not there and i noticed that the modem light was not on meaning there
*was none of the normal internet traffic on start-up. i did not go further
in verifying*
*the system ran as I wanted a clean xsession-error file to look at.*

BUT

FSlint worked ok. I will try again when i have time on my production home
*directory. So I am sorry, but it appears the problem is not reproducible *
*in a **test *environment.

On 27 May 2013 10:25, Pádraig Brady <email address hidden> wrote:

> Well if you wanted to compare dotfiles in 2 dirs you could:
>
> diff <(ls -1d ~/.* | sort) <(ls -1d backup/.* | sort)
>
> When fslint runs you can also auto deselect all files in /home/....
> using the selection functions. Or you could select those
> to and scan the list to see if fslint has selecte/highlighted anything you
> didn't expect
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1184488
>
> Title:
> next boot after using fslint X fails to start
>
> Status in “fslint” package in Ubuntu:
> New
>
> Bug description:
> ^^ This is a kubuntu problem ***
> I used fslint to clean up some of my 1000's of pictures. On the next
> boot the desktop (two monitors) was black and the toolbars did not exist.
> I hav a many boot system 13.04 (3.8.0-22,21,&19), 12.10(3.5.0-28) & a
> fresh 13.04(3.8.0-19). it fails on all as I have a separate home
> partition. System recover was done by copying all the hidden files from a
> spare 13.04 system. On the latest incident i only restored .kde .kde4 and
> from .config eveolution, kde.org and natulius and the desktop came back.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/fslint/+bug/1184488/+subscriptions
>

Revision history for this message
Rolf Leggewie (r0lf) wrote :

what is the status here?

Revision history for this message
Erike Magegere (erike4) wrote :

Please close as old operating system and long time ago

Revision history for this message
Rolf Leggewie (r0lf) wrote :

closing as requested

Changed in fslint (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.