[konsole] [Bug 374259] >2 GB history file tries to overflow lseek

[bugzilla_noreply]

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

whabash...@gmail.com changed:

   What|Removed |Added

 CC||whabash...@gmail.com

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

[plasmashell] [Bug 377190] Crash occures when clicking on the activity button on the desktop

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

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


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

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

[plasmashell] [Bug 377190] Crash occures when clicking on the activity button on the desktop

[David Edmundson]

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

--- Comment #2 from David Edmundson  ---
What's the activity button on the desktop?

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

[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||iratusmalus...@gmail.com

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

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

[krita] [Bug 377146] Brush color selection does not work on several brushes

[Dmitry Kazakov]

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

--- Comment #5 from Dmitry Kazakov  ---
Hi, b-b1!

You can find information about our brush engines in the official manual:

https://docs.krita.org/Category:Brush_Engines



On 04.03.2017 05:02, bugzilla_nore...@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=377146
>
> --- Comment #4 from b...@juno.com ---
> Oops, didn't mean to poke the bear.  No, I just want to know how to make
> them work, including how to use the ones I don't understand.  Is there
> another source of info that does not use technical terms to answer
> technical problems?  Like, could it tell me exactly what "painting with
> surfaces", not colors, means?  And how to access that, in terms of "go to
> this spot and click this/choose that option"?
> I love what I have been able to get the program to do and don't want to
> ditch the thing  because I don't understand chunks of it.  Much better to
> learn how to work with those tools.
> Thanks
>
>
>
> On Fri, 03 Mar 2017 20:34:59 + Boudewijn Rempt
>  writes:
>> https://bugs.kde.org/show_bug.cgi?id=377146
>>
>> --- Comment #3 from Boudewijn Rempt  ---
>> If this is too abstruse, don't use those brushes. Use other brushes.
>> These
>> brushes are meant for people who need this feature; you don't need
>> it, don't
>> use it! There are very likely more features in Krita that are weird
>> or
>> incomprehensible unless you urgently need them. That doesn't mean
>> the features
>> are buggy, though.
>>
>> -- 
>> You are receiving this mail because:
>> You reported the bug.
> 
> Warning: Don't Use Probiotics Before You See This
> Gundry MD
> http://thirdpartyoffers.juno.com/TGL3141/58ba201053ca820102714st03vuc
>

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

[kdenlive] [Bug 377191] New: Chroma key variance not working

[Alexander van der Merwe]

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

Bug ID: 377191
   Summary: Chroma key variance not working
   Product: kdenlive
   Version: git-master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: arvdme...@gmail.com
  Target Milestone: ---

At least in the last few versions of kdenlive, the variance in the chroma key
effect isn't working for me.

I finally got round to compiling kdenlive to try and find the issue, and found
that in the melt module filter_chroma.c the 

mlt_properties_get_double( MLT_FILTER_PROPERTIES( this ), "variance" )

always returns 0.

So, no matter what I set the variance too in the gui, it only matches the
precise pixel color.

For me the issue is resolved when changing kdenlive chroma.xml parameter type
from "constant" to "double".

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

[plasmashell] [Bug 377190] New: Crash occures when clicking on the activity button on the desktop

[David]

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

Bug ID: 377190
   Summary: Crash occures when clicking on the activity button on
the desktop
   Product: plasmashell
   Version: 5.9.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: iratusmalus...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.3)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.11-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Crash occures when clicking on the activity button on the desktop. It crashes
every time.

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 0x7f354e885800 (LWP 5370))]

Thread 9 (Thread 0x7f347e1fe700 (LWP 5812)):
#0  0x7f3547f3e4ed in read () at /usr/lib/libc.so.6
#1  0x7f3542da4aa0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f3542d6026e in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f3542d60744 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f3542d608bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f354886606b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f354880f89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f3548631a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f3480ad00a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#9  0x7f35486366d8 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f3547501454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f3547f4b7df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f3492f57700 (LWP 5686)):
#0  0x7f3542da5e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f3542d5f7b4 in g_main_context_release () at
/usr/lib/libglib-2.0.so.0
#2  0x7f3542d6075a in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f3542d608bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f354886606b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f354880f89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f3548631a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f354c31efd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f35486366d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f3547501454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f3547f4b7df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f35222a7700 (LWP 5654)):
#0  0x7f354750710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f354e013234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f354e013279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f3547501454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3547f4b7df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f3523564700 (LWP 5647)):
#0  0x7f3542da5e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f3542d601b4 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7f3542d60744 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f3542d608bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f354886606b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f354880f89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f3548631a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f35486366d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f3547501454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f3547f4b7df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f352df6d700 (LWP 5633)):
#0  0x7f3542da5e60 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f3542d5fd90 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f3542d606cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f3542d608bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f354886606b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f354880f89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f3548631a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f354b76b025 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f35486366d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f3547501454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f3547f4b7df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f352700 (LWP 5493)):
#0  0x7f3547f4248d in poll () at /usr/lib/libc.so.6
#1  

[krusader] [Bug 377185] Don't delete first letter in "new folder" dialog (F7)

[Toni Asensi Esteve]

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

Toni Asensi Esteve  changed:

   What|Removed |Added

 CC||toni.ase...@kdemail.net
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Toni Asensi Esteve  ---
Hi! That was solved in Krusader 2.5.0. If you experience the same problem using
a recent Krusader please feel free to reopen the bug. Thanks!

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

[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Bernd Steinhauser]

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

Bernd Steinhauser  changed:

   What|Removed |Added

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

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

[kmail2] [Bug 316153] can't move or delete messages in imap inbox

[Andrej M .]

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

Andrej M.  changed:

   What|Removed |Added

 CC||andr...@ubuntu.si

--- Comment #41 from Andrej M.  ---
I wasn't affected by this bug in previous KMail versions (applications 4.14.1
and lower) but now in 16.04.3 (Kontact 5.2.3) it's here and it's extremely
annoying.

Restarting akonadi doesn't help.
Restarting KMail doesn't help, however, the Move option is active for a
fraction of the second and then becomes inactive.

Only thing that helps for a while is recreating the account, but I want to use
the program to read mails not to reconfigure it all the time.

As this is certainly not resolved please reopen it.

Best regards,
Andrej

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

[kdelibs] [Bug 377189] New: Crashed on reboot after updating lots of software

[Jeffrey Reagan]

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

Bug ID: 377189
   Summary: Crashed on reboot after updating lots of software
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kded
  Assignee: unassigned-b...@kde.org
  Reporter: jeffrea...@gmail.com
  Target Milestone: ---

Application: kded4 (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 4.10.1-1-default x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Rebooting after updating software did it. Massive upgrade was selected. Some
repositories not found, skipped. Didn't reboot after the first couple upgrades
were completed (was requested to do so but oops). Yast was running twice at
once, shut off one but that took time. Overlapping yast instances might have
buggered something.

-- Backtrace:
Application: KDE Daemon (kded4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f79ce3097c0 (LWP 1447))]

Thread 4 (Thread 0x7f79b6287700 (LWP 1552)):
#0  0x7f79cb8b866d in poll () at /lib64/libc.so.6
#1  0x7f79c89b5be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f79c89b5cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f79ccf8e0de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f79ccf5fe6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f79ccf60165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f79cce5d0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f79b9cac287 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#8  0x7f79cce5f79f in  () at /usr/lib64/libQtCore.so.4
#9  0x7f79ccbc8454 in start_thread () at /lib64/libpthread.so.0
#10 0x7f79cb8c137f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f79b5a86700 (LWP 1553)):
#0  0x7f79c89b536b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f79c89b5b03 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f79c89b5cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f79ccf8e0de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f79ccf5fe6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f79ccf60165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f79cce5d0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f79cce5f79f in  () at /usr/lib64/libQtCore.so.4
#8  0x7f79ccbc8454 in start_thread () at /lib64/libpthread.so.0
#9  0x7f79cb8c137f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f79b5285700 (LWP 1554)):
#0  0x7f79ccbd0f1c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7f79ccbcabb6 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2  0x7f79ce13fd0d in tls_get_addr_tail () at /lib64/ld-linux-x86-64.so.2
#3  0x7f79cbc0c8e0 in __cxa_get_globals () at /usr/lib64/libstdc++.so.6
#4  0x7f79cbc0c7a9 in std::uncaught_exception() () at
/usr/lib64/libstdc++.so.6
#5  0x7f79cce5539c in  () at /usr/lib64/libQtCore.so.4
#6  0x7f79cce55684 in qWarning(char const*, ...) () at
/usr/lib64/libQtCore.so.4
#7  0x7f79ccf8e2ce in  () at /usr/lib64/libQtCore.so.4
#8  0x7f79c89b5661 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f79c89b5b7b in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7f79c89b5cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7f79ccf8e0de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#12 0x7f79ccf5fe6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#13 0x7f79ccf60165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#14 0x7f79cce5d0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#15 0x7f79ccf41783 in  () at /usr/lib64/libQtCore.so.4
#16 0x7f79cce5f79f in  () at /usr/lib64/libQtCore.so.4
#17 0x7f79ccbc8454 in start_thread () at /lib64/libpthread.so.0
#18 0x7f79cb8c137f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f79ce3097c0 (LWP 1447)):
[KCrash Handler]
#5  0xdc30 in  ()
#6  0x7f79ce13d48a in call_init.part () at /lib64/ld-linux-x86-64.so.2
#7  0x7f79ce13d59b in _dl_init () at /lib64/ld-linux-x86-64.so.2
#8  0x7f79ce141ac8 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#9  0x7f79ce13d334 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#10 0x7f79ce141269 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#11 0x7f79c94deee9 in dlopen_doit () at /lib64/libdl.so.2
#12 0x7f79ce13d334 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2

[krita] [Bug 377188] New: Cannot get smooth brush with OpenGL enabled

[Erich]

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

Bug ID: 377188
   Summary: Cannot get smooth brush with OpenGL enabled
   Product: krita
   Version: 3.1.2
  Platform: unspecified
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OpenGL Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: erich...@gmail.com
  Target Milestone: ---

Created attachment 104358
  --> https://bugs.kde.org/attachment.cgi?id=104358=edit
sample

On macOS Sierra I can´t get smooth lines when OpenGL is enabled. The attached
file shows a sample.

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

[kwin] [Bug 377187] New: multiscreen behavior settings dont work

[Bronson]

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

Bug ID: 377187
   Summary: multiscreen behavior settings dont work
   Product: kwin
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bronsonmath...@gmail.com
  Target Milestone: ---

Setting multiscreen behavior (window actions & behaviors > active screen
follows mouse) doesnt work. My applications keep opening on the secondary
screen, which is not where my mouse is.

Also, is there anyway to force all applications to load on the primary display?

I think a part of the issue may be the I have my secondary monitor on the left
instead of the default right. This looks to play havoc with the kde window
manager...

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

[kmail2] [Bug 377150] Use real attachment's file name when opening an attachment

[Andy Goss]

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

Andy Goss  changed:

   What|Removed |Added

 CC||aeg...@internode.on.net

--- Comment #1 from Andy Goss  ---
I confirm this, it applies at least to PDF files, plus .doc and .odt files
created by Libre Office.

In addition, on Wednesday I received a .doc attachment that Libre Office opened
with a filename of "untitled 1". And it still does today (as do .doc/.odt
attachments to older emails), when attachments sent today open as
"messageviewer_<*>" 

As far back as I can go PDF files want to save as "messageviewer_<*>".

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

[kdenlive] [Bug 377186] New: problems with preview image, uploading video and music

[nymphy]

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

Bug ID: 377186
   Summary: problems with preview image, uploading video and music
   Product: kdenlive
   Version: 16.12.1
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: sky_magic...@ymail.com
  Target Milestone: ---

I guess it's because it's new in Windows altogether but so far I have problems
with it not working with mpeg4 videos and mp3 saying it's invalid, and images I
try and use (no matter which method to upload them--and there are a few) don't
show up in the preview very well. When nothing is selected, the preview is
green static. A selected image from the timeline turns it pink and slightly
transparent, also distorting the image terribly. Previewing opens up melt.exe,
and that doesn't work, it errors out.

Also, is there a way to uninstall? I can't find it anywhere, it doesn't show up
in control panel, not right-click-uninstall.. Wanted to see if that could fix
the issue, but it's impossible if there's no accessible way to wipe it and try
again. Also, deleting the folders outright don't help, the pop-up says kdenlive
is still open somewhere in the system.

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

[kwin] [Bug 377171] Clicking outside of any presented windows should show desktop

[Vishnu]

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

--- Comment #2 from Vishnu  ---
I don't understand. How so? If one accidentally clicks outside one of the
windows and everything minimises, one could just use the shortcut/screen-edge
to get the present windows back again, and choose. There's nothing lost. Also,
if they made such a click, they would would very quickly learn of the existence
of that feature.

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

[plasmashell] [Bug 365308] Left clicking on some system tray icons results in no action

[Adam Treat]

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

--- Comment #9 from Adam Treat  ---
Just tried with 'Hangouts for Chrome' on KDE neon with plasma 5.9.3 as above
and can reproduce as well.

That leads me to believe this is a distro/packaging problem since Arch doesn't
exhibit the issue, but KDE neon does.

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

[plasmashell] [Bug 365308] Left clicking on some system tray icons results in no action

[Adam Treat]

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

Adam Treat  changed:

   What|Removed |Added

Version|5.7.0   |5.9.3
   Platform|Fedora RPMs |Neon Packages

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

[plasmashell] [Bug 365308] Left clicking on some system tray icons results in no action

[Adam Treat]

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

Adam Treat  changed:

   What|Removed |Added

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

--- Comment #8 from Adam Treat  ---
I can reproduce this with latest KDE neon package of KDE Plasma Desktop 5.9.3.

Install latest tomboy application and minimize to the systray and left click
and no action occurs.

KDE Plasma Desktop - 4:5.9.3-0neon+16.04+build55
Tomboy - 1.15.4-0ubuntu3

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

[kdevelop] [Bug 373120] KDevelop crashes / files not closed on Windows

[Kevin Funk]

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

--- Comment #2 from Kevin Funk  ---
Note: Please try KDevelop 5.0.4, we've patched Clang slightly.

Please report if that fixed the issue for you!

https://www.kdevelop.org/download

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

[krita] [Bug 377146] Brush color selection does not work on several brushes

[bugzilla_noreply]

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

--- Comment #4 from b...@juno.com ---
Oops, didn't mean to poke the bear.  No, I just want to know how to make
them work, including how to use the ones I don't understand.  Is there
another source of info that does not use technical terms to answer
technical problems?  Like, could it tell me exactly what "painting with
surfaces", not colors, means?  And how to access that, in terms of "go to
this spot and click this/choose that option"?
I love what I have been able to get the program to do and don't want to
ditch the thing  because I don't understand chunks of it.  Much better to
learn how to work with those tools.
Thanks



On Fri, 03 Mar 2017 20:34:59 + Boudewijn Rempt
 writes:
> https://bugs.kde.org/show_bug.cgi?id=377146
> 
> --- Comment #3 from Boudewijn Rempt  ---
> If this is too abstruse, don't use those brushes. Use other brushes. 
> These
> brushes are meant for people who need this feature; you don't need 
> it, don't
> use it! There are very likely more features in Krita that are weird 
> or
> incomprehensible unless you urgently need them. That doesn't mean 
> the features
> are buggy, though.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

Warning: Don't Use Probiotics Before You See This
Gundry MD
http://thirdpartyoffers.juno.com/TGL3141/58ba201053ca820102714st03vuc

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

[krusader] [Bug 377185] Don't delete first letter in "new folder" dialog (F7)

[Master]

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

Master  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

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

[krusader] [Bug 377185] New: Don't delete first letter in "new folder" dialog (F7)

[Master]

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

Bug ID: 377185
   Summary: Don't delete first letter in "new folder" dialog (F7)
   Product: krusader
   Version: 2.4.0-beta3 "Single Step"
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: um...@bk.ru
  Target Milestone: ---

When typed several letters in new folder dialog, and press cross in right side,
letters to highlight. But backspace key don't work. Else not press cross try
backspace key, all letters deleted, except for first letter, why this?

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

[clazy] [Bug 377134] Class method wrongly tagged as Qt signal if defined after class declaration with Q_SIGNALS as last section

[Sergio Martins]

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

--- Comment #1 from Sergio Martins  ---
Git commit 9315e636246a9bd365b3d22f66fbebefa5757e0e by Sergio Martins.
Committed on 04/03/2017 at 01:36.
Pushed by smartins into branch '1.1'.

incorrect-emit: Add failing unit-test for bug 377134

A  +20   -0tests/incorrect-emit/bug377134.cpp [License: UNKNOWN]  *
A  +0-0tests/incorrect-emit/bug377134.cpp.expected
M  +4-0tests/incorrect-emit/config.json

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


https://commits.kde.org/clazy/9315e636246a9bd365b3d22f66fbebefa5757e0e

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

[clazy] [Bug 377140] Signal methods no longer known as signals if signal method definition has been seen (e.g. with automoc)

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[clazy] [Bug 377140] Signal methods no longer known as signals if signal method definition has been seen (e.g. with automoc)

[Sergio Martins]

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

--- Comment #1 from Sergio Martins  ---
Git commit 6d83b9398776eaa15505f496c5f7161a464c476e by Sergio Martins.
Committed on 04/03/2017 at 01:30.
Pushed by smartins into branch '1.1'.

incorrect-emit: Add failing unit-test for bug 377140

A  +30   -0tests/incorrect-emit/bug377140.cpp [License: UNKNOWN]  *
A  +0-0tests/incorrect-emit/bug377140.cpp.expected
M  +6-2tests/incorrect-emit/config.json

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


https://commits.kde.org/clazy/6d83b9398776eaa15505f496c5f7161a464c476e

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

[kdenlive] [Bug 377184] New: Load Title default path is not taken from previous load

[Phuoc]

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

Bug ID: 377184
   Summary: Load Title default path is not taken from previous
load
   Product: kdenlive
   Version: 16.12.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: h...@huaonline.com
  Target Milestone: ---

Created attachment 104356
  --> https://bugs.kde.org/attachment.cgi?id=104356=edit
Load Title dialog

Win7x64 16.12.1
Load title path is defaulted to the same location every time.

Steps:
1) New project.
2) Add title clip and load an existing title from a location other than
kdenlive directory.
3) Add 2nd title clip.
The Load Title dialog is still defaulted to the kdenlive directory, see
screenshot.

See also initial G+ discussion:
https://plus.google.com/109117066657466745395/posts/VSHZo7wVgWd

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

[kdevelop] [Bug 377183] New: Qt Help GHNS needs to be moved to store.kde.org

[Sven Brauch]

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

Bug ID: 377183
   Summary: Qt Help GHNS needs to be moved to store.kde.org
   Product: kdevelop
   Version: 5.0.80
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@svenbrauch.de
  Target Milestone: ---

It's currently using collect.kde.org, which is being phased out (software is
outdated and we are the only users).

Investigation is needed what needs to be done to move the little data we have
over there, and then the providers URL needs to be changed in the .knsrc file.

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

[kdevelop] [Bug 229112] Add OpenCL C language support

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D4930
 CC||kf...@kde.org

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

[kdevelop] [Bug 229112] Add OpenCL C language support

[Kevin Funk]

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

--- Comment #6 from Kevin Funk  ---
Patch here: https://phabricator.kde.org/D4930

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

[clazy] [Bug 377140] Signal methods no longer known as signals if signal method definition has been seen (e.g. with automoc)

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |smart...@kde.org

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

[clazy] [Bug 377134] Class method wrongly tagged as Qt signal if defined after class declaration with Q_SIGNALS as last section

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |smart...@kde.org

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

[kwin] [Bug 376115] Kwin crash on 'Magic Lamp' effect

[Grief]

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

--- Comment #4 from Grief  ---
I have a workaround!
TL;DR: do `export SVGA_VGPU10=0` anywhere so it would be applied to all 3D
apps.

reference: https://bugs.launchpad.net/stellarium/+bug/1577494

here (https://github.com/ros-simulation/gazebo_ros_pkgs/issues/457) man says
that this in probably the issue in app itself, not it vmware, but this is
doubtable

also here (https://www.mesa3d.org/vmware-guest.html) page says that the
variable from above "may be useful to work around application bugs (such as
incorrect use of the OpenGL 3.x core profile).", so it might be the reason

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

[kaddressbook] [Bug 365944] KAddressbook crashes on startup with configured CardDav

[Ilpo Kantonen]

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

--- Comment #22 from Ilpo Kantonen  ---
(In reply to Ilpo Kantonen from comment #21)
> I tried again to solve kaddressbook crash. At last I deleted all contacts.
> But kaddressbook crashed again:
> 
> KTranscript: Loaded module: /usr/share/locale/fi/LC_SCRIPTS/ki18n5/ki18n5.js
> "Interpolation {$[gen %1]} in {$[gen %1] } failed: Non-string
> return value: undefined"
> "Interpolation {$[gen %1]} in {$[gen %1] käyttö} failed: Non-string
> return value: undefined"
> "Interpolation {$[elat %1]} in { $[yleisnimi_...} failed: Non-string
> return value: undefined"
> "KAddressBook::GlobalContactSession"

The whole console log:

$ kaddressbook
()
""
connectToServer "/tmp/akonadi-ilpo.8zwddF/akonadiserver.socket"
"/subscriber/kaddressbook_17791_E2SHkK"
connectToServer "/tmp/akonadi-ilpo.8zwddF/akonadiserver.socket"
"/subscriber/kaddressbook_17791_lp1Bap"
connectToServer "/tmp/akonadi-ilpo.8zwddF/akonadiserver.socket"
"/subscriber/kaddressbook_17791_7YZEBe"
connectToServer "/tmp/akonadi-ilpo.8zwddF/akonadiserver.socket"
KTranscript: Loaded property map:
/usr/share/locale/fi/LC_SCRIPTS/ki18n5/general.pmapc
KTranscript: Loaded module: /usr/share/locale/fi/LC_SCRIPTS/ki18n5/ki18n5.js
"Interpolation {$[gen %1]} in {$[gen %1] } failed: Non-string
return value: undefined"
"Interpolation {$[gen %1]} in {$[gen %1] käyttö} failed: Non-string
return value: undefined"
"Interpolation {$[elat %1]} in { $[yleisnimi_...} failed: Non-string
return value: undefined"
"KAddressBook::GlobalContactSession"
connectToServer "/tmp/akonadi-ilpo.8zwddF/akonadiserver.socket"
"/subscriber/kaddressbook_17791_RkJLm7"
connectToServer "/tmp/akonadi-ilpo.8zwddF/akonadiserver.socket"
done
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kaddressbook path = /usr/bin pid = 17791
KCrash: Arguments: /usr/bin/kaddressbook 
KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0

[1]+  Pysäytetty kaddressbook
ilpo@ilpow:~/.local/share/contacts$ QSocketNotifier: Invalid socket 15 and type
'Read', disabling...
QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 24 and type 'Read', disabling...
QSocketNotifier: Invalid socket 26 and type 'Read', disabling...

[1]+  Poistui 253 kaddressbook
$

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

[kaddressbook] [Bug 365944] KAddressbook crashes on startup with configured CardDav

[Ilpo Kantonen]

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

Ilpo Kantonen  changed:

   What|Removed |Added

 CC||i...@iki.fi

--- Comment #21 from Ilpo Kantonen  ---
I tried again to solve kaddressbook crash. At last I deleted all contacts. But
kaddressbook crashed again:

KTranscript: Loaded module: /usr/share/locale/fi/LC_SCRIPTS/ki18n5/ki18n5.js
"Interpolation {$[gen %1]} in {$[gen %1] } failed: Non-string
return value: undefined"
"Interpolation {$[gen %1]} in {$[gen %1] käyttö} failed: Non-string
return value: undefined"
"Interpolation {$[elat %1]} in { $[yleisnimi_...} failed: Non-string
return value: undefined"
"KAddressBook::GlobalContactSession"

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

[kdevelop] [Bug 238456] Wrong order processing add_subdirectory

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #2 from Aleix Pol  ---
We are not processing directories anymore

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

[kdenlive] [Bug 377182] New: help me

[randsongameplays]

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

Bug ID: 377182
   Summary: help me
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: randsongamepl...@gmail.com
  Target Milestone: ---

Created attachment 104355
  --> https://bugs.kde.org/attachment.cgi?id=104355=edit
is a tool

When i try to use this, it don't moves. i don't know what is it.

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

[okular] [Bug 376692] Search function fails to find phrases split over two lines

[Tom Colley]

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

--- Comment #4 from Tom Colley  ---
(In reply to Albert Astals Cid from comment #3)
> Searching code is hard given we basically have to guess what's in the PDF.

Hi Albert - I don't understand your comment. This request is not about
searching code; it's about searching for text (a phrase), in a pdf file. By a
phrase, I mean two or more words separated by space. The PDF creation process
tends to eliminate spaces at the end of lines and Okular's search function
doesn't appear to take this into account. I guess I'm asking for a search
function that can interpret line breaks as spaces, though the implementation
would have to be more considered.  Some attention has already been put into
Okular's search function around this, as shown by the way searching the
provided pdf for:

"united states"

finds the third instance, which is formatted with a dash and a line break:

"Unit-
ed States"

So the search function will find instances of phrases split by a dash and a
line break, but not separated by a line break only!

Effective searching for phrases is a feature most users will find helpful.

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

[okular] [Bug 376300] okular doesn't print the form characters correctly

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1

--- Comment #11 from Albert Astals Cid  ---
Ok

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

[okular] [Bug 376692] Search function fails to find phrases split over two lines

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #3 from Albert Astals Cid  ---
Searching code is hard given we basically have to guess what's in the PDF.

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

[okular] [Bug 371887] .ps-files were not displayed since last update of ghostscript

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||vt...@cox.net

--- Comment #10 from Wolfgang Bauer  ---
*** Bug 377120 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 377120] invalidaccess -7

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DUPLICATE

--- Comment #5 from Wolfgang Bauer  ---
(In reply to vtwin farriers from comment #3)
> Ghostscript version is 7.09 on Centos 7.3.1611.
> 
> the "fix" in comment 7 works here as well, although it is line 2022 rather
> than line 2024

Ok, great!

Just in case it wasn't clear already from the other bug report, that is
actually an upstream fix in ghostscript:
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=99e331527d541a8f01ad5455c4eb2aabd67281a6;hp=0d4644c003067fc14ca1db9c600dce420c06e6b1

IMHO, you should ask your distribution to backport that or upgrade ghostscript
to the latest version.
This will not only affect okular, but any application that uses libspectre
(e.g. evince) and maybe others too.

In any case, I suppose we should rather close this as duplicate then...

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

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

[okular] [Bug 376845] Okular ignores default view setting

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Albert Astals Cid  ---
You understand default view is for documents you've never opened before right?
For the rest the last view you used in those documents is used.

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

[okular] [Bug 377128] Zooming with ctrl+scrolling too fast

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/oku
   ||lar/7a50ce0edfc9be8bd23441e
   ||52a4f3a0c60f7e60f
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Albert Astals Cid  ---
Git commit 7a50ce0edfc9be8bd23441e52a4f3a0c60f7e60f by Albert Astals Cid.
Committed on 03/03/2017 at 22:56.
Pushed by aacid into branch 'Applications/16.12'.

Accumulate Control+Wheel Deltas until they reach
QWheelEvent::DefaultDeltasPerStep

This way zooming in/out with a touchpad is easier to control

M  +50   -28   ui/pageview.cpp

https://commits.kde.org/okular/7a50ce0edfc9be8bd23441e52a4f3a0c60f7e60f

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

[okular] [Bug 377120] invalidaccess -7

[vtwin farriers]

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

--- Comment #4 from vtwin farriers  ---
(In reply to Albert Astals Cid from comment #2)
> I find it very strange that you have exactly the same versions of all
> packages and you get different versions.
> 
> Can you confirm any related ghostscript package has exactly the same version?

I can confirm I have identical configurations on multiple machines, and the
"bug" only manifests itself on certain systems. Perhaps there is a library at a
much lower level which differs due to the graphics card that causes the problem
to manifest itself. The machines I have had difficulty with thus far are all
running kmod-nvidia from the epel repository as they have NVidia cards. The few
machines I have which have not had problems reported thus far have intel
graphics chips on board. I have used the same .ps file for testing on both.

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

[okular] [Bug 377120] invalidaccess -7

[vtwin farriers]

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

vtwin farriers  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from vtwin farriers  ---
Ghostscript version is 7.09 on Centos 7.3.1611.

the "fix" in comment 7 works here as well, although it is line 2022 rather than
line 2024

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

[konsole] [Bug 377181] New: Support for termcap/terminfo te@/ti@ sequences.

[Marcos Dione]

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

Bug ID: 377181
   Summary: Support for termcap/terminfo te@/ti@ sequences.
   Product: konsole
   Version: 16.12.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: mdi...@grulic.org.ar
  Target Milestone: ---

I use screen with scrolling support turned on[1]. This was working at least on
kde4's konsole and works on xterm and rxvt, and it doesn't under the specified
version. I started reading a little about terminals and termcap/info and I got
the impression that this could be fixed by configuration, but I don't have the
slightest idea how.

To reproduce:

* install screen
* add the following line to ~/.screenrc:
termcapinfo xterm ti@:te@
* start screen
* produce more lines than the current window size (for instance, cat'ing a long
file)
* try to scroll back with Shift-PageUp, but nothing happens (you can already
see that the vertical scroll bar is not growing).

--
[1] http://www.saltycrane.com/blog/2008/01/how-to-scroll-in-gnu-screen/#c7371

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

[okular] [Bug 377151] View mode is transferred to other open documents

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
I can't reproduce this issue in Okular 1.0, can anyone with the same version
give it a try?

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

[okular] [Bug 377120] invalidaccess -7

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||aa...@kde.org

--- Comment #2 from Albert Astals Cid  ---
I find it very strange that you have exactly the same versions of all packages
and you get different versions.

Can you confirm any related ghostscript package has exactly the same version?

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

[kde] [Bug 377180] New: kde4 plasma crash when plugging in iphone4

[Simon Andric]

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

Bug ID: 377180
   Summary: kde4 plasma crash when plugging in iphone4
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: simonandr...@gmail.com
  Target Milestone: ---

Application: plasma-desktop (4.11.14)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 3.19.0-80-generic x86_64
Distribution: Ubuntu 14.04.5 LTS

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

was trying to plug in iphone4 in my kde4 laptop. immediately after plugging it
in, plasma crashed and again restarted itself.

s.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Namizna lupina Plasma (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fee111e37c0 (LWP 2260))]

Thread 5 (Thread 0x7fede51d2700 (LWP 2265)):
#0  0x7ffc59db9cb6 in ?? ()
#1  0x in ?? ()

Thread 4 (Thread 0x7fedd2fca700 (LWP 2273)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fee09e9dffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7fee09e9e039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7fee04a16184 in start_thread (arg=0x7fedd2fca700) at
pthread_create.c:312
#4  0x7fee10ad937d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fed50e15700 (LWP 2274)):
#0  0x7fee042fe218 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fee0430078b in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fee04300d4b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fee04300ebc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fee0d6b37be in QEventDispatcherGlib::processEvents
(this=0x7fed4c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7fee0d6850af in QEventLoop::processEvents
(this=this@entry=0x7fed50e14de0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7fee0d6853a5 in QEventLoop::exec (this=this@entry=0x7fed50e14de0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7fee0d581c5f in QThread::exec (this=this@entry=0x2b267f0) at
thread/qthread.cpp:537
#8  0x7fee0d666823 in QInotifyFileSystemWatcherEngine::run (this=0x2b267f0)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7fee0d58432f in QThreadPrivate::start (arg=0x2b267f0) at
thread/qthread_unix.cpp:349
#10 0x7fee04a16184 in start_thread (arg=0x7fed50e15700) at
pthread_create.c:312
#11 0x7fee10ad937d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fed42038700 (LWP 2295)):
#0  0x7ffc59db9cb6 in ?? ()
#1  0x in ?? ()

Thread 1 (Thread 0x7fee111e37c0 (LWP 2260)):
[KCrash Handler]
#6  QHashData::nextNode (node=node@entry=0x6ae80f0) at tools/qhash.cpp:294
#7  0x7fee0f2af23a in operator++ (this=) at
../../include/QtCore/../../src/corelib/tools/qhash.h:427
#8  QDeclarativeVisualDataModel::_q_itemsChanged (this=0x3d87ba0, index=0,
count=6, roles=...) at graphicsitems/qdeclarativevisualitemmodel.cpp:1208
#9  0x7fee0f3da7ed in QDeclarativeVisualDataModel::qt_static_metacall
(_o=0x6ae80f0, _c=QMetaObject::ReadProperty, _id=45291440, _a=0x0) at
.moc/release-shared/moc_qdeclarativevisualitemmodel_p.cpp:406
#10 0x7fee0d69a87a in QMetaObject::activate (sender=sender@entry=0x3e5e9d0,
m=m@entry=0x7fee0d9ea6a0 ,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x0) at
kernel/qobject.cpp:3539
#11 0x7fee0d6e45a3 in QAbstractItemModel::layoutChanged
(this=this@entry=0x3e5e9d0) at
.moc/release-shared/moc_qabstractitemmodel.cpp:176
#12 0x7fee0cf9bb47 in QSortFilterProxyModelPrivate::_q_sourceDataChanged
(this=0x3e5ea80, source_top_left=..., source_bottom_right=...) at
itemviews/qsortfilterproxymodel.cpp:1184
#13 0x7fee0d69a87a in QMetaObject::activate (sender=sender@entry=0x3cb2120,
m=m@entry=0x7fee0d9ea6a0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc59ce48a0)
at kernel/qobject.cpp:3539
#14 0x7fee0d6e4527 in QAbstractItemModel::dataChanged
(this=this@entry=0x3cb2120, _t1=..., _t2=...) at
.moc/release-shared/moc_qabstractitemmodel.cpp:163
#15 0x7fed5209cad2 in Plasma::DataModel::setItems
(this=this@entry=0x3cb2120, sourceName=..., list=...) at
../../../../plasma/declarativeimports/core/datamodel.cpp:391
#16 0x7fed5209d729 in Plasma::DataModel::dataUpdated (this=0x3cb2120,
sourceName=..., data=...) at
../../../../plasma/declarativeimports/core/datamodel.cpp:222
#17 0x7fed5209e0d5 in Plasma::DataModel::qt_static_metacall 

[frameworks-kxmlgui] [Bug 375555] Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"

[Albert Astals Cid]

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

--- Comment #18 from Albert Astals Cid  ---
Did those duplicated global shortcuts actually work?

Any idea how you may have gotten them there? Did you ever edit your global
shortcuts?

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

[Phonon] [Bug 375386] HDMI device number for hotplugged audio cannot be determined easily

[dehein]

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

deh...@gmail.com  changed:

   What|Removed |Added

 CC||deh...@gmail.com

--- Comment #2 from deh...@gmail.com  ---
It is definitely unintuitive to search for a better audio output source. All in
all the complete audio toolchain seems gobbled up and you have to click through
different settings to find the correct source.
Somehow under gnome it works better. Even if you need a audio output source
extension to quickly change it, but even under settings a simple click works
and hotplug works often too. Can confirm this with a Thinkpad t520. But I have
to click audio profile HDMI 1 although I use displayport.

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

[krita] [Bug 377146] Brush color selection does not work on several brushes

[Boudewijn Rempt]

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

--- Comment #3 from Boudewijn Rempt  ---
If this is too abstruse, don't use those brushes. Use other brushes. These
brushes are meant for people who need this feature; you don't need it, don't
use it! There are very likely more features in Krita that are weird or
incomprehensible unless you urgently need them. That doesn't mean the features
are buggy, though.

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

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

[zwing99]

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

zwing99  changed:

   What|Removed |Added

 CC||zac.o...@gmail.com

--- Comment #11 from zwing99  ---
Re: Bartel's comment is there any progress on this?

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

[kdenlive] [Bug 377179] New: description of clip disappears.

[Ray Ambrosi]

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

Bug ID: 377179
   Summary: description of clip disappears.
   Product: kdenlive
   Version: 16.12.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: waxw...@gmail.com
  Target Milestone: ---

When saving a description of the clip in the clip monitor, the description is
often lost despite saving the project. 

To explain further, on numerous occasions, when I open a project, some of the
the descriptions that I have typed for each clip are gone. 

I'm running Linux Mint 18 running on a very fast corei7 computer with 32gig
ram.

Kdenlive is amazing. Thank you for your contributions!

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

[krita] [Bug 377146] Brush color selection does not work on several brushes

[bugzilla_noreply]

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

--- Comment #2 from b...@juno.com ---
"The Tangent Normal Brush Engine is an engine that is specifically designed for
drawing normal maps, of the tangent variety. These are in turn used in 3d
programs and game engines to do all sorts of lightning trickery. Common uses of
normal maps include faking detail where there is none, and to drive
transformations(Flow Maps). "  Sorry, the above is as helpful as Windows Help
files:  It means nothing to me, Swahili, etc.  This clearly DOES (won't let me
underline that word instead of caps), clearly does paint in color, blue-purple.
 I don't know what faking detail means.  If I paint this on top of something
else, it just blots it out, just as any other paint would.  Do ;you folks have
a Primer for your Manual??   Signed, Feeling like I am Drowning

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

[krita] [Bug 374562] Random crash when moving/transforming a layer

[supaiku]

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

--- Comment #10 from supaiku  ---
May be noteworthy, that it (subjectively) only happens when I'm transforming a
Layer inside a Group Layer.

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

[krita] [Bug 374562] Random crash when moving/transforming a layer

[supaiku]

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

--- Comment #9 from supaiku  ---
Hey,

I located another crash with a different stacktrace and I'm sure that's a
completely different issue, but it's also related to Layer Transform.

Whenever it happened, I was about to apply the transform by hitting enter.


*** Error in `/home/supaiku/hacking/krita-install/bin/krita': malloc(): memory
corruption (fast): 0x1f579cef ***
=== Backtrace: =
/usr/lib/libc.so.6(+0x70c4b)[0x7fffec249c4b]
/usr/lib/libc.so.6(+0x76fe6)[0x7fffec24ffe6]
/usr/lib/libc.so.6(+0x79411)[0x7fffec252411]
/usr/lib/libc.so.6(__libc_malloc+0x54)[0x7fffec253d44]
/usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x2a0)[0x7fffed0cd9b0]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN24KisQueuesProgressUpdater15sigStartTickingEv+0x29)[0x762fe111]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN24KisQueuesProgressUpdater14updateProgressEiRK7QString+0xf6)[0x761410a0]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN18KisUpdateScheduler14progressUpdateEv+0x11b)[0x7613e221]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN18KisUpdateScheduler13processQueuesEv+0x1b8)[0x7613f2ac]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN18KisUpdateScheduler9endStrokeE12QWeakPointerI9KisStrokeE+0x57)[0x7613eb3b]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN8KisImage9endStrokeE12QWeakPointerI9KisStrokeE+0x42)[0x7615e18e]
/home/supaiku/hacking/krita-install/lib64/kritaplugins/kritatooltransform.so(+0x310d5)[0x7fffa43d70d5]
/home/supaiku/hacking/krita-install/lib64/kritaplugins/kritatooltransform.so(+0x2fdea)[0x7fffa43d5dea]
/home/supaiku/hacking/krita-install/lib64/kritaplugins/kritatooltransform.so(+0xca487)[0x7fffa4470487]
/usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x639)[0x7fffed0cdd49]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN8KisImage21sigStrokeEndRequestedEv+0x29)[0x762fac9d]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN8KisImage16requestStrokeEndEv+0x18)[0x7615e2ea]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(+0x586422)[0x776e2422]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN18KisShortcutMatcher30tryRunSingleActionShortcutImplIN2Qt3KeyE6QEventEEbT_PT0_RK4QSetIS2_E+0x1a4)[0x776eb2fc]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN18KisShortcutMatcher10keyPressedEN2Qt3KeyE+0x5f)[0x776e9593]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN15KisInputManager15eventFilterImplEP6QEvent+0x2f4)[0x776d58d6]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN15KisInputManager11eventFilterEP7QObjectP6QEvent+0x1da)[0x776d55e0]
[New Thread 0x7fff8574f700 (LWP 26970)]
/usr/lib/libQt5Core.so.5(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x111)[0x7fffed0a21a1]
/usr/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x75)[0x7fffedf88325]
/usr/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x1c2e)[0x7fffedf9152e]
[New Thread 0x7fff79ffd700 (LWP 26971)]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN14KisApplication6notifyEP7QObjectP6QEvent+0x45)[0x7776cb11]
/usr/lib/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x110)[0x7fffed0a2440]
/usr/lib/libQt5Widgets.so.5(+0x1b7e1b)[0x7fffedfece1b]
/usr/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x9c)[0x7fffedf8834c]
/usr/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x261)[0x7fffedf8fb61]
/home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN14KisApplication6notifyEP7QObjectP6QEvent+0x45)[0x7776cb11]
/usr/lib/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x110)[0x7fffed0a2440]
/usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate15processKeyEventEPN29QWindowSystemInterfacePrivate8KeyEventE+0xe8)[0x7fffed5ec4b8]
/usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE+0x115)[0x7fffed5f18a5]
/usr/lib/libQt5Gui.so.5(_ZN29QWindowSystemInterfacePrivate24processWindowSystemEventEPNS_17WindowSystemEventE+0x45)[0x7fffed5ce2b5]
/usr/lib/libQt5Gui.so.5(_ZN22QWindowSystemInterface19handleShortcutEventEP7QWindowmi6QFlagsIN2Qt16KeyboardModifierEEjjjRK7QStringbt+0x128)[0x7fffed5d1568]
/usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate15processKeyEventEPN29QWindowSystemInterfacePrivate8KeyEventE+0x134)[0x7fffed5ec504]
/usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE+0x115)[0x7fffed5f18a5]

[kmymoney4] [Bug 377119] Icons still missing

[NSLW]

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

--- Comment #5 from NSLW  ---
(In reply to Sean from comment #4)
> Why is this bug "poorly described", what informations do you need?
> But if I get it right, it will be fixed in version 5.

No icon theme name provided. 
I bet your categories icon would pop out if you would have got oxygen theme
installed and set globally.

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

[kmymoney4] [Bug 377119] Icons still missing

[Sean]

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

--- Comment #4 from Sean  ---
Why is this bug "poorly described", what informations do you need?
But if I get it right, it will be fixed in version 5.

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

[Spectacle] [Bug 377178] New: Very high CPU usage when dragged image hovers the panel

[Michail Vourlakos]

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

Bug ID: 377178
   Summary: Very high CPU usage when dragged image hovers the
panel
   Product: Spectacle
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: mvourla...@gmail.com
  Target Milestone: ---

When the user drags the image screenshot over the panel the spectacle's cpu
usage go crazy...
This makes difficult some times for the user to directly hover with that image
an app e.g. internet, mail etc. in order to attach it in that app

The problem was first noticed with Latte Dock but it is confirmed that it also
occurs with the original plasma panels... 

confirmed also with plasma: 5.9.3

Steps to reproduce: the user drags the screenshot image and continuously hovers
a panel with it

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

[kile] [Bug 376996] Switching to Globalmenu and back keeps menu disabled

[Nikita Skovoroda]

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

Nikita Skovoroda  changed:

   What|Removed |Added

 CC||chalk...@gmail.com

--- Comment #1 from Nikita Skovoroda  ---
Probably related: https://bugs.kde.org/show_bug.cgi?id=376517#c4 and
https://bugs.kde.org/show_bug.cgi?id=376517#c5.

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

[kwin] [Bug 377155] [Wayland] Caps Lock does not run on XWayland applications

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
Hmm, so far I thought 1.19 fixed all those issues.

-- 
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

[Stefano Forli]

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

--- Comment #258 from Stefano Forli  ---
Apologies for missing to report important details, but I wrote it elsewhere and
got lost in cut-n-pasting it.

I found the problem on Kubuntu 16.04.2 running KDE 5.5 on Intel HD4000 GPU.
I will try some backport repositories for getting something newer, but at least
there's hope.

(I'm wondering why it's still reported as open, then, I may have skipped the
rant...)

Thanks for the advice!


EDIT: comment intercepted mid-air by Buovjaga, apparently it's a closed bug,
indeed.

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

[kwin] [Bug 377100] Wayland switches my monitors

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
Please raise that to kscreen. The primary should only be presented on platforms
supporting it.

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

[kwin] [Bug 377171] Clicking outside of any presented windows should show desktop

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Martin Gräßlin  ---
The wished for functionality would be highly confusing for misclicks.

-- 
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

[Buovjaga]

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

Buovjaga  changed:

   What|Removed |Added

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

--- Comment #257 from Buovjaga  ---
This report has too many comments to be useful for developers. I am reverting
status to fixed.

If you are still seeing some weirdness, please open new reports for your
specific problems.

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

[frameworks-kio] [Bug 377144] Make folder dialog maximizes to dolphin window

[Alex]

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

--- Comment #2 from Alex  ---
I can add, that when I resize that window dolphin remembers size and opens
smaller (5.9.3)

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

[krita] [Bug 376553] the color of a frame in the animation timeline is not copied with the frame

[bugzilla_noreply]

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

joup...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kri
   ||ta/ddeee5850af5494fb575898e
   ||0e0e1e7e96767046

--- Comment #2 from joup...@gmail.com ---
Git commit ddeee5850af5494fb575898e0e0e1e7e96767046 by Jouni Pentikäinen.
Committed on 03/03/2017 at 18:31.
Pushed by jounip into branch 'master'.

Use copy constructors when duplicating keyframes

This helps to ensure that all related data (such as color label)
will be copied.

M  +15   -4libs/image/kis_raster_keyframe_channel.cpp
M  +9-2libs/image/kis_scalar_keyframe_channel.cpp

https://commits.kde.org/krita/ddeee5850af5494fb575898e0e0e1e7e96767046

-- 
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

[Enrico Tagliavini]

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

--- Comment #256 from Enrico Tagliavini  ---
(In reply to Stefano Forli from comment #255)
> Any clues on when it's going to be addressed?

For me this has been fixed a long time ago, namely in plasma version 5.8. It
looks like someone may still experience the issue when using the proprietary
nvidia driver. While this is unfortunate it is also not trivial at all to fix
as it's a driver specific problem.

I would recommend to be sure you are using nothing older than plasma 5.8 and,
for the sake of testing, trying to switch to a different driver if you are
using the proprietary nvidia driver.

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #11 from Eike Hein  ---
Fixed by 8028a500e3b2 (and up-merges) in plasma-workspace. The fix will be in
the next round of 5.8.x and 5.9.x bugfix releases.

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

[umbrello] [Bug 377138] Umbrello might benefit from a make check target

[Kip]

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

--- Comment #2 from Kip  ---
Thanks Ralf for your lightning fast fix as usual.

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

[kdeconnect] [Bug 344432] SFTP: When attempting to view kdeconnect in dolphin it crashes

[bugzilla_noreply]

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

log...@questionable-url.com changed:

   What|Removed |Added

 CC||log...@questionable-url.com

--- Comment #1 from log...@questionable-url.com ---
Also on found on KDE Neon User Edition with newest updates.

Following same steps as voncloft, also tried using Dolphin as root user, pulled
this from terminal (launched with sudo dolphin)

kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so'
kdeconnect.kio: Setting host:  "7bbbc87b4655f0d8"
kdeconnect.kio: Setting host:  "7bbbc87b4655f0d8"
kdeconnect.kio: Listing... QUrl("kdeconnect://7bbbc87b4655f0d8/")
kdeconnect.kio: ListDevice "7bbbc87b4655f0d8"
kdeconnect.kio: Stat:  QUrl("kdeconnect://7bbbc87b4655f0d8/")
kdeconnect.kio: Error in DBus request:
QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path
'/modules/kdeconnect/devices/7bbbc87b4655f0d8/sftp'")

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Eike Hein]

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

--- Comment #10 from Eike Hein  ---
Patch under review: https://phabricator.kde.org/D4928

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #9 from Eike Hein  ---
I can reproduce this problem now, for some reason when pinning we pick
krita_odg.desktop over the other .desktop file.

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Alex]

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

--- Comment #8 from Alex  ---
Sure I did, but when I start krita second icon appears so I pin second one and
remove other but then I loose menu. So choice is: two icons or one without
menu.

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

[Discover] [Bug 377175] Discover: wifi used to identify updates but internet declared "missing" when updates requested

[Michael]

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

Michael  changed:

   What|Removed |Added

 CC||mwinth...@comcast.net

--- Comment #1 from Michael  ---
I am using kubuntu 16.04.1 (or maybe .2) with kde desktop and plasma screen.

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

[Breeze] [Bug 377173] QTabWidget & QTabBar have different spacing in document mode between tabbar and controlled container view

[Hugo Pereira Da Costa]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pereira.da.costa@gmail
   ||.com

--- Comment #3 from Hugo Pereira Da Costa  ---
Hi Friedrich,

thanks for reporting and sending the test app. 
I assume it looks right with stock themes (fusion, and/or plastique, depending
on the Qt version).

i remember having fiddled with this in the past (Qt4 and oxygen), and not found
an acceptable way to fix. if I remember the issue was connected to the rounding
at the corners in an (non document mode) tab widget, which was requiring some
extra spacing in the tabbar, not needed in QTabBar mode, and not properly
cancelled in document mode. 

Still, I'll have another look.

Hugo

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

[krita] [Bug 377176] New: 'onion skin' not available for new layer if you move frames from another layer on it

[bugzilla_noreply]

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

Bug ID: 377176
   Summary: 'onion skin' not available for new layer if you move
frames from another layer on it
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: gordie.lachance+...@gmail.com
  Target Milestone: ---

Hey, 'onion skin' property for a NEW layer is not available if you move frames
from another layer on it without having created other frames first.

steps to reproduce :
- create a new layer
- move frames from another layer on it

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

[Discover] [Bug 377175] New: Discover: wifi used to identify updates but internet declared "missing" when updates requested

[Michael]

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

Bug ID: 377175
   Summary: Discover: wifi used to identify updates but internet
declared "missing" when updates requested
   Product: Discover
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mwinth...@comcast.net
  Target Milestone: ---

Discover: wifi is used to identify current updates but internet declared
'missing' when updates requested. Start discover when tray icon shows updates
available. Updates are identified in Discover selection list. Select 'UPDATE'
and password is requested. List of updates disappears and notice appears saying
network unavailable, cannot update whilst no network. Apparently connecting the
ethernet cable fixes this 'network' problem, but problem returns if ethernet
cable is removed. 
opening an x window terminal and using 'sudo apt-get update' and 'sudo apt-get
upgrade' works flawlessly over the >>missing<< wifi.

This bug is being entered over the 'missing' wifi connection.

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Eike Hein]

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

--- Comment #7 from Eike Hein  ---
So according to your config, you simply have two launchers for Krita on your
TM, one to that weird "odg" .desktop file ... remove one of the launchers?

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

[kwin] [Bug 377155] [Wayland] Caps Lock does not run on XWayland applications

[bugzilla_noreply]

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

--- Comment #2 from tro...@free.fr ---
It's XWayland 1.19.1.

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Alex]

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

--- Comment #6 from Alex  ---
Menu is shown with this launcher:
file:///usr/share/applications/org.kde.krita.desktop

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

[Oxygen] [Bug 377174] New: QTabWidget & QTabBar have different spacing in document mode between tabbar and controlled container view

[Friedrich W . H . Kossebau]

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

Bug ID: 377174
   Summary: QTabWidget & QTabBar have different spacing in
document mode between tabbar and controlled container
view
   Product: Oxygen
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: style
  Assignee: hugo.pereira.da.co...@gmail.com
  Reporter: kosse...@kde.org
  Target Milestone: ---

Created attachment 104351
  --> https://bugs.kde.org/attachment.cgi?id=104351=edit
Screenshot with Oxygen style

See https://bugs.kde.org/show_bug.cgi?id=377173 for the same issue with Breeze
style and a demo app.

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

[Breeze] [Bug 377173] QTabWidget & QTabBar have different spacing in document mode between tabbar and controlled container view

[Friedrich W . H . Kossebau]

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

--- Comment #2 from Friedrich W. H. Kossebau  ---
Created attachment 104350
  --> https://bugs.kde.org/attachment.cgi?id=104350=edit
Screenshot with Breeze style

-- 
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

[Stefano Forli]

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

Stefano Forli  changed:

   What|Removed |Added

 CC||ntro...@gmail.com

--- Comment #255 from Stefano Forli  ---
I had found this bug report while googling about this issue and I was surprised
to find out how many people are affected by it. Still, the report has been
around for a while, and there is still no fix on the way. Also, I may disagree
with the importance attributed to the bug, since it's likely to affect most of
laptop users.

Any clues on when it's going to be addressed?


(On a side note, discussions about Plasma bugs tend have this interesting
pattern: 9 out of 10 times, there's a "fix" that involves killing it in more or
less creative ways, and hope for the best. If it works, make an alias for it)

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

[Breeze] [Bug 377173] QTabWidget & QTabBar have different spacing in document mode between tabbar and controlled container view

[Friedrich W . H . Kossebau]

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

--- Comment #1 from Friedrich W. H. Kossebau  ---
Created attachment 104349
  --> https://bugs.kde.org/attachment.cgi?id=104349=edit
demo.pro, for building the demo app

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

[Breeze] [Bug 377173] New: QTabWidget & QTabBar have different spacing in document mode between tabbar and controlled container view

[Friedrich W . H . Kossebau]

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

Bug ID: 377173
   Summary: QTabWidget & QTabBar have different spacing in
document mode between tabbar and controlled container
view
   Product: Breeze
   Version: 5.9.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: QStyle
  Assignee: hugo.pereira.da.co...@gmail.com
  Reporter: kosse...@kde.org
  Target Milestone: ---

Created attachment 104348
  --> https://bugs.kde.org/attachment.cgi?id=104348=edit
main.cpp, for demoing the difference

When using both a stock QTabWidget and a self-made variant of such a widget
(e.g. when creating pages only on the fly) using QTabBar, and doing that with
both versions using the documentMode*, the padding between the tabbar
separation line and the page is inconsistent, other than expected.

See attached demo app for the inconsistency.

Of course it could be questioned who should be responsible to ensuring the
padding between a QTabBar and the container view it is controlling.
In Oxygen style the QTabBar even has a greater padding between bar separation
line and widget border, so the concept of having the padding as part of the
qtabbar seems acceptable, and might not come as such a surprise?

* See
https://doc.qt.io/qt-5/qtabwidget.html#documentMode-prop
https://doc.qt.io/qt-5/qtabbar.html#documentMode-prop

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

[plasmashell] [Bug 377153] Resizing panel too much messes attached folders

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/pla
   ||sma-framework/b99a87a320f46
   ||82939f2279e4177f40f527d0606

--- Comment #3 from Marco Martin  ---
Git commit b99a87a320f4682939f2279e4177f40f527d0606 by Marco Martin.
Committed on 03/03/2017 at 16:52.
Pushed by mart into branch 'master'.

set default hints when repr doesn't export Layout.*

when we go from full to compact repr, if the compact
doesn't export a Layout attached property, the hints shouldn't
remain those of the full repr, so reset to default values
Reviewed-by:Eike Hein

M  +12   -0src/plasmaquick/appletquickitem.cpp

https://commits.kde.org/plasma-framework/b99a87a320f4682939f2279e4177f40f527d0606

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Alex]

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

--- Comment #5 from Alex  ---
Created attachment 104347
  --> https://bugs.kde.org/attachment.cgi?id=104347=edit
file:///usr/share/applications/krita_odg.desktop

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Alex]

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

--- Comment #4 from Alex  ---
launchers=file:///usr/share/applications/krita_odg.desktop,file:///usr/share/applications/org.kde.krita.desktop

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

[kwin] [Bug 377162] Can't reduce a window to its title bar only with mouse scroll

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin  ---
Window shading is currently only implemented for X11 windows.

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Alex]

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

--- Comment #3 from Alex  ---
Created attachment 104345
  --> https://bugs.kde.org/attachment.cgi?id=104345=edit
xprop from krita window

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

[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents

[Alex]

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

--- Comment #2 from Alex  ---
Created attachment 104344
  --> https://bugs.kde.org/attachment.cgi?id=104344=edit
file:///usr/share/applications/org.kde.krita.desktop

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

[dolphin] [Bug 377172] Dolphin unable to read open copy move files with some unicode characters

[Nathan Shearer]

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

Nathan Shearer  changed:

   What|Removed |Added

 CC||k...@nathanshearer.ca

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

[dolphin] [Bug 377172] New: Dolphin unable to read open copy move files with some unicode characters

[Nathan Shearer]

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

Bug ID: 377172
   Summary: Dolphin unable to read open copy move files with some
unicode characters
   Product: dolphin
   Version: 16.12.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: k...@nathanshearer.ca
  Target Milestone: ---

Dolphin can't use files with some unicode files, often causing batch moves or
copies to fail on my systems.

Use a terminal and create a file:
# touch filename_�_filename.txt

Then try to do anything with that file in Dolphin, it will show the file, but
cannot interact with it.

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

[kwin] [Bug 377109] Plasma panels display a strange background

[Martin Gräßlin]

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

--- Comment #6 from Martin Gräßlin  ---
Good. That's what I wanted to ask next.

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

[kwin] [Bug 377155] [Wayland] Caps Lock does not run on XWayland applications

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin  ---
Which XWayland version are you using?

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

[kwin] [Bug 377171] New: Clicking outside of any presented windows should show desktop

[Vishnu]

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

Bug ID: 377171
   Summary: Clicking outside of any presented windows should show
desktop
   Product: kwin
   Version: 5.9.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: vishn...@gmail.com
  Target Milestone: ---

When in the 'Present Windows' view, it would be nice if clicking on the desktop
(instead of on one of the windows) could take me to the bare desktop. i.e.,
minimize all the windows. (like what the bottom-right corner aero thing in
MS-Windows does)

Currently, i think doing that restores the windows to the state that existed
before activating the 'Present Windows' view.

Or this could be added as an option.

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

[kwin] [Bug 364483] Wayland : Kwin's "Slide Back" effect does not work.

[Martin Gräßlin]

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

--- Comment #22 from Martin Gräßlin  ---
Thanks. That's a very useful finding. It could mean the not visible windows are
not ignored.

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