[kwin] [Bug 489623] Maximizing window while panel is floating causes screen glitches
https://bugs.kde.org/show_bug.cgi?id=489623 CUI Hao changed: What|Removed |Added CC||cuihao@gmail.com --- Comment #1 from CUI Hao --- Created attachment 171483 --> https://bugs.kde.org/attachment.cgi?id=171483=edit Screen recording, showing glitches when maximizing a window I also encountered the issue on Arch Linux + Plasma 6.1.2 + Wayland. I have two screens. It only happened on the screen with the panel. And disabling floating panel solves the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477684] dolphin --daemon Crashes Peacefully After Opening First Window Through DBus
https://bugs.kde.org/show_bug.cgi?id=477684 John Hao changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477684] dolphin --daemon Crashes Peacefully After Opening First Window Through DBus
https://bugs.kde.org/show_bug.cgi?id=477684 --- Comment #2 from John Hao --- (In reply to David Edmundson from comment #1) > dolphin --daemon existing is somewhat expected. > This should be fine, the point of the above file is that we're dbus > activated and will get launched again. > > I'm a bit confused from the message. > If you don't launch any dolphins and run > > dbus org.freedesktop.FileManager1 /org/freedesktop/FileManager1 > org.freedesktop.FileManager1.ShowFolders /home asdf > > do you get a dolphin window > > if you close it and run it again do you get a dolphin window. This is curious... the "dbus" command is not found on my system. I have instead used gdbus and the command: gdbus call -e -d org.freedesktop.FileManager1 -o /org/freedesktop/FileManager1 -m org.freedesktop.FileManager1.ShowFolders \[\'/home\'\] "asdf" This returns () and no window, both the first and the consequent times. (this is expected as dolphin no longer opens a window even at the first time). This does open a window if "dolphin --daemon" is ran, and peacefully exits the "dolphin --daemon" process, showing the command is working. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477684] New: dolphin --daemon Crashes Peacefully After Opening First Window Through DBus
https://bugs.kde.org/show_bug.cgi?id=477684 Bug ID: 477684 Summary: dolphin --daemon Crashes Peacefully After Opening First Window Through DBus Classification: Applications Product: dolphin Version: 23.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: johnhaoallw...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin does not spawn a window when called with DBus using FileManager1 (through Firefox or directly) without an active process, and the process crashes peacefully when interacting with it through DBus after opening its first window. (I may not be using the right term of crash as the exit may be intentional, but the exit incorrectly interferes with using Dolphin from DBus) I cannot upload the backtrace: I am unfamiliar with gdb and when following the guide, backtrace.txt is empty due to the crashing process crashing peacefully. STEPS TO REPRODUCE 1. Override /usr/share/dbus-1/services/org.freedesktop.FileManager1.service in .local ~/.local/share/dbus-1/services/org.freedesktop.FileManager1.service: ``` [D-BUS Service] Name=org.freedesktop.FileManager1 Exec=/usr/bin/dolphin --daemon SystemdService=plasma-dolphin.service ``` 2. Use Firefox's "open in folder" for Downloads OBSERVED RESULT Dolphin window does not appear, except for the first time after a reboot. EXPECTED RESULT Dolphin window appears. SOFTWARE/OS VERSIONS Linux: Fedora 39 Sericea, SwayWM (not KDE Plasma) Qt Version: 5.15.11 / 6.6.0 ADDITIONAL INFORMATION Upon spamming the open in folder button at a rapid pace, the dolphin window appears. Firefox appears to be using DBus for "open in folder". Using d-feet, I interacted with the org.freedesktop.FileManager1, which shows it spawns a dolphin process. Using its ShowFolders interface removes the dolphin process and shows nothing. Running dolphin --daemon in a terminal connects it to the FileManager1 DBus and allows Firefox to open a folder once, but after opening this folder, dolphin --daemon peacefully exits. The peaceful exit after opening folder also happens when using FileManager1 DBus directly through d-feet, and using org.kde.dolphin-pid through d-feet. It does not happen when running dolphin --new-window from another command line. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475546] New: Unable to grab mouse cursor on Wayland
https://bugs.kde.org/show_bug.cgi?id=475546 Bug ID: 475546 Summary: Unable to grab mouse cursor on Wayland Classification: Plasma Product: kwin Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: cuihao@gmail.com Target Milestone: --- SUMMARY Mouse cursor cannot be grabbed on Wayland. STEPS TO REPRODUCE 1. On a Plasma Wayland session, run qemu-system-x86_64 2. Click inside the QEMU window Also tested: Xpra and VirtualBox. OBSERVED RESULT The mouse cursor is not grabbed by QEMU and can still move outside, although QEMU believes that it grabs the mouse (as the window title changes to "Press Ctrl+Alt+G to release grab"). EXPECTED RESULT The mouse cursor is grabbed. On Plasma X11, Mouse grabbing works as expected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, with 6.5.6-arch2-1 kernel. (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470189] One of two screens randomly goes white and blank after wake up
https://bugs.kde.org/show_bug.cgi?id=470189 --- Comment #3 from CUI Hao --- I think it's amdgpu driver's issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2354 I'm trying amdgpu.sg_display=0 kernel parameter mentioned in that thread. The system has been running half a day without issue. Before finding this, I had tried downgrading kwin before and that didn't work. So this is not likely caused by kwin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470189] One of two screens randomly goes white and blank after wake up
https://bugs.kde.org/show_bug.cgi?id=470189 --- Comment #1 from CUI Hao --- Created attachment 159225 --> https://bugs.kde.org/attachment.cgi?id=159225=edit Flickering There is also a chance the screen enter the state where it flickers between white and normal video when I move the cursor on that screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470189] New: One of two screens randomly goes white and blank after wake up
https://bugs.kde.org/show_bug.cgi?id=470189 Bug ID: 470189 Summary: One of two screens randomly goes white and blank after wake up Classification: Plasma Product: kwin Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: cuihao@gmail.com Target Milestone: --- Created attachment 159217 --> https://bugs.kde.org/attachment.cgi?id=159217=edit The right screen turns white SUMMARY I connect two monitors to my PC. Recently, after I wake up the monitors from power saving, the right one of them (which is set to non-primary) sometimes goes white and blank. Only mouse cursor is visible. Please see the attachment for picture. When I move the cursor, it still interacts with windows on that screen. I can notice changes of cursor shapes, and even pull windows out from that screen. Turning off+on / Unplugging+Plugging the screen doesn't fix. "killall -9 kwin_wayland" fixes the screen at the cost of losing all windows. STEPS TO REPRODUCE 1. Let the screens sleep. 2. Wake them up. OBSERVED RESULT The right one of the two screens sometimes becomes white. EXPECTED RESULT Both screens are usable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.3-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] driver: nvidia v: 530.41.03 Device-2: AMD Raphael driver: amdgpu v: kernel Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 compositor: kwin_wayland driver: X: loaded: modesetting dri: radeonsi gpu: nvidia,amdgpu resolution: 1: 1920x1080 2: 1920x1080 API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (gfx1036 LLVM 15.0.7 DRM 3.52 6.3.3-arch1-1) The two screens are both connected to the integrated AMD GPU. The left one is connected to the DisplayPort, the right one to the HDMI port. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466904] Powerdevil keeps crashing after resuming from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=466904 --- Comment #2 from Wei Hao --- Created attachment 157023 --> https://bugs.kde.org/attachment.cgi?id=157023=edit Screenshot of journalctl -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466904] Powerdevil keeps crashing after resuming from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=466904 --- Comment #1 from Wei Hao --- Created attachment 157022 --> https://bugs.kde.org/attachment.cgi?id=157022=edit Screenshot of journalctl -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466904] New: Powerdevil keeps crashing after resuming from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=466904 Bug ID: 466904 Summary: Powerdevil keeps crashing after resuming from Screen Energy Saving Classification: Plasma Product: Powerdevil Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dolem@gmail.com CC: m...@ratijas.tk 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 *** Powerdevil crashes every time after upgrading to 5.27.2 when resuming from Screen Energy Saving mode. **KDE is running in Wayland mode.** STEPS TO REPRODUCE 1. Let the device idle to enter Screen Energy Saving. My device is connected to an LG C2 OLED TV monitor through HDMI. After the monitor said the signal lost. Turn off the monitor 2. Wait for 10 mins 3. Turn on the monitor and move the mice or click the keyboard. 4. Enter the OS and you can find powerdevil keeps crashing and there are tons of logs every second during the idle time. OBSERVED RESULT powerdevil crashed and "qt.qpa.wayland: Creating a fake screen in order for Qt not to crash" many times and all running apps like fcitx5, telegram, etc tray icon are missing. Though they are still running. EXPECTED RESULT Log in back normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux beelink-gtr6 6.2.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 03 Mar 2023 15:58:31 + x86_64 GNU/Linux (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 CPU: 16 × AMD Ryzen 9 6900HX with Radeon Graphics GPU: Integrated AMD Radeon 680M ADDITIONAL INFORMATION Some crash logs ``` Mar 06 02:49:53 beelink-gtr6 systemd[1]: systemd-coredump@481-40677-0.service: Deactivated successfully. Mar 06 02:49:53 beelink-gtr6 systemd[1647]: plasma-powerdevil.service: Main process exited, code=dumped, status=11/SEGV Mar 06 02:49:53 beelink-gtr6 systemd[1647]: plasma-powerdevil.service: Failed with result 'timeout'. Mar 06 02:49:53 beelink-gtr6 systemd[1647]: Failed to start Powerdevil. Mar 06 02:49:53 beelink-gtr6 systemd[1647]: plasma-powerdevil.service: Consumed 1.524s CPU time. Mar 06 02:49:53 beelink-gtr6 systemd[1647]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 121. Mar 06 02:49:53 beelink-gtr6 systemd[1647]: Stopped Powerdevil. Mar 06 02:49:53 beelink-gtr6 systemd[1647]: plasma-powerdevil.service: Consumed 1.524s CPU time. Mar 06 02:49:53 beelink-gtr6 systemd[1647]: Starting Powerdevil... Mar 06 02:49:53 beelink-gtr6 org_kde_powerdevil[40687]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Mar 06 02:49:53 beelink-gtr6 org_kde_powerdevil[40687]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Mar 06 02:49:53 beelink-gtr6 org_kde_powerdevil[40687]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: KCrash: Attempting to start /usr/lib/org_kde_powerdevil Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 32 -- exe=/usr/lib/org_kde_powerdevil Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 17 -- platform=wayland Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 27 -- appname=org_kde_powerdevil Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 17 -- apppath=/usr/lib Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 10 -- signal=11 Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 10 -- pid=40687 Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 18 -- appversion=5.27.2 Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 40 -- programname=KDE Power Management System Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 31 -- bugaddress=sub...@bugs.kde.org Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 23 -- productname=Powerdevil Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: 15 -- restarted=true Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: KCrash: crashing... crashRecursionCounter = 2 Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: KCrash: Application Name = org_kde_powerdevil path = /usr/lib pid = 40687 Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: KCrash: Arguments: /usr/lib/org_kde_powerdevil Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40687]: KCrash: Attempting to start /usr/lib/drkonqi Mar 06 02:49:54 beelink-gtr6 org_kde_powerdevil[40722]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Mar 06 02:49:54 beelink-gtr6 drkonqi[40723]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Mar 06 02:49:54 beelink-gtr6
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #15 from CUI Hao --- Tested on plasma 5.26 + kernel 6.0 + nvidia-open 520.56.06. Still saw the same issue. Is this related to DMABUF support on NVIDIA card? https://github.com/NVIDIA/open-gpu-kernel-modules/discussions/243 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459715] Wallpaper "crashes" and only black background shown when external display connected (wayland)
https://bugs.kde.org/show_bug.cgi?id=459715 CUI Hao changed: What|Removed |Added CC||cuihao@gmail.com --- Comment #10 from CUI Hao --- I encountered the same issue on X11 from time to time. But it usually happened after I unlock the screen. Arch Linux w/ latest Plasma 5.25.5. Intel + NVIDIA dual screen. NVIDIA card is the primary GPU. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456951] Global shortcut for arbitrary terminal command should be possible without creating a script file on disk
https://bugs.kde.org/show_bug.cgi?id=456951 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448839] [NVIDIA Wayland] Screen recording and task manager's window thumbnails are black
https://bugs.kde.org/show_bug.cgi?id=448839 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448944] xdg-desktop-portal only shows a black screen when trying to screenshare a whole screen in Wayland with Pipewire (NVIDIA GBM)
https://bugs.kde.org/show_bug.cgi?id=448944 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455961] KRunner pops up at wrong position after active screen changed since 5.25
https://bugs.kde.org/show_bug.cgi?id=455961 --- Comment #3 from CUI Hao --- (In reply to Alexander Lohnau from comment #2) > Are you on X11 or Wayland? X11. Nvidia + Intel dual cards barely work on Plasma Wayland (ref: #452219) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456453] Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set
https://bugs.kde.org/show_bug.cgi?id=456453 --- Comment #2 from CUI Hao --- (In reply to Nate Graham from comment #1) > Pretty sure this'll be fixed by the fix for Bug 450443. > > *** This bug has been marked as a duplicate of bug 450443 *** But it seems all the patches in bug 450443 had been applied when I reported this issue. Now I'm still observing the same issue. Currently the following Arch Linux packages are installed on my machine: - plasma-desktop 5.25.3 - qt5-base 5.15.5+kde+r170-1 (which is compiled from https://invent.kde.org/qt/qt/qtbase/-/commit/aa0c6db334cf6f0887f42cbd82e4af258126bdc5). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456453] Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set
https://bugs.kde.org/show_bug.cgi?id=456453 CUI Hao changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456453] New: Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set
https://bugs.kde.org/show_bug.cgi?id=456453 Bug ID: 456453 Summary: Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set Product: kwin Version: 5.25.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: cuihao@gmail.com Target Milestone: --- Created attachment 150470 --> https://bugs.kde.org/attachment.cgi?id=150470=edit Screen recording that illustrates the bug SUMMARY Please see the attached video. When using Xorg + dual-screen (4K & 200% scale) + PLASMA_USE_QT_SCALING=1, if I place a plasma panel to between the two screens (or exactly, the left edge of the right screen), the right screen become unusable and all windows placed on it will be immediately kicked to the right edge of the screen (outside the visible area). It's still possible to pull a window out but only moving it to the left screen can prevent it from being misplaced again. STEPS TO REPRODUCE 1. Create a fresh new user. Setup a plasma panel. 2. Move the panel to the left edge of the right screen of two screens placed horizontally. 3. Move or start a window on the right screen. OBSERVED RESULT All windows on the right screen are misplaced outside visible area (to the right of the right edge of the right screen). EXPECTED RESULT Windows are correctly placed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with latest packages KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION The left screen is connected to Intel iGPU (i7-10700K). The right is connected to NVIDIA GTX 1650 GPU, which is also the primary GPU. Setting Intel as the primary GPU makes no change. Why am I placing the panel between two screens: I've never intended to do this. But another heisenbug which appears after 5.25 causes my panel to be moved from normal place (leftmost edge) to the wrong place (left edge of the right screen) from time to time after I unlock the screen. And whenever that happens, kwin becomes buggy in the way I said above. About PLASMA_USE_QT_SCALING: I hadn't set the environment variable before 5.25. After 5.25 I noticed everything (icon/text/button) related to plasmashell became smaller than 5.24. Someone told me the environment variable should be set to make plasmashell use the same scale as Qt. They said it's not new in 5.25 and I should have had it set before if I didn't see inconsistent scaling before 5.25. But the thing was I never set it before 5.25. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #10 from CUI Hao --- Created attachment 150302 --> https://bugs.kde.org/attachment.cgi?id=150302=edit My KDE log (default setting + KWIN_DRM_DEVICES to nvidia) My PC has a similar setup to a typical I+N laptop. I set Intel card as primary GPU (connected to one monitor) and use NVIDIA card to connect a second monitor. I observe the very same thing. Basically: 1. By default, kwin_wayland uses Intel card. Both monitors show picture. But the "NVIDIA screen" runs terribly slow. 2. If I set `KWIN_DRM_DEVICES=/dev/dri/card0` (the NVIDIA card), or set NVIDIA card as the primary GPU, then only the NVIDIA screen shows picture. I attached relevant log. The driver is NVIDIA-open 515.48.07, and plasma is 5.25.2. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 455978] New: RAR archives does not open as virtual directory
https://bugs.kde.org/show_bug.cgi?id=455978 Bug ID: 455978 Summary: RAR archives does not open as virtual directory Product: krusader Version: 2.7.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: krarc Assignee: krusader-bugs-n...@kde.org Reporter: he...@hckiang.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY I have both unrar and rar installed and their path shows up in the settings, but when trying to open RAR, it will always use my external archive viewer rather than as virtual directory. Zip and other formats works just fine. Versions: rar 6.12 unrar 6.12 STEPS TO REPRODUCE 1. Install the said versions of rar and unrar 2. Attempt to open an rar file by clicking enter Even if in "Settings -> Protocols" both "application/x-rar" and "application/vnd.rar" are linked under krarc nothing changes. OBSERVED RESULT External program is used to open the rar file. EXPECTED RESULT The rar file is opened with the internal viewer as a virtual directory. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455961] KRunner pops up at wrong position after active screen changed since 5.25
https://bugs.kde.org/show_bug.cgi?id=455961 --- Comment #1 from CUI Hao --- Created attachment 150169 --> https://bugs.kde.org/attachment.cgi?id=150169=edit KRunner pops up at the center of the right screen -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455961] New: KRunner pops up at wrong position after active screen changed since 5.25
https://bugs.kde.org/show_bug.cgi?id=455961 Bug ID: 455961 Summary: KRunner pops up at wrong position after active screen changed since 5.25 Product: krunner Version: 5.25.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: cuihao@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 150168 --> https://bugs.kde.org/attachment.cgi?id=150168=edit KRunner pops up at top-left edge of the left screen SUMMARY KRunner popup appears at wrong position after active screen changed since 5.25. Before 5.25, sometimes (fairly rare) KRunner could pop up from wrong position, which is usually top left edge. But now the issue appears frequently and I find a way to stably trigger it. Screen configuration: - X11 - GPU: - iGPU: Intel UHD Graphics 630 (i7-10700K) as PRIMARY GPU. - dGPU: NVIDIA GeForce GTX 1650. - Dual screen: The left screen is connected to Intel iGPU. The right screen is connected to NVIDIA dGPU. STEPS TO REPRODUCE 1. Move cursor to the left screen, launch KRunner (by pressing Alt-F2). This is a warm up. 2. Move cursor to the right screen, launch KRunner two times. 3. Move cursor to the left screen again, launch KRunner two times. OBSERVED RESULT Step 2: The first time KRunner pops up at the center of the right screen. The second time it pops up at normal position (top center). Step 3: The first time KRunner pops up at the top-left edge of the left screen. The second time it pops up at normal position. EXPECTED RESULT KRunner always pops up at top center of the current screen. SOFTWARE/OS VERSIONS Linux: Arch Linux, latest (non-testing) packages, 5.18.6-zen1-1-zen kernel KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 CUI Hao changed: What|Removed |Added CC||cuihao@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #5 from CUI Hao --- So this is not a Spectacle-specific bug. It's a bug of Qt or Jasper. FYI, I submitted a bug report to Qt: https://bugreports.qt.io/browse/QTBUG-104398 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #4 from CUI Hao --- Well, copying is now OK after I rebooted the system. Saving as jp2 file still triggers segfault. There was probably another bug in clipboard functions. But I think we can focus on the jp2 issue for now... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362
--- Comment #3 from CUI Hao ---
I can confirm Gwenview and possibly other Qt programs crashes at the same place
when copying image data. I reproduced the bug using this very simple Qt
program:
```
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
MainWindow w;
auto clipboard = QApplication::clipboard();
auto data = new QMimeData();
QPixmap pixmap(128, 128);
pixmap.fill();
auto image = pixmap.toImage();
data->setImageData(image);
clipboard->setMimeData(data);
w.show();
return a.exec();
}
```
The error happens in QEventLoop. I don't know how to debug. I blindly searched
`Jpeg2000JasperReader` references but found none in Qt5 code.
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #2 from CUI Hao --- (In reply to Yerrey Dev from comment #1) > Are you using JP2 file format in Configure -> Save -> Filename? > It's PNG. I never changed the setting. I also wonder about why JP2 format is used. But I couldn't find a clue in the code. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] New: Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 Bug ID: 455362 Summary: Spectacle segmentation fault in libjasper after copying image to clipboard Product: Spectacle Version: 22.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: cuihao@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Spectacle crashes with a segmentation fault in libjasper after copying image to clipboard. I think it's Qt's issue with latest libjasper library. See "ADDITIONAL INFORMATION" for my debug attempts. STEPS TO REPRODUCE 1. Open Spectacle 2. Take a screenshot 3. Copy Image to Clipboard and wait for a few seconds OBSERVED RESULT Spectacle crashes with segmentation fault. Sometimes it crashes Plasmashell together. Strangely, it doesn't crash immediate after clicking "Copy Image to Clipboard". There is a few seconds before crashing and I can even paste the image elsewhere. EXPECTED RESULT Spectacle doesn't crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Backtrace in GDB: ``` #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f574b28e3d3 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f574b23e838 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f574c675840 in KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kcrash-5.95.0/src/kcrash.cpp:633 #4 #5 jas_stream_putc_func (stream=0x0, c=0) at /usr/src/debug/jasper-version-3.0.4/src/libjasper/base/jas_stream.c:629 #6 0x7f574467c989 in jp2_putuint32 (out=out@entry=0x0, val=val@entry=12) at /usr/src/debug/jasper-version-3.0.4/src/libjasper/jp2/jp2_cod.c:762 #7 0x7f574467e2e8 in jp2_box_put (box=box@entry=0x56057ff244d0, out=out@entry=0x0) at /usr/src/debug/jasper-version-3.0.4/src/libjasper/jp2/jp2_cod.c:565 #8 0x7f574468054e in jp2_encode (image=0x560580044b90, out=0x0, optstr=0x56057ff8c540 "") at /usr/src/debug/jasper-version-3.0.4/src/libjasper/jp2/jp2_enc.c:146 #9 0x7f5744703c82 in Jpeg2000JasperReader::write (quality=, image=..., this=0x7fff1d7ef250) at /usr/src/debug/qtimageformats/src/plugins/imageformats/jp2/qjp2handler.cpp:864 #10 QJp2Handler::write (this=, image=...) at /usr/src/debug/qtimageformats/src/plugins/imageformats/jp2/qjp2handler.cpp:257 #11 0x7f574c1b3628 in QImageWriter::write (image=..., this=0x7fff1d7ef3a8) at image/qimagewriter.cpp:785 #12 QImageWriter::write (this=0x7fff1d7ef3a8, image=...) at image/qimagewriter.cpp:753 #13 0x7f574c1979d8 in QImage::save (quality=-1, format=, device=0x7fff1d7ef410, this=0x7fff1d7ef420) at image/qimage.cpp:3758 #14 QImage::save (this=0x7fff1d7ef420, device=0x7fff1d7ef410, format=, quality=-1) at image/qimage.cpp:3753 #15 0x7f574c160727 in QInternalMimeData::renderDataHelper (mimeType=..., data=data@entry=0x56057fd90990) at kernel/qinternalmimedata.cpp:228 #16 0x7f57468e0984 in QXcbMime::mimeDataForAtom (connection=0x56057fa1ae60, a=892, mimeData=0x56057fd90990, data=0x7fff1d7ef5e8, atomFormat=, dataFormat=0x7fff1d7ef5dc) at /usr/src/debug/qtbase/src/plugins/platforms/xcb/qxcbmime.cpp:111 #17 0x7f57468d45d4 in QXcbClipboard::sendSelection (property=710, window=, target=892, d=0x56057fd90990, this=0x7f5740001600) at ./qxcbobject.h:53 #18 QXcbClipboard::handleSelectionRequest (req=0x5605800f9330, this=0x7f5740001600) at /usr/src/debug/qtbase/src/plugins/platforms/xcb/qxcbclipboard.cpp:631 #19 QXcbConnection::handleXcbEvent (this=, event=0x5605800f9330) at /usr/src/debug/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:637 #20 0x7f57468d7960 in QXcbConnection::processXcbEvents (this=0x56057fa1ae60, flags=...) at /usr/src/debug/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1020 #21 0x7f57468faf18 in xcbSourceDispatch (source=) at /usr/src/debug/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103 #22 0x7f5749b18c6b in g_main_dispatch (context=0x7f5740005010) at ../glib/glib/gmain.c:3417 #23 g_main_context_dispatch (context=0x7f5740005010) at ../glib/glib/gmain.c:4135 #24 0x7f5749b6f001 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f5740005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4211 #25 0x7f5749b16392 in g_main_context_iteration (context=0x7f5740005010, may_block=1) at ../glib/glib/gmain.c:4276 #26 0x7f574bcd827c in QEventDispatcherGlib::processEvents (this=0x56057fb38950, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x7f574bc862ec in QEventLoop::exec (this=0x7fff1d7ef960, flags=...) at
[kdeconnect] [Bug 454069] New: KDE Connect Windows client can't receive files
https://bugs.kde.org/show_bug.cgi?id=454069 Bug ID: 454069 Summary: KDE Connect Windows client can't receive files Product: kdeconnect Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: h...@42yeah.is Target Milestone: --- Created attachment 149012 --> https://bugs.kde.org/attachment.cgi?id=149012=edit File transfer window SUMMARY My KDE Connect instance in Windows can't receive any file. Everytime I try to send a progress window pop up, but that's all. My android then tells me the file-sending failed. I have tried sending from Android to my iPad, and from my iPad back to my Android, and my Windows to my Android & iPad, and all of them work. STEPS TO REPRODUCE 1. Send file to Windows OBSERVED RESULT File receive window pops up & stays there but does nothing else SOFTWARE/OS VERSIONS Windows: Windows 11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436246] Mouse selection clipboard (PRIMARY) works on Wayland, but klipper wont capture it
https://bugs.kde.org/show_bug.cgi?id=436246 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417939] Context menu disappears when tooltip disappears
https://bugs.kde.org/show_bug.cgi?id=417939 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 CUI Hao changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430388] New: Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 Bug ID: 430388 Summary: Custom Shortcuts cannot record key presses Product: systemsettings Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: cuihao@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 134075 --> https://bugs.kde.org/attachment.cgi?id=134075=edit A short video to demonstrate the issue SUMMARY I couldn't set shortcut keys in "Custom Shortcuts" setting because it failed to record my key presses. STEPS TO REPRODUCE 1. Open "Custom Shortcuts" tab in KDE System Settings. 2. Create a new shortcut or edit an existing one. 3. Switch to the "Trigger" tab, activate the shortcut button following "Shortcut:" text. 3. Press desired key or key combination to set the shortcut. OBSERVED RESULT Key presses were not recorded. The shortcut button still showed "None". A line of error "kf.guiaddons: Cannot record without a window" appeared in stderr every time when pressing the shortcut button. EXPECTED RESULT Key presses are correctly recorded. SOFTWARE/OS VERSIONS Operating System: 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.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Hao Zhang changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410777] Merging a hidden group layer crash Krita
https://bugs.kde.org/show_bug.cgi?id=410777 --- Comment #5 from Khoo Hao Yit --- It works with any image for me. https://youtu.be/BXOTfKMqV1U -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410777] Merging a hidden group layer crash Krita
https://bugs.kde.org/show_bug.cgi?id=410777 Khoo Hao Yit changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |ASSIGNED --- Comment #3 from Khoo Hao Yit --- The attachment has been upload. https://bugs.kde.org/attachment.cgi?id=122045 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410777] Merging a hidden group layer crash Krita
https://bugs.kde.org/show_bug.cgi?id=410777 --- Comment #2 from Khoo Hao Yit --- Created attachment 122045 --> https://bugs.kde.org/attachment.cgi?id=122045=edit krita.log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410777] New: Merging a hidden group layer crash Krita
https://bugs.kde.org/show_bug.cgi?id=410777 Bug ID: 410777 Summary: Merging a hidden group layer crash Krita Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: khoohaoyi...@gmail.com Target Milestone: --- Created attachment 122043 --> https://bugs.kde.org/attachment.cgi?id=122043=edit kritacrash.log SUMMARY Merging a hidden layer crash Krita. STEPS TO REPRODUCE 1. Have a paint layer inside a group layer. 2. Hide the group layer. 3. Click on the group layer and merge it (Ctrl + E). OBSERVED RESULT Freeze and crash. EXPECTED RESULT Merged layer. SOFTWARE/OS VERSIONS Windows: Microsoft Windows 10 Pro, Version 10.0.17763 Build 17763 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 Hao Zhang <theivoryto...@gmail.com> changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Hao Zhang <theivoryto...@gmail.com> changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365037] New: 蓝牙连接失败时 Plasma 崩溃
https://bugs.kde.org/show_bug.cgi?id=365037 Bug ID: 365037 Summary: 蓝牙连接失败时 Plasma 崩溃 Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: liuhao@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.26-21-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: NM 中保存了以前连接过的蓝牙设备，当设备未开启时使用NM进行连接时，Plasma 会弹出连接错误提示或者发生崩溃 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3141ab17c0 (LWP 7652))] Thread 7 (Thread 0x7f312b4a5700 (LWP 7654)): #0 0x7f313afbebbd in poll () at /lib64/libc.so.6 #1 0x7f313ff12422 in () at /usr/lib64/libxcb.so.1 #2 0x7f313ff1400f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f312d5f63c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f313b6b932f in QThreadPrivate::start(void*) (arg=0x11b5040) at thread/qthread_unix.cpp:331 #5 0x7f313a7c80a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f313afc6fed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f3123fff700 (LWP 7670)): #0 0x7f313afbebbd in poll () at /lib64/libc.so.6 #1 0x7f313769be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f313769bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f313b8ebd8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f311c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f313b892d53 in QEventLoop::exec(QFlags) (this=this@entry=0x7f3123ffedf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f313b6b461a in QThread::exec() (this=) at thread/qthread.cpp:503 #6 0x7f313e9c8e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f313b6b932f in QThreadPrivate::start(void*) (arg=0x124beb0) at thread/qthread_unix.cpp:331 #8 0x7f313a7c80a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f313afc6fed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f3117087700 (LWP 7671)): #0 0x7f313afbebbd in poll () at /lib64/libc.so.6 #1 0x7f313769be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f313769bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f313b8ebd8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f3118c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f313b892d53 in QEventLoop::exec(QFlags) (this=this@entry=0x7f3117086df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f313b6b461a in QThread::exec() (this=) at thread/qthread.cpp:503 #6 0x7f313e9c8e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f313b6b932f in QThreadPrivate::start(void*) (arg=0x15a38a0) at thread/qthread_unix.cpp:331 #8 0x7f313a7c80a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f313afc6fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f31158f0700 (LWP 7672)): #0 0x7f31376992a1 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f313769b530 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f313769bd80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f313769bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f313b8ebd8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f31080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f313b892d53 in QEventLoop::exec(QFlags) (this=this@entry=0x7f31158efdf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f313b6b461a in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7f313e9c8e18 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f313b6b932f in QThreadPrivate::start(void*) (arg=0x1683470) at thread/qthread_unix.cpp:331 #9 0x7f313a7c80a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f313afc6fed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f310fdf7700 (LWP 7673)): #0 0x7f313a7cc03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f314119786b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f3141197899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f313a7c80a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f313afc6fed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f3087b0e700 (LWP 7675)): #0 0x7f313afbebbd in poll () at /lib64/libc.so.6 #1 0x7f313769be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f313769bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f313b8ebd8b in
[frameworks-baloo] [Bug 364475] baloo_file_extractor crashes whenever the index exceeds 5G in size
https://bugs.kde.org/show_bug.cgi?id=364475 --- Comment #5 from Hao Zhang <theivoryto...@gmail.com> --- Created attachment 99637 --> https://bugs.kde.org/attachment.cgi?id=99637=edit Patch to fix this bug This bug is fixed with the attached patch. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 364475] baloo_file_extractor crashes whenever the index exceeds 5G in size
https://bugs.kde.org/show_bug.cgi?id=364475 --- Comment #4 from Hao Zhang <theivoryto...@gmail.com> --- The relevant code is in line 97 of the file src/engine/database.cpp mdb_env_set_mapsize(m_env, static_cast(1024) * 1024 * 1024 * 5); // 5 gb The size of the database is HARDCODED to be 5gb!! Is there any specific reason this size cannot be larger? 5gb is far from enough if there are lots of files to index. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362333] baloo_file Closed Unexpectedly a short while after starting KDE
https://bugs.kde.org/show_bug.cgi?id=362333 Hao Zhang <theivoryto...@gmail.com> changed: What|Removed |Added CC||theivoryto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 364475] baloo_file_extractor crashes whenever the index exceeds 5G in size
https://bugs.kde.org/show_bug.cgi?id=364475 --- Comment #3 from Hao Zhang <theivoryto...@gmail.com> --- When I compiled baloo in debug mode, I got the following error before baloo_file_extractor crashes: ASSERT failure in PositionDB::put: "MDB_MAP_FULL: Environment mapsize limit reached", file /home/hao/build/baloo/src/baloo-5.23.0/src/engine/positiondb.cpp, line 80 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358719] fcitx creates blank unusable xembed icon in systray
https://bugs.kde.org/show_bug.cgi?id=358719 CUI Hao <cuihao@gmail.com> changed: What|Removed |Added CC||cuihao@gmail.com --- Comment #5 from CUI Hao <cuihao@gmail.com> --- Hi all, This issue also affects me. I thought fcitx was to blame so I filed an issue to fcitx here: https://github.com/fcitx/fcitx/issues/241 I know nothing about systray programming. If possible, you may provide some technical information for this issue. I notice that if you merely kill fcitx, the blank icon won't disappear from Plasma systray. I though this may be a bug of xembedsniproxy. A dump of xembedsniproxy's terminal output is provided in above issue report. -- You are receiving this mail because: You are watching all bug changes.
