[plasma-integration] [Bug 369319] New: Black screen in Plasma Wayland session

[Daniel via KDE Bugzilla]

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

Bug ID: 369319
   Summary: Black screen in Plasma Wayland session
   Product: plasma-integration
   Version: 5.7.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: dah1...@gmail.com

Created attachment 101278
  --> https://bugs.kde.org/attachment.cgi?id=101278=edit
File .wayland-errors

Unsure if it is a plasma-integration or a kwin issue, so forgive me if I am
mistaken.

I'm running KDE Neon up to date, my graphic card is an old nVidia GeForce 7100.
I had to setup nouveau.noaccel=1 at grub, because otherwise Plasma/Kwin freezes
and must do a hard reset (in every LiveDVD I have tried: KaOS, KDE Neon, Gecko
Linux, Manjaro...)

 When I try to start a Plasma Wayland session, all I can see is a black screen
with just the mouse pointer (which I can move). Alt+F2 does not work (either).
When changing to a tty (Ctrl+Alt+F2, i.e.), it seems that for fraction of a
second I can see the desktop, but when going back to Ctrl+Alt+F7 everything is
black with just the mouse pointer. 

Below some information I think can be useful (there is no crash, so I can't
attach a crash-report):

daniel@pc-medion:~$ lspci | grep VGA
00:10.0 VGA compatible controller: NVIDIA Corporation C73 [GeForce 7100 /
nForce 630i] (rev a2)

daniel@pc-medion:~$ kwin --version
kwin 5.7.5

daniel@pc-medion:~$ kwin_wayland --version
kwin 5.7.5

daniel@pc-medion:~$ glxinfo | grep GLX
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read
Extended renderer info (GLX_MESA_query_renderer):
240 GLX Visuals
300 GLXFBConfigs:

daniel@pc-medion:~$ modinfo nouveau
filename:  
/lib/modules/4.4.0-38-generic/kernel/drivers/gpu/drm/nouveau/nouveau.ko
license:GPL and additional rights
description:nVidia Riva/TNT/GeForce/Quadro/Tesla
author: Nouveau Project
srcversion: F12E920A89ED6A8476981A9
alias:  pci:v12D2d*sv*sd*bc03sc*i*
alias:  pci:v10DEd*sv*sd*bc03sc*i*
depends:drm,drm_kms_helper,ttm,mxm-wmi,wmi,video,i2c-algo-bit
intree: Y
vermagic:   4.4.0-38-generic SMP mod_unload modversions 
parm:   tv_norm:Default TV norm.
Supported: PAL, PAL-M, PAL-N, PAL-Nc, NTSC-M, NTSC-J,
hd480i, hd480p, hd576i, hd576p, hd720p, hd1080i.
Default: PAL
*NOTE* Ignored for cards with external TV encoders. (charp)
parm:   vram_pushbuf:Create DMA push buffers in VRAM (int)
parm:   nofbaccel:Disable fbcon acceleration (int)
parm:   tv_disable:Disable TV-out detection (int)
parm:   ignorelid:Ignore ACPI lid status (int)
parm:   duallink:Allow dual-link TMDS (default: enabled) (int)
parm:   pstate:enable sysfs pstate file, which will be moved in the
future (int)
parm:

[kmail2] [Bug 322126] emails get filtered twice and thus duplicated in kmail2

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de
Version|4.10.5  |5.1
 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #11 from Denis Kurz  ---
Hussam, thank you for your feedback.

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

[Akonadi] [Bug 299422] Akonadi failed to set SEEN flag and move letters with (at least) imap and git resources.

[mva]

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

Vadim A. Misbakh-Soloviov (mva)  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #11 from Vadim A. Misbakh-Soloviov (mva)  ---
Since there is no git resource, that ported to KF5 anymore, I can test only on
IMAP.

And, as far as I can see, it working pretty fine for now.

Although, when I reported that buf I had something about 200k+ letters in Inbox
and something about 30-70k in some another folders. Since then I already
archived many of that mail. And with current amounts I don't experience that
bug anymore.

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

[Akonadi] [Bug 327370] CalDAV / ownCloud reminders not showing on login if the machine was off at the start time.

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de
Version|4.11|5.1.3
 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---

--- Comment #6 from Denis Kurz  ---
Florian, thank you for your feedback.

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

[kmail2] [Bug 335117] Information leak when using GPG on Bcc recipients

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
Version|5.2.1   |5.2.3
 Status|NEEDSINFO   |CONFIRMED

--- Comment #4 from Denis Kurz  ---
Thanks for your feedback, Dominik.

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

[kdenlive] [Bug 369295] Error exporting when use Key Spill Mop Up filter

[Jerome BAPTISTE via KDE Bugzilla]

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

--- Comment #2 from Jerome BAPTISTE  ---
I am using this version
16.08.1~ubuntu16.04.1
LP-PPA-kdenlive-kdenlive-stable

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

[konsole] [Bug 369370] New: CJK character is rendered with its lower half cutted

[CDnX via KDE Bugzilla]

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

Bug ID: 369370
   Summary: CJK character is rendered with its lower half cutted
   Product: konsole
   Version: 15.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: ruby3...@gmail.com

(tested in Korean and Japanese, on locale ko_KR.UTF-8)

Reproducible: Always

Steps to Reproduce:
1. Input CJK characters.

Actual Results:  
characters are cutted in half.

Expected Results:  
full character should be rendered.

using kde lts 16.04.1

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

[kmail2] [Bug 331946] kmail2 4.12.3 crash after moving a big folder to another one ( imap )

[Bruno Friedmann via KDE Bugzilla]

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

Bruno Friedmann  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Bruno Friedmann  ---
Tested on 16.08.1 seems to work with big folders on the same imap account.

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

[kmail2] [Bug 298001] wallet request pops up on a different display than kmail2 is running on

[Christopher Heiny via KDE Bugzilla]

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

--- Comment #3 from Christopher Heiny  ---
I gave up on Kmail about a year and a half ago.  As far as I'm concerned, you
can close this bug.

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

[kmail2] [Bug 302277] Email stuck in outbox

[Christopher Heiny via KDE Bugzilla]

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

--- Comment #4 from Christopher Heiny  ---
I gave up on Kmail about a year and a half ago.  As far as I'm concerned, you
can close this bug.

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

[kmail2] [Bug 314783] slow IMAP connection hogs the preview pane

[Michi via KDE Bugzilla]

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

