[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Patrick Rudolph
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #9 from Patrick Rudolph  ---
Turns out the ibus behaviour on tty change is already fixed here:
https://bugs.kde.org/show_bug.cgi?id=379930

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

[kdevelop] [Bug 384953] KDevelop Open dialogue box is dog-butt slow when code is parsing

2017-10-01 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=384953

--- Comment #9 from Sven Brauch  ---
Note, to get more standard traces with multiple threads, use "thread apply all
bt".

The trace you posted points to looking up the mime type of a document. Being
just one sample, that doesn't really tell what the time is spent on ...

I don't know, I don't see the problem here. Which file dialog are you using?
How large is the directory it opens on?

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

[okular] [Bug 385200] Low resolution rendering when using display scaling on HiDPI monitor

2017-10-01 Thread Henrik Fehlauer
https://bugs.kde.org/show_bug.cgi?id=385200

--- Comment #4 from Henrik Fehlauer  ---
Thanks for testing, and make sure to let Lukas know in Phabricator if you still
find any issues.

> Is there any estimate yet when this would make it into master,
> or even into Neon packages?
As soon as Lukas is back from traveling and resumes work, and the relevant
people are happy with the state, I guess, but I would not expect it earlier
than for the KDE Applications 17.12 release (see
https://community.kde.org/Schedules/Applications/17.12_Release_Schedule).

While Neon is not the official KDE distribution, they are usually very fast to
provide packages after a release. As soon as the feature is merged to master,
you may find it also in some of the unstable Neon editions.

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

[konsole] [Bug 385286] New: Konsole segfault

2017-10-01 Thread Samantha McVey
https://bugs.kde.org/show_bug.cgi?id=385286

Bug ID: 385286
   Summary: Konsole segfault
   Product: konsole
   Version: 17.08.1
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: samant...@posteo.net
  Target Milestone: ---

Application: konsole (17.08.1)

Qt Version: 5.7.1
Frameworks Version: 5.38.0
Operating System: Linux 4.12.0-sabayon x86_64
Distribution: "Sabayon Linux amd64 17.10"

-- Information about the crash:
- What I was doing when the application crashed:
 perl -C -E'say
"\x{1F3F4}\x{E0067}\x{E0062}\x{E0065}\x{E006E}\x{E0067}\x{E007F}"'

It is reproducible every time for me. See
https://emojipedia.org/flag-for-england/

The font I have set is Fantasque Sans, though I don't know if that matters. The
perl command above prints out the 'England' flag. It is a new emoji and it's
causing Konsole to crash every time it was seen. Either printing it out with
perl or by using less on the UCD (Unicode emoji data files).

The crash can be reproduced every time.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f27fd90d840 (LWP 13401))]

Thread 3 (Thread 0x7f27e0f35700 (LWP 13403)):
#0  0x7f27fd3bf1fd in read () from /lib64/libc.so.6
#1  0x7f27f4d99570 in g_wakeup_acknowledge () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f27f4d56572 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f27f4d56a48 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f27f4d56bac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f27fa08cb1c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f27fa04389a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f27f9eb696c in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f27fd98a395 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#9  0x7f27f9ebac1d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f27f6a2165c in start_thread () from /lib64/libpthread.so.0
#11 0x7f27fd3cd4fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f27e2c2a700 (LWP 13402)):
#0  0x7f27fd3c367d in poll () from /lib64/libc.so.6
#1  0x7f27f6e46852 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f27f6e4853f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f27e495dce9 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f27f9ebac1d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f27f6a2165c in start_thread () from /lib64/libpthread.so.0
#6  0x7f27fd3cd4fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f27fd90d840 (LWP 13401)):
[KCrash Handler]
#6  0x7f27fa81bf03 in QRegion::~QRegion() () from /usr/lib64/libQt5Gui.so.5
#7  0x7f27fa7dac49 in QPainterState::~QPainterState() () from
/usr/lib64/libQt5Gui.so.5
#8  0x7f27fa7cb5c9 in QRasterPaintEngineState::~QRasterPaintEngineState()
() from /usr/lib64/libQt5Gui.so.5
#9  0x7f27fa7e1f82 in QPainter::end() () from /usr/lib64/libQt5Gui.so.5
#10 0x7f27fa82d7db in
QImageTextureGlyphCache::fillTexture(QTextureGlyphCache::Coord const&, unsigned
int, QFixed) () from /usr/lib64/libQt5Gui.so.5
#11 0x7f27fa82c150 in QTextureGlyphCache::fillInPendingGlyphs() () from
/usr/lib64/libQt5Gui.so.5
#12 0x7f27fa7d0a25 in QRasterPaintEngine::drawCachedGlyphs(int, unsigned
int const*, QFixedPoint const*, QFontEngine*) () from /usr/lib64/libQt5Gui.so.5
#13 0x7f27fa7d3a4b in QRasterPaintEngine::drawTextItem(QPointF const&,
QTextItem const&) () from /usr/lib64/libQt5Gui.so.5
#14 0x7f27fa7ed847 in QPainterPrivate::drawTextItem(QPointF const&,
QTextItem const&, QTextEngine*) () from /usr/lib64/libQt5Gui.so.5
#15 0x7f27fa7ee1c0 in QPainter::drawText(QPointF const&, QString const&,
int, int) () from /usr/lib64/libQt5Gui.so.5
#16 0x7f27fd05be8e in Konsole::TerminalDisplay::drawCharacters(QPainter&,
QRect const&, QString const&, Konsole::Character const*, bool) () from
/usr/lib64/libkonsoleprivate.so.17
#17 0x7f27fd05c2c5 in Konsole::TerminalDisplay::drawTextFragment(QPainter&,
QRect const&, QString const&, Konsole::Character const*) () from
/usr/lib64/libkonsoleprivate.so.17
#18 0x7f27fd062fd7 in Konsole::TerminalDisplay::drawContents(QPainter&,
QRect const&) () from /usr/lib64/libkonsoleprivate.so.17
#19 0x7f27fd0634b7 in Konsole::TerminalDisplay::paintEvent(QPaintEvent*) ()
from /usr/lib64/libkonsoleprivate.so.17
#20 0x7f27fab47688 in QWidget::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#21 0x7f27fd06638a in Konsole::TerminalDisplay::event(QEvent*) () from
/usr/

[klipper] [Bug 385285] New: web.whatsapp.com fillup klipper

2017-10-01 Thread Samuel Suther
https://bugs.kde.org/show_bug.cgi?id=385285

Bug ID: 385285
   Summary: web.whatsapp.com fillup klipper
   Product: klipper
   Version: 5.10.5
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasma-widget
  Assignee: mgraess...@kde.org
  Reporter: s.sut...@gmx.de
  Target Milestone: ---

Created attachment 108124
  --> https://bugs.kde.org/attachment.cgi?id=108124&action=edit
Klipper - 2 chars

If you open https://web.whatsapp.com/ in your Browser, 
and chat a bit with another user, 
you'll found, that the clipper is filled up with many trash ... means each 2
chars are written in web.whatsapp.com are appear as new entry in clipper.

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

[konversation] [Bug 385243] Change the behaviour of the Alt+1..0 hotkeys (to quickly switch between tabs)

2017-10-01 Thread Eike Hein
https://bugs.kde.org/show_bug.cgi?id=385243

Eike Hein  changed:

   What|Removed |Added

 CC||h...@kde.org

--- Comment #1 from Eike Hein  ---
Nice idea. Reviewed on Phab.

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

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Patrick Rudolph
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #8 from Patrick Rudolph  ---
I can confirm that running ibus-daemon --xim -d as user fixes the problem.
I had to place it inside a while loop to restart it automatically every time I
switch ttys as the ibus daemon crashes.

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

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #7 from Silver Salonen  ---
Wow, that totally fixes the problem for me!

Thank you very much Theo!

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

[dolphin] [Bug 385254] Don't change Information panel selection on icon hover when icons are set to double-click

2017-10-01 Thread Clinton Ignatov
https://bugs.kde.org/show_bug.cgi?id=385254

Clinton Ignatov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from Clinton Ignatov  ---
Hmm. I think you're right.

I'm playing around more and since the info panel reverts back to represent the
selection the mouseovers aren't as intrusive as I initially thought. I'd like
to disable them, but since that's a minor wish and not a bug I'll close this
ticket.

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

[krita] [Bug 385276] Krita canvas lags on larger displays on macOS

2017-10-01 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=385276

Alvin Wong  changed:

   What|Removed |Added

 CC||alvinhoc...@gmail.com

--- Comment #1 from Alvin Wong  ---
Well, if you apply these patches does it get even slower?

https://phabricator.kde.org/D7973
https://phabricator.kde.org/D7982
https://phabricator.kde.org/D7984

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

