Bug 10117 - Places opens Audacious instead of Nautilus in Gnome 3 fallback mode
Summary: Places opens Audacious instead of Nautilus in Gnome 3 fallback mode
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Götz Waschk
QA Contact:
URL:
Whiteboard: MGA4TOO
Keywords: Junior_job, PATCH, Triaged
: 7802 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-16 00:38 CEST by Ezequiel Partida
Modified: 2018-10-17 11:06 CEST (History)
2 users (show)

See Also:
Source RPM: audacious
CVE:
Status comment:


Attachments

Description Ezequiel Partida 2013-05-16 00:38:34 CEST
Places opens Audacious instead of Nautilus in Gnome 3 fallback mode.

If I insert a usb-stick it will also open Audacious instead of nautilus to list files.

I was able to fix it by editing /usr/local/share/applications/mimeinfo.cache and adding the next line at the end.

x-directory/normal=nautilis.desktop;

I just guess you might wanted to know. ;-)

I think this should be fixed. :-)

Regards
Comment 1 Manuel Hiebel 2013-07-12 18:17:16 CEST
*** Bug 7802 has been marked as a duplicate of this bug. ***

CC: (none) => goetz.waschk

Comment 2 Manuel Hiebel 2013-07-12 18:17:40 CEST
dup

Keywords: (none) => Junior_job, PATCH, Triaged
Assignee: bugsquad => goetz.waschk
Source RPM: (none) => audacious

Comment 3 Renato Dali 2015-04-08 05:26:23 CEST
I had the same problem, but with KDE. I inserted a usb hd and instead of Dolphin, Audacious was opened.

On April 6th, 2015, I noticed Audacious somehow became the first option is KDE's System Settings / File associations in both inode/directory and inode/mount-point (in Mageia 4). After I moved Audacious downwards everything got normal again.

I remember testing some hours earlier a MMS card (a kind of flash memory card) and that it opened with Dolphin; I surely used that PC several times with pen drives, too.

I can only imagine this is due some update I did recently, though I'm not able to say which would be responsible for that change:

Just for the record, these are my recent rpm logs:

[root@localhost log]# pwd
/var/log
[root@localhost log]# ls -l
total 2360
...
-rw-r--r-- 1 root  root             94164 Abr  7 08:10 rpmpkgs
-rw-r--r-- 1 root  root             94164 Abr  5 09:38 rpmpkgs.1
-rw-r--r-- 1 root  root             21318 Mar 28 11:07 rpmpkgs.2.gz
-rw-r--r-- 1 root  root             21313 Mar 21 13:13 rpmpkgs.3.gz
-rw-r--r-- 1 root  root             21281 Mar 15 10:17 rpmpkgs.4.gz
...

I have no idea why there's no logs prior to that (maybe some auto-cleaning?). There's another log of Jan 16.

Anyway, look at these diffs:

[root@localhost log]# diff --side-by-side --suppress-common-lines rpmpkgs rpmpkgs.1                                                                                                                                                    
mate-file-manager-1.6.3-1.2.mga4.i586.rpm                     | mate-file-manager-1.6.3-1.1.mga4.i586.rpm

And after doing a backup of said files to a rpmtest directory,