--- Comment #4 from Michi  ---
(In reply to Denis Kurz from comment #3)
this still exists.
Generally, this is the case after a lost network connection (e.g. after the
computer went into sleep mode).

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

[Akonadi] [Bug 327370] CalDAV / ownCloud reminders not showing on login if the machine was off at the start time.

[Florian E . J . Fruth via KDE Bugzilla]

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

--- Comment #5 from Florian E.J. Fruth  ---
This bug still exists for KOrganizer 5.1.3 with KDE Frameworks 5.23.0 on Ubuntu
16.04.1. I can't tell how this corresponds to the "KDE Applications 15.08 or
later"-Version.
IMHO Korganizer (or Akonadi) needs to update the calender before showing the
reminders to get this right. It seams to only show the reminders that were
present on shutdown.

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

[krita] [Bug 369308] New: UX issues with the startup splash screen / about dialog

[via KDE Bugzilla]

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

Bug ID: 369308
   Summary: UX issues with the startup splash screen / about
dialog
   Product: krita
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: alvinhoc...@gmail.com

1. When Krita is still loading, the splash screen is unresponsive and links and
recent files are non-functional. On Windows, attempts at clicking on the window
can cause the "unresponsive program" dialog to show, And if the user does
attempt to click on the links, the clicks might still be registered after Krita
has finished loading.

This appears to me as bad UX. "Unclickable" UI elements that appears to be
clickable are bad, users may attempt to click on them but to receive no
response, or even worse, a response after a long period.

The easy way would be to hide the links portions while Krita is still loading.
Even though the splash screen would still be unresponsive, users would normally
not interact with it and should not trigger the "unresponsive program" dialog.

2. The splash screen doesn't close when pressing `Esc`. I would expect users to
expect this to work.

3. The about dialog uses the same UI widget as the splash screen, which shows
the "Recent Files" links. Those seems weird to be on the about dialog, so I
would suggest hiding them in the about dialog.

Reproducible: Always

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

[krita] [Bug 369306] New: Unfocusing the window then drawing at the canvas yields no pressure detection or smoothing at the initial stroke.

[Phoenix Enero via KDE Bugzilla]

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

Bug ID: 369306
   Summary: Unfocusing the window then drawing at the canvas
yields no pressure detection or smoothing at the
initial stroke.
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: phoenix.en...@gmail.com

Trying to draw after putting the window out of focus yields no pressure
detection or smoothing at the initial brush stroke. Subsequent brush strokes
work normally.

Reproducible: Always

Steps to Reproduce:
1. Open any document or create a new one.
2. Place the Krita window out of focus. You can do this by clicking anywhere
outside the Krita window.
3. Draw a brush stroke in the Krita canvas.

Actual Results:  
Brush stroke looks ragged with no pressure detection at all.

Expected Results:  
Brush stroke has pressure detection and is stabilized (this may vary between
different brushes.)

Tablet I'm using is HUION H610 Pro.

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

[Breeze] [Bug 369307] Wrong find command in file validate_svg.sh

[Alexander Reinholdt via KDE Bugzilla]

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

--- Comment #1 from Alexander Reinholdt  ---
Created attachment 101269
  --> https://bugs.kde.org/attachment.cgi?id=101269=edit
Patch that fixes the described failure

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

[Breeze] [Bug 369307] New: Wrong find command in file validate_svg.sh

[Alexander Reinholdt via KDE Bugzilla]

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

Bug ID: 369307
   Summary: Wrong find command in file validate_svg.sh
   Product: Breeze
   Version: 5.7.95
  Platform: Other
OS: FreeBSD
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: alexander.reinho...@kdemail.net
CC: kain...@gmail.com

When compiling from source under FreeBSD using ports with the plasma5 branch
from area51 merged, compilation of the package breeze-icons fails with an
'illegal command' error, due to a wrong find command line in the
validate_svg.sh file. (See additional information section for a patch.)

Reproducible: Always

Steps to Reproduce:
Compile breeze-icons from source under FreeBSD.

Actual Results:  
Fails with an 'illegal command' error.

Expected Results:  
Compiles successfully.

The following patch fixes the problem:

diff --git a/validate_svg.sh b/validate_svg.sh
index bbc3076..adaf26f 100644
--- a/validate_svg.sh
+++ b/validate_svg.sh
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash

-find -name '*.svg' -exec xmllint --noout {} + 2> xmlerrors
+find . -name '*.svg' -exec xmllint --noout {} + 2> xmlerrors
 if [ -s xmlerrors ]; then
 cat xmlerrors
 rm xmlerrors

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Thomas Schmitt via KDE Bugzilla]

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

--- Comment #45 from Thomas Schmitt  ---
Hi.

a summary of the winded road which brought me to the current diagnosis.

After my theory of lack of multi-session support on overwritable media
brought us to the code where this support is already implemented, i first
thought it was only about a missing media type in the list of overwritables.

But the code for detection of BD-R in POW state made it clear that i
misinterpreted the list of overwritables in growisofs. The growisofs list
does not contain BD-R POW (profile 0x41 + feature 0x38) but rather
BD-R RRM (profile 0x42), which is still missing in K3B's list.

Since growisofs does not format BD-R to RRM by default, there had to be
a different deviation of K3B's determination of Next Writable Address
from growisofs method of determination.
I found this deviation when comparing K3b::...::getNextWritableAdress()
with plusminus_r_C_parm() in growisofs_mmc.cpp.


Discovered problems along that road:

Obviously the K3B code to predict growisofs decisions was not completely
updated after growisofs introduced support for BD media. One would possibly
have to compare all media related gestures with those of growisofs.
(I compared the computation of lastSessionStart for BD-R POW and found
it correct. But other aspects may still offer pitfalls.)

One known deviation is the difference between the list of overwritables
in growisofs (DVD+RW, DVD+RW DL, formatted DVD-RW, DVD-RAM, BD-R RRM,
and BD-RE) to the ones in K3B (MEDIA_DVD_PLUS_RW, MEDIA_DVD_PLUS_RW_DL,
MEDIA_DVD_RW_OVWR, MEDIA_BD_RE).

I.e. DVD-RAM and BD-R RRM are missing in the K3B list of overwritables.

It seems essential that both programs use the same list.


Have a nice day :)

Thomas

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

[plasmashell] [Bug 369309] New: App Dashoard doesn't follow system color scheme

[郭云鹤]

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

Bug ID: 369309
   Summary: App Dashoard doesn't follow system color scheme
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Dashboard
  Assignee: notm...@gmail.com
  Reporter: guoyunhebr...@gmail.com
CC: bhus...@gmail.com

By default, KDE uses a light color scheme, light background and dark symbols.
However, the full screen App Dashboard always use dark background. Thus, dark
symbol icons are hard to identify in such a dark background. See screenshot in
attachment.

Hope that App Dashboard uses system color scheme for background and text color.
So that when color scheme is changing, symbols/icons are always clear.

Reproducible: Always

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

[kmail2] [Bug 130959] kmail reply sender identity does not honour folder's sender identity

[Peter Lewis via KDE Bugzilla]

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

Peter Lewis  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #7 from Peter Lewis  ---
I can confirm that in 4.14 the reply identity recognises the send identity of
the folder so the bug has been resolved.

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

[plasmashell] [Bug 369309] App Dashoard doesn't follow system color scheme

[郭云鹤]

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

--- Comment #1 from Guo Yunhe (郭云鹤)  ---
Created attachment 101270
  --> https://bugs.kde.org/attachment.cgi?id=101270=edit
Screenshot

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

[kmail2] [Bug 296561] kmail2 loses POP3 incoming mails

[Christopher Heiny via KDE Bugzilla]

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

--- Comment #8 from Christopher Heiny  ---
I gave up on Kmail about a year and a half ago.  As far as I'm concerned, you
can close this bug.

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

[akregator] [Bug 163573] Akregator crashed while clicking an article title

[Christopher Heiny via KDE Bugzilla]

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

--- Comment #36 from Christopher Heiny  ---
I no longer experience this issue as of Akregator > 4.14.

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

[korganizer] [Bug 257723] Invitation replies are always sent immediately

[Michi via KDE Bugzilla]

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

--- Comment #13 from Michi  ---
(In reply to Denis Kurz from comment #12)
it's even worse now. The only action shown in an invitation now is "check my
calender" which only opens the korganizer; I would expect to see a marker where
the event would be, but see nothing.

but back to the original problem, since I can't reply at all, there's no way
how "replies are always sent immediately" - bug resolved ;-)

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

[krita] [Bug 369305] Color picking alternate invocation gets stuck when un-focusing the Krita window

[Phoenix Enero via KDE Bugzilla]

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

--- Comment #1 from Phoenix Enero  ---
Forgot to add: The tablet I'm using is HUION H610 Pro.

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

[Akonadi] [Bug 310037] updated events have mangled date information

[Michi via KDE Bugzilla]

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

--- Comment #2 from Michi  ---
as you can see here https://bugs.kde.org/show_bug.cgi?id=257723#c13, the whole
invitation handling is broken, I can't verify whether the problem still exists.
I can't even add an invitation to my calender in the first place.

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

[Akonadi] [Bug 328025] Moving read mail ends up in 'new' directory instead of 'cur' directory

[Patrick via KDE Bugzilla]

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

Patrick  changed:

   What|Removed |Added

Version|4.11|16.08

--- Comment #2 from Patrick  ---
This bug is still reproducible in akonadi 16.08.

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

[Akonadi] [Bug 318913] CPU consumption too high

[LtWorf]

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

--- Comment #3 from Salvo "LtWorf" Tomaselli  ---
I gave up on akonadi, I think it's beyond fixing and I moved on to a mail
client that can receive and send mails.

So, feel free to close all the bugs I opened because I won't be trying to
reproduce them.

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

[konsole] [Bug 369370] CJK character is rendered with its lower half cutted

[CDnX via KDE Bugzilla]

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

--- Comment #1 from CDnX  ---
Created attachment 101292
  --> https://bugs.kde.org/attachment.cgi?id=101292=edit
captured with ascii and CJK characters.

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