[okular] [Bug 385200] Low resolution rendering when using display scaling on HiDPI monitor

2017-10-01 Thread Markus Krötzsch
https://bugs.kde.org/show_bug.cgi?id=385200

--- Comment #3 from Markus Krötzsch  ---
Thanks for the build instructions. They worked well and the result is looking
very good. I will use this local version of okular for now. Is there any
estimate yet when this would make it into master, or even into Neon packages?

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

[kmail2] [Bug 385284] KMail2 crashes when inline forwarding a message

2017-10-01 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=385284

--- Comment #1 from Igor Zhuravlov  ---
If I double-click to that message, then the following lines are adding to
.xsession-errors :

 void AdblockManager::reloadConfig() false   
AdBlock::AdblockManager(0x260a560)
this does not work on a KActionCollection containing actions!
js: Uncaught SyntaxError: missing ) after argument list
js: Uncaught TypeError: qt.jQuery is not a function
js: Uncaught TypeError: qt.jQuery is not a function
js: Uncaught TypeError: qt.jQuery is not a function

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

[plasma-integration] [Bug 385273] Dragging QListWidgetItems with icons crashes under Plasma, not other envs

2017-10-01 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=385273

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Flöser  ---
Please report the crash to Qt. The backtrace does not contain any code written
by KDE.

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

[kmail2] [Bug 385284] KMail2 crashes when inline forwarding a message

2017-10-01 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=385284

Igor Zhuravlov  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=378363
Version|unspecified |5.3.0

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

[kmail2] [Bug 385284] New: KMail2 crashes when inline forwarding a message

2017-10-01 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=385284

Bug ID: 385284
   Summary: KMail2 crashes when inline forwarding a message
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: zhuravlov...@ya.ru
  Target Milestone: ---

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.87-18.29-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
I just tried to inline forward one message. Then KMail crashes. KMail cannot
view or open this message showing blank window instead.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3b0aaca940 (LWP 4175))]

Thread 40 (Thread 0x7f39737fc700 (LWP 4253)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af88936e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8bb5341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7f3973ffd700 (LWP 4252)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af88936e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8bb5341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7f3a38a8d700 (LWP 4251)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af88936e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8bb5341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7f3a3928e700 (LWP 4250)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af88936e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8bb5341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 36 (Thread 0x7f3a39a8f700 (LWP 4249)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af88936e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8bb5341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7f3a3a290700 (LWP 4248)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af88936e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8bb5341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 34 (Thread 0x7f3a3aa91700 (LWP 4247)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af889270d in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8bb5341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f3a3b7a5700 (LWP 4246)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3af8b86873 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f3af8b86899 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f3a40ea7700 (LWP 4244)):
#0  0x7f3afd8890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3aeea9493b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f3aeea94969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f3afd884744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b078dcaad in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f3a41f0b700 (LWP 4232)):
#0  0x7f3b078d028d in read () at /lib64/libc.so.6
#1  0x7f3afd0aa670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3afd069e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3afd06a2a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f3afd06a42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f3b083f833b in
QEventDispatcherGlib::processEvents(QFlags) ()

[dolphin] [Bug 385283] New: When closing tabs terminal doesn't update properly

2017-10-01 Thread Ryein Goddard
https://bugs.kde.org/show_bug.cgi?id=385283

Bug ID: 385283
   Summary: When closing tabs terminal doesn't update properly
   Product: dolphin
   Version: 17.04.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: panels: terminal
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ryein.godd...@gmail.com
  Target Milestone: ---

When you have Dolphin open and also the terminal option open changing tabs
changes the terminal directory to match, awesome, but one small problem is if
you are currently viewing a tab and have another tab open then decide to close
the tab you are currently viewing it does not update the terminal directory.

On ubuntu 16.04 with backports ppa.
https://community.kde.org/Kubuntu/PPAs

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

[dolphin] [Bug 385066] [Request] Touch screen swipe gestures to scroll the folders/files list

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385066

--- Comment #1 from Nate Graham  ---
*** Bug 385069 has been marked as a duplicate of this bug. ***

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

[Breeze] [Bug 385069] Touch screen swipe gestures drag the window instead scroll its content

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385069

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||pointedst...@zoho.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Nate Graham  ---
This is basically a duplicate of the other bug you filed:
https://bugs.kde.org/show_bug.cgi?id=385066

And yes, I agree that touch swipes need to be supported here.

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

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

[systemsettings] [Bug 385109] Make the sidebar resizable

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385109

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
Summary|Become the sidebar  |Make the sidebar resizable
   |resizable   |

--- Comment #1 from Nate Graham  ---
This is with Brazilian Portuguese, right? Can you attach a screenshot or two?

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

[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385275

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
Apple's TextEdit does this, too.

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

[frameworks-baloo] [Bug 340099] Deleting a tag by deleting the file in tags://* doesn't work

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=340099

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[frameworks-baloo] [Bug 314373] Creating files in tag folders causes unspecified behaviour

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=314373

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[frameworks-baloo] [Bug 332214] File properties dialog is populated incorrectly for results in the tags:/ KIO

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=332214

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[frameworks-baloo] [Bug 340098] Drag and drop for tags not working

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=340098

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[frameworks-baloo] [Bug 376229] Not able to rename files when opening a tag:/// folder

2017-10-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=376229

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kontact] [Bug 385025] Kontact Calendar

2017-10-01 Thread Jeff Fitzmaurice
https://bugs.kde.org/show_bug.cgi?id=385025

--- Comment #2 from Jeff Fitzmaurice  ---
Created attachment 108123
  --> https://bugs.kde.org/attachment.cgi?id=108123&action=edit
New crash information added by DrKonqi

kontact (5.5.1) using Qt 5.7.1

- What I was doing when the application crashed:

Again, I was reading email and decided to switch to the Calendar.  Upon
switching, Kontact crashed.

-- Backtrace (Reduced):
#6  0x7fde15b96ef5 in
EventViews::AgendaView::placeDecorations(QList&,
QDate const&, QWidget*, bool) () at /lib64/libKF5EventViews.so.5
#7  0x7fde15b9ec5c in EventViews::AgendaView::createDayLabels(bool) () at
/lib64/libKF5EventViews.so.5
#8  0x7fde15b9f9ed in EventViews::AgendaView::init(QDate const&, QDate
const&) () at /lib64/libKF5EventViews.so.5
#9  0x7fde15b9fd83 in
EventViews::AgendaView::AgendaView(QSharedPointer const&,
QDate const&, QDate const&, bool, bool, QWidget*) () at
/lib64/libKF5EventViews.so.5
#10 0x7fde38a80160 in KOAgendaView::KOAgendaView(QWidget*, bool) () at
/lib64/libkorganizerprivate.so.5

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

[valgrind] [Bug 383723] SIGILL failure with ud2 opcode (macOS)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=383723

Rhys Kidd  changed:

   What|Removed |Added

 Attachment #107858|0   |1
is obsolete||

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

[valgrind] [Bug 383811] Support macOS High Sierra (10.13)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=383811

Rhys Kidd  changed:

   What|Removed |Added

 Attachment #108101|0   |1
is obsolete||

--- Comment #15 from Rhys Kidd  ---
Comment on attachment 108101
  --> https://bugs.kde.org/attachment.cgi?id=108101
initial macOS High Sierra (10.13) support v2

Preliminary support for Darwin 17.x (macOS 10.13) has now landed in Valgrind
master with 1ce04c35c2ebbc8ea3c2b38ba69daa9dd40cde35.

Please create a new, standalone bug report for any subsequent issues that you
may encounter, this bug report will be used as a meta one to track each
blocker.

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

[valgrind] [Bug 383723] SIGILL failure with ud2 opcode (macOS)

2017-10-01 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=383723

--- Comment #14 from Andy  ---
The easiest way I could think of to create a minimal Qt example was to create a
.app for it and include the Qt libs so it's all self-contained.

I've included the source and a README with what I did and how I run valgrind on
it.

Because it is too big to attach (23M), I put it on Google Drive here:

   https://drive.google.com/open?id=0BxjC6Z37KBFvS0ZlSnJadDZkSWM

If you need anything else (or that example isn't helpful and I can do something
differently) please let me know.

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

[kdenlive] [Bug 385282] New: small audio thumbnails in tracks

2017-10-01 Thread alberto
https://bugs.kde.org/show_bug.cgi?id=385282

Bug ID: 385282
   Summary: small audio thumbnails in tracks
   Product: kdenlive
   Version: git-master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: paj...@gmail.com
  Target Milestone: ---

When you are syncing audio is a must

This video kind of explain how to fix it but they are still very small:
https://www.youtube.com/watch?v=UKslOkep9g0

They should use 100% of the space for audio only tracks and most likely at
least half on videos or being able to toggle it with video (If the problem is
that hides the pictures)

I think the new timeline will separate automatically video and audio, so more
reason to make it bigger :)

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

