'Indicator Applet Complete' keeps crashing after boot up
- Inicie sesión ou rexístrese para enviar comentarios
Hi there,
I have recently repaired my file system (/dev/mapper/vgtrisquel-home) using fsck, and although it's great to use my OS and access my HD again, there is however one or two annoying 'bugs' that I'd really like to fix.
The first issue is that my 'Indicator Applet Complete' crashes when I enter the desktop. This can be overcome with a simple click on the 'Reload' button, but it would be great to not have to do this everything single time I open the desktop.
The second, my shortcuts thumbnails are no longer displaying my own customized thumbnail pics (only one remains for some reason). I thought I could've simple re-selected the images I've used, but it not changing the boring old 'blue folders' icons that you can see.
Thirdly and finally, I always like to place my shortcuts in specific location around the desktop top, and although I can simply move them back to where I'd prefer them to be, it will always return to the 'messy' default position as soon as I reboot the device.
This isn't a huge issue in terms of practicality, I'm just glad to be able to use my laptop normally again, but I would very much prefer to get this fixed somehow.
Any advice and help would be well appreciated.
Thank you
Mike
| Anexo | Tamaño |
|---|---|
| Indicator 'Applet Complete 'quit on me.png | 1.09 MB |
Try to apply all the pending updates, you might be missing some.
I've already tried updating and upgrading, but I still get the same results.
After an unclean shutdown (aka, accidentally pulling the plug out), it did behave this way to before I restarted the system (hoping that it would fix this issue) and then I had the damaged file system problem that I have recently overcome.
I believe a a certain file system has been damaged and still is damaged which is causing the desktop to behave in this way, but I just don't know what.
I've checked all the current filesystems and they all appear to be clean (although, sda2 doesn't state it's clean but it doesn't state it has any issues).
>I believe a a certain file system has been damaged and still is damaged which is causing the desktop to behave in this way
Hmm, that may be possible.
Just to be sure, whats the output of:
cat /etc/apt/sources.list
user@device:~$ cat /etc/apt/sources.list
# deb cdrom:[Trisquel 11.0 _aramo_ - Release amd64 (20230315)]/ aramo main
# Trisquel repositories for supported software and updates
deb https://archive.trisquel.org/trisquel/ aramo main
deb-src https://archive.trisquel.org/trisquel/ aramo main
deb https://archive.trisquel.org/trisquel/ aramo-security main
deb-src https://archive.trisquel.org/trisquel/ aramo-security main
deb https://archive.trisquel.org/trisquel/ aramo-updates main
deb-src https://archive.trisquel.org/trisquel/ aramo-updates main
# deb https://archive.trisquel.org/trisquel/ aramo-backports main
# deb-src https://archive.trisquel.org/trisquel/ aramo-backports main
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
Should I remove the # from the aramo-backports mains?
This seems right,
# deb cdrom:[Trisquel 11.0 _aramo_ - Release amd64 (20230315)]/ aramo main
# Trisquel repositories for supported software and updates
deb https://archive.trisquel.org/trisquel/ aramo main
deb-src https://archive.trisquel.org/trisquel/ aramo main
deb https://archive.trisquel.org/trisquel/ aramo-security main
deb-src https://archive.trisquel.org/trisquel/ aramo-security main
deb https://archive.trisquel.org/trisquel/ aramo-updates main
deb-src https://archive.trisquel.org/trisquel/ aramo-updates main
# deb https://archive.trisquel.org/trisquel/ aramo-backports main
# deb-src https://archive.trisquel.org/trisquel/ aramo-backports main
You might like to use gnome-disks to run some SMART tests, and find out if some sectors might be failing.
Like you mention, it is possible that filesystem might be damaged and you get this issues out of it. If the HDD already show a large amount of damaged sectors I wonder if a (re)installation would help.
Regards.