--- Comment #8 from Lastique  ---
(In reply to Christophe Giboudeaux from comment #7)
> file_db_data should only contain directories nowadays. run 'akonadictl fsck'
> and check if you still have files inside.

Thanks, 'akonadictl fsck' removed the files from file_db_data. It didn't fix
syncing though.

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

[plasmashell] [Bug 369192] fail to load thumbnail of the windows content

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
Version|5.0.0   |5.7.95
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #4 from Christoph Feck  ---
Thanks for the update.

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

[Discover] [Bug 369323] New: Discover 5.8 Beta requires unreleased kirigami version

[Fabian Vogt via KDE Bugzilla]

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

Bug ID: 369323
   Summary: Discover 5.8 Beta requires unreleased kirigami version
   Product: Discover
   Version: 5.7.95
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: fab...@ritter-vogt.de

With kirigami 1.0.2, plasma-discover segfaults on start:

QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:119 Type DiscoverDrawer unavailable
qrc:/qml/DiscoverDrawer.qml:90 Kirigami.Separator is not a type

org.kde.kirigami.Separator got introduced 20 days ago and is so far only in git
master.

Reproducible: Always

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

[Akonadi] [Bug 298962] Kmail sometimes causes emails from an IMAP folder to be blank and also wipes them out in the IMAP folder

[Frederick Zhang via KDE Bugzilla]

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

--- Comment #19 from Frederick Zhang  ---
Hi Denis,

I've got 4 accounts in my Kmail and this just happens from time to time (approx
1 out of 10 boots I will bump into this issue), and I have to reboot my machine
to fix it...

...but yes, it seems that this is a quite different from the description. I
deem that I've seen a similar issue here and this should be the reply to a
wrong thread however I can't find it...

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

[krita] [Bug 369306] Unfocusing the window then drawing at the canvas yields no pressure detection or smoothing at the initial stroke.

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
I am not sure we can fix this, I am afraid. I am a little curious though, why
is the window unfocussing mid-stroke for you?

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
There is no translation yet.

Handbook is huge and so far to be finalized. The translations take time and as
we cut the large docbook files in small parts, translator needs to adjust
translations workflow.

So the handbook translations will be include in tarball in the far future.

Gilles Caulier

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

[kcron] [Bug 369314] I cant execute actions manually, in Spanish (ejectuar ahora)

[Burkhard Lueck via KDE Bugzilla]

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

Burkhard Lueck  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Burkhard Lueck  ---
confirmed in master compiled from sources
output of "Run now" action starting systemseetings in a terminal says
"Unknown option 'c'."

Using kcron version 5.0 in kbuntu 16.04.1 LTS with 
Frameworks 5.23.0, Plasma 5.6.5 and Applications 15.12.3 
"Run now" action works for me

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

[plasma-nm] [Bug 366164] Plasmashell crash when plasma-nm applet exists trying to connect to a VPN

[via KDE Bugzilla]

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

k...@pcfe.net changed:

   What|Removed |Added

 CC||k...@pcfe.net

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

[kdialog] [Bug 369216] kdialog path parsing regression

[Burkhard Lueck via KDE Bugzilla]

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

--- Comment #3 from Burkhard Lueck  ---
Christoph is right here, using his examples I have the same issue

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

[kontact] [Bug 369329] New: Kmail and consequently Kontact crash

[Johannes Kehrer via KDE Bugzilla]

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

Bug ID: 369329
   Summary: Kmail and consequently Kontact crash
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: j...@gmx.de

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
The emails in kmail were shown. Whenever (always) I click on a (HTML) message
kmail and kontact crash.
It seems that it tries to show this message, but the crash happens.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5dd58b4600 (LWP 3239))]

Thread 34 (Thread 0x7f5c81bf0700 (LWP 3357)):
#0  0x7f5dcd4efea0 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5dcd4aa82a in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5dcd4aa98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5dd2d8eaab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5dd2d366fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5dd2b5c3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f5dd2b612e8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f5dce0fd454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f5dd22583ff in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f5c836aa700 (LWP 3329)):
#0  0x7f5dd224b75d in read () at /lib64/libc.so.6
#1  0x7f5dcd4eeae0 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5dcd4aa325 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5dcd4aa814 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f5dcd4aa98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f5dd2d8eaab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f5dd2d366fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f5dd2b5c3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f5dd2b612e8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f5dce0fd454 in start_thread () at /lib64/libpthread.so.0
#10 0x7f5dd22583ff in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f5c888c5700 (LWP 3307)):
#0  0x7f5dce10310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5dc5883d49 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f5dc5884460 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f5dc5884630 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f5dc588123d in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f5dce0fd454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5dd22583ff in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f5c8b1e8700 (LWP 3288)):
#0  0x7f5dcd4efe89 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5dcd4a98a4 in g_main_context_release () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f5dcd4aa82a in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f5dcd4aa98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f5dd2d8eaab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f5dd2d366fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f5dd2b5c3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f5dd2b612e8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5dce0fd454 in start_thread () at /lib64/libpthread.so.0
#9  0x7f5dd22583ff in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7f5c8b9e9700 (LWP 3286)):
#0  0x7f5dd224b75d in read () at /lib64/libc.so.6
#1  0x7f5dcd4eeae0 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5dcd4aa325 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5dcd4aa814 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f5dcd4aa98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f5dd2d8eaab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f5dd2d366fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f5dd2b5c3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f5dd2b612e8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f5dce0fd454 in start_thread () at /lib64/libpthread.so.0
#10 0x7f5dd22583ff in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f5c9addd700 (LWP 3280)):
#0  0x7f5dcd4efea4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5dcd4aa82a in  () at /usr/lib64/libglib-2.0.so.0
#2 

[konsole] [Bug 369328] New: Settings -> Edit current profile. Does neither apply the settings to the current shell session nor inform about this

[Achim Bohnet via KDE Bugzilla]

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

Bug ID: 369328
   Summary: Settings -> Edit current profile.   Does neither apply
the settings to the current shell session nor inform
about this
   Product: konsole
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: a...@mpe.mpg.de

Changing settings in 'edit current dialog' are not applied immediately after
'okay' or 'apply' nor or is the user informed about this fact.

Reproducible: Always

Steps to Reproduce:
1.  Open Settings -> Edit current profile
2.  e.g.  choose to hide the scrollbar
3. select 'okay; to close the dialog

Actual Results:  
the scrollbar of the current shell window is still there

Expected Results:  
Either hide the scrollbar after 'okay' or 'Apply' or inform the use that only
new konsole windows or newly created session with same profile will apply the
settings.

As it is, it looks like konsole ignores the setting.  Confuses me once in a
while again ;-)

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

[kontact] [Bug 245024] Kontact crashed on shutdown

[RussianNeuroMancer via KDE Bugzilla]

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

RussianNeuroMancer  changed:

   What|Removed |Added

 CC|russianneuroman...@ya.ru|

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

[Spectacle] [Bug 369330] 'Window under cursor' assume wrongly that dialogs are always in the upper left corner

[Achim Bohnet via KDE Bugzilla]

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

--- Comment #1 from Achim Bohnet  ---
Created attachment 101283
  --> https://bugs.kde.org/attachment.cgi?id=101283=edit
screenshot of upper left area with dimension of the dialog.  Dialog itself is
partially visible in the lower right area

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[Burkhard Lueck via KDE Bugzilla]

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

--- Comment #4 from Burkhard Lueck  ---
Scripty permforms a check for valid language docbook in his daily run, see e.g
ftp://l10n.kde.org/160920.trunk_l10n-kf5 and reports invalid language docbooks
in his log.
Thats why I am sure we have some fully translated language docbooks, e.g.
checkXML5
/home/kdeframeworks/src/l10n-kf5/uk/docs/extragear-graphics/digikam/index.docbook
reports no error, that means the digikam docbook is fully translated in locale
uk.

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

[konsole] [Bug 369328] Settings -> Edit current profile. Does neither apply the settings to the current shell session nor inform about this

[Achim Bohnet via KDE Bugzilla]

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

--- Comment #3 from Achim Bohnet  ---
I'll usually only set scrollbar=off  (and scrollback=3000 lines).   I'll check
what else is affected as soon as time permit tonight.

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

[plasmashell] [Bug 369332] New: Plasmashell crashed while configuring "Digital Clock"

[Tony via KDE Bugzilla]

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

Bug ID: 369332
   Summary: Plasmashell crashed while configuring "Digital Clock"
   Product: plasmashell
   Version: 5.7.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jodr...@live.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.4)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I was editing the "Digital Clock" settings due to an issue with it, (it was
gone) had to tick "Show local time zone" for it to appear again.

The crash happen after a reboot and i wanted to untick "Show local time zone"
so "UTC" is not shown in it, as i did that plasma crashed.