[root@localhost rpmtests]# gunzip rpmpkgs.2.gz                                                                                                                                                                                         
[root@localhost rpmtests]# ls                                                                                                                                                                                                          
rpmpkgs  rpmpkgs.1  rpmpkgs.2  rpmpkgs.3.gz  rpmpkgs.4.gz                                                                                                                                                                              
[root@localhost rpmtests]# diff --side-by-side --suppress-common-lines rpmpkgs rpmpkgs.2
chromium-browser-41.0.2272.101-1.mga4.i586.rpm                | chromium-browser-40.0.2214.111-1.mga4.i586.rpm                                                                                                                         
chromium-browser-stable-41.0.2272.101-1.mga4.i586.rpm         | chromium-browser-stable-40.0.2214.111-1.mga4.i586.rpm                                                                                                                  
cups-filters-1.0.53-1.1.mga4.i586.rpm                         | cups-filters-1.0.53-1.mga4.i586.rpm                                                                                                                                    
firefox-31.6.0-1.mga4.i586.rpm                                | firefox-31.5.3-1.mga4.i586.rpm                                                                                                                                         
firefox-pt_BR-31.6.0-1.mga4.noarch.rpm                        | firefox-pt_BR-31.5.3-1.mga4.noarch.rpm                                                                                                                                 
firefox-pt_PT-31.6.0-1.mga4.noarch.rpm                        | firefox-pt_PT-31.5.3-1.mga4.noarch.rpm                                                                                                                                 
kde-l10n-handbooks-pt_BR-4.12.5-1.mga4.noarch.rpm             <                                                                                                                                                                        
libcups-filters1-1.0.53-1.1.mga4.i586.rpm                     | libcups-filters1-1.0.53-1.mga4.i586.rpm                                                                                                                                
libmariadb-embedded18-5.5.42-1.mga4.i586.rpm                  | libmariadb-embedded18-5.5.41-1.mga4.i586.rpm                                                                                                                           
libmariadb18-5.5.42-1.mga4.i586.rpm                           | libmariadb18-5.5.41-1.mga4.i586.rpm                                                                                                                                    
libnss3-3.18.0-1.1.mga4.i586.rpm                              | libnss3-3.18.0-1.mga4.i586.rpm                                                                                                                                         
librpm3-4.11.1-9.1.mga4.i586.rpm                              | librpm3-4.11.1-9.mga4.i586.rpm                                                                                                                                         
librpmbuild3-4.11.1-9.1.mga4.i586.rpm                         | librpmbuild3-4.11.1-9.mga4.i586.rpm                                                                                                                                    
librpmsign3-4.11.1-9.1.mga4.i586.rpm                          | librpmsign3-4.11.1-9.mga4.i586.rpm                                                                                                                                     
libtasn1_6-3.6-1.1.mga4.i586.rpm                              | libtasn1_6-3.6-1.mga4.i586.rpm                                                                                                                                         
libzeitgeist1.0_1-0.3.18-3.mga4.i586.rpm                      <                                                                                                                                                                        
libzip2-0.11.2-1.1.mga4.i586.rpm                              | libzip2-0.11.2-1.mga4.i586.rpm                                                                                                                                         
mariadb-client-5.5.42-1.mga4.i586.rpm                         | mariadb-client-5.5.41-1.mga4.i586.rpm                                                                                                                                  
mariadb-common-5.5.42-1.mga4.i586.rpm                         | mariadb-common-5.5.41-1.mga4.i586.rpm                                                                                                                                  
mariadb-common-core-5.5.42-1.mga4.i586.rpm                    | mariadb-common-core-5.5.41-1.mga4.i586.rpm                                                                                                                             
mariadb-core-5.5.42-1.mga4.i586.rpm                           | mariadb-core-5.5.41-1.mga4.i586.rpm                                                                                                                                    
mate-file-manager-1.6.3-1.2.mga4.i586.rpm                     | mate-file-manager-1.6.3-1.1.mga4.i586.rpm                                                                                                                              
midori-0.5.5-2.mga4.i586.rpm                                  <                                                                                                                                                                        
nss-3.18.0-1.1.mga4.i586.rpm                                  | nss-3.18.0-1.mga4.i586.rpm
python-rpm-4.11.1-9.1.mga4.i586.rpm                           | python-rpm-4.11.1-9.mga4.i586.rpm
rootcerts-20150326.00-1.mga4.i586.rpm                         | rootcerts-20150226.00-1.mga4.i586.rpm
rootcerts-java-20150326.00-1.mga4.i586.rpm                    | rootcerts-java-20150226.00-1.mga4.i586.rpm
rpm-4.11.1-9.1.mga4.i586.rpm                                  | rpm-4.11.1-9.mga4.i586.rpm
rpm-build-4.11.1-9.1.mga4.i586.rpm                            | rpm-build-4.11.1-9.mga4.i586.rpm
[root@localhost rpmtests

I also added the keyword MGA4TOO because it happened in Mageia 4.

CC: (none) => mkare
Whiteboard: (none) => MGA4TOO

Comment 4 Renato Dali 2015-04-08 05:30:40 CEST
Sorry to be not able to provide better information other than "it happened".
Comment 5 Ezequiel Partida 2018-10-17 11:06:47 CEST
This seems to be fixed since Mageia 6.

I will close it if there's no problem with it.

Regards

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.