[krita] [Bug 441390] New: whenever i draw on my canvas using my wacom 4k pen the ink of the pens get all clunked up
https://bugs.kde.org/show_bug.cgi?id=441390 Bug ID: 441390 Summary: whenever i draw on my canvas using my wacom 4k pen the ink of the pens get all clunked up Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: ll4677...@gmail.com Target Milestone: --- SUMMARY the lines are not how they should be STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441391] New: whenever i draw on my canvas using my wacom 4k pen the ink of the pens get all clunked up
https://bugs.kde.org/show_bug.cgi?id=441391 Bug ID: 441391 Summary: whenever i draw on my canvas using my wacom 4k pen the ink of the pens get all clunked up Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: ll4677...@gmail.com Target Milestone: --- SUMMARY the lines are not how they should be STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441391] whenever i draw on my canvas using my wacom 4k pen the ink of the pens get all clunked up
https://bugs.kde.org/show_bug.cgi?id=441391 --- Comment #1 from li li --- (In reply to li li from comment #0) > SUMMARY > the lines are not how they should be > > STEPS TO REPRODUCE > 1. > 2. > 3. > > OBSERVED RESULT > > > EXPECTED RESULT > > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441391] whenever i draw on my canvas using my wacom 4k pen the ink of the pens get all clunked up
https://bugs.kde.org/show_bug.cgi?id=441391 li li changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441393] New: Lines are not how they should be
https://bugs.kde.org/show_bug.cgi?id=441393 Bug ID: 441393 Summary: Lines are not how they should be Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: crash Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: ll4677...@gmail.com Target Milestone: --- Created attachment 140956 --> https://bugs.kde.org/attachment.cgi?id=140956&action=edit Lines are like this SUMMARY Lines are not how they should be STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472568] New: The OSD window displayed on the lock screen is not the same as the Osd window in the non lock screen state
https://bugs.kde.org/show_bug.cgi?id=472568 Bug ID: 472568 Summary: The OSD window displayed on the lock screen is not the same as the Osd window in the non lock screen state Classification: Plasma Product: kwin Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: l_c3...@163.com Target Milestone: --- SUMMARY The OSD window displayed on the lock screen is not the same as the Osd window in the non lock screen state. The OSD window on the lock screen is drawn by the lock screen itself, not the default OSD window STEPS TO REPRODUCE 1. In a non lock screen state, call up the OSD window; 2. When the screen is locked, call up the OSD window; 3. View the styles of two OSD windows and the implementation code of the lock screen OSD window OBSERVED RESULT EXPECTED RESULT The OSD window displayed under the lock screen is consistent with the OSD window in a non lock screen state, and the lock screen no longer draws its own OSD window SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472375] New: The Virtual keyboard will be covered by the fuzzy search Tooltip
https://bugs.kde.org/show_bug.cgi?id=472375 Bug ID: 472375 Summary: The Virtual keyboard will be covered by the fuzzy search Tooltip Classification: Plasma Product: kwin Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: l_c3...@163.com Target Milestone: --- Created attachment 160374 --> https://bugs.kde.org/attachment.cgi?id=160374&action=edit Bug phenomenon SUMMARY When using the Virtual keyboard (onboard), when entering files in the search box, a fuzzy search drop-down box pops up. At this time, the Virtual keyboard is covered and cannot continue to input. STEPS TO REPRODUCE 1. Open System Settings 2. Click on the input box in the upper right corner 3. Call out the Virtual keyboard and enter the text in the input box 4. Fuzzy search pop-up appears OBSERVED RESULT Fuzzy search pop-up window covers Virtual keyboard,the Virtual keyboard can no longer be entered. EXPECTED RESULT The Virtual keyboard can input text normally on the fuzzy search pop-up window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version：5.15.0-76-generic(64位) graphics platform：X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472375] The Virtual keyboard will be covered by the fuzzy search Tooltip
https://bugs.kde.org/show_bug.cgi?id=472375 li changed: What|Removed |Added Resolution|DOWNSTREAM |--- Status|RESOLVED|REPORTED Version|5.24.7 |5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472375] The Virtual keyboard will be covered by the fuzzy search Tooltip
https://bugs.kde.org/show_bug.cgi?id=472375 --- Comment #2 from li --- This issue can still be replicated on Ubuntu 2304 plasma version 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454841] New: Not hard code the order of the day, month and year
https://bugs.kde.org/show_bug.cgi?id=454841 Bug ID: 454841 Summary: Not hard code the order of the day, month and year Product: dolphin Version: 22.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins: git Assignee: sebast...@sebastian-doerner.de Reporter: eastern...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- When show log, an arg "--date=format:%d-%m-%Y" is hard coded. In different regions, people are used to different orders of the day, month and year. Perhaps we could mark the string as i18n so that it can be localised? The arg string is in https://invent.kde.org/sdk/dolphin-plugins/-/blob/c01c0ffb8fbd92df2b48c34769a584dbc12d0ea9/git/fileviewgitplugin.cpp#L469 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 450571] LC_TIME zh_CN.UTF-8 letter only weekday label length is invalid
https://bugs.kde.org/show_bug.cgi?id=450571 Eastern Li changed: What|Removed |Added CC||easter...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466000] New: Failed to grab shortcuts on X Wayland when window was unmanaged
https://bugs.kde.org/show_bug.cgi?id=466000 Bug ID: 466000 Summary: Failed to grab shortcuts on X Wayland when window was unmanaged Classification: Plasma Product: kwin Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: i...@jiahao.li Target Milestone: --- Created attachment 156435 --> https://bugs.kde.org/attachment.cgi?id=156435&action=edit X11 Unmanaged Window SUMMARY STEPS TO REPRODUCE 1. Open VMware workstation 17 on Kwin wayland. 2. Run Windows or Linux in VM. 2. Press shortcuts which combined with Win, Alt. OBSERVED RESULT The host task switcher grabed shortcuts first, the VM grabed it again. EXPECTED RESULT Keyboard grab should be inhibited in host. VM grab the shortcuts. SOFTWARE/OS VERSIONS Arch Linux 6.1.11 Linux/KDE Plasma: 5.27.0 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Keyboard xwayland protocol didn't be added in kwin 5.26.5. So the shortcuts in vmware or freerdp(X11) can't be grabbed correctly. For kwin 5.27, the shortcuts feature was added, so freerdp (X11) can grab shortcuts correctly. https://invent.kde.org/lijiahao/kwin/-/blob/master/src/wayland/keyboard_shortcuts_inhibit_v1_interface.cpp However, the same issue existed in vmware. I think it may caused by the X11 unmanaged window. Xwayland can't handle the unmanaged key grab correctly? https://linux.die.net/man/3/xgrabkeyboard VMware workstation has two windows: GTK UI and VM virtual desktop. The GTK UI was managed by X11. But the VM window was unmanaged. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466000] Failed to grab shortcuts on X Wayland when window was unmanaged
https://bugs.kde.org/show_bug.cgi?id=466000 Jiahao Li changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Jiahao Li --- (In reply to Vlad Zahorodnii from comment #1) > The unmanaged window must have keyboard focus (from kwin's perspective). > Otherwise kwin is not going to inhibit global shortcuts. Can you check that > it's the case? I checked that with xev and xwinfo. The vmware children windows are special. It can't handle correct mouse enter event correctly. It's not bug in kwin. The input grab code implements are different in varities X11 softwares. Mutter can force grab it by setting. https://gitlab.gnome.org/GNOME/mutter/-/issues/1720 But KDE has a better way to do it. I added a troubleshooting on Archwiki. https://wiki.archlinux.org/title/KDE#X11_shortcuts_conflict_on_Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485769] Autologin settings for SDDM not read from kde_settings.conf correctly
https://bugs.kde.org/show_bug.cgi?id=485769
--- Comment #11 from Li Jiajun ---
Created attachment 170803
--> https://bugs.kde.org/attachment.cgi?id=170803&action=edit
Screenshot_shows_fixing_the_issue_by_reverting_the_commit_of_kirigami
Flozza is right.
I fixed the issue by comment out the commit of kirigami
458003901cfcdbea2e3789e320d44725f5a18428
Perhaps SDDM-KCM requires modifications to accommodate the changes implemented
in Kirigami.
Here is my patch to comment out that commit as temporal fix.
>From ccc65a2a206de614acb13154d40516fe5082c45a Mon Sep 17 00:00:00 2001
From: wlmqljj
Date: Sat, 22 Jun 2024 16:51:12 +0800
Subject: [PATCH] revert
https://invent.kde.org/frameworks/kirigami/-/merge_requests/1480
---
src/layouts/columnview.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/layouts/columnview.cpp b/src/layouts/columnview.cpp
index 583a8885..bb729271 100644
--- a/src/layouts/columnview.cpp
+++ b/src/layouts/columnview.cpp
@@ -709,10 +709,10 @@ void ContentItem::updateVisibleItems()
m_visibleItems.removeAll(item);
});
attached->setInViewport(true);
-item->setEnabled(true);
+// item->setEnabled(true);
} else {
attached->setInViewport(false);
-item->setEnabled(false);
+// item->setEnabled(false);
}
}
--
2.45.2
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 478390] New: [Win] Wrong Default File Path of "Receiving File" on Windows 10
https://bugs.kde.org/show_bug.cgi?id=478390 Bug ID: 478390 Summary: [Win] Wrong Default File Path of "Receiving File" on Windows 10 Classification: Applications Product: kdeconnect Version: 23.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: woshilizhi...@hotmail.com Target Milestone: --- The default file path of "receiving file" function has an extra "/". The path should be like "C://%DEVICENAME%/Desktop" instead of "/C://%DEVICENAME%/Desktop". STEPS TO REPRODUCE 1. Devices --> Plugin Settings --> File Sharing --> Path SOFTWARE/OS VERSIONS Windows: Windows 10 22H2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478635] New: Couldn't find the phone if the phone is the host of the hotspot. KDE Connect 22.12.3-1 on Debian 12
https://bugs.kde.org/show_bug.cgi?id=478635 Bug ID: 478635 Summary: Couldn't find the phone if the phone is the host of the hotspot. KDE Connect 22.12.3-1 on Debian 12 Classification: Applications Product: kdeconnect Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: woshilizhi...@hotmail.com Target Milestone: --- If I use the android phone as a hotspot and connect PC into that Wi-Fi hotspot, I cannot find my phone in KDE Connect. But I can find the phone and pair it with the PC if I use KDE Connect 23.08.4 on Windows. STEPS TO REPRODUCE 1. Turn on the network share on the phone. 2. Connect the PC into that Wi-Fi network. 3. Use terminal simulator on the phone to confirm that the PC and the phone are in the same LAN. 4. Open KDE Connect and check devices list. The phone and the PC couldn't find each other. OBSERVED RESULT The phone and the PC couldn't find each other though they're in the same LAN. EXPECTED RESULT They can find each other and pair just like that in Windows. SOFTWARE/OS VERSIONS Windows: Windows 10 22H2, KDE Connect v23.08.4 Linux/KDE Plasma: Debian 12, KDE Connect v22.12.3-1 Phone: Android 10, KDE Connect v1.29.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 481344] New: Cannot receive photos sent from the Android client
https://bugs.kde.org/show_bug.cgi?id=481344 Bug ID: 481344 Summary: Cannot receive photos sent from the Android client Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: iOS Status: REPORTED Severity: normal Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: 0xdkxy.pollard...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Send any photo through kdeconnect android client 2. Cannot get that photo in iOS Files KDE Connect folder 3. OBSERVED RESULT Cannot receive the photo EXPECTED RESULT Receive that photo SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 481344] Cannot receive photos sent from the Android client
https://bugs.kde.org/show_bug.cgi?id=481344 Haoyu Li <0xdkxy.pollard...@gmail.com> changed: What|Removed |Added CC||0xdkxy.pollard...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 479333] Unable to print non-A4 page sizes correctly with KDE applications
https://bugs.kde.org/show_bug.cgi?id=479333 --- Comment #2 from Leisquid Li --- (In reply to Nate Graham from comment #1) > Can you please paste the output of running `locale` in a terminal window? Okay. Here is the output of running `locale` in Konsole: ``` LANG=zh_CN.UTF-8 LC_CTYPE="zh_CN.UTF-8" LC_NUMERIC="zh_CN.UTF-8" LC_TIME="zh_CN.UTF-8" LC_COLLATE="zh_CN.UTF-8" LC_MONETARY="zh_CN.UTF-8" LC_MESSAGES="zh_CN.UTF-8" LC_PAPER="zh_CN.UTF-8" LC_NAME="zh_CN.UTF-8" LC_ADDRESS="zh_CN.UTF-8" LC_TELEPHONE="zh_CN.UTF-8" LC_MEASUREMENT="zh_CN.UTF-8" LC_IDENTIFICATION="zh_CN.UTF-8" LC_ALL= ``` The language set in Plasma was Simplified Chinese when this problem was found in this environment. After that I set the language to English, did the same tests, and same problem occurred. Here is the output of running `locale` in the English environment: ``` LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= ``` -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 479333] Unable to print non-A4 page sizes correctly with KDE applications
https://bugs.kde.org/show_bug.cgi?id=479333 --- Comment #4 from Leisquid Li --- (In reply to Nate Graham from comment #3) > Thanks. Oh you're welcome. Best regards, Leisquid Li -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 Noah Li changed: What|Removed |Added CC||um...@tuta.io -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485769] Autologin settings for SSD not read from kde_settings.conf correctly
https://bugs.kde.org/show_bug.cgi?id=485769 Li Jiajun changed: What|Removed |Added CC||wlmq...@qq.com --- Comment #3 from Li Jiajun --- As a common user, I can reproduce this. Seems a regression. Version: sddm-kcm 6.0.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453406] New: Systemd startup: Changes to Autostart Programs require a reboot rather than a re-login to be applied
https://bugs.kde.org/show_bug.cgi?id=453406 Bug ID: 453406 Summary: Systemd startup: Changes to Autostart Programs require a reboot rather than a re-login to be applied Product: systemsettings Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: nicolas.fe...@gmx.de Reporter: eastern...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I have turned on systemd startup. After I change the Autostart Programs, re-login doesn't reflect the changes, but reboot does. STEPS TO REPRODUCE 1. add/remove a item in Autostart Programs 2. re-login 3. reboot OBSERVED RESULT 2: changes not yet effective 3: changes have taken effect EXPECTED RESULT Changes take effect after re-login, as when systemd startup is turned off. SOFTWARE/OS VERSIONS Linux: 5.17.5 systemd: 250.5 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453406] Systemd startup: Changes to Autostart Programs require a reboot rather than a re-login to be applied
https://bugs.kde.org/show_bug.cgi?id=453406 Eastern Li changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Eastern Li --- (In reply to David Edmundson from comment #2) > That's surprising. It should regenerate for the new session. I bet it ends > when that user's session restarts. Which is different from restarting, but > potentially different from logging out too i.e if you log out and have also > ssh'd in it wouldn't reload, but a logout that actually reaped everything > would. Thanks for your info. I noticed that when I logged out and returned to SDDM, there were some user processes that had not yet exited. It took a few seconds for them to exit. My previous re-login did not allow time for them to do so. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452949] New: Revert a string to make it suitable for more apps
https://bugs.kde.org/show_bug.cgi?id=452949 Bug ID: 452949 Summary: Revert a string to make it suitable for more apps Product: Akonadi Version: GIT (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: libakonadi Assignee: kdepim-b...@kde.org Reporter: eastern...@outlook.com Target Milestone: --- SUMMARY Akonadi is used in many apps, such as KMail, KOrganizer, Kalendar. The string (https://invent.kde.org/pim/akonadi/-/blob/master/src/widgets/cachepolicypage.ui#L118) is shown in the three apps, but only suits KMail. The previous string (https://invent.kde.org/pim/akonadi/-/commit/4c8cccb196bab944834bdd9e2ea3b869b173c970#bdbba614c22dab1d8eeec72026b4f2e87fa1361f_152_96) seems more suitable. STEPS TO REPRODUCE 1. Open one of the previously mentioned apps 2. Right click on the folder/calendar on the left 3. Click on Folder Properties/Edit Calendar 4. The string will appear in the Retrieve tab EXPECTED RESULT A string that suits all apps. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457417] Crash when trying to close a file after close project
https://bugs.kde.org/show_bug.cgi?id=457417 --- Comment #2 from X. Li --- (In reply to Christoph Cullmann from comment #1) > Could you try if the latest build here > > https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Nightly_win64/ > > Fixes it? You can just use the ZIP and execute Kate from it after extraction > without installation. Thanks for your reply. It looks like the latest build has redesigned its project module. It no longer has a 'Open Folder' command. Previous repro steps are no longer available. I've tried to open some files, the 'Documents' side window then show opened file names and their folders. If I choose to right click a folder and select 'Close' in the popup menu, the folder and all opened files in it will be closed as well. No crashes. Right now I cannot find any method to create a project. The 'Project' menu looks like empty and no controls available in 'Project' side window. That's all I can tell so far. Would you plz tell me if I've missed something? Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457417] Crash when trying to close a file after close project
https://bugs.kde.org/show_bug.cgi?id=457417 --- Comment #4 from X. Li --- (In reply to Christoph Cullmann from comment #3) > Hi, yeah, we had there some regression. > > Which build did you try? I would hope the latest 1676 should have this fixed. I tried build 1675. Now build 1676 has got 'Open Folder' command again. When I was trying to close a project, it requires all related opening files been closed as well. No other crash found. So the problem should have been fixed. Thank you :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457417] Crash when trying to close a file after close project
https://bugs.kde.org/show_bug.cgi?id=457417 --- Comment #6 from X. Li --- (In reply to Christoph Cullmann from comment #5) > Nice, we will update the store version soon, too, nice that the issue is > solved, crashes during work is always ugly... > > Thanks for testing it! It's a pleasure that I can help. Thank you for your efforts as well :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 441120] View difference does not work
https://bugs.kde.org/show_bug.cgi?id=441120 Eastern Li changed: What|Removed |Added CC|eastern...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457417] New: Crash when trying to close a file after close project
https://bugs.kde.org/show_bug.cgi?id=457417 Bug ID: 457417 Summary: Crash when trying to close a file after close project Product: kate Version: 22.04.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: fayfa...@outlook.com Target Milestone: --- SUMMARY While we can use 'project' side window to manage a folder, if we close a project when there're still some file in that project left opening, and then try to close that file, we got a crash. STEPS TO REPRODUCE 1. Open a folder. 2. In project side window, click a file to open it. 3. Click the close button in project side window to close the folder. 4. Click the close button at the file tab's right edge. (any other equivalent operation like using :bd command in vi mode leads to the same result) OBSERVED RESULT Kate crashed. Kate will only crash when we're trying to close a file in the recently closed project. It won't crash if the file is not related to the project. EXPECTED RESULT Opened file closed. SOFTWARE/OS VERSIONS Windows: Windows 10 21H2 KDE Plasma Version: 5.94.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Language: zh_CN Kate installed from Microsoft Store. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441349] New: latte-dock crash on system starts
https://bugs.kde.org/show_bug.cgi?id=441349 Bug ID: 441349 Summary: latte-dock crash on system starts Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: liyakun...@gmail.com Target Milestone: --- Application: latte-dock (0.10.0) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.8-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: The system just starts and latte-dock was set to auto start, but the latte-dock crash after system start without any additional operations. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fab89916200 (LWP 3421))] [KCrash Handler] #6 0x55c859e615fe in QString::QString (other=..., this=0x7ffd84121580) at /usr/include/qt5/QtCore/qstring.h:1093 #7 Latte::Layout::AbstractLayout::name (this=) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layout/abstractlayout.cpp:204 #8 Latte::Layouts::Synchronizer::currentLayoutsNames (this=) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layouts/synchronizer.cpp:202 #9 0x55c859e9521e in Latte::Layouts::Manager::currentLayoutsNames (this=) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layouts/manager.cpp:155 #10 Latte::Settings::Controller::Layouts::initLayouts (this=0x55c85c84d7a0) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/layoutscontroller.cpp:582 #11 0x55c859e5bce6 in Latte::Settings::Controller::Layouts::Layouts (parent=0x55c85c497290, this=0x55c85c84d7a0) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/layoutscontroller.cpp:75 #12 Latte::Settings::Handler::TabLayouts::TabLayouts (parent=0x55c85c035f10, this=0x55c85c497290) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/tablayoutshandler.cpp:54 #13 Latte::Settings::Dialog::SettingsDialog::SettingsDialog (parent=0x0, corona=, this=0x55c85c035f10) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/settingsdialog.cpp:69 #14 Latte::Layouts::Manager::showLatteSettingsDialog (this=0x55c85bf89f00, firstPage=0, toggleCurrentPage=) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layouts/manager.cpp:398 #15 0x55c859f1fd91 in LatteDockAdaptor::qt_static_metacall (_a=0x7ffd84121880, _id=10, _c=QMetaObject::InvokeMetaMethod, _o=0x55c85c0505c0) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/build/app/lattedockadaptor.moc:184 #16 LatteDockAdaptor::qt_metacall (this=0x55c85c0505c0, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7ffd84121880) at /usr/src/debug/latte-dock-0.10.0-1.1.x86_64/build/app/lattedockadaptor.moc:241 #17 0x7fab8c47f6bb in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=) at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190 #18 0x7fab8c4830ac in QDBusConnectionPrivate::activateCall (this=this@entry=0x7fab7800b910, object=0x55c85c0505c0, flags=flags@entry=273, msg=...) at qdbusintegrator.cpp:904 #19 0x7fab8c4835b9 in QDBusConnectionPrivate::activateCall (msg=..., flags=273, object=, this=0x7fab7800b910) at qdbusintegrator.cpp:853 #20 QDBusConnectionPrivate::activateObject (this=0x7fab7800b910, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1489 #21 0x7fab8c485e58 in QDBusActivateObjectEvent::placeMetaCall (this=0x55c85bdb6f60) at qdbusintegrator.cpp:1617 #22 0x7fab8c1a7f5e in QObject::event (this=0x7ffd84122240, e=0x55c85bdb6f60) at kernel/qobject.cpp:1314 #23 0x7fab8cfa9a7f in QApplicationPrivate::notify_helper (this=, receiver=0x7ffd84122240, e=0x55c85bdb6f60) at kernel/qapplication.cpp:3632 #24 0x7fab8c17b96a in QCoreApplication::notifyInternal2 (receiver=0x7ffd84122240, event=0x55c85bdb6f60) at kernel/qcoreapplication.cpp:1064 #25 0x7fab8c17e9b7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55c85bc854b0) at kernel/qcoreapplication.cpp:1821 #26 0x7fab8c1d37d3 in postEventSourceDispatch (s=s@entry=0x55c85bdaa6a0) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7fab8a54380f in g_main_dispatch (context=0x7fab80005000) at ../glib/gmain.c:3337 #28 g_main_context_dispatch (context=0x7fab80005000) at ../glib/gmain.c:4055 #29 0x7fab8a543b98 in g_main_context_iterate (context=context@entry=0x7fab80005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #30 0x7fab8a543c4f in g_main_context_iteration (context=0x7fab80005000, may_block=1) at ../glib/gmain.c:4196 #31 0x7fab8c1d2e54 in QEventDispatcherGlib::p
[kate] [Bug 441120] View difference does not work
https://bugs.kde.org/show_bug.cgi?id=441120 Eastern Li changed: What|Removed |Added CC||eastern...@outlook.com --- Comment #6 from Eastern Li --- Not work too. Operating System: Arch Linux kate and kompare Version: 21.08.01 without kdiff and meld kate open a new empty file (path: /tmp/tmp/kate.XX ), and there is a diff file (path: /tmp/kate.XX ) that should be opened by kompare. I try to restore changes(in following commits) in kate/katemwmodonhddialog.cpp in 340..355 lines, then it appears to work. https://invent.kde.org/utilities/kate/-/commit/edefa27760adc151d400c932ed88d5d942571080 https://invent.kde.org/utilities/kate/-/commit/3c0b2e30c9a6b133bfcd24e7ef3d4466da0031f7 https://invent.kde.org/utilities/kate/-/commit/a4f4008559488d6dbd433d0efa75798df575119f -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436871] New: Applet may open incorrect session
https://bugs.kde.org/show_bug.cgi?id=436871 Bug ID: 436871 Summary: Applet may open incorrect session Product: kate Version: 21.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: eastern...@outlook.com Target Milestone: --- SUMMARY If the name of a session contains characters that need to be escaped with %, an incorrect session will be opened when opening it with the applet. STEPS TO REPRODUCE 1. With the applet, create a new session and let its name is `%30`. 2. Close the correct session that was automatically opened. 3. Manually open the session `%30` with the applet. OBSERVED RESULT Session `0` will be (created and) opened. ADDITIONAL INFORMATION For non-ascii chars, such as `test测试` will open `test??`. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436871] Applet may open incorrect session
https://bugs.kde.org/show_bug.cgi?id=436871 --- Comment #1 from Eastern Li --- I tried editing `addons/sessionapplet/katesessionsjob.cpp`. Replace `QUrl::fromPercentEncoding(dest.toLatin1())` with `dest` on line 62. Now it seems to be working properly. But I am not sure if the source of the bug is that the function is passed the wrong (not encoded) parameter. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 --- Comment #12 from Grder Li --- (In reply to Eddi-Jay Ohlms from comment #10) > (In reply to Grder Li from comment #9) > > With some debugging, I found this seems to be related to the > > systemvolumeplugin-pulse plugin in some pluseaudio object lifecycles > > management. Crash is not happening anymore after disabling the systemvolume > > plugin from the desktop side. > > What is KDE using the plugin for? > Why does it do? > Does it limit usability in any way? It's for controlling PulseAudio volume from the phone. I don't really need this feature, so I disabled the plugin. Not sure how it would affect other users. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479333] New: Unable to print non-A4 page sizes correctly with KDE applications
https://bugs.kde.org/show_bug.cgi?id=479333 Bug ID: 479333 Summary: Unable to print non-A4 page sizes correctly with KDE applications Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: leisq...@outlook.com Target Milestone: --- SUMMARY When printing with KDE applications such as Gwenview and Okular, the final page size or scaling output to the printer is incorrect, even if the page size is set to any particular value. I originally found this problem when testing Canon printers. When I was printing with Gwenview and set the page size to a particular small size, some printers would print an image scaled to A4 size, while others would stop working and warn that the corresponding paper was missing - when querying the error details on the printer, it showed that the paper size required for the print job was A4. It was later tested that the output to the printer was still A4 regardless of the page size. Changing the default options for the printer didn't help. The same problem occurs with CUPS virtual PDF printers, not just Canon printers. But this problem doesn't occur if you print with non-KDE applications, such as GIMP or Chromium. I think that this bug is related to KDE applications, rather than printer drivers. STEPS TO REPRODUCE Take the CUPS virtual PDF printer as an example. If you have a physical printer, you can use it for testing as well. 1. Install cups and cups-pdf, and start the CUPS service. 2. Add a CUPS virtual PDF printer, or your physical printer. 3. Print an image or PDF document with any KDE application: open the "Print" dialog, click "Properties", and set Page size to a value different from A4. Orientation can also be set to "Portrait" or "Landscape". OBSERVED RESULT Printing results vary depending on the KDE application used. For example, when printing with Gwenview, the page size of the document output through the printer is A4, regardless of the page size selected; when printing with KolourPaint, the page size is correct, but the Orientation of the printed document is always Portrait, regardless of whether the Orientation is set to "Portrait" or "Landscape". EXPECTED RESULT Prints the correct image according to the page size and orientation settings. SOFTWARE/OS VERSIONS Operating System: Arch Linux x86_64 Kernel Version: 6.6.8-arch1-1 (64-bit) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Graphics Platform: X11 OpenPrinting CUPS Version: 2.4.7-2 ADDITIONAL INFORMATION When a picture is being printed, the contents of the picture are processed and placed in a SPOOLing queue with a file name usually "d-xxx", sometimes as a PDF document. You will find that the page size, orientation, and scaling of this document are all correct if you open it. So I'm wondering if maybe the KDE applications are outputting wrong information about the print job? Best regards, Leisquid Li -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 479333] Unable to print non-A4 page sizes correctly with KDE applications
https://bugs.kde.org/show_bug.cgi?id=479333 Leisquid Li changed: What|Removed |Added Assignee|unassigned-b...@kde.org |dantt...@gmail.com Component|general |general Product|kde |print-manager -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472793] New: merkuro-calendar crashes on startup (binding loop)
https://bugs.kde.org/show_bug.cgi?id=472793 Bug ID: 472793 Summary: merkuro-calendar crashes on startup (binding loop) Classification: Applications Product: kalendar Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: easter...@outlook.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY merkuro-calendar crashes because of binding loop when user requests Chinese UI > file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:32:9: > QML Loader (parent or ancestor of QQuickLayoutAttached): Binding loop > detected for property "maximumWidth" STEPS TO REPRODUCE 1. add a new linux user and login 2. run `merkuro-calendar` => work 3. run `LANG=zh_CN LANGUAGE= merkuro-calendar` => crash SOFTWARE/OS VERSIONS merkuro-calenda (Gear) 23.07.80 KDE Plasma Version: 5.27.6 (wayland) KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 (kde patched) -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472793] merkuro-calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472793 Eastern Li changed: What|Removed |Added Summary|merkuro-calendar crashes on |merkuro-calendar crashes on |startup (binding loop) |startup -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472793] merkuro-calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472793 --- Comment #2 from Eastern Li --- (In reply to brainpower from comment #1) > Any "LANG" which is not empty or C, does produce a crash: > > no crash: > LANG= merkuro-calendar > LANG=C merkuro-calendar > > crash: > LANG=C.UTF-8 merkuro-calendar > LANG=de_DE.UTF-8 merkuro-calendar > LANG=fr_FR.UTF-8 merkuro-calendar > LANG=en_US.UTF-8 merkuro-calendar > LANG=en_US merkuro-calendar not any LANG produce a crash `LANG=en_US.UTF-8 LANGUAGE=en_US merkuro-calendar` => work extra info: if rm/mv /usr/share/locale//LC_MESSAGES/libkirigami2plugin_qt.qm or libphonon_qt.qm, then the window is shown with mainly English UI. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471060] Filesystem sidebar context menu / Open with / [App] shows Choose Application dialog
https://bugs.kde.org/show_bug.cgi?id=471060 Gary Li changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/kate/-/commit/131b2e4 ||2e1456bbc7d3fd9afdba5bf73cc ||71589a Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Gary Li --- Git commit 131b2e42e1456bbc7d3fd9afdba5bf73cc71589a by Gary Li. Committed on 08/08/2023 at 19:26. Pushed by cullmann into branch 'master'. Fix open with in Filesystem view KateFileActions::showOpenWithMenu expects the desktop path to be given in the action's data as a string instead of as a StringList. M +1-0addons/filebrowser/katefilebrowser.cpp https://invent.kde.org/utilities/kate/-/commit/131b2e42e1456bbc7d3fd9afdba5bf73cc71589a -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 472085] New: NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc
https://bugs.kde.org/show_bug.cgi?id=472085 Bug ID: 472085 Summary: NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc Classification: Applications Product: NeoChat Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: litime...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY I tried to use craft to install neochat, but it failed during installation STEPS TO REPRODUCE 1. I installed craft on my pc, following https://community.kde.org/Get_Involved/development/Windows 2. `craft neochat` 3. The install process failed OBSERVED RESULT -- [0/1] Install the project... Install pdb: C:\CraftRoot\build\kde\frameworks\tier2\kcrash\image-RelWithDebInfo-5.101.0-dbg\bin\KF5Crash.pdb for KF5Crash.dll *** Action: post-install for kde/frameworks/tier2/kcrash *** *** Action: qmerge for kde/frameworks/tier2/kcrash *** *** Action: post-qmerge for kde/frameworks/tier2/kcrash *** *** Craft all succeeded: kde/frameworks/tier2/kcrash after 9 seconds *** *** Handling package: libs/mingw-crt4msvc, action: all *** *** Action: fetch-binary for libs/mingw-crt4msvc *** *** libs/mingw-crt4msvc not found in cache *** *** Action: fetch for libs/mingw-crt4msvc *** wget https://files.kde.org/craft/prebuilt/22.11/windows/gcc/x86_64/RelWithDebInfo/libs/runtime/runtime-11.2.0-2-62-20221115T215525-windows-gcc-x86_64.7z Action: fetch for libs/mingw-crt4msvc:22.11 FAILED *** Craft all failed: libs/mingw-crt4msvc after 0 seconds *** fatal error: package libs/mingw-crt4msvc all failed Craft stopped with out completing ['libs/mingw-crt4msvc', 'libs/gpg-error', 'libs/gcrypt', 'libs/cyrus-sasl', 'kdesupport/qca', 'libs/assuan2', 'libs/gpgme/gpgme', 'kde/frameworks/tier3/kwallet', 'kde/frameworks/tier3/ktextwidgets', 'kde/frameworks/tier3/kio', 'kde/plasma-mobile/neochat'] -- SOFTWARE/OS VERSIONS Windows: Windows 10 22H2 19045.3086 ADDITIONAL INFORMATION I tried `craft libs/mingw-crt4msvc`, but it failed too. Maybe this bug belongs to craft? -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 472085] NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc
https://bugs.kde.org/show_bug.cgi?id=472085 --- Comment #2 from Zhenbo Li --- Thanks Tobias I've tried various times, and I found wget failed very frequently. Is this caused by my internet condition (I assume it's good enough) or something at the server? ===full log=== PS C:\CraftRoot> craft libs/mingw-crt4msvc Craft : C:\CraftRoot Version : master ABI : windows-cl-msvc2019-x86_64 Download directory : C:\CraftRoot\download *** Handling package: dev-utils/7zip-base, action: all *** *** Action: fetch-binary for dev-utils/7zip-base *** *** dev-utils/7zip-base not found in cache *** *** Action: fetch for dev-utils/7zip-base *** wget https://files.kde.org/craft/3rdparty/7zip/2301/7z2301-extra.zip Action: fetch for dev-utils/7zip-base:23.01 FAILED *** Craft all failed: dev-utils/7zip-base after 0 seconds *** fatal error: package dev-utils/7zip-base all failed Craft stopped with out completing ['dev-utils/7zip-base', 'dev-utils/cmake-base', 'dev-utils/kshimgen', 'dev-utils/7zip', 'dev-utils/cmake', 'dev-utils/wget', 'dev-utils/git', 'python-modules/pip-system', 'python-modules/virtualenv', 'dev-utils/python3', 'python-modules/pip', 'virtual/bin-base', 'dev-utils/patch', 'dev-utils/sed', 'dev-utils/jom', 'dev-utils/ninja', 'virtual/craft-blueprints-kde-base', 'craft/craft-core', 'craft/craft-blueprints-kde', 'virtual/base', 'libs/mingw-crt4msvc'] -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 472085] NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc
https://bugs.kde.org/show_bug.cgi?id=472085 --- Comment #4 from Zhenbo Li --- (In reply to Ben Cooksley from comment #3) > If you'd prefer not to make that information public please email it to me > direct. Thank you. I've sent these info to your email. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463765] New: Reply, Boost, Favorite icons not loaded
https://bugs.kde.org/show_bug.cgi?id=463765 Bug ID: 463765 Summary: Reply, Boost, Favorite icons not loaded Classification: Applications Product: Tokodon Version: 22.11.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: litime...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 154981 --> https://bugs.kde.org/attachment.cgi?id=154981&action=edit screenshot for bug.png SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. just login The reply, boost and favourite icons are missing. See attachment EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION I installed it following 1. Install #KDECraft with #Powershell , see https://community.kde.org/Get_Involved/development/Windows 2. C:\CraftRoot\craft\craftenv.ps1 3. craft kitemmodels 4. craft qtkeychain 5. craft tokodon 6. tokodon (https://fediscience.org/@zhenboli/109622589813581062) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463765] Reply, Boost, Favorite icons not loaded
https://bugs.kde.org/show_bug.cgi?id=463765 --- Comment #1 from Zhenbo Li --- I just compiled the git version following these commands - cmake -G ninja - ninja - bin/tokodon.exe And I could see these icons. I think I should close this bug report? -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 357170] plasmashell loaded longer than ksplash
https://bugs.kde.org/show_bug.cgi?id=357170 Noah Li changed: What|Removed |Added CC||siheyua...@gmail.com --- Comment #4 from Noah Li --- I have the same issue. When ksplash quits I see plasma still loading and widgets not where they shuld have been. I think this defeats the purpose of a splash screen. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430247] New: Add Fine Control for Grid Spacing in Icons Mode
https://bugs.kde.org/show_bug.cgi?id=430247 Bug ID: 430247 Summary: Add Fine Control for Grid Spacing in Icons Mode Product: dolphin Version: 20.12.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: siheyua...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 133990 --> https://bugs.kde.org/attachment.cgi?id=133990&action=edit Demonstration of different grid spacing. SUMMARY It seems that Dolphin 20.12.0 has changed the grid spacing in icons mode. I have always been accustomed to the old "middle" spacing, but the new "middle" spacing is too wide while "small" spacing is too narrow. I wonder if there is any plan to implement fine control on grid spacing, provided that there is no way to adjust the default value of "middle" spacing. STEPS TO REPRODUCE 1. Upgrade to Dolphin 20.12.0; 2. Open some directory in icons mode; 3. Observe. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429904] translations missing everywhere, except the main window
https://bugs.kde.org/show_bug.cgi?id=429904 Noah Li changed: What|Removed |Added CC||siheyua...@gmail.com --- Comment #3 from Noah Li --- Same issue in version 20.12.0 but worse. Even the main window is not localized. The only place with localization is the language menu list in the "Settings → Configure Language" dialog... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 430463] New: Incorrect Display of Rendering Progress in Desktop Notification
https://bugs.kde.org/show_bug.cgi?id=430463 Bug ID: 430463 Summary: Incorrect Display of Rendering Progress in Desktop Notification Product: kdenlive Version: 20.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: siheyua...@gmail.com Target Milestone: --- Created attachment 134120 --> https://bugs.kde.org/attachment.cgi?id=134120&action=edit Rendering Progress - Kdenlive v.s. Desktop Notification SUMMARY The rendering progress as shown in the desktop notification is stuck at the beginning. Also the rendering speed is displayed as "$(num) B/s" while the corresponding speed as shown in Kdenlive is "$(num) fps". SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429904] translations missing everywhere, except the main window
https://bugs.kde.org/show_bug.cgi?id=429904 --- Comment #5 from Noah Li --- @emohr Yes I am on Linux. I am using the Kdenlive package provided by the official Arch repository. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 430561] New: Konversation Does Not Appear on Top when Called from Plasma System Tray
https://bugs.kde.org/show_bug.cgi?id=430561 Bug ID: 430561 Summary: Konversation Does Not Appear on Top when Called from Plasma System Tray Product: konversation Version: 1.8.201180 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: siheyua...@gmail.com Target Milestone: --- Created attachment 134196 --> https://bugs.kde.org/attachment.cgi?id=134196&action=edit When Konversation does not appear on top. SUMMARY Sometimes Konversation does not appear on top when called from Plasma system tray. I experimented a bit but cannot confirm what conditions make the window appear on top and what do not. None of the other windows is forced on top by KWin rules. STEPS TO REPRODUCE 1. Open Konversation and minimize it to Plasma system tray; 2. Click the tray icon to resume Konversation. OBSERVED RESULT Konversation appears above other windows. EXPECTED RESULT Sometimes Konversation appears beneath other windows. When this happens it will be shown highlighted in the taskbar. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 430561] Konversation Does Not Appear on Top when Called from Plasma System Tray
https://bugs.kde.org/show_bug.cgi?id=430561 --- Comment #1 from Noah Li --- *Sorry I messed up the observed and expected results in bug description but you get the idea. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488081] Scaling is not applied to SDDM when Applying Plasma Settings, always stays 1.0
https://bugs.kde.org/show_bug.cgi?id=488081 Li Jiajun changed: What|Removed |Added CC||wlmq...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 407637] Keyboard shortcuts stopped working
https://bugs.kde.org/show_bug.cgi?id=407637 Honghao Li changed: What|Removed |Added CC||i...@rasphino.cn --- Comment #1 from Honghao Li --- Created attachment 120130 --> https://bugs.kde.org/attachment.cgi?id=120130&action=edit kded5 crash screen record I press print key (associate with a custom shortcut) -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 407637] Keyboard shortcuts stopped working
https://bugs.kde.org/show_bug.cgi?id=407637 --- Comment #2 from Honghao Li --- SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 Kernel Version: 5.0.16-2-clear OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 15.6 GiB of RAM I have the same issue with mthw0. After login, KDEinit5 crash due to segmentation fault. Then if I use custom shortcuts, entries in Status and Notifications and global menu are gone, and kded5 crash. Then I start kded5 from terminal and make a screen record. If I press Print key, which is associated with a custom shortcut, kded5 will crash... -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 407637] Keyboard shortcuts stopped working
https://bugs.kde.org/show_bug.cgi?id=407637 --- Comment #3 from Honghao Li --- Created attachment 120131 --> https://bugs.kde.org/attachment.cgi?id=120131&action=edit kdeinit5 crash log crash log about crashed kdeinit5 when I login -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 407637] Keyboard shortcuts stopped working
https://bugs.kde.org/show_bug.cgi?id=407637 --- Comment #4 from Honghao Li --- Created attachment 120132 --> https://bugs.kde.org/attachment.cgi?id=120132&action=edit kded5 running log KCrash didn't show up when kded5 crash -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 407637] Keyboard shortcuts stopped working
https://bugs.kde.org/show_bug.cgi?id=407637 --- Comment #7 from Honghao Li --- Created attachment 120139 --> https://bugs.kde.org/attachment.cgi?id=120139&action=edit kded5 crash log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407624] SNI not working on 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407624 Honghao Li changed: What|Removed |Added CC||i...@rasphino.cn -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 407614] kded_touchpad crashes at startup
https://bugs.kde.org/show_bug.cgi?id=407614 --- Comment #24 from Honghao Li --- (In reply to Roman Gilg from comment #19) > Can you guys, who experienced this issue test the new revision at: > https://phabricator.kde.org/D21278 This works for me, thx! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407529] NVIDIA display issues on wake from suspend
https://bugs.kde.org/show_bug.cgi?id=407529 Honghao Li changed: What|Removed |Added CC||i...@rasphino.cn -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407529] NVIDIA display issues on wake from suspend
https://bugs.kde.org/show_bug.cgi?id=407529 Honghao Li changed: What|Removed |Added CC|i...@rasphino.cn | -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 407614] kded_touchpad crashes at startup
https://bugs.kde.org/show_bug.cgi?id=407614 Honghao Li changed: What|Removed |Added CC||i...@rasphino.cn --- Comment #31 from Honghao Li --- My kded5 still crash when wake up from suspend. I use archlinux with KDE 5.16. Here is my kded5 crash log: Application: kded5 (kded5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f06c82b33c0 (LWP 19704))] Thread 6 (Thread 0x7f06b77fe700 (LWP 19709)): #0 0x7f06ccb500d1 in poll () at /usr/lib/libc.so.6 #1 0x7f06ca5ba7c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f06ca5ba8ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f06cb95bba4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f06cb90519c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f06cb73f9e9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f06cb740dec in () at /usr/lib/libQt5Core.so.5 #7 0x7f06cb4d3a92 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f06ccb5acd3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f06b7fff700 (LWP 19708)): #0 0x7f06ccb4bc54 in read () at /usr/lib/libc.so.6 #1 0x7f06ca568961 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f06ca5b8f70 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f06ca5ba766 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f06ca5bb7f2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7f06bd0cc508 in () at /usr/lib/libgio-2.0.so.0 #6 0x7f06ca595f21 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f06cb4d3a92 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f06ccb5acd3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f06bcd12700 (LWP 19707)): #0 0x7f06ccb500d1 in poll () at /usr/lib/libc.so.6 #1 0x7f06ca5ba7c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f06ca5ba8ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f06ca5ba902 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f06ca595f21 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f06cb4d3a92 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f06ccb5acd3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f06bf4ea700 (LWP 19706)): #0 0x7f06ca568420 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f06ca5ba7b5 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f06ca5ba8ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f06cb95bba4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f06cb90519c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f06cb73f9e9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f06cbc6fba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f06cb740dec in () at /usr/lib/libQt5Core.so.5 #8 0x7f06cb4d3a92 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f06ccb5acd3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f06c6903700 (LWP 19705)): #0 0x7f06ccb500d1 in poll () at /usr/lib/libc.so.6 #1 0x7f06ca52f630 in () at /usr/lib/libxcb.so.1 #2 0x7f06ca5312db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f06c74d5bd9 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f06cb740dec in () at /usr/lib/libQt5Core.so.5 #5 0x7f06cb4d3a92 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f06ccb5acd3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f06c82b33c0 (LWP 19704)): [KCrash Handler] #6 0x7f069a054280 in () at /usr/lib/qt/plugins/kded_touchpad.so #7 0x7f069a047c06 in () at /usr/lib/qt/plugins/kded_touchpad.so #8 0x7f06cb9314d7 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #9 0x7f069a054764 in () at /usr/lib/qt/plugins/kded_touchpad.so #10 0x7f069a054810 in () at /usr/lib/qt/plugins/kded_touchpad.so #11 0x7f069a05487e in () at /usr/lib/qt/plugins/kded_touchpad.so #12 0x7f06cb9314d7 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #13 0x7f06cb93cf6a in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #14 0x7f06cb93d2c2 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f06cc546f04 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7f06cc54e541 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f06cb906609 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #18 0x7f06cb95c806 in () at /usr/lib/libQt5Core.so.5 #19 0x7f06ca5b890f in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #20 0x7f06ca5ba869 in () at /usr/lib/libglib-2.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 Honghao Li changed: What|Removed |Added CC||i...@rasphino.cn -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411377] New: It is hard to see the words if the font size is too small in text editor.
https://bugs.kde.org/show_bug.cgi?id=411377 Bug ID: 411377 Summary: It is hard to see the words if the font size is too small in text editor. Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: coleman_...@hotmail.com Target Milestone: --- Created attachment 122398 --> https://bugs.kde.org/attachment.cgi?id=122398&action=edit Krita Text Editor snapshot SUMMARY It is hard to see the words if the font size is too small（e.g. font size 6） in text editor. If i have 30 words in text editor's text box then it is not convinent if i want to edit the words. STEPS TO REPRODUCE 1. input many words(for example 50 words) in text editor. 2. change font size to 6. 3. then hard to see becuase too small. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411377] It is hard to see the words if the font size is too small in text editor.
https://bugs.kde.org/show_bug.cgi?id=411377 Jeff Li changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED|RESOLVED --- Comment #2 from Jeff Li --- (In reply to Boudewijn Rempt from comment #1) > I'm afraid there isn't much we can do about it. For some reason, Qt's text > editor component implements zoom through setting the font size, and we > haven't yet found a way around that. Thank you. I wish Krita could improve it someday. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411377] It is hard to see the words if the font size is too small in text editor.
https://bugs.kde.org/show_bug.cgi?id=411377 --- Comment #4 from Jeff Li --- (In reply to Boudewijn Rempt from comment #3) > Ah, no please, leave the report open -- it really is a problem so we'll have > to figure out a way around in any case. Ok, thank you. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413542] Can't UNbind Meta+Space from the global shortcuts
https://bugs.kde.org/show_bug.cgi?id=413542 Jacob Li changed: What|Removed |Added CC||jacobthepolym...@gmail.com --- Comment #10 from Jacob Li --- I've got exactly the same problem. Meta+Space for KRunner is default but there's not a way to change it. Did some search. Perhaps it has to do with this recent change? https://phabricator.kde.org/D24033 Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.0.0-36-generic OS Type: 64-bit Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31.4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413542] Can't UNbind Meta+Space from the global shortcuts
https://bugs.kde.org/show_bug.cgi?id=413542 --- Comment #13 from Jacob Li --- Per my test, Nate's workaround will work for newly created users. For an existing user, I think they also need to modify $HOME/.config/kglobalshortcutsrc . I edited out all occurrences of Meta+Space in the [krunner.desktop] section, and the problem is fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401001] New: media controller notification card's layout issue
https://bugs.kde.org/show_bug.cgi?id=401001 Bug ID: 401001 Summary: media controller notification card's layout issue Product: kdeconnect Version: 1.10 Platform: Android OS: Android 8.x Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: honghao...@outlook.jp Target Milestone: --- Created attachment 116280 --> https://bugs.kde.org/attachment.cgi?id=116280&action=edit screenshot SUMMARY media controller notification card's layout issue space between media controller's album image and next song button are missing. STEPS TO REPRODUCE 1. play music on the computer side 2. on the phone side, open the notification card OBSERVED RESULT Please look at my screenshot. EXPECTED RESULT there should be some space between the next button and the album image. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Android: 8.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 403821] New: Kate freezes when typing "config" with Kconfig mode
https://bugs.kde.org/show_bug.cgi?id=403821 Bug ID: 403821 Summary: Kate freezes when typing "config" with Kconfig mode Product: kate Version: 18.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: i...@rasphino.cn Target Milestone: --- Created attachment 117768 --> https://bugs.kde.org/attachment.cgi?id=117768&action=edit OBSERVED RESULT SUMMARY Kate freezes when typing "config" with Kconfig mode STEPS TO REPRODUCE 1. set "Mode" to "Configuration" -> "Kconfig" 2. type "config" OBSERVED RESULT Kate freezes with "confi" EXPECTED RESULT Kate display "config" normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 Honghao Li changed: What|Removed |Added CC||i...@rasphino.cn -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398879] New: nvidiafb and Falkon => content of window is all black
https://bugs.kde.org/show_bug.cgi?id=398879 Bug ID: 398879 Summary: nvidiafb and Falkon => content of window is all black Product: Falkon Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: now...@gmail.com Reporter: sexxxena...@gmail.com Target Milestone: --- Created attachment 115125 --> https://bugs.kde.org/attachment.cgi?id=115125&action=edit Content is all black but site is correclty loaded with nvidiafb Hi, Since the "nouveau" drivers crashed my machine on a regular basis, I switched to nvidiafb (FYI it's an old - ~15 years -, but perfectly functional desktop, with a "GeForce 7600 GS" video card)). With this change, it's working perfectly, apart for Falkon: whatever site I go to, the content of Falkon's window - the webpage content part - is always all black - the menus and bars are OK. If I use the mouse in the page, I can copy-paste text, so I know Falkon is actually loading the pages correctly, it's just a display bug... -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398879] nvidiafb and Falkon => content of window is all black
https://bugs.kde.org/show_bug.cgi?id=398879 LI AR changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from LI AR --- Hi, Thanks for your quick answer. Both did the trick! Thanks a lot, Falkon is so light&fast, I'm so happy to be able to use it again !!! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395354] New: Configuration of "Double Click to open file" not available
https://bugs.kde.org/show_bug.cgi?id=395354 Bug ID: 395354 Summary: Configuration of "Double Click to open file" not available Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: liyakun...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- Created attachment 113304 --> https://bugs.kde.org/attachment.cgi?id=113304&action=edit configuration of mouse click Single/double click setting is not available in the Mouse configuration. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395354] Configuration of "Double Click to open file" not available
https://bugs.kde.org/show_bug.cgi?id=395354 Yakun Li changed: What|Removed |Added Platform|Other |Neon Packages Version|unspecified |5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450014] Unable to switch input method in Overview search
https://bugs.kde.org/show_bug.cgi?id=450014 Li Jiajun changed: What|Removed |Added CC||wlmq...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 495293] New: Error in displaying and saving annotates with Chinese charactor
https://bugs.kde.org/show_bug.cgi?id=495293 Bug ID: 495293 Summary: Error in displaying and saving annotates with Chinese charactor Classification: Applications Product: okular Version: 23.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: woshilizhi...@hotmail.com Target Milestone: --- SUMMARY Okular cannot display text comment which includes Chinese charactor. OBSERVED RESULT English annotate and comments are displayed normally. Text comments including Chinese charactor can be added in Okular and displayed normally in other PDF readers such as Firefox. They cannot be displayed in Okular. Also, Okular warns that there're mistakes in file. All of the saving actions are made in Okular. EXPECTED RESULT ALL of the contents are displayed and saved normally. SOFTWARE/OS VERSIONS Windows: Windows 10 22H2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 492945] Power Management is not available when autologin enabled
https://bugs.kde.org/show_bug.cgi?id=492945 Li Jiajun changed: What|Removed |Added CC||wlmq...@qq.com --- Comment #2 from Li Jiajun --- I have this problem too, It is caused by https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/commit/8277adb7cd89293fd4d32407eee1596ffbf6acce This commit is supposed to prevent potential race conditions, so maybe a better solution is needed rather than reverting that? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 492859] Power Management Applet doesn't detect power-profiles-daemon
https://bugs.kde.org/show_bug.cgi?id=492859 Li Jiajun changed: What|Removed |Added CC||wlmq...@qq.com --- Comment #6 from Li Jiajun --- This is caused by https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/commit/8277adb7cd89293fd4d32407eee1596ffbf6acce ppd starts too late for powerdevil -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 495918] New: batterymonitor applet cannot detect TLP
https://bugs.kde.org/show_bug.cgi?id=495918 Bug ID: 495918 Summary: batterymonitor applet cannot detect TLP Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: plasma-b...@kde.org Reporter: wlmq...@qq.com CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY As of plasma 6.2.3, there is a regression causing the function cannot determine whether tlp exist. The applet will always show the alert that ppd not installed. STEPS TO REPRODUCE 1. Install tlp and uninstall ppd 2. start plasmashell 3. open applet and see what happened OBSERVED RESULT Applet cannot detect if tlp is installed EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: no macOS: no (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 6.2.3 KDE Plasma Version: 6.2.3 KDE Frameworks Version: not associated Qt Version: not associated ADDITIONAL INFORMATION the MR introduce this issue: https://invent.kde.org/plasma/powerdevil/-/merge_requests/454 fix: https://invent.kde.org/plasma/powerdevil/-/merge_requests/461 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 495918] batterymonitor applet cannot detect TLP
https://bugs.kde.org/show_bug.cgi?id=495918 Li Jiajun changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499533] New: Frequently toggling fullscreen causing window flickering
https://bugs.kde.org/show_bug.cgi?id=499533 Bug ID: 499533 Summary: Frequently toggling fullscreen causing window flickering Classification: Plasma Product: kwin Version: 6.2.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: wlmq...@qq.com Target Milestone: --- Created attachment 177981 --> https://bugs.kde.org/attachment.cgi?id=177981&action=edit OBSERVED RESULT: flickering when toggling full-screen SUMMARY If I continuously press full-screen toggling shortcut, frequently switch between full-screen modes, occasionally the underlying window is revealed, causing flickering. Regarding the use case, there isn’t any particular scenario that demands rapid switching full-screen. So not a big deal anyway. Just Kwin would be better without the flickering. STEPS TO REPRODUCE For firefox: 1. Open Firefox 2. Toggle fullscreen mode frequently (For firefox it’s long-press F11) For other app (like mpv or konsole): 1. Bind fullscreen shortcut key to whatever U like. 2. Rapidly tap the full screen key (long-pressing seems works too). OBSERVED RESULT There will be split-second of exposing the window underneath the current one, causing flickering. See upload gif:OBSERVED_RESULT.gif EXPECTED RESULT Getting window always showup and follow right z-index when switching full-screen mode. For comparison, There is a Win11 24h2 one. Win11 not behave the best, there also some drawback on compositor. See upload gif:EXPECTED_RESULT.gif SOFTWARE/OS VERSIONS Windows: Not affected macOS: Not affected Linux/KDE Plasma: Manjaro KDE Plasma 6.2.5 Wayland and X11 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.13.0-1-MANJARO (AMD64) ADDITIONAL INFORMATION Initial conversation: https://discuss.kde.org/t/frequently-toggling-fullscreen-causing-window-flickering/29153 Can reproduced on both: AMD 7840HS Laptop AMD Ryzen 3700x, Radeon Vega56 platform More system information, See upload txt: inxi.txt -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 503571] New: Add Dark Mode Support to SDDM Theme with Grey Password Field Background for Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=503571 Bug ID: 503571 Summary: Add Dark Mode Support to SDDM Theme with Grey Password Field Background for Breeze Dark Classification: Plasma Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Color scheme Assignee: plasma-b...@kde.org Reporter: uywe...@gmail.com Target Milestone: --- Created attachment 180808 --> https://bugs.kde.org/attachment.cgi?id=180808&action=edit Example for comparison When using the Breeze Dark theme, the SDDM login screen’s password box and login button defaults to a white background. This differs from KDE lock screen,disrupting system visual consistency. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504566] New: Audio volume applet experiences GUI introduced thread blocking when sliding volume slider with a high polling rate mouse
https://bugs.kde.org/show_bug.cgi?id=504566 Bug ID: 504566 Summary: Audio volume applet experiences GUI introduced thread blocking when sliding volume slider with a high polling rate mouse Classification: Plasma Product: plasmashell Version First 6.3.5 Reported In: Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Audio Volume widget Assignee: plasma-b...@kde.org Reporter: wlmq...@qq.com CC: isma...@gmail.com Target Milestone: 1.0 Created attachment 181568 --> https://bugs.kde.org/attachment.cgi?id=181568&action=edit A GIF showing the issue of GUI Animation rendering thread blocking issue of PA applet. SUMMARY I noticed that when I use a gaming mouse with a high polling rate (1000Hz) to drag the volume slider of the Plasma PulseAudio Applet, there is a significant delay due to GUI rendering thread blocking. STEPS TO REPRODUCE 1. Use a gaming mouse with a 1000Hz report rate. 2. Drag the volume slider of the PulseAudio Applet back and forth. OBSERVED RESULT There is noticeable delay and lag in volume adjustment, slider movement, and OSD animation. See the attached image for reference. EXPECTED RESULT When using a high-report-rate input device, the computing does not need to be so precise. Reducing the computational burden of animations or preferably handling related logic asynchronously would be ideal. SOFTWARE/OS VERSIONS Windows: Not relevant macOS: Not relevant (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Manjaro / Plasma 6.3.5 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 ADDITIONAL INFORMATION See the attached Gif image for reference. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] New: Task batch management
https://bugs.kde.org/show_bug.cgi?id=467312 Bug ID: 467312 Summary: Task batch management Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: BatchQueueManager-Core Assignee: digikam-bugs-n...@kde.org Reporter: san.li@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. selecte mp4 2. Apply Metadata Template 3. selecte templates 4. perform tasks OBSERVED RESULT Unable to process item EXPECTED RESULT Item processed successfully ADDITIONAL INFORMATION Batch operations on parent folders (including subfolders) are currently not available -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] Applying a template in the BQM fails in MP4 files
https://bugs.kde.org/show_bug.cgi?id=467312 san.li@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from san.li@gmail.com --- (In reply to Maik Qualmann from comment #1) > Writing to MP4 files will only be possible in digiKam-8.0.0 with activated > ExifTool support. > > Maik Hi Maik Most of the time I want to batch write metadata or templates to multiple folders, even rename them, and convert them to other formats such as webp. Probably digikam already implements these functions, but I didn't find a way to use them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] Applying a template in the BQM fails in MP4 files
https://bugs.kde.org/show_bug.cgi?id=467312 san.li@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from san.li@gmail.com --- (In reply to Maik Qualmann from comment #4) > https://docs.digikam.org/en/batch_queue.html > > Maik Thanks, Maik, I'm aware of the documentation, but it doesn't seem to solve my problem: Doing operations on images in multiple folders (a parent folder with multiple subfolders), such as writing metadata or writing Template with copyright information. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] Applying a template in the BQM fails in MP4 files
https://bugs.kde.org/show_bug.cgi?id=467312 --- Comment #7 from san.li@gmail.com --- (In reply to Maik Qualmann from comment #6) > You can also display sub-albums in the main view via the view menu and then > mark the corresponding images and add them to the BQM. This is the intended > workflow. Templates can be applied and in digiKam-8.0.0 also captions and > labels. We already have bug reports requests for more metadata. > > Maik Thank you very much. According to the method you provided, I can select all the pictures that need batch processing before entering BQM. Although this is more cumbersome than freely selecting folders and files after entering BQM, at least there is a solution, which is good start. Looking forward to more surprises in subsequent versions. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 456204] New: Zmodem receive feature doesn't work
https://bugs.kde.org/show_bug.cgi?id=456204 Bug ID: 456204 Summary: Zmodem receive feature doesn't work Product: konsole Version: 22.04.2 Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: lwhsu@lwhsu.org Target Milestone: --- SUMMARY When downloading a file from remote machine with zmodem, there is no window pops out and asks where to save file. STEPS TO REPRODUCE 1. Use konsole and ssh login a remove machine 2. Use lsz to send a file with zmodem OBSERVED RESULT Session is blocking. EXPECTED RESULT A windows pops out and ask where to save file. SOFTWARE/OS VERSIONS FreeBSD: 13.1-RELEASE (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15 ADDITIONAL INFORMATION Reverting https://invent.kde.org/utilities/konsole/-/commit/5557840822b193d1df48c145e3f1182993a30632 restores the old behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364082] New: Crash on start when no binary nvidia driver is available
https://bugs.kde.org/show_bug.cgi?id=364082 Bug ID: 364082 Summary: Crash on start when no binary nvidia driver is available Product: kdenlive Version: 16.04.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: lionghosts...@gmail.com It always crashes when no binary nvidia driver is installed. After I install the driver, it does not crash. It also occurs on fedora 23. Reproducible: Always Steps to Reproduce: 1. Install a clean ubuntu 16.04 2. Install kdenlive from kdenlive-test 3. Launch it Actual Results: Crash immediately Expected Results: Normal launch -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available
https://bugs.kde.org/show_bug.cgi?id=364082 --- Comment #3 from Yueqi Li --- I switched to Ubuntu. The problem still persists if I use open-source driver . Removing cache at "/home/leo/.cache/kdenlive-thumbs.kcache" // / processing file open // / processing file open: validate OpenGL vendor: "Intel Open Source Technology Center" OpenGL renderer: "Mesa DRI Intel(R) Haswell Mobile " OpenGL ARG_SYNC: true OpenGL OpenGLES: false Segmentation fault (core dumped) If I use nvidia driver. It works on nvidia binary driver. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available
https://bugs.kde.org/show_bug.cgi?id=364082 --- Comment #5 from Yueqi Li --- Removing cache at "/home/leo/.cache/kdenlive-thumbs.kcache" // / processing file open // / processing file open: validate klauncher not running... launching kdeinit kdeinit5: preparing to launch 'libkdeinit5_klauncher' kdeinit5: Launched KLauncher, pid = 2422, result = 0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :0 kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' OpenGL vendor: "Intel Open Source Technology Center" OpenGL renderer: "Mesa DRI Intel(R) Haswell Mobile " OpenGL ARG_SYNC: true OpenGL OpenGLES: false [New Thread 0x7fffa2cd7700 (LWP 2425)] Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault. 0x72457630 in QOpenGLContext::shareGroup() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe2cb5700 (LWP 2411)] [New Thread 0x7fffd997c700 (LWP 2412)] [New Thread 0x7fffd917b700 (LWP 2413)] [New Thread 0x7fffd897a700 (LWP 2414)] [New Thread 0x7fffcbfff700 (LWP 2415)] [Thread 0x7fffd897a700 (LWP 2414) exited] [New Thread 0x7fffd897a700 (LWP 2416)] [New Thread 0x7fffab0f6700 (LWP 2417)] [New Thread 0x7fffaa0f5700 (LWP 2418)] [New Thread 0x7fffa9818700 (LWP 2419)] Removing cache at "/home/leo/.cache/kdenlive-thumbs.kcache" // / processing file open // / processing file open: validate klauncher not running... launching kdeinit kdeinit5: preparing to launch 'libkdeinit5_klauncher' kdeinit5: Launched KLauncher, pid = 2422, result = 0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :0 kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' OpenGL vendor: "Intel Open Source Technology Center" OpenGL renderer: "Mesa DRI Intel(R) Haswell Mobile " OpenGL ARG_SYNC: true OpenGL OpenGLES: false [New Thread 0x7fffa2cd7700 (LWP 2425)] Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault. 0x72457630 in QOpenGLContext::shareGroup() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (gdb) thread apply all bt Thread 11 (Thread 0x7fffa2cd7700 (LWP 2425)): #0 0x714ffe8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fffee42531c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffee42542c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x72135a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x720dcdea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x71ef98a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x71efe84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fffefe2d6fa in start_thread (arg=0x7fffa2cd7700) at pthread_create.c:333 #8 0x7150bb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7fffa9818700 (LWP 2419)): #0 0x714ffe8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fffee42531c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffee42542c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x72135a7f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x720dcdea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x71ef98a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x72caa3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x71efe84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fffefe2d6fa in start_thread (arg=0x7fffa9818700) at pthread_create.c:333 #9 0x7150bb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fffaa0f5700 (LWP 2418)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x71effa26 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x71efb4d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x71efe84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fffefe2d6fa in start_thread (arg=0x7fffaa0f5700) at pth
[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available
https://bugs.kde.org/show_bug.cgi?id=364082 --- Comment #7 from Yueqi Li --- Does glxgears run, or also crash? It works in both drivers. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available
https://bugs.kde.org/show_bug.cgi?id=364082 --- Comment #9 from Yueqi Li --- When can you fix it? -- You are receiving this mail because: You are watching all bug changes.
[Artikulate] [Bug 363250] New: It is empty on the GUI
https://bugs.kde.org/show_bug.cgi?id=363250
Bug ID: 363250
Summary: It is empty on the GUI
Product: Artikulate
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: cordlandw...@kde.org
Reporter: liyaowang2...@gmail.com
It is totally empty on the GUI after artikulate was booted, also happened when
you open the sub-windows, like the windows of download course.
when I booted from the terminal, then some information was showed which could
be useful to find the bug.
log_liblearner: Database path:
"/home/li/.local/share/artikulate/learnerdata.db"
log_liblearner: No last active profile found, falling back to first found
profile
log_libsound: Load Plugin: "GStreamer Backend"
There is no subdirectory "skeletons" in directory "." cannot load skeletons.
There is no subdirectory "courses" in directory "." cannot load courses.
qrc:/artikulate/qml/Main.qml:182: ReferenceError: courseFilterModel is not
defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:186:9: QML
Binding: Property 'raised' does not exist on Item.
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:137:9: QML
Binding: Property 'raised' does not exist on Item.
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:186:9: QML
Binding: Property 'raised' does not exist on Item.
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:137:9: QML
Binding: Property 'raised' does not exist on Item.
knewstuff: Initializing KNS3::Engine from ' "artikulate.knsrc" '
No frame loaded
No frame loaded
No frame loaded
knewstuff: Loading KNewStuff3 config: "artikulate.knsrc"
knewstuff: Categories: ()
knewstuff: Using registry file:
"/home/li/.local/share/knewstuff3/artikulate.knsregistry"
knewstuff: Loading KNS2 registry of files for the component: "artikulate"
knewstuff: Cache read... entries: 0
knewstuff: loading providers from
"http://edu.kde.org/artikulate/downloads/providers.xml";
knewstuff: XmlLoader::load(): url:
QUrl("http://edu.kde.org/artikulate/downloads/providers.xml";)
klauncher not running... launching kdeinit
klauncher not running... launching kdeinit
klauncher not running... launching kdeinit
klauncher not running... launching kdeinit
couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher5
was not provided by any .service files"
There is no subdirectory "skeletons" in directory "." cannot load skeletons.
There is no subdirectory "courses" in directory "." cannot load courses.
knewstuff: Write registry
--
Note: My system is arch linux with the gnome desktop environment. The program
artikulate is under the KDE, therefore, it could be factor need to be
considered.
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[Artikulate] [Bug 363250] It is empty on the GUI
https://bugs.kde.org/show_bug.cgi?id=363250 --- Comment #1 from Yaowang Li --- Created attachment 99062 --> https://bugs.kde.org/attachment.cgi?id=99062&action=edit The screenshot of the main window -- You are receiving this mail because: You are watching all bug changes.
[Artikulate] [Bug 363250] It is empty on the GUI
https://bugs.kde.org/show_bug.cgi?id=363250 --- Comment #2 from Yaowang Li --- Created attachment 99063 --> https://bugs.kde.org/attachment.cgi?id=99063&action=edit the screenshot windows of the download course -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363477] New: the vim mode is not working with kate after enable it
https://bugs.kde.org/show_bug.cgi?id=363477 Bug ID: 363477 Summary: the vim mode is not working with kate after enable it Product: kate Version: 5.0.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Vi Input Mode Assignee: kwrite-bugs-n...@kde.org Reporter: liyakun...@gmail.com the vim mode is not working with kate after enable it Reproducible: Always Expected Results: The expected result is that I can use vim command to work like in kde4 -- You are receiving this mail because: You are watching all bug changes.