After plasma came back, i tried again, "UTC" is shown no matter if i tick or
untick "Show local time zone".

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 0x7f85806c18c0 (LWP 1279))]

Thread 26 (Thread 0x7f83121cf700 (LWP 25932)):
#0  0x7f8579c786ed in poll () from /lib64/libc.so.6
#1  0x7f8576295876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f857629598c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f857a5a8aab in QEventDispatcherGlib::processEvents
(this=0x7f82f0011400, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f857a5506fa in QEventLoop::exec (this=this@entry=0x7f83121ced00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f857a3763c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7f857a37b2e8 in QThreadPrivate::start (arg=0x449a2f0) at
thread/qthread_unix.cpp:341
#7  0x7f857946f454 in start_thread () from /lib64/libpthread.so.0
#8  0x7f8579c813ff in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f830d6e7700 (LWP 25928)):
#0  0x7f8579c7475d in read () from /lib64/libc.so.6
#1  0x7f85762d9ae0 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f8576295325 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8576295814 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f857629598c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f857a5a8aab in QEventDispatcherGlib::processEvents
(this=0x7f82e40017e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#6  0x7f857a5506fa in QEventLoop::exec (this=this@entry=0x7f830d6e6ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f857a3763c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#8  0x7f857d754095 in ?? () from /usr/lib64/libQt5Qml.so.5
#9  0x7f857a37b2e8 in QThreadPrivate::start (arg=0x5237100) at
thread/qthread_unix.cpp:341
#10 0x7f857946f454 in start_thread () from /lib64/libpthread.so.0
#11 0x7f8579c813ff in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7f847dffb700 (LWP 25670)):
#0  0x7f857947510f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f857a37c19b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x5060180) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x4c2f3a0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f84bdd83e90 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f84bdd88048 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f84bdd8300d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f84bdd880a2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f84bdd8300d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f84bdd85ed9 in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f857a37b2e8 in QThreadPrivate::start (arg=0x7f846c002f90) at
thread/qthread_unix.cpp:341
#10 0x7f857946f454 in start_thread () from /lib64/libpthread.so.0
#11 0x7f8579c813ff in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7f847e7fc700 (LWP 25669)):
#0  0x7f857947510f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f857a37c19b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x5060180) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x4c2f3a0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f84bdd83e90 in

[akregator] [Bug 289641] Clicking on "Speak Selected Articles" does not read articles (does not do anything)

[Nick via KDE Bugzilla]

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

--- Comment #3 from Nick  ---
I can report this on akregator 4.14.2,(which is also what all users from Debian
stable are likely to be using).
I don't have frameworks / version 5 onwards though.
Thanks.

On 24 September 2016 20:43:51 BST, Denis Kurz via KDE Bugzilla
 wrote:
>https://bugs.kde.org/show_bug.cgi?id=289641
>
>Denis Kurz  changed:
>
>   What|Removed |Added
>
> Resolution|--- |WAITINGFORINFO
> Status|UNCONFIRMED |NEEDSINFO
>
>--- Comment #2 from Denis Kurz  ---
>This bug has only been reported for versions before 4.14, which have
>been
>unsupported for at least two years now. Can anyone tell if this bug
>still
>present?
>
>If noone confirms this bug for a Framework-based version of akregator
>(version
>5.0 or later, as part of KDE Applications 15.08 or later), it gets
>closed in
>about three months.
>
>-- 
>You are receiving this mail because:
>You are on the CC list for the bug.
>You voted for the bug.

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

[korganizer] [Bug 236658] Events deleted if moved

[Andreas Mahel via KDE Bugzilla]

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

--- Comment #5 from Andreas Mahel  ---
Hm...
I tried to reproduce the behavior using the steps I had outlined in comment 2,
and at least the event was not deleted.
So from the wording of the bug, it does not occur any more.

However: what actually happens is - nothing. 
Using the mouse to drag any of the occurrences of a recurring event to a
different time or day still opens the nice dialog asking if the change is to be
applied to this event / future events (if not the first occurrence) / all
events. But nothing is ever changed in the event.
This in KOrganizer 5.3.0 on Opensuse Tumbleweed.

>From an end user's perspective, it still means that modifying recurring events
by drag does not work.

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

[kmail2] [Bug 315638] Clicking on column headers does not sort ascending or descending

[mva]

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

--- Comment #8 from Vadim A. Misbakh-Soloviov (mva)  ---
Eeerm. I just checked it once more and it works fine. So, nevermind ;)

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

[krita] [Bug 368360] Krita does not remember shortcut save location.

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
Is this with the appimage?

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[Burkhard Lueck via KDE Bugzilla]

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

--- Comment #2 from Burkhard Lueck  ---
(In reply to caulier.gilles from comment #1)
> There is no translation yet.
> 
That is wrong.

digikam has 7 translated dobooks updated for 5.0, see Description

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

[kwin] [Bug 369317] Kwin crash with gles

[Andrei Slavoiu via KDE Bugzilla]

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

Andrei Slavoiu  changed:

   What|Removed |Added

   Platform|Compiled Sources|Gentoo Packages

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

[kcron] [Bug 369314] I cant execute actions manually, in Spanish (ejectuar ahora)

[Antonio Rojas via KDE Bugzilla]

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

Antonio Rojas  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED
 CC||aro...@archlinux.org

--- Comment #4 from Antonio Rojas  ---
Another side effect of 366793

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

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

[plasmashell] [Bug 369327] New: User photo/avatar doesn't support antialias

[郭云鹤]

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

Bug ID: 369327
   Summary: User photo/avatar doesn't support antialias
   Product: plasmashell
   Version: 5.5.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: guoyunhebr...@gmail.com
CC: plasma-b...@kde.org

The user photo/avatar in application launcher, SDDM login screen and lock
screen has obvious no antialiasing. This make photos and drawings render in a
bad result.

See screenshot attachment.

Reproducible: Always

Steps to Reproduce:
1. Set a user profile photo.
2. Open application launcher. Look at the user photo in launcher.
3. Lock the screen. Look at the user photo in lock screen.
4. Logout. Look at the user photo in login screen.

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

[plasmashell] [Bug 369327] User photo/avatar doesn't support antialias

[郭云鹤]

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

--- Comment #1 from Guo Yunhe (郭云鹤)  ---
Created attachment 101282
  --> https://bugs.kde.org/attachment.cgi?id=101282=edit
Screenshot of user photo/avatar in application launcher

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

[Spectacle] [Bug 369330] 'Window under cursor' assume wrongly that dialogs are always in the upper left corner

[Achim Bohnet via KDE Bugzilla]

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

Achim Bohnet  changed:

   What|Removed |Added

 Attachment #101283|screenshot of upper left|Result when clicking on the
description|area with dimension of the  |dialog: screenshot of upper
   |dialog.  Dialog itself is   |left area with dimension of
   |partially visible in the|the dialog.  Dialog itself
   |lower right area|is partially visible in the
   ||lower right area

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

[kcron] [Bug 369314] I cant execute actions manually, in Spanish (ejectuar ahora)

[Txutxifel via KDE Bugzilla]

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

--- Comment #2 from Txutxifel  ---
Versión: 5.7.95 (i tried no downgrade with same results)
Personal cron
Yes, It's means

Thank for your quick answer

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

[akregator] [Bug 329530] Akregator produces multiple and distracting/disturbing certificate errors, including when it is only open in tray.

[Nick via KDE Bugzilla]

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

--- Comment #2 from Nick  ---
Hi,
I can report this on akregator 4.14.2,(which is also what all users from Debian
stable are likely to be using).
I don't have frameworks / version 5 onwards though.
Thanks.

On 24 September 2016 20:45:25 BST, Denis Kurz via KDE Bugzilla
 wrote:
>https://bugs.kde.org/show_bug.cgi?id=329530
>
>Denis Kurz  changed:
>
>   What|Removed |Added
>
> Status|UNCONFIRMED |NEEDSINFO
> Resolution|--- |WAITINGFORINFO
>
>--- Comment #1 from Denis Kurz  ---
>This bug has only been reported for versions before 4.14, which have
>been
>unsupported for at least two years now. Can anyone tell if this bug
>still
>present?
>
>If noone confirms this bug for a Framework-based version of akregator
>(version
>5.0 or later, as part of KDE Applications 15.08 or later), it gets
>closed in
>about three months.
>
>-- 
>You are receiving this mail because:
>You reported the bug.

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

[digikam] [Bug 369321] New: Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[Burkhard Lueck via KDE Bugzilla]

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

Bug ID: 369321
   Summary: Translation of digikam + showfoto docbooks missing in
digikam-5.2.0 tarball
   Product: digikam
   Version: 5.2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Documentation
  Assignee: digikam-de...@kde.org
  Reporter: lu...@hube-lueck.de

doc translation of digikam version 5.0 for locale ca, it, nl. pt, pt_BR, sv, uk
are missing in the tarball

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

[kmail2] [Bug 369322] New: Folder / Mailing List Management menu item duplicate of Folder Properties

[Graeme Hewson via KDE Bugzilla]

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

Bug ID: 369322
   Summary: Folder / Mailing List Management menu item duplicate
of Folder Properties
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: b...@wormhole.me.uk

As per summary. The Folder / Mailing List Management menu item seems to be
unnecessary as it's identical to Folder / Folder Properties.

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

[kdevelop] [Bug 369324] New: KDevelop5 crashes when i press Build

[Roman Lebedev via KDE Bugzilla]

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

Bug ID: 369324
   Summary: KDevelop5 crashes when i press Build
   Product: kdevelop
   Version: 5.0.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: lebedev...@gmail.com

Application: kdevelop (5.0.1)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

Sometimes, when i press build button, kdevelop crashes.
CMake-based project is loaded (darktable).
I see no obivious pattern.

The crash can be reproduced every time.

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

Thread 18 (Thread 0x7f0ea2090700 (LWP 9470)):
#0  0x7f0ed1396538 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f0ed7ca7b76 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0ed7ca32f2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0ed7ca6d78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0ed1390464 in start_thread (arg=0x7f0ea2090700) at
pthread_create.c:333
#5  0x7f0ed75b997f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 17 (Thread 0x7f0ea38d7700 (LWP 9468)):
#0  0x7f0ed0529024 in g_mutex_unlock (mutex=0x2708e80) at
././glib/gthread-posix.c:1348
#1  0x7f0ed04e2ecc in g_main_context_prepare
(context=context@entry=0x2708e80, priority=priority@entry=0x7f0ea38d6b40) at
././glib/gmain.c:3497
#2  0x7f0ed04e38fb in g_main_context_iterate
(context=context@entry=0x2708e80, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3907
#3  0x7f0ed04e3aec in g_main_context_iteration (context=0x2708e80,
may_block=1) at ././glib/gmain.c:3988
#4  0x7f0ed7ed451b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0ed7e7c19a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0ed7ca1e53 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0ed7ca6d78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0ed1390464 in start_thread (arg=0x7f0ea38d7700) at
pthread_create.c:333
#9  0x7f0ed75b997f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f0ea40d8700 (LWP 9384)):
#0  0x7f0ed139618f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0ed7ca7c3b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0ecce14da0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f0ecce18fc8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f0ecce13f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f0ecce19022 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f0ecce13f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f0ecce16de9 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f0ed7ca6d78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f0ed1390464 in start_thread (arg=0x7f0ea40d8700) at
pthread_create.c:333
#10 0x7f0ed75b997f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7f0ea48d9700 (LWP 9383)):
#0  0x7f0ed75b50b9 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f0ed7c9ea00 in QBasicMutex::lockInternal() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0ed7c9eb12 in QMutex::lock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0eacb68ec8 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at
/usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.25
#4  0x7f0eacb68d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[via KDE Bugzilla]

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

--- Comment #3 from caulier.gil...@gmail.com ---
Are you sure that ALL handbooks files are present in listed languages :

https://quickgit.kde.org/?p=digikam-doc.git=blob=TODO

The script used to build tarball with translations will check if all files are
present for current language to package. If one is missing, the language is not
included. Note that the script do not check if file is fully translated of
course. It check if file is present to SVN, in goal to have a compilable
translated handbook.

Gilles Caulier

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

[korganizer] [Bug 328486] Recurring todos completed in todoview, marks todo complete forever end does not reschedule.

[Gerard Dirkse via KDE Bugzilla]

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

--- Comment #3 from Gerard Dirkse  ---
Have left korganizer behind me due to total unrepsonsiveness >3 years to
reported problems.

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

[korgac] [Bug 369325] New: korgac used xdg autostart & session management to startup

[Achim Bohnet via KDE Bugzilla]

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

Bug ID: 369325
   Summary: korgac used xdg autostart &  session management to
startup
   Product: korgac
   Version: 5.3.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: a...@mpe.mpg.de

There is
1)  the file /etc/xdg/autostart/org.kde.korgac.desktop
2)  korgac -session 101a119f1a41c300014747926830020380006_1474798364_653715

This implies that using the korgac RMB menu 'Start reminder deamon at login'
does not work,
because session management still starts korgac

Reproducible: Always

Steps to Reproduce:
1. Use RMB Menu of korgac systray icon and disable 'Start reminder daemon at
login
2. logout/login
3. check if korgac is still running

Actual Results:  
korg is still running

Expected Results:  
korg is not started on login



First: I'm a long time KDE PIM user and *I* can not life without it.  
Nevertheless I would prefer korgac autostart=false by default.

My Goal: start akonadi and PIM tools only when needed.
My Rational:
most of my user at work and my familie don't use KDE PIM, nevertheless it's
started by default.
This is also true for neons and kubuntu  live ISO session (because xdg
autostart is true by default)  which makes also no sense for a life session.

Achim

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

[Akonadi] [Bug 241850] Wrong address extension in google-akonadiplugin

[Jens Westemeier via KDE Bugzilla]

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

--- Comment #2 from Jens Westemeier  ---
I moved to Thunderbird some years ago, so I can't tell whether the bug still
exists.

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

[konsole] [Bug 366793] Regression in Konsole's handling of command line parameters

[Antonio Rojas via KDE Bugzilla]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||jesa...@gmail.com

--- Comment #17 from Antonio Rojas  ---
*** Bug 369314 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 369326] New: Kdevelop reliably crashes when Project -> Open Configuration

