[konsole] [Bug 420463] konsole windows & tabs that have been open for a long time no longer accept keyboard input
https://bugs.kde.org/show_bug.cgi?id=420463 Jani-Matti Hätinen changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Jani-Matti Hätinen --- This was actually an ibus related issue. Opened a new bug with appropriate title & steps to reproduce as #420464 *** This bug has been marked as a duplicate of bug 420464 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420464] konsole windows stop accepting keyboard input if you kill the ibus daemon
https://bugs.kde.org/show_bug.cgi?id=420464 --- Comment #1 from Jani-Matti Hätinen --- *** Bug 420463 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420464] New: konsole windows stop accepting keyboard input if you kill the ibus daemon
https://bugs.kde.org/show_bug.cgi?id=420464 Bug ID: 420464 Summary: konsole windows stop accepting keyboard input if you kill the ibus daemon Product: konsole Version: 20.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: jani-matti.hati...@iki.fi Target Milestone: --- SUMMARY konsole windows & tabs opened while ibus daemon was running will stop accepting keyboard input if you stop/kill the daemon. All other software works fine. STEPS TO REPRODUCE 1. Open a konsole window, or let one open as part of your desktop session during start-up 2. Kill the ibus daemon (maybe because you don't need emojis) 3. Try typing in the konsole window OBSERVED RESULT Keyboard input in the console window has no effect EXPECTED RESULT konsole (out of all software) should keep working with, or without something like ibus -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420463] New: konsole windows & tabs that have been open for a long time no longer accept keyboard input
https://bugs.kde.org/show_bug.cgi?id=420463 Bug ID: 420463 Summary: konsole windows & tabs that have been open for a long time no longer accept keyboard input Product: konsole Version: 20.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: jani-matti.hati...@iki.fi Target Milestone: --- SUMMARY If a konsole window/tab has been open for a long time, at some point it simply stops accepting any keyboard input (including tab-switching with Shift-Left/Right). Always reproducible with windows/tabs that have been restored during session start-up. STEPS TO REPRODUCE 1. Leave a konsole window/tab open as part of your saved session 2. Start KDE 3. Don't type anything into said konsole window 4. Leave the session running for at least a few hours OBSERVED RESULT Keyboard input typed into the konsole window has no effect whatsoever. EXPECTED RESULT konsole should work as usual. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 266568] The name of the opened file/disc isn't shown in the window title
https://bugs.kde.org/show_bug.cgi?id=266568 --- Comment #7 from Jani-Matti Hätinen --- It is a horrible, horrible 'design decision' though. It elevates the application name as the main information above the content displayed, which is always wrong. No user cares one bit that Dragon player happens to be the piece of software that is playing their video file (unless of course they discover a bug in the application), they only care about the content being displayed. This problem is especially egrecious if one tries to use Dragon Player to play different video clips as part of video editing workflow. Because there's no way to see which file is playing in which window when the files are paused, Dragon Player is utterly useless in this use case simply due to this bug. Status bar does nothing in this case, because it won't show up in the task manager. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403163] Neon live install image is lacking the 32-bit EFI boot file bootia32.efi
https://bugs.kde.org/show_bug.cgi?id=403163 --- Comment #1 from Jani-Matti Hätinen --- To clarify, e.g. my Asus Transformer boot into Neon just fine with just the bootia32.efi file added. However, I do get an error about missing files from /boot/grub/i386-efi folder during boot, so one might want to include those as well. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403163] New: Neon live install image is lacking the 32-bit EFI boot file bootia32.efi
https://bugs.kde.org/show_bug.cgi?id=403163 Bug ID: 403163 Summary: Neon live install image is lacking the 32-bit EFI boot file bootia32.efi Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: jani-matti.hati...@iki.fi CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Quite a few Windows tablets and mini-pc's, while supporting the amd64 instruction set, use a 32-bit EFI boot system. Currently the Neon live images do not have the requisite bootia32.efi file to boot & install on these system STEPS TO REPRODUCE 1. Take a computer using 32-bit EFI boot (such as the Asus Transformer, or Lenovo Ideacentre Stick) 2. Insert a current Neon live image USB 3. Attempt to boot OBSERVED RESULT The machine fails to boot from the USB & boots into Windows EXPECTED RESULT The machine should be able to boot from the USB -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 266568] The name of the opened file/disc isn't shown in the window title
https://bugs.kde.org/show_bug.cgi?id=266568 Jani-Matti Hätinen changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #5 from Jani-Matti Hätinen --- Still broken in Dragon Player 18.08.2, using KDE Frameworks 5.11.1 Steps to Reproduce: 1. Open Dragon Player 2. Open any file or disk with it Actual Results: The window title doesn't change Expected Results: Window title should change to the form: Filename / Title from metadata of the opened file/disk - Dragon Player -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 --- Comment #11 from Jani-Matti Hätinen <jani-matti.hati...@iki.fi> --- If you're worried that new users won't be able to switch between HTML and non-HTML message views (a feature, which no one uses btw) make the HTML status bar visible by default and add a comment to the configuration page about the lost functionality if the bar is disabled. Simply forcing the bar on all users does absolutely nothing to promote said functionality. 99,5% of Kmail users are old users. Quit messing around with their settings. We've set it up the way we like it, and we know what we've done and why. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Jani-Matti Hätinen <jani-matti.hati...@iki.fi> changed: What|Removed |Added CC||jani-matti.hati...@iki.fi --- Comment #10 from Jani-Matti Hätinen <jani-matti.hati...@iki.fi> --- This is horrible design, and the offered 'justification' for it is a sad, sad joke. At least give us a configuration option we can add to kmail2rc. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 386852] New: plasma-integration is stuck on 5.11.0 due to version numbering
https://bugs.kde.org/show_bug.cgi?id=386852 Bug ID: 386852 Summary: plasma-integration is stuck on 5.11.0 due to version numbering Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: jani-matti.hati...@iki.fi CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- The package plasma-integration has a package version 4:5.11.0-0neon+16.04+xenial+build58, which takes precedence over any later build thanks to the 4: versioning. The only way to update to the latest package is to manually choose the latest version and the freeze the package. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 161028] Tree view for Places panel
https://bugs.kde.org/show_bug.cgi?id=161028 --- Comment #16 from Jani-Matti Hätinen <jani-matti.hati...@iki.fi> --- Any chance this might get implemented some day? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358254] Setting the toolbar font does nothing
https://bugs.kde.org/show_bug.cgi?id=358254 --- Comment #1 from Jani-Matti Hätinen <jani-matti.hati...@iki.fi> --- Still broken in QT 5.6.1, Frameworks 5.23.0, Plasma 5.6.5 and Applications 16.04.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 364967] New: Kmail message list does not remember rightmost column width
https://bugs.kde.org/show_bug.cgi?id=364967 Bug ID: 364967 Summary: Kmail message list does not remember rightmost column width Product: kmail2 Version: 5.2.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: jani-matti.hati...@iki.fi I've setup the Kmail message list using the two-row with clickable state style so that there's no horizontal scroll bar. Every time I restart Kmail, it needlessly expands the rightmost clickable state column and thus causes a horizontal scroll bar to appear. I have not modified the clickable state style in any way. Reproducible: Always Steps to Reproduce: 1. Adjust column widths to your liking 2. Restart Kmail Actual Results: Rightmost column is expanded needlessly Expected Results: Column widths should remain as set by the user -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 358257] Please forward port the option "Outline active window title" from KDE4
https://bugs.kde.org/show_bug.cgi?id=358257 --- Comment #3 from Jani-Matti Hätinen <jani-matti.hati...@iki.fi> --- Works for me. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 358257] New: Please forward port the option "Outline active window title" from KDE4
https://bugs.kde.org/show_bug.cgi?id=358257 Bug ID: 358257 Summary: Please forward port the option "Outline active window title" from KDE4 Product: Oxygen Version: 5.4.3 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: win deco Assignee: hugo.pere...@free.fr Reporter: jani-matti.hati...@iki.fi The Oxygen window decoration in KDE5 has dropped the option "Outline active window title". This option was absolutely crucial in terms of usability as it made it trivial to instantly spot the active window even on multi-screen setups. Currently on KDE5 this is nigh impossible. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358259] New: Please bring back custom button spacing from KDE4
https://bugs.kde.org/show_bug.cgi?id=358259 Bug ID: 358259 Summary: Please bring back custom button spacing from KDE4 Product: kwin Version: 5.4.3 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: jani-matti.hati...@iki.fi With kwin/KDE5 it's no longer possible to customise the spacing between the buttons in the window title. This used to be an excellent usability aid in KDE4 as it allowed one to clearly separate the window close button from the maximise/minimise buttons and thus greatly reducing the chances of a mis-click. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358259] Please bring back custom button spacing from KDE4
https://bugs.kde.org/show_bug.cgi?id=358259 --- Comment #2 from Jani-Matti Hätinen <jani-matti.hati...@iki.fi> --- Created attachment 96752 --> https://bugs.kde.org/attachment.cgi?id=96752=edit An example of a KDE4 setup with clearly separated buttons -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358254] New: Setting the toolbar font does nothing
https://bugs.kde.org/show_bug.cgi?id=358254 Bug ID: 358254 Summary: Setting the toolbar font does nothing Product: systemsettings Version: 5.4.3 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: jani-matti.hati...@iki.fi CC: unassigned-b...@kde.org KDE/Qt 5 applications no longer follow the toolbar font setting (toolBarFont in kdeglobals). Instead the font used in toolbars is set by the General font setting (font in kdeglobals). Reproducible: Always Steps to Reproduce: 1. Set a different font/size in General and Toolbar font in systemsettings or .config/kdeglobals Actual Results: Toolbar fonts follow the General font setting Expected Results: Toolbar fonts should follow the Toolbar font setting -- You are receiving this mail because: You are watching all bug changes.
