[kate] [Bug 369138] Regex no longer available

[via KDE Bugzilla]

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

--- Comment #2 from daobr...@redhat.com ---
I ran this:
yum downgrade kate --allowerasing

Running transaction
  Downgrading : kate-16.04.1-1.fc24.x86_64 
   1/4
  Downgrading : kate-plugins-16.04.1-1.fc24.x86_64 
   2/4
  Erasing : kate-plugins-16.08.1-1.fc24.x86_64 
   3/4
  Erasing : kate-16.08.1-1.fc24.x86_64 
   4/4
  Verifying   : kate-16.04.1-1.fc24.x86_64 
   1/4
  Verifying   : kate-plugins-16.04.1-1.fc24.x86_64 
   2/4
  Verifying   : kate-16.08.1-1.fc24.x86_64 
   3/4
  Verifying   : kate-plugins-16.08.1-1.fc24.x86_64 
   4/4

Downgraded:
  kate.x86_64 16.04.1-1.fc24  
kate-plugins.x86_64 16.04.1-1.fc24

Complete!

I now have regex, case sensitive search, and all my faves back~! :)

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

[kactivitymanagerd] [Bug 368870] activity switcher shown twice in clone mode

[Kai Krakow via KDE Bugzilla]

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

--- Comment #5 from Kai Krakow  ---
(In reply to Ivan Čukić from comment #1)
> Thanks (especially for taking the time to record the video).
> 
> I'll see to replicate this - might be a problem of the new screen management
> stuff.

I think this was already in plasma 5.6 - maybe earlier but I cannot recall. The
video was also not recorded with the most recent plasma version. But the
problem is still the same.

I'll wait for 5.8 as suggested in comment #4.

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

[kate] [Bug 369138] Regex no longer available

[via KDE Bugzilla]

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

--- Comment #1 from daobr...@redhat.com ---
Version 16.04.3 on Fedora 24 has this feature available. The kate packages seem
to be the same, so there must be something else at play.

Working versions on 16.04.3:
kate-16.08.1-1.fc24.x86_64
kate4-part-4.14.3-16.fc24.x86_64
kate-plugins-16.08.1-1.fc24.x86_64

KDE Frameworks 5.25.0
Qt 5.6.1 (built against 5.6.1)
The xcb windowing system


The "broken" version16.08.1 :
kate4-part-4.14.3-16.fc24.x86_64
kate-16.08.1-1.fc24.x86_64
kate-plugins-16.08.1-1.fc24.x86_64


KDE Frameworks 5.26.0
Qt 5.6.1 (built against 5.6.1)
The xcb windowing system

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

[digikam] [Bug 369139] New: digikam is crashing when applying tag-changes

[via KDE Bugzilla]

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

Bug ID: 369139
   Summary: digikam is crashing when applying tag-changes
   Product: digikam
   Version: 4.12.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: f.bren...@gmx.net

Application: digikam (4.12.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-36-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
When i'm adding some new metadata-information to my pictures digikam is doing
well until short before finishing. The metadata is updated and fine when
reopening digikam.

Maybe the problem is, that the collection is stored on an external drive??

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fe20b694b40 (LWP 24416))]

Thread 14 (Thread 0x7fe1837fe700 (LWP 24441)):
#0  0x7fe1fe26eb73 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fe1fe26f317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe1fe26f4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe2055182ce in QEventDispatcherGlib::processEvents
(this=0x7fe1740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fe2054e618f in QEventLoop::processEvents
(this=this@entry=0x7fe1837fda20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fe2054e64f5 in QEventLoop::exec (this=this@entry=0x7fe1837fda20,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fe20978d7e3 in Digikam::WorkerObjectRunnable::run (this=0x8cf66f0)
at /build/digikam-J9prv3/digikam-4.12.0/core/libs/threads/threadmanager.cpp:196
#7  0x7fe2053cae0a in QThreadPoolThread::run (this=0x4c73790) at
concurrent/qthreadpool.cpp:108
#8  0x7fe2053d7e3c in QThreadPrivate::start (arg=0x4c73790) at
thread/qthread_unix.cpp:352
#9  0x7fe201d1c6fa in start_thread (arg=0x7fe1837fe700) at
pthread_create.c:333
#10 0x7fe20486bb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fe183fff700 (LWP 24440)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7fe201d1ee82 in __GI___pthread_mutex_lock (mutex=0x7fe1a0041c38) at
../nptl/pthread_mutex_lock.c:115
#2  0x7fe1db385133 in sqlite3_finalize () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#3  0x7fe1db5f694d in QSQLiteResultPrivate::finalize (this=0x7fe1a00439b0)
at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:154
#4  QSQLiteDriver::close (this=0x7fe1a00200e0) at
../../../sql/drivers/sqlite/qsql_sqlite.cpp:587
#5  0x7fe1db5f4dce in QSQLiteDriver::open (this=0x7fe1a00200e0, db=...,
conOpts=...) at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:548
#6  0x7fe20b3703b0 in QSqlDatabase::open (this=) at
kernel/qsqldatabase.cpp:839
#7  0x7fe202dc6fc3 in ?? () from /usr/lib/libbaloofiles.so.4
#8  0x7fe202dc78c7 in ?? () from /usr/lib/libbaloofiles.so.4
#9  0x7fe202dc2d5a in Baloo::FileModifyJob::doStart() () from
/usr/lib/libbaloofiles.so.4
#10 0x7fe205501db1 in QObject::event (this=0x7fe17c015ac0, e=) at kernel/qobject.cpp:1222
#11 0x7fe206149fdc in QApplicationPrivate::notify_helper
(this=this@entry=0x29eb100, receiver=receiver@entry=0x7fe17c015ac0,
e=e@entry=0x7fe17c0164e0) at kernel/qapplication.cpp:4570
#12 0x7fe206150f16 in QApplication::notify (this=this@entry=0x7ffd4fe09780,
receiver=receiver@entry=0x7fe17c015ac0, e=e@entry=0x7fe17c0164e0) at
kernel/qapplication.cpp:4356
#13 0x7fe206eb36aa in KApplication::notify (this=0x7ffd4fe09780,
receiver=0x7fe17c015ac0, event=0x7fe17c0164e0) at
../../kdeui/kernel/kapplication.cpp:311
#14 0x7fe2054e790d in QCoreApplication::notifyInternal
(this=0x7ffd4fe09780, receiver=receiver@entry=0x7fe17c015ac0,
event=event@entry=0x7fe17c0164e0) at kernel/qcoreapplication.cpp:955
#15 0x7fe2054eb3c6 in QCoreApplication::sendEvent (event=0x7fe17c0164e0,
receiver=0x7fe17c015ac0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x4c733f0) at
kernel/qcoreapplication.cpp:1579
#17 0x7fe2054eb6a3 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1472
#18 0x7fe20551813e in QCoreApplication::sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#19 postEventSourceDispatch (s=0x7fe17c001f00) at
kernel/qeventdispatcher_glib.cpp:300

[digikam] [Bug 369140] New: Tags don't appear at all

[Robinson Twins via KDE Bugzilla]

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

Bug ID: 369140
   Summary: Tags don't appear at all
   Product: digikam
   Version: 5.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: robinsontwin...@gmail.com

I have tried to tag photos with keywords and tried to add face tags to DigiKam
but nothing works. I have DigiKam on my Win 10 laptop and can add tags without
issues, but the Ubuntu 16.04 computer I have with DigiKam 5.1 never accepts
tags. The message I get is "failed to add tag to database". Up to this point in
time, there are no tags in the database at all.

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

[kate] [Bug 369138] New: Regex no longer available

[via KDE Bugzilla]

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

Bug ID: 369138
   Summary: Regex no longer available
   Product: kate
   Version: 16.08
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: search
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: daobr...@redhat.com

I'm on F24 and ran dnf update yesterday and now I can't discover what's
happened to the regular expression search. Neither can I find case-sensitive
search. Did I miss something? I use this constantly, every day, for work. It
exists and works fine in 15.12.3 on F23 but I can't use that any more.

Reproducible: Always

Steps to Reproduce:
1. Install kate and all the usual plug-ins
2. Open Search and Replace pane
3. Look for "Regular Expressions" and "Match case" check boxes

