[KScreen] [Bug 358689] Support Qt 5.6 new highdpi environment variable

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358689

--- Comment #6 from Martin Gräßlin  ---
(In reply to Weng Xuetian from comment #5)
> Emm, I'd prefer leave it open until it support real "per screen" setting
> instead of set same ratio for all screen.

we cannot have per screen on X11.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365366] Can not download new Version

[Thomas Baumgart via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365366

--- Comment #8 from Thomas Baumgart  ---
*** Bug 365307 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365307] Download

[Thomas Baumgart via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365307

Thomas Baumgart  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #5 from Thomas Baumgart  ---


*** This bug has been marked as a duplicate of bug 365366 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kgamma] [Bug 353689] Display Broadcast RGB color space settings support request

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353689

--- Comment #3 from Martin Gräßlin  ---
Ok I don't have any idea about that. I think it's best to keep it in kgamma
module as that's about adjusting the color space of the output in the most
broadest way.

Unfortunately I do not expect that this will developed and added any time soon.
Maybe on Wayland, but for X11 I consider it as unlikely.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 365797] Second monitor distorts when being adjusted

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365797

--- Comment #8 from Martin Gräßlin  ---
That looks all fine:
* xorg log doesn't have warnings
* kwin debug output is correct - it detected the screens as printed in xorg
log, compositor is active and happy
* glxinfo doesn't show any "bad" limits

My assumption currently is that also Plasma (and other applications) get the
graphics reset from the NVIDIA driver. If that's the case you don't need to
restart the complete session. A
kquitapp5 plasmashell
plasmashell

from e.g. KRunner should also fix it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ki18n] [Bug 365917] ki18n fails to link on musl libc due to _nl_msg_cat_cntr

[awilfox]

https://bugs.kde.org/show_bug.cgi?id=365917

--- Comment #1 from A. Wilcox (awilfox)  ---
Created attachment 100223
  --> https://bugs.kde.org/attachment.cgi?id=100223=edit
Patch to ki18n to check for presence of _nl_msg_cat_cntr before using it

I cannot upload to Gerrit using my KDE Identity account (awilcox) so I am
submitting the patch here.  This patch allows ki18n (tested on 5.21.0, 5.24.0,
and master) to build on both glibc (using _nl_msg_cat_cntr) and musl (without
using _nl_msg_cat_cntr).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365366] Can not download new Version

[Thomas Baumgart via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365366

Thomas Baumgart  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Thomas Baumgart  ---
The MS-Windows version of KMyMoney 4.8 was generated and uploaded yesterday.
The link on the kmymoney.org website has been updated. Please use
https://sourceforge.net/projects/kmymoney2/files/KMyMoney-Windows/4.8.0/kmymoney-x86-setup-4.8.0.exe/download
to download the installer.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kguiaddons] [Bug 365894] KMail(2) documentation not available

[Burkhard Lueck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365894

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1

[Kai Uwe Broulik via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365570

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Resolution|--- |FIXED
   Version Fixed In||5.7.2
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 358311] broken highlighting

[Kevin Funk via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358311

--- Comment #8 from Kevin Funk  ---
FYI: Related reviews/commits:
https://git.reviewboard.kde.org/r/128480/
http://commits.kde.org/kdevelop/5d076e29438261f3b70b633fd79551a50f0e9ef6
http://commits.kde.org/kdevplatform/c9265847835d8d534906ae7ec42aa3784c54d0df

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365868] Hang in plasmashell when searching for specific "mä" in widgets using widget explorer

[Mattias Põldaru via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365868

--- Comment #10 from Mattias Põldaru  ---
I hot-patched the right file and can confirm, this workaround definitely made
the resize loop go away. Thank you!

Maybe the resize loop needs something like resize attempt counter so it would
always stop after a few rounds and be happy with the smaller width?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 362531] Plasma panels are not transparent after login

[Leslie Zhai via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362531

--- Comment #22 from Leslie Zhai  ---
(In reply to Marco Martin from comment #20)
> (In reply to Leslie Zhai from comment #18)
> > When meets the race situation - KWin has not registered
> > _KDE_NET_WM_BACKGROUND_CONTRAST_REGION, my monkey patch still could NOT work
> > ;-)
> 
> since you can reproduce and have it built from source...
> can you put some debug output in effectwatcher.cpp?
> I'm especially interested in EffectWatcher::nativeEventFilter
> * if events are catched at all by nativeEventFilter
> * if it ever arrives in the branch with the emit
> effectChanged(m_effectActive);
> * what are the values of m_effectActive and isEffectActive() when (if) the
> events arrive

my debug.patch https://forum.isoft-linux.org/viewtopic.php?f=4=42

and my test way:
1. pkill plasmashell
2. run plasmashell again
3. openbox --replace
4. kwin_x11 --replace

result:
* EffectWatcher constructor for "_KDE_NET_WM_BACKGROUND_CONTRAST_REGION" atom
is often !isNull()
* kwin_x11 enabled _KDE_NET_WM_BACKGROUND_CONTRAST_REGION, m_effectActive is
true
* when switch to openbox wm without supporting (due to it is only for KWin)
_KDE_NET_WM_BACKGROUND_CONTRAST_REGION, isEffectActive is false, and
m_effectActive became false, then emit effectChanged
* when switch back to kwin_x11, isEffectActive is true, and m_effectActive
became true, then emit effectChanged

so the race condition is just like "openbox --replace" || disabled
_KDE_NET_WM_BACKGROUND_CONTRAST_REGION

Regards,
Leslie Zhai

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 358689] Support Qt 5.6 new highdpi environment variable

[Weng Xuetian via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358689

--- Comment #5 from Weng Xuetian  ---
Emm, I'd prefer leave it open until it support real "per screen" setting
instead of set same ratio for all screen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 365920] New: Exporting file from pdf crashes with segmetation fault.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365920

Bug ID: 365920
   Summary: Exporting file from pdf crashes with segmetation
fault.
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: a246246_246-...@yahoo.co.jp

When I try to convert pdf to tiff using the following command line:

$krita.exe" --export --export-filename=sample.tif -- sample.pdf

It opens dialog "PDF Import Options".  Select First page and other settings are
also kept as default, then click OK.

Program crashes with

Segmentation fault

and no tif image is generated. Note that sample.pdf is 1 page.


Reproducible: Always

Steps to Reproduce:
See Details.


Actual Results:  
Segmentation fault without result image.

Expected Results:  
result image is generated.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 365864] Display layout preview renders off-window in Display Configuration using Wayland

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365864

Christoph Feck  changed:

   What|Removed |Added

Product|systemsettings  |KScreen
  Component|general |kcm
   Assignee|plasma-b...@kde.org |se...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 365865] Display resolution setting in Display Configuration not obeyed in Wayland Plasma session

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365865

Christoph Feck  changed:

   What|Removed |Added

Product|systemsettings  |KScreen
  Component|general |common
   Assignee|plasma-b...@kde.org |se...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 365900] Cannot enter required password when trying to enable Nvidia video driver

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365900

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||cf...@kde.org

--- Comment #2 from Christoph Feck  ---
Please report issues with the Driver Manager directly to the bug tracker of
your distribution.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 353099] git master (reopened) - When project playback reaches near end of timeline, pause function becomes unresponsive

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353099

Jesse  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Jesse  ---
Confirmed fix in latest git master build. Works great! Thanks JB! Marking as
resolved/fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 353051] Consider having Play button and SPACEBAR in Project Monitor play project from the beginning of timeline

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353051

Jesse  changed:

   What|Removed |Added

   Platform|Kubuntu Packages|Mint (Ubuntu based)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 353051] Consider having Play button and SPACEBAR in Project Monitor play project from the beginning of timeline

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353051

