[plasmashell] [Bug 370215] New: Monospace font does not default to Hack in KCM fontsettings module
https://bugs.kde.org/show_bug.cgi?id=370215 Bug ID: 370215 Summary: Monospace font does not default to Hack in KCM fontsettings module Product: plasmashell Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: accounts+bugs@florianjacob.de CC: plasma-b...@kde.org I just updated to 5.8 and wanted do use the new default font Hack, as it was described in:http://jriddell.org/2016/08/01/your-new-monospace-font-hack/ I went to the KCM Font module and pressed the „reset to defaults“ button, but the Monospace font was reset to Oxygen Mono 9 instead of Hack 9. Switching manually to Hack 9 works, though. Reproducible: Always Steps to Reproduce: 1. Go to the Fonts KCM Module 2. Press „Reset to defaults“ button Actual Results: The Monospace font was set to Oxygen Mono 9. Expected Results: The Monospace font should have ben set to Hack 9. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 365978] no sip accounts
https://bugs.kde.org/show_bug.cgi?id=365978 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 357663] Owncloud missing (Fedora), empty list with OpenSuse
https://bugs.kde.org/show_bug.cgi?id=357663 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 357663] Owncloud missing (Fedora), empty list with OpenSuse
https://bugs.kde.org/show_bug.cgi?id=357663 --- Comment #3 from Florian Jacob --- Yeah, same here. „Configure your web accounts like Google, Live and ownCloud“ but none of the listed is presennt. I can only configure telepathy based instant messaging accounts. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 365116] kate horizontally cuts off lines if they contain tall characters
https://bugs.kde.org/show_bug.cgi?id=365116 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de --- Comment #7 from Florian Jacob --- For the record: I can reproduce this with Arch Linux and Qt 5.7 too, as soon as I switch to the Oxygen Mono font. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 365890] New: When using Shift+Home/End as shortcut using the neo layout, the Shift+U / Shift+O keys do not enter large U/O anymore.
https://bugs.kde.org/show_bug.cgi?id=365890 Bug ID: 365890 Summary: When using Shift+Home/End as shortcut using the neo layout, the Shift+U / Shift+O keys do not enter large U/O anymore. Product: frameworks-kglobalaccel Version: 5.24.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: accounts+bugs@florianjacob.de CC: kdelibs-b...@kde.org My X11 keyboard layout is set to the german neo layout. I can reproduce this regardles of whether I choose neo or normal german keyboard layout via tha KDE keyboard layout setting. In both layouts, it's the key right next to the left shift key. So with german layout I can't type Shift+A, with neo, I can't type Shift+U. It's still very likely that this is related to using neo layout (but I can't test it on a clean machine), because the keys Mod4+U (physical A key) / Mod4+O (physical G key) are alternative Home / End keys in neo. It seems like kglobalaccel (or the underlying Qt) are somehow overreacting and filtering out Shift+U too because Mod4+U would be the targeted Home key. Here's the output of xev for Shift+A and Shift+S via german keyboard layout. It seems like the KeyPress Event for Shift+A can't be decoded to "A". KeyPress event, serial 28, synthetic NO, window 0xa1, root 0x97, subw 0x0, time 4513962, (73,104), root:(73,518), state 0x2000, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 28, synthetic NO, window 0xa1, root 0x97, subw 0x0, time 4514652, (73,104), root:(73,518), state 0x2001, keycode 30 (keysym 0x55, U), same_screen YES, XKeysymToKeycode returns keycode: 38 XLookupString gives 1 bytes: (55) "U" XmbLookupString gives 1 bytes: (55) "U" XFilterEvent returns: False KeyRelease event, serial 28, synthetic NO, window 0xa1, root 0x97, subw 0x0, time 4514723, (73,104), root:(73,518), state 0x2001, keycode 30 (keysym 0x55, U), same_screen YES, XKeysymToKeycode returns keycode: 38 XLookupString gives 1 bytes: (55) "U" XFilterEvent returns: False KeyRelease event, serial 28, synthetic NO, window 0xa1, root 0x97, subw 0x0, time 4515127, (73,104), root:(73,518), state 0x2001, keycode 50 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 28, synthetic NO, window 0xa1, root 0x97, subw 0x0, time 4544507, (77,91), root:(77,505), state 0x2000, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeymapNotify event, serial 28, synthetic NO, window 0x0, keys: 4294967191 0 0 0 64 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 28, synthetic NO, window 0xa1, root 0x97, subw 0x0, time 4545002, (77,91), root:(77,505), state 0x2001, keycode 38 (keysym 0x41, A), same_screen YES, XKeysymToKeycode returns keycode: 40 XLookupString gives 1 bytes: (41) "A" XFilterEvent returns: False KeyRelease event, serial 28, synthetic NO, window 0xa1, root 0x97, subw 0x0, time 4545352, (77,91), root:(77,505), state 0x2001, keycode 62 (keysym 0xffe5, Caps_Lock), same_screen YES, XKeysymToKeycode returns keycode: 50 XLookupString gives 0 bytes: XFilterEvent returns: False Reproducible: Always Steps to Reproduce: 0. Probably: Use neo as X11 keyboard layout setting 1. Custom Shortcuts > New > Global Shortcut > Command 2. Trigger: Shift+Home 3. Action: notify-send "hi" 4. Try to enter the large letter U in any textbox Actual Results: nothing happens Expected Results: a large letter "U" is entered. I'm using current KDE via ArchLinux (Qt 5.7.0, KF 5.24.0, Plasma 5.7.2) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 343452] Does not sort numbers naturally any longer
https://bugs.kde.org/show_bug.cgi?id=343452 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 366620] New: the minimal example given at the start page of kirigami docs is broken
https://bugs.kde.org/show_bug.cgi?id=366620 Bug ID: 366620 Summary: the minimal example given at the start page of kirigami docs is broken Product: kirigami Version: unspecified Platform: Other URL: https://api.kde.org/kirigami/html/index.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: accounts+bugs@florianjacob.de I tried to copy the example code to a file and execute it as it was the first kirigami code I found that I could try out, but it did not run. Reproducible: Always Steps to Reproduce: 1. copy the example in a file, e.g. example.qml 2. execute it with qml example.qml Actual Results: QQmlApplicationEngine failed to load component file:///home/florian/test.qml:41 Action is not a type and, after fixing the actions: file:///home/florian/test.qml:73: ReferenceError: sheet is not defined file:///home/florian/test.qml:42: ReferenceError: sheet is not defined Expected Results: executing the sample with no error >From line 40 onwards, the example uses Action instead of Kirigami.Action, which seems to cause an import error. After I replaced all „Action“ with „Kirigam.Action“ the file executes, but throws an error about the used sheet variable. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 343427] kcm_sddm : Allow keyboard layout selection
https://bugs.kde.org/show_bug.cgi?id=343427 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 363451] Commit 58a8036 breaks existing wallets for some users
https://bugs.kde.org/show_bug.cgi?id=363451 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 361853] rsibreak does not start automatically after install
https://bugs.kde.org/show_bug.cgi?id=361853 --- Comment #2 from Florian Jacob --- It was directly after installation, so the config file didn't exist at all. I did some testing and was very irritated by the behaviour, I thought the results might be wrong due to automatic session restore. I now found http://l10n.kde.org/docs/admin/autostart-and-runonce.html and that I made a wrong assumption, I thought the false in /etc/xdg meant the needed value of the setting to autostart is false, which turned out to be wrong: “The value true at the end of the line is used as default value if the key or config file is not present.” In case it's intentional to start rsibreak automatically on login but requiring that it was started manually once, everything is fine. ;) Sorry for the noise! -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 361853] rsibreak does not start automatically after install
https://bugs.kde.org/show_bug.cgi?id=361853 --- Comment #4 from Florian Jacob --- Thanks alot for maintaining rsibreak then, it's a really useful tool to me. :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Florian Jacob changed: What|Removed |Added CC||accounts+bugs.kde@florianja ||cob.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Florian Jacob changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #9 from Florian Jacob --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 361853] New: rsibreak does not start automatically after install
https://bugs.kde.org/show_bug.cgi?id=361853 Bug ID: 361853 Summary: rsibreak does not start automatically after install Product: rsibreak Version: 0.12.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: accounts+bugs@florianjacob.de Despite the „start rsibreak automatically on login“ option being enabled by default, rsibreak does not start after login. Reproducible: Always Steps to Reproduce: 1. install rsibreak 2. reboot Actual Results: rsibreak did not start. Expected Results: rsibreak started and the applet is visible in the system tray. I found the line ``` X-KDE-autostart-condition=rsibreakrc:General:AutoStart:false ``` in `/etc/xdg/autostart/rsibreak_autostart.desktop`. If I understand X-KDE-autostart-condition right, this should actually be ``` X-KDE-autostart-condition=rsibreakrc:General:AutoStart:true ``` to use the config option right. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 361860] New: pam unlock does not work when using a kwallet name other than “kdewallet”
https://bugs.kde.org/show_bug.cgi?id=361860 Bug ID: 361860 Summary: pam unlock does not work when using a kwallet name other than “kdewallet” Product: frameworks-kwallet Version: 5.20.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: accounts+bugs@florianjacob.de CC: kdelibs-b...@kde.org I tried to setup automatic unlock on login, but the unlock always failed. As soon as I renamed my wallet to “kdewallet”, the unlock worked. Reproducible: Always Steps to Reproduce: 1. Set up automatic unlock e.g. after this guide: https://wiki.archlinux.org/index.php/KDE_Wallet#Unlock_KDE_Wallet_automatically_on_login 2. create a new wallet with blowfish backend, using e.g. “kwallet” as the name. 3. delete the default “kdewallet” 4. or explicitly choose the new wallet as default wallet in the settings menu Actual Results: The unlock fails: kwalletd5: Wallet failed to get opened by PAM, error code is -9 kwalletd5: fsize: 2765156783 encrypted.size(): 53520 blksz: 8 kwalletd5: Wallet new enough, using new hash kwalletd5: kwalletd5 started Expected Results: The unlock succeeds. I looked around in the kwallet code to find out what the error code -9 actually means, it seems to come from here: https://github.com/KDE/kwallet/blob/master/src/runtime/kwalletd/backend/backendpersisthandler.cpp#L414 I'm reporting this because the code seemed like it would actually support encrypting whatever wallet is currently set as default wallet, in contrary to this statement found in the arch wiki: Note: Currently, pam_kwallet-git / kwallet-pam has at least two limitations: first, it's not compatible with GnuPG keys, so KDE Wallet must use the standard blowfish encryption. Also, the wallet name must be "kdewallet" (that's the default name). If, for some reason, you create a new wallet, you need to use this name (so you will probably need to rename the old wallet too). -- You are receiving this mail because: You are watching all bug changes.
