"Show in folder" for downloads does not work

[kolen]

In almost freshly installed Ubuntu 13.10 nothing happens if "Show in folder" clicked for downloads, both clicking bottom panel dropdown menu or clicking link on chrome://downloads/.

Related: #606544, but it is old and that report says that opening files does not work too. Opening files works for me, only "show in folder" does not work.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: chromium-browser 29.0.1547.65-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Mon Oct 28 16:57:22 2013
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationDate: Installed on 2013-10-23 (5 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

[kolen (incredible-angst)]

Related: https://code.google.com/p/chromium/issues/detail?id=19987, but for "non-GNOME/KDE Ubuntu systems". I use default desktop.

Also:

kolen@kolen-ThinkPad-L412:~/items$ mimeopen ~
Please choose a default application for files of type inode/directory

 1) Files (nautilus-folder-handler)
 2) Files (nautilus)
 3) Disk Usage Analyzer (baobab)
 4) Other...

use application #

Choosing "1" works.

[Chad Miller (cmiller)]

Please close chromium, start a terminal, run "chromium-browser", reproduce bug, and attach the chromoium output in the terminal and the last few lines of "dmesg" output here.

[kolen (incredible-angst)]

$ chromium-browser
[22675:22675:1028/185426:ERROR:profile_sync_service.cc(1242)] History Delete Directives, Sync Error: Delete directives not supported with encryption.
[6:62:1028/185438:ERROR:platform_thread_linux.cc(99)] Failed to set nice value of thread to -10
[22675:22675:1028/185441:ERROR:browser_window_gtk.cc(1051)] Not implemented reached in virtual void BrowserWindowGtk::WebContentsFocused(content::WebContents*)
[22675:22675:1028/185500:ERROR:CONSOLE(1)] "Uncaught ReferenceError: downloadsList is not defined", source: (1)

"Uncaught ReferenceError: downloadsList is not defined" appeared after opening chrome://downloads/, not after clicking "Show in folder". Nothing appears in chromium output when clicking "Show in folder".

dmesg: nothing changed after running chromium-browser

[20888.623623] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[20888.682232] r8169 0000:04:00.0 eth0: link down
[20888.682258] r8169 0000:04:00.0 eth0: link down
[20888.682365] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[20890.606362] r8169 0000:04:00.0 eth0: link up
[20890.606379] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[26713.119086] Adding 4194300k swap on /swapfile. Priority:-1 extents:10 across:5005308k FS
[26824.092170] systemd-hostnamed[12636]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[28123.278896] window-stack-br[1718]: segfault at 8 ip 00007f58be001bd4 sp 00007fff3403c830 error 4 in libQt5DBus.so.5.0.2[7f58bdfd2000+73000]
[28315.432279] systemd-hostnamed[15403]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[28888.219678] systemd-hostnamed[16483]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[29460.266768] systemd-hostnamed[16753]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[31792.010104] systemd-hostnamed[17862]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[33506.204930] atkbd serio0: Unknown key pressed (translated set 2, code 0xf1 on isa0060/serio0).
[33506.204939] atkbd serio0: Use 'setkeycodes e071 <keycode>' to make it known.
[33506.216199] atkbd serio0: Unknown key released (translated set 2, code 0xf1 on isa0060/serio0).
[33506.216206] atkbd serio0: Use 'setkeycodes e071 <keycode>' to make it known.
[35493.803264] systemd-hostnamed[22118]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!

[Chad Miller (cmiller)]

Thank you!

Now, in a terminal, run these and paste results, please?

xdg-user-dir DOWNLOAD

xdg-user-dir DESKTOP

[kolen (incredible-angst)]

$ xdg-user-dir DOWNLOAD
/home/kolen/Downloads
$ xdg-user-dir DESKTOP
/home/kolen/Desktop

[Paul White (paulw2u)]

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

Do you still see a problem related to the one that you reported using currently supported versions of Ubuntu and Chromium? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

[Paul White (paulw2u)]

Bug report won't expire due to bug watch
Reporter last commented on bug nearly 6 years ago
No response to comment #7 by reporter
Issue not reproducible here with Chromium 75 so closing