[kdevelop] [Bug 384953] KDevelop Open dialogue box is dog-butt slow when code is parsing

2017-10-01 Thread Daniel Santos
https://bugs.kde.org/show_bug.cgi?id=384953

--- Comment #8 from Daniel Santos  ---
Being that I don't know QT or KDE, if you can give me a hint as to which
thread(s) service the open dialogue and which are the parsing threads I will
play with it some more and see what I can figure out.  My wild guesses are that
"QQmlThread" is servicing the open dialogue (defined in qml?), "pool" is the
main thread pool thread and that each of the "Queue" threads are members of
that pool (that do parsing)?  Futexes were fairly recently introduced (3.18 I
think?), so maybe this flaw is something new-ish in the framework?

I don't know if it's normal, but one of those threads has 22 levels of
recursion.

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

[kaffeine] [Bug 385272] Instant recording does not work, while scheduled does.

2017-10-01 Thread Mauro Carvalho Chehab
https://bugs.kde.org/show_bug.cgi?id=385272

--- Comment #1 from Mauro Carvalho Chehab  ---
(In reply to Skarmoutsos Vangelis from comment #0)
> When pressing Instant recording button an overlay message informs that
> recording started and if pressed again it informs that recording stopped,
> but no file is created.
> 
> When schedule a recording the corresponding file is created normally.

What Kaffeine version are you using?

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

[valgrind] [Bug 365327] Support macOS Sierra (10.12)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=365327

Rhys Kidd  changed:

   What|Removed |Added

 Depends on|383723  |


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=383723
[Bug 383723] SIGILL failure with ud2 opcode (macOS)
-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 383723] SIGILL failure with ud2 opcode (macOS)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=383723

Rhys Kidd  changed:

   What|Removed |Added

Summary|[PATCH] macOS 10.12.x:  |SIGILL failure with ud2
   |UNKNOWN workq_ops option|opcode (macOS)
   |128, and ud2 opcode |
 Blocks|365327  |

--- Comment #13 from Rhys Kidd  ---
There's really two different bug reports here, so I've gone about cleaning this
up by addressing the workq_ops warning first. Valgrind master has a fix
ed6ad13bc8f2b33c493a72db9915f3681002e8d0 which should mean the warning no
longer occurs.

Thanks for the initial patch Andy Maloney.

I've updated the bug report to reflect that this now just tracks the 'ud2'
issue. Given that is likely architecture dependent, not macOS 10.12 dependent,
I've unlinked this as a blocker to bz#365327.

A minimal test case that reproduces the remaining ud2 opcode issue would be
very helpful in getting it resolved.


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=365327
[Bug 365327] Support macOS Sierra (10.12)
-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 384970] Esc after reading a comment

2017-10-01 Thread Luciana
https://bugs.kde.org/show_bug.cgi?id=384970

--- Comment #2 from Luciana  ---
I appreciate your prompt response and I'm sorry for my late reply.
I had my problem solved with a newer version. Thanks.

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

[ktorrent] [Bug 385281] New: Fallo al abrir KTorrent

2017-10-01 Thread Paco
https://bugs.kde.org/show_bug.cgi?id=385281

Bug ID: 385281
   Summary: Fallo al abrir KTorrent
   Product: ktorrent
   Version: 4.3.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: rpp...@msn.com
  Target Milestone: ---

Application: ktorrent (4.3.1)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.19.0-84-generic x86_64
Distribution: Ubuntu 15.04

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

I was opening the VMware Workstation and I had opened Chrome too

-- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f551269e800 (LWP 5009))]

Thread 4 (Thread 0x7f54e7fff700 (LWP 5067)):
#0  0x7f550e48b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f551218985c in net::Poll::poll(int) () from
/usr/lib/libktorrent.so.5
#2  0x7f551218670c in ?? () from /usr/lib/libktorrent.so.5
#3  0x7f5512186836 in ?? () from /usr/lib/libktorrent.so.5
#4  0x7f5512186a49 in ?? () from /usr/lib/libktorrent.so.5
#5  0x7f550f0036ff in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f550b1666aa in start_thread (arg=0x7f54e7fff700) at
pthread_create.c:333
#7  0x7f550e496eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f54e77fe700 (LWP 5068)):
#0  0x7f550effe1d7 in QMutex::unlock() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#1  0x7f55121815d5 in ?? () from /usr/lib/libktorrent.so.5
#2  0x7f5512185fab in ?? () from /usr/lib/libktorrent.so.5
#3  0x7f5512186116 in ?? () from /usr/lib/libktorrent.so.5
#4  0x7f5512186a49 in ?? () from /usr/lib/libktorrent.so.5
#5  0x7f550f0036ff in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f550b1666aa in start_thread (arg=0x7f54e77fe700) at
pthread_create.c:333
#7  0x7f550e496eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f54e6ffd700 (LWP 5069)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f550f003c56 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f551218932a in ?? () from /usr/lib/libktorrent.so.5
#3  0x7f550f0036ff in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f550b1666aa in start_thread (arg=0x7f54e6ffd700) at
pthread_create.c:333
#5  0x7f550e496eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f551269e800 (LWP 5009)):
[KCrash Handler]
#6  0x7f550e3c5267 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f550e3c6eca in __GI_abort () at abort.c:89
#8  0x7f550e408c53 in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7f550e51edad "*** %s ***: %s terminated\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f550e4a8e8c in __GI___fortify_fail (msg=,
msg@entry=0x7f550e51ed44 "buffer overflow detected") at fortify_fail.c:38
#10 0x7f550e4a6e80 in __GI___chk_fail () at chk_fail.c:28
#11 0x7f550e4a8dd7 in __fdelt_chk (d=) at fdelt_chk.c:25
#12 0x7f5510967f87 in ?? () from
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4
#13 0x7f5510965c2a in ?? () from
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4
#14 0x7f551095ec27 in QAbstractSocket::waitForBytesWritten(int) () from
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4
#15 0x7f5511311a42 in ?? () from /usr/lib/libkio.so.5
#16 0x7f55113127ec in KIO::Connection::sendnow(int, QByteArray const&) ()
from /usr/lib/libkio.so.5
#17 0x7f5511312fdc in ?? () from /usr/lib/libkio.so.5
#18 0x7f55113e6ecc in KIO::Slave::accept() () from /usr/lib/libkio.so.5
#19 0x7f550f1231ec in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#20 0x7f550f1231ec in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x7f5511311ae3 in ?? () from /usr/lib/libkio.so.5
#22 0x7f550f1231ec in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x7f551056909b in KLocalSocketServer::incomingConnection(int) () from
/usr/lib/libkdecore.so.5
#24 0x7f55105d78cc in ?? () from /usr/lib/libkdecore.so.5
#25 0x7f550f1231ec in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x7f550f17056e in QSocketNotifier::activated(int) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x7f550f12c45b in QSocketNotifier::event(QEvent*) () from
/usr/lib/x86_64-

[kmymoney4] [Bug 385278] Investment management needs optimization

2017-10-01 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=385278

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
We are aware there are lots of areas for improvement in terms of handling
investments.  The current effort is all going towards completing the migration
to KDE Frameworks, and once that is complete, the team will be evaluating all
the remaining outstanding bugs and enhancement requests, and I personally hope
that some rework of investments will be included.

In addition, 4.6.4 is rather old.  You should be able to upgrade to 4.8
immediately.  4.8.1 will be released shortly with many bug fixes, and 4.8.2
will follow shortly afterwards, mainly with an fix to allow continued OFX
downloads for users who have banks who have stopped supporting Quicken 2014. 
(4.8.1 is already available for Windows.)

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

[digikam] [Bug 385280] digikam does not use the native Plasma file dialog under Plasma

2017-10-01 Thread Fabian Vogt
https://bugs.kde.org/show_bug.cgi?id=385280

Fabian Vogt  changed:

   What|Removed |Added

 CC||fab...@ritter-vogt.de

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

[www.kde.org] [Bug 385252] Plasma 5.8 announcement / source pages are not working correctly

2017-10-01 Thread awilfox
https://bugs.kde.org/show_bug.cgi?id=385252

--- Comment #4 from A. Wilcox (awilfox)  ---
Excuse me, but are you kidding?

Have you considered maybe not shipping point updates to
plasma-workspace-wallpapers and oxygen-icons when they don't change content,
instead of REMOVING the current *LTS* release from the stable mirror?

The KDE system admins do understand what the term 'LTS' means, right?  It means
"long term support".  Long term.  Not short term.

