[kwin] [Bug 479359] sddm-helper-start-wayland fails/exits after manually turn on monitors
https://bugs.kde.org/show_bug.cgi?id=479359 Emre changed: What|Removed |Added CC||ereno...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 477045] Power Battery Applet Remaining Charge Percent not getting updated
https://bugs.kde.org/show_bug.cgi?id=477045 --- Comment #2 from Emre --- Created attachment 163211 --> https://bugs.kde.org/attachment.cgi?id=163211=edit Another example -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 477045] Power Battery Applet Remaining Charge Percent not getting updated
https://bugs.kde.org/show_bug.cgi?id=477045 Emre changed: What|Removed |Added Summary|Power Applet Remaining |Power Battery Applet |Charge Percent not getting |Remaining Charge Percent |updated |not getting updated -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 477045] Power Applet Remaining Charge Percent not getting updated
https://bugs.kde.org/show_bug.cgi?id=477045 --- Comment #1 from Emre --- Created attachment 163187 --> https://bugs.kde.org/attachment.cgi?id=163187=edit Energy Info window Battery percentagea -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 477045] New: Power Applet Remaining Charge Percent not getting updated
https://bugs.kde.org/show_bug.cgi?id=477045 Bug ID: 477045 Summary: Power Applet Remaining Charge Percent not getting updated Classification: Plasma Product: Powerdevil Version: 5.27.9 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ereno...@hotmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 163186 --> https://bugs.kde.org/attachment.cgi?id=163186=edit Power Tray Icon Percentage SUMMARY I'm using my laptop w/o a power adapter and noticing that the power icon in tray always shows "Batttery at 92%". However when i look at Energy in Info center, I can see it's at 78% (or lower). If I restart upower with systemctl, then I have a correct up-to-date value in the icon matching Energy info window , but it gets outdated quickly as I use the laptop. STEPS TO REPRODUCE 1. Unplug power, suspend 2. Resume and start working 3. After some time, ie 15 mins, hover over the power icon in tray and see remaining percent. Then right click the power icon in tray and click "Show Energy Information". See the real remaining battery there, not matching the hover value. 4. You can restart the upower daemon with systemd to get an updated % but it will quickly get outdated as well. It does not update. OBSERVED RESULT Battery % is not being updated as battery is used EXPECTED RESULT Battery % shall be correctly shown, matching Energy Info window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.27.9 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION In the pictures, you can see that actual battery is 75% while the tray icon still showing 77%. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432291] Hide mouse cursor after some timout on the lock and login screens
https://bugs.kde.org/show_bug.cgi?id=432291 Emre changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #3 from Emre --- +1 for this. I'm on an OLED panel and I want everything to dissapear from the screen after some time. Current KDE lockscreen elements dissapear (I have pure black background), but only the mouse remains. Appreciate if it can also disssapear together with rest of the elements and come back when a key is pressed or mouse is moved. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470918] SDDM numlock behaviour is broken
https://bugs.kde.org/show_bug.cgi?id=470918 Emre changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470918] New: SDDM numlock behaviour is broken
https://bugs.kde.org/show_bug.cgi?id=470918 Bug ID: 470918 Summary: SDDM numlock behaviour is broken Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: emretunc...@gmail.com Target Milestone: --- SUMMARY *** I enabled NumLock from Settings -> Keyboard -> Hardware, also I added; "[General] Numlock=on" to /etc/sddm.conf but after fresh reboot in SDDM Login Screen numpad doesnt work. Numlock seems enabled as it should be but I need to click password bar to use numpad keys otherwise cannot write anything with numpad even if it looks like I can write. *** STEPS TO REPRODUCE 1. Settings -> Keyboard -> Hardware -> NumLock on Plasma Startup -> Turn on. 2. Adding Numlock=on to [General] section in /etc/sddm.conf file. 3. Reboot or Log Out from system. OBSERVED RESULT NumLock seems enabled but numpad keys doesn't work until clicking password area. EXPECTED RESULT Numpad keys should work without clicking password bar or disabling/enabling NumLock. SOFTWARE/OS VERSIONS Linux: Debian 12 Stable KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland SDDM Version: 0.19.0-5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 --- Comment #25 from Emre --- (In reply to Syiad from comment #24) > Is someone actually working on this, or is the proposed solution to use > Thunderbird instead of Kontact? > > Why is kmail trying to change the format of the quoted html in the first > place? This really makes e-mail responses look ridiculous, thereby > prohibiting the use of Kontact/kmail in a professional context. Hi Syiad, if you're suffering from this bug, I suggest you move to Evolution or Outlook on the Web. I dont think this will be solved. It's been 7 years it's been reported... -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 393212] Can't access Google Drive behind company proxy
https://bugs.kde.org/show_bug.cgi?id=393212 --- Comment #2 from Emre --- Hi, not using KDE anymore so can't check it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] Cannot unlock KDE lockscreen after undocking while laptop screen was off
https://bugs.kde.org/show_bug.cgi?id=437471 --- Comment #3 from Emre --- This bug now forces me to remember to unlock first, then undock my laptop. In that case the laptop monitor gets activated and application windows move to the laptop screen, so workflow is not broken. If I happen to forget to unlock, ie need to undock & take my laptop urgently, then I can't unlock anymore... Need to force power off the laptop and maybe lose data... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] Cannot unlock KDE lockscreen after undocking while laptop screen was off
https://bugs.kde.org/show_bug.cgi?id=437471 Emre changed: What|Removed |Added Summary|No lock screen after|Cannot unlock KDE |undocking with lid closed |lockscreen after undocking ||while laptop screen was off -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] No lock screen after undocking with lid closed
https://bugs.kde.org/show_bug.cgi?id=437471 Emre changed: What|Removed |Added Platform|Other |Archlinux Packages Version|5.10.3 |5.24.2 --- Comment #2 from Emre --- I dont think this is a duplicate of the other case. This is happening in Wayland. Maybe a bit more precision to help debug it. I'm now using KDE 5.24.2. In my scenario, laptop is docked with Thunderbolt port, using two external screens, laptop screen is off (closed or open, but off). I lock my screen. I can unlock it fine as long as I dont undock. But if I undock it while screen was locked, the laptop screen turns on as expected, and displays the wallpaper. But the lockscreen password entry box is not visible. Moving mouse around, trying to go to TTY and back, does not help, no password entry box. Entering password manually does not make any difference neither. So it seems the lockscreen password entry box is stuck in a monitor/screen which no longer exists as the laptop is undocked, and it's not moved to the active screen/monitor. This is a dealbreaker case for many laptop users. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] No lock screen after undocking with lid closed
https://bugs.kde.org/show_bug.cgi?id=437471 Emre changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Emre changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #394 from Emre --- So, I was trying KDE 5.24 on my Arch and using Wayland. No primary display setting in Wayland it seems. I booted my laptop with Thunderbolt docking station connected and lid closed. Two external screens working fine. When I unplugged my docking station with lid off, and lifted the lid up, nothing visible on screen. Could not do anything. Had to force reboot. Then I rebooted my PC with only laptop screen. Logged in, no panel. Plugged docking station, Panel visible on one of the external monitors (wrong one). Unplugged the docking station, laptop turned on (lid was always open this time), panel dissaperared, did not move to Laptop screen. So imho, on wayland, all this display configurations and panel placement needs to be looked at. It's very common for laptops to dock and undock. Shall I open a bug report? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 --- Comment #20 from Emre --- (In reply to Peter Wibberley from comment #19) > Actually kmail 5.18.3. > > Given that a lot of email correspondents are using Outlook, this problem is > a bit inconvenient, and detracts from the professionalism of the replies we > make using kmail. Any solution/workaround would be much appreciated. > > Thanks and regards Hi Peter, it seems this bug would not get resolved, probably it needs very heavy changes on Kmail and hence nobody touches it from the developers. Workarounds are proposed in other answers, ie switch to Evolution, or use Outlook on the Web, or even Thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] New: No lock screen after undocking with lid closed
https://bugs.kde.org/show_bug.cgi?id=437471 Bug ID: 437471 Summary: No lock screen after undocking with lid closed Product: kscreenlocker Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: ereno...@hotmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When undocking from thunderbolt docking station with laptop lid closed, and opening the lid, the screen is on, mouse pointer is visible. Screen locker is not visible and desktop cannot be accessed as password cannot be entered. Going to other TTY console, logging in and killing kscreenlocker_greeter brings the screenlock window back and then the desktop can then be unlocked. STEPS TO REPRODUCE 1. Dock your laptop and close the laptop lid (settings to not standby when lid closed). Work with your external monitors. 2. Unplug your thunderbolt docking cable while laptop lid is closed. 3. Open the lid of your laptop, see that mouse pointer is visible, but no screenlocker window to enter your password. OBSERVED RESULT screenlocker window to enter your password is not visible (probably it still thinks its displaying on external monitors which no longer exist). You can't enter your password and you can't unlock, hence you can't access your desktop. EXPECTED RESULT screenlocker is presented and I can enter my password to access my desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.21.5 / 5.82.0 (latest on Arch as of 20/05/2021) KDE Plasma Version: 5.21.5 / 5.82.0 KDE Frameworks Version: 5.21.5 / 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #20 from Emre --- for my case, I have KDE Connect and receiving for example SMS notifications which include some one-time password. My eye sight is not 100%, and when I'm rushing to read the SMS content to copy the one-time-passcode, it's pretty difficult. It would help if I could make those pop-ups a one or two font size bigger. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426273] Screen distorsions and ghosting in multi-monitor setup on Plasma-Wayland
https://bugs.kde.org/show_bug.cgi?id=426273 --- Comment #4 from Emre --- Created attachment 131472 --> https://bugs.kde.org/attachment.cgi?id=131472=edit Showing more ghosting -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426273] Screen distorsions and ghosting in multi-monitor setup on Plasma-Wayland
https://bugs.kde.org/show_bug.cgi?id=426273 --- Comment #3 from Emre --- Each time I right click the desktop or any other window buttons in primary monitor, the second monitor distorted image updates, as if its cycling through the path the Konsole window followed on this monitor. If I right that distorted desktop in second monitor, right click desktop menu appears but then it also ghosts and stays around. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426273] Screen distorsions and ghosting in multi-monitor setup on Plasma-Wayland
https://bugs.kde.org/show_bug.cgi?id=426273 --- Comment #2 from Emre --- Created attachment 131471 --> https://bugs.kde.org/attachment.cgi?id=131471=edit window ghosting on wayland No there is no desktop background. Here is how it looks like. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426273] New: Screen distorsions and ghosting in multi-monitor setup on Plasma-Wayland
https://bugs.kde.org/show_bug.cgi?id=426273 Bug ID: 426273 Summary: Screen distorsions and ghosting in multi-monitor setup on Plasma-Wayland Product: kwin Version: 5.19.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: ereno...@hotmail.com Target Milestone: --- SUMMARY I have a two monitor setup, side by side, 24" 1920x1200 screens. I'm using latest arch linux KDE packages. When I login to a wayland session, it logs in normally. Then for example I launch konsole application or any other application, it works on first screen. Then I move the window to 2nd monitor with my mouse and problems start. When I move the window around in 2nd monitor, many more konsole window ghosts appear and they dont go away. STEPS TO REPRODUCE 1. login to plasma-wayland session 2. launch any application, move to 2nd monitor 3. move your window around and see the screen getting filled up with ghosts of the same window OBSERVED RESULT ghosts of same window appears, does not refresh, does not dissapear. EXPECTED RESULT Normal behaviour, you can move windows as you wish with no artifacts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: arch linux, up to date of Sept 7th, 2020. KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION xcb windowing system is stated in about system -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425573] Spectacle does not save Rectangular Selection
https://bugs.kde.org/show_bug.cgi?id=425573 Emre changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #2 from Emre --- I confirm this bug as well. It was working properly in earlier versions. Now, when I do this, only clipboard is saved, file on disk does not exist. But if I launch spectacle manually after clicking the shortcut button, then a file is automatically created but which spans all my monitors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Allow to change notification font size and color in configuration file.
https://bugs.kde.org/show_bug.cgi?id=411314 Emre changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #14 from Emre --- Agree for this bug. I have KDE Connect and receiving for example SMS notifications which include some one-time password. My eye sight is not 100%, and when I'm rushing to read the SMS content to copy the one-time-passcode, it's pretty difficult. It would help if I could make those pop-ups a one or two font size bigger. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 --- Comment #15 from Emre --- I gave up long time ago on this. Evolution can handle the spaces, you can use that one if double space is really an issue. For myself, I switched to using Office365 on the Web, the webmail of Outlook. Works mostly well and has other integrations (calendars, room finder, name completion...) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 --- Comment #12 from Emre --- Dears, any development on this? KMail added EWS resource and it seems to work good, but without solving this bug, we can't use Kmail in Corporate Office 365 environment. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 393212] New: Can't access Google Drive behind company proxy
https://bugs.kde.org/show_bug.cgi?id=393212 Bug ID: 393212 Summary: Can't access Google Drive behind company proxy Product: kio-gdrive Version: 1.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: ereno...@hotmail.com Target Milestone: --- on Arch with kioclient 5.12.4. When I'm behind company proxy, which is configured with a Proxy Autoconfiguration URL pointing to a PAC file, Google Drive integration in Dolphin does not work. when I'm at home, with direct connnection to internet. It works. So is there a bug in the proxy connection or this is a feature not yet implemented? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 Emre <ereno...@hotmail.com> changed: What|Removed |Added Platform|Neon Packages |Archlinux Packages Version|5.3.0 |5.7.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 Emre <ereno...@hotmail.com> changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #10 from Emre <ereno...@hotmail.com> --- I'm suffering from this as well. Forwarded emails show up in the email with double spacing, rendering difficult to read to the eyes. I assume this is similar issue like we had back in days when Evolution used its own rendering engine. It was fixed in Evolution when they moved to webkitgtk to render emails. Thunderbird is also handling it well. Can't Kmail use webkit as well? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389369] Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 --- Comment #5 from Emre <ereno...@hotmail.com> --- I progressed a bit and explained the issue here as well: https://github.com/KrissN/akonadi-ews/issues/48 Basically, there's a disconnect between Akonadi-Ews resource and the Kwallet. EWS resource does not save the password to KWallet and then can't find it, resulting in different types of connection errors. I managed to overcome it by manually entering the password to kwallet, either using kwalletmanager or by qdbus command like below: qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_6 /Settings org.kde.Akonadi.Ews.Wallet.setPassword "my_app_password" I had to re-create the account and enter the password again btw, to make folders visible in Kmail, that could be subject to another bug. (folders were visible inside the akonadi server subscriptions dialog) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370510] Can't move windows to 2nd monitor - stuck at panel border
https://bugs.kde.org/show_bug.cgi?id=370510 --- Comment #14 from Emre <ereno...@hotmail.com> --- I can freely move windows now over the taskbar. So I think the issue is resolved. Latest KDE in Arch, I guess it's 5.12.2. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389369] Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 Emre <ereno...@hotmail.com> changed: What|Removed |Added Version|5.7.1 |5.7.2 --- Comment #4 from Emre <ereno...@hotmail.com> --- Tested on 5.7.2 as well, same result :( -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389369] Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 --- Comment #3 from Emre <ereno...@hotmail.com> --- Managed to get the http debugging on and attached the trace. Looks like it fails first, then tries Basic Auth, succeeds with a HTTP 200 OK response. Then fails again with 401. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389369] Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 --- Comment #2 from Emre <ereno...@hotmail.com> --- Created attachment 110092 --> https://bugs.kde.org/attachment.cgi?id=110092=edit Akonadi Ews http tracing -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389369] Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 Emre <ereno...@hotmail.com> changed: What|Removed |Added Platform|Other |Archlinux Packages --- Comment #1 from Emre <ereno...@hotmail.com> --- My system is an up to date Arch linux x64. As stated, Evolution is working perfectly fine on this setup. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389369] New: Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 Bug ID: 389369 Summary: Can't Authenticate to Office 365 Product: Akonadi Version: 5.7.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-b...@kde.org Reporter: ereno...@hotmail.com CC: kri...@op.pl Target Milestone: --- I'm giving a try to use Kmail instead of Evolution in my work setup. Our company uses Office 365. Evolution is able to connect to https://outlook.office365.com/EWS/Exchange.asmx and access the mailbox with "basic" authentication, using email address as username and a special app password (otherwise we have OAUTH dual factor authentication). Same for the AquaMail app on my Android, both using EWS. However, akonadi-ews can't connect, throws unable to connect errors, "offline" or "401" errors. I tried adding DOMAIN field, keeping it empty, etc, it didn't make any difference. I also selected and deselected NTLMv2, no difference. I added the following to .config/QtProject/qtlogging.ini to have more details but my system does not have any .xsession-errors file (using KDE on GDM) [rules] kf5.kio.kio_http.auth=true Here's the error I have in the system journal, email address changed for privacy. kiod5[6190]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 kiod5[6190]: org.kde.kio.kpasswdserver: User = "emre.e...@company.com" , WindowId = 0 kiod5[6190]: org.kde.kio.kpasswdserver: User = "emre.e...@company.com" , WindowId = 0 seqNr = 2 , errorMsg = "" kiod5[6190]: org.kde.kio.kpasswdserver: key= "https-emre.e...@company.com@outlook.office365.com:-1" , user= "emre.e...@company.com" se kiod5[6190]: org.kde.kio.kpasswdserver: key= "https-emre.e...@company.com@outlook.office365.com:-1" akonadi_ews_resource[6733]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 kiod5[6190]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 kiod5[6190]: org.kde.kio.kpasswdserver: User = "emre.e...@company.com" , WindowId = 0 kiod5[6190]: org.kde.kio.kpasswdserver: User = "emre.e...@company.com" , WindowId = 0 seqNr = 0 , errorMsg = "" kiod5[6190]: org.kde.kio.kpasswdserver: key= "https-emre.e...@company.com@outlook.office365.com:-1" , user= "emre.e...@company.com" se kiod5[6190]: org.kde.kio.kpasswdserver: key= "https-emre.e...@company.com@outlook.office365.com:-1" akonadi_ews_resource[6733]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 akonadi_ews_resource[6733]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 kiod5[6190]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 kiod5[6190]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 kiod5[6190]: org.kde.kio.kpasswdserver: User = "emre.e...@company.com" , WindowId = 0 kiod5[6190]: org.kde.kio.kpasswdserver: User = "emre.e...@company.com" , WindowId = 0 seqNr = 4 , errorMsg = "" kiod5[6190]: org.kde.kio.kpasswdserver: key= "https-emre.e...@company.com@outlook.office365.com:-1" , user= "emre.e...@company.com" se kiod5[6190]: org.kde.kio.kpasswdserver: key= "https-emre.e...@company.com@outlook.office365.com:-1" akonadi_ews_resource[6733]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 akonadi_ews_resource[6733]: ERROR "Failed to process EWS request - HTTP code 401" -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 Emre Unlu <e...@eunlu.com> changed: What|Removed |Added CC||e...@eunlu.com --- Comment #18 from Emre Unlu <e...@eunlu.com> --- I can reproduce this easily on KDE neon dev. ed. -stable and can get logs if needed. forvelin@stormgarden:~$ sudo partitionmanager QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loaded backend plugin: "pmlibpartedbackendplugin" QLayout: Attempting to add QLayout "" to PartitionManagerWidget "m_PartitionManagerWidget", which already has a layout QLayout: Attempting to add QLayout "" to ListDevices "m_ListDevices", which already has a layout QLayout: Attempting to add QLayout "" to QWidget "m_ListOperations", which already has a layout QLayout: Attempting to add QLayout "" to QWidget "m_InfoPane", which already has a layout QLayout: Attempting to add QLayout "" to QWidget "m_TreeLog", which already has a layout "Using backend plugin: pmlibpartedbackendplugin (1)" "Scanning devices..." QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object "Device found: ATA INTEL SSDSC2BW18" getting temp failed for "/dev/sda" : No such file or directory blkid: unknown file system type "" on "/dev/sda2" QFileInfo::absolutePath: Constructed with empty filename "Partition ‘/dev/sda2’ is not properly aligned (first sector: 1001470, modulo: 2046)." KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = partitionmanager path = /usr/bin pid = 4349 KCrash: Arguments: /usr/bin/partitionmanager KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/tmp/runtime-root/kdeinit5__0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 346918] Removing the ALT+F1 shortcut for displaying Application launcher isn't saved between sessions when removed from "Global shortcuts -> plasmashell"-section
https://bugs.kde.org/show_bug.cgi?id=346918 Emre Unlu <e...@eunlu.com> changed: What|Removed |Added CC||e...@eunlu.com --- Comment #9 from Emre Unlu <e...@eunlu.com> --- Similar thing is happening to me, Application Launcher shortcut changes are not preserved between sessions. KDE Plasma 5.7.5 and Fedora 24 here. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Emre <ereno...@hotmail.com> changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #14 from Emre <ereno...@hotmail.com> --- +1 to this in Arch KDE Plasma 5.8. I'm using a Surface Pro 3 without a keyboard (sometimes). I want to be able to suspend and resume without logging in first. This is the default "sane" behavior in Windows. Power button or shutdown/suspend icons on screen always suspends regardless of lock screen state. This shall be the default mode in laptops which shall be disabled by an option if more security is required. Hope there are more users who try to use KDE on laptops! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370510] Can't move windows to 2nd monitor - stuck at panel border
https://bugs.kde.org/show_bug.cgi?id=370510 --- Comment #5 from Emre <ereno...@hotmail.com> --- Hi Luke, no, when the panel is at the top, that problem does not exist. Windows can freely move between monitors. The workaround that Martin has given works well. If you click ALT before you click the window titlebar, then you can move the window to the other monitor passing under the panel. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370510] Can't move windows to 2nd monitor - stuck at panel border
https://bugs.kde.org/show_bug.cgi?id=370510 --- Comment #3 from Emre <ereno...@hotmail.com> --- Thanks Martin for the response and the ALT+LEFT_MOUSE tip. That helps as a workaround although one that requires an extra step each time you want to move a window. In MS Windows desktops no such problem exists. I do not understand what you mean that it's a protection. In years of Windows use, never faced such issue. By the time the last pixel row comes to the panel it jumps to second screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370510] Can't move windows to 2nd monitor - stuck at panel border
https://bugs.kde.org/show_bug.cgi?id=370510 --- Comment #1 from Emre <ereno...@hotmail.com> --- Created attachment 101529 --> https://bugs.kde.org/attachment.cgi?id=101529=edit Screenshot that shows the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370510] New: Can't move Windows to 2nd monitor - stuck at panel border
https://bugs.kde.org/show_bug.cgi?id=370510 Bug ID: 370510 Summary: Can't move Windows to 2nd monitor - stuck at panel border Product: kwin Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ereno...@hotmail.com I have a two monitor setup. Laptop screen eDP1 is below the HDMI screen. Xrandr is like this: xrandr --output eDP1 --auto --below HDMI1 --output HDMI1 --auto --primary Large Monitor on HDMI is the primary one, it has the taskbar/panel 100% of the width. The panel is at the bottom edge of the HDMI monitor. The Laptop Monitor on eDP1 does not have any panels, just empty. When I try to move a window using my mouse from the top monitor, through the panel, to the bottom monitor, the window goes but gets stuck at the panel. So the window is essentially trapped in the top monitor. If I use the Move To Screen - Screen Two (eDP1) command on the top left icon of that window, the window moves. Hope I'm not the only one using Top-Bottom monitor configurations :) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370510] Can't move windows to 2nd monitor - stuck at panel border
https://bugs.kde.org/show_bug.cgi?id=370510 Emre <ereno...@hotmail.com> changed: What|Removed |Added Summary|Can't move Windows to 2nd |Can't move windows to 2nd |monitor - stuck at panel|monitor - stuck at panel |border |border -- You are receiving this mail because: You are watching all bug changes.
