the fresh installation reports error in i3 config file because of $mod+d duplicate entries
i3 config file
it is already reported upstream here but we should patch it ourselves for better experience with fresh installation.
The default config by i3-config-wizard creates duplicate keybinding for $mod+d in .config/i3/config
i3-config-wizard
.config/i3/config
Those two duplicate keybindings are following (for dmenu):
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)
@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.
i3
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)
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
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.
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.
` @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
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.
I created a new documentation page about how to report i3 bugs on Fedora in i3-sig/docs#12. Feedback welcome!
Once that merges, I propose closing this ticket too.
<img alt="Local preview of new docs page: How to report i3 bugs on Fedora" src="/i3-sig/Fedora-i3-Spin/issue/raw/files/117a6b725f68c6c2cea501c2c739b32373add9ed64592349865fc269f4599d8f-Screenshot_2021-01-19_How_to_report_i3_bugs_on_Fedora_Local_Preview_-_Fedora_i3_S_I_G_.png" />
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)
Login to comment on this ticket.