Actual Results:  
"Regular Expressions" and "Match case" check boxes absent. No visible way to
perform these searches.

Expected Results:  
Should have displayed my fav search/replace tool :)

The ability to use regexes and case-sensitive search, with multiple/global
replace over entire dir trees and lists of files is a major part of what I do
as an editor. If I were a coder I'd help fix or port or whatever. Maybe I can
review a man page or something? Help?

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

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

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #37 from Leslie Zhai  ---
Git commit e9faad4a24e80ee83a3881707e394ca4be66f5c7 by Leslie Zhai.
Committed on 21/09/2016 at 04:36.
Pushed by lesliezhai into branch 'multisession'.

Add more check for inquiring the ISO filesystem size

M  +5-1libk3b/projects/k3bgrowisofswriter.cpp

http://commits.kde.org/k3b/e9faad4a24e80ee83a3881707e394ca4be66f5c7

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

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

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #36 from Leslie Zhai  ---
Git commit b22f60344db146aa6b5136373b0a0b270d5d8ee9 by Leslie Zhai.
Committed on 21/09/2016 at 04:09.
Pushed by lesliezhai into branch 'multisession'.

Inquire the ISO filesystem size

Hi Thomas, please review it ;-)
CCMAIL: scdbac...@gmx.net

M  +16   -3libk3b/projects/k3bgrowisofswriter.cpp

http://commits.kde.org/k3b/b22f60344db146aa6b5136373b0a0b270d5d8ee9

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

[plasmashell] [Bug 369137] Screen will not lock when switching virtual terminal

[Arthur Țițeică via KDE Bugzilla]

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

Arthur Țițeică  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

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

[plasmashell] [Bug 369137] New: Screen will not lock when switching virtual terminal

[Arthur Țițeică via KDE Bugzilla]

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

Bug ID: 369137
   Summary: Screen will not lock when switching virtual terminal
   Product: plasmashell
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur+...@titeica.ro
CC: bhus...@gmail.com, plasma-b...@kde.org

The laptop sits idle on tty2 and KDE is started on tty1.

When switching back to the desktop on tty1 the screen is not locked even after
the configured timeout of 5 minutes passes.


Reproducible: Always

Steps to Reproduce:
1. I start the desktop on tty1 with startx (no desktop manager like sddm). Xorg
is started as a user process not under root (xorg 1.18.4).
2. I switch to another tty an run another user xorg with kodi
3. I exit kodi on tty2 and the shell automatically logs out.
4. After a few hours I switch to tty1 with KDE and the screen is still
unlocked.



Expected Results:  
The plasma screen should be locked after the configured inactivity timeout (5
min in my case).

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

[digikam] [Bug 368734] Moving a hierarchy of tags (a tag with subtags) doesn't work and can lead to losing the complete hierarchy

[via KDE Bugzilla]

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

--- Comment #9 from caulier.gil...@gmail.com ---
The problem still present because the wrong hierarchy was saved in image
metadata (XMP)

At start up, even if database is empty, whole hierarchy is recreated using file
metadata.

If you want to find which metadata option is to origin of the problem, you need
to use fresh image not yet tagged.

Gilles Caulier

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

[krunner] [Bug 369136] Krunner please add better plugin help/documentation button.

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

Summary|Krunner better plugin   |Krunner please add better
   |help/documentation. |plugin help/documentation
   ||button.

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

[krunner] [Bug 369136] New: Krunner better plugin help/documentation.

[Tony via KDE Bugzilla]

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

Bug ID: 369136
   Summary: Krunner better plugin help/documentation.
   Product: krunner
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: jodr...@live.com

Some of the krunner plugins don't have a "help" or "configuration" button
showing how to use/configure them. 
Ex: the "Dictionary" plugin lets you "define" the keyword need it to run it,
the web shortcuts can be change on system settings BUT  the spell checker,
although it can be configure in system settings, does not show how to use the
krunner plugin or the unit converter which can't be configure on system
settings and does not have a "help" button either.

The lack of this may lead users (like me) to believe they do not work, are
broken or something alike due to the lack of this information.

Reproducible: Always

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

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

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #35 from Leslie Zhai  ---
Git commit 9a6340ed76aaa8fa8784168ef7d286710097cee3 by Leslie Zhai.
Committed on 21/09/2016 at 02:41.
Pushed by lesliezhai into branch 'master'.

Wrong alleged_next_session for growisofs

WIP in multisession branch.

M  +2-2libk3b/projects/k3bgrowisofswriter.cpp

http://commits.kde.org/k3b/9a6340ed76aaa8fa8784168ef7d286710097cee3

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

[klipper] [Bug 369135] enhancement request: add option to "clear clipboard at startup"

[via KDE Bugzilla]

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

j22...@gmail.com changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[klipper] [Bug 369135] New: enhancement request: add option to "clear clipboard at startup"

[via KDE Bugzilla]

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

Bug ID: 369135
   Summary: enhancement request: add option to "clear clipboard at
startup"
   Product: klipper
   Version: 0.9.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: j22...@gmail.com

Enhancement request: add option to "clear clipboard at startup".

Reproducible: Always

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

[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #47 from Leslie Zhai  ---
Hi rmbg,

You are welcome! and Happy birthday for KDE 20 years :-)
https://timeline.kde.org/ thanks a lot for your test!

Regards,
Leslie Zhai

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

[plasmashell] [Bug 369134] New: Taskbar moves to certain monitor after returning to a locked session

[via KDE Bugzilla]

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

Bug ID: 369134
   Summary: Taskbar moves to certain monitor after returning to a
locked session
   Product: plasmashell
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: db...@posteo.de
CC: plasma-b...@kde.org

Probably related to bug https://bugs.kde.org/show_bug.cgi?id=369130

I have a setup with two monitors operating in different resolutions, one of
them is in vertical mode (rotate left). 
Most of the times , when I return to my session after it got locked because of
inactivity, the taskbar that was placed on screen one,  is suddenly on screen
two.



I'm going to add some more info as soon as I can find some pattern.

Reproducible: Sometimes

Steps to Reproduce:
1. lock your session 
2. unlock your session
3.

Actual Results:  
Taskbar moves from the rightern monitor to the leftern

Expected Results:  
Taskbar should stay.

The rightern taskbar is attached to the bottom. The leftern taskbar on the
vertical monitor is attached to the top.

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

[kwin] [Bug 369133] New: Sizing of Windows is problematic if screen resolution is below minimum size of window

[via KDE Bugzilla]

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

Bug ID: 369133
   Summary: Sizing of Windows is problematic if screen resolution
is below minimum size of window
   Product: kwin
   Version: 5.7.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: db...@posteo.de

Take the display configuration dialogue. It's window has a minimum size. If you
decrease your resolution to a certain amount you won't be able to push the
apply button anymore, because it's hidden under your taskbar (assuming it is at
the bottom) or, if you don't have a taskbar or it is set to hidden mode, it
will be out of visible area.

This is very problematic, especially, if you want to change your resolution.

Reproducible: Always

Steps to Reproduce:
1. Open display config dialogue
2. Drastically decrease your resolution
3. Try to increase resolution again; Good luck finding/hitting the apply button
(alt + a will do, though)

Actual Results:  
I was not able to hit the apply button with my cursor.

Expected Results:  
Even though a window has a certain minimal size, it should always (!) be
possible to click all elements of a window.

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

[konversation] [Bug 369132] New: When joining a new channel it should switch to that channel.

[via KDE Bugzilla]

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

Bug ID: 369132
   Summary: When joining a new channel it should switch to that
channel.
   Product: konversation
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: manuelcha...@gmail.com

Right now when I join a channel with /j I have to switch to that channel
manually afterwards. It would be better I think if it switched to it
automatically.

Reproducible: Always

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

[kwin] [Bug 369131] New: Closed application keeps its size when closed even if started on another screen

[via KDE Bugzilla]

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

Bug ID: 369131
   Summary: Closed application keeps its size when closed even if
started on another screen
   Product: kwin
   Version: 5.7.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: multihead
  Assignee: kwin-bugs-n...@kde.org
  Reporter: db...@posteo.de

If you open a window on a certain monitor and close it afterwards; the next
time you start it it will keep its last known size.