--- Comment #1 from Jesse  ---
Any chance this can be considered before the 16.08 release, or is there a
reason hitting SPACEBAR when at the end of the timeline doesn't play the
project from the beginning of the timeline?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[kubik via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354400

--- Comment #53 from kubik  ---
(In reply to kubik from comment #52)
> In my Debian (jessie or stretch) installing package kdepim (and reboot)
> solved this problem.

Edit: Another package is needed: baloo-utils :-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 365832] cursor image is mixture of two cursors

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365832

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||cf...@kde.org

--- Comment #1 from Christoph Feck  ---
The cursor is rendered by the video drivers for the X11 server. Please report
this issue to the developers of your video drivers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 365845] QPushButtons and other default UI elements are too big

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365845

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
Product|kde |Breeze
   Assignee|unassigned-b...@kde.org |hugo.pereira.da.costa@gmail
   ||.com
  Component|general |QStyle
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Christoph Feck  ---
> Is there a way to scale down the size of the default ui elements?

Use a different widget style, such as QtCurve or Skulpture.

For Plasma 5, KDE developers increased the default size to follow the trend of
High-DPI and finger-friendly interfaces.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 365861] Saving file in LibreOffice as docx

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365861

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Feck  ---


*** This bug has been marked as a duplicate of bug 341990 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Baloo] [Bug 341990] Baloo Crash - XapianDocument::getValue

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=341990

Christoph Feck  changed:

   What|Removed |Added

 CC||richardjhdonald...@gmail.co
   ||m

--- Comment #99 from Christoph Feck  ---
*** Bug 365861 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kauth] [Bug 365910] Adjust Date and Time applet crash following suspend-resume cycle

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365910

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org
  Component|general |general
Product|kde |frameworks-kauth

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 365815] filename rendering issues in Kate's Open dialog

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365815

--- Comment #1 from Christoph Feck  ---
> Screenshot attached.

Please attach it using the "Add an attachment" link on this page. If you
already uploaded it to a third-party file host, you may also add a comment with
the link.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Severe flickering when interacting with some windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #1 from Chris  ---
Well, now I can't duplicate what was happening. Well, I'll post another comment
here when it starts happening again...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365919] New: Slideshow does not show any more than the first slide.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365919

Bug ID: 365919
   Summary: Slideshow does not show any more than the first slide.
   Product: digikam
   Version: 5.0.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: SlideShow
  Assignee: digikam-de...@kde.org
  Reporter: russell.ev...@gmail.com

Using the Slideshow option, only the first slide is displayed.  This is the
case for the selection or all mode.  This is the for the 64 bit version on
Windows 10.  Please note the that Slideshow function works in version 4.14 of
Digikam, so I am using that version at this time.

Reproducible: Always

Steps to Reproduce:
1. Select a few slides
2. Try the Slideshow option
3.  Only the first slide is displayed.

Actual Results:  
Only one slide is shown

Expected Results:  
A slideshow of the selected photos.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 362570] Kscreen settings no longer shows display ID since 16.04 update

[jamese via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362570

--- Comment #3 from jamese  ---
Thanks  for the response.

Consider that hitting the [i] info button shows on screen eith DP1-1 or DP1-2,
which is great but there is no correlation with the  'Display ID' on the OSD
and the related "Dell Inc,  Dell U2414H" labelled screen in the settings
window, as those labels don't include DP1-1 or DP1-2.

The only way to see which of the screens is DP1-1 and which is DP1-2 is to
click on the screen and look at the title above the "Display [ ] Enabled"
checkbox.
Previously, as I knew my DP1-2 screen was the left one, I could just look at
the screen layout presented and drag and drop it to the left, then DP1-1 to the
right. Didn't have to click the "i" or look at the screen title.

The recent change added an extra step when you have two identical external
screens.

There is a previous version with the "Display id" here, in this case HDM1 -
https://www.kde.org/announcements/plasma-5.2/kscreen.png

If the label for the screen said "DP1-1/2, Dell Inc, U2414H" that'd solve the
issue.

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] New: Severe flickering when interacting with some windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

Bug ID: 365918
   Summary: Severe flickering when interacting with some windows
   Product: kwin
   Version: 5.7.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: scene-opengl
  Assignee: kwin-bugs-n...@kde.org
  Reporter: emailofch...@gmail.com

When I use GLX as my backend, everything works fine (though I do experience
tearing sometimes, though that's a separate issue that's partly thanks to
Nvidia). And as of a recent update that included xorg-server and some others,
using OpenGL as the backend causes severe flickering on the desktop or entire
screen.

Since this can't be captured with a screenshot, I'm going to capture a video of
it. This will take a bit more time, so I'll be linking that in a while.

Reproducible: Always

Steps to Reproduce:
1. Switch to one of the two OpenGL backends.
2. Open one or a few new Dolphin windows, for example.
3. Move the cursor around on top of it.

Actual Results:  
Flickering in areas of the screen.

Expected Results:  
Nothing out of the ordinary should happen.

Using Nvidia might or might not be a factor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365916] Multiple clicks on the system tray crashes plasma shell

[idoitprone via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365916

--- Comment #4 from idoitprone  ---
Created attachment 100222
  --> https://bugs.kde.org/attachment.cgi?id=100222=edit
Crash logs when clicking on a blutetooth icon

It seems to be easier to reproduce this crash by repeatedly clicking bluetooth
and I do not have bluetooth on this laptop

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdesu] [Bug 349668] kdesu freeze if two-factor authentication pam is set

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349668

Chris  changed:

   What|Removed |Added

 CC||riddo...@gmail.com

--- Comment #1 from Chris  ---
I have the same issue, also with the same configuration line.  If I had the
time, I'd try to fix this, but right now all I can do is confirm the problem. 
It appears to time out, given a couple minutes, to return a 'permission
denied'.

In case someone has doubts about it, ordinary sudo in my terminal works, as
does my ssh configuration.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346740

David Edmundson  changed:

   What|Removed |Added

 CC||monkeyboy...@yahoo.com

--- Comment #57 from David Edmundson  ---
*** Bug 365670 has been marked as a duplicate of this bug. ***

--- Comment #58 from David Edmundson  ---
*** Bug 365916 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346740

--- Comment #57 from David Edmundson  ---
*** Bug 365670 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365670] Plasma crashed when selecting contact IM

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365670

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from David Edmundson  ---


*** This bug has been marked as a duplicate of bug 346740 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365916] Multiple clicks on the system tray crashes plasma shell

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365916

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from David Edmundson  ---


*** This bug has been marked as a duplicate of bug 346740 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365916] Multiple clicks on the system tray crashes plasma shell

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365916

--- Comment #2 from David Edmundson  ---
>I forgot to mention I enable Opengl 3.1 ES since Martin seems to complain 
>about common bugs lately. I will try to see if this crash ever happens in 
>Opengl 3.1 GLX. 

It's not. Dont' feel the need to try it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365916] Multiple clicks on the system tray crashes plasma shell

[idoitprone via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365916

--- Comment #1 from idoitprone  ---
I forgot to mention I enable Opengl 3.1 ES since Martin seems to complain about
common bugs lately. I will try to see if this crash ever happens in Opengl 3.1
GLX. 

I wonder if it is related. Oh well

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365295] The three icons in buttons "Search", "Filter" and "Close" are very small

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365295

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #5 from David Edmundson  ---
If the icons are different to activity manager that's a bug, yes. Sorry to
misunderstand you at first.

Unfortunately I can't reproduce it, and the code between the two is mostly
identical.

Can you send me your exact font and icon config and reopen this bug report.
(ideally just attach your ~/.config/kdeglobals)

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ki18n] [Bug 365917] New: ki18n fails to link on musl libc due to _nl_msg_cat_cntr

