Bug 757435 - No completion because dmenu defaults command became dmenu_run
Summary: No completion because dmenu defaults command became dmenu_run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xmonad
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-27 02:32 UTC by Patrice FERLET
Modified: 2012-01-25 22:32 UTC (History)
5 users (show)

Fixed In Version: xmonad-0.10-1.fc16
Clone Of:
Environment:
Last Closed: 2012-01-25 22:32:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Call dmenu_run (1.30 KB, patch)
2011-11-28 10:22 UTC, Petr Šabata
no flags Details | Diff

Description Patrice FERLET 2011-11-27 02:32:52 UTC
Description of problem:
While demnu is drawn, typing keys have to display corresponding commands

Version-Release number of selected component (if applicable):
4.1.1-1.fc16

How reproducible:
Simply try to open demnu (I'm on Xmonad => Super+P)

Steps to Reproduce:
1. Open Xmonad session
2. Try Mod+P (mod = alt by default I guess)
3.
  
Actual results:
A simple bar... no completion

Expected results:
Have completion, as in Fedora 13,14,15...

Additional info:
Trying to lauch demnu_run on console is the expected result. So, it could be nice to change xmonad config to lauch dmenu_run on Mod+P... Or something that make all stuff working ;)

Comment 1 Petr Šabata 2011-11-28 10:19:26 UTC
(In reply to comment #0)
> (...)
> Additional info:
> Trying to lauch demnu_run on console is the expected result. So, it could be
> nice to change xmonad config to lauch dmenu_run on Mod+P... Or something that
> make all stuff working ;)

Indeed, this an xmonad bug which still calls "dmenu_path | dmenu" in its default config instead of "dmenu_run" (which has been around for quite some time now).

Comment 2 Petr Šabata 2011-11-28 10:22:27 UTC
Created attachment 537422 [details]
Call dmenu_run

This patch should fix it.  I don't know anything about xmonad, though.

Comment 3 Jens Petersen 2011-12-02 08:20:55 UTC
Thanks for reporting.

This is actually fixed in xmonad-0.10.
We should build that soon and push it to f16 also.

Comment 4 Jens Petersen 2011-12-03 07:11:04 UTC
This should be fixed in xmonad-0.10-1.fc17.

Comment 5 Fedora Update System 2012-01-05 06:19:55 UTC
xmonad-0.10-1.fc16,ghc-xmonad-contrib-0.10-1.fc16,bluetile-0.6-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/xmonad-0.10-1.fc16,ghc-xmonad-contrib-0.10-1.fc16,bluetile-0.6-1.fc16

Comment 6 Fedora Update System 2012-01-07 22:54:25 UTC
Package xmonad-0.10-1.fc16, ghc-xmonad-contrib-0.10-1.fc16, bluetile-0.6-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xmonad-0.10-1.fc16 ghc-xmonad-contrib-0.10-1.fc16 bluetile-0.6-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-0158/xmonad-0.10-1.fc16,ghc-xmonad-contrib-0.10-1.fc16,bluetile-0.6-1.fc16
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-01-25 22:32:02 UTC
xmonad-0.10-1.fc16, ghc-xmonad-contrib-0.10-1.fc16, bluetile-0.6-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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