However, if you have two monitors, and reopen the application on the other
monitor which has a different resolution (height is smaller), then an
application that was maximized before, will have it's titlebar hidden outside
of range.

There is a workaround by using the 'Move' feature, but it is not nice.

Also, this behavior might occur, when changing the resolution between closing
and reopening.

I suggest to implement a check, whether the window is indeed inside the current
screen, and if not, move it inside, and then, resize, if necessary.
There should be at least an option to specify, whether you want this behavior
for the 'total screen' or the current screen; monitors might have totally
different dpi.

Reproducible: Always

Steps to Reproduce:
1. Open an application on the monitor with larger height
2. Maximize it and close it
3. Open the application on the other monitor

Actual Results:  
Title bar is out of range

Expected Results:  
Title bar is inside current monitor (better even whole window)

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

[Discover] [Bug 325728] No copy-paste?

[via KDE Bugzilla]

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

cluelessco...@gmail.com changed:

   What|Removed |Added

 CC||cluelessco...@gmail.com

--- Comment #1 from cluelessco...@gmail.com ---
What does Resolved Invalid mean?

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

[plasmashell] [Bug 368933] Plasma crashed after clicking system tray icon

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #2 from Franco Pellegrini  ---
Unfortunately, I am unable to reproduce it...

Can you tell me which plasma packages to install, so I have them if it happens
again? when dr. konqi came up I clicked the button that should install all the
needed dbg packages, but it said all packages were already installed...

Do you know if there's a way to recover the old crash and try to get more
information after installing the dbg packages?

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

[kwin] [Bug 369130] New: Windows move to certain monitor after returning to a locked session

[via KDE Bugzilla]

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

Bug ID: 369130
   Summary: Windows move to certain monitor after returning to a
locked session
   Product: kwin
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: multihead
  Assignee: kwin-bugs-n...@kde.org
  Reporter: db...@posteo.de

I have a setup with two monitors operating in different resolutions, one of
them is in vertical mode (rotate left). 
Most of the times , when I return to my session after it got locked because of
inactivity, some of the windows that were placed on screen one,  are suddenly
on screen two.

This behavior is very ugly, since the shape of the windows changes enormously
(non-vertical to vertical).

I'm going to add some more info as soon as I can find some pattern.

Reproducible: Sometimes

Steps to Reproduce:
1. open several windows (in a certain monitor setup?!)
2. lock your session
3. unlock your session

Actual Results:  
Windows on monitor 1 are placed on monitor 2

Expected Results:  
Windows stay where they were before

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

[konsole] [Bug 369021] There should be splitting options on right click menu.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[Powerdevil] [Bug 369129] Powerdevil does not provide a way to inhibit screen saving

[Rudd-O]

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

Manuel Amador (Rudd-O)  changed:

   What|Removed |Added

 CC||rud...@rudd-o.com

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

[Powerdevil] [Bug 369129] Powerdevil does not provide a way to inhibit screen saving

[Rudd-O]

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

--- Comment #1 from Manuel Amador (Rudd-O)  ---
The relevant PA thread is this one:

https://lists.freedesktop.org/archives/pulseaudio-discuss/2016-September/026910.html

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

[Powerdevil] [Bug 369129] New: Powerdevil does not provide a way to inhibit screen saving

[Rudd-O]

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

Bug ID: 369129
   Summary: Powerdevil does not provide a way to inhibit screen
saving
   Product: Powerdevil
   Version: 5.7.3
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: rud...@rudd-o.com

The D-Bus interface in Powerdevil (specifically the inhibitor interface) does
not provide a working way that will let me inhibit screen saving (BUT,
importantly, NOT the screen locker).