The Plasma team has definitely committed[1] to releasing more LTS patches,
through at least April 2018.  They understand what LTS means, and understand
that distributions rely on stability so that they may package your software and
bring you the users that donate to your causes and make your community so
vibrant.

Since 5.8.8 is due in a few days shy of three weeks (2017-10-18), I suppose I
don't have much of a case for you moving the 5.8.7 release back to stable,
unless there is a major issue that causes the 5.8.8 release to slip.  (It
doesn't look like this will be the case, judging from the current backlog.) 
But you *must not* "archive" 5.8.8 to "save space" until April 2018.  Is this
clear?  5.8.8 is a Long Term Support release and must be supported Long Term.

Thank you for your understanding.

[1]: https://community.kde.org/Schedules/Plasma_5

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

[digikam] [Bug 385280] digikam does not use the native Plasma file dialog under Plasma

2017-10-01 Thread Luca Beltrame
https://bugs.kde.org/show_bug.cgi?id=385280

Luca Beltrame  changed:

   What|Removed |Added

Summary|digikam does not use the|digikam does not use the
   |native Plasma dialog under  |native Plasma file dialog
   |Plasma  |under Plasma

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

[digikam] [Bug 385280] New: digikam does not use the native Plasma dialog under Plasma

2017-10-01 Thread Luca Beltrame
https://bugs.kde.org/show_bug.cgi?id=385280

Bug ID: 385280
   Summary: digikam does not use the native Plasma dialog under
Plasma
   Product: digikam
   Version: 5.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: lbeltr...@kde.org
  Target Milestone: ---

As the subject says, the file dialog is explicitly set as non-native:

https://github.com/KDE/digikam/blob/40b5bdf3139b142f3cbc6df23e10d64d9321fbc8/libs/widgets/files/dfiledialog.cpp#L37

This means that all the advanced features (and desktop consistency) of
KFileDialog are unavailable when running on Plasma, since the QPA plugin is not
used.

Is there a true, practical reason for this?

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

[valgrind] [Bug 383811] Support macOS High Sierra (10.13)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=383811

--- Comment #14 from Rhys Kidd  ---
Actually, there's a whole separate listing of Mach syscalls which have negative
numerals. Often they are presented as positive numbers in output, which lead to
the confusion here.

Mach syscall 43 was re-added in macOS 10.12 as mach_generate_activity_id.
Valgrind does not yet support it.

Anyway, tracking that unrelated issue here:
https://bugs.kde.org/show_bug.cgi?id=385279. Please comment further on that
issue at the newly created bug.

As the macOS 10.13 preliminary patch is otherwise passing basic smoke tests,
I'll land it in valgrind master later tonight. Thanks for your testing
assistance!

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

[valgrind] [Bug 385279] unhandled syscall: mach:43 (mach_generate_activity_id)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=385279

Rhys Kidd  changed:

   What|Removed |Added

 CC||bertrand.adr...@gmail.com,
   ||fxcoud...@gcc.gnu.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 Blocks||365327
   Assignee|jsew...@acm.org |rhysk...@gmail.com

--- Comment #1 from Rhys Kidd  ---
Mach syscall 43 was re-added in macOS 10.12 as mach_generate_activity_id

See further:
https://opensource.apple.com/source/xnu/xnu-4570.1.46/osfmk/mach/syscall_sw.h.auto.html


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=365327
[Bug 365327] Support macOS Sierra (10.12)
-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 365327] Support macOS Sierra (10.12)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=365327

Rhys Kidd  changed:

   What|Removed |Added

 Depends on||385279


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=385279
[Bug 385279] unhandled syscall: mach:43 (mach_generate_activity_id)
-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 385279] New: unhandled syscall: mach:43 (mach_generate_activity_id)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=385279

Bug ID: 385279
   Summary: unhandled syscall: mach:43 (mach_generate_activity_id)
   Product: valgrind
   Version: 3.14 SVN
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: rhysk...@gmail.com
  Target Milestone: ---

SYSCALL[38163,1](unix:399) sys_close ( 3 )[sync] --> Success(0x0:0x0)
SYSCALL[38163,1](mach:43) unimplemented (by the kernel) syscall: mach:43!
(ni_syscall)
 --> [pre-fail] Failure(0x4e) eq_SyscallStatus:
  {78 0 43}
  {78 0 40}

valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_SyscallStatus(UInt,
SyscallStatus *, SyscallStatus *)): the 'impossible' happened.

host stacktrace:
==90616==at 0x2580523BB: ???
==90616==by 0x25805274C: ???
==90616==by 0x258052723: ???
==90616==by 0x2580EB9D4: ???
==90616==by 0x2580EAFB9: ???
==90616==by 0x2580E91E0: ???
==90616==by 0x2580E79A0: ???
==90616==by 0x2580F985E: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 771)
==90616==at 0x10076AEFA: mach_generate_activity_id (in
/usr/lib/system/libsystem_kernel.dylib)
==90616==by 0x1003A7F57: _voucher_activity_id_allocate_slow (in
/usr/lib/system/libdispatch.dylib)
==90616==by 0x1003A7209: voucher_activity_create_with_data (in
/usr/lib/system/libdispatch.dylib)
==90616==by 0x1007CEFE2: _os_activity_create_addr (in
/usr/lib/system/libsystem_trace.dylib)
==90616==by 0x10055D219: ds_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==90616==by 0x10055CD5B: si_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==90616==by 0x10055CE3E: search_item_bynumber (in
/usr/lib/system/libsystem_info.dylib)
==90616==by 0x10055CD96: search_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==90616==by 0x10055CD5B: si_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==90616==by 0x10055C27E: getpwuid (in /usr/lib/system/libsystem_info.dylib)
==90616==by 0x10002B958: setupvals (in /bin/zsh)
==90616==by 0x10002D0C5: zsh_main (in /bin/zsh)
==90616==by 0x1003FA144: start (in /usr/lib/system/libdyld.dylib)

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

[kmymoney4] [Bug 385278] New: Investment management needs optimization

2017-10-01 Thread Henser Deas
https://bugs.kde.org/show_bug.cgi?id=385278

Bug ID: 385278
   Summary: Investment management needs optimization
   Product: kmymoney4
   Version: unspecified
  Platform: MS Windows
OS: Linux
Status: UNCONFIRMED
  Keywords: needs_verification
  Severity: critical
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: bruno.gla...@gmx.de
  Target Milestone: ---

- Calculation of investment interest partly wrong (e.g. clearly positive
interest was given negative)
- Please include all categories of expenses for calculation of investment
interest
- Please include all categories of income for calculation of investment
interest
- Please include an option for visualization of individual investment price
graph (now I can only choose individual accounts)
I am using KMyMoney 4.6.4 both on Kubuntu 14.06 and Win7

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

[kmymoney4] [Bug 385274] Need to update Quicken versions in libofx ofx import

2017-10-01 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=385274

Ralf Habacker  changed:

   What|Removed |Added

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