[awilfox]

https://bugs.kde.org/show_bug.cgi?id=365917

Bug ID: 365917
   Summary: ki18n fails to link on musl libc due to
_nl_msg_cat_cntr
   Product: frameworks-ki18n
   Version: 5.24.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: caslav.i...@gmx.net
  Reporter: awil...@adelielinux.org
CC: kdelibs-b...@kde.org

We're trying to package KDE Plasma 5 for our new distribution Adélie Linux,
based on the musl libc.  The musl libc provides libintl (similar to glibc) but
does not use the same internals, so even though we are using the GNU gettext
(__USE_GNU_GETTEXT = 1), the libintl included with the libc does not define
_nl_msg_cat_cntr (nor does it need it).

There is no preprocessor definition for musl (as it is an attempt to be a
strictly compliant POSIX C library - see
http://wiki.musl-libc.org/wiki/FAQ#Q:_why_is_there_no_MUSL_macro_.3F for info)
so it should likely be a CMake test to determine if the symbol is available.

Reproducible: Always

Steps to Reproduce:
1. Use musl libc.
2. Attempt to build ki18n.


Actual Results:  
/usr/src/kde-frameworks/ki18n-5.24.0/work/ki18n-5.24.0/src/kcatalog.cpp:177:
undefined reference to `_nl_msg_cat_cntr'

Expected Results:  
Successful build.

Relevant configure output:

-- Looking for __GLIBC__
-- Looking for __GLIBC__ - not found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Looking for dngettext
-- Looking for dngettext - found
-- libintl is part of libc, no extra library is required.
-- Found LibIntl: /usr/include  
-- Found Gettext: /usr/bin/msgmerge (found version "0.19.7") 


Relevant build log output:

CMakeFiles/KF5I18n.dir/kcatalog.cpp.o: In function
`KCatalogPrivate::setupGettextEnv()':
/usr/src/kde-frameworks/ki18n-5.24.0/work/ki18n-5.24.0/src/kcatalog.cpp:177:
undefined reference to `_nl_msg_cat_cntr'
collect2: error: ld returned 1 exit status
src/CMakeFiles/KF5I18n.dir/build.make:276: recipe for target
'src/libKF5I18n.so.5.24.0' failed

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365916] Multiple clicks on the system tray crashes plasma shell

[idoitprone via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365916

idoitprone  changed:

   What|Removed |Added

Summary|Multiple clicks on the  |Multiple clicks on the
   |system tray crashes |system tray crashes plasma
   ||shell

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365916] New: Multiple clicks on the system tray crashes

[idoitprone via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365916

Bug ID: 365916
   Summary: Multiple clicks on the system tray crashes
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: monkeyboy...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.27-24-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I was clicking on the chipboard constantly. I only manage to crash the plasma
shell twice.

In other instance, I mange to crash the shell by repeatly clicking on the icon
in the expanded system tray as indicated by the triangle array

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb85d3ca7c0 (LWP 1730))]

Thread 7 (Thread 0x7fb83700 (LWP 1817)):
#0  0x7fb8568cbbfd in poll () at /lib64/libc.so.6
#1  0x7fb852fa8e64 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb838003070, timeout=-1, context=0x7fb838000990) at gmain.c:4103
#2  0x7fb852fa8e64 in g_main_context_iterate
(context=context@entry=0x7fb838000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3803
#3  0x7fb852fa8f7c in g_main_context_iteration (context=0x7fb838000990,
may_block=1) at gmain.c:3869
#4  0x7fb8571f8d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fb85719fd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fb856fc161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fb85a2d5e18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fb856fc632f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fb8560d50a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fb8568d402d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fb832d6f700 (LWP 1821)):
#0  0x7fb8568cbbfd in poll () at /lib64/libc.so.6
#1  0x7fb852fa8e64 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb82c002e70, timeout=-1, context=0x7fb82c000990) at gmain.c:4103
#2  0x7fb852fa8e64 in g_main_context_iterate
(context=context@entry=0x7fb82c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3803
#3  0x7fb852fa8f7c in g_main_context_iteration (context=0x7fb82c000990,
may_block=1) at gmain.c:3869
#4  0x7fb8571f8d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fb85719fd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fb856fc161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fb85a2d5e18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fb856fc632f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fb8560d50a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fb8568d402d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fb83155c700 (LWP 1822)):
#0  0x7fb8568cbbfd in poll () at /lib64/libc.so.6
#1  0x7fb852fa8e64 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb824003070, timeout=-1, context=0x7fb824000990) at gmain.c:4103
#2  0x7fb852fa8e64 in g_main_context_iterate
(context=context@entry=0x7fb824000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3803
#3  0x7fb852fa8f7c in g_main_context_iteration (context=0x7fb824000990,
may_block=1) at gmain.c:3869
#4  0x7fb8571f8d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fb85719fd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fb856fc161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fb85a2d5e18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fb856fc632f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fb8560d50a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fb8568d402d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fb82bbd7700 (LWP 1823)):
#0  0x7fb8560d903f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb85caa486b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fb85caa4899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fb8560d50a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fb8568d402d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fb7a3fff700 (LWP 1824)):
#0  0x7fb8568c7ccd in read () at /lib64/libc.so.6
#1  0x7fb852fe9b60 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fb7a3ffebb0, __fd=) at /usr/include/bits/unistd.h:44
#2  0x7fb852fe9b60 in g_wakeup_acknowledge (wakeup=0x7fb824002780) at
gwakeup.c:210
#3  0x7fb852fa8999 in g_main_context_check

[plasmashell] [Bug 365868] Hang in plasmashell when searching for specific "mä" in widgets using widget explorer

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365868

--- Comment #9 from David Edmundson  ---
Given you have gdb skills, if you want to test a patch:

https://phabricator.kde.org/D2239

but don't feel you have to.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kguiaddons] [Bug 365053] Icon overlay discards origin

[gandolfi rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365053

--- Comment #2 from gandolfi rafael  ---
Created attachment 100221
  --> https://bugs.kde.org/attachment.cgi?id=100221=edit
Self-contained test cases to illustrate the bug and the proposed patch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361976] git master (re-opened) - Playback of certain video files produces large distortion artifacts (video example & sample footage included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361976

Jesse  changed:

   What|Removed |Added

   Severity|major   |normal
Summary|16.07.70 git master -   |git master (re-opened) -
   |rendering from .mp4 h.264   |Playback of certain video
   |footage produces large  |files produces large
   |distortion artifacts (video |distortion artifacts (video
   |example & sample footage|example & sample footage
   |included)   |included)
   Platform|Ubuntu Packages |Mint (Ubuntu based)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365868] Hang in plasmashell when searching for specific "mä" in widgets using widget explorer

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365868

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361976] 16.07.70 git master - rendering from .mp4 h.264 footage produces large distortion artifacts (video example & sample footage included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361976

Jesse  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #7 from Jesse  ---
I needed to re-open this one, because I'm having a heck of a time trying to
make video files not have distortion with video files made from Blender.

Literally, the only difference that shows in the clip monitor between video
clips from Blender and video clips rendered in Kdenlive from Blender, is the
bitrate: blender video files have a bitrate of 31,697 kb/s, while Kdenlive
rendered projects FROM Blender video clips are 19,864 kb/s.

Does Kdenlive have an issue with other higher bitrate video files? If not, any
idea what the problem could be?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365899] Plasma unexpectedly crashes

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365899

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---
>#9 0x in _mesa_Clear () at /usr/lib/dri/i965_dri.so

Crash is deep inside mesa, your graphic driver. 

There is nothing we can do. Please upgrade/downgrade your version of mesa to
fix this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365902] Crash after changing network connection

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365902

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---


*** This bug has been marked as a duplicate of bug 346118 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346118

David Edmundson  changed:

   What|Removed |Added

 CC||ralf.habac...@freenet.de

--- Comment #143 from David Edmundson  ---
*** Bug 365902 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Wladimir Mangelardo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356479

Wladimir Mangelardo  changed:

   What|Removed |Added

 CC||wmangela...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1

[Bob Wya via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365570

Bob Wya  changed:

   What|Removed |Added

 Attachment #100134|0   |1
is obsolete||

--- Comment #12 from Bob Wya  ---
Created attachment 100220
  --> https://bugs.kde.org/attachment.cgi?id=100220=edit
Refactored for Plasma 5.7.2: John Salatas's
plasma-workspace-5.7.0-systray_iconsize.patch

Sigh :-(

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 364524] kcmshell5 kcm_sddm dumps core everytime it is executed

[Bob Wya via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364524

--- Comment #1 from Bob Wya  ---
Still present in 5.7.2 ... Sigh...

kcmshell5 kcm_sddm

QDBusArgument: read from a write-only object
Aborted (core dumped)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #31 from Jesse  ---
Been testing the updated packages. 90% working, but I came across a few issues.
I made an in-depth video so you could see them: https://youtu.be/KYySd7hJtKQ.

Sorry if I'm talking too fast. Let me know so I can slow it down in future
videos. :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[klipper] [Bug 221206] Klipper does not allow to select (and thus to make it ready for pasting) most recently added (sic!) clipboard entry

[Maciej Mrozowski via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=221206

--- Comment #16 from Maciej Mrozowski  ---
Just a comment, I'm unable to reproduce the problem anymore for quite some
time.
And now with plasma5, where klipper is replaced with plasmoid... feel free to
close this one as 'obsolete' unless people who commented have some objections.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 365915] New: Dolphin crash on NFS copy

[Dan Mons via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365915

Bug ID: 365915
   Summary: Dolphin crash on NFS copy
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: dm...@cuttingedge.com.au

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-31-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Copied a file on an NFSv3 server.  From NFS location to the same export.  NFS
server has root squash.

- Custom settings of the application:

NFSv3 storage (Solaris/ZFS/NFSv3), root squash, mounted on local system.  All
Dolphin file copies done as a non-root user locally.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0d733298c0 (LWP 3135))]

Thread 5 (Thread 0x7f0d4f189700 (LWP 3139)):
#0  0x7f0d72d61e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0d6955639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0d695564ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0d6db6aa9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0d6db11dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0d6d92e8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0d6d93384e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0d6a0e16fa in start_thread (arg=0x7f0d4f189700) at
pthread_create.c:333
#8  0x7f0d72d6db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f0d52a3a700 (LWP 3138)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0d56f47aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f0d56f47907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f0d6a0e16fa in start_thread (arg=0x7f0d52a3a700) at
pthread_create.c:333
#4  0x7f0d72d6db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f0d5323b700 (LWP 3137)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0d56f47aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f0d56f47907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f0d6a0e16fa in start_thread (arg=0x7f0d5323b700) at
pthread_create.c:333
#4  0x7f0d72d6db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f0d5d856700 (LWP 3136)):
#0  0x7f0d72d61e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0d674edc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f0d674ef8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f0d5fba8629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f0d6d93384e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0d6a0e16fa in start_thread (arg=0x7f0d5d856700) at
pthread_create.c:333
#6  0x7f0d72d6db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0d733298c0 (LWP 3135)):
[KCrash Handler]
#6  0x7f0d72c61930 in vtable for DolphinFileItemListWidget () from
/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#7  0x7f0d6db24fc7 in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0d71366b99 in KDialogJobUiDelegate::Private::next() () from
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9  0x7f0d6db43ea1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f0d6e61705c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f0d6e61c516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f0d6db1462b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f0d6db16a26 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f0d6db6a673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 

[Breeze] [Bug 365035] Regression: folder-tar and folder-scripts missing on smallest size

[andreas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365035

andreas  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from andreas  ---
It's fixed in master and will be released with KF 5.25.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout

[Francis Herne via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364650

--- Comment #8 from Francis Herne  ---
Backtrace:

#0  0x7fffdb2d20b8 in ?? () from /usr/lib/qt/plugins/styles/breeze.so
#1  0x7490d8b6 in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#2  0x755ede78 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#3  0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#4  0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress
(this=0xfa8c40, keyEvent=0x7f7ff6e0) at
/home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310
#5  0x77902574 in KateVi::InputModeManager::handleKeypress
(this=0x9e5160, e=0x7f7ff6e0) at
/home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147
#6  0x778c199d in KateViInputMode::keyPress (this=0x93d460,
e=0x7f7ff6e0) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292
#7  0x778c125f in KateViInputMode::stealKey (this=0x93d460,
k=0x7f7ff6e0) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144
#8  0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80,
obj=0x9ee140, e=0x7f7ff6e0) at
/home/flh/projects/ktexteditor/src/view/kateviewinternal.cpp:2280
#9  0x7490d9e1 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#10 0x755ede15 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#11 0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#12 0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress
(this=0xfa8c40, keyEvent=0x7f7ffb00) at
/home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310
#13 0x77902574 in KateVi::InputModeManager::handleKeypress
(this=0x9e5160, e=0x7f7ffb00) at
/home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147
#14 0x778c199d in KateViInputMode::keyPress (this=0x93d460,
e=0x7f7ffb00) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292
#15 0x778c125f in KateViInputMode::stealKey (this=0x93d460,
k=0x7f7ffb00) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144
#16 0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80,
obj=0x9ee140, e=0x7f7ffb00) at
/home/flh/projects/ktexteditor/src/view/kateviewinternal.cpp:2280
#17 0x7490d9e1 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#18 0x755ede15 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#19 0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#20 0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress
(this=0xfa8c40, keyEvent=0x7f7fff20) at
/home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310
#21 0x77902574 in KateVi::InputModeManager::handleKeypress
(this=0x9e5160, e=0x7f7fff20) at
/home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147
#22 0x778c199d in KateViInputMode::keyPress (this=0x93d460,
e=0x7f7fff20) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292
#23 0x778c125f in KateViInputMode::stealKey (this=0x93d460,
k=0x7f7fff20) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144
#24 0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80,
obj=0x9ee140, e=0x7f7fff20) at
/home/flh/projects/ktexteditor/src/view/kateviewinternal.cpp:2280
#25 0x7490d9e1 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#26 0x755ede15 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#27 0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#28 0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress
(this=0xfa8c40, keyEvent=0x7f800340) at
/home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310
#29 0x77902574 in KateVi::InputModeManager::handleKeypress
(this=0x9e5160, e=0x7f800340) at
/home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147
#30 0x778c199d in KateViInputMode::keyPress (this=0x93d460,
e=0x7f800340) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292
#31 0x778c125f in KateViInputMode::stealKey (this=0x93d460,
k=0x7f800340) at
/home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144
#32 0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80,
obj=0x9ee140, e=0x7f800340) at

[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout

[Francis Herne via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364650

Francis Herne  changed:

   What|Removed |Added

 CC||m...@flherne.uk

--- Comment #7 from Francis Herne  ---
Assuming I'm looking at the same bug...

For me it happens frequently when using '/', with a variety of keys and my
usual UK keyboard layout.

Reverting
https://quickgit.kde.org/?p=ktexteditor.git=commit=025edb11ca9b0fa3685802e6c9cb608a4daa7911
avoids it.

I get a loopy backtrace several tens of thousands of calls deep until the stack
fills up - line 310 of emulatedcommandbar.cpp re-emits a key event, which is
then handled again resulting in an endless cycle of duplicate events.

The surrounding 'm_suspendEditEventFiltering' assignments seem intended to
avoid these, but the only method checking that attribute is
EmulatedCommandBar::eventFilter() which isn't called.

KateViewInternal::eventFilter() *is* called, so the patch author might have
been confused about which class object would handle the duplicated event.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365836] "next activity" and "previous activity" shortcuts erratic

[Michael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365836

--- Comment #5 from Michael  ---
(In reply to Ivan Čukić from comment #4)
> I'm unable to replicate this on a live neon (updated to 5.7.2)
> 
> If I only press meta+tab, meta+tab, meta+tab it alternates between the two
> last used activities - pressing meta+tab switches to the previous one (like
> with alt+tab for windows).

You're right, 'previous activity' alone does not have erratic behavior.  The
behavior of 'next activity' is erratic. I think the keybindings introduce a bit
of a delay, I'll describe how I trigger the race condition. I bind "next
activity" and "previous activity" to the forward/back buttons on my mouse. I
send dbus commands with xbindkeys. Pressing meta+tab and meta+shift+tab
introduces a bit of a delay so the race condition is less obvious.

#Previous Activity - forward button
"qdbus org.kde.kglobalaccel /component/plasmashell invokeShortcut 'previous
activity'"
   b:9

#Next Activity - back button
"qdbus org.kde.kglobalaccel /component/plasmashell invokeShortcut 'next
activity'"
   b:8



> If I press meta+tab,tab,tab, it goes through the list from the most recently
> used one to the least recently used one. 

So perhaps it will make sense why I preferred the behavior in Plasma 5.5:
there's no way to bind meta+tab+tab+tab to mouse buttons, and no dbus interface
I can use to replicate this. I don't think mimicking behavior similar to
alt+tab is a good justification for the change. For one, the activity bar
widget does not change around activity order, so there's no longer any useful
visual indicator to explain where you're going to go when you press meta+tab or
meta+shift+tab. I usually don't care to remember in advance which activity I
came from last, I just want to cycle through the activity bar. Next, I expect
people using more than 3-4 activities to be extremely small. When there are
only 3 activities running there is not really any benefit to changing the order
of activities around. Previously, with two shortcuts, there was always one
button to map to each alternate activity. With four activities running, only
one activity would require more than two presses. Pulling up a large activities
sidebar to remind you of all the choices is not as useful. In the alt+tab task
switcher case, it makes sense to observe the pop-up if you have 10 or 15
windows open. And finally, activating "previous activity" then "next activity"
does not necessarily return you to where you started if you send the commands
quickly enough. The commands are non-invertible. 


On top of those personal workflow preferences there is still the race condition
with "next activity." if "previous activity" returns you to the activity you
were using previously, what is a sensible behavior for "next activity" if you
haven't pressed "previous activity?" There is no next, you're at the end of the
line. I think at a minimum sending the 'next activity' command repeatedly
shouldn't make the Activity Switcher widget flip around unpredictably.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kexi] [Bug 365914] New: Crash when try to change the type of a field and then add data

[Juan José Morales via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365914

Bug ID: 365914
   Summary: Crash when try to change the type of a field and then
add data
   Product: kexi
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: kexi-b...@kde.org
  Reporter: juanjosemoralesar...@gmail.com
CC: a...@piggz.co.uk, in...@fables.co.za

Application: kexi (3.0 Alpha (git  master))
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.0-31-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Change the type of a field and later try to add some data

- Unusual behavior I noticed:
The application crash

- Custom settings of the application:

compiled from source

-- Backtrace:
Application: Kexi (kexi), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f181b45d8c0 (LWP 4492))]

Thread 3 (Thread 0x7f17fd1ee700 (LWP 4496)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f18052af213 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7f18052ae937 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7f18162616fa in start_thread (arg=0x7f17fd1ee700) at
pthread_create.c:333
#4  0x7f181a2c3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f180845a700 (LWP 4493)):
#0  0x7f181a2b7e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1811295c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f18112978d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f180a7ac629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f181a62b84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f18162616fa in start_thread (arg=0x7f180845a700) at
pthread_create.c:333
#6  0x7f181a2c3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f181b45d8c0 (LWP 4492)):
[KCrash Handler]
#6  KDbExpression::isNull (this=0x30003000320030) at
/home/juan/kde/src/kdb/src/expression/KDbExpression.cpp:287
#7  0x7f1819434a7d in KDbField::type (this=this@entry=0x2a29800) at
/home/juan/kde/src/kdb/src/KDbField.cpp:207
#8  0x7f17f305e950 in KexiTableEdit::setupContents (this=0x2720710,
p=, focused=, val=..., txt=...,
align=@0x7ffc004b3cdc: 384, y_offset=@0x7ffc004b3cd8: 0, w=@0x7ffc004b3ccc:
120, h=@0x7ffc004b3cd0: 18) at
/home/juan/kde/src/kexi/src/widget/tableview/kexitableedit.cpp:220
#9  0x7f17f304e4a2 in KexiTableScrollArea::paintCell
(this=this@entry=0x2968290, p=p@entry=0x7ffc004b3ed0,
data=data@entry=0x28ecca0, record=record@entry=0, column=column@entry=0,
cr=..., print=false) at
/home/juan/kde/src/kexi/src/widget/tableview/KexiTableScrollArea.cpp:731
#10 0x7f17f304f578 in KexiTableScrollArea::paintRow (maxwc=360, collast=2,
colfirst=0, cy=, cx=, rowp=0, r=0,
pb=0x7ffc004b3ed0, data=0x28ecca0, this=0x2968290) at
/home/juan/kde/src/kexi/src/widget/tableview/KexiTableScrollArea.cpp:461
#11 KexiTableScrollArea::drawContents (this=0x2968290,
p=p@entry=0x7ffc004b3ed0) at
/home/juan/kde/src/kexi/src/widget/tableview/KexiTableScrollArea.cpp:586
#12 0x7f17f3059428 in KexiTableScrollAreaWidget::paintEvent
(this=0x2710f00, e=0x7ffc004b41b0) at
/home/juan/kde/src/kexi/src/widget/tableview/KexiTableScrollAreaWidget.cpp:42
#13 0x7f181abf9f88 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f181abb705c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f181abbc516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7f181a80c62b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f181abf2a79 in QWidgetPrivate::sendPaintEvent(QRegion const&) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f181abf30c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f181abf3d6c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f181abf2c31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f181abf3d6c in 

[KScreen] [Bug 350874] After login, my dual head config is stubbornly messed up.

[Michał Walenciak via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350874

--- Comment #6 from Michał Walenciak  ---
I do not reproduce it anymore on KDE: 5.24.0
Anyone confirms?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 365840] git master - Consider reversing order of effect stack in Properties widget: bottom effect is first, top effect is last.

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365840

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Jesse, I found the actual order to be intuitive, but maybe that's because I
consider it to be a list rather than a stack. But then I always liked Casio
calculators, but never HPs. ;)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365346] Screen configuration never restored on startup

[Heiko Tietze via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365346

--- Comment #7 from Heiko Tietze  ---
(In reply to Peter Mattern from comment #6)
> Maybe the OP will drop another note.

Neither arrangement nor resolution was restored well. Plasma adds the trouble
with panels, while LXQt is even worse with background not fitting the original
setup. Meanwhile I found a workaround, namely to configure the montor file in
/etc/X11/xorg.onf/ properly. There are too many issues to track it down, IMHO.
There are enough other bugs open.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

[Daniel Vrátil via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354056

Daniel Vrátil  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED
 CC||dvra...@kde.org

--- Comment #46 from Daniel Vrátil  ---
Closing again as those "problems persist" reports are against a version that
does not contain the bugfix.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 351850] Random crash when having a gmail account setup in kmail

[Daniel Vrátil via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=351850

Daniel Vrátil  changed:

   What|Removed |Added

 CC||steve...@gmail.com

--- Comment #27 from Daniel Vrátil  ---
*** Bug 363390 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 363390] Akonadi randomly crashes

[Daniel Vrátil via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363390

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 351850 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir

[Daniel Vrátil via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353957

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kexi] [Bug 365878] When define search column this is not saved

[Juan José Morales via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365878

--- Comment #3 from Juan José Morales  ---
Hi.

I add the enviroment var that you said and rebuid the app. After that I try the
steps i describe in the bug. FInally when i clicked the Data Tab in the User
table the app crash.

There is some debug info :


QUrl("file:///home/juan/newDataBase.kexi")
filter: ("*.kexi|Proyecto", "basado", "en", "archivos", "de", "base", "de",
"datos", "Kexi", "(*.kexi)\n*|todos", "los", "archivos") path:
"/home/juan/newDataBase.kexi"
appended extension, result: "/home/juan/newDataBase.kexi.kexi"
org.kde.kdb.sqlitedriver: "/home/juan/newDataBase.kexi.kexi"
org.kde.kdb.core: TABLE KDbObject: ID=-1 NAME="kexi__objects" CAPTION=""
DESC=""
 - "o_id" UNSIGNED Integer AUTOINC UNIQUE PKEY NOTNULL NOTEMPTY 
 - "o_type" UNSIGNED Byte 
 - "o_name" Text 
 - "o_caption" Text 
 - "o_desc" LongText   
org.kde.kdb.sqlitedriver: "/home/juan/newDataBase.kexi.kexi"
org.kde.kdb.sqlitedriver: 
org.kde.kdb.core: TABLE KDbObject: ID=-1 NAME="kexi__objects" CAPTION=""
DESC=""
 - "o_id" UNSIGNED Integer AUTOINC UNIQUE PKEY NOTNULL NOTEMPTY 
 - "o_type" UNSIGNED Byte 
 - "o_name" Text 
 - "o_caption" Text 
 - "o_desc" LongText   
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT name FROM sqlite_master WHERE
type='table' AND name LIKE 'kexi__blobs') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE
db_property='kexiproject_major_ver') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE db_property='
kexiproject_major_ver') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE
db_property='kexiproject_minor_ver') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE db_property='
kexiproject_minor_ver') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT name FROM sqlite_master WHERE
type='table' AND name LIKE 'kexi__parts') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT name FROM sqlite_master WHERE
type='table' AND name LIKE 'kexi__userdata') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE
db_property='project_caption') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE db_property='
project_caption') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE
db_property='project_desc') LIMIT 1"
org.kde.kdb.core: !cursor->moveFirst() || cursor->eof()
KDbEscapedString:"SELECT 1 FROM (SELECT 1 FROM kexi__db WHERE db_property='
project_desc') LIMIT 1"
":/icons/breeze/actions/32/document-empty.svg"
"Tag 'img' is not defined in message {<__kuit_internal_top__>  "id"
org.kde.kdb.core: "type" :  ""  ->  "0"
"id" Text
subType strings:  "Text|LongText" 
names:  "Text|Long Text"
subType= 0  type= 11
org.kde.kdb.core: no table specified!
org.kde.kdb.core: no table specified!
-- AFTER: "RECORD DATA (4 COLUMNS):" "0:[]"  "1:[QString]id"  "2:[int]0" 
"3:[]" 
EDIT RECORD ACCEPTED:
SHOW POPUP
QPainter::begin: Cannot paint on an image with the QImage::Format_Indexed8
format
QPainter::setCompositionMode: Painter not active
QMargins(1, 31, 0, 0)
QWidget::setMinimumSize: (verticalHeader/KexiTableScrollAreaHeader) Negative
sizes (20,-1) are not possible
QPainter::begin: Cannot paint on an image with the QImage::Format_Indexed8
format
QPainter::setCompositionMode: Painter not active
QMargins(1, 1, 0, 0)
QPainter::begin: Cannot paint on an image with the QImage::Format_Indexed8
format
QPainter::setCompositionMode: Painter not active
QMargins(1, 1, 0, 0)
QMargins(1, 1, 0, 0)
QMargins(1, 1, 0, 0)
no column relatedData 
 - moving to setData(KDbField &)
added: ' "Text" '
added: ' "Integer Number" '
added: ' "Floating Point Number" '
added: ' "Yes/No" '
added: ' "Date/Time" '
added: ' "Object" '
destroying old data (owned)
QWidget::setMinimumSize: (verticalHeader/KexiTableScrollAreaHeader) Negative
sizes (18,-1) are not possible
QWidget::setMinimumSize: (verticalHeader/KexiTableScrollAreaHeader) Negative
sizes (18,-1) are not possible
QMargins(1, 1, 0, 0)
HIDE!!!
subType strings:  "Byte|ShortInteger|Integer|BigInteger" 
names:  "Byte|Short Integer Number|Integer Number|Big Integer Number"
QVariant(QString, "Text")
"type"  =  QVariant(int, 3)  (oldvalue =  QVariant(int, 11) )
"Modificada la propiedad «type» del campo de la tabla de «11» a «3» (UID=1)"
"subType"  =  QVariant(QString, "Integer")  (oldvalue =  QVariant(Invalid) )
"Modificada la propiedad «subType» del campo de la tabla de «» 

[Akonadi] [Bug 363928] After suspend akonadiserver use about 2 cpus

[Daniel Vrátil via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363928

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #5 from Daniel Vrátil  ---
I see only one active thread in middle of an SQL query execution, could easily
be a full sync after reconnecting to network after resume from suspend.

How long does it get stuck in such state? It is possible that during the
suspend large portions of the database pages get swapped out of memory and then
the query takes a very long time as the database needs to load everything from
the disk again...

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds

[Till Schäfer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363741

--- Comment #16 from Till Schäfer  ---
by why does a mysql schema drop/create helps in this case?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds

[Daniel Vrátil via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363741

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||dvra...@kde.org
 Ever confirmed|0   |1

--- Comment #15 from Daniel Vrátil  ---
Please try removing content of ~/.local/share/akonadi/search_db and
~/.local/share/baloo/{calendars,collections,contacts,email,emailContacts,notes}
(if if exists)

This unfortunately is Xapian crashing on its own (probably corrupted) database,
something that is currently out of our control.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361151] (Enhancement) Implement changing the mouse acceleration profile of libinput in Wayland.

[Bernd Steinhauser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361151

Bernd Steinhauser  changed:

   What|Removed |Added

 CC||li...@bernd-steinhauser.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 350688] Mouse acceleration setting has no effect with libinput

[Bernd Steinhauser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350688

Bernd Steinhauser  changed:

   What|Removed |Added

 CC||li...@bernd-steinhauser.de

--- Comment #8 from Bernd Steinhauser  ---
The kcm only supports evdev.

Now that libinput (and xf86-input-libinput) or getting pretty much standard,
sooner or later support for this will be implemented, I guess.
Especially since libinput is now claimed as being complete (for the moment).
See bug 361151 as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365913] in crash

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365913

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
welcome to the show, update to Qt 5.6 asap

*** This bug has been marked as a duplicate of bug 341497 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #66 from Thomas Lübking  ---
*** Bug 365913 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365913] New: in crash

[Rafis Kamaliev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365913

Bug ID: 365913
   Summary: in crash
   Product: kwin
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ra...@pisem.net

Application: kwin_x11 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.27-24-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: turn on PC from hibernation,
screen have some colour cubes on black before

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0ecb6ea800 (LWP 1955))]

Thread 5 (Thread 0x7f0ea8f24700 (LWP 1977)):
#0  0x7fffaf9d3b26 in clock_gettime ()
#1  0x7f0ecb07fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f0ec8d1f7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f0ec8e9f3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f0ec8e9e7a3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#5  0x7f0ec8e9ef3b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f0ec8e47d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f0ec8c6961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f0ec316be18 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f0ec8c6e32f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f0eca69f0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f0ecb07302d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f0ea27fd700 (LWP 1997)):
#0  0x7f0eca6a303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0ec7bf186b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f0ec7bf1899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f0eca69f0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0ecb07302d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f0ea37ff700 (LWP 9139)):
#0  0x7f0eca6a303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0ec8c6f34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f0ec385f1cb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f0ec385f663 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f0ec8c6e32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f0eca69f0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0ecb07302d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f0e09c64700 (LWP 12739)):
#0  0x7f0eca6a303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0ec8c6f34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f0ec385f1cb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f0ec385f663 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f0ec8c6e32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f0eca69f0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0ecb07302d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f0ecb6ea800 (LWP 1955)):
[KCrash Handler]
#6  0x7f0ec93c21a0 in QScreen::refreshRate() const () at
/usr/lib64/libQt5Gui.so.5
#7  0x7f0ec385fb1f in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f0ec385fc8f in  () at /usr/lib64/libQt5Quick.so.5
#9  0x7f0ec8e79cc6 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f0ec8c4708e in QUnifiedTimer::startAnimationDriver() () at
/usr/lib64/libQt5Core.so.5
#11 0x7f0ec8c488ca in QUnifiedTimer::startTimers() () at
/usr/lib64/libQt5Core.so.5
#12 0x7f0ec8e7aac6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#13 0x7f0ec9b2de7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#14 0x7f0ec9b32cc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#15 0x7f0ec8e49e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#16 0x7f0ec8e4c057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#17 0x7f0ec8e9eec4 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#18 0x7f0eb156e33d in  () at /usr/lib64/libQt5XcbQpa.so.5
#19 0x7f0ec8e47d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#20 0x7f0ec8e4f8f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#21 0x7f0ecb33b9e7 in kdemain () at /usr/lib64/libkdeinit5_kwin_x11.so
#22 0x7f0ecafafb25 in __libc_start_main () at /lib64/libc.so.6
#23 0x0040085e in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You 

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #30 from Jesse  ---
Sounds good. I'll keep checking and report after testing the updates.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #29 from Jean-Baptiste Mardelle  ---
Oh, yes sorry I forgot to check the upload status... update should then be
available whenever launchpad decides it.. probably something between 30 minutes
and 2 hours...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #28 from Jesse  ---
Created attachment 100219
  --> https://bugs.kde.org/attachment.cgi?id=100219=edit
Screenshot of current ppa:kdenlive/kdenlive-master packages on website

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #27 from Jesse  ---
Hmmm, nothing in the update manager, yet. I checked the website, and there's a
green gear instead of a check mark near the MLT packages that were built 17
minutes ago. Hovering over it shows the tooltip "All packages were successfully
built but have not yet been published."

I'm also attaching a screenshot of the page.

Should I download all of the packages manually and install? Will that mess up
anything once the ppa publishes any further updates?

-- 
You are receiving this mail because:
You are watching all bug changes.

[rsibreak] [Bug 362082] Can't save welcome message skip

[Michael Palimaka via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362082

Michael Palimaka  changed:

   What|Removed |Added

 CC||kensing...@gentoo.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365824] krunner, launcher and applet windows just blink and won't show up

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365824

--- Comment #8 from Thomas Lübking  ---
Please check against the xrender compositor, but

> if I minimize all running apps (empty desktop) it works and the calendar is 
> shown as expected

really makes me believe it's the window type juggling, notably since only QML
clients seem affected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #26 from Jean-Baptiste Mardelle  ---
Update should be available from PPA now, please test.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 353099] git master (reopened) - When project playback reaches near end of timeline, pause function becomes unresponsive

[Jean-Baptiste Mardelle via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353099

--- Comment #6 from Jean-Baptiste Mardelle  ---
Git commit 244c700295b5b6b92a8e33b4f75f6de785ddeb45 by Jean-Baptiste Mardelle.
Committed on 20/07/2016 at 20:24.
Pushed by mardelle into branch 'Applications/16.08'.

Fix cannot pause near end of clip regression

M  +1-0src/mainwindow.cpp
M  +1-1src/monitor/monitor.cpp
M  +1-1src/monitor/monitor.h
M  +1-1src/renderer.cpp
M  +1-1src/timeline/customtrackview.cpp
M  +1-0src/timeline/customtrackview.h

http://commits.kde.org/kdenlive/244c700295b5b6b92a8e33b4f75f6de785ddeb45

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365824] krunner, launcher and applet windows just blink and won't show up

[altosch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365824

--- Comment #7 from altosch  ---
Correction: krunner still doesn't work. It behaves like I described before.
Just blinks and nothing more.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 365912] ppc64BE segfault during jm-insns test (RELRO)

[Will Schmidt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365912

--- Comment #1 from Will Schmidt  ---
Created attachment 100217
  --> https://bugs.kde.org/attachment.cgi?id=100217=edit
proposed patch

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 365716] Digital clock display is missing digits

[Bob Wya via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365716

--- Comment #3 from Bob Wya  ---
Created attachment 100218
  --> https://bugs.kde.org/attachment.cgi?id=100218=edit
KDE Plasma 5.7.2 panel - digital clock - missing digits

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #25 from Jesse  ---
No sweat. I'll be standing by. :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kphotoalbum] [Bug 365873] When playing jpg's and mpeg's in Slideshow, the whole program exits without warning.

[Johannes Zarl-Zierl via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365873

Johannes Zarl-Zierl  changed:

   What|Removed |Added

 CC||johan...@zarl-zierl.at

--- Comment #1 from Johannes Zarl-Zierl  ---
What exactly do you mean by "the software just exits"?
Does it crash? Is there a window after exit that says something like "Sorry,
the program kphotoalbum closed unexpectedly"?

Does this always happen on the last mpeg file, regardless of which files you
are viewing, or does it happen on the same video file?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365824] krunner, launcher and applet windows just blink and won't show up

[altosch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365824

--- Comment #6 from altosch  ---
Yes, that was it. I switched to OpenGL 2 and the problem is gone.

The setting is here: System Settings / Display / Compositor / Rendering backend
/ OpenGL2.0
Then I wanted to log out and log in to apply change but Plasma got frozen (just
black screen and mouse cursor) so I had to restart the sddm service from
console.

Thank you for your help.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 365912] ppc64BE segfault during jm-insns test (RELRO)

[Will Schmidt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365912

Will Schmidt  changed:

   What|Removed |Added

 CC||c...@us.ibm.com,
   ||will_schm...@vnet.ibm.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 365912] New: ppc64BE segfault during jm-insns test (RELRO)

[Will Schmidt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365912

Bug ID: 365912
   Summary: ppc64BE segfault during jm-insns test (RELRO)
   Product: valgrind
   Version: 3.12 SVN
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: will_schm...@vnet.ibm.com

When running the valgrind tests, the jm-insns test is segfaulting when it
attempts to patch instructions as it deals with the ppc64 (BE) function
descriptor.  
This is actually due to the RELRO option being enabled by default for the ppc64
(BE) platform, per an upstream binutils change. 
Patch to follow.




Reproducible: Always

Steps to Reproduce:
1.  Build and run valgrind regression test on ppc64 platform with new binutils
installed
2.  specifically run the test  " none/tests/ppc64/jm-insns -f "
3.  see it segfault.

Actual Results:  
...
PPC float load insns
with one register + one 16 bits immediate args with flags update:

Program received signal SIGSEGV, Segmentation fault.
...


Expected Results:  
...
All done. Tested 77 different instructions


Patch to disable the relro option for the jm-insns test to follow momentarily.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma4] [Bug 285603] xrandr --scale as option Settings/Display and Monitor for laptops

[Jos van den Oever via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=285603

Jos van den Oever  changed:

   What|Removed |Added

 CC||j...@vandenoever.info

--- Comment #1 from Jos van den Oever  ---
The dialog 'Display and Monitor' from 'System Settings' has an option 'Scale
Display' that allows you to scale up for use on high resolution displays. There
is no option to scale down: the slider has magnification factors from 1 to 3,
but not lower than 1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #24 from Jean-Baptiste Mardelle  ---
A few hours ago, I just fixed a huge memleak in the qtblend transition. That
might be the cause for your slowdown. I have pushed the fix to MLT git master
but for some reason the build fails on our PPA so it has not been updated, I am
trying to fix this... will let you know when the fix is in PPA

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361360

--- Comment #23 from Jesse  ---
Further investigation shows that this is only apparent on one of my other
workstations, with the only real difference between it and the others are that
it has two Nvidia GTX660's in it, where the others have two Nvidia GTX970ti's
and 980ti's. The machine with the 660's in it is also having the problem of
layouts not properly loading at start-up, where the others don't. They're both
running the Nvidia 361.42 proprietary driver (as it's needed to utilize the GPU
for programs like Blender).

Could the graphics card be the issue? Is it possible there's some
incompatibility between Kdenlive and older graphics cards?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 365911] New: Krunner crash. (Maybe Resume related)

[Tilman Keskinöz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365911

Bug ID: 365911
   Summary: Krunner crash. (Maybe Resume related)
   Product: krunner
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: til...@arved.at

Application: krunner (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-31-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Resumed Laptop. Alt+F2 to start krunner. Application crashed.

- Unusual behavior I noticed:

thunderbird had lost its fonts after resume, so i closed it and wanted to
restart it via krunner.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2df3e068c0 (LWP 19377))]

Thread 19 (Thread 0x7f2d8affd700 (LWP 20749)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2df0f56aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3049aa0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x264b400,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f2dca4a42bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f2dca4a84e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f2dca4a346d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f2dca4a8542 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f2dca4a346d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f2dca4a6353 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f2df0f5584e in QThreadPrivate::start (arg=0x7f2d84002990) at
thread/qthread_unix.cpp:331
#10 0x7f2deeaaa6fa in start_thread (arg=0x7f2d8affd700) at
pthread_create.c:333
#11 0x7f2df0866b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7f2d8b7fe700 (LWP 20748)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2df0f56aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3049aa0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x264b400,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f2dca4a42bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f2dca4a84e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f2dca4a346d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f2dca4a8542 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f2dca4a346d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f2dca4a8542 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f2dca4a346d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f2dca4a6353 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f2df0f5584e in QThreadPrivate::start (arg=0x7f2d8c003190) at
thread/qthread_unix.cpp:331
#12 0x7f2deeaaa6fa in start_thread (arg=0x7f2d8b7fe700) at
pthread_create.c:333
#13 0x7f2df0866b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f2d8bfff700 (LWP 20747)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2df0f56aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3049aa0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x264b400,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f2dca4a42bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f2dca4a84e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f2dca4a346d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  

[kde] [Bug 365910] New: Adjust Date and Time applet crash following suspend-resume cycle

[Bob Wya via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365910

Bug ID: 365910
   Summary: Adjust Date and Time applet crash following
suspend-resume cycle
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bob.mt@gmail.com

Application: kcmshell5 (5.7.2)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.24.0
Operating System: Linux 4.6.4-zen x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
Updated Gentoo to Plasma 5.7.2
Unable to access Date and Time settings from Digital Clock in panel (on either
dual-display)...
Unable to restart the Date and Time settings applet (crash dialog simply
reappears).
Digital Clock also missing digits from clock face (not date) on one display
(internal laptop display). Possibly unrelated??

Nvidia proprietary drivers 367.35 on a Geforce GTX 970M.

Backtrace attached.

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efef74817c0 (LWP 21943))]

Thread 5 (Thread 0x7efed214c700 (LWP 21947)):
#0  0x7efef6f8d37d in poll () from /lib64/libc.so.6
#1  0x7efef060f00c in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7efef060f392 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x7efed2c36a26 in gdbus_shared_thread_func () from
/usr/lib64/libgio-2.0.so.0
#4  0x7efef0635825 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0
#5  0x7efef262d424 in start_thread () from /lib64/libpthread.so.0
#6  0x7efef6f963fd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7efed294d700 (LWP 21946)):
#0  0x7efef0653759 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7efef060eff2 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7efef060f11c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7efef060f159 in glib_worker_main () from /usr/lib64/libglib-2.0.so.0
#4  0x7efef0635825 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0
#5  0x7efef262d424 in start_thread () from /lib64/libpthread.so.0
#6  0x7efef6f963fd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7efeddca1700 (LWP 21945)):
#0  0x7efef6f8d37d in poll () from /lib64/libc.so.6
#1  0x7efef060f00c in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7efef060f11c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7efef4ef8ebb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7efef4ea01ba in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7efef4cdd88b in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7efef7588c08 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7efef4ce32ad in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7efef262d424 in start_thread () from /lib64/libpthread.so.0
#9  0x7efef6f963fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7efee6885700 (LWP 21944)):
#0  0x7efef6f8d37d in poll () from /lib64/libc.so.6
#1  0x7efef2c658f2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7efef2c67707 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7efee941dbf9 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7efef4ce32ad in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7efef262d424 in start_thread () from /lib64/libpthread.so.0
#6  0x7efef6f963fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7efef74817c0 (LWP 21943)):
[KCrash Handler]
#6  0x7efef6ee02f8 in raise () from /lib64/libc.so.6
#7  0x7efef6ee174a in abort () from /lib64/libc.so.6
#8  0x7efef4ccb9e9 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib64/libQt5Core.so.5
#9  0x7efef7587f88 in
QDBusArgumentPrivate::checkRead(QDBusArgumentPrivate*) [clone .part.27] () from
/usr/lib64/libQt5DBus.so.5
#10 0x7efef75d6428 in
QDBusArgumentPrivate::checkReadAndDetach(QDBusArgumentPrivate*&) () from
/usr/lib64/libQt5DBus.so.5
#11 0x7efef75d93e9 in QDBusArgument::beginMapEntry() const () from
/usr/lib64/libQt5DBus.so.5
#12 0x7efed33576b2 in PolkitQt1::Authority::Private::init() () from
/usr/lib64/libpolkit-qt5-core-1.so.1
#13 0x7efed3358051 in PolkitQt1::Authority::Authority(_PolkitAuthority*,
QObject*) () from /usr/lib64/libpolkit-qt5-core-1.so.1
#14 0x7efed3358312 in PolkitQt1::Authority::instance(_PolkitAuthority*) ()
from /usr/lib64/libpolkit-qt5-core-1.so.1
#15 0x7efed35d05fa in KAuth::Polkit1Backend::Polkit1Backend() () from

[digikam] [Bug 365907] digikam timestamp not updated after use of Adjust Time

[Kristian via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365907

--- Comment #8 from Kristian  ---
You're right, thank you for clarification. Which makes me point over to bug
365876. I think, the new behaviour with the BQM is absolutely not
user-friendly.

-- 
You are receiving this mail because:
You are watching all bug changes.