What I am looking for is a D-Bus call that will let me inhibit DPMS power save
on all screens of the session, while allowing the screen saver to kick in and
display itself (even if it's the blank screen saver), and the screen locker to
activate.

I know I can tell the screen locker to inhibit itself, but that is the opposite
of what I want, and furthermore does not prevent DPMS standby from kicking in.

This is important because I am writing a PulseAudio policy module that will
prevent screen blanking on HDMI devices when HDMI audio out is being used (DPMS
standby kills the audio stream as soon as it kicks in).

Thanks.

Reproducible: Always

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

[kdenlive] [Bug 369058] Kenlive crashing when files are imported

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |User Interface
   Assignee|unassigned-b...@kde.org |j...@kdenlive.org
Product|kde |kdenlive

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

[frameworks-baloo] [Bug 369101] Baloo indexing file

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |frameworks-baloo
   Assignee|unassigned-b...@kde.org |pinak.ah...@gmail.com
  Component|general |Baloo File Daemon
Version|unspecified |5.18.0

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

[dolphin] [Bug 352177] Moving/copying by drag n' drop between dolphin windows does not respect pressed Ctrl/shift

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |UPSTREAM

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

[plasmashell] [Bug 369128] New: When hidding a system tray element using a kbd shortcut, the close animation behaivs wrong

[Götz via KDE Bugzilla]

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

Bug ID: 369128
   Summary: When hidding a system tray element using a kbd
shortcut, the close animation behaivs wrong
   Product: plasmashell
   Version: 5.7.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: goetzchr...@gmail.com

Instead of animation the closing of the system tray element, it animates as
opening and then closing.

Reproducible: Always

Steps to Reproduce:
1. Assign a keyboard shortcut for some entry, e.g. the Battery and Brightness
(in system tray widget's settings)
2. Press the shortcut to open the widget, or do it manually.
3. Press the shortcut to close the widget (don't do it manually).

Actual Results:  
Two animations when closing the widget.

Expected Results:  
Only one close animation.

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

[cantor] [Bug 368986] Shouldn't the Julia back-end be an optional back-end ?

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/cant
   ||or/b25211738b84f91533562599
   ||2826dbfe6b2d860f

--- Comment #2 from Christoph Feck  ---
Git commit b25211738b84f915335625992826dbfe6b2d860f by Ivan Lakhtanov.
Committed on 20/09/2016 at 12:43.
Pushed by ivanlakhtanov into branch 'master'.

Fixes for build system and added FindJulia.cmake

Bug: 368986
Differential Revision: https://phabricator.kde.org/D2575

A  +55   -0cmake/FindJulia.cmake
M  +12   -1src/backends/CMakeLists.txt
M  +1-1src/backends/julia/juliaserver/CMakeLists.txt

http://commits.kde.org/cantor/b25211738b84f915335625992826dbfe6b2d860f

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

[plasmashell] [Bug 369127] New: Wayland hangs my pc.

[Tony via KDE Bugzilla]

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

Bug ID: 369127
   Summary: Wayland hangs my pc.
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jodr...@live.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Under a wayland session i tried to check out if this
https://bugs.kde.org/show_bug.cgi?id=367612 has been resolved...
To my surprise is worst on wayland, it hangs my pc, have to hard reset it.

I am not sure if it because i am using Nvidia(nouveau gtx 760), but wayland
session its just too dam "unstable" right now.





Reproducible: Always

Steps to Reproduce:
1.Login to a wayland session.
2.Do the steps described on bug 367612
3.See your PC hang.

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

[kmail2] [Bug 364967] Kmail message list does not remember rightmost column width

[Kay Simon via KDE Bugzilla]

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

Kay Simon  changed:

   What|Removed |Added

 CC||kayingosi...@gmail.com

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

[digikam] [Bug 368862] Thumbnails for Olympus raw (ORF) in albumview are blurred

[Guenther M . Erhard via KDE Bugzilla]

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

--- Comment #16 from Guenther M. Erhard  ---
Just compiled 5.3 from git with libraw 0.18 and the error is the same. So it is
libraw.
I'll report to the libraw team.

Thanks,
Guenther

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

[ark] [Bug 369126] New: Ark does not fallow "apply to all" check box.

[Tony via KDE Bugzilla]

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

Bug ID: 369126
   Summary: Ark does not fallow "apply to all" check box.
   Product: ark
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: jodr...@live.com
CC: rak...@freebsd.org, rthoms...@gmail.com

While extracting 2 or more compressed files (rar in this case) with a common
file in each of the compressed ones, in the same folder, ark will not
fallow/forced "apply to all" option when it encounters the "common" file
already decompressed on the same folder.

It does not matter if i picked "skip" or "overwrite", ark is not "applying to
all" in neither case.

I did not try to do the same from the command line.

Reproducible: Always

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

[kmail2] [Bug 359063] Plain text version of html-only message is not respecting encoding specified in html message

[resplin via KDE Bugzilla]

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

--- Comment #5 from resplin  ---
I'm seeing this in 5.3.0, even when the email doesn't have accents. Creating a
plain-text reply to any HTML-only email results in the wrong encoding in the
response.

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

[kmail2] [Bug 359063] Plain text version of html-only message is not respecting encoding specified in html message

[resplin via KDE Bugzilla]

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

resplin  changed:

   What|Removed |Added

 CC||richard-...@esplins.org

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[anewuser via KDE Bugzilla]

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

anewuser  changed:

   What|Removed |Added

 CC|caip...@fastmail.fm |

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

[krita] [Bug 369125] New: Brushstroke offset compared to actual cursor

[Pierre via KDE Bugzilla]

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

Bug ID: 369125
   Summary: Brushstroke offset compared to actual cursor
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: bloodyw...@tastyespresso.de

Looks like a brush engine problem for me, since it doesn't happen with all
brushes. But Deevads 2B roller brush shows a nice example of this effect (In
deevads current krita brush kit) (pixel brush with texture)

This is not a problem between tablet and krita cursor, the offset here is fine
or not present at all.
But with some brushes it looks like the actual stroke is offset.

Found the problem which causes this: enabled dynamic size in brush editor. The
brush scales down because of low pressure but the scaled down stroke doesn't
get centered like one with max pressure.

Reproducible: Always

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

[kteatime] [Bug 369124] (Regression) Incorrect, outdated kteatime icon

[Tomasz C . via KDE Bugzilla]

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

Tomasz C.  changed:

   What|Removed |Added

 CC||toma...@o2.pl

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

[kteatime] [Bug 369124] New: (Regression) Incorrect, outdated kteatime icon

[Tomasz C . via KDE Bugzilla]

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

Bug ID: 369124
   Summary: (Regression) Incorrect, outdated kteatime icon
   Product: kteatime
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@hilefoks.org
  Reporter: toma...@o2.pl

After update kteatime to version 16.08.1 systray icon was restored with kde4
and did not fit the Plasma 5.

I think it's better to undo the change and let it be a nice icon that
corresponds to the Plasma 5, although it will not be a progress bar.

Reproducible: Always

Steps to Reproduce:
1. Update kteatime to version 16.08.1
2. Run kteatime




Regression commit:
https://bugs.kde.org/show_bug.cgi?id=279222

Icon before:
https://quickgit.kde.org/?p=plasma-framework.git=blob=e22d98e21b553fa7669167517c02032078c14a0e=16b478a8275f7718f13f6d29a0f6a6caafbc78f8=src%2Fdesktoptheme%2Fbreeze%2Ficons%2Fkteatime.svgz

Icon after:
https://quickgit.kde.org/?p=kteatime.git=blob=f53048c3c19f91a198de653add8889225f8c3a7b=7c93786615bae868b6412a875d9010b06b5380d1=data%2Ficons%2F48-apps-kteatime.png

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

[kdenlive] [Bug 369123] New: If a clip in timeline is grouped (video+audio) remove space don't work and this warning appear "cannot remove space in a track with a group."

[Doru via KDE Bugzilla]

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

Bug ID: 369123
   Summary: If a clip in timeline is grouped (video+audio) remove
space don't work and this warning appear "cannot
remove space in a track with a group."
   Product: kdenlive
   Version: 16.08.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: doru...@gmail.com

If a clip in timeline is grouped (video+audio) remove space don't work and this
warning appear "cannot remove space in a track with a group."

Reproducible: Always

Steps to Reproduce:
1. Group video+audio clips.
2. Try to remove space between preview clip and grouped clip.

Actual Results:  
warning appear "cannot remove space in a track with a group."

Expected Results:  
The space between the 2 clips should be removed.

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

[kdeconnect] [Bug 369122] New: ~/.cache/kioexec/krun/_0_ does not exist

[Piotr Dobrogost via KDE Bugzilla]

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

Bug ID: 369122
   Summary: ~/.cache/kioexec/krun/_0_ does not exist
   Product: kdeconnect
   Version: 1.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: p...@bugs.kde.dobrogost.net

When trying to browse files on phone I get the following error in file manager
(Krusader):
The directory ~/.cache/kioexec/krun/_0_ does not exist.


Reproducible: Always




Fedora 24 up to date
kdeconnect 1.0-1.fc24
KDE Connect 1.4.3

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

[kwin] [Bug 367766] Compositing won't start with Nvidia 370.23 drivers on Quadro card.

[Joe via KDE Bugzilla]

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

--- Comment #9 from Joe  ---
So, I have an affected system, but not the slightest knowledge of OpenGL,
unfortunately - last time I came close to that was messing around with SDL 1.2
years ago.

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

[dolphin] [Bug 351938] Missing Comment in desktop file

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org
 Ever confirmed|0   |1
   Severity|normal  |wishlist
 Status|UNCONFIRMED |CONFIRMED

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

[kontact] [Bug 355477] Kontact crashes on startup

[Klos via KDE Bugzilla]

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

Klos  changed:

   What|Removed |Added

 CC||eduard.k...@gmx.de

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

[kontact] [Bug 355477] Kontact crashes on startup

[Klos via KDE Bugzilla]

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

--- Comment #5 from Klos  ---
Created attachment 101204
  --> https://bugs.kde.org/attachment.cgi?id=101204=edit
New crash information added by DrKonqi

kontact (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6

Kontact crashes on startup

-- Backtrace (Reduced):
#6  0x7fd3958a35c3 in QTextLayout::position (this=this@entry=0x2211a10) at
text/qtextlayout.cpp:876
#7  0x7fd3958e1317 in QTextDocumentLayoutPrivate::layoutBlock
(this=this@entry=0x1d36420, bl=..., blockPosition=blockPosition@entry=1377,
blockFormat=..., layoutStruct=layoutStruct@entry=0x7fffc4e82c40,
layoutFrom=layoutFrom@entry=67, layoutTo=layoutTo@entry=68,
previousBlockFormat=previousBlockFormat@entry=0x7fffc4e826d0) at
text/qtextdocumentlayout.cpp:2572
#8  0x7fd3958e96a3 in QTextDocumentLayoutPrivate::layoutFlow
(this=this@entry=0x1d36420, it=...,
layoutStruct=layoutStruct@entry=0x7fffc4e82c40, layoutFrom=layoutFrom@entry=67,
layoutTo=layoutTo@entry=68, width=..., width@entry=...) at
text/qtextdocumentlayout.cpp:2415
#9  0x7fd3958e4d44 in QTextDocumentLayoutPrivate::layoutCell
(this=this@entry=0x1d36420, t=t@entry=0x2227000, cell=..., width=...,
width@entry=..., layoutFrom=layoutFrom@entry=67, layoutTo=layoutTo@entry=68,
td=td@entry=0x2245e50, absoluteTableY=absoluteTableY@entry=...,
withPageBreaks=withPageBreaks@entry=false) at text/qtextdocumentlayout.cpp:1545
#10 0x7fd3958e583c in QTextDocumentLayoutPrivate::layoutTable
(this=this@entry=0x1d36420, table=0x2227000, layoutFrom=layoutFrom@entry=67,
layoutTo=layoutTo@entry=68, parentY=..., parentY@entry=...) at
text/qtextdocumentlayout.cpp:1655

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

[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi

[Stormi via KDE Bugzilla]

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

Stormi  changed:

   What|Removed |Added

 CC||sto...@laposte.net

--- Comment #11 from Stormi  ---
Same issue here in Mageia cauldron and plasma-workspace-5.7.95

This particular issue is flagged release_blocker for the upcoming Mageia 6
release, because most non-KDE programs in the systray can't be interacted with.

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

[kmail2] [Bug 369121] New: Application crashed by starting

[Klos via KDE Bugzilla]

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

Bug ID: 369121
   Summary: Application crashed by starting
   Product: kmail2
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eduard.k...@gmx.de

Application: kmail (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-37-generic x86_64
Distribution: Linux Mint 17.1 Rebecca

-- Information about the crash:
I dont know for fixing this problem

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f950315a800 (LWP 8442))]

Thread 2 (Thread 0x7f94d9fcc700 (LWP 8447)):
#0  0x7f95004abfdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f94f8510fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f94f85110ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9500e487be in QEventDispatcherGlib::processEvents
(this=0x7f94d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f9500e1a0af in QEventLoop::processEvents
(this=this@entry=0x7f94d9fcbda0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f9500e1a3a5 in QEventLoop::exec (this=this@entry=0x7f94d9fcbda0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f9500d16c5f in QThread::exec (this=this@entry=0x1813af0) at
thread/qthread.cpp:537
#7  0x7f9500dfb823 in QInotifyFileSystemWatcherEngine::run (this=0x1813af0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f9500d1932f in QThreadPrivate::start (arg=0x1813af0) at
thread/qthread_unix.cpp:349
#9  0x7f94fdd7b184 in start_thread (arg=0x7f94d9fcc700) at
pthread_create.c:312
#10 0x7f95004b937d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f950315a800 (LWP 8442)):
[KCrash Handler]
#6  0x7f95003f5c37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x7f95003f9028 in __GI_abort () at abort.c:89
#8  0x7f95004322a4 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7f95005406b0 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f950043e55e in malloc_printerr (ptr=,
str=0x7f9500540850 "free(): invalid next size (fast)", action=1) at
malloc.c:4996
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3840
#11 0x7f950159f48d in free (alignment=8, x=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:99
#12 free (this=, x=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:468
#13 operator= (v=..., this=0x1b380c0) at
../../include/QtCore/../../src/corelib/tools/qvector.h:395
#14 clear (this=0x1b380c0) at
../../include/QtCore/../../src/corelib/tools/qvector.h:348
#15 QTextEngine::clearLineData (this=0x1b380c0) at text/qtextengine.cpp:1483
#16 0x7f95015a1268 in QTextLayout::clearLayout (this=) at
text/qtextlayout.cpp:659
#17 0x7f95015b2e6c in QTextBlock::clearLayout
(this=this@entry=0x7fffe100d9f0) at text/qtextobject.cpp:1084
#18 0x7f95015ea0e3 in QTextDocumentLayout::documentChanged (this=0x15451d0,
from=0, oldLength=0, length=2846) at text/qtextdocumentlayout.cpp:2882
#19 0x7f95017a4663 in QTextEditPrivate::relayoutDocument
(this=this@entry=0x17feb90) at widgets/qtextedit.cpp:1438
#20 0x7f95017a4e60 in QTextEdit::resizeEvent (this=,
e=0x7fffe100deb0) at widgets/qtextedit.cpp:1397
#21 0x7f950139c2ce in QWidget::event (this=this@entry=0x1838ae0,
event=event@entry=0x7fffe100deb0) at kernel/qwidget.cpp:8541
#22 0x7f950173e04e in QFrame::event (this=0x1838ae0, e=0x7fffe100deb0) at
widgets/qframe.cpp:557
#23 0x7f9500e1b646 in
QCoreApplicationPrivate::sendThroughObjectEventFilters
(this=this@entry=0x12a9be0, receiver=receiver@entry=0x184f100,
event=event@entry=0x7fffe100deb0) at kernel/qcoreapplication.cpp:1063
#24 0x7f950134ce0c in QApplicationPrivate::notify_helper
(this=this@entry=0x12a9be0, receiver=receiver@entry=0x184f100,
e=e@entry=0x7fffe100deb0) at kernel/qapplication.cpp:4563
#25 0x7f95013534a0 in QApplication::notify (this=this@entry=0x7fffe100ed20,
receiver=receiver@entry=0x184f100, e=e@entry=0x7fffe100deb0) at
kernel/qapplication.cpp:4353
#26 0x7f9502b93cca in KApplication::notify (this=0x7fffe100ed20,
receiver=0x184f100, event=0x7fffe100deb0) at
../../kdeui/kernel/kapplication.cpp:311
#27 0x7f9500e1b4dd in QCoreApplication::notifyInternal
(this=0x7fffe100ed20, receiver=receiver@entry=0x184f100,
event=event@entry=0x7fffe100deb0) at kernel/qcoreapplication.cpp:953
#28 0x7f9501398301 in sendEvent (event=0x7fffe100deb0, receiver=0x184f100)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#29 

[Skanlite] [Bug 299517] Skanlite should support scan to pdf.

[thev00d00]

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

Ian Whyman (thev00d00)  changed:

   What|Removed |Added

 CC||thev00...@gentoo.org

--- Comment #9 from Ian Whyman (thev00d00)  ---
So it's 2016 now, any change?

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Bob Wya via KDE Bugzilla]

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