--- Comment #3 from Ralf Habacker  ---
(In reply to Jack from comment #2)
> Should this also be cherry picked to master, or will the user ability to add
> versions be sufficient?

The related source in master looks equal to 4.8, so I would say yes
my 2cent

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

[valgrind] [Bug 383811] Support macOS High Sierra (10.13)

2017-10-01 Thread Adrien Bertrand
https://bugs.kde.org/show_bug.cgi?id=383811

--- Comment #13 from Adrien Bertrand  ---
(In reply to Adrien Bertrand from comment #12)
> (In reply to Rhys Kidd from comment #11)
> > Can you add '--trace-syscalls=yes' to your valgrind and report the lines
> > prior to the one that contains eq_SyscallStatus?
> 
> There you go:
> 
> SYSCALL[38163,1](unix:399) sys_close ( 3 )[sync] --> Success(0x0:0x0)
> SYSCALL[38163,1](mach:43) unimplemented (by the kernel) syscall: mach:43!
> (ni_syscall)
>  --> [pre-fail] Failure(0x4e) eq_SyscallStatus:
>   {78 0 43}
>   {78 0 40}

Same thing trying valgrind on bash (syscall 43).
Isn't that supposed to be getegid, according to
https://github.com/apple/darwin-xnu/blob/0a798f6738bc1db01281fc08ae024145e84df927/bsd/kern/syscalls.master#L93
?

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

[valgrind] [Bug 383811] Support macOS High Sierra (10.13)

2017-10-01 Thread Adrien Bertrand
https://bugs.kde.org/show_bug.cgi?id=383811

--- Comment #12 from Adrien Bertrand  ---
(In reply to Rhys Kidd from comment #11)
> Can you add '--trace-syscalls=yes' to your valgrind and report the lines
> prior to the one that contains eq_SyscallStatus?

There you go:

SYSCALL[38163,1](unix:399) sys_close ( 3 )[sync] --> Success(0x0:0x0)
SYSCALL[38163,1](mach:43) unimplemented (by the kernel) syscall: mach:43!
(ni_syscall)
 --> [pre-fail] Failure(0x4e) eq_SyscallStatus:
  {78 0 43}
  {78 0 40}

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

[kmymoney4] [Bug 385274] Need to update Quicken versions in libofx ofx import

2017-10-01 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=385274

--- Comment #2 from Jack  ---
Should this also be cherry picked to master, or will the user ability to add
versions be sufficient?

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

[skrooge] [Bug 385277] New: Wrong budget for split-operations with unaligned dates

2017-10-01 Thread Bernhard Scheirle
https://bugs.kde.org/show_bug.cgi?id=385277

Bug ID: 385277
   Summary: Wrong budget for split-operations with unaligned dates
   Product: skrooge
   Version: Trunk from git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: bernhard+...@scheirle.de
CC: steph...@mankowski.fr
  Target Milestone: ---

Created attachment 108122
  --> https://bugs.kde.org/attachment.cgi?id=108122&action=edit
Example skrooge file

If the sub-operations of a split-operation are using a different date than the
split-operation itself, the budget for these sub-operations gets calculated
wrongly:
The sub-operations get treated with the date of the split-operation.

Example (also see attached skrooge file):
* Monthly budget for category "Cat1" is 50€

* Standard-operation:
* * 2017.09.25 - Cat1 - 50€ - [A]

* Split-operation with two sub-operations:
* * 2017.09.29 - 100€
* * * 2017.10.01 - Cat1 - 50€ - [B]
* * * 2017.10.01 - Cat2 - 50€

Actual Result:
The amount for the Cat1 budget is:
2017.09 - 100€ (A + B) (Budget contains operations of September and October)
2017.10 -   0€

Expected Result:
The amount for the Cat1 budget is:
2017.09 - 50€ (A)
2017.10 - 50€ (B)

Note: Reports do use the date of the sub-operations correctly.

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

[krita] [Bug 385276] New: Krita canvas lags on larger displays on macOS

2017-10-01 Thread Bernhard Liebl
https://bugs.kde.org/show_bug.cgi?id=385276

Bug ID: 385276
   Summary: Krita canvas lags on larger displays on macOS
   Product: krita
   Version: unspecified
  Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bernhard.li...@gmx.org
  Target Milestone: ---

Krita's graphics output on macOS is relatively slow, and it is very slow on 5k
iMacs.

This seems to be related to QT's QWidget implementation on macOS. And this is
probably a well-known problem.

If not, this ticket can keep track of infos about QT's state of things. 

Two useful pointers I found:

https://forum.qt.io/topic/59578/rendering-performance-problems-on-imac-with-retina-5k/24

https://bugreports.qt.io/browse/QTBUG-44228

As QT's OpenGL compositing internally happens with and without Krita's OpenGL
canvas, switching to Krita's raster canvas does not make a difference.

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

[valgrind] [Bug 383199] unhandled amd64-darwin syscall: unix:463 (openat)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=383199

Rhys Kidd  changed:

   What|Removed |Added

Summary|valgrind crash on unhanded  |unhandled amd64-darwin
   |syscall called from |syscall: unix:463 (openat)
   |libsqlite3.dylib|

--- Comment #4 from Rhys Kidd  ---
irad, can you attach or link to the patch you wrote locally when trying to
address the missing openat syscall? That will allow me to figure out why it is
still not working for you.

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

[valgrind] [Bug 383811] Support macOS High Sierra (10.13)

2017-10-01 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=383811

--- Comment #11 from Rhys Kidd  ---
(In reply to Adrien Bertrand from comment #10)
> However, when trying something more complex (valgrind /usr/bin/gcc -v), I
> get the same issue as paragraph 3 of comment #3 here (valgrind:
> m_syswrap/syswrap-main.c:438 (Bool eq_SyscallStatus(UInt, SyscallStatus *,
> SyscallStatus *)): the 'impossible' happened.)

Can you add '--trace-syscalls=yes' to your valgrind and report the lines prior
to the one that contains eq_SyscallStatus?

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=179678

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[dolphin] [Bug 189302] Unmounting busy device in dolphin: missing information who is blocking

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=189302

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[dolphin] [Bug 216425] rename file systems label

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=216425

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kmymoney4] [Bug 385274] Need to update Quicken versions in libofx ofx import

2017-10-01 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=385274

Ralf Habacker  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kmy
   ||money/75efcd673f8a750681ba3
   ||5cc6e12a4d6d13ca474
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||4.8.2

--- Comment #1 from Ralf Habacker  ---
Git commit 75efcd673f8a750681ba35cc6e12a4d6d13ca474 by Ralf Habacker, on behalf
of Jack Ostroff.
Committed on 01/10/2017 at 20:25.
Pushed by habacker into branch '4.8'.

Added two most recent versions of Quicken for Windows for identity for OFX
direct connect.

Reviewers: #kmymoney

Differential Revision: https://phabricator.kde.org/D8096

FIXED-IN:4.8.2

M  +3-0kmymoney/plugins/ofximport/dialogs/mymoneyofxconnector.cpp

https://commits.kde.org/kmymoney/75efcd673f8a750681ba35cc6e12a4d6d13ca474

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

[kdeplasma-addons] [Bug 364309] don't work in breeze dark

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=364309

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[krita] [Bug 363903] Krita crashes whenever I try to draw on canvas.

2017-10-01 Thread Amber
https://bugs.kde.org/show_bug.cgi?id=363903

--- Comment #22 from Amber  ---
It won't let me draw on the canvas. The canvas opens, but my brushes and mouse
won't even show up. I can't draw on existing canvases either.

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

[krita] [Bug 363903] Krita crashes whenever I try to draw on canvas.

2017-10-01 Thread Amber
https://bugs.kde.org/show_bug.cgi?id=363903

--- Comment #21 from Amber  ---
It won't let me draw on the canvas. The canvas opens, but my brushes and mouse
won't even show up. I can't draw on existing canvases either.

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

[kate] [Bug 385275] New: When exiting the application don't force user to save, unsaved document only save it as temporary

2017-10-01 Thread Piotr Mierzwinski
https://bugs.kde.org/show_bug.cgi?id=385275

Bug ID: 385275
   Summary: When exiting the application don't force user to save,
unsaved document only save it as temporary
   Product: kate
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

When exiting the application don't force user to save, unsaved document only
save it as temporary/"not saved" in some safe place (maybe in the same
directory as original one). And with next run of Kate just restore it, marked
as unsaved.

This situation is a bit annoying when user want to leave system (login off,
shut down computer) and from Kate pops up window - "Not saved document" which
stops all shutting down process :/.

I met this feature in Notepad++ (one of the most popular text editor for
Windows).

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

[kwin] [Bug 376104] Quick tile window to any screen edge or corner de-maximizes the window without tiling as a first action since plasma 5.9.0

2017-10-01 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=376104

--- Comment #20 from Martin Flöser  ---
(In reply to Nate Graham from comment #19)
> Martin, since we do have test cases for X11 now, is this something we can
> get submitted to Phabricator as a patch?

No as it does not address the reasons on why the code was moved in first place.
Just reverting a commit does not fix things, it causes issues in other places.

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

[krita] [Bug 363903] Krita crashes whenever I try to draw on canvas.

2017-10-01 Thread Amber
https://bugs.kde.org/show_bug.cgi?id=363903

Amber  changed:

   What|Removed |Added

 CC||amberyode...@gmail.com

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

[kmymoney4] [Bug 385274] New: Need to update Quicken versions in libofx ofx import

2017-10-01 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=385274

Bug ID: 385274
   Summary: Need to update Quicken versions in libofx ofx import
   Product: kmymoney4
   Version: 4.8.1
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: ostrof...@users.sourceforge.net
  Target Milestone: ---

In the OFX Details tab of the Online settings tab of the Edit Account dialog,
there is a dropdown to select how KMM identifies itself to the OFX server. 
Currently, the highest version is "Quicken Windows 2014" (identifying as
QWIN2300.)  Some banks have already stopped supporting this version and require
a higher version.  This currently blocks OFX direct connect import for users of
those banks.  

I will submit a patch through Phabricator to include identification for the
2015 and 2016 versions.  Hopefully by the time the Frameworks migration is
complete, it will be possible for users to add new versions without needing to
recompile.  However, please comment if I should also patch Master with the same
additions.

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

[kwin] [Bug 385260] Regression: Virtual desktops not working

2017-10-01 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=385260

Martin Flöser  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kwi
   ||n/f988a5f6547b92d68f9875342
   ||52497ba618c4ff1

--- Comment #3 from Martin Flöser  ---
Git commit f988a5f6547b92d68f987534252497ba618c4ff1 by Martin Flöser.
Committed on 01/10/2017 at 19:56.
Pushed by graesslin into branch 'master'.

Reload VirtualDesktop settings after passing RootInfo on VirtualDesktopManager

Summary:
The load method and updateLayout ensure the virtual desktop information
is synced to RootInfo and thus to other X11 applications. Thus we need
to call it again when initing X11.

Test Plan: Not tested as I'm on Wayland, but given the changes it's obvious.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D8086

M  +5-4virtualdesktops.h
M  +5-1workspace.cpp

https://commits.kde.org/kwin/f988a5f6547b92d68f987534252497ba618c4ff1

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

[kwin] [Bug 376104] Quick tile window to any screen edge or corner de-maximizes the window without tiling as a first action since plasma 5.9.0

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=376104

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasma-integration] [Bug 385273] Dragging QListWidgetItems with icons crashes under Plasma, not other envs

2017-10-01 Thread JanKusanagi
https://bugs.kde.org/show_bug.cgi?id=385273

JanKusanagi  changed:

   What|Removed |Added

 CC||jan-b...@gmx.co.uk

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

[plasma-integration] [Bug 385273] Dragging QListWidgetItems with icons crashes under Plasma, not other envs

2017-10-01 Thread JanKusanagi
https://bugs.kde.org/show_bug.cgi?id=385273

--- Comment #1 from JanKusanagi  ---
Just in case, I forgot to add that I can reproduce this consistently, every
time.

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

[plasma-integration] [Bug 385273] New: Dragging QListWidgetItems with icons crashes under Plasma, not other envs

2017-10-01 Thread JanKusanagi
https://bugs.kde.org/show_bug.cgi?id=385273

Bug ID: 385273
   Summary: Dragging QListWidgetItems with icons crashes under
Plasma, not other envs
   Product: plasma-integration
   Version: 5.10.4
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: jan-b...@gmx.co.uk
  Target Milestone: ---

Created attachment 108121
  --> https://bugs.kde.org/attachment.cgi?id=108121&action=edit
Backtrace, Qt 5.9.1, KF 5.38, Plasma 5.10.4

I noticed a crash in a program I develop, when dragging certain items (the ones
that have an icon) from a QListWidget to another.

I made a very small proof of concept, here:
https://gitlab.com/bugpocs/WidgetListCrash

The crash looks like this, triggered after dragging one of the items with icon
from the left-side list to the right-side list:


./WidgetListCrash 
Trying to construct an instance of an invalid type, type id: 6553705
Trying to construct an instance of an invalid type, type id: 788558336
Trying to construct an instance of an invalid type, type id: 524358
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)



Dragging the items with no icon works fine.

I've tested this under Mageia, Debian and Archlinux, some i386, some x86_64,
some under Plasma, some under other environments.


I pondered reporting this to Qt directly, but the crash does NOT happen under
Xfce or Mate, for instance, so I started to suspect KDEPlasmaPlatformTheme.so.
The crash also doesn't happen under Plasma, IF I run the program with
XDG_CURRENT_DESKTOP=something-other-than-KDE. Besides Plasma, the crash also
happens under LXQt, unless doing the above trick.

So basically, it seems like the crash is averted when Qt believes the
environment is GTK-based.


I don't know if this is due to something Qt does "directly", based on some of
the desktop-depending stuff done, or instance, here:
http://code.qt.io/cgit/qt/qtbase.git/tree/src/platformsupport/themes/genericunix/qgenericunixthemes.cpp
http://code.qt.io/cgit/qt/qtbase.git/tree/src/platformsupport/services/genericunix/qgenericunixservices.cpp

... but after talking about this on #kde-devel, I've decided to report it here,
and hopefully the experts will know ;)

Thank you for your time!

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

[kdenlive] [Bug 379351] i cannot make a showslide clip and i cannot render a clip with jpg images

2017-10-01 Thread farid
https://bugs.kde.org/show_bug.cgi?id=379351

--- Comment #7 from farid  ---
(In reply to DeMus from comment #6)
> Also see https://bugs.kde.org/show_bug.cgi?id=376464 which tells about the
> same bug. It's not only Windows, it is also the linux version. I don't know
> when it started, which Kdenlive version, but suddenly it didn't work
> anymore. I now have a huge project which I can't finish becuase of it.
> Converting all images from jpg to png is possible but a lot of extra work.
> Is it possible somebody takes a look at this? Thank you.

I am using the linux version and don't have any issues. Afaik it is a windows
only problem... 

Which versions of MLT and Kdenlive are you using? How did you install them?

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

[plasmashell] [Bug 380384] Plasma-Wayland completely freezing on Nouveau driver

2017-10-01 Thread Aleksey Samoilov
https://bugs.kde.org/show_bug.cgi?id=380384

Aleksey Samoilov  changed:

   What|Removed |Added

Version|5.10.0  |master

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

[kaffeine] [Bug 385272] New: Instant recording does not work, while scheduled does.

2017-10-01 Thread Skarmoutsos Vangelis
https://bugs.kde.org/show_bug.cgi?id=385272

Bug ID: 385272
   Summary: Instant recording does not work, while scheduled does.
   Product: kaffeine
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: skarmouts...@gmail.com
  Target Milestone: ---

When pressing Instant recording button an overlay message informs that
recording started and if pressed again it informs that recording stopped, but
no file is created.

When schedule a recording the corresponding file is created normally.

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

[digikam] [Bug 378082] Several small new bugs in Geolocation Editor

2017-10-01 Thread Jens
https://bugs.kde.org/show_bug.cgi?id=378082

--- Comment #8 from Jens  ---
regarding "use file date when metadata is not available", I assume this means
"filesystem date".
If so, how about using the Digikam DB datetime stamp? This might be different
from the filesystem date.

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

[digikam] [Bug 385148] Form fields are almost invisible using most "dark" shipped themes

2017-10-01 Thread Jens
https://bugs.kde.org/show_bug.cgi?id=385148

--- Comment #4 from Jens  ---
Fusion. only Fusion and Windows are available.

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

[plasmashell] [Bug 385271] New: Resizing taskbar panel under wayland crashes plasmashell

2017-10-01 Thread Kevin Liu
https://bugs.kde.org/show_bug.cgi?id=385271

Bug ID: 385271
   Summary: Resizing taskbar panel under wayland crashes
plasmashell
   Product: plasmashell
   Version: 5.10.95
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kevin@potatofrom.space
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.95)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.12.0-1-amd-staging x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed: resizing the height of the
task manager panel crashes plasmashell every time when the resize finishes.

- Custom settings of the application: Running under Wayland on Arch Linux,
using KDE 5.10.95 from kde-unstable repository. I also have a triple-monitor
setup -- I'm resizing the taskbar on the middle monitor.

This may not be Plasma's problem, as I'm also running mesa-git and AMD's 4.12
staging kernel, but I thought I'd post it anyway.

(Props to the fine Wayland support, by the way -- it's quite usable nowadays.
Still some bugs, though!)

The crash can be reproduced every time.

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

Thread 61 (Thread 0x7fb83050c700 (LWP 16653)):
[KCrash Handler]
#5  0x7fb9b3062c81 in wl_proxy_create_wrapper () at
/usr/lib/libwayland-client.so.0
#6  0x7fb9956647aa in  () at /usr/lib/libEGL_mesa.so.0
#7  0x7fb99565170f in  () at /usr/lib/libEGL_mesa.so.0
#8  0x7fb995f8bf4d in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#9  0x7fb995f8a4c5 in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#10 0x7fb9b5266a39 in QOpenGLContext::makeCurrent(QSurface*) () at
/usr/lib/libQt5Gui.so.5
#11 0x7fb9b85f2f86 in  () at /usr/lib/libQt5Quick.so.5
#12 0x7fb9b85fac46 in  () at /usr/lib/libQt5Quick.so.5
#13 0x7fb9b85f9e5b in  () at /usr/lib/libQt5Quick.so.5
#14 0x7fb9b85fa254 in  () at /usr/lib/libQt5Quick.so.5
#15 0x7fb9b485e13b in  () at /usr/lib/libQt5Core.so.5
#16 0x7fb9b3a1708a in start_thread () at /usr/lib/libpthread.so.0
#17 0x7fb9b416a1bf in clone () at /usr/lib/libc.so.6

Thread 60 (Thread 0x7fb830d0d700 (LWP 16652)):
#0  0x7fb9b3a1d38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb90f25e77c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7fb90f25e688 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7fb9b3a1708a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fb9b416a1bf in clone () at /usr/lib/libc.so.6

Thread 59 (Thread 0x7fb8322bd700 (LWP 16651)):
#0  0x7fb9b3a1d38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb9b485f5cc in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb9b85f9dca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fb9b85fa254 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fb9b485e13b in  () at /usr/lib/libQt5Core.so.5
#5  0x7fb9b3a1708a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fb9b416a1bf in clone () at /usr/lib/libc.so.6

Thread 58 (Thread 0x7fb832abe700 (LWP 16650)):
#0  0x7fb9b3a1d38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb90f25e77c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7fb90f25e688 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7fb9b3a1708a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fb9b416a1bf in clone () at /usr/lib/libc.so.6

Thread 57 (Thread 0x7fb833f0c700 (LWP 16649)):
#0  0x7fb9b415b7d8 in read () at /usr/lib/libc.so.6
#1  0x7fb9aea85730 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fb9aea416eb in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fb9aea41bb0 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fb9aea41d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fb9b4a9c064 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fb9b4a3ffdb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fb9b48593ee in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fb9b79c83d9 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7fb9b485e13b in  () at /usr/lib/libQt5Core.so.5
#10 0x7fb9b3a1708a in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fb9b416a1bf in clone () at /usr/lib/libc.so.6

Thread 56 (Thread 0x7fb887fff700 (LWP 16564)):
#0  0x7fb9b3a1d38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0

[digikam] [Bug 385269] [DK 5.7] database migration sqlite -> mysql external server fails

2017-10-01 Thread Marcel Derioss
https://bugs.kde.org/show_bug.cgi?id=385269

Marcel Derioss  changed:

   What|Removed |Added

 CC||mader...@gmail.com

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

[plasma-pa] [Bug 385270] New: Disable volume slider by scroll function optionally

2017-10-01 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=385270

Bug ID: 385270
   Summary: Disable volume slider by scroll function optionally
   Product: plasma-pa
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: shaloksha...@protonmail.ch
CC: plasma-b...@kde.org
  Target Milestone: ---

I scroll on my laptop with two fingers on the touchpad, I think this is quite
common. So, when I do this in plasma-pa, to reach the different streams (there
are quite a lot here) does this change the actual volume instead scrolling
down.

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

[digikam] [Bug 385269] New: [DK 5.7] database migration sqlite -> mysql external server fails

2017-10-01 Thread Marcel Derioss
https://bugs.kde.org/show_bug.cgi?id=385269

Bug ID: 385269
   Summary: [DK 5.7] database migration sqlite -> mysql external
server fails
   Product: digikam
   Version: 5.7.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Database-Migration
  Assignee: digikam-bugs-n...@kde.org
  Reporter: mader...@gmail.com
  Target Milestone: ---

Conditions: DK-5.7 Archlinux x86_64 Mariadb-10.1.28-1
DK works fine with sqlite.
Message with database migration tool sqlite -> mysql external server:
'Details: Cannot add or update a child row: a foreign key constraint fails
(`mydk`.`ImageInformation`, CONSTRAINT `ImageInformation_Images` FOREIGN KEY
(`imageid`) REFERENCES `Images` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)'

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

[digikam] [Bug 384492] Error migrating database from SQLite to MySQL external

2017-10-01 Thread Marcel Derioss
https://bugs.kde.org/show_bug.cgi?id=384492

Marcel Derioss  changed:

   What|Removed |Added

 CC||mader...@gmail.com

--- Comment #2 from Marcel Derioss  ---
(In reply to Mattia from comment #0)
> I'm trying to migrate my Digikam DB from SQLite to an external MySQL server
> (MariaDB 5.5.44 running on Qnap NAS).
> 
> The process fails at 91% of "Copy ImageInformation" step with the error
> "Cannot add or update a child row: a foreign key constraint fails
> (`digikam`.`ImageInformation`, CONSTRAINT `ImageInformation_Images` FOREIGN
> KEY (`imageid`) REFERENCES `Images` (`id`) ON DELETE CASCADE ON UPDATE
> CASCADE)"

I got today same fail message with database migration tool sqlite -> mysql
external server:
'Details: Cannot add or update a child row: a foreign key constraint fails
(`mydk`.`ImageInformation`, CONSTRAINT `ImageInformation_Images` FOREIGN KEY
(`imageid`) REFERENCES `Images` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)'
Conditions: DK-5.7 Archlinux x86_64 Mariadb-10.1.28-1
DK works fine with sqlite.

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

[plasmashell] [Bug 385164] [Wayland] No starting animation of application

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=385164

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kile] [Bug 385261] App crashes while opening a non root or master tex File

2017-10-01 Thread Michel Ludwig
https://bugs.kde.org/show_bug.cgi?id=385261

--- Comment #1 from Michel Ludwig  ---
Can you please attach a small test case that demonstrates the problem? (or a
crash backtrace) Thanks!

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

[kwin] [Bug 385214] Color scheme setting broken for QtWayland XdgShellV6 windows

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=385214

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kile] [Bug 385268] KILE crashes everytime with mageia 6

