[plasmashell] [Bug 408762] Kicker and Kick Off don't respect panel edge.
https://bugs.kde.org/show_bug.cgi?id=408762 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Friedrich W. H. Kossebau --- This bug is result of panels now (Plasma 5.16) having masks, and thus breaking the back introduced with https://phabricator.kde.org/R242:6aedda94b27a3ac60176dce960484af3f7787c07 For more details see https://phabricator.kde.org/T10889 (still needs someone to pick up and find/implement a solution satisfying both Plasma panels & Latte dock, will not be me) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408744] Inner Shadow layer style broken since 4.1.x
https://bugs.kde.org/show_bug.cgi?id=408744 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407567] i want to connect for the or KDE connect in my mobile to PC
https://bugs.kde.org/show_bug.cgi?id=407567 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 397302] KDE Partition manager crashing after upgrade
https://bugs.kde.org/show_bug.cgi?id=397302 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407532] the app doesn't draw in the same place as my cursor is pointing( about a quarter centemeter.
https://bugs.kde.org/show_bug.cgi?id=407532 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 374098] Replace the Maxima entry code with its LaTeX representation
https://bugs.kde.org/show_bug.cgi?id=374098 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407902] KMyMoney crashes in LEAP15.1
https://bugs.kde.org/show_bug.cgi?id=407902 --- Comment #16 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407621] I cant create a new canvas
https://bugs.kde.org/show_bug.cgi?id=407621 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 404825] the loudness wont adjust
https://bugs.kde.org/show_bug.cgi?id=404825 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407566] Dolphin crashes when opening a folder or a file
https://bugs.kde.org/show_bug.cgi?id=407566 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397952] kdenlive Automask crashed by clicking analyse button
https://bugs.kde.org/show_bug.cgi?id=397952 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407784] 3D Accelerated windows stop refreshing.
https://bugs.kde.org/show_bug.cgi?id=407784 --- Comment #15 from razangriff-ra...@tutanota.com --- Happens both ways. Although as mentioned earlier switching it on/off does refresh and unfreeze the windows, but doesn't prevent them from freezing again in either mode. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408766] New: Corrupted files downloading from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=408766 Bug ID: 408766 Summary: Corrupted files downloading from KDE Connect Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Copying files from Android to Linux results in corrupt files. The file size is identical but checksums do not match. STEPS TO REPRODUCE 1. Open KDE Connect in file browser eg. Dolphin 2. Copy file from Android to local file system OBSERVED RESULT File is copied and notification displays transfer is complete. File checksum does not match the source on Android. SOFTWARE Android/KDE Connect 1.12.9 Linux/kdeconnect 1.3.4 OS VERSIONS KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I have only observed this when copying from Android to Linux. Copying files from Linux to Android appears to work without any noticeable issues. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408765] filter>adjust,all items are out of order.they are not opened.
https://bugs.kde.org/show_bug.cgi?id=408765 tus...@vista.aero changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||tus...@vista.aero Status|REPORTED|NEEDSINFO --- Comment #1 from tus...@vista.aero --- Hi, I cannot reproduce this on master on Linux, and your description to the bug is not complete. Please add more information as required in the template. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408765] New: filter>adjust,all items are out of order.they are not opened.
https://bugs.kde.org/show_bug.cgi?id=408765 Bug ID: 408765 Summary: filter>adjust,all items are out of order.they are not opened. Product: krita Version: 4.2.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: okoi...@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 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #5 from Mike --- One more observation. I was able to reproduce the freeze reliably with 'wireshark'. I changed a few settings in 'systemsettings' and the error was gone. It never happened again. Then I restored my home directory from a backup - and the error was back: the freeze occurred every time I started 'wireshark'. It might well be that the error only occurs with certain system settings - or after you migrated from an older version of KDE Plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #4 from Mike --- Created attachment 120906 --> https://bugs.kde.org/attachment.cgi?id=120906=edit kwin_wayland gdb backtrace I was able to write a gdb backtrace. 1) I started Plasma, opened a konsole window and started 'wireshark' 2) The GUI froze 3) I connected from another machine via SSH 4) kwin_wayland was running with a load of 100% 5) I started GDB and attached to the kwin_wayland process 6) I created the backtrace -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408626] Please support pinyin (chinese) input natively
https://bugs.kde.org/show_bug.cgi?id=408626 --- Comment #10 from Christoph Feck --- > understand what kind of input system KDE is using To answer this question: KDE applications or Plasma doesn't have an input system. All input is handled in Qt, except for special input widgets such as Kate/KWrite. Qt itself gets input from either X11 or libinput, depending on what session type you use. The task Nate referenced doesn't propose any "native" KDE method either, because then it would only work with KDE applications. You really need a low-level (X)IM tool. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408051] With touch, always activate items on single-click
https://bugs.kde.org/show_bug.cgi?id=408051 --- Comment #3 from Christoph Feck --- The startDragDistance used to be configurable with 'kcmshell5 mouse'. Unfortunately the QML 'port' removed many options. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407784] 3D Accelerated windows stop refreshing.
https://bugs.kde.org/show_bug.cgi?id=407784 --- Comment #14 from Christoph Feck --- XRender still is compositing. Please test with disabled effects, you can toggle them with Shift+Alt+F12. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 --- Comment #39 from Christoph Feck --- *** Bug 408759 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 408759] ktorrent crashes when I delete a torrent while download is in progress
https://bugs.kde.org/show_bug.cgi?id=408759 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- Same cause as bug 383127: Accessing data of already deleted model. *** This bug has been marked as a duplicate of bug 383127 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 404045] line-h.png border issue
https://bugs.kde.org/show_bug.cgi?id=404045
ZBalling changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC||val.zapod...@gmail.com
Ever confirmed|0 |1
--- Comment #5 from ZBalling ---
Hello! I know how to solve a problem.
In /usr/share/themes/Breeze/gtk-2.0/widgets/menu (in my case, include
"widgets/menu" was in /usr/share/themes/Breeze/gtk-2.0/gtkrc)
style "separator_menu_item"
{
engine "pixmap"
{
image
{
function= BOX
file = "../assets/line-h.png"
border= { 1, 1, 1, 1 }
stretch = TRUE
}
}
}
Should be
border= { 0, 0, 0, 0 }
Than the problem vanishes. I use debian 10 Buster with breeze-gtk-theme
5.14.5-1
Also please open bug in debian.
https://packages.debian.org/buster/breeze-gtk-theme
Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
[amarok] [Bug 408764] New: Amarok - Context - Applets have incorrect background color
https://bugs.kde.org/show_bug.cgi?id=408764 Bug ID: 408764 Summary: Amarok - Context - Applets have incorrect background color Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Context View Assignee: amarok-bugs-d...@kde.org Reporter: jensen...@riseup.net Target Milestone: kf5 Created attachment 120905 --> https://bugs.kde.org/attachment.cgi?id=120905=edit shows the light-blue background color when using Breeze Dark theme SUMMARY In Amarok's "Context" window: all Applets get their background color from the wrong color setting in KDE Plasma. This is not an issue when using KDE's default light theme (Breeze), but when I switch to theme "Breeze Dark" theme (using System Settings > Colors), it becomes difficult to read the embedded Wikipedia pages. STEPS TO REPRODUCE 1. Configure KDE Plasma to use the "Breeze Dark" theme in System Settings > Colors. 2. Open Amarok 2.9.0 3. Look at Amarok's Context. OBSERVED RESULT I cannot read the Wikipedia page easily - links are almost impossible to read. EXPECTED RESULT I was expecting the Wikipedia page to be easily readable, even when using a dark operating system color scheme. ANALYSIS See attached image. All affected areas are cirled. These areas should not have a light-blue background color on the Breeze Dark theme. The reason the color is light-blue is because Amarok is filling these areas with the "Selection Background": This setting can be found here: KDE Plasma > System Settings > Colors > Edit Color Scheme > Colors > Common Colors > Selection Background "Selection Background" is probably not the right source for background colors. I think it makes more sense to get the color from the "View Background" or "Window Background" or "Button Background" or something that is intended to be used as a normal background color. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-21-generic OS Type: 64-bit Processors: 4 × AMD FX(tm)-4100 Quad-Core Processor Memory: 21.6 GiB of RAM (1600 MHz DDR3) ADDITIONAL INFORMATION Thanks for making such an awesome music player! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 408764] Amarok - Context - Applets have incorrect background color
https://bugs.kde.org/show_bug.cgi?id=408764 jensen...@riseup.net changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408471] DigiKam crashes after about 10 photos viewed, random images then fail to load
https://bugs.kde.org/show_bug.cgi?id=408471 --- Comment #2 from jasonl...@gmail.com --- Hi, I'm not sure what you meant by trace but I grabbed a snapshot of lines that seemed relevant around the point in time that the program crashed. [23480] C:\ [23480] BuildSupportList_On_Win8 [23480] Begin buildSupportList-- C:\\Temp\Win8_64\GeneStor.inf [23480] Open inf fail (error code : 3) [12156] digikam.dimg: "E:/LIBRARIES/IMAGES/My Photography/20171227_094825.jpg" : JPEG file identified [23480] bOpenDevList==FALSE [12156] digikam.general: Stacked View Mode : 1 [12156] digikam.dimg: "E:/LIBRARIES/IMAGES/My Photography/20171227_094242.jpg" : JPEG file identified [12156] digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC profile. [12156] digikam.dimg: "E:/LIBRARIES/IMAGES/My Photography/20171227_095652.jpg" : JPEG file identified [12156] digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC profile. [12156] digikam.dimg: Failed to allocate chunk of memory of size 12780288 std::bad_alloc [12156] digikam.general: Stacked View Mode : 1 [12156] digikam.general: Stacked View Mode : 1 [12156] digikam.dimg: "E:/LIBRARIES/IMAGES/My Photography/20171227_100122.jpg" : JPEG file identified [12156] digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC profile. [12156] digikam.general: Using 8 CPU core to run threads [12156] digikam.general: Action Thread run 1 new jobs [12156] digikam.general: One job is done [12156] digikam.general: Cancel Main Thread [12156] digikam.dimg: "E:/LIBRARIES/IMAGES/My Photography/20171227_100250.jpg" : JPEG file identified [12156] digikam.general: Stacked View Mode : 1 [12156] digikam.dimg: "E:/LIBRARIES/IMAGES/My Photography/20171227_101150.jpg" : JPEG file identified [12156] digikam.general: Stacked View Mode : 1 [12156] digikam.dimg: "E:/LIBRARIES/IMAGES/My Photography/20171227_100135.jpg" : JPEG file identified [12156] digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC profile. [12156] digikam.dimg: Failed to allocate chunk of memory of size 3195072 std::bad_alloc [12156] MGWHELP: C:\Program Files (x86)\digiKam\libwinpthread-1.dll - no dwarf symbols [12156] MGWHELP: C:\Program Files (x86)\digiKam\Qt5Core.dll - no dwarf symbols I'm seeing some errors around failing to allocate chunk of memory, and no dwarf symbols. Not sure what that means, but I'm running 40% CPU, 56% memory after DigiKam shut down. Hopefully you can assist, because it's not much use using a program that shuts down every 5 minutes or so. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 370263] Gpx files open but nothing is displayed
https://bugs.kde.org/show_bug.cgi?id=370263 --- Comment #20 from Fufu Fang --- (In reply to Stefan Bauer from comment #12) > (In reply to Olivier Carton from comment #11) > > Now that have realized that the track is indeed drawn, > > I think that there is another issue. > > > > In older version of Marble (1.9.2 for instance), loading a GPX file > > (directly in Marble or from Dolphin) makes Marble zoom in and change > > the focus so that the track uses most of the window and is really visible. > > > > In Marble 2.1.0, the focus is not changed and the view is still on > > the starting view of the globe. This has two effects. > > > >+ this lack of feedback from Marble lets the user think that the track > > has not been drawn. > >+ the user must know where the track is on earth because Marble does > > not zoom on it. This is even made more difficult by the fact that > > the track is barely visible. > > Yeah, there's an old feature request which relates to this. > > https://bugs.kde.org/show_bug.cgi?id=323673 > > Either this one should be reopened or a new bug should be filed. IMHO the > current issue should be focused on bringing back the old style of how the > GPX is drawn. I'll try if I could come up with a patch. It would be great if you could bring back the old style of the GPX was drawn. If not, it would be great if the GPX drawing style can be configured. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 370263] Gpx files open but nothing is displayed
https://bugs.kde.org/show_bug.cgi?id=370263 Fufu Fang changed: What|Removed |Added Target Milestone|--- |2.2 (KDE Applications ||17.04) CC||fangfufu2...@gmail.com Platform|Archlinux Packages |Debian testing --- Comment #19 from Fufu Fang --- (In reply to Stefan Bauer from comment #2) > Could you please check with a well-known GPX file that there is actually > nothing displayed? (I.e. load a GPX file with a known track and zoom close > the location of the track.) > > Tracks are currently drawn with a 1px wide white line which is easily > overlooked. I was considering to file a bug about that fact, maybe this one > is about the same issue. Yes, the track is currently drawn with 1px wide white line. Is there any ways to make the line thicker? I can't seem to change the drawing style. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406548] [Wayland] Kwin always hangs when I open kdenlive or it hangs randomly when I open other windows
https://bugs.kde.org/show_bug.cgi?id=406548 Mike changed: What|Removed |Added CC||b...@ubhofmann.de --- Comment #8 from Mike --- Could be the same as bug 408754 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #3 from Mike --- Could be the same as bug 406548 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408741] dropdown menu appears on wrong side when window opened fullscreen on second display
https://bugs.kde.org/show_bug.cgi?id=408741 --- Comment #3 from Victor Prudniy --- Also now found that this bug appears only for windows without titlebar -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408741] dropdown menu appears on wrong side when window opened fullscreen on second display
https://bugs.kde.org/show_bug.cgi?id=408741 --- Comment #2 from Victor Prudniy --- x11 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408763] New: Conflict of shortcuts: "Previous terminal" and "Next terminal"
https://bugs.kde.org/show_bug.cgi?id=408763 Bug ID: 408763 Summary: Conflict of shortcuts: "Previous terminal" and "Next terminal" Product: yakuake Version: 3.0.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: h...@kde.org Reporter: konto.s...@gmail.com Target Milestone: --- SUMMARY It seems like that the shortcuts "Next terminal" and "Previous terminal" are in conflict with each other. If both of the two shortcuts are set, only one of them could work. The other one will trigger a "Ambiguous shortcut detected" dialog box. STEPS TO REPRODUCE 1. Settings -> Configure Shortcuts 2. Set arbitrary shortcuts for "Previous terminal" and "Next terminal" 3. Use the previously defined shortcuts for previous/next terminal OBSERVED RESULT -> The shortcut for "Previous terminal" will trigger "Ambiguous shortcut detected" dialog box, even if it is not ambiguous at all and there is no conflict. EXPECTED RESULT -> Previous/Next terminal shortcuts should work if they are not ambiguous. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408762] New: Kicker and Kick Off don't respect panel edge.
https://bugs.kde.org/show_bug.cgi?id=408762 Bug ID: 408762 Summary: Kicker and Kick Off don't respect panel edge. Product: plasmashell Version: 5.16.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: trujill...@gmail.com Target Milestone: 1.0 Created attachment 120904 --> https://bugs.kde.org/attachment.cgi?id=120904=edit Screenshot of issue. Notice Menu. SUMMARY Applets with menus have their menu's extending past the edge of the panel. STEPS TO REPRODUCE 1. Set a regular PLasma panel. 2. Make the panel's height (if vertical) or width (if horizontal) less than 100% 3. Add kicker or Kick Off to panel placed on either edge. OBSERVED RESULT The menu window extends past the edge of the panel. Picture Attached. EXPECTED RESULT Menu should be aligned with edge of the panel. That was the behavior in 5.14 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 (available in About System) KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION First bug. Very Willing to help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408761] New: Undoing transformation steps no longer works though shortcuts
https://bugs.kde.org/show_bug.cgi?id=408761 Bug ID: 408761 Summary: Undoing transformation steps no longer works though shortcuts Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: somerandomperson1...@gmail.com Target Milestone: --- SUMMARY When using the transform tool, undoing action steps no longer work when using a keyboard or tablet shortcut. Before, I was able to warp the selection twice and undo 1 warp with the undo shortcut, but now the shortcut does nothing. Through the Edit menu and clicking Undo causes the desired effect, undoing 1 step. The shortcut works outside the transform tool, but not within. STEPS TO REPRODUCE 1. Make a selection 2. Click the transform tool or Ctrl+T (default) 3. Make a change to the selection 4. Use the undo shortcut, Ctrl+Z (default) OBSERVED RESULT The undo of the change doesn't revert EXPECTED RESULT The last transform action step would revert; move back to where it was, un-warp the warp, turn back the rotation, etc. SOFTWARE/OS VERSIONS Windows: 10 (x86_64) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION A windows update happened last night and may have something to do with it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 393238] Reduce shadow size/strength for background windows
https://bugs.kde.org/show_bug.cgi?id=393238 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 408760] New: Kate segfaults when Korean files are open with uim
https://bugs.kde.org/show_bug.cgi?id=408760 Bug ID: 408760 Summary: Kate segfaults when Korean files are open with uim Product: kate Version: 19.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: mycarr...@tutanota.com Target Milestone: --- Application: kate (19.04.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 5.1.9-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I'm moderately sure I was doing something else with Kate out of focus. 3 UTF-8 Korean files were open for some hours at the time. - Custom settings of the application: I was using uim/Byeoru input method. The crash can be reproduced sometimes. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1622b0a840 (LWP 4208))] Thread 2 (Thread 0x7f161bad7700 (LWP 4210)): #0 0x7f1627602c54 in read () from /usr/lib/libc.so.6 #1 0x7f16257d3961 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1625823f70 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f1625825766 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f16258258ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f1627b3c984 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1627ae64dc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f162792b239 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f1627db4ba6 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f162792c63c in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f1626317a92 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f1627611cd3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1622b0a840 (LWP 4208)): [KCrash Handler] #6 0x7f1627ae7744 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7f16226c3fbc in QUimPlatformInputContext::commitString(QString const&) () from /usr/lib/qt/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so #8 0x7f16226c4042 in QUimPlatformInputContext::commit_cb(void*, char const*) () from /usr/lib/qt/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so #9 0x7f16226a4a3d in ?? () from /usr/lib/libuim.so.8 #10 0x7f1620013807 in ?? () from /usr/lib/libuim-scm.so.0 #11 0x7f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0 #12 0x7f1620013b80 in ?? () from /usr/lib/libuim-scm.so.0 #13 0x7f1620013d07 in ?? () from /usr/lib/libuim-scm.so.0 #14 0x7f162001310e in ?? () from /usr/lib/libuim-scm.so.0 #15 0x7f1620013559 in ?? () from /usr/lib/libuim-scm.so.0 #16 0x7f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0 #17 0x7f1620013b80 in ?? () from /usr/lib/libuim-scm.so.0 #18 0x7f1620013807 in ?? () from /usr/lib/libuim-scm.so.0 #19 0x7f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0 #20 0x7f162001e963 in ?? () from /usr/lib/libuim-scm.so.0 #21 0x7f16200137ec in ?? () from /usr/lib/libuim-scm.so.0 #22 0x7f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0 #23 0x7f1620014094 in ?? () from /usr/lib/libuim-scm.so.0 #24 0x7f162000325d in GCROOTS_call_with_gc_ready_stack () from /usr/lib/libgcroots.so.0 #25 0x7f1620023644 in uim_scm_callf () from /usr/lib/libuim-scm.so.0 #26 0x7f16226a2d4b in uim_focus_out_context () from /usr/lib/libuim.so.8 #27 0x7f16226c22de in QUimPlatformInputContext::unsetFocus() () from /usr/lib/qt/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so #28 0x7f162802de28 in QGuiApplicationPrivate::_q_updateFocusObject(QObject*) () from /usr/lib/libQt5Gui.so.5 #29 0x7f16280339e8 in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () from /usr/lib/libQt5Gui.so.5 #30 0x7f1628038a4e in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #31 0x7f1628011d9c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #32 0x7f162257db8c in ?? () from /usr/lib/libQt5XcbQpa.so.5 #33 0x7f162582390f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #34 0x7f1625825869 in ?? () from /usr/lib/libglib-2.0.so.0 #35 0x7f16258258ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #36 0x7f1627b3c969 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #37 0x7f1627ae64dc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #38 0x7f1627aee596 in
[systemsettings] [Bug 408595] Some color items didn't change when apply new colorscheme.
https://bugs.kde.org/show_bug.cgi?id=408595 jo0ap7Se changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #4 from jo0ap7Se --- (In reply to Nate Graham from comment #3) > Where in Plasma? The Task Manager's colors, perhaps? I finally found that Kvantum cause this problem... Thanks for your reply. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 Luca Carlon changed: What|Removed |Added Summary|Hard to open apps clicking |Applications are not always |on the icons|opened when clicked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384532] Desktop toolbox button jumps around if placed in a corner
https://bugs.kde.org/show_bug.cgi?id=384532 J.Novo changed: What|Removed |Added CC||jgc.n...@gmail.com --- Comment #10 from J.Novo --- This is happening to me too. Mostly when placed just above the panel but sometimes (varies with the theme though) at top left corner. Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-51-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384143] HiPDI: freehand line in presentation mode is blocky
https://bugs.kde.org/show_bug.cgi?id=384143 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #2 from Mike --- > you run startx to get a wayland session? My fault. I'm sorry. I run a script 'startk' and its contents is export XDG_SESSION_TYPE=wayland export $(dbus-launch) && startplasmacompositor -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 408756] Install Amarok
https://bugs.kde.org/show_bug.cgi?id=408756 Antonio Rojas changed: What|Removed |Added Status|REPORTED|RESOLVED CC||aro...@archlinux.org Resolution|--- |DOWNSTREAM --- Comment #1 from Antonio Rojas --- Please report this to your distribution -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- >2. Start GUI (KDE Plasma) with 'startx' >5. GUI freezes, mouse disappears, top shows 100% CPU for /usr/bin/kwin_wayland you run startx to get a wayland session? -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 408759] New: ktorrent crashes when I delete a torrent while download is in progress
https://bugs.kde.org/show_bug.cgi?id=408759 Bug ID: 408759 Summary: ktorrent crashes when I delete a torrent while download is in progress Product: ktorrent Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: bugsefor...@gmx.com Target Milestone: --- STEPS TO REPRODUCE 1. add a torrent to ktorrent 2. while ktorrent downloads the newly added torrent, select it and press delete key (a dialog box shows up) 3. click "Delete data" button OBSERVED RESULT ktorrent crashes EXPECTED RESULT no crash SOFTWARE/OS VERSIONS ktorrent 5.1.1 Operating System: Arch Linux KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Thread 30 (Thread 0x7fffbd7fa700 (LWP 28680)): #0 0x759350d1 in poll () at /usr/lib/libc.so.6 #1 0x703b401c in () at /usr/lib/libresolv.so.2 #2 0x703b1a11 in __res_context_query () at /usr/lib/libresolv.so.2 #3 0x703b2059 in () at /usr/lib/libresolv.so.2 #4 0x703b264d in __res_context_search () at /usr/lib/libresolv.so.2 #5 0x7fffec011f5d in _nss_dns_gethostbyname4_r () at /usr/lib/libnss_dns.so.2 #6 0x759292c2 in gaih_inet.constprop () at /usr/lib/libc.so.6 #7 0x7592a2e8 in getaddrinfo () at /usr/lib/libc.so.6 #8 0x773610dc in QHostInfoAgent::fromName(QString const&) (hostName=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208 #9 0x7734f5d8 in QHostInfoRunnable::run() (this=0x58d93e70) at kernel/qhostinfo.cpp:689 #10 0x75dbdc91 in QThreadPoolThread::run() (this=0x557bd590) at thread/qthreadpool.cpp:99 #11 0x75dba63c in QThreadPrivate::start(void*) (arg=0x557bd590) at thread/qthread_unix.cpp:361 #12 0x7498da92 in start_thread () at /usr/lib/libpthread.so.0 #13 0x7593fcd3 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7fffdf7fe700 (LWP 28678)): #0 0x74993fa6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x75dc0899 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x557b0580, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 0x75dc0899 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557b0580) at thread/qwaitcondition_unix.cpp:144 #3 0x75dc0899 in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x557ba2b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x75dc09d8 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x557ba4f0, mutex=mutex@entry=0x557ba2b0, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x75dbdeab in QThreadPoolThread::run() (this=0x557ba4e0) at ../../include/QtCore/../../src/corelib/thread[m[m/qmutex.h:240 #6 0x75dba63c in QThreadPrivate::start(void*) (arg=0x557ba4e0) at thread/qthread_unix.cpp:361 #7 0x7498da92 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7593fcd3 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7fffd700 (LWP 28677)): #0 0x74993fa6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x75dc0899 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x56306b50, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 0x75dc0899 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x56306b50) at thread/qwaitcondition_unix.cpp:144 #3 0x75dc0899 in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x557ba2b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x75dc09d8 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x563068d0, mutex=mutex@entry=0x557ba2b0, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x75dbdeab in QThreadPoolThread::run() (this=0x563068c0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:240 #6 0x75dba63c in QThreadPrivate::start(void*) (arg=0x563068c0) at thread/qthread_unix.cpp:361 #7 0x7498da92 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7593fcd3 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7fffde7fc700 (LWP 28676)): #0 0x759350d1 in poll () at /usr/lib/libc.so.6 #1 0x703b401c in () at /usr/lib/libresolv.so.2 #2 0x703b1a11 in __res_context_query () at /usr/lib/libresolv.so.2 #3 0x703b2059 in () at /usr/lib/libresolv.so.2 #4 0x703b264d in __res_context_search () at /usr/lib/libresolv.so.2 #5 0x7fffec011f5d in _nss_dns_gethostbyname4_r () at /usr/lib/libnss_dns.so.2 #6 0x759292c2 in gaih_inet.constprop () at /usr/lib/libc.so.6 #7 0x7592a2e8 in getaddrinfo () at /usr/lib/libc.so.6 #8 0x773610dc in
[kate] [Bug 408302] GDB Plugin Not Working
https://bugs.kde.org/show_bug.cgi?id=408302 --- Comment #2 from Alberto Díaz López --- (In reply to Kåre Särs from comment #1) > Hi, > > Have you started the debugging? You have to start the application in the > debugger one time before you can start setting breakpoints. > > This is because starting the application/debugging loads the application > into GDB. Before that GDB is not even started. > > Setting of breakpoints before GDB is started is a bit of a problem. One > could start GDB and load the application when one tries to set a > break-point, but somebody would have to implement it... > > Please reply if my analysis/guess of the situation is right or wrong. I suppose your guess is right, yes. I didn't started the debugging yet. In fact, i'm searching how to start GDB debugging, but i can't find it. To test if that's the only reason or if there's more. Thank you for your quick and certain response. Bests ^^. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384143] HiPDI: freehand line in presentation mode is blocky
https://bugs.kde.org/show_bug.cgi?id=384143 --- Comment #1 from Oliver Sander --- Patch at https://phabricator.kde.org/D21836 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408753] No favourite blending modes by default
https://bugs.kde.org/show_bug.cgi?id=408753 --- Comment #2 from Tymond --- There were always (or, always as far as I remember) favourite blending modes. The list is compiled mostly of blending modes that are the most widely available (for example SAI had those, Medibang or other programs, see here: https://medibangpaint.com/en/use/2016/07/medibang-paint-blending-mode-tutorial/ or here: https://cms-assets.tutsplus.com/uploads/users/1152/posts/25089/image/basic-guide-layer-modes.jpg). Most art tutorials are using those, too. So I believe that was a way to make Krita less scary for newcomers. I, for example, never remember where "Normal" blending mode is located, so how beginners could not get lost in the list. Also for beginners right now it just looks like an empty category that exists for no reason... Hence I believe it is a mistake, a bug that comes from either Reptorian's (who was working on adding new blending modes) or Boud's (who is/was generally working on resources) work. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 --- Comment #11 from Egmont Koblinger --- Hi Kurt, Mariusz, > This is breaking > `clear` command, which replaces scrollback with current screen contents. You seem to have missed my latest comment (comment 8). As of ncurses 20180804, the "clear" command correctly clears the entire history in konsole, even without the just committed change. Therefore the claim that I quoted is no longer valid, and does not justify this change. The change makes konsole behave like xterm, which is not necessarily better in this case. For example, pressing Ctrl+L at the bash prompt now wipes out the last screenful of data, while the rest is still available in the scrollback. This behavior (i.e. xterm's behavior) makes little sense to me. In my firm opinion, Konsole's previous behavior (which differed from xterm's) of scrolling out those lines made much more sense: the scrollback buffer contained meaningful data even after a Ctrl+L at the shell prompt. If you really wish to go for this new behavior and be fully compatible with xterm, I'm not trying to stop you. But I'm kindly asking you to test the old and new behavior and evaluate the differences against a new ncurses which fixed clear's behavior, and make your choice based on this, rather than based on an old ncurses as you apparently did. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 408758] memcheck internal error: Signal 10 (SIGBUS)
https://bugs.kde.org/show_bug.cgi?id=408758 --- Comment #1 from John Ralls --- The command line for the crashed session was: valgrind --log-file=gramps-memory --suppressions=$HOME/Development/gtk-sources/valgrind-3.15.0/darwin15.supp --suppressions=/Users/john/Development/Gramps-Build/gramps-stable-git-Mavericks/src/Python-3.6.8/Misc/valgrind-python.supp --main-stacksize=67108864 $PREFIX/bin/python $PREFIX/bin/gramps The elevated --main-stacksize was necessary to avoid an earlier crash; in that case valgrind mentioned the stack size (8MB) and suggested increasing it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408749] Krita crashes when drawing on the canvas while animation is playing and no frames are added
https://bugs.kde.org/show_bug.cgi?id=408749 jpl.ll...@gmail.com changed: What|Removed |Added Platform|MS Windows |Appimage CC||jpl.ll...@gmail.com OS|MS Windows |Linux --- Comment #1 from jpl.ll...@gmail.com --- I can confirm this for the 4.2.1 AppImage file running on Ubuntu 16.04. The bug goes as far back as at least 4.1.1, but is not present on 3.3.1. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 408758] New: memcheck internal error: Signal 10 (SIGBUS)
https://bugs.kde.org/show_bug.cgi?id=408758 Bug ID: 408758 Summary: memcheck internal error: Signal 10 (SIGBUS) Product: valgrind Version: 3.14.0 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: jra...@ceridwen.us Target Milestone: --- Created attachment 120903 --> https://bugs.kde.org/attachment.cgi?id=120903=edit Session transcript of crashed memcheck session MacOS 10.11.6 with the 2019 security updates, Apple LLVM version 7.3.0 (clang-703.0.31), running in a VMWare Fusion 8.5.10 VM provisioned with 4 cores and 8GB of memory on a late 2013 MacPro running MacOS 10.14. Valgrind was built from the 3.14.0 source tarball and configured with --with-64bitonly. The program under test was Gramps (https://github.com/gramps-project/gramps) running in a gtk-osx (https://gitlab.gnome.org/GNOME/gtk-osx) build environment with recent HEADS of glib (https://gitlab.gnome.org/GNOME/glib) and gtk-3-24 (https://gitlab.gnome.org/GNOME/gtk). Gramps is a Python program, and Python was version 3.6.8 built in the same environment. Python, glib, gtk, and most dependencies were built with -O0 -g. All of the session output is in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 Kurt Hindenburg changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||konsole/commit/7a1116ccff5d ||a88f6ef7e0c4d50ae979b09fed8 ||f Resolution|--- |FIXED --- Comment #9 from Kurt Hindenburg --- Git commit 7a1116ccff5da88f6ef7e0c4d50ae979b09fed8f by Kurt Hindenburg, on behalf of Mariusz Glebocki. Committed on 15/06/2019 at 21:03. Pushed by hindenburg into branch 'master'. CSI 2J: Do not append current screen to history Summary: This behavior is present in e.g. xterm and linux console. Currently when using CSI 2J escape sequence, screen contents are appended to scrollback (including bottom empty lines). This is breaking `clear` command, which replaces scrollback with current screen contents. Test Plan: * Start Konsole with a shell * `clear` **Expected result:** Cleared display, empty scrollback. **Actual result:** Cleared display, but scrollback contains previous display contents. --- * Start Konsole with a shell * seq 1000 * `echo -ne '\033[2J` **Expected result:** Cleared display, numbers in last scrollback lines. **Actual result:** Cleared display, but scrollback contains previous display contents (i.e. shell prompt in last lines) Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: hindenburg, konsole-devel, #konsole Tags: #konsole Differential Revision: https://phabricator.kde.org/D21282 M +0-6src/Screen.cpp https://invent.kde.org/kde/konsole/commit/7a1116ccff5da88f6ef7e0c4d50ae979b09fed8f -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon |konsole/commit/7a1116ccff5d |sole/7a1116ccff5da88f6ef7e0 |a88f6ef7e0c4d50ae979b09fed8 |c4d50ae979b09fed8f |f | --- Comment #10 from Kurt Hindenburg --- Git commit 7a1116ccff5da88f6ef7e0c4d50ae979b09fed8f by Kurt Hindenburg, on behalf of Mariusz Glebocki. Committed on 15/06/2019 at 21:03. Pushed by scmsync into branch 'master'. CSI 2J: Do not append current screen to history Summary: This behavior is present in e.g. xterm and linux console. Currently when using CSI 2J escape sequence, screen contents are appended to scrollback (including bottom empty lines). This is breaking `clear` command, which replaces scrollback with current screen contents. Test Plan: * Start Konsole with a shell * `clear` **Expected result:** Cleared display, empty scrollback. **Actual result:** Cleared display, but scrollback contains previous display contents. --- * Start Konsole with a shell * seq 1000 * `echo -ne '\033[2J` **Expected result:** Cleared display, numbers in last scrollback lines. **Actual result:** Cleared display, but scrollback contains previous display contents (i.e. shell prompt in last lines) Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: hindenburg, konsole-devel, #konsole Tags: #konsole Differential Revision: https://phabricator.kde.org/D21282 M +0-6src/Screen.cpp https://commits.kde.org/konsole/7a1116ccff5da88f6ef7e0c4d50ae979b09fed8f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408744] Inner Shadow layer style broken since 4.1.x
https://bugs.kde.org/show_bug.cgi?id=408744 --- Comment #6 from Ahab Greybeard --- Your latest attachment shows the Blending Options parameters which haven't been implemented yet. You need to click on the name "Inner Shadow" so that it is highlighted, as in my attached screenshot. Ticking the box applies the layer effect. Clicking the name selects the parameters for display and adjustment. I suspect that the 4.1.x default parameters for that layer effect are different from the current ones and that may be why you feel the effect is 'wrong'. Again, what do you expect to see? What did 4.1.x do that was acceptable to you? You need to try adjusting the Inner Shadow layer effect parameters. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408757] New: Display settings crashed
https://bugs.kde.org/show_bug.cgi?id=408757 Bug ID: 408757 Summary: Display settings crashed Product: systemsettings Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dj_ha...@yahoo.de Target Milestone: --- Application: systemsettings5 (5.16.80) Qt Version: 5.12.2 Frameworks Version: 5.60.0 Operating System: Linux 5.0.0-16-generic x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: Open the settings dialog and going to the display settings to change to a higher DPI for my 4k Display but it doesn't open. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6021ec06c0 (LWP 1416))] Thread 28 (Thread 0x7f5fad8c4700 (LWP 1713)): #0 0x7f60264d3729 in __GI___poll (fds=0x7f5f98004e30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f602422fcb6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f602422fddc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6026a55063 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6026a005bb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f602684b2c6 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6025b6bef5 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f602684c612 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6024cc7182 in start_thread (arg=) at pthread_create.c:486 #9 0x7f60264dfb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f5fae5fc700 (LWP 1497)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e295a577dc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e295a57788, cond=0x55e295a577b0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e295a577b0, mutex=0x55e295a57788) at pthread_cond_wait.c:655 #3 0x7f601ccf8bab in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f601ccf8917 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f6024cc7182 in start_thread (arg=) at pthread_create.c:486 #6 0x7f60264dfb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f5faedfd700 (LWP 1496)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e295812968) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e295812918, cond=0x55e295812940) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e295812940, mutex=0x55e295812918) at pthread_cond_wait.c:655 #3 0x7f601ccf8bab in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f601ccf8917 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f6024cc7182 in start_thread (arg=) at pthread_create.c:486 #6 0x7f60264dfb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f5faf7fe700 (LWP 1495)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e29537feec) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e29537fe98, cond=0x55e29537fec0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e29537fec0, mutex=0x55e29537fe98) at pthread_cond_wait.c:655 #3 0x7f601ccf8bab in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f601ccf8917 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f6024cc7182 in start_thread (arg=) at pthread_create.c:486 #6 0x7f60264dfb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f5fa700 (LWP 1494)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e2952a9a18) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e2952a99c8, cond=0x55e2952a99f0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e2952a99f0, mutex=0x55e2952a99c8) at pthread_cond_wait.c:655 #3 0x7f601ccf8bab in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f601ccf8917 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f6024cc7182 in start_thread (arg=) at pthread_create.c:486 #6 0x7f60264dfb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f5fb68cf700 (LWP 1493)): #0 0x7f60264d3729 in __GI___poll (fds=0x7f5fa8004e30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1
[okular] [Bug 407998] Okular scales down pages when printing
https://bugs.kde.org/show_bug.cgi?id=407998 --- Comment #12 from Nate Graham --- Ah perfect, I forgot that it was already committed! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408731] Krita crashes on showing welcome screen if a special tiff file is in Rec. Docs
https://bugs.kde.org/show_bug.cgi?id=408731 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Ahab Greybeard --- I can confirm this for the latest current nightly krita-4.3.0-prealpha-bebb0d6-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 408756] New: Install Amarok
https://bugs.kde.org/show_bug.cgi?id=408756 Bug ID: 408756 Summary: Install Amarok Product: amarok Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: develo...@flexsis.net Target Milestone: kf5 Created attachment 120902 --> https://bugs.kde.org/attachment.cgi?id=120902=edit Info report bug SUMMARY I don't install STEPS TO REPRODUCE 1. sudo apt-get install amarok OBSERVED RESULT alexandre@Dell-Inspiron-3542:~$ sudo apt-get install amarok [sudo] senha para alexandre: Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto O pacote amarok não está disponível, mas é referenciado por outro pacote. Isto pode significar que o pacote está faltando, ficou obsoleto ou está disponível somente a partir de outra fonte E: O pacote 'amarok' não tem candidato para instalação -- PS: Text above in portuguese language. == EXPECTED RESULT Install the Amarok SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.04 / KDE Plasma 5.16.0 (available in About System) KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION kernel: 5.1.0-050100-generic S.O. 64 bits -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408744] Inner Shadow layer style broken since 4.1.x
https://bugs.kde.org/show_bug.cgi?id=408744 --- Comment #5 from gabrielborgesbonifa...@gmail.com --- (In reply to Ahab Greybeard from comment #3) > I forgot to add a comment: What are the parameters you've used for your > Inner Shadow and what did you expect to see? https://bugs.kde.org/attachment.cgi?id=120901 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408755] New: Cannot save multiple layers with different colorspaces to tiff
https://bugs.kde.org/show_bug.cgi?id=408755 Bug ID: 408755 Summary: Cannot save multiple layers with different colorspaces to tiff Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- Created attachment 120900 --> https://bugs.kde.org/attachment.cgi?id=120900=edit Test .kra file SUMMARY Multiple layers in tiff seem to work... if all the layers are of the same colorspace or if all the layers are of supported colorspaces (I don't know which one is the case). Otherwise the content is skewed or missing or lost and all the layers have the same colorspace. STEPS TO REPRODUCE 1. Open the attached file. 2. Save as tiff (don't flatten, yes, save ICC profile). 3. Open the file in another tab. 4. Convert the bottom layer colorspace to the same as the top one (XYZ, but I don't remember the bit depth). 5. Save as tiff (the same options). 6. Compare the results with .kra and with the tiff file saved previously. OBSERVED RESULT File saved in 2. looks differently; doesn't have the pink stroke. EXPECTED RESULT All files look at least similar to each other, no content is missing. (The tiff file saved in 5. is different from .kra, but that's because of the colorspace conversion; you'll see the same results if you convert the image colorspace in .kra file to the colorspace tiff exporter converted to). SOFTWARE/OS VERSIONS Linux Mint Qt Version: 5.12.3 ADDITIONAL INFORMATION Using Krita git master 0893c1a784 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408744] Inner Shadow layer style broken since 4.1.x
https://bugs.kde.org/show_bug.cgi?id=408744 --- Comment #4 from gabrielborgesbonifa...@gmail.com --- Created attachment 120901 --> https://bugs.kde.org/attachment.cgi?id=120901=edit My Inner Shadows parameters -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408753] No favourite blending modes by default
https://bugs.kde.org/show_bug.cgi?id=408753 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- The list of favourite blending modes is populated by you selecting blending modes from other categories and clicking the small box to the left of the mode name, to add (or remove) that blending mode to (from) the favourites list. 4.1.7 did have initial entries in the favourites category but that always seemed strange to me, because how could krita know what my favourite blending modes are? I assume that someone had decided that they were the 'most common and useful' blending modes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 Mike changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] New: kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 Bug ID: 408754 Summary: kwin-5.16.0: GUI (Wayland) freezes Product: kwin Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: b...@ubhofmann.de Target Milestone: --- I use KDE plasma in Wayland mode (kwin is the Wayland compositor) on Gentoo Linux. Last week I updated to: - kde-plasma 5.16.0 - kde-frameworks 5.59.0 - kde-apps 19.04.2 After that, my screen randomly froze once or twice a day. Today I found out that I can trigger a freeze by starting Wireshark-3.0.2 from konsole: GUI freezes, mouse disappears, top shows 100% CPU for /usr/bin/kwin_wayland, Alt-Ctrl-Fn or Ctrl-BS don't work. I downgraded kde-plasma/kwin to 5.15.5 (only this package). I haven't had any freezes since then and I can start Wireshark-3.0.2 without problems. Reproducible: Always Steps to Reproduce: 1. Login as ordinary user on Linux TTY console 2. Start GUI (KDE Plasma) with 'startx' 3. open a konsole terminal 4. enter 'wireshark' 5. GUI freezes, mouse disappears, top shows 100% CPU for /usr/bin/kwin_wayland SOFTWARE/OS VERSIONS - Gentoo Linux: default/linux/amd64/17.1/no-multilib - Linux Kernel: 4.19.50 - GCC: 8.3.0 - KDE Plasma Version: 5.16.0 - KDE Frameworks Version: 5.59.0 - KDE Apps: 19.04.2 - Qt Version: 5.12.3 ADDITIONAL INFORMATION I also filed a bug at: https://bugs.gentoo.org/688128 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408753] New: No favourite blending modes by default
https://bugs.kde.org/show_bug.cgi?id=408753 Bug ID: 408753 Summary: No favourite blending modes by default Product: krita Version: 4.2.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- SUMMARY If you reset the configuration, there is no favourite blending modes. STEPS TO REPRODUCE 1. Reset the configuration. 2. Open Krita 4.2.1. 3. Try to assign a different blending mode. OBSERVED RESULT Favourite blending modes are empty. EXPECTED RESULT There should be a list of favourite blending modes just like before. SOFTWARE/OS VERSIONS Qt Version: 5.12.3 Linux Mint ADDITIONAL INFORMATION I'm using appimage. In 4.1.7, there is a list of favourite blending modes available. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 --- Comment #7 from Konstantin Kharlamov --- (In reply to Martin Flöser from comment #6) > What's your screen resolution? $ xrandr -q Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1366x768 60.07*+ 1280x720 59.97 1152x768 59.95 1024x768 59.95 800x600 59.96 848x480 59.94 720x480 59.94 640x480 59.94 HDMI-0 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 408736] Message Window no longer shows URL of link.
https://bugs.kde.org/show_bug.cgi?id=408736 lnx...@westlot.net changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from lnx...@westlot.net --- (In reply to Laurent Montel from comment #5) > (In reply to lnxusr from comment #4) > > Created attachment 120893 [details] > > Kontact Mail Window > > > > There is no status bar on the email window. Is this perhaps the problem? > > Is there a new setting somewhere that defaulted to there not being a status > > bar in the email window? > > > > Here's a screenshot of the window over the Kontact window, you can see the > > status bar of the main Kontact window just under the email window. > > Yep it's the problem. > I don't implemented "hide/show statusbar" perhaps an old settings > Try to look at in ~/.config/kmail2rc or kontactrc > > "ShowStatusBar=false" > > Perhaps it's the problem. That fixed it. kmail2rc has a [Separate Reader Window] section with StatusBar. It was set to Disabled so I changed it to Enabled and now have the URL back in the window. Thank you Laurent, much appreciated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 --- Comment #6 from Martin Flöser --- What's your screen resolution? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408674] Plasma 5.16 causing graphical glitches and corruptions with Kvantum themes that use blur
https://bugs.kde.org/show_bug.cgi?id=408674 --- Comment #8 from duncanyo...@gmail.com --- Created attachment 120899 --> https://bugs.kde.org/attachment.cgi?id=120899=edit Blur Noise Levels Maybe my issue should be split from this one. As I have no tearing or slow down to speak of. The only issue I have is the broken noise. Level 2 looks exactly like level 1, but it's brighter. There is no noise on level 1 or 2, on level 3 there is noise but it doesn't look correct. If the background is light it looks fine. But when the background is dark, it looks very noisy and stands out a lot. I also noticed that the corners of the windows do not always appear rounded like they should. I have attached an image that should clearly show what I am talking about. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 408752] New: Comma separator in stored constant returns nan
https://bugs.kde.org/show_bug.cgi?id=408752 Bug ID: 408752 Summary: Comma separator in stored constant returns nan Product: kcalc Version: 18.12 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: danretire...@gmail.com Target Milestone: --- SUMMARY Comma separator in stored constant returns nan STEPS TO REPRODUCE 1. In Settings select Science Mode 2. In Settings turn on Constants Buttons 3. With a number greater than one thousand in the display field (with comma separators) select the Shift button. The C1-C6 buttons will all change to Store 4. Select one of the Store buttons 5. Clear the display with AC button 6. Hover over the button the number was stored in (C1-C6). The stored number should be displayed as a tool tip 7. Select the button the number was stored in OBSERVED RESULT The display field shows nan EXPECTED RESULT The stored number SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION In Settings if you select Configure Kcalc... you can edit the entry to remove the commas and it will work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408751] Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=
https://bugs.kde.org/show_bug.cgi?id=408751 annu...@yahoo.com changed: What|Removed |Added CC||annu...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408751] New: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=
https://bugs.kde.org/show_bug.cgi?id=408751 Bug ID: 408751 Summary: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55fdbb5a1904) at ../sysdeps/unix/sysv/linux/f Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: annu...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 [Current thread is 1 (Thread 0x7ff6a04e8880 (LWP 2552))] Thread 12 (Thread 0x7ff66ef40700 (LWP 5904)): #0 0x7ff6a37cf3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55fdbcf3f010) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff6a37cf3bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55fdbcf3efc0, cond=0x55fdbcf3efe8) at pthread_cond_wait.c:502 #2 0x7ff6a37cf3bb in __pthread_cond_wait (cond=0x55fdbcf3efe8, mutex=0x55fdbcf3efc0) at pthread_cond_wait.c:655 #3 0x7ff6a490a733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff6a490a819 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff6a66485d9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7ff6a664883a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff6a4904612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff6a37c9182 in start_thread (arg=) at pthread_create.c:486 #9 0x7ff6a4597b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7ff66cdd7700 (LWP 4914)): [KCrash Handler] #6 0x7ff68c146a47 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so #7 0x7ff6a4ae3563 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff6a669c150 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff6a6644c14 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7ff6a66487f8 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7ff6a4904612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff6a37c9182 in start_thread (arg=) at pthread_create.c:486 #13 0x7ff6a4597b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7ff657fff700 (LWP 4552)): #0 0x7ff6a37cf3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55fdbc4d25e4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff6a37cf3bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55fdbc4d2590, cond=0x55fdbc4d25b8) at pthread_cond_wait.c:502 #2 0x7ff6a37cf3bb in __pthread_cond_wait (cond=0x55fdbc4d25b8, mutex=0x55fdbc4d2590) at pthread_cond_wait.c:655 #3 0x7ff6a490a733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff6a490a819 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff6a66485d9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7ff6a664883a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff6a4904612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff6a37c9182 in start_thread (arg=) at pthread_create.c:486 #9 0x7ff6a4597b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7ff66dd4b700 (LWP 3042)): #0 0x7ff6a457b867 in sched_yield () at ../sysdeps/unix/syscall-template.S:78 #1 0x7ff68faeb44b in () at /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #2 0x7ff68ea7c9f9 in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #3 0x7ff68e9927ee in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #4 0x7ff68fae5324 in () at /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #5 0x7ff69c0be196 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #6 0x7ff6a4ecd48b in QOpenGLContext::swapBuffers(QSurface*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7ff6a6644c56 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff6a66487f8 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff6a4904612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff6a37c9182 in start_thread (arg=) at pthread_create.c:486 #11 0x7ff6a4597b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7ff66700 (LWP 2936)): #0 0x7ff6a4586fb4 in __GI___libc_read (nbytes=16, buf=0x7ff66fffeac0, fd=49) at ../sysdeps/unix/sysv/linux/read.c:26 #1
[yakuake] [Bug 407726] Button icons blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=407726 kmi changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #6 from kmi --- Not a dupe. The other bug is about the title bar buttons (those have been fixed). This is about OK/Cancel buttons in preferences. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407998] Okular scales down pages when printing
https://bugs.kde.org/show_bug.cgi?id=407998 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #11 from Michael Weghorn --- (In reply to Nate Graham from comment #10) > (In reply to Sergio from comment #9) > > I have finally managed installing a recent version of okular (1.7.2). The > > operation of the scaling menu is a bit unclear to me, though. > > > > 1. It is presented as a PDF option, but okular supports many more formats. > > For instance, the option is absent for tiff, which is a nice multipage > > format for things like BW document scans with Group4 compression (even if > > those can certainly be embedded in PDF). Similarly, the option is absent for > > PNG, etc. > It's being implemented for other file formats too. I can't find the patch > right now but I know it's in progress! This is https://phabricator.kde.org/D10974 and I quickly verified that current development version of Okular actually offers either "Fit to printable area" or "Fit to full page" when opening a TIFF file. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 328937] Shortcuts for move tab
https://bugs.kde.org/show_bug.cgi?id=328937 Davide Gianforte changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kru ||sader/ca00347a865e34c37bd48 ||a4c8c99fe885ad42c5c Status|CONFIRMED |RESOLVED --- Comment #2 from Davide Gianforte --- Git commit ca00347a865e34c37bd48a4c8c99fe885ad42c5c by Davide Gianforte. Committed on 15/06/2019 at 19:29. Pushed by gengisdave into branch 'master'. Shortcuts to move tab This adds two new actions to tab popup (with relative hardcoded shortcuts) to move the current tab to the left or right. You can't move the first tab to the left or the last one to the right. FIXED: [ 328937 ] Shortcuts for move tab M +18 -0krusader/panelmanager.cpp M +2-0krusader/panelmanager.h M +2-0krusader/paneltabbar.cpp M +14 -0krusader/tabactions.cpp M +3-0krusader/tabactions.h https://commits.kde.org/krusader/ca00347a865e34c37bd48a4c8c99fe885ad42c5c -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408647] The tool to change the speed of the project folder does not work well
https://bugs.kde.org/show_bug.cgi?id=408647 --- Comment #2 from RafaMar --- (In reply to emohr from comment #1) > Created attachment 120887 [details] > speed-job_18-12_19-04 > > Do you mean: clip job -> duplicate clip with speed change? The tool of version 18.12 never gave me problems, towards bin their work, I do not see any improvement in the new tool. I tested with a value of 50% in version 19.04 and it does not work, it creates the new clip but it does not change the speed. It only serves to accelerate. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 408736] Message Window no longer shows URL of link.
https://bugs.kde.org/show_bug.cgi?id=408736 --- Comment #5 from Laurent Montel --- (In reply to lnxusr from comment #4) > Created attachment 120893 [details] > Kontact Mail Window > > There is no status bar on the email window. Is this perhaps the problem? > Is there a new setting somewhere that defaulted to there not being a status > bar in the email window? > > Here's a screenshot of the window over the Kontact window, you can see the > status bar of the main Kontact window just under the email window. Yep it's the problem. I don't implemented "hide/show statusbar" perhaps an old settings Try to look at in ~/.config/kmail2rc or kontactrc "ShowStatusBar=false" Perhaps it's the problem. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 408699] Partition info is barely readable or completely unreadable with breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=408699 --- Comment #1 from Andrius Štikonas --- Any suggestions? I can try to set the text to be black but that's probably against the idea of dark theme... By the way you can always change file system colours in KPM settings, to make it more readable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408744] Inner Shadow layer style broken since 4.1.x
https://bugs.kde.org/show_bug.cgi?id=408744 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Summary|An bug found since v4.1.X |Inner Shadow layer style ||broken since 4.1.x -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408177] Assert saving lab to tiff. [GDB backtrace]
https://bugs.kde.org/show_bug.cgi?id=408177 --- Comment #7 from Tymond --- Git commit 0893c1a78427403164ec29c5c86a46869f57d057 by Agata Cacko. Committed on 15/06/2019 at 16:50. Pushed by tymond into branch 'master'. Add conversion of colorspace to tiff export Not every colorspace supported by Krita is supported by tiff. In case of exporting an image with an unsupported color space it should convert to the closest one. This commit ensures that. M +8-0plugins/impex/tiff/kis_tiff_converter.cc M +65 -21 plugins/impex/tiff/kis_tiff_writer_visitor.cpp https://invent.kde.org/kde/krita/commit/0893c1a78427403164ec29c5c86a46869f57d057 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408744] An bug found since v4.1.X
https://bugs.kde.org/show_bug.cgi?id=408744 --- Comment #3 from Ahab Greybeard --- I forgot to add a comment: What are the parameters you've used for your Inner Shadow and what did you expect to see? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408744] An bug found since v4.1.X
https://bugs.kde.org/show_bug.cgi?id=408744 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #2 from Ahab Greybeard --- Created attachment 120898 --> https://bugs.kde.org/attachment.cgi?id=120898=edit Inner Shadow parameters and effects -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408731] Krita crashes on showing welcome screen if a special tiff file is in Rec. Docs
https://bugs.kde.org/show_bug.cgi?id=408731 --- Comment #1 from Tymond --- Created attachment 120897 --> https://bugs.kde.org/attachment.cgi?id=120897=edit Crash log -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408750] New: Can't apply CUSTOM effects.
https://bugs.kde.org/show_bug.cgi?id=408750 Bug ID: 408750 Summary: Can't apply CUSTOM effects. Product: kdenlive Version: 19.04.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: bartol...@outlook.com Target Milestone: --- Created attachment 120896 --> https://bugs.kde.org/attachment.cgi?id=120896=edit custom effect can't be applied SUMMARY If i create a new custom effect (for example from volume default effect) when i drag it to an empty audio track, the effect will not be added, and nothing happens. in the example image: created a custom effect [2] from volume effect (gained at +10db) [1] after that moving the custom effect [2] to the timeline [3] nothing happens. SOFTWARE/OS VERSIONS Windows: 10 64 (available in About System) ADDITIONAL INFORMATION STEPS TO REPRODUCE 1. create a +10db volume custom effect 2. move custom effect to timeline 3. OBSERVED RESULT nothing EXPECTED RESULT the volume effect with +10fb gain will be addeed to timeline audio track. P.S. can someone confirm that the bug is present on Linux version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 --- Comment #5 from Konstantin Kharlamov --- (In reply to Konstantin Kharlamov from comment #4) > (In reply to Martin Flöser from comment #1) > > Please provide output of xprop and xwininfo of emacs. Emacs is known to be > > not standard compliant, it's a tricky application. > > Thanks, attached I did that with kwin-tiling extension enabled, is that okay? I can redo them if not. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 --- Comment #4 from Konstantin Kharlamov --- (In reply to Martin Flöser from comment #1) > Please provide output of xprop and xwininfo of emacs. Emacs is known to be > not standard compliant, it's a tricky application. Thanks, attached -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 --- Comment #3 from Konstantin Kharlamov --- Created attachment 120895 --> https://bugs.kde.org/attachment.cgi?id=120895=edit xwininfo on Emacs -Q -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408749] New: Krita crashes when drawing on the canvas while animation is playing and no frames are added
https://bugs.kde.org/show_bug.cgi?id=408749 Bug ID: 408749 Summary: Krita crashes when drawing on the canvas while animation is playing and no frames are added Product: krita Version: 4.2.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kapyia@gmail.com Target Milestone: --- SUMMARY Krita crashes when drawing on the canvas while animation is playing but there are no frames are added. STEPS TO REPRODUCE 1. Open up a new clean document and switch over to the Animation workspace 2. Immediately go over to the Animation docker and press Play 3. With the Freehand Brush Tool try to draw on the canvas while the Timeline is playing OBSERVED RESULT Krita instantly locks up, leaving no kritacrash.log file behind. EXPECTED RESULT I would expect Krita to stop the animation and continue as if you'd never hit Play in the first place, possibly triggering a warning saying "No active animation frames could be found". SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION When there ARE active frames available in the Timeline, Krita prevents the lock up by switching over to an available frame, pausing the timeline, and drawing onto it. Perhaps the software gets stuck looking for active frames and not finding any to draw onto? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 --- Comment #2 from Konstantin Kharlamov --- Created attachment 120894 --> https://bugs.kde.org/attachment.cgi?id=120894=edit xprop on Emacs -Q -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 --- Comment #1 from Martin Flöser --- Please provide output of xprop and xwininfo of emacs. Emacs is known to be not standard compliant, it's a tricky application. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] New: Hard to open apps clicking on the icons
https://bugs.kde.org/show_bug.cgi?id=408748 Bug ID: 408748 Summary: Hard to open apps clicking on the icons Product: plasmashell Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: carlon.l...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Since Plasma version 5.16 it is very difficult to open apps. It seems that clicking on the icons does not always result in the app being opened. I have to click multiple times, and even in that case, sometimes the application is not opened. The only reliable way to open is to hover on the application with the pointer and to press enter. STEPS TO REPRODUCE 1. Click on an icon, once or multiple times. OBSERVED RESULT Application not always opened. EXPECTED RESULT Application used to open after the first click. Now it opens only sometimes. Other times, multiple clicks are needed. Other times, no way to open it. I need to press enter. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Used to work in previous versions. I think I had 5.15.4 before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408741] dropdown menu appears on wrong side when window opened fullscreen on second display
https://bugs.kde.org/show_bug.cgi?id=408741 --- Comment #1 from Martin Flöser --- X11 or Wayland? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390630] Add filtering feature (only KDE apps, only GNOME apps, only phone apps, not phone apps, etc)
https://bugs.kde.org/show_bug.cgi?id=390630 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408747] New: System Settings crashes when trying to modify language from list
https://bugs.kde.org/show_bug.cgi?id=408747 Bug ID: 408747 Summary: System Settings crashes when trying to modify language from list Product: systemsettings Version: 5.16.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: n...@horsefucker.org Target Milestone: --- Application: systemsettings5 (5.16.0) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.19.49-1-lts x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: System settings does not let you chance your settings under System Settings -> Language. I tried removing a language (German and Japanese) and adding a language (American English), it always causes the application to segfault. - Custom settings of the application: Current Language list includes: British English, German, Japanese The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbf53320140 (LWP 10672))] Thread 6 (Thread 0x7fbf3a7e5700 (LWP 10699)): #0 0x7fbf581000d1 in poll () at /usr/lib/libc.so.6 #1 0x7fbf55dca7c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fbf55dcb7f2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7fbf4b397508 in () at /usr/lib/libgio-2.0.so.0 #4 0x7fbf55da5f21 in () at /usr/lib/libglib-2.0.so.0 #5 0x7fbf56b03a92 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fbf5810acd3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fbf3afe6700 (LWP 10698)): #0 0x7fbf581000d1 in poll () at /usr/lib/libc.so.6 #1 0x7fbf55dca7c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fbf55dca8ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fbf55dca902 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fbf55da5f21 in () at /usr/lib/libglib-2.0.so.0 #5 0x7fbf56b03a92 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fbf5810acd3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fbf42f5d700 (LWP 10696)): #0 0x7fbf581000d1 in poll () at /usr/lib/libc.so.6 #1 0x7fbf55dca7c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fbf55dca8ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fbf58633984 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fbf585dd4dc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fbf58422239 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fbf577af059 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fbf5842363c in () at /usr/lib/libQt5Core.so.5 #8 0x7fbf56b03a92 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fbf5810acd3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fbf43c91700 (LWP 10675)): #0 0x7fbf56b09bac in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbf482b0304 in () at /usr/lib/dri/i965_dri.so #2 0x7fbf482b0028 in () at /usr/lib/dri/i965_dri.so #3 0x7fbf56b03a92 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fbf5810acd3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fbf50d14700 (LWP 10674)): #0 0x7fbf581000d1 in poll () at /usr/lib/libc.so.6 #1 0x7fbf55dca7c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fbf55dca8ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fbf58633984 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fbf585dd4dc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fbf58422239 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fbf588abba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fbf5842363c in () at /usr/lib/libQt5Core.so.5 #8 0x7fbf56b03a92 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fbf5810acd3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fbf53320140 (LWP 10672)): [KCrash Handler] #6 0x7fbf5762e6ae in QV4::QObjectWrapper::wrap(QV4::ExecutionEngine*, QObject*) () at /usr/lib/libQt5Qml.so.5 #7 0x7fbf576cee25 in QV4::ExecutionEngine::fromVariant(QVariant const&) () at /usr/lib/libQt5Qml.so.5 #8 0x7fbf5762bd33 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fbf5762cc3a in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) () at /usr/lib/libQt5Qml.so.5 #10 0x7fbf5762d4b7 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) () at /usr/lib/libQt5Qml.so.5 #11 0x7fbf401cf598 in () #12 0x in () [Inferior 1 (process
[kontact] [Bug 408736] Message Window no longer shows URL of link.
https://bugs.kde.org/show_bug.cgi?id=408736 --- Comment #4 from lnx...@westlot.net --- Created attachment 120893 --> https://bugs.kde.org/attachment.cgi?id=120893=edit Kontact Mail Window There is no status bar on the email window. Is this perhaps the problem? Is there a new setting somewhere that defaulted to there not being a status bar in the email window? Here's a screenshot of the window over the Kontact window, you can see the status bar of the main Kontact window just under the email window. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408693] Text goes underneath already placed shape/symbol
https://bugs.kde.org/show_bug.cgi?id=408693 --- Comment #2 from Ahab Greybeard --- I've just tested the 15th June krita-4.3.0-prealpha-bebb0d6-x86_64.appimage and it is now different. Creating and editing a text object makes it go one level lower than the highest non-text object on the layer. Further to that, it then goes one layer lower than the highest of any other text boxes that are also immediately under that highest level non-text object. Text boxes seem to have their own stacking order separate from non-text objects but subsidiary to non-text objects. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408660] Konsole's cursor becomes colorized by colorized print output
https://bugs.kde.org/show_bug.cgi?id=408660 Postix changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Postix --- Thanks Egmont, that means you can confirm it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408660] Konsole's cursor becomes colorized by colorized print output
https://bugs.kde.org/show_bug.cgi?id=408660 Postix changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408746] New: emacs full screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=408746 Bug ID: 408746 Summary: emacs full screen doesn't work Product: kwin Version: 5.16.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: hi-an...@yandex.ru Target Milestone: --- SUMMARY Pressing kwin's "full screen" button doesn't work with Emacs. This was found as part of research on this issue https://github.com/kwin-scripts/kwin-tiling/issues/161 STEPS TO REPRODUCE 1. Start `emacs -Q` 2. Press the button that you have bound to "make window fullscreen" kwin action OBSERVED RESULT Nothing happens. EXPECTED RESULT Emacs should get opened to full screen. SOFTWARE/OS VERSIONS Window API: X11 KDE Plasma Version: 5.16 KDE Frameworks Version: 5.59 Qt Version: 5.12.3 ADDITIONAL INFORMATION This works fine on i3wm, so this looks like kwin issue. -- You are receiving this mail because: You are watching all bug changes.