--- Comment #195 from Bob Wya  ---
(In reply to abac00s from comment #194)
> THANK YOU Bob Wya for the awesome script. You encouraged me to learn bash
> scripting ;)

Sorry guys - this bad form for a Bugzilla! But the bug is closed - so I'm
letting myself off :-)

O.T.
Well the script is mainly awk. But you can do amazing stuff with awk! I can
highly recommend learning it - it's very powerful and has C-like
features/syntax. I spent a month doing a deep dive - so I can make it do pretty
much anything (I've even written an xml parser in it). I can highly recommend
installing / using mawk (which is only awk compatible - and does not support
the gawk extensions) - but it's multiple orders of magnitude faster!!

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

[kdenlive] [Bug 368984] Removing "dissolve" crashes Kdenlive

[Vincent PINON via KDE Bugzilla]

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

--- Comment #8 from Vincent PINON  ---
sorry:
https://phabricator.kde.org/project/board/40/

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

[kdenlive] [Bug 368984] Removing "dissolve" crashes Kdenlive

[Vincent PINON via KDE Bugzilla]

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

--- Comment #7 from Vincent PINON  ---
https://phabricator.kde.org/tag/kdenlive/

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

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[via KDE Bugzilla]

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

ham...@laposte.net changed:

   What|Removed |Added

 CC||ham...@laposte.net

--- Comment #238 from ham...@laposte.net ---
Here, I had never seen this bug before upgrading to KF 5.26.0. in 3 days, it
happened twice.

Thread 1 (Thread 0x7f98f97fd640 (LWP 13335)):
[KCrash Handler]
#5  0x7f98f6731140 in ?? () from /usr/lib/libQt5Qml.so.5
#6  0x7f98f698041a in QQmlDelegateModel::_q_itemsChanged(int, int,
QVector const&) () from /usr/lib/libQt5Qml.so.5
#7  0x7f98f69a7a9c in ?? () from /usr/lib/libQt5Qml.so.5
#8  0x7f98f69a81d8 in QQmlDelegateModel::qt_metacall(QMetaObject::Call,
int, void**) () from /usr/lib/libQt5Qml.so.5
#9  0x7f98f3804684 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#10 0x7f98f387bcbc in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from /usr/lib/libQt5Core.so.5
#11 0x7f982764c2e3 in ?? () from /usr/lib/liblegacytaskmanager.so.5
#12 0x7f98f38044e9 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#13 0x7f9827657a78 in
LegacyTaskManager::AbstractGroupableItem::changed(QFlags)
() from /usr/lib/liblegacytaskmanager.so.5
#14 0x7f982763f4a0 in ?? () from /usr/lib/liblegacytaskmanager.so.5
#15 0x7f98f38044e9 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#16 0x7f9827657c68 in
LegacyTaskManager::Task::changed(QFlags) () from
/usr/lib/liblegacytaskmanager.so.5
#17 0x7f9827629ea5 in LegacyTaskManager::Task::setActive(bool) () from
/usr/lib/liblegacytaskmanager.so.5
#18 0x7f9827645769 in
LegacyTaskManager::LegacyTaskManager::activeWindowChanged(unsigned long long)
() from /usr/lib/liblegacytaskmanager.so.5
#19 0x7f98f380485e in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#20 0x7f98f647eab2 in KWindowSystem::activeWindowChanged(unsigned long
long) () from /usr/lib/libKF5WindowSystem.so.5
#21 0x7f98d994fecb in ?? () from
/usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so
#22 0x7f98f37d621f in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
from /usr/lib/libQt5Core.so.5
#23 0x7f98e36a3c34 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/lib/libQt5XcbQpa.so.5
#24 0x7f98e36a48c5 in QXcbConnection::processXcbEvents() () from
/usr/lib/libQt5XcbQpa.so.5
#25 0x7f98f3805349 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#26 0x7f98f4743e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#27 0x7f98f474b5b1 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#28 0x7f98f37d8c80 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#29 0x7f98f37db3fd in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#30 0x7f98f382d173 in ?? () from /usr/lib/libQt5Core.so.5
#31 0x7f98ee0ffe67 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#32 0x7f98ee1000d0 in ?? () from /usr/lib/libglib-2.0.so.0
#33 0x7f98ee10017c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#34 0x7f98f382d57f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#35 0x7f98f37d70da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#36 0x7f98f37df5cc in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#37 0x0041b54d in ?? ()
#38 0x7f98f2e4c291 in __libc_start_main () from /usr/lib/libc.so.6
#39 0x0041b8ca in _start ()

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

[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO

[Kåre Särs via KDE Bugzilla]

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

--- Comment #10 from Kåre Särs  ---
I'm a bit confused as I'm running 64Bit Kubuntu 16.04 + backports (KF5.23,
Plasma 5.6.5) + compiled from sources KTextEditor + Kate and I don't have that
problem... From the logs it seems You are also on 64Bit...

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

[kontact] [Bug 369120] New: Kontact crashed by starting the application

[Klos via KDE Bugzilla]

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

Bug ID: 369120
   Summary: Kontact crashed by starting the application
   Product: kontact
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eduard.k...@gmx.de

Application: kontact (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-37-generic x86_64
Distribution: Linux Mint 17.1 Rebecca

-- Information about the crash:
- What I was doing when the application crashed: nothing
- Unusual behavior I noticed: i don't noticed
- Custom settings of the application: default settings

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7f7ac2b65700 (LWP 6544)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7adebfb81d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7adebfb859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f7adb31c184 in start_thread (arg=0x7f7ac2b65700) at
pthread_create.c:312
#4  0x7f7ae13d037d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f7a82262700 (LWP 6545)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7ade93c20d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7adec2afd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f7adb31c184 in start_thread (arg=0x7f7a82262700) at
pthread_create.c:312
#4  0x7f7ae13d037d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f7a72896700 (LWP 6548)):
#0  0x7f7ae13c2fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f7adae3cfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7adae3d0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7ae1b497be in QEventDispatcherGlib::processEvents
(this=0x7f7a6c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f7ae1b1b0af in QEventLoop::processEvents
(this=this@entry=0x7f7a72895da0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f7ae1b1b3a5 in QEventLoop::exec (this=this@entry=0x7f7a72895da0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f7ae1a17c5f in QThread::exec (this=this@entry=0xed2d60) at
thread/qthread.cpp:537
#7  0x7f7ae1afc823 in QInotifyFileSystemWatcherEngine::run (this=0xed2d60)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f7ae1a1a32f in QThreadPrivate::start (arg=0xed2d60) at
thread/qthread_unix.cpp:349
#9  0x7f7adb31c184 in start_thread (arg=0x7f7a72896700) at
pthread_create.c:312
#10 0x7f7ae13d037d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f7ae3e4e800 (LWP 6543)):
[KCrash Handler]
#6  deref (this=0x7f7a) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:133
#7  QList::~QList (this=0x148a2b0, __in_chrg=)
at ../../include/QtCore/../../src/corelib/tools/qlist.h:731
#8  0x7f7ae2777921 in ~QTextOptionPrivate (this=0x148a2b0,
__in_chrg=) at text/qtextoption.cpp:48
#9  QTextOption::operator= (this=0x1416f80, o=...) at text/qtextoption.cpp:129
#10 0x7f7ae276312c in QTextLayout::setTextOption
(this=this@entry=0x1416f10, option=...) at text/qtextlayout.cpp:427
#11 0x7f7ae27a1656 in QTextDocumentLayoutPrivate::layoutBlock
(this=this@entry=0xef4cb0, bl=..., blockPosition=blockPosition@entry=1380,
blockFormat=..., layoutStruct=layoutStruct@entry=0x7fff07057710,
layoutFrom=layoutFrom@entry=67, layoutTo=layoutTo@entry=68,
previousBlockFormat=previousBlockFormat@entry=0x7fff070571a0) at
text/qtextdocumentlayout.cpp:2594
#12 0x7f7ae27a96a3 in QTextDocumentLayoutPrivate::layoutFlow
(this=this@entry=0xef4cb0, it=...,
layoutStruct=layoutStruct@entry=0x7fff07057710, layoutFrom=layoutFrom@entry=67,
layoutTo=layoutTo@entry=68, width=..., width@entry=...) at
text/qtextdocumentlayout.cpp:2415
#13 0x7f7ae27a4d44 in QTextDocumentLayoutPrivate::layoutCell
(this=this@entry=0xef4cb0, t=t@entry=0x140f360, cell=..., width=...,
width@entry=..., layoutFrom=layoutFrom@entry=67, layoutTo=layoutTo@entry=68,
td=td@entry=0xef45a0, absoluteTableY=absoluteTableY@entry=...,
withPageBreaks=withPageBreaks@entry=false) at text/qtextdocumentlayout.cpp:1545
#14 0x7f7ae27a583c in QTextDocumentLayoutPrivate::layoutTable
(this=this@entry=0xef4cb0, table=0x140f360, layoutFrom=layoutFrom@entry=67,
layoutTo=layoutTo@entry=68, parentY=..., parentY@entry=...) at
text/qtextdocumentlayout.cpp:1655
#15 

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[via KDE Bugzilla]

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

abac...@outlook.com changed:

   What|Removed |Added

 CC||abac...@outlook.com

--- Comment #194 from abac...@outlook.com ---
THANK YOU Bob Wya for the awesome script. You encouraged me to learn bash
scripting ;)

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

[LabPlot2] [Bug 369057] Crash when removing a column in a spreadsheet

[Alexander Semke via KDE Bugzilla]

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

Alexander Semke  changed:

   What|Removed |Added

   Version Fixed In||2.4

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

[digikam] [Bug 368862] Thumbnails for Olympus raw (ORF) in albumview are blurred

[via KDE Bugzilla]

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

--- Comment #15 from caulier.gil...@gmail.com ---
Are you sure that problem is not fixed with digiKam 5.1.0 which include libraw
0.18 ?

If no, please report this problem to Libraw team, through github project page.

https://github.com/LibRaw/LibRaw/issues

Gilles Caulier

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

[digikam] [Bug 368862] Thumbnails for Olympus raw (ORF) in albumview are blurred

[Guenther M . Erhard via KDE Bugzilla]

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

--- Comment #14 from Guenther M. Erhard  ---
In my opinion the problem is the libraw version. Exiv2 is the same version
(0.25) on both Ubuntu 14.04 and 16.04.

I have now installed libraw 0.16.2 instead of 0.17.1 in my Ubuntu 16.04 and
recompiled digikam 4.13 for a test and it is working! After thumbnails
recreating they are sharp. So something has changed in libraw 0.17.

Guenther

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

[umbrello] [Bug 369087] Umbrello/KF5 does not show icons in the properties and settings dialogs

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Ralf Habacker  ---
Bug has been detected with KDE Frameworks 5.22.

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

[umbrello] [Bug 369085] Umbrello/KF5 does not show icons in the diagram tool bar

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Ralf Habacker  ---
Bug has been detected with KDE Frameworks 5.22.

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

[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"

[Petros via KDE Bugzilla]

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

--- Comment #3 from Petros  ---
Portage reemerged libxcb, mesa and last xorg-server with this specific order
but the problem persists.

equery b libGL.so  
 * Searching for libGL.so.1 ... 
dev-util/apitrace-7.1 (/usr/lib64/apitrace/wrappers/libGL.so.1 -> glxtrace.so)
media-libs/mesa-12.0.3 (/usr/lib32/libGL.so.1 -> libGL.so.1.2.0)
media-libs/mesa-12.0.3 (/usr/lib64/libGL.so.1 -> libGL.so.1.2.0)
media-libs/mesa-12.0.3 (/usr/lib64/libGL.so.1.2.0)

file libGL.so.1
libGL.so.1: symbolic link to libGL.so.1.2.0

file libxcb-dri3.so.0
libxcb-dri3.so.0: symbolic link to libxcb-dri3.so.0.0.0

file libxcb-dri3.so.0.0.0
libxcb-dri3.so.0.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, stripped

At first I though that there had to be some kind of inconsistency with the
naming scheme of the symlinks. But every symlink exists and points where it
should be. 

Below I provide the LD_DEBUG outputs relevanto dri3 from these two appimages
(5.0.0-1 and 5.0.1)

LD_DEBUG="files" ./kdevelop-latest.AppImage 2>&1 | tee | grep xcb-dri3
 11109: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libGL.so.1 [0]
 11109: file=libxcb-dri3.so.0 [0];  generating link map
 11109: calling init: /usr/lib64/libxcb-dri3.so.0
 11132: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libGL.so.1 [0]
 11132: file=libxcb-dri3.so.0 [0];  generating link map
 11132: calling init: /usr/lib64/libxcb-dri3.so.0
 11135: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libGL.so.1 [0]
 11135: file=libxcb-dri3.so.0 [0];  generating link map
 11135: calling init: /usr/lib64/libxcb-dri3.so.0
 11109: calling fini: /usr/lib64/libxcb-dri3.so.0 [0]
 11135: calling fini: /usr/lib64/libxcb-dri3.so.0 [0]
 11132: calling fini: /usr/lib64/libxcb-dri3.so.0 [0]
the whole output (  https://paste.pound-python.org/show/tvVFadlzvxdsYVOHwFv9/ )


LD_DEBUG="files" ./KDevelop-5.0.1-x86_64.AppImage 2>&1 | tee | grep xcb-dri
 11225: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libGL.so.1 [0]
 11225: file=libxcb-dri3.so.0 [0];  generating link map
 11225: /usr/lib64/libxcb-dri3.so.0: error: symbol lookup error:
undefined symbol: xcb_send_request_with_fds (fatal)
kdevelop: symbol lookup error: /usr/lib64/libxcb-dri3.so.0: undefined symbol:
xcb_send_request_with_fds

And system-installed kdevelop:
LD_DEBUG="files" /usr/bin/kdevelop
 12432: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libGL.so.1 [0]
 12432:EBUG=file=libxcb-dri3.so.0 [0];  generating link map
 12432:EBUG=calling init: /usr/lib64/libxcb-dri3.so.0
 12440: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libEGL.so.1
[0]
 12440: file=libxcb-dri3.so.0 [0];  generating link map
 12440: calling init: /usr/lib64/libxcb-dri3.so.0
^C

The same command, with the same (in some way) executables, and the same (?)
libraries provided. Why there is this inconsistency in the behavior?

PS I even tried to recompile libxcb, mesa and xorg without -ggdb, but of course
this wasn't an issue.

PS1. I tried to create the output of LD_DEBUG="all" for the 5.0.0-1 version,
but soon enough the log size was over 170MB. No way this thing can be uploaded
with my internet connection. If it is necessary though, let me know.

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

[Patrice Kouame via KDE Bugzilla]

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

--- Comment #15 from Patrice Kouame  ---
understood.

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #14 from Boudewijn Rempt  ---
On OSX, with git master, you must have Qt 5.7 patched with the patch in the
ext_qt folder.

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

[Patrice Kouame via KDE Bugzilla]

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

--- Comment #13 from Patrice Kouame  ---
Hey Nim -

Yes, I fully understand that and usually turn off openGL when playing around
with master.  Setting back to 2.1 is just a quick workaround to look at other
things. Not meant as a recommendation to anyone.  Just wanted to relate and
(explain) my experience to n7down  who may be in the same boat on macOS.

On another note,  I've been on krita+Qt5.7 on mac for a while now. In fact, the
release notes in 3rdparty suggested (once?) that it wasn't a requirement (boud
confirmed it informally), so I felt safe sticking with a "virgin" Qt5.7
straight out of the box.  Are you saying, I should revert to 5.6 or ext_qt
until 3.1 and your changes hit the street?

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

[krita] [Bug 369119] New: Inconsistent Instant Preview Mode user interface/experience

[Patrice Kouame via KDE Bugzilla]

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

Bug ID: 369119
   Summary: Inconsistent Instant Preview Mode user
interface/experience
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: pkou...@mac.com

The Instant Preview Mode (IP) is disabled when selecting a Filter brush with
Gaussian effect (for example).  The check box in the panel goes dark with
strike-thru text. Thereafter, selecting another brush does not necessarily
reset the mode.  It stays disabled for all brushes.  Only tickling a parameter,
like Size or Ratio in the Pixel brush for instance,  resets, it.  Not all
parameters do this though.

Also, assuming the IP Mode menu item should always reflect the Brush engine
panel setting (and vice-versa), it doesn’t. The menu item stays checked even
though the brush engine settings say its off.

Finally, with IP Mode OFF (via menu), shouldn’t it be disabled for all brushes?
No matter what brush setting is changed?

NOTE: My understanding of how IP mode works may be twisted.  Please advise if
that's the case, but I didn't find the current workflow intuitive.


Reproducible: Always

Steps to Reproduce:
1. Just to be safe, cleared all of my krita settings
2. Open krita with a new document
3. Set Instant Preview (IP) Mode On (via menu)
3. Click the toolbar Brush Settings icon - IP is, by default, checked.
4. Cycle through some other brush engines to verify that IP is enabled/checked
everywhere
5. Select Filter and IP is disabled (goes dark after a split second)
6. All other brush settings now have IP disabled
7. Select another brush and IP is re-enabled ONLY after selecting the right
parameter (for Pixel, Size or Ratio does thr trick)



Expected Results:  
1. When switching to a non Filter brush, IP mode should be (re)enabled if its
compatible 
2. The IP Mode menu setting should always reflect the current brush engine
setting

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Nicolas Dietrich via KDE Bugzilla]

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

--- Comment #193 from Nicolas Dietrich  ---
I'm not so sure that this is really resolved. I'm still experiencing
misbehavior with Plasma 5.8 (few days old). I don't have time for thorough
testing though.

Note that my comment #189 does exist in Plasma 5.8 (at very until least days
back, when I last deleted some plasmarc file) - I opened issue 368818 for the
exact behavior, but I'm afraid that this might just be a duplicate of this bug
here.

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

[okular] [Bug 325119] Size of inline notes not adjusted to font size and does not respect drawn boundaries

[via KDE Bugzilla]

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

--- Comment #6 from dannycoli...@gmail.com ---
Any progress?

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

[okular] [Bug 325119] Size of inline notes not adjusted to font size and does not respect drawn boundaries

[via KDE Bugzilla]

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

dannycoli...@gmail.com changed:

   What|Removed |Added

 CC||dannycoli...@gmail.com

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

[okular] [Bug 358060] Inline note cannot be resized

[via KDE Bugzilla]

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

dannycoli...@gmail.com changed:

   What|Removed |Added

 CC||dannycoli...@gmail.com

--- Comment #1 from dannycoli...@gmail.com ---
+1
It'll help resolve that bug https://bugs.kde.org/show_bug.cgi?id=325119

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

[dolphin] [Bug 351754] Installation of plugins failed due to older version to be installed

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---
This is a packaging issue (sounds like missing codecs in openSUSE), closing as
such.

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

[via KDE Bugzilla]

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

--- Comment #12 from nimth...@gmail.com ---
Hi Pkouame,

The problem you face with that crash is that bleeding edge master now requires
a patched Qt5.7 until Qt adds my changes. Using an unpatched Qt5.7 breaks
everything because we ask for a 3.2 Core Profile (which you **do** get btw, you
get a 4.1 core profile) and this profile deprecates all of Qt's legacy shaders.
This is why it gives you shader compilation errors showing Qt's inner shaders.

Setting the format back to 2.1 will cause you to revert to the state of Krita
before my changes, which means no instant preview and high quality filtering.

If you want to try the bleeding edge Krita you should use the Qt we pack with
Krita and its applied patches and remove your 2.1 format setting.

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

[dolphin] [Bug 351617] After archive is extracted, Dolphin fails to display Extracted Folder

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Elvis Angelaccio  ---
I cannot reproduce and in the meantime both Dolphin and Ark (which does the
actual extraction) have been ported to qt5. Please reopen if you can reproduce
again on newer releases.

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

[k3b] [Bug 366569] K3b doesn't allow using network files

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

[David Edmundson via KDE Bugzilla]

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

--- Comment #2 from David Edmundson  ---
Someone linked me to the G+ post, so I got a bit more info.

When you say the "session has crashed" what does that mean? Can you still run
krunner with alt+space?

We don't do core files generally in KDE code, as we have our own debug hander,
drkonqui, normally this prompts you with a backtrace and you should have a big
dialog saying about this.
(unless explicitly disabled, in which case, don't)

The other option is to manually launch plasmashell from a konsole

>From konsole
kquitapp5 plasmashell
gdb plasmashell


then when you come back and it's crashed type:
 - "thread apply all bt"

and copy and paste the pages of data.

I'll also try the multiple sessions thing tonight, and see.

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

[plasmashell] [Bug 359152] No application can be run after some uptime

[Jiri Slaby via KDE Bugzilla]

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

--- Comment #5 from Jiri Slaby  ---
(In reply to David Edmundson from comment #4)
> So you have the file when you log in, then at some point it disappears?

Exactly.

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

[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO

[Marvin Jens via KDE Bugzilla]

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

--- Comment #9 from Marvin Jens  ---
please let me know if there is anything I can do to provide useful debug
output. This bug is really haunting me every day!

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

[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.

[Hugo Parente Lima via KDE Bugzilla]

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

--- Comment #35 from Hugo Parente Lima  ---
This bug was (is) a blocker to me, in fact it was the root cause that make me
move away from my KDE/yakuake working env. :-(. At least I learned tmux :-)

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

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Denis Revin via KDE Bugzilla]

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

Denis Revin  changed:

   What|Removed |Added

 CC||denis.re...@gmail.com

--- Comment #13 from Denis Revin  ---
Same issue for me. It's not clear from this error that you must to do. Can you
be more informative about it? For example, you can just tell user something
like: "Please, run `gpg2 --full-gen-key` to add at least one key"

Thank you :)

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

[Patrice Kouame via KDE Bugzilla]

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

--- Comment #11 from Patrice Kouame  ---
Created attachment 101203
  --> https://bugs.kde.org/attachment.cgi?id=101203=edit
shader compiler errors

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

[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.

[via KDE Bugzilla]

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

--- Comment #6 from kdde@porcupinefactory.org ---
I have no idea how I didn't notice that before. That solves the configuration
workflow I suppose.

I still claim that the MAC default is unsuitable for a user unaware of WiFi
privacy problems. As the defaults author makes decisions on behalf of
non-specialists, the defaults should be safe and conservative.

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

[Patrice Kouame via KDE Bugzilla]

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

--- Comment #10 from Patrice Kouame  ---
NOTE: Whereas the crash is fixed.  The shader loader is still not happy.  Check
out my attached log.
Missing version strings in shaders this time around...

For me, running bleeding edge krita master on unpatched Qt5.7 without Nim's
changes required hard coding a format.setVersion(2, 1) .  Seems like even with
4.1 enabled and format.setVersion(3, 2) macOS really just gives you a core 2.1
profile...Avoided the brutal seg.

Patrice

Test Environment
Krita 3.0.2 beta b9c7f564101b12e4f1a102b79ad588226795cbfe
mac pro 3,1
NVIDIA GeForce GTX 680 2G
macOS Sierra GM
Xcode 8 Release

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

[korganizer] [Bug 340204] Korganizers 5.3.1 reminder is up to one minute late

[Till Schäfer via KDE Bugzilla]

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

Till Schäfer  changed:

   What|Removed |Added

Version|unspecified |GIT (master)
Summary|Korganizers 4.14.2 reminder |Korganizers 5.3.1 reminder
   |is up to one minute late|is up to one minute late

--- Comment #1 from Till Schäfer  ---
still valid for version 5.3.1

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

[plasmashell] [Bug 366190] KDE KickOff Application Launcher crashes when typing to search for applications

[David Edmundson via KDE Bugzilla]

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

--- Comment #7 from David Edmundson  ---
Interestingly it's not a related bug. Same action, different cause.

This is the same bug as the infamous 342763 and 346118
which are completely different actions, with the same cause. There is a patch
for Qt pending.

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

[frameworks-baloo] [Bug 369092] Plasma crashes when trying to search anything

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

  Component|general |general
Version|5.5.5   |unspecified
Product|plasmashell |frameworks-baloo
   Target Milestone|1.0 |---
   Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com

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

[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from David Edmundson  ---
If there's a crash it would help if we can see a backtrace.

Please reopen with one, thanks.

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

[plasmashell] [Bug 369100] Dark theme affects aspects of applications that it should not

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
That's almost certainly a bug in their applications. If they cherry-pick what
theme parts they load (and do it badly) there's not a lot we can do.

Any idea what toolkit those applications are written in?

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

[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

   Assignee|kdevelop-bugs-n...@kde.org  |m...@svenbrauch.de

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

[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---
Thanks a lot for this info. I think the interesting line is this:

  5970: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libGL.so.1 [0]

and that is the only thing which needs it, and conversely the only thing which
can look up symbols in it (and fail), or am I wrong here?

libGL.so.0 is taken from your system (as it should be), and thus your versions
of libGL and libxcb-dri3.so seem to be binary incompatible. Can you please
rebuild them both?

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

[plasmashell] [Bug 355190] copy current date/time into clipboard

[Barry Jackson via KDE Bugzilla]

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

--- Comment #25 from Barry Jackson  ---
Will this be in 5.8.0?

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

[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #4 from David Edmundson  ---
What version of plasma-framework?

-- 
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 #34 from Thomas Schmitt  ---
Hi,

it really works when you tell growisofs -M the correct -C values
which match the ones computed by growisofs.

Session 1:

  genisoimage -R file1 | \
  growisofs -Z /dev/sr4=/dev/fd/0

The ISO has a size of 176 blocks. growisofs would next round up to
integer multiples of 16. That still yields 176.
So i use -C 0,176 in Session 2:

  genisoimage -M /dev/sr4 -C 0,176 -R file2 | \
  growisofs -C 0,176 -M /dev/sr4=/dev/fd/0

growisofs agreed to -C 0,176. 
So it was not necessary to override the ideas of growisofs via
option -use-the-force-luke=seek=...

Mounting the DVD+RW shows both files.

So this would be a viable method, too.
One just would have to try ISO 9660 size determination if the MMC
track position inquiry yields 0,0.

Don't forget to check for the magic number of ISO 9660 at the start
of block 16. If the first 6 bytes are not {0x01,'C','D','0','0','1'},
then it is not an ISO 9660 and there is no use in reading the 32 bit
number from byte offset 80.
In this case, no multi-session can be offered to the user.

Have a nice day :)

Thomas

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

[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys

[rmbg via KDE Bugzilla]

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

--- Comment #46 from rmbg  ---
Hi, 
On Plasma 5.7.95 (Plasma 5.8 beta) seems to be fixed! Shift + del directly
delete files or folders ("do you really want to delete these X items?")  and
also ctrl + x cuts files or folder and let you paste where you want. 

Fantastic!

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

[frameworks-baloo] [Bug 362222] Baloo crashes every session; file search doesn't work

[via KDE Bugzilla]

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

rene_...@vonwert.eu changed:

   What|Removed |Added

 CC||rene_...@vonwert.eu

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

[konqueror] [Bug 367908] Konqueror crashed by opening/closing a tar archive

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---


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

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

[ark] [Bug 193908] Ark crashes when closing it during large archive loading

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||lx21...@googlemail.com

--- Comment #157 from Elvis Angelaccio  ---
*** Bug 367908 has been marked as a duplicate of this bug. ***

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

[apper] [Bug 341902] Searchgroups not supported by backends

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM
 CC||rdie...@math.unl.edu

--- Comment #4 from Rex Dieter  ---
This is a downstream (fedora) issue, nothing apper can do about a distro's
choice of PackageKit backends (and features)

See also:
https://bugzilla.redhat.com/show_bug.cgi?id=1177137
https://bugzilla.redhat.com/show_bug.cgi?id=1181859
https://bugzilla.redhat.com/show_bug.cgi?id=1098735

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