Hi, since a long time, i have nautillus freeze, perhaps when there is network share mounted. Today, i think it was freeze, but in fact, the context menu was very long to be displayed. when closing nautillus, i got a kernel: traps, i will provide journalctl output. I have nautillus action from github.
Created attachment 14530 [details] journalctl output
CC: (none) => surfzoid
(In reply to Eric Petit from comment #0) > Today, the context menu was very long to > be displayed. > > I have nautillus action from github. Are these two pints related ? nautillus 'action' defining the context menu ? Is your Nautilus as Mageia provides, or extended from github?
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #2) > (In reply to Eric Petit from comment #0) > > Today, the context menu was very long to > > be displayed. > > > > I have nautillus action from github. > > Are these two pints related ? nautillus 'action' defining the context menu ? > Is your Nautilus as Mageia provides, or extended from github? i don't know how 'action' is integrated in the menu, it is python script like shell extensions, here https://github.com/bassmanitram/actions-for-nautilus . Nautilus is mageia 9 one
Thank you for that pointer. "actions-for-nautilus" "An extension to the Gnome "Files" file manager that allows you to add arbitrary actions to the file selection context menu " As I suspected, which explains the very long context menu. We do not have it. Install Dependencies it relies on python 3+, nautilus-python, and certain process management tools (which are likely already installed but just in case :)). Fedora: nautilus-python python3-gobject procps-ng js-jquery We offer all 4 pkgs, which presumably you have. Did you follow the "Download & Install the Extension" instructions (make install)? The next thing to try is to UNinstall the extension as described on the same page "Uninstallation", to test whether that changes anything - other than reducing the context menu!
In fact, it is not often, for exemple, yesterday only one time contexte menu was slow. The most often it was a freeze of nautjlus. With MGA8, there was nautilus action in rpm's list. I tried to watch journalct -f, run nautilus in console, but nothing when or just before it freeze. I don't remembrer if i installed or just copied files, sincerely i prefer keep it, because the new version of gnome nautilus do not have refresh anymore, just F5 key and have issu, probably mime type issu. Evry days i watch and manage video from security cams and need those previous feature
sorry i didn't reread , about mime type, nautilus do not start default app, QtVsPlayer to read the videos files, but occasionally, it read !
Created attachment 14531 [details] sudo journalctl |grep -i "kernel: traps"> /tmp/kernel.trap This is what i should did in first.
Eric, you are missing the point. Please re-read, and reply to, comment 4. Your comments are not clear; if you prefer to write in French, ça va. It looks possible that your problems come from having added 'actions-for-nautilus' (from git) to Nautilus. It is important to remove this from your system (then perhaps un-install & re-install Nautilus) to see whether you still have problems. If I understand correctly, you *need* the extra functions provided by this extension; you would have to live without them short-term. (In reply to Eric Petit from comment #5) > Every day I > watch and manage video from security cams and need those previous features We need to consider what to do.
Hello, i will do it, but freeze are more and more rare. I remember also, i remove the gnome-console.
Hi, Nautilus action removed. Context menu took more than one minute to be displayed. log attached and see also another bug i reported whose come back.
Created attachment 14535 [details] log
There is something strange, like i got two diferents nautilus, one is open from the menu or dock, other by dropbox new file notif. see screenshots
Created attachment 14537 [details] With dropbox
Created attachment 14538 [details] without dropbox
(In reply to Eric Petit from comment #10) > Nautilus action removed. > log attached and see also another bug i reported whose come back. The log looks more relevant to the other dbus bug. Thank you for removing 'actions-for-nautilus'; it did not look easy. (In reply to Eric Petit from comment #12) > There is something strange, like i got two diferents nautilus, one is open > from the menu or dock, other by dropbox new file notif. It is likely that nautilus is being launched differently to show different displays. List the nautilus packages you have: $ rpm -qa | grep nautilus | sort Try UNinstalling Nautilus, and repeat the list. (If it looks that it would take too much with it, try: # rpm -e --nodeps nautilus ) Then check what nautilus packages you now have. Then re-install it, and re-show nautilus packages. It might be sensible to logout/login before trying it again. All this is to try and start with a clean nautilus installation.
(In reply to Lewis Smith from comment #15) > (In reply to Eric Petit from comment #10) > > Nautilus action removed. > > log attached and see also another bug i reported whose come back. > The log looks more relevant to the other dbus bug. > Thank you for removing 'actions-for-nautilus'; it did not look easy. > > (In reply to Eric Petit from comment #12) > > There is something strange, like i got two diferents nautilus, one is open > > from the menu or dock, other by dropbox new file notif. > It is likely that nautilus is being launched differently to show different > displays. > > List the nautilus packages you have: > $ rpm -qa | grep nautilus | sort > Try UNinstalling Nautilus, and repeat the list. > (If it looks that it would take too much with it, try: > # rpm -e --nodeps nautilus > ) > Then check what nautilus packages you now have. > Then re-install it, and re-show nautilus packages. > It might be sensible to logout/login before trying it again. > All this is to try and start with a clean nautilus installation. i already did urpmi --replacepkgs --replacefiles nautilus isn't enough? humm, a new error : rpm -qa | grep nautilus | sort erreur : rpmdbNextIterator : ignoré h# 3141 Entête SHA256 digest: BAD (Expected 5a725dee54d37e5055164c65b745d57dd40f4cbb0101230709291880de0701e5 != aef3bc10c02d667ed3ef689932f6a6e5cc441948a3c9cdf5d22ee374708bacae) Entête SHA1 digest: BAD (Expected 945fd7ef92c2da687af8d412e752d70b5daaf2c3 != 54b35ab5f19f8fc355102ae9f4e115294ee8814b) folder-color-extensions-nautilus-0.2.7-5.mga9 gnome-terminal-nautilus-3.48.1-1.mga9 lib64nautilus4-44.2.1-1.mga9 lib64nautilus-gir4.0-44.2.1-1.mga9 nautilus-44.2.1-1.mga9 nautilus-dropbox-2024.01.22-1.mga9.nonfree nautilus-python-4.0-1.mga9 nautilus-sendto-3.8.6-5.mga9 eric@SurfzoidPC:~:[0]$ rpm -qa | grep nautilus lib64nautilus4-44.2.1-1.mga9 nautilus-sendto-3.8.6-5.mga9 gnome-terminal-nautilus-3.48.1-1.mga9 erreur : rpmdbNextIterator : ignoré h# 3141 Entête SHA256 digest: BAD (Expected 5a725dee54d37e5055164c65b745d57dd40f4cbb0101230709291880de0701e5 != aef3bc10c02d667ed3ef689932f6a6e5cc441948a3c9cdf5d22ee374708bacae) Entête SHA1 digest: BAD (Expected 945fd7ef92c2da687af8d412e752d70b5daaf2c3 != 54b35ab5f19f8fc355102ae9f4e115294ee8814b) nautilus-python-4.0-1.mga9 lib64nautilus-gir4.0-44.2.1-1.mga9 folder-color-extensions-nautilus-0.2.7-5.mga9 nautilus-dropbox-2024.01.22-1.mga9.nonfree nautilus-44.2.1-1.mga9
Just in cas urpme lib64nautilus4 urpme --auto-orphans Pour satisfaire les dépendances, les 4 paquetages suivants vont être désinstallés (1.7Mo): (paquetages orphelins) gnome-directory-thumbnailer-0.1.11-5.mga9.x86_64 gvfs-google-1.50.4-1.mga9.x86_64 lib64gdata22-0.18.1-5.mga9.x86_64 libgdata-i18n-0.18.1-5.mga9.noarch Supprimer 4 paquetages ? (o/N) o rpm -qa | grep nautilus | sort erreur : rpmdbNextIterator : ignoré h# 3141 Entête SHA256 digest: BAD (Expected 5a725dee54d37e5055164c65b745d57dd40f4cbb0101230709291880de0701e5 != aef3bc10c02d667ed3ef689932f6a6e5cc441948a3c9cdf5d22ee374708bacae) Entête SHA1 digest: BAD (Expected 945fd7ef92c2da687af8d412e752d70b5daaf2c3 != 54b35ab5f19f8fc355102ae9f4e115294ee8814b) eric@SurfzoidPC:~:[0]$ urpmi gvfs-google libgdata-i18n lib64gdata22 folder-color-extensions-nautilus gnome-terminal-nautilus Marque lib64gdata22 comme étant manuellement installé, il ne sera pas considéré comme un paquet orphelin Marque gvfs-google comme étant manuellement installé, il ne sera pas considéré comme un paquet orphelin writing /var/lib/rpm/installed-through-deps.list Pour satisfaire les dépendances, les paquetages suivants vont être installés : Paquetage Version Révision Arch (média « Core Release ») folder-color-extensions-nauti> 0.2.7 5.mga9 noarch gnome-directory-thumbnailer 0.1.11 5.mga9 x86_64 (recommandé) gnome-terminal-nautilus 3.48.1 1.mga9 x86_64 gvfs-google 1.50.4 1.mga9 x86_64 lib64gdata22 0.18.1 5.mga9 x86_64 lib64nautilus-gir4.0 44.2.1 1.mga9 x86_64 lib64nautilus4 44.2.1 1.mga9 x86_64 libgdata-i18n 0.18.1 5.mga9 noarch nautilus 44.2.1 1.mga9 x86_64 nautilus-python 4.0 1.mga9 x86_64 un espace additionnel de 15Mo sera utilisé. 2.9Mo de paquets seront récupérés. Procéder à l'installation des 10 paquetages ? (O/n) o Delta of 2 rpms!
Comment 16,17 show something is wrong with your RPMs: all those errors reported by 'rpm -qa'. (In reply to Eric Petit from comment #16) > i already did > urpmi --replacepkgs --replacefiles nautilus > isn't enough? It is not what I would do to start with a clean Nautilus setup. I suggested: - removing it - remove anything 'nautilus' in $HOME (esp .config/nautilus/) ; I forgot to suggest this. - # urpmi --clean [I forgot this, too; clears the pkg cache] - re-install it. FWIW my own system has just: gnome-terminal-nautilus-3.48.1-1.mga9 lib64nautilus4-44.2.1-1.mga9 nautilus-44.2.1-1.mga9 and these are all possible pkgs, ignoring dependencies: folder-color-extensions-nautilus gnome-terminal-nautilus kdeconnect-kde-nautilus lib64nautilus-devel lib64nautilus-gir4.0 lib64nautilus4 nautilus nautilus-dropbox nautilus-python nautilus-sendto nextcloud-client-nautilus nitroshare-nautilus seahorse-nautilus tortoisehg-nautilus tuncel-nautilus tuncel-nautilus-data wezterm-nautilus CC'ing DaveH who might have a suggestion about those pkg digest errors in c16 c17. (In reply to Eric Petit from comment #17) > Delta of 2 rpms! Please explain what you mean!
CC: (none) => davidwhodgins
Sorry, i canot waste so many time by removing my nautilus conf, it is not a test computer, i have another one PC with MGA8 with a similar conf, nautilus work very fine on it. I guess rpm error came after installing the test rpm, what can i do to solve this error?
Answering myself rpm --rebuilddb solved issue.
Thank you. Are you happy now that Nautilus works correctly?
The "urpmi --clean" would likely have been enough to clear it. The bad digest indicates the rpm package is been corrupted. That can happen when there's a corrupt file on the main mirror (in which case everyone who installs the package will see it), or when a there is an error while the mirror syncs from the main or another mirror (in which case everyone using that mirror will see it, or as is usually the case, when something went wrong during the downloading of the rpm file from the mirror by the system that then ends up with the bad digest errors. Most of the time the error is caused by a download being interrupted, leaving a partial file in /var/cache/urpmi/rpms. The "urpmi --clean" command just deletes any files from that directory. That option is not done automatically as people who pay money per gb downloaded don't want to repeatedly download a file if the copy on the mirror is corrupt. Alternatively, the rpm file download can be continued from where it stopped by using urpmi with the --resume option. The resume will fail too though, if the file was actually corrupted by the interruption rather then truncated, or the copy on the mirror is bad.
Thank you dave to remember me urpmi --clean , i did a rm -f /var/cache/urpmi/rpms/* and rm -f /var/cache/urpmi/partial/* It is not the clean way, but it the error was here. rebuilddb worked
(In reply to Lewis Smith from comment #21) > Thank you. Are you happy now that Nautilus works correctly? ?!?
(In reply to Eric Petit from comment #24) > (In reply to Lewis Smith from comment #21) > > Thank you. Are you happy now that Nautilus works correctly? > ?!? Etes-vous maintenant satisfait que Nautilus fonctionne correctement? (In reply to Eric Petit from comment #20) > rpm --rebuilddb > solved issue. Le bug, est-il resolu? Pouvons-nous le fermer?
(In reply to Lewis Smith from comment #25) > (In reply to Eric Petit from comment #24) > > (In reply to Lewis Smith from comment #21) > > > Thank you. Are you happy now that Nautilus works correctly? > > ?!? > Etes-vous maintenant satisfait que Nautilus fonctionne correctement? > > (In reply to Eric Petit from comment #20) > > rpm --rebuilddb > > solved issue. > Le bug, est-il resolu? Pouvons-nous le fermer? "rpm --rebuilddb solved issue." of errors reported by 'rpm -qa'.!
Thanks for the clarification. So Nautilus is still behaving badly - context menu very slow to show - even without the "actions-for-nautilus" extension. I have just tried Nautilus & its basic context menu, no problem. Recap: these seems to be the pkgs (not including their dependencies) that allow it to function: gnome-terminal-nautilus-3.48.1-1.mga9 lib64nautilus4-44.2.1-1.mga9 nautilus-44.2.1-1.mga9 Could it be the presence of an additional Nautilus package causing the problem? Your original list in comment 16 was corrupt. Can you re-post it? I wonder now whether Bug 33226 is behind this; you have here the same "JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get".
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=33226