2017-10-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=385268

--- Comment #1 from nougu...@orange.fr ---
Crash confirmed with mageia 6

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

[kile] [Bug 385268] New: KILE crashes everytime with mageia 6

2017-10-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=385268

Bug ID: 385268
   Summary: KILE crashes everytime with mageia 6
   Product: kile
   Version: 2.1.3
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: editor
  Assignee: michel.lud...@kdemail.net
  Reporter: nougu...@orange.fr
  Target Milestone: ---

Mageia 6
New hard disk, no OS before - 
AMD 64, 1 core for this experiment
It is the 3rd PC to test kile crash !
Error msg : "no editor component found"

=> crashes EVERYTIME, impossible to use kile (with kate) with mga 6
NO crash with mga 5 or less.


Thread 1 (Thread 0x7f2f4ee64840 (LWP 7431)):
[KCrash Handler]
#6  0x005d019c in KileDocument::Manager::fileOpen(KUrl const&, QString
const&, int) ()
#7  0x005d154c in KileDocument::Manager::fileSelected(KUrl const&) ()
#8  0x004cbc7c in Kile::openDocument(QString const&) ()
#9  0x006406c3 in MainAdaptor::qt_metacall(QMetaObject::Call, int,
void**) ()
#10 0x7f2f4c0486b5 in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QList const&, int) () from /lib64/libQtDBus.so.4
#11 0x7f2f4c049bab in QDBusConnectionPrivate::activateCall(QObject*, int,
QDBusMessage const&) () from /lib64/libQtDBus.so.4
#12 0x7f2f4c04a897 in
QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&,
QDBusMessage const&, int) () from /lib64/libQtDBus.so.4
#13 0x7f2f4c04aa9b in QDBusActivateObjectEvent::placeMetaCall(QObject*) ()
from /lib64/libQtDBus.so.4
#14 0x7f2f4c65a651 in QObject::event(QEvent*) () from /lib64/libQtCore.so.4
#15 0x7f2f4b5846ec in QWidget::event(QEvent*) () from /lib64/libQtGui.so.4
#16 0x7f2f4b946873 in QMainWindow::event(QEvent*) () from
/lib64/libQtGui.so.4
#17 0x7f2f4d1c7349 in KXmlGuiWindow::event(QEvent*) () from
/lib64/libkdeui.so.5
#18 0x7f2f4b530ffc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQtGui.so.4
#19 0x7f2f4b537acc in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQtGui.so.4
#20 0x7f2f4d0d0b9a in KApplication::notify(QObject*, QEvent*) () from
/lib64/libkdeui.so.5
#21 0x7f2f4c6418ed in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /lib64/libQtCore.so.4
#22 0x7f2f4c644b4e in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQtCore.so.4
#23 0x7f2f4c66fbfe in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQtCore.so.4
#24 0x7f2f46793ac7 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#25 0x7f2f46793cf8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#26 0x7f2f46793d9c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#27 0x7f2f4c66fd6e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQtCore.so.4
#28 0x7f2f4b5d44a6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() from /lib64/libQtGui.so.4
#29 0x7f2f4c6402b1 in
QEventLoop::processEvents(QFlags) () from
/lib64/libQtCore.so.4
#30 0x7f2f4c6405c5 in
QEventLoop::exec(QFlags) () from
/lib64/libQtCore.so.4
#31 0x7f2f4b9e63ec in QDialog::exec() () from /lib64/libQtGui.so.4
#32 0x004ce111 in Kile::slotPerformCheck() ()
#33 0x7f2f4c654b00 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /lib64/libQtCore.so.4
#34 0x7f2f4b52b4d2 in QAction::triggered(bool) () from /lib64/libQtGui.so.4
#35 0x7f2f4b52c677 in QAction::activate(QAction::ActionEvent) () from
/lib64/libQtGui.so.4
#36 0x7f2f4b9670b9 in
QMenuPrivate::activateCausedStack(QList > const&, QAction*,
QAction::ActionEvent, bool) () from /lib64/libQtGui.so.4
#37 0x7f2f4b96b269 in QMenuPrivate::activateAction(QAction*,
QAction::ActionEvent, bool) () from /lib64/libQtGui.so.4
#38 0x7f2f4d190382 in KMenu::mouseReleaseEvent(QMouseEvent*) () from
/lib64/libkdeui.so.5
#39 0x7f2f4b583fb0 in QWidget::event(QEvent*) () from /lib64/libQtGui.so.4
#40 0x7f2f4b96f283 in QMenu::event(QEvent*) () from /lib64/libQtGui.so.4
#41 0x7f2f4b530ffc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQtGui.so.4
#42 0x7f2f4b537c33 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQtGui.so.4
#43 0x7f2f4d0d0b9a in KApplication::notify(QObject*, QEvent*) () from
/lib64/libkdeui.so.5
#44 0x7f2f4c6418ed in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /lib64/libQtCore.so.4
#45 0x7f2f4b5372cd in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/lib64/libQtGui.so.4
#46 0x7f2f4b5ae1ac in QETWidget::translateMouseEvent(_XEvent const*) ()
from /lib64/libQtGui.so.4
#47 0x7f2f4b5ac1ed in QApplication::x11ProcessEvent(_XEvent*) () from
/lib64/libQtGui.so.4
#48 0x7f2f4b5d43e2 in x11EventSourceDispatch(_GSour

[kwin] [Bug 385215] Appmenu broken for QtWayland XdgShellV6 windows

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=385215

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasmashell] [Bug 385231] Kwin shortcut: Maximize window, it should not be applied to the Application Launcher

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=385231

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasma-browser-integration] [Bug 385253] Display the domain title in plasma-pa

2017-10-01 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=385253

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Theo
https://bugs.kde.org/show_bug.cgi?id=376966

Theo  changed:

   What|Removed |Added

 CC||alpha0...@yahoo.de

--- Comment #6 from Theo  ---
I have this problem on openSUSE Tumbleweed, KDE Plasma 5.10.5. Keystrokes are
registered only sporadically in all KDE applications as described in
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721 (that
bug seems to be about input fields only, though). This happens often after my
system has been stalled when running out of memory. Once my system is
responding again, the IBus daemon for the desktop user is gone. Running
'ibus-daemon --xim -d' as user fixes the keyboard input problem.

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

[okular] [Bug 374539] Crash when viewing a rotated PDF

2017-10-01 Thread Mariusz Libera
https://bugs.kde.org/show_bug.cgi?id=374539

Mariusz Libera  changed:

   What|Removed |Added

 CC||mariusz.lib...@gmail.com

--- Comment #4 from Mariusz Libera  ---
Created attachment 108120
  --> https://bugs.kde.org/attachment.cgi?id=108120&action=edit
journald log of okular crashing

I've also experienced Okular crashing while rotating some pdf files, but it's
hard to reproduce - not that it's particularly rare but I don't know what
triggers it, it seems random. I can open some file and click the rotate button
and it will crash immediately and then open the same file again and rotate
multiple times without okular crashing.

This is what I see in dmesg:
[602308.448068] Queue(0x55fab8e[32636]: segfault at 7f6c80e06a50 ip
7f6c80e06a50 sp 7f6c4ec47d98 error 15 in
libQt5Gui.so.5.9.1[7f6c80dfe000+11000]
[602379.844094] Queue(0x55e4077[32683]: segfault at 7fb0a119aa50 ip
7fb0a119aa50 sp 7fb06e7fbd98 error 15 in
libQt5Gui.so.5.9.1[7fb0a1192000+11000]
[602421.140441] Queue(0x55ef002[374]: segfault at 7f3786826a50 ip
7f3786826a50 sp 7f37597c1d98 error 15 in
libQt5Gui.so.5.9.1[7f378681e000+11000]
[602434.107134] Queue(0x5632d6e[715]: segfault at 7fb6813eda50 ip
7fb6813eda50 sp 7fb6427fbd98 error 15 in
libQt5Gui.so.5.9.1[7fb6813e5000+11000]
[602461.503357] okular[734]: segfault at 0 ip   (null) sp
7ffdbe2448e8 error 14 in okular[5646f282c000+2]
[602965.542151] Queue(0x5618bd6[1075]: segfault at 7f94da75ba50 ip
7f94da75ba50 sp 7f94ad714d98 error 15 in
libQt5Gui.so.5.9.1[7f94da753000+11000]
[603058.734477] Queue(0x5596fa8[1539]: segfault at 20 ip 7feb27384b5c sp
7feb1aa75d98 error 4 in libOkular5Core.so.7.0.0[7feb272f8000+f1000]
[603078.711396] Queue(0x55ffae2[1577]: segfault at 7f719655ea50 ip
7f719655ea50 sp 7f7168ca9d98 error 15 in
libQt5Gui.so.5.9.1[7f7196556000+11000]

I've also included some traces from journald, I don't know how useful they are.

Archlinux package:
Name: okular
Version : 17.08.1-1

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

[ark] [Bug 385028] Attempting to extract password-protected 7zip file with wrong password crashes Ark

2017-10-01 Thread Martin Unzner
https://bugs.kde.org/show_bug.cgi?id=385028

Martin Unzner  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Unzner  ---
Me neither, strangely enough. Must have been something wrong with my setup. I
will  open another ticket if the issue reoccurs. Thanks!

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

[plasma4] [Bug 385267] KDE tar protocol copies entire archive to /tmp/kde-user/ktar-n[pidof kio_archive].tar

2017-10-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=385267

ask4supp...@email.cz changed:

   What|Removed |Added

 CC||ask4supp...@email.cz

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

[plasma4] [Bug 385267] New: KDE tar protocol copies entire archive to /tmp/kde-user/ktar-n[pidof kio_archive].tar

2017-10-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=385267

Bug ID: 385267
   Summary: KDE tar protocol copies entire archive to
/tmp/kde-user/ktar-n[pidof kio_archive].tar
   Product: plasma4
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ask4supp...@email.cz
  Target Milestone: ---

Is it really necessary to copy the entire archive instead of extracting it
directly to a folder of similar name (e. g. /tmp/kde-user/ktar-n[pidof
kio_archive)?

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

[kate] [Bug 384644] KATE tab bar no longer configurable

2017-10-01 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=384644

--- Comment #3 from Dominik Haumann  ---
Are you talking about the multiline-tabbar, or the toolbar-like tabbar?

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

[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction

2017-10-01 Thread Phil KdeBugs
https://bugs.kde.org/show_bug.cgi?id=385251

--- Comment #3 from Phil KdeBugs  ---
I just noticed(!) checking 381000 how old my version seems to be , even though
this is clean install of stretch. 

I'm happy to try a more recent version (if this is fixed), though it does seem
quite severe...

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

[krita] [Bug 385265] Bezier node handles are too small for HD tablets

2017-10-01 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=385265

Alvin Wong  changed:

   What|Removed |Added

  Component|tablet support  |general
 CC||alvinhoc...@gmail.com
   Platform|Other   |MS Windows

--- Comment #1 from Alvin Wong  ---
Well... there is an option to enable Hi-DPI support, that's in General->Window.
The canvas render now acts a bit weird (though I have some patches for that),
but the general UI scaling is handled pretty nicely by Qt.

With that resolution it's probably either a Surface Pro 4 or the 2017 Surface
Pro, right? The default 200% scaling works fine for me. Are there anything that
you find to be unsatisfactory (other than the canvas being blurry)?

(Oh high density displays applications are basically unusable without any
Hi-DPI support enabled, that's to be expected.)

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

[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction

2017-10-01 Thread Phil KdeBugs
https://bugs.kde.org/show_bug.cgi?id=385251

--- Comment #2 from Phil KdeBugs  ---
Hi,

I just installed the dbsyms for the following:

libqt5core5a-dbgsym
libqt5gui-dbgsym
libqt5gui5-dbgsym

Version: 5.7.1+dfsg-3+b1

I will try and grab a better annotated trace.

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

[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg

2017-10-01 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=372447

--- Comment #9 from David Edmundson  ---
Please see the memory leak and upstream Qt bug in 381000

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

[plasmashell] [Bug 375860] Crash in QTXML Patterns parsing

2017-10-01 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=375860

David Edmundson  changed:

   What|Removed |Added

 CC||skstel...@gmail.com

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

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


[plasmashell] [Bug 385266] Plasma crashed when it was in screen saver mode

2017-10-01 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=385266

David Edmundson  changed:

   What|Removed |Added

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

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


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

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

  1   2   >