[plasmashell] [Bug 396083] Media Player widget doesn't update correctly
https://bugs.kde.org/show_bug.cgi?id=396083 --- Comment #6 from el...@seznam.cz --- Spotify flatpak org.mpris.MediaPlayer2.Player.Rate = 1 org.mpris.MediaPlayer2.Player.Position = 0 (always) org.mpris.MediaPlayer2.Player.CanSeek = false I also checked DeaDBeeF org.mpris.MediaPlayer2.Player.Rate = 1 org.mpris.MediaPlayer2.Player.Position = long int that changes org.mpris.MediaPlayer2.Player.CanSeek = true So it looks like spotify must be fixed, right? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382174] Not creating thumbnails and not editing (F4) files created for Samsung panorama jpgs [patch]
https://bugs.kde.org/show_bug.cgi?id=382174 Maik Qualmann changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Maik Qualmann --- Gilles, can you please update the AppImage, I had tested it only with Samsung S7 test images. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382174] Not creating thumbnails and not editing (F4) files created for Samsung panorama jpgs [patch]
https://bugs.kde.org/show_bug.cgi?id=382174 --- Comment #15 from Maik Qualmann --- Git commit 2e885007206da2bc608ea7494c6cd2fdedba6c9f by Maik Qualmann. Committed on 05/07/2018 at 05:48. Pushed by mqualmann into branch 'master'. fix crash with Samsung S8 panoramas M +7-2core/libs/dimg/loaders/jpegloader.cpp https://commits.kde.org/digikam/2e885007206da2bc608ea7494c6cd2fdedba6c9f -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules
https://bugs.kde.org/show_bug.cgi?id=361708 --- Comment #5 from battagli...@gmail.com --- Finally, I note the problem may result from a discrepancy between upower and acpi. Note the following terminal results. Both of these are in the state where the AC is not plugged in, but the tray icon still says discharging (even though battery panel icon says discharging): $ acpi -V Battery 0: Discharging, 50%, 01:55:40 remaining Battery 0: design capacity 5006 mAh, last full capacity 4092 mAh = 81% Adapter 0: off-line <- NOTE HERE Thermal 0: ok, 40.0 degrees C Thermal 0: trip point 0 switches to mode hot at temperature 240.0 degrees C Thermal 1: ok, 35.3 degrees C Thermal 1: trip point 0 switches to mode hot at temperature 60.0 degrees C Thermal 2: ok, 0.0 degrees C Thermal 2: trip point 0 switches to mode hot at temperature 97.0 degrees C Thermal 3: ok, 38.0 degrees C Thermal 3: trip point 0 switches to mode hot at temperature 54.0 degrees C Cooling 0: x86_pkg_temp no state information available Cooling 1: Processor 0 of 10 Cooling 2: Processor 0 of 10 Cooling 3: intel_powerclamp no state information available Cooling 4: pch_skylake no state information available Cooling 5: Processor 0 of 10 Cooling 6: Processor 0 of 10 Note that Adapter 0 is offline. On the other hand, here's upower -u. Note Adapter 0 (line_power_ADP1) is ONLINE! ~ $ upower -d Device: /org/freedesktop/UPower/devices/line_power_ADP1 native-path: ADP1 power supply: yes updated: Thu 05 Jul 2018 12:54:02 AM EDT (2262 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes <- SEE HERE icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT1 native-path: BAT1 vendor: SMP model:X910527 serial: 39135 power supply: yes updated: Thu 05 Jul 2018 01:31:23 AM EDT (21 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 15.547 Wh energy-empty:0 Wh energy-full: 31.192 Wh energy-full-design: 38.152 Wh energy-rate: 7.507 W voltage: 7.567 V time to empty: 2.1 hours percentage: 49% capacity:81.7572% technology: lithium-ion icon-name: 'battery-good-symbolic' History (charge): 1530768666 49.000 discharging History (rate): 1530768683 7.507 discharging 1530768682 18.735 charging 1530768675 7.695 discharging 1530768666 8.580 discharging Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 05 Jul 2018 01:31:23 AM EDT (21 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: none energy: 15.547 Wh energy-full: 31.192 Wh energy-rate: 7.507 W time to empty: 2.1 hours percentage: 49% icon-name: 'battery-good-symbolic' Daemon: daemon-version: 0.99.4 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules
https://bugs.kde.org/show_bug.cgi?id=361708 --- Comment #4 from battagli...@gmail.com --- Created attachment 113772 --> https://bugs.kde.org/attachment.cgi?id=113772=edit All charging One more - now things are plugged in. Note that the tray icon is "charging", and now the battery icon in the panel dropdown is also "charging." In the previous screenshot, the battery icon in the panel dropdown was the normal "discharging" battery. However, crucially, in both cases, the battery tray icon was charging -- even though it is only really charging in this one and not the last one. The tray icon seems to dictate which power management behaviors are followed, so that it always does AC mode even if discharging. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules
https://bugs.kde.org/show_bug.cgi?id=361708 --- Comment #3 from battagli...@gmail.com --- Created attachment 113771 --> https://bugs.kde.org/attachment.cgi?id=113771=edit Battery inconsistency Note the tray icon still has the battery in AC mode, even though it is listed as "Discharging" in the panel. More importantly, the power management settings still respond as if the AC were plugged in. I want it to auto-suspend only if battery is discharging and not suspend if AC is plugged in. The result here is that it thinks the AC is plugged in, discharges, and drains the battery. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules
https://bugs.kde.org/show_bug.cgi?id=361708 battagli...@gmail.com changed: What|Removed |Added CC||battagli...@gmail.com --- Comment #2 from battagli...@gmail.com --- Same exact issue - on Neon Xenial running Plasma 5.13. `acpi` and `upower` will show the battery charge/discharge status correctly responding to AC plug on/off events, but the plasmashell battery icon will remain on "plugged in" mode even if I unplug. Strangely, sometimes the battery icon will still say "plugged in," even though when I click on the battery, it still says "discharging". Screenshot attached below. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update
https://bugs.kde.org/show_bug.cgi?id=384459 jMdZ changed: What|Removed |Added CC||mauro.da...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 209885] KDiff3 preprocessor command won't accept single quotes like the docs say
https://bugs.kde.org/show_bug.cgi?id=209885 michael changed: What|Removed |Added CC||reeves...@gmail.com Assignee|joachim.e...@gmx.de |reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 396019] Folding layer 1 not possible when layer 2 yet folded
https://bugs.kde.org/show_bug.cgi?id=396019 jMdZ changed: What|Removed |Added CC||mauro.da...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #12 from Shmerl --- So what exactly can be segfaulting using QThread and libwayland-client.so.0.3.0? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #11 from Martin Flöser --- According to the log KWin is not segfaulting but exiting due to drm Backend Not working. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396173] kwin_x11 --replace ignores other virtual desktops
https://bugs.kde.org/show_bug.cgi?id=396173 Martin Flöser changed: What|Removed |Added Flags||Wayland-, X11+ -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 272530] Kdiff3 documentation not available
https://bugs.kde.org/show_bug.cgi?id=272530 michael changed: What|Removed |Added Assignee|joachim.e...@gmx.de |reeves...@gmail.com Status|ASSIGNED|RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 294941] KDIFF3 crashes, when checking large tasks
https://bugs.kde.org/show_bug.cgi?id=294941 michael changed: What|Removed |Added Assignee|joachim.e...@gmx.de |reeves...@gmail.com Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 152669] wish: horizontal scrolling with alt+wheelmouse / touchpad
https://bugs.kde.org/show_bug.cgi?id=152669 michael changed: What|Removed |Added Assignee|joachim.e...@gmx.de |reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 104784] triple-merge: io-errors cause empty files for identification
https://bugs.kde.org/show_bug.cgi?id=104784 michael changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED Assignee|joachim.e...@gmx.de |reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 306909] Unable to save files when -o parameter is used. Message says: klauncher said: Unknown protocol ''.
https://bugs.kde.org/show_bug.cgi?id=306909 michael changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REOPENED|RESOLVED Assignee|joachim.e...@gmx.de |reeves...@gmail.com --- Comment #4 from michael --- Please verify with lastest kdiff3 I am unable to repo. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 256842] Whish: Integration in Dolphin context menu
https://bugs.kde.org/show_bug.cgi?id=256842 michael changed: What|Removed |Added Assignee|joachim.e...@gmx.de |reeves...@gmail.com Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 165473] KDiff3 doesn't reload non-local files
https://bugs.kde.org/show_bug.cgi?id=165473 michael changed: What|Removed |Added CC|reeves...@gmail.com | Assignee|joachim.e...@gmx.de |reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 165473] KDiff3 doesn't reload non-local files
https://bugs.kde.org/show_bug.cgi?id=165473 michael changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 140286] Merging affects dirs and files that are ignored by dir-anti-pattern
https://bugs.kde.org/show_bug.cgi?id=140286 michael changed: What|Removed |Added Assignee|joachim.e...@gmx.de |reeves...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 116840] Comparing a local with a file via kio does not work
https://bugs.kde.org/show_bug.cgi?id=116840 michael changed: What|Removed |Added CC||reeves...@gmail.com Assignee|joachim.e...@gmx.de |reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 116840] Comparing a local with a file via kio does not work
https://bugs.kde.org/show_bug.cgi?id=116840 michael changed: What|Removed |Added CC|reeves...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 116840] Comparing a local with a file via kio does not work
https://bugs.kde.org/show_bug.cgi?id=116840 michael changed: What|Removed |Added CC|reeves...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 116840] Comparing a local with a file via kio does not work
https://bugs.kde.org/show_bug.cgi?id=116840 michael changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396180] New: Crash on pause after adding video to timeline
https://bugs.kde.org/show_bug.cgi?id=396180 Bug ID: 396180 Summary: Crash on pause after adding video to timeline Product: kdenlive Version: unspecified Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: xorport+kdebugtr...@gmail.com Target Milestone: --- This was tested on kdenlive-18.08-beta17-x86_64.AppImage Steps to reproduce: Add clip Drag it to the very beginning of the timeline Press play, then pause Bug can be reproduced only on clean new project. error: Assertion fctx->async_lock failed at libavcodec/pthread_frame.c:153 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394993] In recent beta version of kdeconncet android app, fails to send files from device to computer
https://bugs.kde.org/show_bug.cgi?id=394993 xbbsky <619082...@qq.com> changed: What|Removed |Added CC||619082...@qq.com --- Comment #10 from xbbsky <619082...@qq.com> --- I've tried kdeconnect version 1.0.3 on ubuntu 18.04, and failed to send files from device to computer. But I succeeded with kdeconnect version 1.0.3 on ubuntu 16.04. Hope this message help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396179] New: Krita crashing randomly
https://bugs.kde.org/show_bug.cgi?id=396179 Bug ID: 396179 Summary: Krita crashing randomly Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: turtleyboy...@gmail.com Target Milestone: --- Created attachment 113770 --> https://bugs.kde.org/attachment.cgi?id=113770=edit kritacrash.log I just upgraded from Krita 4.0.3 to 4.1.0 and it's been crashing too often for no reason. I submitted a post on the Krita sub: (https://www.reddit.com/r/krita/comments/8vzjgc/i_just_installed_krita_410_and_it_crashes_too/) And I've been told to submit a bug with the kritacrash.log information if the transform tool fix in the kritarc file doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396178] New: Content of mount-binded device is incorrect
https://bugs.kde.org/show_bug.cgi?id=396178 Bug ID: 396178 Summary: Content of mount-binded device is incorrect Product: dolphin Version: 18.04.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: incompl...@aixon.co Target Milestone: --- Say you have an external USB HDD, on which there is partition /dev/sdx1 labeled "somelabel", and there is an folder named "foo" on this partition, if you: step 1: plugin the external device, click the "somelabel" device located under "Removable Devices" section in dolphin, to mount this partition (/dev/sdx1) on /run/media/username/somelabel step 2: drag /home/username/bar to the "Places" section in dolphin step 3: sudo mount --bind /run/media/username/somelabel/foo /home/username/bar, where bar is folder that is not on /dev/sdx1 step 4: click "bar" in the "Places" section step 5: click "somelabel" in the "Removable Devices" section step 6: close dolphin step 7: open dolphin again, and click "somelabel" in the "Removable Devices" section, you will see contents of /run/media/username/somelabel/foo, while contents of /run/media/username/somelabel are expected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396065] Brush tools,vector tools, or any drawing tools won't work
https://bugs.kde.org/show_bug.cgi?id=396065 --- Comment #3 from vanyossi --- that is strange. Cna you save the file? The drawing you are trying to finish cannot be drawn to even if krita is restarted and the file reopened? If that is the case, can you share the .kra file with us? You can attach it here or if it is too big, store it somewhere (mega, gdrive, dropbox) and send us the link. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #10 from Shmerl --- I also copied startplasmacompositor and edited kwin launch there to use: gdb -ex run --args /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/x86_64-linux-gnu/libexec/startplasma It hung the system completely to me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #9 from Shmerl --- Is there some way to force core generation? I'm not sure why it's not created, ulimit is set to unlimited. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 Maximilian Böhm changed: What|Removed |Added CC||m...@elbmurf.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396065] Brush tools,vector tools, or any drawing tools won't work
https://bugs.kde.org/show_bug.cgi?id=396065 --- Comment #2 from deeisabe...@gmail.com --- Hello. The problem might have not been the version I used of Krita. I had an older version with the same issue, then thought updating the software would fix it, but it didn't. I was lining a drawing of mine and I had almost finished, but as I was about to finish, any drawing tools I tried to use stopped working. I checked if I had accidentally made the layer I was working on invisible or if I was on eraser mode, but I wasn't. I've also tried deleting the layer and creating a new one, but that didn't fix the problem either. I opened a new document and the drawing tools work, but they won't work on the drawing I'm currently trying to finish. On Tue, Jul 3, 2018 at 7:16 PM, vanyossi wrote: > https://bugs.kde.org/show_bug.cgi?id=396065 > > vanyossi changed: > >What|Removed |Added > > > CC||ghe...@gmail.com > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from vanyossi --- > Hi! > > It's nearly impossible to know what is happening to you with so little > detail! > Please could you explain what you were doing when the tools stopped > working? A > step by step procedure to make it happen. Also adding a video of it > happening > would be of great help > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396150] Multiline tool is broken
https://bugs.kde.org/show_bug.cgi?id=396150 --- Comment #2 from Jordan Ferrazza --- I will. What is with the broken tool? Deprecation? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 396177] Plasmashell dialog regression when KDE is used with Xmonad introduced by bugfix 381242.
https://bugs.kde.org/show_bug.cgi?id=396177 charlie.pauc...@openmailbox.org changed: What|Removed |Added CC||charlie.paucard@openmailbox ||.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 396177] New: Plasmashell dialog regression when KDE is used with Xmonad introduced by bugfix 381242.
https://bugs.kde.org/show_bug.cgi?id=396177
Bug ID: 396177
Summary: Plasmashell dialog regression when KDE is used with
Xmonad introduced by bugfix 381242.
Product: frameworks-plasma
Version: 5.47.0
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: libplasmaquick
Assignee: notm...@gmail.com
Reporter: charlie.pauc...@openmailbox.org
Target Milestone: ---
Opening dialogs such as the "application launcher" when XMonad is used as a
window manager fails. Most of the time, the dialog fails to appear, or is
immediately closed when it does,
This regression was introduced by Plasma Framework version 5.47.0.
Reverting 11f4e5b392acade56ad240f695f66eb42377e57c on plasma-framework.git (the
commit introduced by bugfix 381242) seems to fix the issue.
Related: https://bugs.kde.org/show_bug.cgi?id=381242
## Reproducible ?
Successfully reproduced on clean and up to date KDE build, with empty XMonad
configuration file, and empty KDE configuration.
## Steps to reproduce
1/ Install XMonad, and set XMonad as the window manager for KDE:
echo "export KDEWM=/usr/bin/xmonad" >>
${XDG_CONFIG_HOME:-$HOME/.config}/plasma-workspace/env/wm.sh
2/ [Optional] Move the "dashboard panel" to the top of the screen. I have found
the bug to be significantly more likely when the panel is at the top of the
screen.
3/ Re-launch KDE.
4/ Repeatedly attempt to open dialogs on the dashboard panel, e.g. the
application launcher. Most of the time, the dialogs will not appear, or will be
closed immediately.
## Versions
KDE Frameworks 5.47.0, KDE Plasma 5.13, and XMonad 0.13.
--
You are receiving this mail because:
You are watching all bug changes.
[elisa] [Bug 391462] Wrong search behaviour
https://bugs.kde.org/show_bug.cgi?id=391462 Stefan Brüns changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #5 from Stefan Brüns --- Michal, this is still missing the output from balooshow -x If you don't provide the information required for fixing this problem, we are unfortunately forced to close this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #8 from Shmerl --- startplasmacompositor: Starting up... dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 No backend specified through command line argument, trying auto resolution FATAL ERROR: backend failed to initialize, exiting now Segmentation fault startplasmacompositor: Shutting down... startplasmacompositor: Done. I tried it a few times - that segfault doesn't happen every time, and I don't see any cores. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396175] plasma-workspace-5.13.2 crashes switching between activities
https://bugs.kde.org/show_bug.cgi?id=396175 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |CONFIRMED --- Comment #3 from David Edmundson --- Bug is real + obvious. Will fix -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #7 from David Edmundson --- try dbus-launch startplasmacompositor instead -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 395948] Juk tag editor doesn't work
https://bugs.kde.org/show_bug.cgi?id=395948 Michael Pyne changed: What|Removed |Added Version Fixed In||18.08 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/juk ||/117646dd6232b0843ebce081ec ||6c591899516f16 --- Comment #2 from Michael Pyne --- Git commit 117646dd6232b0843ebce081ec6c591899516f16 by Michael Pyne. Committed on 04/07/2018 at 23:28. Pushed by mpyne into branch 'master'. Bring back inline tag editing. This was a KDE 4 JuK feature that had been left disabled in the port to Plasma 5/KF5. I finished the implementation here in response to a user request. Given the code changes it's technically best described as a new feature (even if it used to work in KDE 4) so it probably won't show up until the next release of KDE Applications, though it should be safe to backport for interested distributions. GUI: FIXED-IN:18.08 M +33 -74 playlist.cpp M +1-10 playlist.h M +2-2playlistitem.cpp https://commits.kde.org/juk/117646dd6232b0843ebce081ec6c591899516f16 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #6 from Shmerl --- I tried to start Plasma session manually from tty, and got this: startplasmacompositor: Starting up... dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments No backend specified through command line argument, trying auto resolution FATAL ERROR: backend failed to initialize, exiting now startplasmacompositor: Shutting down... startplasmacompositor: Done. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #6 from Jérôme Carretero --- Workaround for the particular Qt 5.11 scenario: compiling qtcore with CXXFLAGS+=" -mno-rdrnd". -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #5 from Tom Hughes --- Well running a program that's hard coded to use it on a CPU that doesn't support it is always going to fail, so don't do that... Valgrind runs your program on an emulated CPU that is normally close to, but not identical to, your actual CPU which is why we adjust the CPUID to indicate what features are actually available. Unless you're only planning to run your program on specific hardware then it really needs to check this kind of thing at run time anyway. *** This bug has been marked as a duplicate of bug 353370 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9
https://bugs.kde.org/show_bug.cgi?id=353370 Tom Hughes changed: What|Removed |Added CC||cj-...@zougloub.eu --- Comment #20 from Tom Hughes --- *** Bug 396176 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #4 from Jérôme Carretero --- Tested with the now's SVN, it's still unhandled. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #3 from Jérôme Carretero --- actually, that issues disables advertising rdrand in CPUID, but what if the program is hard-coded to use it... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #2 from Jérôme Carretero --- Might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=353370 but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #1 from Jérôme Carretero --- It's rdrand32_step (used as a gcc built-in) vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==30590== valgrind: Unrecognised instruction at address 0x846054f. ==30590==at 0x846054F: _rdrand32_step (immintrin.h:109) ==30590==by 0x846054F: qt_random_cpu (qrandom.cpp:114) ==30590==by 0x846054F: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (qrandom.cpp:369) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] New: vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 Bug ID: 396176 Summary: vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6 Product: valgrind Version: 3.13.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: cj-...@zougloub.eu Target Milestone: --- vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==17999== valgrind: Unrecognised instruction at address 0x846054f. ==17999==at 0x846054F: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x84609C8: QRandomGenerator::_fillRange(void*, void*) (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x84A2F55: qt_create_qhash_seed() (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x84A2FA3: qt_initialize_qhash_seed() (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x84A3210: QHashData::detach_helper(void (*)(QHashData::Node*, void*), void (*)(QHashData::Node*), int, int) (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x84B90B1: QHash::Node>::detach() (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x84B58D9: prepareEngine(QRegExpPrivate*) (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x84B5A87: QRegExp::QRegExp(QString const&, Qt::CaseSensitivity, QRegExp::PatternSyntax) (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x8507A2D: QDirIteratorPrivate::QDirIteratorPrivate(QFileSystemEntry const&, QStringList const&, QFlags, QFlags, bool) (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x8507EDF: QDirIterator::QDirIterator(QString const&, QStringList const&, QFlags, QFlags) (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x8504DE1: QDir::entryList(QStringList const&, QFlags, QFlags) const (in /usr/lib64/libQt5Core.so.5.11.1) ==17999==by 0x8504F3E: QDir::entryList(QFlags, QFlags) const (in /usr/lib64/libQt5Core.so.5.11.1) (checking the instruction (recompiling qtcore...), will follow-up in a few minutes) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396175] plasma-workspace-5.13.2 crashes switching between activities
https://bugs.kde.org/show_bug.cgi?id=396175 --- Comment #2 from Pablo Cholaky --- I forgot, also recompiled kwin on that batch. Sorry for too many post responses. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395549] Some effects not doing anything but shows a status bar that stays forever rolling.
https://bugs.kde.org/show_bug.cgi?id=395549 --- Comment #10 from eugeneyale --- In fact, none of those under miscellaneous has parameters with kdenlive-18.08-beta15-x86_64.AppImage and kdenlive-18.08-beta16-x86_64.AppImage version -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396175] plasma-workspace-5.13.2 crashes switching between activities
https://bugs.kde.org/show_bug.cgi?id=396175 --- Comment #1 from Pablo Cholaky --- I recompiled qtcore, qtgui, qtquickcontrols without debug flags and seems to work again. May it be a compilation mistake by myself? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396175] plasma-workspace-5.13.2 crashes switching between activities
https://bugs.kde.org/show_bug.cgi?id=396175 David Edmundson changed: What|Removed |Added Version|5.13.2 |5.47.0 Product|plasmashell |frameworks-kactivities-stat ||s Target Milestone|1.0 |--- Assignee|k...@davidedmundson.co.uk|ivan.cu...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395549] Some effects not doing anything but shows a status bar that stays forever rolling.
https://bugs.kde.org/show_bug.cgi?id=395549 --- Comment #9 from eugeneyale --- Hi tried kdenlive-18.08-beta16-x86_64.AppImage today the bug is fixed for chromakey News bugs appear : Atadenoise, noise and perspective haven't any parameters. I just have the title the menu isn't fully translated mix between French and English -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396175] New: plasma-workspace-5.13.2 crashes switching between activities
https://bugs.kde.org/show_bug.cgi?id=396175 Bug ID: 396175 Summary: plasma-workspace-5.13.2 crashes switching between activities Product: plasmashell Version: 5.13.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: walterc...@slash.cl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.2) (Compiled from sources) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.0-waltercool x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: Reproducing the problem is fair easily than using the shortcut to switch between activities. plasma-workspace crashes each time I trigger the control. Using Qt 5.11.1, Plasma 5.13.2 and Frameworks 5.37.0. Gentoo. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f417c5880 (LWP 29568))] Thread 13 (Thread 0x7f1e4bbff700 (LWP 29586)): #0 0x7f1f3a18f57c in futex_wait_cancelable (private=, expected=0, futex_word=0x559e25b353a4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x559e25b35350, cond=0x559e25b35378) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x559e25b35378, mutex=0x559e25b35350) at pthread_cond_wait.c:655 #3 0x7f1f3b05e003 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x559e25b35350) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x559e257745e8, mutex=mutex@entry=0x559e257745e0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7f1f3effe188 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x559e257745d8) at scenegraph/qsgthreadedrenderloop.cpp:245 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x559e25774560) at scenegraph/qsgthreadedrenderloop.cpp:709 #7 0x7f1f3effe5ba in QSGRenderThread::run (this=0x559e25774560) at scenegraph/qsgthreadedrenderloop.cpp:738 #8 0x7f1f3b05d896 in QThreadPrivate::start (arg=0x559e25774560) at thread/qthread_unix.cpp:367 #9 0x7f1f3a18896a in start_thread (arg=0x7f1e4bbff700) at pthread_create.c:463 #10 0x7f1f3a8e805f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f1e64e9b700 (LWP 29585)): #0 0x7f1f3a18f57c in futex_wait_cancelable (private=, expected=0, futex_word=0x559e25620c44) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x559e25620bf0, cond=0x559e25620c18) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x559e25620c18, mutex=0x559e25620bf0) at pthread_cond_wait.c:655 #3 0x7f1f3b05e003 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x559e25620bf0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x559e25752e18, mutex=mutex@entry=0x559e25752e10, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7f1f3effe188 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x559e25752e08) at scenegraph/qsgthreadedrenderloop.cpp:245 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x559e25752d90) at scenegraph/qsgthreadedrenderloop.cpp:709 #7 0x7f1f3effe5ba in QSGRenderThread::run (this=0x559e25752d90) at scenegraph/qsgthreadedrenderloop.cpp:738 #8 0x7f1f3b05d896 in QThreadPrivate::start (arg=0x559e25752d90) at thread/qthread_unix.cpp:367 #9 0x7f1f3a18896a in start_thread (arg=0x7f1e64e9b700) at pthread_create.c:463 #10 0x7f1f3a8e805f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f1e65e63700 (LWP 29584)): #0 0x7f1f3a18f8aa in futex_reltimed_wait_cancelable (private=, reltime=0x7f1e65e62bf0, expected=0, futex_word=0x559e2465eb70) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f1e65e62ca0, mutex=0x559e2465eb20, cond=0x559e2465eb48) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x559e2465eb48, mutex=0x559e2465eb20, abstime=0x7f1e65e62ca0) at pthread_cond_wait.c:667 #3 0x7f1f3b05df6e in QWaitConditionPrivate::wait_relative (time=3, this=0x559e2465eb20) at thread/qwaitcondition_unix.cpp:133 #4 QWaitConditionPrivate::wait (time=3, this=0x559e2465eb20) at thread/qwaitcondition_unix.cpp:141 #5 QWaitCondition::wait (this=this@entry=0x559e249d7db0, mutex=mutex@entry=0x559e24fae090, time=3) at thread/qwaitcondition_unix.cpp:215 #6 0x7f1f3b053dc9 in QThreadPoolThread::run (this=0x559e249d7da0) at thread/qthreadpool.cpp:146 #7
[Spectacle] [Bug 358641] Have Spectacle remember filename
https://bugs.kde.org/show_bug.cgi?id=358641 Emmanuel Revah changed: What|Removed |Added CC||bugrep...@manurevah.com --- Comment #9 from Emmanuel Revah --- I can only add that I've been sad (and lost trying out other programs) since Ksnapshot's easy file naming thing has left us. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396133] Global menu causes an empty window of qBittorrent
https://bugs.kde.org/show_bug.cgi?id=396133 --- Comment #8 from Nick Stefanov --- I tried KDE_NO_GLOBAL_MENU=1 qbittorrent but for me it doesn't help. The only solution for me is to use Breeze Look & Feel wich I don't like. I always use Oxygen Look & Feel theme. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396174] Cannot create new investment
https://bugs.kde.org/show_bug.cgi?id=396174 --- Comment #1 from Jack --- The wrong version number (5.0.0 displayed in 5.0.1) is a known issue. I've seen many cases of the details window being too small to see the details without manually making it larger. I don't know if this is really a KMyMoney issue or some underlying library, but someone will have to look to see if there is some parameter when creating/displaying that window that will help. It might be a regression when moving to Frameworks. As far as I can tell, creating a Stock (or Equite) account should be automatic and I can't think of any way it could possible be a parent account, especially at the time of creation. I have not yet tried to recreate this - your instructions look good, so I wonder if in the process of creating the second stock, something is not getting deselected and is being used as the parent of the new stock instead of using the main investment account. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396174] New: Cannot create new investment
https://bugs.kde.org/show_bug.cgi?id=396174 Bug ID: 396174 Summary: Cannot create new investment Product: kmymoney Version: 5.0.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: wolfg...@rohdewald.de Target Milestone: --- maybe this should be several bug reports. 1. Help/About says I have version 5.0.0, but the detail error message below seems to say I have 5.0.1 When creating a new investment, I get Unable to create all objects for the investment The second bug is that pressing the button "Details" does not show any details. They only get visible if I manually enlarge the window. It should enlarge itself automatically. The detailled error message says: Stock account cannot be parent account caugt in /build/kmymoney-8Tb1zm/kmymoney-5.0.1/kmymoney/mymoney/mymoneyfile.cpp:1059 So what exactly is a stock account? I cannot see this anywhere in the user interface, there it seems to be an Equity. So maybe the error message should be "Equity cannot be parent" - that would certainly have helped me to discover a workaround solution, see below. How to reproduce: 1. select the page "Investments" 2. select an account 3. now one of the equities has light blue as background 4. right mouse click BELOW the list of equities: Now I can add an equity, everything is fine. 5. now one of the equities has DARK blue as background 6. right click anywhere and create new equity. The above error appears. It seems that kmymoney tries to use a selected equity as parent for the new equity. I cannot imagine a situation in real life where this makes sense. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 396027] start fails due to "Config Error: Unable to open file /usr/local/bin/kf5-frameworks-build-include which was included from line 44"
https://bugs.kde.org/show_bug.cgi?id=396027 --- Comment #7 from krichter...@aol.de --- Thank you very much, the issue is fixed with the mentioned commit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 Nate Graham changed: What|Removed |Added Version Fixed In||5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 396027] start fails due to "Config Error: Unable to open file /usr/local/bin/kf5-frameworks-build-include which was included from line 44"
https://bugs.kde.org/show_bug.cgi?id=396027 Michael Pyne changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||18.08 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||src-build/3dbada64198c288ce ||34802ef75f82f19cf49dc42 --- Comment #6 from Michael Pyne --- Git commit 3dbada64198c288ce34802ef75f82f19cf49dc42 by Michael Pyne. Committed on 04/07/2018 at 20:20. Pushed by mpyne into branch 'master'. setup: Make the setup script work with cmake-installed kdesrc-build. This entails installing the sample rc files, and allowing kdesrc-build-setup to find the right path to those files. Note that to fix this bug you'd have to reinstall kdesrc-build and re-run kdesrc-build-setup. FIXED-IN:18.08 M +7-1CMakeLists.txt M +10 -0kdesrc-build-setup https://commits.kde.org/kdesrc-build/3dbada64198c288ce34802ef75f82f19cf49dc42 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 396027] start fails due to "Config Error: Unable to open file /usr/local/bin/kf5-frameworks-build-include which was included from line 44"
https://bugs.kde.org/show_bug.cgi?id=396027 Michael Pyne changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #5 from Michael Pyne --- So there's two problems then. 1) The kdesrc-build-setup script only works when running kdesrc-build directly from a git checkout (which is why the path is wrong here) 2) The files that the installed .kdesrc-buildrc refers to are not installed. Again this is an artifact of the assumption that kdesrc-build is used directly from a git checkout of kdesrc-build. I'll work on both of those. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396173] New: kwin_x11 --replace ignores other virtual desktops
https://bugs.kde.org/show_bug.cgi?id=396173 Bug ID: 396173 Summary: kwin_x11 --replace ignores other virtual desktops Product: kwin Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: magnus.gros...@gmail.com Target Milestone: --- I use KDE with `KDEWM=bspwm` for tiling. I also sometimes like to dynamically change between kwin and bspwm on runtime. What was great with KDE is that this worked flawlessly by just using `kwin_x11 --replace`. In KDE 5.12 it did at least, but there seems to be the following regression in KDE 5.13: When I switch from bspwm to kwin, only the windows on the current bspwm desktop are taken over, the others get lost (they are not accessible at all, don't appear in Latte Dock and they are not there when I switch the desktop in kwin). Expected Behavior: If I have 2 desktops in bspwm and switch to kwin, it should have the windows from bspwm-desktop #1 in kde-desktop #1 and the windows from bspwm-desktop #2 in kde-desktop #2, like it was in KDE 5.12. Actual Behavior: KDE just takes over the windows from the current bspwm desktop and discards the windows from all other desktops making them inaccessible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 Eike Hein changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/4ad27c62b5e71dc ||f143c5e5a96d9127de38c7d2d Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #29 from Eike Hein --- Git commit 4ad27c62b5e71dcf143c5e5a96d9127de38c7d2d by Eike Hein. Committed on 04/07/2018 at 19:41. Pushed by hein into branch 'Plasma/5.13'. Correct Folder View sizing and representation switch behavior Summary: * Resolve inherent layout hint conflicts between full and compact representations by setting them seperately. This fixes a recent regression causing tiny popups. * Correctly respect the panel icon size hint when scaling the compact representation, with the code and behavior now matching the Icon applet. * Only expand into the full representation in place on vertical panels. This is not a bugfix, and optional. But I think the expansion is useless on horizontal panels, and this means fewer users have to care about changing the panel icon size hint if they're using a really tall horizontal panel or Latte with parabolic zooming. Reviewers: mart, broulik, mvourlakos Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D13870 M +11 -0 containments/desktop/package/contents/ui/CompactRepresentation.qml M +29 -9containments/desktop/package/contents/ui/main.qml https://commits.kde.org/plasma-desktop/4ad27c62b5e71dcf143c5e5a96d9127de38c7d2d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396172] plasmashell crahed after entering search query in kde application menu
https://bugs.kde.org/show_bug.cgi?id=396172 --- Comment #1 from Alex --- Operating System: openSUSE Tumbleweed(updates for 2018-07-04) Plasmashell version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396172] New: plasmashell crahed after entering search query in kde application menu
https://bugs.kde.org/show_bug.cgi?id=396172 Bug ID: 396172 Summary: plasmashell crahed after entering search query in kde application menu Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: medic...@ukr.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 113768 --> https://bugs.kde.org/attachment.cgi?id=113768=edit crash backtrace Qt Version: 5.11.1 Frameworks Version: 5.47.0 Kernel: Linux 4.17.3-1-default x86_64 Steps to reproduce a bug: 1. Click menu 2. In search input enter first symbol of search query 3. Enter second symbol of search query If number of search results causes rendering a scrollbar after entering second symbol of search query(more than 14 apps on my 1920x1080 monitor), than plasmashell crashed. The crash can be reproduced every time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396133] Global menu causes an empty window of qBittorrent
https://bugs.kde.org/show_bug.cgi?id=396133 --- Comment #7 from Maksym --- Sorry, I made mistake, all this things are confusing me. I have tried Qt 5.11.1 with Plasma 5.12.4 (because Plasma 5.13.2 with Qt older than 5.11.1 doesn't work, I see the black screen at start up the system) and qBt had an empty window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396133] Global menu causes an empty window of qBittorrent
https://bugs.kde.org/show_bug.cgi?id=396133 --- Comment #6 from Maksym --- (In reply to Christoph Feck from comment #4) > Could be another victim of https://bugreports.qt.io/browse/QTBUG-69277 > > If possible, please test with Qt older than 5.11.1. Yes, it's because Qt 5.11.1 version. Today I have tried Plasma 5.13.2 with Qt 5.10.1 and qBt worked correctly. This bug can be closed, because it seems not to be related to plasmashell or global menu. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391253] a baloo_file process continue to run when X session is stopped
https://bugs.kde.org/show_bug.cgi?id=391253 milo...@o2.pl changed: What|Removed |Added CC||milo...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396171] New: CPU related brush performance issues on many mid to low-end mobile CPUs
https://bugs.kde.org/show_bug.cgi?id=396171 Bug ID: 396171 Summary: CPU related brush performance issues on many mid to low-end mobile CPUs Product: krita Version: 4.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: tyson...@mail.com Target Milestone: --- Recently I have been testing mid to low-end laptops and all-in-ones for using with Krita in budget-sensitive scenarios. These computers range roughly from $229 to $529. From these tests, I discovered that Krita’s brush system is very selective when it comes to mobile and SoC CPUs. There were huge CPU related slowdowns towards some particular hardware/software settings, while the the CPU can be rather strong but still performed poorly in some cases. ### TEST Fresh Windows 10 with latest drivers and patches installed (well, mostly). Manjaro KDE 17.1.11 Live USB (Linux 4.14) Krita 4.1.0 / A4 300 dpi 8 bit / Basic-5_size, Basic-6_detail, Air_brush_soft, Distort_move Stablizer OFF, Brush Smoothing: None / Basic When slowdown happened, test again with GPU acceleration OFF. Wacom Intuos S (Generation 3, CTL-4100) ### RESULT ### Keys that triggered slowdowns 1) Basic-6_detail brush preset (slow drawing, or fast drawing with dropped tablet signals) 2) Windows 10 + CPUs before Skylake (6th gen) 3) CPUs with poor single-thread performance ### Good CPUs (Windows and Linux): Celeron 3865U (4GB) / N4000 (4GB) / Core m3-6Y30 (4GB) / Core i3-3240 (4GB) / Core i5-7200U (8GB) / Core i5-8250U (8GB) ### Good CPUs (Linux only): Core i3-4010U (4GB) / Core i7-3520M (16GB) ### BAD: Intel Celeron N3150M (16GB) / N3450 (4GB) AMD A4-7220 (4GB) / A6-9210 (4GB) / A9-9420 (4GB) / A10-9600P (4GB) / A12-9700P (8GB) ### ANALYZE ### The Role of GPU Turning ON and OFF GPU acceleration have no effect to any slowdowns happened in this test. ### Basic-6_detail This particular preset can slow down lowend CPUs badly. I never changed its size during the tests. David Reevoy suspects: 0.02 spacing and precision to 5, plus Fan corner parameter being resource heavy. It needs at least Core m3-6Y30 to perform nicely. ### Core i7-3520M (Mobile) and Core i3-3240 (Desktop) They are the same 3rd Generation of Intel Core I family CPUs. Both have 2 cores and 4 threads. They support the same instructions. On spec, i7-3520M is better in every way, it has 1.3 times larger L3 cache and a 4 times larger GPU scale. There is only one exception: i3-3240 has a base clock of 3.40 Ghz, while i7-3520M has 2.90 Ghz. However, the latter can burst to 3.60 Ghz. On benchmark, Core i3-3240 has marginal better single thread performance (1810 vs 1782). Under Windows 10, the weaker Core i3-3240 handled Krita very well, while the supposedly stronger Core i7-3520M with 4 times larger RAM lagged badly. When it came to Linux, they both performed very well. In this case, I suspect Windows 10’s way of handling multi-thread CPU workload. I also suspect the effects from Intel’s Hyper-threading bug / Meltdown / Spectre patches. The Core i7-3520M resides in a Thinkpad X230T, it has Hyper-threading / Meltdown / Spectre patched in its BIOS. The Core i3-3240 resides in a budget all-in-one PC, it never received any related BIOS update. ### Core i3-4010U This CPU performed poorly under Windows, but performed rather well under Linux. Its Windows performance is slightly better than i7-3520M. It has no right to though, since it has a much lower clock speed (1.70 Ghz) and it has no burst capability. On benchmark, these CPUs’ single-thread ratings are: (i3-4010U:932 / i7-3520M:1782) In this case, I suspect Windows 10’s CPU driver was optimized towards 3rd gen and 4th gen Intel Core CPUs differently. ### Celeron 3865U and N4000 These two CPUs both have 2 cores and 2 threads, with a base clock of 1.10 Ghz. They have no hyper-threading or burst capabilities. They performed well under Windows in general. I didn’t test them under Linux but I expect them to do well too. When handling the brush preset “Basic-6_detail”, they could draw the line in a timely fashion. However, if the strokes were long and quick, big chunks of tablet signals were dropped, resulted in lines that similar to what happened on MacOSX in the past. ### Intel Celeron N3150M and N3450 These two CPUs both have 4 cores and 4 threads. N3150M has a base clock of 1.60Ghz and it can burst to 2.08Ghz. N3450 has a base clock of 1.10 Ghz and it can burst to 2.20 Ghz. They both suffered huge slowdowns under Windows and Linux. They have no rights to though, because compared to the fore-mentioned Celeron 3865U and N4000, they have 2 times more cores and 2 times faster clock. In this case, I suspect Krita’s single thread performance sensitivity. Although N3150M
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Martin Flöser changed: What|Removed |Added Resolution|--- |INVALID Status|REOPENED|RESOLVED --- Comment #3 from Martin Flöser --- That is outside the scope of KWin. Modes are reported by the drm subsystem. You need to check the capabilities the drm driver provides to add modes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396086] Changing elements order takes near 5 minutes in a folder with 50 images
https://bugs.kde.org/show_bug.cgi?id=396086 --- Comment #9 from Maik Qualmann --- I currently have no explanation why it takes so long. An album with 500 images is the time not measurable, the sorting is done immediately. A virtual album with 20,000 images in the view needs to sort by date about 1-2 seconds, sort by name about 5-6 seconds. And there are significantly more powerful computers than my double core... Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Mike Lothian changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- Ever confirmed|0 |1 --- Comment #2 from Mike Lothian --- Ignoring VMware, how does one specify a different mode on kwin_wayland? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 395988] KMainWindow saves invalid window/widget state under Qt 5.11.1
https://bugs.kde.org/show_bug.cgi?id=395988 --- Comment #13 from Max --- There's an update from Qt report... They don't think it's a Qt's bug. https://bugreports.qt.io/browse/QTBUG-69277?focusedCommentId=411008=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-411008 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396170] New: Gallery creation error
https://bugs.kde.org/show_bug.cgi?id=396170 Bug ID: 396170 Summary: Gallery creation error Product: digikam Version: 5.9.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: showfoto Assignee: digikam-bugs-n...@kde.org Reporter: deuch...@gmail.com Target Milestone: --- Generating a gallery in showfoto sometimes ends with the following error: "could not load xml file ''". Everything appears to be ok except there is no index.html file created. There *is* a gallery.xml file. I have created a lot of galleries successfully over the last couple of months and, after trying different photo selections I have come to the conclusion that this error only occurs when at least one of the images is from a screen grab! I am using PaintShopPro 8 for the screen grabs. Maybe I should try something else? - but I don't see why, it functions perfectly well with all other images! Please advise -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Martin Flöser --- We cannot workaround VMware issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396163] Opening steam doesn't align to the top left
https://bugs.kde.org/show_bug.cgi?id=396163 --- Comment #3 from Martin Flöser --- KWin does resize windows to fit. Looks like steam is ignoring that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396152] GTK4-demo's main window can only be moved by starting moving upwards
https://bugs.kde.org/show_bug.cgi?id=396152 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Martin Flöser --- Clearly a toolkit bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396169] New: Global menu doesn't work well with Virtualbox (Virtual machine menu Device->USB hides randomly)
https://bugs.kde.org/show_bug.cgi?id=396169 Bug ID: 396169 Summary: Global menu doesn't work well with Virtualbox (Virtual machine menu Device->USB hides randomly) Product: plasmashell Version: 5.12.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: metqua...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 113767 --> https://bugs.kde.org/attachment.cgi?id=113767=edit It should show a list of connected devices. And the area besides of the mouse still can click. Kubuntu 18.04, KDE 5.44, Plasma 5.12.5 Everything is fine, like Firefox, SystemSettings,... But VirtualBox 5.2.10, running virtual machine -> Devices -> USB -> (USB devices) is hide randomly. When it hide, I still can click the area where the submenu would show (if it works). VLC 3.0.2 'View' and Kate 17.12.3 'Bookmarks' menu doesn't show. Looks like Global Menu doesn't work with changing menu entry. Hope it get fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 396164] The "Audio Volume" applet sliders should not become transparent at zero point
https://bugs.kde.org/show_bug.cgi?id=396164 --- Comment #4 from uRohan --- (In reply to Kai Uwe Broulik from comment #3) > This means they're muted Interestingly... I've never met such behavior (moreover, we already have a "mute" status indicator in the form of an icon) **without any criticism**. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #28 from Jeff Smith --- Not allowing full view on a horizontal panel is a top notch fix. Thanks Eike. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396155] Reference images tool lacks features
https://bugs.kde.org/show_bug.cgi?id=396155 Quiralta changed: What|Removed |Added CC||rjquira...@gmail.com --- Comment #2 from Quiralta --- Just want to make a "cross reference" with the dialog in the phabricator and google+ as it was about the same requests. Like this we can keep the comments together and easier for the devs to check out. :) https://i.imgur.com/BgBQPC4.png https://plus.google.com/+DigiDirt/posts/WRmosFxeMxx -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 396018] Circular dependency after "Use platform detection from KWorkSpace in KCMShell" (896dd55)
https://bugs.kde.org/show_bug.cgi?id=396018 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395995] Notifications Messed up?
https://bugs.kde.org/show_bug.cgi?id=395995 --- Comment #9 from wolfyrion --- The other applications were Clementine - The music player every time I change a song it popups notifications the name of the song KDE Connect - it displays in KDE Notification whatever notification I received from my smartphone that includes - Emails , sms and other applications -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395995] Notifications Messed up?
https://bugs.kde.org/show_bug.cgi?id=395995 --- Comment #8 from wolfyrion --- [wolfyrion@WPC ~]$ dbus-send --session --print-reply --dest=org.freedesktop.DBus / \ > org.freedesktop.DBus.GetConnectionUnixProcessID > string:org.freedesktop.Notifications method return time=1530716152.757616 sender=org.freedesktop.DBus -> destination=:1.798 serial=3 reply_serial=2 uint32 9512 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389110] Being able to change gamma
https://bugs.kde.org/show_bug.cgi?id=389110 --- Comment #3 from Roman Gilg --- It's planned. The problem is that there are some patches hold by missing review already for quite some time, which I need to land first before I can continue working on the gamma stuff. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383174] google photo, export stops after a random quantity of photos
https://bugs.kde.org/show_bug.cgi?id=383174 --- Comment #4 from Thanh Trung Dinh --- Hi, I think it's a problem of Google API quota. I will find a way to work around. Thanh -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395995] Notifications Messed up?
https://bugs.kde.org/show_bug.cgi?id=395995 --- Comment #7 from Kai Uwe Broulik --- The popups shown in the last screenshot is not Plasma. Please check what process is owning notifications: dbus-send --session --print-reply --dest=org.freedesktop.DBus / \ org.freedesktop.DBus.GetConnectionUnixProcessID string:org.freedesktop.Notifications -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396161] Native X programs seem to be double zoomed on hidpi
https://bugs.kde.org/show_bug.cgi?id=396161 --- Comment #13 from Mike Lothian --- Am I safe to just delete the kdeglobals file? Are there any other configs you'd recommend getting rid of to start with a clean slate? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396168] New: Asistants ignore rescaling of image
https://bugs.kde.org/show_bug.cgi?id=396168 Bug ID: 396168 Summary: Asistants ignore rescaling of image Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Assistants are unaffected by rescaling the image, and so they will be incorrect after rescale. Steps to repo: 1; Create an image 2; Place assistants and specific points 3; Rescale image to 50% width and height. Actual behavior: Assistants retain their position relative to the original image size. Expected behavior: Assistants retain position and scale relative to the image's new dimensions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] New: Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Bug ID: 396167 Summary: Unable to specify a resolution to kwin_wayland Product: kwin Version: 5.13.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m...@fireburn.co.uk Target Milestone: --- I have a VMware VM running linux on one screen of a 3 screen Windows 7 machine Under X11, in order to get a full screen 1920x1080 screen I have to create an Xorg.conf: Section "Monitor" Identifier"Default Monitor" UseModes "Default Modes" Option"PreferredMode" "1920x1080@60" EndSection Section "Modes" Identifier"Default Modes" modeline "1920x1080@60" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync EndSection Section "Device" Identifier"Default Device" Driver"vmware" Option"IgnoreEDID" "1" EndSection Section "Screen" Identifier"Default Screen" Monitor "Default Monitor" Device"Default Device" EndSection Section "ServerLayout" Identifier"Default Layout" Screen"Default Screen" EndSection If I don't specify this then 1920x1080 is missing (the closest to this is then 1680x1050 or 1920x1440) If however I start a Wayland session there doesn't appear to be a way to force 1080p Is there a wayland equivalent of Xorg.0.log? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395995] Notifications Messed up?
https://bugs.kde.org/show_bug.cgi?id=395995 --- Comment #6 from wolfyrion --- Created attachment 113766 --> https://bugs.kde.org/attachment.cgi?id=113766=edit Better Screenshot for the notification bug using terminal command Better Screenshot for the notification bug using terminal command notify-send 'Hello world!' 'This is an example notification.' --icon=dialog-information -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 --- Comment #5 from Robert Laney --- Hi Julian, I "solved" the bug by re-installing completely mageia 6 distro including KDE. The problem disappeared so far. So, I can't redo a Valgrind log from this Dolphin crash. (I will do it if it occurs again :-( ) Sorry, BL Le 29/06/2018 à 21:34, Julian Schraner a écrit : > https://bugs.kde.org/show_bug.cgi?id=383942 > > Julian Schraner changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > CC||juliquad...@gmail.com > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #4 from Julian Schraner --- > First: Thanks for uploading the valgrind log! The version you were using to > originally report this bug is now severely outdated. Could you try to update > Dolphin and reproduce this crash again? If the bug does still occur, a new > valgrind log would be helpful as this would represent the current state of the > cod e better. Thanks! > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396161] Native X programs seem to be double zoomed on hidpi
https://bugs.kde.org/show_bug.cgi?id=396161 --- Comment #12 from David Edmundson --- If you set the scaling to 2 in the kscreen KCM on X and you can switch between two with minimal differences. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396166] New: Dolphin Crashing when loading program
https://bugs.kde.org/show_bug.cgi?id=396166 Bug ID: 396166 Summary: Dolphin Crashing when loading program Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: len...@cole.cc CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: Dolphin crashes when clicking on icon in toolbar, seems to do it 2-3 times before it will stay open. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2dfee1a6c0 (LWP 7420))] Thread 4 (Thread 0x7f2dd576a700 (LWP 7424)): #0 0x7f2df1631cd9 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2df15ec538 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2df88aa90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2df884f9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2df866e22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2df867316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2df375d6db in start_thread (arg=0x7f2dd576a700) at pthread_create.c:463 #7 0x7f2dfe6a388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2de559b700 (LWP 7423)): #0 0x7f2dfe6920b4 in __GI___libc_read (fd=7, buf=0x7f2de559ab60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f2df1630960 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2df15ebf27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2df15ec3e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2df15ec54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2df88aa90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2df884f9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2df866e22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2df8d27d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f2df867316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2df375d6db in start_thread (arg=0x7f2de559b700) at pthread_create.c:463 #11 0x7f2dfe6a388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2de7cd8700 (LWP 7422)): #0 0x7f2dfe696bf9 in __GI___poll (fds=0x7f2de7cd7ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2df0f2d747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2df0f2f36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2deaa852a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f2df867316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2df375d6db in start_thread (arg=0x7f2de7cd8700) at pthread_create.c:463 #6 0x7f2dfe6a388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2dfee1a6c0 (LWP 7420)): [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:371 #7 0x7f2df8676de0 in QByteArray::QByteArray(char const*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2df5fa6f20 in Baloo::DocumentDataDB::get(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #9 0x7f2df5fb85f1 in Baloo::Transaction::documentData(unsigned long long) const () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #10 0x7f2dfc91f0ee in Baloo::File::load() () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5 #11 0x7f2dfcee32e0 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5BalooWidgets.so.5 #12 0x7f2df8881122 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f2df985982c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f2df98610f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f2df88519a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f2df885411d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
[kwin] [Bug 396161] Native X programs seem to be double zoomed on hidpi
https://bugs.kde.org/show_bug.cgi?id=396161 --- Comment #11 from Mike Lothian --- I guess the point I'm trying to make is, with the same config, things should look the same under X11 & Wayland It should be possible to switch between the two without noticing -- You are receiving this mail because: You are watching all bug changes.
