[Breeze] [Bug 446468] Selected folder icon becomes white in selected list items
https://bugs.kde.org/show_bug.cgi?id=446468 Francisco Pina Martins changed: What|Removed |Added CC||stu...@pinamartins.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #29 from Francisco --- (In reply to Kevin Krammer from comment #24) > Disabling KScreen2 also works to avoid the issue. Confirmed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #16 from Francisco González --- (In reply to Zamundaaa from comment #15) > Do the DPMS issues still happen with released Plasma 6? They seem gone! Although some versions ago, when the screen went off by timeout, some garbage was displayed, but moving the mouse was enough to "clean" that. I'mma keep you updated if it happens again, but for now seems fixed. Thank you for your work <3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436214] Measure distances (and areas?)
https://bugs.kde.org/show_bug.cgi?id=436214 Francisco changed: What|Removed |Added CC||franje...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #6 from Francisco --- Even better (focusing on the suspicious EDID bit). Sorry about the spam: https://share.firefox.dev/4axsSYc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #5 from Francisco --- Sorry, I missed there is an easier way to share this: https://profiler.firefox.com/from-url/https%3A%2F%2Fpub-32f46577ac8f4e2b84ba6635b1d55699.r2.dev%2Fpepe.perf/calltree/?globalTrackOrder=0=1881-2=1=category=10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #4 from Francisco --- Notice that ksmserver is also using quite a bit of CPU, maybe they are sending each other events in an infinite loop? Perf for ksmserver is here: https://pub-32f46577ac8f4e2b84ba6635b1d55699.r2.dev/ksmserver.perf -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #3 from Francisco --- (In reply to fanzhuyifan from comment #2) > Hotspot profiling data pointing to where these processes are using all > those cpu cycles would be extremely helpful. I did some profiling on kwin_x11 with debuginfod data and this is the gist of it. You can get the full trace from https://pub-32f46577ac8f4e2b84ba6635b1d55699.r2.dev/pepe.perf and load it in https://profiler.firefox.com or https://www.speedscope.app/ I have used a simple "perf report" to generate the lines below: Samples: 62K of event 'cycles:P', Event count (approx.): 23722680927 Children Self Command Shared Object Symbol - 36,84% 0,00% kwin_x11kwin_x11 [.] 0x55638a2d3ef4 ◆ 0x55638a2d3ef4 ▒ __libc_start_main ▒ 0x7f905a643ccf ▒ 0x55638a2cfc24 ▒ - QCoreApplication::exec() ▒ - 36,84% QEventLoop::exec(QFlags) ▒ - 36,83% QEventDispatcherGlib::processEvents(QFlags) ▒ - 36,81% g_main_context_iteration ▒ - 36,62% 0x7f9059c973a6 ▒ - 36,58% 0x7f9059c38f68 ▒ - 19,21% 0x7f90559ecbd6 ▒ - 19,18% QXcbConnection::processXcbEvents(QFlags) ▒ - 18,69% QXcbConnection::handleXcbEvent(xcb_generic_event_t*) ▒ - 10,83% QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long long*) ▒ - 8,47% KWin::Workspace::workspaceEvent(xcb_generic_event_t*) ▒ - 6,78% KWin::Workspace::createUnmanaged(unsigned int) ▒ + 3,75% KWin::X11Window::X11Window() ▒ + 2,18% KWin::X11Window::track(unsigned int) ▒ + 0,65% operator new(unsigned long) ▒ + 1,30% KWin::Workspace::updateXStackingOrder() ▒ + 2,19% 0x7f905dbbf6d9 ▒ - 7,78% QXcbConnection::initializeScreens(bool) ▒ - 7,75% QXcbConnection::initializeScreensFromMonitor(xcb_screen_iterator_t*, int
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking the screen
https://bugs.kde.org/show_bug.cgi?id=484323 Francisco changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||franje...@gmail.com --- Comment #1 from Francisco --- Can confirm I observe the same behaviour, both kwin_x11 and Xorg together using 100% CPU. This is with kwin 6.0.2-3 on manjaro. Interestingly, when I move the mouse and the screen goes from black to background image, CPU usage goes back to normal. Also interesting is that I use a LG TV as display, not a monitor, so there is no "proper" display suspend, but rather the TV shows a no-signal background picture for a while. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 478508] Program freezes/crashes when loading a previously saved .lml file.
https://bugs.kde.org/show_bug.cgi?id=478508 --- Comment #2 from Francisco Ulloa --- Created attachment 164162 --> https://bugs.kde.org/attachment.cgi?id=164162=edit Project file plus file imported into spreadsheet The zip folder contains the project file after importing the example file into a spreadsheet and saving it. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 478508] New: Program freezes/crashes when loading a previously saved .lml file.
https://bugs.kde.org/show_bug.cgi?id=478508 Bug ID: 478508 Summary: Program freezes/crashes when loading a previously saved .lml file. Classification: Applications Product: LabPlot2 Version: 2.10.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: faulloaoso...@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. Import an .csv file to a spreadsheet. 2. Save the project as .lml file. 3. Re open the project from a new window, by using "Open". OBSERVED RESULT The program freezes and the file is not charged after 20 minutes. EXPECTED RESULT The project is loaded and the saved progress is available again. SOFTWARE/OS VERSIONS Windows: 10 PRO 64-bit, (10.0, Build 19045) 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 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #13 from Francisco González --- Oh, by the way I'm testing KDE 6 from source, built with kdesrc-build from branch master. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Francisco González --- Hi. I've noticed that this issue is partially solved, because the commit only fixes TTY switching, but not when the computer is powered on after sleep, or when the screen powers off due to the energy management timeout. It's not the same kind of corruption though, since the glitches involve one of my screens not turning on, and the other one refreshing at a very low rate (like 2-5 fps). I'm not sure if this is the same bug, but in case it isn't, please close this report and tell me if you need me to file it as another bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473575] New: Avoid sleep while flushing cache to removable drive
https://bugs.kde.org/show_bug.cgi?id=473575 Bug ID: 473575 Summary: Avoid sleep while flushing cache to removable drive Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fgonzalez.n...@gmail.com Target Milestone: --- Today I was copying an ISO image to a Ventoy-enabled USB drive (exfat). It seems that the file transfer was cached by default, so the file transfer dialog was closed after the file was cached. After clicking the secure-remove button, Plasma showed me the message to not unplug the device until the flush was done. After 10 minutes (by setting) my computer went to sleep, and after resuming the flush message was still showing. It would mean that the flush might not finish prior to sleep. It would be nice to have a feature to disable sleep while a cached file transfer is still being done since file corruption might happen. STEPS TO REPRODUCE 1. Transfer a file to a device with write cache enabled. 2. Wait for the computer to sleep (make sure to set an appropriate time threshold so the sleep can occur while the flush is still going). 3. Resume the computer and check the flush dialog and/or file corruption. OBSERVED RESULT The computer goes to sleep but after resuming, the cache flush is still ongoing. EXPECTED RESULT The computer goes to sleep only after the cache flush has ended. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, 6.4.11-arch2-1 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Running on Wayland -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 473254] Graphics version mismatch
https://bugs.kde.org/show_bug.cgi?id=473254 --- Comment #4 from Francisco Cribari --- (In reply to m.eik michalke from comment #3) > the package may technically not be out-of-date, it is just not compatible > with the R version installed. that is if it still works with the R version > shipped with arch and you upgraded R from a third party repo. how did you > upgrade R? I upgraded R from the Arch repository. The two Arch packages (rkward and r) have the same maintainer / packager. ~ pacman -Qi r Name: r Version : 4.3.1-2 Description : Language and environment for statistical computing and graphics Architecture: x86_64 URL : https://www.r-project.org/ Licenses: GPL Groups : None Provides: r-kernsmooth=2.23.21 r-mass=7.3.60 r-matrix=1.5.4.1 r-base=4.3.1 r-boot=1.3.28.1 r-class=7.3.22 r-cluster=2.1.4 r-codetools=0.2.19 r-compiler=4.3.1 r-datasets=4.3.1 r-foreign=0.8.84 r-grdevices=4.3.1 r-graphics=4.3.1 r-grid=4.3.1 r-lattice=0.21.8 r-methods=4.3.1 r-mgcv=1.8.42 r-nlme=3.1.162 r-nnet=7.3.19 r-parallel=4.3.1 r-rpart=4.1.19 r-spatial=7.3.16 r-splines=4.3.1 r-stats=4.3.1 r-stats4=4.3.1 r-survival=3.5.5 r-tcltk=4.3.1 r-tools=4.3.1 r-translations=4.3.1 r-utils=4.3.1 Depends On : lapack libtiff pcre2 perl libxmu pango zip unzip curl icu which Optional Deps : tk: tcl/tk interface [installed] texlive-bin: latex sty files [installed] gcc-fortran: needed to compile some CRAN packages [installed] blas-openblas: faster linear algebra [installed] Required By : python-rchitect radian rkward rstudio-desktop-bin Optional For: graphviz Conflicts With : None Replaces: None Installed Size : 84.02 MiB Packager: Antonio Rojas Build Date : Sun 18 Jun 2023 06:19:57 AM -03 Install Date: Wed 28 Jun 2023 10:10:38 PM -03 Install Reason : Explicitly installed Install Script : No Validated By: Signature ~ pacman -Qi rkward Name: rkward Version : 0.7.5-2 Description : An easy to use and easily extensible IDE/GUI for R Architecture: x86_64 URL : https://rkward.kde.org/ Licenses: GPL Groups : None Provides: None Depends On : qt5-webengine ktexteditor r Optional Deps : None Required By : None Optional For: None Conflicts With : None Replaces: None Installed Size : 15.68 MiB Packager: Antonio Rojas Build Date : Tue 06 Dec 2022 02:23:59 PM -03 Install Date: Tue 06 Dec 2022 06:19:24 PM -03 Install Reason : Explicitly installed Install Script : No Validated By: Signature -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 473254] Graphics version mismatch
https://bugs.kde.org/show_bug.cgi?id=473254 --- Comment #2 from Francisco Cribari --- (In reply to m.eik michalke from comment #1) > thanks for the report. > > from the information you provided it looks like your installation of RKWard > was built with R 4.2.2 and you later replaced this with R 4.3.1, which also > upgraded the R graphics engine from version 15 (compile time) to 16 > (runtime). your build of RKWard can't fully handle that newer version, but > needs to be recompiled in order to also support R 4.3. I do realize that the Arch package needs to be rebuilt. I marked it as out-of-date. Nonetheless, the package maintainer told me to report the issue here. (His reply: "Please stop flagging this package out of date. If you want to report an issue, use the bug tracker.") That's why I filed this bug report. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 473254] Graphics version mismatch
https://bugs.kde.org/show_bug.cgi?id=473254 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 473254] New: Graphics version mismatch
https://bugs.kde.org/show_bug.cgi?id=473254 Bug ID: 473254 Summary: Graphics version mismatch Classification: Applications Product: rkward Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: R Console Assignee: rkward-de...@kde.org Reporter: crib...@gmail.com Target Milestone: --- SUMMARY *** I run rkward version 0.7.5-2 and R version 4.3.1 on Arch Linux. I am unable to produce plots (with rkward's default settings). *** STEPS TO REPRODUCE 1. Start rkward 2. Execute the following R code: a <- rnorm(1000); hist(a) OBSERVED RESULT The plot (histogram) is not produced. Instead, the following error is issued: "R Graphics Engine version has changed (from 15 to 16). This change requires a recompilation." EXPECTED RESULT A plot (histogram) should be produced. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux kernel 6.4.9-arch1-1 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.5.10 ADDITIONAL INFORMATION ---Problem description--- Please fill in the missing bits *in English*. Please give a brief summary on the problem: I am unable to produce plots (with rkward's default settings). What - in detail - did you do directly before you encountered this problem? Nothing When you try to repeat the above, does the problem occur again (no, sometimes, always)? Always If applicable: When doing the same thing in an R session outside of RKWard, do you see the same problem? No Do you have any further information that might help us to track this problem down? In particular, if applicable, can you provide sample data and sample R code to reproduce this problem? a <- rnorm(1000); hist(a) RKWard is available in many different packagings, and sometimes problems are specific to one method of installation. How did you install RKWard (which file(s) did you download)? >From the Arch Linux repositories. ---Session Info--- -- Frontend -- RKWard version: 0.7.5 KDE Frameworks version (runtime): 5.108.0 KDE Frameworks version (compile time): 5.100.0 Qt version (runtime): 5.15.10 Qt version (compile time): 5.15.7 Using QWebEngine for HTML rendering Local config directory: /home/cribari/.config RKWard storage directory: /home/cribari/.rkward/ Backend version (as known to the frontend): 4.3.1 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend -- Backend -- Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.rbackend R version (compile time): 4.2.2 (2022-10-31 r83211) R runtime session info: R version 4.3.1 (2023-06-16) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Arch Linux Matrix products: default BLAS/LAPACK: /usr/lib/libopenblas.so.0.3; LAPACK version 3.11.0 locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8 LC_COLLATE=C [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 [7] LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 [9] LC_ADDRESS=en_US.UTF-8LC_TELEPHONE=en_US.UTF-8 [11] LC_MEASUREMENT=en_US.UTF-8LC_IDENTIFICATION=en_US.UTF-8 time zone: America/Recife tzcode source: system (glibc) attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] rkward_0.7.5 loaded via a namespace (and not attached): [1] compiler_4.3.1 tools_4.3.1parallel_4.3.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 Francisco Pina Martins changed: What|Removed |Added CC||stu...@pinamartins.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #9 from Francisco González --- Also, running sudo journalctl -b 0 --grep drm sometimes shows a flooded journal with a "Page flip failed" error that said that there was no space left on device (IIRC). Can't remember in which case did it happen, but it seems it was when I was using the "radeon" module rather than "amdgpu". If it happens again, I'll post that output here. BTW, the screen corruption shows up with any of those modules. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #8 from Francisco González --- Some observations: - About the screen mode changes on TTY switch, the screen frequency regression to 60 Hz is noticeable but is not informed by KScreen, which shows 75 Hz. - Even though I'm not an expert on this, it seems that the lack of DRM_CLIENT_CAP_ATOMIC support on my graphics card and some problem with KWin handling that, might be the cause of the screen corruption. - In the duplicated bug referenced before, the user has a Radeon HD 6310, which seems to be pre-GCN (one gen before my GPU). That could mean that this bug might be replicable with HD 7000 series GPUs or older. - Running drm_info on my laptop (Intel UHD Graphics 620) shows support for DRM_CLIENT_CAP_ATOMIC, and there are no artifacts at all. PS: somehow, got baited into this 2016 article that might be related to this issue. VT Switching with Atomic Modeset. https://blog.ffwll.ch/2016/01/vt-switching-with-atomic-modeset.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #7 from Francisco González --- Created attachment 158955 --> https://bugs.kde.org/attachment.cgi?id=158955=edit Output before switching to TTY (drm_info) Sorry, had uploaded the wrong file before. Note that on line 5, says "DRM_CLIENT_CAP_ATOMIC not supported". Also, on line 166, mode is "1920x1080@74.97 driver phsync pvsync" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added Attachment #158953|0 |1 is obsolete|| --- Comment #6 from Francisco González --- Comment on attachment 158953 --> https://bugs.kde.org/attachment.cgi?id=158953 Output before switching to TTY (drm_info) >may 14 18:49:04 MSI-DESKTOP systemd[670]: Starting KDE Window Manager... >may 14 18:49:04 MSI-DESKTOP systemd[670]: Started KDE Window Manager. >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: No backend specified, >automatically choosing drm >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: kwin_wayland_drm: >drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU >"/dev/dri/card0" >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL vendor string: >AMD >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL renderer string: >AMD Radeon HD 7700 Series (verde, LLVM 15.0.7, DRM 3.52, 6.3.1-arch1-1) >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL version string: >4.6 (Core Profile) Mesa 23.0.3 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL shading language version >string: 4.60 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Driver: >Unknown >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: GPU class: >Unknown >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL version: >4.6 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: GLSL version: >4.60 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Mesa version: >23.0.3 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Linux kernel version: >6.3.1 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Requires strict binding: >no >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: GLSL shaders: >yes >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Texture NPOT support: >yes >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Virtual Machine: >no >may 14 18:49:05 MSI-DESKTOP kwin_wayland[711]: kwin_xkbcommon: XKB: >inet:323:58: unrecognized keysym "XF86EmojiPicker" >may 14 18:49:05 MSI-DESKTOP kwin_wayland[711]: kwin_xkbcommon: XKB: >inet:324:58: unrecognized keysym "XF86Dictate" >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: (WW) Option "-listen" >for file descriptors is deprecated >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: Please use "-listenfd" >instead. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: (WW) Option "-listen" >for file descriptors is deprecated >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: Please use "-listenfd" >instead. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: The XKEYBOARD keymap >compiler (xkbcomp) reports: >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: > Warning: >Unsupported maximum keycode 708, clipping. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: > X11 >cannot support keycodes above 255. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: Errors from xkbcomp are >not fatal to the X server -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #5 from Francisco González --- Created attachment 158954 --> https://bugs.kde.org/attachment.cgi?id=158954=edit Output after switching back from TTY (drm_info) Same deal with "DRM_CLIENT_CAP_ATOMIC not supported", but this time in line 166, mode was reverted to default "Mode: 1920x1080@60.00 preferred driver phsync pvsync" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added Attachment #158953|Output before switching |Output before switching to description|back to TTY (drm_info) |TTY (drm_info) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #4 from Francisco González --- Created attachment 158953 --> https://bugs.kde.org/attachment.cgi?id=158953=edit Output before switching back to TTY (drm_info) Note that on line 5, says "DRM_CLIENT_CAP_ATOMIC not supported". Also, on line 166, mode is "1920x1080@74.97 driver phsync pvsync" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #3 from Francisco González --- Created attachment 158952 --> https://bugs.kde.org/attachment.cgi?id=158952=edit Output after switching back from TTY (journalctl --user-unit plasma-kwin_wayland.service --boot 0) This output was obtained after running journalctl, while the screen was corrupted, via SSH with my laptop. There is no difference in journalctl output from before and after switching to TTY (checked with diff). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added CC||fgonzalez.n...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469443] Broken graphics after waking up from sleep on Wayland session
https://bugs.kde.org/show_bug.cgi?id=469443 Francisco González changed: What|Removed |Added CC||fgonzalez.n...@gmail.com --- Comment #1 from Francisco González --- It sounds like a duplicate of mine (https://bugs.kde.org/show_bug.cgi?id=469280) Which AMD GPU do you have? Does the bug happen if you switch to a TTY and then switch back to the GUI? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 Francisco González changed: What|Removed |Added CC||fgonzalez.n...@gmail.com --- Comment #11 from Francisco González --- (In reply to WojtasJD from comment #10) > I have similar issue with corrupted screen ( > https://bugsfiles.kde.org/attachment.cgi?id=149347 ) in: > - openSUSE 15.4, kernel 5.14.x and KDE Plasma 5.24.4 (installed on disk) > - neon-user-20230420-0722.iso (kernel 5.19; KDE Plasma 5.27.4 ; with user > "neon" logged out from X11 and logged in to Wayland live session) > > I have AMD Radeon HD 6570 (GPU name: TURKS, generation: Northern Islands) - > with radeon driver; amdgpu does not support this card. > > In my case I don't need to suspend the machine, it is enough to switch from > TTY1...6 (text login prompt) to TTY8 (Plasma) and screen is corrupted (with > good mouse cursor). > To 'repair' this I need to switch to TTY7 (SDDM) and back to TTY8 (Plasma). > After repair, again switching to TTY1...6 (but not TTY7 (SDDM)) and back to > TTY8 (Plasma) - screen is distorted (with good mouse cursor)... > > Same behavior with KDE neon (TTY numbers different). Got a HD 7750 (VERDE, Southern Islands). In my system, the screen corruption appears with both of them radeon and amdgpu, in the same fashion and equally work-aroundable as yours. At this point, I'm unsure if this is a GPU driver bug, from KDE or even Wayland, since this doesn't happen in GNOME (Wayland). Maybe they implemented some way to switch back from TTY without screen artifacts. By the way, this corruption doesn't occur on XOrg. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #39 from Francisco Cribari --- (In reply to Mauro Molinari from comment #38) > Ever heard about sleep and hibernation? ;-) Sure. I use them daily. I'm on Arch Linux which is not shy in updates. Several updates (kernel (zen), etc.) require a reboot. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #37 from Francisco Cribari --- (In reply to ticonzero from comment #35) > Well I do like it, in fact I'm sticking with it, but I do miss being able > to restore the old session, for me it means not having to reopen dozen of > pdfs in different okular instances on different desktops Same here. This bug is the only reason why I am not running Wayland. I usually have about a dozen PDF (okular) and over twenty text (kate) files open. It is too much work to open each of these files again every time I restart the computer. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 462177] Greek letters are not displayed in plots
https://bugs.kde.org/show_bug.cgi?id=462177 --- Comment #1 from Francisco Cribari --- Greek letters are not included in R plots. To reproduce the issue, start RKward and execute: a = rnorm(1); hist(a, main = expression(paste(mu,"=0"))) -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 462177] Greek letters are not displayed in plots
https://bugs.kde.org/show_bug.cgi?id=462177 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 462177] New: Greek letters are not displayed in plots
https://bugs.kde.org/show_bug.cgi?id=462177 Bug ID: 462177 Summary: Greek letters are not displayed in plots Classification: Applications Product: rkward Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: crib...@gmail.com Target Milestone: --- Created attachment 153977 --> https://bugs.kde.org/attachment.cgi?id=153977=edit Screenshot SUMMARY *** I run RKWad version 0.7.5-1 under Arch Linux + KDE. Greek letters do not show up in R plots in RKward *** STEPS TO REPRODUCE 1. Start RKWard 2. Execute: a = rnorm(1); hist(a, main = expression(paste(mu,"=0"))) 3. I see a blank square instead of the Greek letter "mu" in the title of the plot OBSERVED RESULT A black square is shown instead of the Greek letter "mu" (see the attached screenshot) EXPECTED RESULT The Greek letter "mu" should be displayed in the title of the plot SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux + KDE (available in About System) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.1 Qt Version: 5.15.7 ADDITIONAL INFORMATION --- Please fill in --- --- IMPORTANT NOTE: If possible at all, please use the "Report bug" feature from the "Help" menu inside RKWard. Otherwise, please make sure to read http://rkward.kde.org/bugs for guidelines on what information to include in your report. --- -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461825] New: error doing network task
https://bugs.kde.org/show_bug.cgi?id=461825 Bug ID: 461825 Summary: error doing network task Classification: Applications Product: dolphin Version: 22.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bigalli...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.08.1) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.5-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: was moving network files and it just bugged dolphin , and desktop froze. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x5558799f72c0 in ?? () #5 0x7f1d3eed2855 in QObject::property(char const*) const () from /lib64/libQt5Core.so.5 #6 0x7f1d40bb55f4 in KUiServerV2JobTracker::registerJob(KJob*) () from /lib64/libKF5JobWidgets.so.5 #7 0x7f1d40bb264c in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libKF5JobWidgets.so.5 #8 0x7f1d3eedb9a6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f1d3eedb9a6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f1d3f9e0843 in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /lib64/libQt5DBus.so.5 #11 0x7f1d3f9e1182 in QDBusServiceWatcher::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5 #12 0x7f1d3f9e163b in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5 #13 0x7f1d3f9920bb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5 #14 0x7f1d3eed2c44 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f1d3fbaed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f1d3eea81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f1d3eeab534 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #18 0x7f1d3eef9537 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f1d3cbe5faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f1d3cc3b2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #21 0x7f1d3cbe3940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f1d3eef902a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f1d3eea6c1a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f1d3eeaece2 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55587614ca39 in main () [Inferior 1 (process 9638) detached] The reporter indicates this bug may be a duplicate of or related to bug 372452, bug 375526, bug 387203, bug 451474, bug 455696. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411114] Some touchpad settings get lost after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=44 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458052] New: When opening a new file it deletes the current one without prompt or being able to recover it
https://bugs.kde.org/show_bug.cgi?id=458052 Bug ID: 458052 Summary: When opening a new file it deletes the current one without prompt or being able to recover it Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: frank2018ri...@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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows Windows 10 Pro: 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.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #11 from Francisco Cribari --- Will this bug get fixed soon? It is the sole reason why I'm not on Wayland. Can someone let us know what time frame can be realistic expected for this to be sorted out? Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454959] Electron apps cursor theme
https://bugs.kde.org/show_bug.cgi?id=454959 --- Comment #3 from Francisco Z --- (In reply to Bacteria from comment #2) > I am not able to reproduce it on various electron apps. This is most likely > an electron bug. Can you try on Code - OSS from Arch repo? > > Operating System: Arch Linux > KDE Plasma Version: 5.24.90 > KDE Frameworks Version: 5.94.0 > Qt Version: 5.15.4 > Graphics Platform: Wayland Same in Code - OSS, there is a video: https://files.catbox.moe/f5gzsk.mkv -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454959] Electron apps cursor theme
https://bugs.kde.org/show_bug.cgi?id=454959 Francisco Z changed: What|Removed |Added CC||rhodium@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454959] Electron apps cursor theme
https://bugs.kde.org/show_bug.cgi?id=454959 --- Comment #1 from Francisco Z --- Created attachment 149523 --> https://bugs.kde.org/attachment.cgi?id=149523=edit moar -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454959] New: Electron apps cursor theme
https://bugs.kde.org/show_bug.cgi?id=454959 Bug ID: 454959 Summary: Electron apps cursor theme Product: kwin Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: rhodium@gmail.com Target Milestone: --- Created attachment 149522 --> https://bugs.kde.org/attachment.cgi?id=149522=edit cursor 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. Install any electron app (Visual studio code, heroic launcher, discord...) 2. Open the file picker of the previous installed app under wayland session 3. Mouse cursor theme don't match with breeze cursor. OBSERVED RESULT Cursor theme changes in File Picker or some places under Wayland, it doesn't happend in a X11 session. EXPECTED RESULT Do not change the mouse cursor theme. In X11 session this is fine. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux x64 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION I'm not sure if it's a kde plasma bug or electron, so i open both: https://github.com/electron/electron/issues/34448 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454143] [Wayland] Misplaced position pressing click and navigating in menus
https://bugs.kde.org/show_bug.cgi?id=454143 --- Comment #3 from Francisco Z --- (In reply to Nate Graham from comment #2) > Since you're on X11, the X server is responsible for this, not any KDE code. > I guess X11 is slowly bit-rotting as the world moves to Wayland. I would > recommend that you personally move to use the Plasma Wayland session too, if > possible. > > You could also file a bug report on the X server here: > https://gitlab.freedesktop.org/xorg/xserver/-/issues/ It only happend in Plasma Wayland session, in Plasma X11 is fine :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454143] [Wayland] Misplaced position pressing click and navigating in menus
https://bugs.kde.org/show_bug.cgi?id=454143 Francisco Z changed: What|Removed |Added CC||rhodium@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454143] [Wayland] Misplaced position pressing click and navigating in menus
https://bugs.kde.org/show_bug.cgi?id=454143 --- Comment #1 from Francisco Z --- Created attachment 149068 --> https://bugs.kde.org/attachment.cgi?id=149068=edit another -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454143] New: [Wayland] Misplaced position pressing click and navigating in menus
https://bugs.kde.org/show_bug.cgi?id=454143 Bug ID: 454143 Summary: [Wayland] Misplaced position pressing click and navigating in menus Product: plasmashell Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rhodium@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 149066 --> https://bugs.kde.org/attachment.cgi?id=149066=edit mouse position STEPS TO REPRODUCE 1. Open kate or some kde application, resize and move to the bottom 2. Press left mouse click in File and without releasing, try to navigate tought menus. OBSERVED RESULT Misplaced position of mouse cursor EXPECTED RESULT Good position of mouse cursor, like in X11 session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 451593] rkward constantly crashes
https://bugs.kde.org/show_bug.cgi?id=451593 --- Comment #5 from Francisco Cribari --- UPDATE: I've just experienced a crash with the option "Function argument completion" unticked (all other options activated). -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 451593] rkward constantly crashes
https://bugs.kde.org/show_bug.cgi?id=451593 --- Comment #4 from Francisco Cribari --- (In reply to Thomas Friedrichsmeier from comment #3) > Thanks for clarifying. I'll have to test with KTexteditor 5.92, maybe the > problem is there. > > Things you can do to help track down the bug (or to work around it): > > - Try disabling some completion types in Settings->Configure RKWard->Script > Editor. Perhaps you can pin down, which ones exactly are causing the crash. > - Try compiling the git master version of RKWard. > - If you have that option, try running on a system with an older version of > KTextEditor. > - Should you notice any pattern (e.g. fully repeatable crash on a particular > instruction), please let me know (I have just tried repeatedly typing a > bunch of variations of "pdf(coo", but was unable to produce a crash). I unticked the option "Function call tip" in the "Code Completion / Code Hints" tab of Settings -> Configure RKWard... -> Script editor. Result: no crashes. I then activated back "Function call tip". Result: The crashes returned. I then unticked "Object name completion" (all other options activated). Result: No crashes. I then unticked "Auto word completion (all other options activated). Result: Crashes. I then unticked "Function argument completion (all other options activated). Result: No crashes. I then unticked "Filename completion (all other options activated). Result: Crashes. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 451593] rkward constantly crashes
https://bugs.kde.org/show_bug.cgi?id=451593
--- Comment #2 from Francisco Cribari ---
(In reply to Thomas Friedrichsmeier from comment #1)
> Thanks for reporting.
>
> > The crash can be reproduced every time.
>
> You mean every time you type an instruction in the script window, you are
> getting the crash? Or is it "only" something that happens often? Or does
> this happen, when you type something specific (what)?
>
> I have never seen this bug, before. Which does not mean it isn't real, only
> that I need some more info to find out, where to start looking.
What I mean is that the crashes happen frequently. For instance, I had over ten
crashes today. I start rkward, click on File... select the option Open R Script
File... and then open a file that contains R instructions. Then I execute some
instructions by highlighting them and then pressing CTRL + Enter. For instance,
setwd("~/courses/et588-mr2/programs/")
getwd()
Most crashes happen when I am typing in the script window, e.g., I type
pdf(coo
and then rkward crashes.
--
You are receiving this mail because:
You are watching all bug changes.
[rkward] [Bug 451593] rkward constantly crashes
https://bugs.kde.org/show_bug.cgi?id=451593 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 451593] New: rkward constantly crashes
https://bugs.kde.org/show_bug.cgi?id=451593
Bug ID: 451593
Summary: rkward constantly crashes
Product: rkward
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: rkward-de...@kde.org
Reporter: crib...@gmail.com
Target Milestone: ---
Application: rkward (0.7.2)
Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.16.14-zen1-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.24.3 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I was typing an R instruction in the script window. I have been getting these
crashes regularly.
The crash can be reproduced every time.
-- Backtrace:
Application: RKWard (rkward), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#6 0x7fe413247f34 in QModelIndex::sibling(int, int) const
(this=0x7ffcfc38b958, arow=690569216, acolumn=0) at
/usr/include/qt/QtCore/qabstractitemmodel.h:446
#7 0x7fe413255c19 in KateCompletionModel::mapToSource(QModelIndex const&)
const (this=, proxyIndex=...) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/katecompletionmodel.cpp:919
#8 0x7fe413266c81 in
KateArgumentHintModel::contextMatchQuality(QModelIndex const&) const
(this=0x7ffcfc38b9e0, index=) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/kateargumenthintmodel.cpp:309
#9 0x7fe41325ea83 in ExpandingWidgetModel::matchColor(QModelIndex const&)
const (this=this@entry=0x55d12a162a60, index=...) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/expandingtree/expandingwidgetmodel.cpp:46
#10 0x7fe41325eca8 in ExpandingWidgetModel::data(QModelIndex const&, int)
const (this=this@entry=0x55d12a162a60, index=..., role=role@entry=8) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/expandingtree/expandingwidgetmodel.cpp:81
#11 0x7fe413264c08 in KateArgumentHintModel::data(QModelIndex const&, int)
const (this=0x55d12a162a60, index=..., role=8) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/kateargumenthintmodel.cpp:217
#12 0x7fe41251aca0 in QModelIndex::data(int) const (arole=8,
this=0x7ffcfc38bf70) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:460
#13 QStyledItemDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex
const&) const (this=0x55d12a176390, option=0x7ffcfc38bdf0, index=...) at
itemviews/qstyleditemdelegate.cpp:351
#14 0x7fe41251e81b in QStyledItemDelegate::sizeHint(QStyleOptionViewItem
const&, QModelIndex const&) const (this=this@entry=0x55d12a176390, option=...,
index=...) at itemviews/qstyleditemdelegate.cpp:410
#15 0x7fe4132655d8 in ArgumentHintDelegate::sizeHint(QStyleOptionViewItem
const&, QModelIndex const&) const (this=0x55d12a176390, option=,
index=...) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/kateargumenthinttree.cpp:55
#16 0x7fe41256a54d in QTreeView::indexRowSizeHint(QModelIndex const&) const
(this=0x7ffcfc38bf70, index=) at itemviews/qtreeview.cpp:2995
#17 0x7fe41256a732 in QTreeViewPrivate::itemHeight(int) const (item=0,
this=0x55d12a16c230) at
../../include/QtWidgets/5.15.3/QtWidgets/private/../../../../../src/widgets/itemviews/qtreeview_p.h:85
#18 QTreeViewPrivate::itemHeight(int) const (this=this@entry=0x55d12a16c230,
item=item@entry=1) at itemviews/qtreeview.cpp:3460
#19 0x7fe41256e7f4 in QTreeViewPrivate::updateScrollBars()
(this=0x55d12a16c230) at itemviews/qtreeview.cpp:3711
#20 0x7fe41256eb3b in QTreeView::updateGeometries() (this=0x55d12a16bc10)
at itemviews/qtreeview.cpp:2834
#21 0x7fe4124f3592 in QAbstractItemView::doItemsLayout()
(this=0x55d12a16bc10) at itemviews/qabstractitemview.cpp:1222
#22 0x7fe4125639c3 in QTreeView::doItemsLayout() (this=0x55d12a16bc10) at
itemviews/qtreeview.cpp:2102
#23 0x7fe41256ba22 in QAbstractItemViewPrivate::executePostedLayout() const
(this=0x55d12a16c230) at
../../include/QtWidgets/5.15.3/QtWidgets/private/../../../../../src/widgets/itemviews/qabstractitemview_p.h:94
#24 QAbstractItemViewPrivate::executePostedLayout() const (this=0x55d12a16c230)
at
../../include/QtWidgets/5.15.3/QtWidgets/private/../../../../../src/widgets/itemviews/qabstractitemview_p.h:226
#25 QTreeView::sizeHintForColumn(int) const (this=0x55d12a16bc10, column=0) at
itemviews/qtreeview.cpp:2857
#26 0x7fe41326575e in KateArgumentHintTree::sizeHintForColumn(int) const
(column=0, this=0x55d12a16bc10) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/kateargumenthinttree.cpp:124
#27 KateArgumentHintTree::resizeColumns() (this=0x55d12a16bc10) at
/usr/src/debug/ktexteditor-5.92.0/src/completion/kateargumenthinttree.cpp:231
#28 KateArgumentHintTree::updateGeometry(QRect) (this=0x55d12a16bc10, geom=...)
at
[rkward] [Bug 449696] Error in RK() : Graphics API version mismatch
https://bugs.kde.org/show_bug.cgi?id=449696 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com --- Comment #3 from Francisco Cribari --- I run Arch Linux + KDE, rkward version 0.7.2-1 in a laptop with Intel GPU (mesa driver). I am still experiencing this problem. When I try to plot something, I get the following error message: Error in RK() : Graphics API version mismatch Suggestions are welcome. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450873] Kate crashes when closing many tabs, under a limited number of tabs setting on
https://bugs.kde.org/show_bug.cgi?id=450873 --- Comment #1 from Francisco Boni --- Tentative bug fix and merge request here: https://invent.kde.org/utilities/kate/-/merge_requests/643 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450873] New: Kate crashes when closing many tabs, under a limited number of tabs setting on
https://bugs.kde.org/show_bug.cgi?id=450873 Bug ID: 450873 Summary: Kate crashes when closing many tabs, under a limited number of tabs setting on Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: bobonib...@gmail.com Target Milestone: --- Created attachment 147138 --> https://bugs.kde.org/attachment.cgi?id=147138=edit crash report from kcrash 1. Enable a limited number of tabs 2. Close a large amount of tabs simultaneously, preferably via the Document Tree View OBSERVED RESULT Segmentation Fault EXPECTED RESULT Close all tabs correctly, even under a limited number of tabs setting. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Clear Linux latest KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.91.0 Qt Version: 5.12.2 (with community open-source patches) Kernel: 5.16.11 ADDITIONAL INFORMATION The bug doesn't replicate if we set "Limit number of tabs" to 0 (unlimited). Kate compiled from the latest git. gcc-11.2.0-gd86949f5f5 CXXFLAGS: -ggdb3 -ggnu-pubnames -Og -march=native -mtune=native -Wall -Wl,--as-needed -Wl,--build-id=sha1 -Wl,--enable-new-dtags -Wl,--hash-style=gnu -Wl,-z,now,-z,relro,-z,max-page-size=0x1000,-z,separate-code -mprefer-vector-width=256 -falign-functions=32 -fasynchronous-unwind-tables -fno-stack-protector -fuse-ld=bfd -fuse-linker-plugin -malign-data=cacheline -feliminate-unused-debug-types -mtls-dialect=gnu2 -Wl,-sort-common -Wno-error -Wp,-D_REENTRANT -pipe -fPIC -static-libstdc++ -static-libgcc -pthread CMAKE_BUILD_TYPE=Release BUILD_TESTING:BOOL=OFF -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com --- Comment #19 from Francisco Cribari --- I am also experiencing this bug on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447876] New: [Wayland] Using window rules to pin windows to specific virtual desktops causes "ghost" windows to appear on the pager
https://bugs.kde.org/show_bug.cgi?id=447876 Bug ID: 447876 Summary: [Wayland] Using window rules to pin windows to specific virtual desktops causes "ghost" windows to appear on the pager Product: kwin Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: stu...@pinamartins.com Target Milestone: --- Created attachment 145076 --> https://bugs.kde.org/attachment.cgi?id=145076=edit A screenshot showing the window rules' settings that cause the issue SUMMARY *** I have setup "Window Rules" so that some of my apps are "restricted" to a specific virtual desktop, eg. Firefox to Virtual Desktop 3 (screenshot attached). Under X11, if I am on Virtual Desktop 1, and launch firefox, all firefox windows are launched in Virtual Desktop 3, which is reflected on the pager panel widget. This is the expected behavior. Doing so under wayland, however, results in firefox windows launching on Virtual Desktop 3, but a "ghost" window also appearing on the virtual desktop I have launched it from. Moving the "ghost" window in the pager to a different Virtual Desktop results in moving the actual window there. A "ghost" window remains on the pager where the actual window actually was. Moving the actual window using the pager does not remove the "ghost" window. *** STEPS TO REPRODUCE 1. Create multiple Virtual Desktops and activate the pager widget 2. Set window rules as in the attached screenshot 3. Log in using a wayland session 4. Launch firefox from Virtual Desktop 1 5. Watch how the pager widget makes firefox show up on both Virtual Desktops, even though the window only exists on Virtual Desktop 3 6. This does not occur under X11 OBSERVED RESULT When window rules are active under a wayland session, the pager makes copies of windows on the wrong virtual desktops EXPECTED RESULT The pager widget displays the windows only on the desktop they currently exist in, just like in a X11 session. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I can reproduce the issue on two independent systems -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #12 from Francisco Hurtado --- (In reply to Maik Qualmann from comment #11) > I close the bug because the current digiKam version reads geolocation > metadata from HEIF images. > > Maik Thanks Maik and DK Team! All the best, FH -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #10 from Francisco Hurtado --- (In reply to Maik Qualmann from comment #9) > There will be no fix or workaround if the cause is that you added the HEIC > images before digiKam could support the metadata. > > Go to the search in the left sidebar, enter "heic" in the quick search at > the top. All of your HEIC images should now be displayed, depending on the > number, it may take a while. Select them all, select the option to reread > the metadata from the item menu. > > There is also the maintenance tool, where you can also read the image > metadata again. > > Maik Thanks Maik. I hope you found the traces useful. All the best -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #8 from Francisco Hurtado --- (In reply to caulier.gilles from comment #7) > Francisco, > > I think it's more the new HEIF metadata support introduced in Exiv2 and used > to populate the database which can make mess. > > The Exiv2 version supporting HEIF is 0.27.4: > > https://www.exiv2.org/whatsnew.html > > digiKam for Windows has only used this Exiv2 version with last 7.3.0. > > Best regards > > Gilles Caulier Thanks Gilles for your quick answer. Do you recommend in this case go throuhg a complete re-reading for files? Otherwise, I'll wait for for a fix or workaround. Thanks in advance. Best regards, FH -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #6 from Francisco Hurtado --- Hi Maik, Following your instructions, I've attached some traces made for one image HEIC (IMG_4580.HEIC) that I've copied in Pictures album. Once copied the behaviour is as commented (no metadata for GPS, maybe other are not present). The second part in the traces is when I re-read the metadata of that file from Item menu (and GPS information appears in metadata). I hope was useful. I'm not an expert in software development. A guess: All my heic files were already in others albums in database for long time. Could it be related with some kind of inconsistency in database in previous releases of DK? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 Francisco Hurtado changed: What|Removed |Added CC||fhurtadodu...@gmail.com --- Comment #5 from Francisco Hurtado --- Created attachment 141445 --> https://bugs.kde.org/attachment.cgi?id=141445=edit Traces of DK with new HEIC file in album Pictures -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #3 from Francisco Hurtado --- (In reply to Francisco Hurtado from comment #2) > Thanks Maik for (In reply to Maik Qualmann from comment #1) > > Please upload a sample HEIC image with GPS information. If not public, to my > > email address. > > The sample HEIC images that I have with GPS information are displayed > > correctly in digiKam. > > > > It is possible that the GPS information was not recognized during the first > > scan because the files were locked by other programs. As a test, do a > > re-read of the image metadata via the item menu. > > > > Maik > > Thanks Maik for your quick reply. > > I have followed your indication and I did a re-read of metadata > susccessfully. > > This is interesting because, although I created a new album with photos > taken out of an iphone, it seems that videos and jpgs have no problem to be > read at first moment (with te correct metadata for GPS in digikam) but it > seems that there is a problem only with HEICs. > > In fact, a refresh of the album do not fix the problem. I have to select > photos an re-read metadata. > > What do you think? > > I'll keep you posted if I discover anything more. > > Thanks in advance > > Best New information about this rare behaviour. As mentioned, when I re-read metadata for my apple HEIC photo, all was fine and the GPS metadata are read correctly and digikam store geolocation properly. Well, if I take that photo whose metadata was correctly re-read and stored in digikam, then make a copy of it and refresh the album again, this new copy is not read properly and the geolocation info is not shown at all. Again, if re-read metadata all fine. It seems to me that is something that does not work well in the first reading in digikam for HEIC files. Best -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #2 from Francisco Hurtado --- Thanks Maik for (In reply to Maik Qualmann from comment #1) > Please upload a sample HEIC image with GPS information. If not public, to my > email address. > The sample HEIC images that I have with GPS information are displayed > correctly in digiKam. > > It is possible that the GPS information was not recognized during the first > scan because the files were locked by other programs. As a test, do a > re-read of the image metadata via the item menu. > > Maik Thanks Maik for your quick reply. I have followed your indication and I did a re-read of metadata susccessfully. This is interesting because, although I created a new album with photos taken out of an iphone, it seems that videos and jpgs have no problem to be read at first moment (with te correct metadata for GPS in digikam) but it seems that there is a problem only with HEICs. In fact, a refresh of the album do not fix the problem. I have to select photos an re-read metadata. What do you think? I'll keep you posted if I discover anything more. Thanks in advance Best -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442192] New: [Wayland] Restore session not working
https://bugs.kde.org/show_bug.cgi?id=442192 Bug ID: 442192 Summary: [Wayland] Restore session not working Product: plasmashell Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: crib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Under Wayland, the session is not restored upon reboot, even when the "Restore previous saved session" is selected in system settings. STEPS TO REPRODUCE 1. Start KDE Plasma under Wayland. 2. Open some applications (konsole, kedit, Dolphin, etc.). 3. Reboot. OBSERVED RESULT The previous session is not restored. EXPECTED RESULT The previous session should be restored. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.22.5-2 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378711] [Wayland] Qt and Gtk applications have two different copy stacks
https://bugs.kde.org/show_bug.cgi?id=378711 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com --- Comment #11 from Francisco Cribari --- I am having the same problem under Arch Linux + Wayland. See the details below. SUMMARY Under Wayland, middle mouse copy-paste doesn't work between GTK and Qt applications. STEPS TO REPRODUCE 1. Start KDE Plasma under Wayland. 2. Using a mouse (left button pressed), highlight some text in a GTK application, say, Google Chrome. 3. Move the mouse to a Qt application (for instance, kedit or konsole) and middle-click. OBSERVED RESULT The highlighted text in the GTK application is not copied into the Qt application. EXPECTED RESULT The highlighted text in the GTK application should be copied into the Qt application. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.22.5-2 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] New: HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 Bug ID: 442189 Summary: HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation Product: digikam Version: 7.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Geolocation Assignee: digikam-bugs-n...@kde.org Reporter: fhurtadodu...@gmail.com Target Milestone: --- SUMMARY All HEIC new photos coming from Apple devices have into the metadata their proper GPS coordinates but digikam cannot handle them into its database once the image has been processed. STEPS TO REPRODUCE 1. Put your HEIC geolocated photos in digikam album 2. You can see all metadata information, even the coordinates but the information is not taken into account in digikam database. So you are not able to access to it through the Map view for geolocation. 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.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874 --- Comment #27 from Francisco Cribari --- I am still experiencing the problem (Arch Linux and an external HD with a single ext4 partition). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices after connecting the device for 2nd time
https://bugs.kde.org/show_bug.cgi?id=438874 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com --- Comment #13 from Francisco Cribari --- I run Arch Linux + KDE, and I'm also affected by this bug. I'm using Dolphin to mount and unmount devices. I believe this bug is related to https://bugs.kde.org/show_bug.cgi?id=438478 . -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438062] New: Fallo kde connect
https://bugs.kde.org/show_bug.cgi?id=438062 Bug ID: 438062 Summary: Fallo kde connect Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: franmonte...@gmail.com Target Milestone: --- Application: kdeconnectd (21.04.1) Qt Version: 5.15.3 Frameworks Version: 5.82.0 Operating System: Linux 5.4.0-74-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: fallo de aplicacion a partir de la ultima actualizacion. falla el servicio kde connect The crash can be reproduced every time. -- Backtrace: Application: Demonio de KDE Connect (kdeconnectd), signal: Segmentation fault [New LWP 1488] [New LWP 1515] [New LWP 1526] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fee381e4aff in __GI___poll (fds=0x7ffceb6a7768, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fee346b7d40 (LWP 1463))] Thread 4 (Thread 0x7fee3083a700 (LWP 1526)): #0 0x7fee36d264dd in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fee36cd83f4 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fee36cd9225 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fee36cd94a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fee387b2b3b in QEventDispatcherGlib::processEvents (this=0x7fee28000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fee38756dcb in QEventLoop::exec (this=this@entry=0x7fee30839ce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7fee38570bb2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7fee38571d4c in QThreadPrivate::start (arg=0x559498d9b130) at thread/qthread_unix.cpp:329 #8 0x7fee376fa609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fee381f1293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fee31a4b700 (LWP 1515)): #0 0x7fee36cd88f5 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fee36cd929b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fee36cd94a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fee387b2b3b in QEventDispatcherGlib::processEvents (this=0x7fee24000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fee38756dcb in QEventLoop::exec (this=this@entry=0x7fee31a4acb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fee38570bb2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fee390dbf4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fee38571d4c in QThreadPrivate::start (arg=0x7fee3915fd80) at thread/qthread_unix.cpp:329 #8 0x7fee376fa609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fee381f1293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fee33630700 (LWP 1488)): #0 0x7fee381e4aff in __GI___poll (fds=0x7fee3362fbe8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fee36845c1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fee3684790a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fee33d79e88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fee38571d4c in QThreadPrivate::start (arg=0x559498c5b5d0) at thread/qthread_unix.cpp:329 #5 0x7fee376fa609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fee381f1293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fee346b7d40 (LWP 1463)): [KCrash Handler] #4 Device::reloadPlugins (this=this@entry=0x559498dfa810) at ./core/device.cpp:192 #5 0x7fee39d45562 in Device::addLink (this=this@entry=0x559498dfa810, identityPacket=..., link=, link@entry=0x559498e9c190) at ./core/device.cpp:302 #6 0x7fee39d38b73 in Daemon::onNewDeviceLink (this=0x7ffceb6a9e90, identityPacket=..., dl=0x559498e9c190) at ./core/daemon.cpp:206 #7 0x7fee3878f2ee in QtPrivate::QSlotObjectBase::call (a=0x7ffceb6a8360, r=0x7ffceb6a9e90, this=0x559498debfc0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x559498d0f350, signal_index=3, argv=0x7ffceb6a8360) at kernel/qobject.cpp:3886 #9 0x7fee387886b7 in QMetaObject::activate (sender=sender@entry=0x559498d0f350, m=m@entry=0x7fee39d5d880 ,
[elisa] [Bug 435698] Elisa appears to be blocking the display during playback of music
https://bugs.kde.org/show_bug.cgi?id=435698 Francisco Isgleas changed: What|Removed |Added CC||franci...@isgleas.com --- Comment #1 from Francisco Isgleas --- Created attachment 137699 --> https://bugs.kde.org/attachment.cgi?id=137699=edit elisa supresses power management I can confirm this. The power management widget states: "elisa is currently suppressing power management: playing music" This is preventing the session from locking and screen saver to start, but does not seem to interfere with screen going blank. elisa 20.04.2 Plasma 5.18.6 kernel 5.3.18 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 163014] Broken numbering in nested ol elements (invalid HTML)
https://bugs.kde.org/show_bug.cgi?id=163014 --- Comment #8 from Francisco Galera --- I do not remember this bug. I changed to i3wm some years ago. I do not use kde nowadays.Thankyou, anyway.Best,FG En domingo, 21 de marzo de 2021 1:25:21 CET, Justin Zobel escribió: https://bugs.kde.org/show_bug.cgi?id=163014 --- Comment #7 from Justin Zobel --- Thank you for the bug report. As this report hasn't seen any changes in 10 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 431765] run_tests.py fail when clazy-standalone traverses a symbolic link
https://bugs.kde.org/show_bug.cgi?id=431765 Francisco Boni changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Francisco Boni --- Merged: https://invent.kde.org/sdk/clazy/-/merge_requests/32 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 431765] run_tests.py fail when clazy-standalone traverses a symbolic link
https://bugs.kde.org/show_bug.cgi?id=431765 --- Comment #1 from Francisco Boni --- Proposed fix: https://invent.kde.org/sdk/clazy/-/merge_requests/32 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 431765] New: run_tests.py fail when clazy-standalone traverses a symbolic link
https://bugs.kde.org/show_bug.cgi?id=431765 Bug ID: 431765 Summary: run_tests.py fail when clazy-standalone traverses a symbolic link Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bobonib...@gmail.com CC: smart...@kde.org Target Milestone: --- Clazy-standalone outputs the complete *.cpp file path. Normalizing it so it compares OK with the expected output by using os.getcwd() (run_tests.py:554) doesn't work if the source root is traversed via symbolic link path /insilications/apps/symbolic_link/tests $ ./run_tests.py --verbose Qt version: 51500 Qt headers: /usr/include/qt5 clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang clazy -Wno-unused-value -Qunused-arguments -std=c++14 -isystem /usr/include/qt5 -fPIC -L /usr/lib64 -c -Xclang -plugin-arg-clazy -Xclang post-event post-event/main.cpp Running: clazy-standalone function-args-by-ref/main.cpp -export-fixes=function-args-by-ref/main.cpp.clazy-standalone.yaml -checks=function-args-by-ref -- -Wno-unused-value -Qunused-arguments -std=c++14 -isystem /usr/include/qt5 -fPIC -L /usr/lib64 output_file=function-args-by-ref/main.cpp.out [FAIL] function-args-by-ref/main.cpp (standalone) diff -Naur --strip-trailing-cr function-args-by-ref/main.cpp.expected function-args-by-ref/main.cpp.result --- function-args-by-ref/main.cpp.expected 2021-01-17 19:04:36.916670022 -0300 +++ function-args-by-ref/main.cpp.result 2021-01-17 20:01:05.948949841 -0300 @@ -1,18 +1,18 @@ -function-args-by-ref/main.cpp:245:10: warning: 'virtualMethod2' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] -function-args-by-ref/main.cpp:28:10: warning: Missing reference on non-trivial type (const struct NonTrivial) [-Wclazy-function-args-by-ref] +/insilications/apps/symbolic_link/tests/function-args-by-ref/main.cpp:245:10: warning: 'virtualMethod2' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] +/insilications/apps/symbolic_link/tests/function-args-by-ref/main.cpp:28:10: warning: Missing reference on non-trivial type (const struct NonTrivial) [-Wclazy-function-args-by-ref] Their physical path: /insilications/clazy/tests/function-args-by-ref/main.cpp.expected: function-args-by-ref/main.cpp:245:10: warning: 'virtualMethod2' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] function-args-by-ref/main.cpp:28:10: warning: Missing reference on non-trivial type (const struct NonTrivial) [-Wclazy-function-args-by-ref] /insilications/clazy/tests/function-args-by-ref/main.cpp.result: /insilications/apps/symbolic_link/tests/function-args-by-ref/main.cpp:245:10: warning: 'virtualMethod2' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] /insilications/apps/symbolic_link/tests/function-args-by-ref/main.cpp:28:10: warning: Missing reference on non-trivial type (const struct NonTrivial) [-Wclazy-function-args-by-ref] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426621] [Wayland] Impossible to type accented characters (ô, ã, é, etc) in Qt5 apps
https://bugs.kde.org/show_bug.cgi?id=426621 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393907] Problems with keyboard layout using wayland
https://bugs.kde.org/show_bug.cgi?id=393907 --- Comment #6 from Francisco Cribari --- I am also affected by this. Arch Linux, KDE, Wayland, Brazilian keyboard. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393907] Problems with keyboard layout using wayland
https://bugs.kde.org/show_bug.cgi?id=393907 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 Francisco Isgleas changed: What|Removed |Added CC||franci...@isgleas.com --- Comment #25 from Francisco Isgleas --- Trying to setup a new ews account, authentication is successful when testing connection but the "OK" button remains greyed out. As the configuration has not been saved to this point, the workaround has been not useful, kdepim-runtime 20.04 QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.ews.client: Starting OAuth2 authentication org.kde.pim.ews.client: Launching browser for authentication org.kde.pim.ews.client: PKeyAuth certificates not found org.kde.pim.ews.client: Authentication succeeded -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Francisco Cribari changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 --- Comment #3 from Francisco Cribari --- The problem was solved after libkdcraw was upgraded to version 20.08.2-2 on my system. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] New: Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Bug ID: 427718 Summary: Gwenview does not start Product: gwenview Version: 20.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: crib...@gmail.com Target Milestone: --- SUMMARY I run Arch Linux and KDE Plasma 5.20. I am unable to start gwenview. The version of gwenview in my system is 20.08.2. STEPS TO REPRODUCE 1. Try to start gwenview 2. 3. OBSERVED RESULT Gwenview does not start. The error message: gwenview: symbol lookup error: /usr/lib/libKF5KDcraw.so.5: undefined symbol: _ZN6LibRaw11open_bufferEPvm EXPECTED RESULT Gwenview should start. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, KDE Plasma 5.20 (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Francisco Cribari changed: What|Removed |Added CC|crib...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 421618] Cannot unset filter
https://bugs.kde.org/show_bug.cgi?id=421618 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com --- Comment #3 from Francisco Cribari --- I run Arch Linux and I'm having the same problem with kamoso (version 20.04.2-1). -- 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 Juan Francisco Cantero Hurtado changed: What|Removed |Added CC||juanfra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 419784] New: KSysGuard crashes when try to close.
https://bugs.kde.org/show_bug.cgi?id=419784 Bug ID: 419784 Summary: KSysGuard crashes when try to close. Product: ksysguard Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: francisco.mosqu...@outlook.es CC: plasma-b...@kde.org Target Milestone: --- Application: ksysguard (5.18.4) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.3.0-45-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: Closing it. Extra applications opened: - Mail Client - Mozilla Firefox - WhatsDesk The crash can be reproduced sometimes. -- Backtrace: Application: Monitor del sistema (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f91ab64fc00 (LWP 14448))] Thread 3 (Thread 0x7f916700 (LWP 14452)): #0 0x7f91aaf2bbf9 in __GI___poll (fds=0x7f9168002de0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f919896c5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f919896c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f91a67930db in QEventDispatcherGlib::processEvents (this=0x7f9168000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f91a673263a in QEventLoop::exec (this=this@entry=0x7f916fffe970, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f91a6543317 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7f91a6ec0555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f91a65447ec in QThreadPrivate::start (arg=0x7f91a7138da0) at thread/qthread_unix.cpp:342 #8 0x7f919a8ed6db in start_thread (arg=0x7f916700) at pthread_create.c:463 #9 0x7f91aaf3888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f9176304700 (LWP 14451)): #0 0x7f919a8f39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56452bab3928) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56452bab38d8, cond=0x56452bab3900) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56452bab3900, mutex=0x56452bab38d8) at pthread_cond_wait.c:655 #3 0x7f917763decb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f917763dac7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f919a8ed6db in start_thread (arg=0x7f9176304700) at pthread_create.c:463 #6 0x7f91aaf3888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f91ab64fc00 (LWP 14448)): [KCrash Handler] #6 0x7f91a65ccd4a in operator== (s1=..., s2=...) at text/qstring.cpp:3383 #7 0x7f91a7c82205 in QLabel::setText (this=0x56452bf01970, text=...) at widgets/qlabel.cpp:287 #8 0x7f91ab27b170 in TopLevel::answerReceived (this=0x56452be3c750, id=, answerList=...) at ./gui/ksysguard.cpp:466 #9 0x7f91aa2c6b8a in KSGRD::SensorAgent::processAnswer(char const*, int) () from /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #10 0x7f91aa2cde24 in ?? () from /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #11 0x7f91a676efe7 in QtPrivate::QSlotObjectBase::call (a=0x7ffe78decc30, r=0x56452bee0bf0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #12 doActivate (sender=0x56452be98400, signal_index=15, argv=0x7ffe78decc30) at kernel/qobject.cpp:3870 #13 0x7f91a67698a2 in QMetaObject::activate (sender=sender@entry=0x56452be98400, m=m@entry=0x7f91a6bff7e0 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffe78decc30) at kernel/qobject.cpp:3930 #14 0x7f91a66a22ba in QProcess::readyReadStandardOutput (this=this@entry=0x56452be98400, _t1=...) at .moc/moc_qprocess.cpp:367 #15 0x7f91a66a8b11 in QProcessPrivate::tryReadFromChannel (this=0x56452bee36c0, channel=0x56452bee37d0) at io/qprocess.cpp:1073 #16 0x7f91a66a8fe0 in QProcessPrivate::_q_canReadStandardOutput (this=) at io/qprocess.cpp:1084 #17 QProcess::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffe78decde0) at .moc/moc_qprocess.cpp:208 #18 0x7f91a676edc9 in doActivate (sender=0x56452beb5bd0, signal_index=3, argv=0x7ffe78decde0) at kernel/qobject.cpp:3882 #19 0x7f91a67698a2 in QMetaObject::activate (sender=sender@entry=0x56452beb5bd0, m=m@entry=0x7f91a6c01bc0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe78decde0) at kernel/qobject.cpp:3930 #20 0x7f91a67725c8 in QSocketNotifier::activated (this=this@entry=0x56452beb5bd0, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141 #21 0x7f91a6772982 in QSocketNotifier::event
[frameworks-kio] [Bug 414264] Misleading error message on webdavs protocol
https://bugs.kde.org/show_bug.cgi?id=414264 Juan Francisco Cantero Hurtado changed: What|Removed |Added Version|5.64.0 |5.66.0 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||juanfra...@gmail.com --- Comment #1 from Juan Francisco Cantero Hurtado --- I see the same error when I try to log in a nextcloud server. Log in to Box.com works fine. The same nextcloud url, user and password works using Thunar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 --- Comment #14 from Francisco Cribari --- I'm experiencing the same error under Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408279] Battery and brightness widget doesn't show correct time remaining estimate
https://bugs.kde.org/show_bug.cgi?id=408279 --- Comment #19 from Francisco Cribari --- More info... ┌─[cribari @ darwin5r ~] └─╼ upower -e /org/freedesktop/UPower/devices/battery_BAT0 /org/freedesktop/UPower/devices/line_power_ADP1 /org/freedesktop/UPower/devices/battery_BAT1 /org/freedesktop/UPower/devices/mouse_dev_EC_10_CC_F1_B3_3C /org/freedesktop/UPower/devices/DisplayDevice ┌─[cribari @ darwin5r ~] └─╼ inxi -B Battery: ID-1: BAT1 charge: 31.2 Wh condition: 31.2/30.0 Wh (104%) ┌─[cribari @ darwin5r ~] └─╼ ls /sys/class/power_supply ADP1 BAT1 ┌─[cribari @ darwin5r ~] └─╼ ls /sys/class/power_supply/BAT1 alarm current_now power type capacitycycle_count presentuevent capacity_level deviceserial_number voltage_min_design charge_full hwmon4status voltage_now charge_full_design manufacturer subsystem charge_now model_nametechnology -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408279] Battery and brightness widget doesn't show correct time remaining estimate
https://bugs.kde.org/show_bug.cgi?id=408279 --- Comment #18 from Francisco Cribari --- Arch Linux, KDE Plasma 5.17.4, Samsung laptop: ┌─[cribari @ darwin5r ~] └─╼ acpi -ib Battery 0: Discharging, 100%, 03:33:43 remaining Battery 0: design capacity 3950 mAh, last full capacity 4100 mAh = 100% ┌─[cribari @ darwin5r ~] └─╼ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: (null) power supply: no updated: Wed 31 Dec 1969 09:00:00 PM -03 (1576260181 seconds ago) has history: no has statistics: no unknown warning-level: unknown battery-level: unknown icon-name: '(null)' ┌─[cribari @ darwin5r ~] └─╼ upower -i /org/freedesktop/UPower/devices/battery_BAT1 native-path: BAT1 vendor: SAMSUNG Electronics model:SR Real Battery serial: 123456789 power supply: yes updated: Fri 13 Dec 2019 03:02:41 PM -03 (29 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 31.16 Wh energy-empty:0 Wh energy-full: 31.16 Wh energy-full-design: 30.02 Wh energy-rate: 8.1776 W voltage: 8.597 V time to empty: 3.8 hours percentage: 100% capacity:100% technology: lithium-ion icon-name: 'battery-full-symbolic' ┌─[cribari @ darwin5r ~] └─╼ upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep "time" time to empty: 3.8 hours -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408279] Battery and brightness widget doesn't show correct time remaining estimate
https://bugs.kde.org/show_bug.cgi?id=408279 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com --- Comment #17 from Francisco Cribari --- I have the same problem with KDE Plasma (version 5.17.4) under both Arch Linux and Manjaro. The battery widget only informs me the percentage remaining. I no longer see the estimated remaining time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 414721] New: No acceso total al terminar
https://bugs.kde.org/show_bug.cgi?id=414721 Bug ID: 414721 Summary: No acceso total al terminar Product: konsole Version: 18.04.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: monitoring Assignee: konsole-de...@kde.org Reporter: atiladelmo...@gmail.com Target Milestone: --- SUMMARY 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 Negativo acceso al terminal -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #118 from Francisco Cribari --- Created attachment 123898 --> https://bugs.kde.org/attachment.cgi?id=123898=edit New crash information added by DrKonqi baloo_file (5.64.0) using Qt 5.13.2 - What I was doing when the application crashed: The crash happens at every single login. - Unusual behavior I noticed: Crash - Custom settings of the application: No custom settings. Crash happens with the vailla kernel and also with the zen kernel. I use the Breeze theme and no custom settings. -- Backtrace (Reduced): #13 0x7fa7477be619 in mdb_cursor_put () from /usr/lib/liblmdb.so #14 0x7fa7477c14ab in mdb_put () from /usr/lib/liblmdb.so #15 0x7fa7492d0b7a in Baloo::DocumentTimeDB::put(unsigned long long, Baloo::DocumentTimeDB::TimeInfo const&) () from /usr/lib/libKF5BalooEngine.so.5 #16 0x7fa7492f7a95 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags) () from /usr/lib/libKF5BalooEngine.so.5 #17 0x7fa7492ea695 in Baloo::Transaction::replaceDocument(Baloo::Document const&, QFlags) () from /usr/lib/libKF5BalooEngine.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413892] New: Plasma crash under Wayland when I unplugged second monitor
https://bugs.kde.org/show_bug.cgi?id=413892 Bug ID: 413892 Summary: Plasma crash under Wayland when I unplugged second monitor Product: plasmashell Version: 5.17.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: crib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.2) Qt Version: 5.13.2 Frameworks Version: 5.63.0 Operating System: Linux 5.3.8-zen1-1-zen x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Plasma crashed when I unplugged a HDMI projection (second monitor). Plugged the projector and all went well. When I unplugged it Plasma crashed. - Unusual behavior I noticed: Plasma crash. - Custom settings of the application: No custom settings. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb00c37ac80 (LWP 11176))] Thread 12 (Thread 0x7fafe21e0700 (LWP 11545)): #0 0x7fb0104bbc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb010fca610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb010fca702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb012c50e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb012c510ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fafcb7fe700 (LWP 11462)): #0 0x7fb0104bbc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb010fca610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb010fca702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb012c50e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb012c510ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fafcbfff700 (LWP 11441)): #0 0x7fb00f2d94e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7fb00f329088 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb00f329241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb0111eab2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb01119183c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb010fc3305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #7 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fafe19df700 (LWP 11422)): #0 0x7fb0104bbc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb010fca610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb010fca702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb012c50e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb012c510ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7faff4c8d700 (LWP 11419)): #0 0x7fb00f326dbb in () at /usr/lib/libglib-2.0.so.0 #1 0x7fb00f3276cc in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb00f32898b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7fb00f329096 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb00f329241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb0111eab2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb01119183c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fb010fc3305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #9 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fafe34e7700 (LWP 11382)): #0 0x7fb00f32067f in g_source_ref () at /usr/lib/libglib-2.0.so.0 #1 0x7fb00f3276b2 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb00f32782f in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3
[KScreen] [Bug 413174] 5.17 lost the ability to detect when a monitor is unplugged during a session
https://bugs.kde.org/show_bug.cgi?id=413174 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 369077] Issues with UEFI dual booting with other Ubuntu OS's
https://bugs.kde.org/show_bug.cgi?id=369077 Francisco Matheus changed: What|Removed |Added CC||francisco.matheus.souza@gma ||il.com -- You are receiving this mail because: You are watching all bug changes.