[Roman Lebedev via KDE Bugzilla]

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

Bug ID: 369326
   Summary: Kdevelop reliably crashes when Project -> Open
Configuration
   Product: kdevelop
   Version: 5.0.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: lebedev...@gmail.com

Application: kdevelop (5.0.1)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

I see no obivious pattern.
It worked fine yesterday.

Now, each time i press Project -> Open Configuration, kdevelop crashes.
This is cmake-based project.

The crash can be reproduced every time.

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

Thread 17 (Thread 0x7f7aef300700 (LWP 31482)):
#0  0x7f7b1e5be538 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f7b24ecfb76 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f7b24ecb2f2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f7b24eced78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f7b1e5b8464 in start_thread (arg=0x7f7aef300700) at
pthread_create.c:333
#5  0x7f7b247e197f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f7af0ade700 (LWP 31480)):
#0  0x7f7b1d751009 in g_mutex_lock (mutex=mutex@entry=0x365fc70) at
././glib/gthread-posix.c:1336
#1  0x7f7b1d70b9bb in g_main_context_iterate (priority=,
n_fds=1, fds=0x35df960, timeout=, context=0x365fc70) at
././glib/gmain.c:4221
#2  0x7f7b1d70b9bb in g_main_context_iterate
(context=context@entry=0x365fc70, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3922
#3  0x7f7b1d70baec in g_main_context_iteration (context=0x365fc70,
may_block=1) at ././glib/gmain.c:3988
#4  0x7f7b250fc51b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f7b250a419a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f7b24ec9e53 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f7b24eced78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f7b1e5b8464 in start_thread (arg=0x7f7af0ade700) at
pthread_create.c:333
#9  0x7f7b247e197f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7f7af1300700 (LWP 31414)):
#0  0x7f7b247dd0b9 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f7b24ec6a00 in QBasicMutex::lockInternal() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f7b24ec6b12 in QMutex::lock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f7af9d90ec8 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at
./languages/clang/duchain/clanghelpers.cpp:133
#4  0x7f7af9d90d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at
./languages/clang/duchain/clanghelpers.cpp:121
#5  0x7f7af9d90d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at
./languages/clang/duchain/clanghelpers.cpp:121
#6  0x7f7af9d90d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at

[Spectacle] [Bug 369330] New: 'Window under cursor' assume wrongly that dialogs are always in the upper left corner

[Achim Bohnet via KDE Bugzilla]

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

Bug ID: 369330
   Summary: 'Window under cursor' assume wrongly that dialogs are
always in the upper left corner
   Product: Spectacle
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: a...@mpe.mpg.de

