#33 i3 config file error due to duplicate keybinding in fresh installation
Closed: complete a month ago by nasirhm. Opened 2 months ago by aashu23.

Summary

the fresh installation reports error in i3 config file because of $mod+d duplicate entries

Background

it is already reported upstream here
but we should patch it ourselves for better experience with fresh installation.

Details

The default config by i3-config-wizard creates duplicate keybinding for $mod+d in .config/i3/config

Those two duplicate keybindings are following (for dmenu):

  • bindsym $mod+d exec --no-startup-id dmenu_run
  • bindsym $mod+d exec --no-startup-id i3-dmenu-desktop

Outcome

no error should be displayed in fresh installation.


This is already tracked in the bugzilla ticket, no point in having that in two places.

Metadata Update from @defolos:
- Issue close_status updated to: moved
- Issue status updated to: Closed (was: Open)

2 months ago

@defolos I asked @aashu23 to open this ticket so we could track the work for the patch in the Spin itself. I viewed it as separate from the Bugzilla ticket, which I see as more specific to the i3 package itself.

Do you have any thoughts on workflow or how best to handle this? Even if we don't use Pagure for this, it is probably worth writing a doc on how people should request new features or open bugs about i3 in Fedora.

Metadata Update from @jflory7:
- Issue status updated to: Open (was: Closed)

2 months ago

Metadata Update from @jflory7:
- Issue priority set to: next meeting (was: awaiting triage)
- Issue set to the milestone: F34 – Change Completion deadline (testable)
- Issue tagged with: needs feedback, type - internal organization, type - packages

2 months ago

Justin W. Flory pagure@pagure.io writes:

jflory7 added a new comment to an issue you are following:
` @defolos I asked @aashu23 to open this ticket so we could track the work for the patch in the Spin itself. I viewed it as separate from the Bugzilla ticket, which I see as more specific to thei3` package itself.

Do you have any thoughts on workflow or how best to handle this? Even if we don't use Pagure for this, it is probably worth writing a doc on how people should request new features or open bugs about i3 in Fedora.

Everything that is specific to the i3 package belongs into Bugzilla. All
the additional stuff for the spin belongs here. That's why I also think
that this is not the right place to track i3 bugs, as we'll have the
same issue open in two places (neither of which is upstream) only
leading to duplication.

Is this already pushed to stable? I know @defolos create the package, because I tested it.

It is in f33, but afaik not in f32 yet.

The update is pushed in f32 and f33: https://bugzilla.redhat.com/show_bug.cgi?id=1908152

Thank you @defolos for the update :)

Metadata Update from @nasirhm:
- Issue close_status updated to: complete
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata