Description of problem: Upon finishing of a downloaded File or anything in the Downloads menu. If I click on the open containing folder option in firefox, spe is launched. Just weird behaviour. Version-Release number of selected component (if applicable): firefox-21.0-3.fc18.x86_64 spe-0.8.4.h-12.fc18.noarch How reproducible: well it happens on my machine Steps to Reproduce: 1. Install both packages 2. Open Firefox and download Something 3. Once download has finished click the green Arrow in the top right corner 4. to the right of the file you downloaded click the folder arrow Actual results: spe is opened Expected results: folder where downloaded file should be opened Additional info: Possibly a bug in spe package, once spe is removed the bug disappears
I can't reproduce this, does it matter what type of file is downloaded?
I am using lxde desktop, it happens on my computer with xfce and lxde all types it's almost like firefox is using spe as the file manager for downloads
Does it happen under GNOME or KDE?
I tend not to install Gnome or KDE on my machines. I tried a gdb on firefox-bin but it didn't say much cept that spe was started, at the same time I hit the folder icon in downloads section of firefox. This is puzzling
Does it happen with Seamonkey or Konqueror?
It happens in: seamonkey midori firefox not in: konqueror opera I would speculate, but might be off. It might be something in gtk or a setting in either application that uses spe as the default folder opener for downloads. Is there a way i could get all the calls from firefox seamonkey or midori It is only when i right-click and select open parent folder. This is the debug option midori has ------------------------------------------------------------------------------- [myusername@localhost ~]$ midori -d (midori4:3526): GLib-GIO-CRITICAL **: g_file_get_parent: assertion `G_IS_FILE (file)' failed (midori4:3526): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed ** (midori4:3526): CRITICAL **: void webkit_download_start(WebKitDownload*): assertion `priv->timer == NULL' failed SPE v0.8.4.h (c)2003-2008 www.stani.be If spe fails to start: - type "python SPE.py --debug > debug.txt 2>&1" at the command prompt (or if you use tcsh: "python SPE.py --debug >& debug.txt") - send debug.txt with some info to spe.stani.be[at]gmail.com Blender support disabled (run SPE inside Blender to enable). Encrypted debugging enabled. Launching application... ------------------------------------------------------------------------------- weird huh
I'm going to reassign this to glib2, since I *think* that's what's failing. glib2 maintainers, please let me know if there's more I can do.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.