When I tried to make a snapshot of dialogs,  spectable always captures they
upper left area with the width and height of the dialog.  It not capture the
dialog itself.

Reproduceable in virtualbox mit neon pkg from master and  PC with 4.7.4

Reproducible: Always

Steps to Reproduce:
1. open kate
2. Ctrl^O to open the 'open file' dialog.
3. Make sure the dialog is not in the upper left corner
4. Start spectable
5. select 'window under cursor' and click on the open file dialog of kate

Actual Results:  
spectable makes a screenshot of the upper left aera of the screen with the
dimensions of the dialog (see screenshot)

Expected Results:  
spectable makes a screenshot of the dialog

A workaround for the bug is to move the dialog in the upper left corner and
then take the screenshot.   :-)

Thx for the cool tools spectacle!
Achim

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

[kmail2] [Bug 284704] Help file lacks any information about maildir accounts

[via KDE Bugzilla]

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

--- Comment #5 from abrah...@acm.org ---
I'm using 4.13.3.  In case you're wondering why I'm not using a newer version,
it's because I'm running Kubuntu 14.04.  And why am I running 14.04?  It's
because I need different wallpaper for different desktops and newer versions
don't have that.  It's been promised by the developer to return, but he
requested that people stop bugging him about it.  I'm eagerly awaiting the
return of that feature, but in the meantime I'm taking advantage of the fact
that 14.04 is a long-term release.

In any case, I'm unable to test whether my comment really applies to the latest
release of kmail.

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

[kontact] [Bug 369331] New: kontact crashes during closing

[via KDE Bugzilla]

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

Bug ID: 369331
   Summary: kontact crashes during closing
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: alfa...@gmx.de

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.4.21-2-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
By closing Kontact (by menue or window button), the application crahses!
Version 16.08.1

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f22f5ac0800 (LWP 5826))]

Thread 23 (Thread 0x7f2274616700 (LWP 5936)):
#0  0x7f22e9d6ad14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f22e9d284a0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f22e9d28d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f22e9d28f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f22f32b7f3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f22f326788b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f22f30ae02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f22f30b2859 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f22ebafa0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f22f27a402d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f22758e3700 (LWP 5911)):
#0  0x7f22f279bbfd in poll () at /lib64/libc.so.6
#1  0x7f22e9d28e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f22e9d28f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f22f32b7f3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f22f326788b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f22f30ae02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f22f30b2859 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f22ebafa0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f22f27a402d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f2276c72700 (LWP 5859)):
#0  0x7ffd17d64b62 in clock_gettime ()
#1  0x7f22f27b0c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f22f31568b1 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f22f32b65c9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f22f32b6b45 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f22f32b7d0e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f22e9d284ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f22e9d28d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f22e9d28f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f22f32b7f3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f22f326788b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f22f30ae02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f22f30b2859 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f22ebafa0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f22f27a402d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f2277473700 (LWP 5857)):
#0  0x7f22e9d28d62 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f22e9d28f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f22f32b7f3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f22f326788b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f22f30ae02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f22f30b2859 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f22ebafa0a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7f22f27a402d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f2277c74700 (LWP 5855)):
#0  0x7ffd17d64b62 in clock_gettime ()
#1  0x7f22f27b0c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f22f31568b1 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f22f32b65c9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f22f32b6b45 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f22f32b7d0e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f22e9d284ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f22e9d28d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f22e9d28f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f22f32b7f3b in

[konsole] [Bug 369328] Settings -> Edit current profile. Does neither apply the settings to the current shell session nor inform about this

[Kurt Hindenburg via KDE Bugzilla]

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

--- Comment #1 from Kurt Hindenburg  ---
That is very strange.  DO you know if it is only the scrollbar option or
everything that is ignored?  It all works here.  Also, how recent is Neon's
master checkout?

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

[konsole] [Bug 369328] Settings -> Edit current profile. Does neither apply the settings to the current shell session nor inform about this

[Achim Bohnet via KDE Bugzilla]

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

--- Comment #2 from Achim Bohnet  ---
Today short after midnight  I assume from the version number.

achim@neon-dev-unstable:~$ apt-cache policy konsole
konsole:
  Installed: 4:16.08.1+p16.04+git20160925.0034-0

neon dev unstable is alwasy from master J.Riddell told me.

This a a virtualbox installed today.   But I've seen it on 16.08.03 (neon dev
stable) too.

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

[frameworks-baloo] [Bug 362647] Can't search with Chinese characters

[via KDE Bugzilla]

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

zwpwj...@126.com changed:

   What|Removed |Added

 CC||zwpwj...@126.com

--- Comment #2 from zwpwj...@126.com ---
Confirmed, using Baloo 5.26.

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[via KDE Bugzilla]

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

--- Comment #5 from caulier.gil...@gmail.com ---
ok, 

I will run the digiKam release script to see if at least with UK, the complete
handbook files are found properly.

Gilles Caulier

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

[kmail2] [Bug 282132] mail replies are shown in the message list without sender (aka from:) information

[Michi via KDE Bugzilla]

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

--- Comment #5 from Michi  ---
for more than 5 years now.

It's an account on a Strato server.

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

[kontact] [Bug 369333] Crash when deleting message in kmail2

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.3.2
 CC||mon...@kde.org

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

[kdenlive] [Bug 369295] Error exporting when use Key Spill Mop Up filter

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Jean-Baptiste Mardelle  ---
Thanks for your report, I can confirm this is an issue in our  PPA, working on
it.

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

[kaddressbook] [Bug 280800] kmail group contacts not working

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #8 from Freek de Kruijf  ---
Checked it in kmail5 16.08.01. Problem does not exist anymore.

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

[Akonadi] [Bug 241850] Wrong address extension in google-akonadiplugin

[Christophe Giboudeaux via KDE Bugzilla]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Christophe Giboudeaux  ---
Thanks for the feedback.

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

[dolphin] [Bug 364956] Add option to keep music/video preview, when mouse hover somewhere else

[Arran via KDE Bugzilla]

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

Arran  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Arran  ---
*** This bug has been confirmed by popular vote. ***

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

[digikam] [Bug 369334] When deleting folder, it should warn about non-image files

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Severity|critical|normal

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

[Akonadi] [Bug 338215] A substring in a call to drkonqi from akonadi in kdepimlibs is not completely filled in

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Freek de Kruijf  ---
I am unable to check this for kmail5 or rather akonadi. It appeared when
connecting to a courier IMAP server with a problem. Now I am using dovecot.
Can't reproduce it.

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

[kmail2] [Bug 298399] 'Customize accounts order' randomly fails if folders are sorted manually

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED

--- Comment #14 from Freek de Kruijf  ---
Checked it for kmail5 16.08.1 and it works as it should.

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

[kmail2] [Bug 292516] KMail2 IMAP accounts keep crashing and loosing email content

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Freek de Kruijf  ---
Does not happen anymore. Is no longer reproducible. Consider it fixed.

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

[kmail2] [Bug 357313] Column-width in the main window, i.e. "subject", "from", "date" not kept, crowded to left

[tony den haan via KDE Bugzilla]

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

tony den haan  changed:

   What|Removed |Added

 CC||kdeb...@tuxick.net

--- Comment #2 from tony den haan  ---
similar problem here: i only saw the date column, when i resized leftmost i
also had the Sender column. "Adjust column sizes" does nothing at all, so at
the moment kmail is unusable for me.


KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
Ubuntu 16.04.1 LTS

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[via KDE Bugzilla]

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

--- Comment #7 from caulier.gil...@gmail.com ---
This is the result of digiKam release script that i configured to checkout
handbook translations :

-- Extract documentation translation files from git repositories. Please wait,
it can take a while...
-- NOTE: (u) want mean uncomplete translations files, which will be removed
from compilation.
digikam: af(u) ar(u) az(u) be(u) bg(u) bn(u) br(u) bs(u) ca(u) cs(u) csb(u)
cy(u) da(u) de(u) el(u) en_GB(u) eo(u) es(u) et(u) eu(u) fa(u) fi(u) fo(u)
fr(u) fy(u) ga(u) gl(u) ha(u) he(u) hi(u) hr(u) hsb(u) hu(u) id(u) is(u) it(u)
ja(u) ka(u) kk(u) km(u) ko(u) ku(u) lb(u) lo(u) lt(u) lv(u) mi(u) mk(u) mn(u)
ms(u) mt(u) nb(u) nds(u) ne(u) nl(u) nn(u) nso(u) oc(u) pa(u) pl(u) pt(u)
pt_BR(u) ro(u) ru(u) rw(u) se(u) sk(u) sl(u) sq(u) sr(u) sr@Latn(u) ss(u) sv(u)
ta(u) te(u) tg(u) th(u) tr(u) tt(u) uk(u) uz(u) uz@cyrillic(u) ven(u) vi(u)
wa(u) xh(u) zh_CN(u) zh_HK(u) zh_TW(u) zu(u) 
showfoto: 
-- Documentation translation files extraction done.

As expected, none has full list of files from digiKam handbook. All are dropped
from tarball.

Did you take a look in 

https://quickgit.kde.org/?p=digikam-doc.git=blob=TODO

... where you have all docbook files listed which constitute the digiKam
handbook ? The original hanbook, written more than 10 year ago was cut in small
parts now. The release script will check if all files are present in SVN to
considerate that translated documentation is ready to by packaged for a
specific language.

Gilles Caulier

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

[kontact] [Bug 335679] kontact crashed after migrating password to kwallet

[Stanislav Piecka via KDE Bugzilla]

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

Stanislav Piecka  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WONTFIX

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

[kontact] [Bug 335679] kontact crashed after migrating password to kwallet

[Stanislav Piecka via KDE Bugzilla]

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

Stanislav Piecka  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[Burkhard Lueck via KDE Bugzilla]

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

--- Comment #9 from Burkhard Lueck  ---
(In reply to caulier.gilles from comment #7)
> 
> As expected, none has full list of files from digiKam handbook. All are
> dropped from tarball.
> 
Your script seems to be broken, at least locales it, nl. pt, pt_BR, uk have a
fully translated docbook for digikam + showfoto 5.0 - verified with checkXML5

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

[kmail2] [Bug 219572] composer hard wraps at window border

[Tristan Miller via KDE Bugzilla]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #15 from Tristan Miller  ---
I can confirm that the bug still exists in KMail 5.1.3 (KDE Applications
5.12.3).

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[via KDE Bugzilla]

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

--- Comment #10 from caulier.gil...@gmail.com ---
But between 5.0 and 5.2, a lots of changes have been performed. As i said, the
docbook have been cut in small parts and new parts have been add. The list of
docbook files is :

annexes-credits.docbook
editor-cm-connection.docbook
editor-cm-definitions.docbook
editor-cm.docbook
editor-cm-intro.docbook
editor-cm-monitor.docbook
editor-cm-pcs.docbook
editor-cm-rawfile.docbook
editor-cm-rendering.docbook
editor-cm-srgb.docbook
editor-cm-wkspace.docbook
editor-color-auto.docbook
editor-color-bw.docbook
editor-color-correction.docbook
editor-color-curves.docbook
editor-color.docbook
editor-color-exposure.docbook
editor-color-levels.docbook
editor-color-mixer.docbook
editor-color-neg.docbook
editor-color-wb.docbook
editor-decorate-border.docbook
editor-decorate.docbook
editor-decorate-inserttext.docbook
editor-decorate-texture.docbook
editor-enhance-blur.docbook
editor-enhance-distortion.docbook
editor-enhance.docbook
editor-enhance-hotpixels.docbook
editor-enhance-inpaint.docbook
editor-enhance-lenscorrection.docbook
editor-enhance-localcontrast.docbook
editor-enhance-nr.docbook
editor-enhance-redeyes.docbook
editor-enhance-restoration.docbook
editor-enhance-sharpen.docbook
editor-enhance-vignetting.docbook
editor-filters-blurfx.docbook
editor-filters-charcoal.docbook
editor-filters-colorsfx.docbook
editor-filters-distortionfx.docbook
editor-filters.docbook
editor-filters-emboss.docbook
editor-filters-filmgrain.docbook
editor-filters-oilpaint.docbook
editor-filters-raindrops.docbook
editor-photoediting.docbook
editor-transform-crop.docbook
editor-transform.docbook
editor-transform-freerotation.docbook
editor-transform-liquid.docbook
editor-transform-perspective.docbook
editor-transform-resize.docbook
editor-transform-rotateflip.docbook
editor-transform-shear.docbook
editor-using.docbook
index.docbook
intro-background.docbook
intro-camerasupport.docbook
intro-contrib.docbook
intro-database.docbook
intro-firstrun.docbook
intro-imageformats.docbook
intro-info.docbook
intro-movieformats.docbook
intro-pluginsupport.docbook
menu-bqm.docbook
menu-camera.docbook
menu-editor.docbook
menu-lighttable.docbook
menu-mainwindow.docbook
tool-acquireimages.docbook
tool-advrename.docbook
tool-calendar.docbook
tool-dropbox.docbook
tool-expoblending.docbook
tool-facebook.docbook
tool-findduplicates.docbook
tool-flashexport.docbook
tool-flickrexport.docbook
tool-geolocationeditor.docbook
tool-googleexport.docbook
tool-imageshack.docbook
tool-imgur.docbook
tool-kmlexport.docbook
tool-maintenance.docbook
tool-mediawiki.docbook
tool-metadataeditor.docbook
tool-panorama.docbook
tool-piwigoexport.docbook
tool-presentation.docbook
tool-printwizard.docbook
tool-rajce.docbook
tool-remotestorage.docbook
tool-sendimages.docbook
tool-smug.docbook
tool-vkontakte.docbook
tool-yandexfotki.docbook
using-bqm.docbook
using-camera-basis.docbook
using-camera.docbook
using-camera-gps.docbook
using-camera-intro.docbook
using-camera-processing.docbook
using-dam-build.docbook
using-dam-copyright.docbook
using-dam-corruption.docbook
using-dam.docbook
using-dam-intro.docbook
using-dam-workflow.docbook
using-lighttable.docbook
using-mainwindow-albumsview.docbook
using-mainwindow-datesview.docbook
using-mainwindow.docbook
using-mainwindow-fuzzysearches.docbook
using-mainwindow-imageview.docbook
using-mainwindow-intro.docbook
using-mainwindow-labelsview.docbook
using-mainwindow-peopleview.docbook
using-mainwindow-searchesview.docbook
using-mainwindow-tagsview.docbook
using-mainwindow-timelineview.docbook
using-setup-album.docbook
using-setup-camera.docbook
using-setup-cm.docbook
using-setup-collections.docbook
using-setup-database.docbook
using-setup.docbook
using-setup-editor-iface.docbook
using-setup-editor-raw.docbook
using-setup-editor-save.docbook
using-setup-editor-version.docbook
using-setup-intro.docbook
using-setup-lighttable.docbook
using-setup-metadata.docbook
using-setup-metadata-intro.docbook
using-setup-metadata-rotation-ac.docbook
using-setup-metadata-views.docbook
using-setup-mimetype.docbook
using-setup-misc-behavior.docbook
using-setup-misc.docbook
using-setup-plugins.docbook
using-setup-quality.docbook
using-setup-slideshow.docbook
using-setup-templates.docbook
using-setup-theme.docbook
using-setup-tooltip.docbook
using-sidebar-captions.docbook
using-sidebar-colors.docbook
using-sidebar.docbook
using-sidebar-filters.docbook
using-sidebar-intro.docbook
using-sidebar-maps.docbook
using-sidebar-metadata.docbook
using-sidebar-properties.docbook
using-sidebar-tools.docbook
using-tagsmngr.docbook

... my script is not broken...

Gilles Caulier

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

[konversation] [Bug 369337] New: Crash if I close the watched nicks tab

[Lays Rodrigues via KDE Bugzilla]

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

Bug ID: 369337
   Summary: Crash if I close the watched nicks tab
   Product: konversation
   Version: 1.6
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: laysrodriguessi...@gmail.com

Application: konversation (1.6-branch #4910)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdcd25bb800 (LWP 8228))]

Thread 5 (Thread 0x7fdcad01f700 (LWP 8233)):
#0  0x7fdcc95f44b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fdccbcc6b66 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fdccbcc2274 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fdccbcc5d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fdcc95ee454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fdccb2d77df in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7fdcb5c5a700 (LWP 8232)):
#0  0x7fdccb2ce48d in poll () from /usr/lib/libc.so.6
#1  0x7fdcc5a7a066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fdcc5a7a17c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fdccbef459b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fdccbe9e0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdccbcc10f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fdccbcc5d78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fdcc95ee454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fdccb2d77df in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7fdcb7072700 (LWP 8231)):
#0  0x7fdccbef3b08 in ?? () from /usr/lib/libQt5Core.so.5
#1  0x7fdcc5a795b9 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fdcc5a79f8b in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fdcc5a7a17c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fdccbef459b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fdccbe9e0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fdccbcc10f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fdccc305e75 in ?? () from /usr/lib/libQt5DBus.so.5
#8  0x7fdccbcc5d78 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7fdcc95ee454 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7fdccb2d77df in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fdcbcfd5700 (LWP 8230)):
#0  0x7fdccb2ce48d in poll () from /usr/lib/libc.so.6
#1  0x7fdcc798c8e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fdcc798e679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fdcbef16469 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fdccbcc5d78 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fdcc95ee454 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fdccb2d77df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fdcd25bb800 (LWP 8228)):
[KCrash Handler]
#5  0x005d1c49 in ViewContainer::canMoveViewLeft() const ()
#6  0x005d52fb in ViewContainer::updateViewActions(int) ()
#7  0x005d6bdb in ViewContainer::updateFrontView() ()
#8  0x005d6f73 in ViewContainer::viewSwitched(int) ()
#9  0x005d9b54 in ViewContainer::cleanupAfterClose(ChatWindow*) ()
#10 0x006b02a4 in ?? ()
#11 0x7fdccbecb4e9 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#12 0x006a4f12 in ChatWindow::closing(ChatWindow*) ()
#13 0x005cad4b in ChatWindow::~ChatWindow() ()
#14 0x0057 in NicksOnline::~NicksOnline() ()
#15 0x00580079 in NicksOnline::~NicksOnline() ()
#16 0x005d36ca in ViewContainer::closeNicksOnlinePanel() ()
#17 0x005da094 in ViewContainer::closeCurrentView() ()
#18 0x006b0289 in ?? ()
#19 0x7fdccbecb4e9 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#20 0x7fdccce04472 in QAction::triggered(bool) () from
/usr/lib/libQt5Widgets.so.5
#21 0x7fdccce06e60 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/libQt5Widgets.so.5
#22 0x7fdcccf74eea in ?? () from /usr/lib/libQt5Widgets.so.5
#23 0x7fdcccf7b0ec in ?? () from /usr/lib/libQt5Widgets.so.5
#24 0x7fdcccf7f0e0 in QMenu::mouseReleaseEvent(QMouseEvent*) () from
/usr/lib/libQt5Widgets.so.5
#25 0x7fdccce51f18 in QWidget::event(QEvent*) () from

[korganizer] [Bug 210554] Wrong time zone in "Time and Date" configure dialog and appointments

[Tristan Miller via KDE Bugzilla]

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

Tristan Miller  changed:

   What|Removed |Added

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

--- Comment #4 from Tristan Miller  ---
The bug is no longer present in KOrganizer 5.1.3 because the Settings dialog no
longer allows the user to select a time zone.  I'd mark this as RESOLVED but
I'm not sure which resolution type to use (FIXED, WORKSFORME, UNMAINTAINED,
INVALID?).

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

[kontact] [Bug 335679] kontact crashed after migrating password to kwallet

[Christophe Giboudeaux via KDE Bugzilla]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|WONTFIX |WORKSFORME

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

[korganizer] [Bug 109854] CTRL + drag in ToDo sidebar doesn't copy items

[Christophe Giboudeaux via KDE Bugzilla]

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

--- Comment #4 from Christophe Giboudeaux  ---
why do you reopen the bug, then ?

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

[kmail2] [Bug 219572] composer hard wraps at window border

[Christophe Giboudeaux via KDE Bugzilla]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #16 from Christophe Giboudeaux  ---
Thanks. This is also valid with git master

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

[kmail2] [Bug 219572] composer hard wraps at window border

[Christophe Giboudeaux via KDE Bugzilla]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

Version|1.99.0  |5.3.1

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

[kmail2] [Bug 282132] mail replies are shown in the message list without sender (aka from:) information

[Denis Kurz via KDE Bugzilla]

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

--- Comment #6 from Denis Kurz  ---
I'm sorry to ask again, but which version of KMail do you use? You can find the
version in KMail itself (or Kontact, for that matter) and clicking "Help ->
Introduction to KMail" in the menu. This information is quite essential, since
we lack the manpower to support old versions.

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

[korganizer] [Bug 109854] CTRL + drag in ToDo sidebar doesn't copy items

[Tristan Miller via KDE Bugzilla]

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

--- Comment #5 from Tristan Miller  ---
I was clearing the NEEDSINFO flag.  I don't know if this report should be
closed or repurposed for the issue discussed in my comment.

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

[kontact] [Bug 369333] New: Crash when deleting message in kmail2

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 369333
   Summary: Crash when deleting message in kmail2
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: freekdekru...@kde.nl

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I was going through a number of new messages, which were successively deleted.
After a few KMail crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f20a9216600 (LWP 8190))]

Thread 34 (Thread 0x7f1f58af9700 (LWP 8303)):
#0  0x7f20a0e50ea4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f20a0e0b996 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f20a66efaab in QEventDispatcherGlib::processEvents (this=0x32d48b0,
flags=...) at kernel/qeventdispatcher_glib.cpp:419
#3  0x7f20a66976fa in QEventLoop::exec (this=this@entry=0x7f1f58af8c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f20a64bd3c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#5  0x7f20a64c22e8 in QThreadPrivate::start (arg=0x30e9d70) at
thread/qthread_unix.cpp:341
#6  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#7  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f1f5ba3e700 (LWP 8300)):
#0  0x7f20a66eefa0 in timerSourcePrepareHelper (timeout=0x7f1f5ba3dab4,
src=) at kernel/qeventdispatcher_glib.cpp:126
#1  timerSourcePrepare (source=, timeout=0x7f1f5ba3dab4) at
kernel/qeventdispatcher_glib.cpp:159
#2  0x7f20a0e0ad79 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f20a0e0b79b in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f20a0e0b98c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f20a66efaab in QEventDispatcherGlib::processEvents
(this=0x7f1f58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#6  0x7f20a66976fa in QEventLoop::exec (this=this@entry=0x7f1f5ba3dc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f20a64bd3c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#8  0x7f20a64c22e8 in QThreadPrivate::start (arg=0x30f1f90) at
thread/qthread_unix.cpp:341
#9  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#10 0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f1f697a6700 (LWP 8248)):
#0  0x7f20a1a6410f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f20991e4d49 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f20991e5460 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f20991e5630 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f20991e223d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#6  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f1f6abed700 (LWP 8242)):
#0  0x7f20a1a6410f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f20991e4d49 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f20991e5460 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f20991e5630 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f20991e223d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#6  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f1f6b3ee700 (LWP 8237)):
#0  0x7f20a0e0afe5 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f20a0e0b7e8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f20a0e0b98c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f20a66efaab in QEventDispatcherGlib::processEvents
(this=0x7f1f5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f20a66976fa in QEventLoop::exec (this=this@entry=0x7f1f6b3edc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f20a64bd3c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7f20a64c22e8 in QThreadPrivate::start (arg=0x2348d30) at
thread/qthread_unix.cpp:341
#7  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#8  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f1f6bbef700 (LWP 8235)):
#0  0x7f20a0e0af30 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  

[digikam] [Bug 369334] New: When deleting folder, it should warn about non-image files

[Mathieu MD via KDE Bugzilla]

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

Bug ID: 369334
   Summary: When deleting folder, it should warn about non-image
files
   Product: digikam
   Version: 5.1.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: math...@ghack.net

If you have non-image files into a folder (.zip, .txt, etc.) DigiKam will not
warn you when you will delete the folder. I agree DK is not expected to display
these files, but still, I feel unsafe if it is able to delete a folder
containing other files without at least warning me about them.

Reproducible: Always

Steps to Reproduce:
1. Create a folder under one of your collections
2. Open it with file explorer (Dolphin for me)
3. From the file explorer, create a text file
4. Back to DK, delete the folder

Actual Results:  
DK ask the usual question about deleting the folder itself, but don't warn
about the text file, and when confirmed actually remove the folder.

Expected Results:  
DK should explicitly warn about the presence of this text file.

Fortunately, the text file is actually moved into the trash, and so it can be
retrieved. But one may not check trash content very often...

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

[kdenlive] [Bug 369296] crash rendering in .mp4 on video with "levels" colour correction effect

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Jean-Baptiste Mardelle  ---
I can confirm there is currently a problem in our PPA's frei0r package, we are
working on it.

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