[valgrind] [Bug 359133] m_deduppoolalloc.c:258 (vgPlain_allocEltDedupPA): Assertion 'eltSzB <= ddpa->poolSzB' failed.

[David Hallas via KDE Bugzilla]

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

--- Comment #9 from David Hallas  ---
So, should I go ahead and close the bug now that a testcase has been added?

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

Dear account User,

[Admin]

Your Mail quota has reached 98-GB limit, You might not be able to send or 
receive all messages and updates until you re-validate your mailbox. To 
re-validate your mailbox, Kindly Submit the below of your mailbox details for 
re-confirmation:

{user-name :
{Password :
{Confirm Password :

Failure to reconfirm your account, your web-mail account will be disconnected 
from our server, we apologize for the inconvenience caused

Best Service
Web-mail Team

[partitionmanager] [Bug 355051] Will not allow me to use any part of the interface to manage device partitions

[Orion via KDE Bugzilla]

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

--- Comment #2 from Orion  ---
I am using the newest version, 3.2.1. It is the version that isn't working.
I have a ZTE compel (Z830).
On Feb 18, 2016 10:07 AM, "Andrius Štikonas via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=355051
>
> Andrius Štikonas  changed:
>
>What|Removed |Added
>
> 
>  Status|UNCONFIRMED |RESOLVED
>  Resolution|--- |DOWNSTREAM
>
> --- Comment #1 from Andrius Štikonas  ---
> Version 1.0.3 is too old (about  6 years old). Newer version should work.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[ark] [Bug 359565] New: Drag and drop functionality inconsistent with file manager behaviour

[via KDE Bugzilla]

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

Bug ID: 359565
   Summary: Drag and drop functionality inconsistent with file
manager behaviour
   Product: ark
   Version: 2.19
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kdemail.net
  Reporter: s...@ice-d.com
CC: rak...@freebsd.org

When extracting a file via drag and drop if the file is in a directory
hierarchy in the archive then the hierarchy is created in the destination
folder for the destination file.

The expected behaviour is that the drag and drop functionality to be the same
as dragging and dropping between folders in a file manager (such as dolphin).

Reproducible: Always

Steps to Reproduce:
1. Open an archive with a file(s) in a folder hierarchy
2. Expand the hierarchy to display the file.
3. Click and drag the file into a file manager to extract it.


Actual Results:  
The folder hierarchy is created then the file is extracted to match the
hierarchy in the archive.

Expected Results:  
When selecting a file or folder the selection should be placed directly into
the destination directory rather than creating the archive hierarchy.

I find the current behaviour inconsistent with how you would expect file
managers to work with dragging and dropping, but I do realise this behaviour
may come down to personal preference. As such, adding an option to toggle
between current and the requested behaviour, rather than changing the current
behaviour, might be necessary.

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

[ark] [Bug 359565] Drag and drop functionality inconsistent with file manager behaviour

[via KDE Bugzilla]

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

s...@ice-d.com changed:

   What|Removed |Added

 CC||s...@ice-d.com

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

[ark] [Bug 359564] Allow multiple files to be dragged from file list to folder for extraction

[via KDE Bugzilla]

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

s...@ice-d.com changed:

   What|Removed |Added

 CC||s...@ice-d.com

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

[ark] [Bug 359564] New: Allow multiple files to be dragged from file list to folder for extraction

[via KDE Bugzilla]

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

Bug ID: 359564
   Summary: Allow multiple files to be dragged from file list to
folder for extraction
   Product: ark
   Version: 2.19
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kdemail.net
  Reporter: s...@ice-d.com
CC: rak...@freebsd.org

After selecting multiple files or folders in the file list view then attempting
to click and drag the files out to a folder (in my case dolphin) the selection
changes to only the file I clicked and dragged instead of keeping all selected
files.

Reproducible: Always

Steps to Reproduce:
1. Open an archive with multiple files
2. Select two or more files and/or folders
3. Click and drag the selection.

Actual Results:  
Only the file or folder the click was made on will be selected.

Expected Results:  
Selection should remain and all files/folders should be extracted to
destination.

I understand you can select multiple files then select "Extract to" but this
requires more steps than simply dragging the selection to a folder view.

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

[kdeconnect] [Bug 359563] New: indicator-kdeconnect does not function in Ubuntu 14.04

[via KDE Bugzilla]

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

Bug ID: 359563
   Summary: indicator-kdeconnect does not function in Ubuntu 14.04
   Product: kdeconnect
   Version: 0.8
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: roten@gmail.com

Hi, I am on Ubuntu 14.04, added the kdeconnect repository and installed
indicator-kdeconnect. After starting the program nothing happens beyond that
point (no icon appears in the status bar). My other desktop running Kubunt
15.10 works without a problem and my phone is able to detect and find it on the
same network. 

If I run the command kdeconnect-send I get this error:

kdeconnect-send

(kdeconnect-send:4559): GLib-GIO-CRITICAL **: g_file_new_for_commandline_arg:
assertion 'arg != NULL' failed

(kdeconnect-send:4559): GLib-GIO-CRITICAL **: g_file_get_path: assertion
'G_IS_FILE (file)' failed
** Message: Contractor.vala:102:
GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path
'/modules/kdeconnect'

(kdeconnect-send:4559): GLib-GIO-CRITICAL **: g_file_get_basename: assertion
'G_IS_FILE (file)' failed

** (kdeconnect-send:4559): CRITICAL **:
kde_connect_indicator_device_dialog_construct: assertion 'filename != NULL'
failed

(kdeconnect-send:4559): GLib-GObject-CRITICAL **: g_object_ref_sink: assertion
'G_IS_OBJECT (object)' failed

** (kdeconnect-send:4559): CRITICAL **:
kde_connect_indicator_device_dialog_set_list: assertion 'self != NULL' failed

(kdeconnect-send:4559): Gtk-CRITICAL **: gtk_dialog_run: assertion
'GTK_IS_DIALOG (dialog)' failed

(kdeconnect-send:4559): GLib-GObject-WARNING **: invalid (NULL) pointer
instance

(kdeconnect-send:4559): GLib-GObject-CRITICAL **: g_signal_connect_data:
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(kdeconnect-send:4559): Gtk-CRITICAL **: gtk_widget_show_all: assertion
'GTK_IS_WIDGET (widget)' failed


Thanks

Reproducible: Always

Steps to Reproduce:
1. run command kdeconnect-send on Ubuntu 14.04.
2.
3.

Actual Results:  
kdeconnect-send

(kdeconnect-send:4559): GLib-GIO-CRITICAL **: g_file_new_for_commandline_arg:
assertion 'arg != NULL' failed

(kdeconnect-send:4559): GLib-GIO-CRITICAL **: g_file_get_path: assertion
'G_IS_FILE (file)' failed
** Message: Contractor.vala:102:
GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path
'/modules/kdeconnect'

(kdeconnect-send:4559): GLib-GIO-CRITICAL **: g_file_get_basename: assertion
'G_IS_FILE (file)' failed

** (kdeconnect-send:4559): CRITICAL **:
kde_connect_indicator_device_dialog_construct: assertion 'filename != NULL'
failed

(kdeconnect-send:4559): GLib-GObject-CRITICAL **: g_object_ref_sink: assertion
'G_IS_OBJECT (object)' failed

** (kdeconnect-send:4559): CRITICAL **:
kde_connect_indicator_device_dialog_set_list: assertion 'self != NULL' failed

(kdeconnect-send:4559): Gtk-CRITICAL **: gtk_dialog_run: assertion
'GTK_IS_DIALOG (dialog)' failed

(kdeconnect-send:4559): GLib-GObject-WARNING **: invalid (NULL) pointer
instance

(kdeconnect-send:4559): GLib-GObject-CRITICAL **: g_signal_connect_data:
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(kdeconnect-send:4559): Gtk-CRITICAL **: gtk_widget_show_all: assertion
'GTK_IS_WIDGET (widget)' failed


Expected Results:  
It works.

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

[muon] [Bug 358359] HIgh cpu consumption and apt-check process infinte fork

[Ivan Adzhubey via KDE Bugzilla]

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

Ivan Adzhubey  changed:

   What|Removed |Added

 CC||iadzhu...@verizon.net

--- Comment #14 from Ivan Adzhubey  ---
Not sure whether the above mentioned fix has been committed yet or not but
today's update-notifier-common update to version 3.163.1 which arrived via
Kubuntu PPA did not fix the problem for me on my Kubuntu 15.10 system with
Plasma 5.5.3: apt-get update command still spawns hundreds of rough apt-check
processes which eat up all memory and CPU on my desktop.

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

[kde] [Bug 359562] KDE Crashes when remotely logging in

[via KDE Bugzilla]

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

hkobetit...@medstrat.com changed:

   What|Removed |Added

 CC||hkobetit...@medstrat.com

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

[kde] [Bug 359562] New: KDE Crashes when remotely logging in

[via KDE Bugzilla]

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

Bug ID: 359562
   Summary: KDE Crashes when remotely logging in
   Product: kde
   Version: 4.14.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: hkobetit...@medstrat.com

KDE Crashes when remotely logging in from Remote Desktop.

Reproducible: Always

Steps to Reproduce:
1.Create a PPTP connection to Kubuntu system
2.Run Remote Desktop 
3.Log in remotely to Kubuntu system

Actual Results:  
Application: KDE Daemon (kded4), signal: Segmentation fault


Expected Results:  
Nothing

Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".Application: KDE Daemon (kded4),
signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7fc57a1a56c2 in ?? () from
/usr/lib/kde4/plugins/kscreen/KSC_XRandR11.so
#7  0x7fc57a5d9ba9 in KScreen::Config::current() () from
/usr/lib/libkscreen.so.1
#8  0x7fc57a7f77b5 in KScreenDaemon::monitorConnectedChange() () from
/usr/lib/kde4/kded_kscreen.so
#9  0x7fc57a7f7e5f in KScreenDaemon::KScreenDaemon(QObject*,
QList const&) () from /usr/lib/kde4/kded_kscreen.so
#10 0x7fc57a7f8968 in ?? () from /usr/lib/kde4/kded_kscreen.so
#11 0x7fc597c06433 in KPluginFactory::create (this=0x1de9390,
iface=0x7fc597c5b500  "KDEDModule",
parentWidget=0x0, parent=0x1c59110, args=..., keyword=...) at
../../kdecore/util/kpluginfactory.cpp:203
#12 0x7fc580658d3a in create (args=..., parent=0x1c59110,
this=) at ../../kdecore/util/kpluginfactory.h:507
#13 Kded::loadModule (this=this@entry=0x1c59110, s=...,
onDemand=onDemand@entry=false) at ../../kded/kded.cpp:409
#14 0x7fc580659561 in Kded::initModules (this=0x1c59110) at
../../kded/kded.cpp:268
#15 0x7fc580659d18 in Kded::recreateDone (this=this@entry=0x1c59110) at
../../kded/kded.cpp:580
#16 0x7fc580659d83 in Kded::recreate (this=0x1c59110, initial=) at ../../kded/kded.cpp:547
#17 0x7fc58065c25d in KDEDApplication::newInstance (this=)
at ../../kded/kded.cpp:833
#18 0x7fc598430f6a in KUniqueApplicationAdaptor::newInstance
(this=0x1d460b0, asn_id=..., args=...) at
../../kdeui/kernel/kuniqueapplication.cpp:442
#19 0x7fc598430fe5 in KUniqueApplicationAdaptor::qt_static_metacall
(_o=_o@entry=0x1d460b0, _id=_id@entry=0, _a=_a@entry=0x7fff86f18990,
_c=QMetaObject::InvokeMetaMethod) at ./kuniqueapplication_p.moc:57
#20 0x7fc598431203 in qt_static_metacall (_a=0x7fff86f18990, _id=0,
_c=QMetaObject::InvokeMetaMethod, _o=0x1d460b0) at
./kuniqueapplication_p.moc:100
#21 KUniqueApplicationAdaptor::qt_metacall (this=0x1d460b0,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff86f18990) at
./kuniqueapplication_p.moc:101
#22 0x7fc5949f41f6 in QDBusConnectionPrivate::deliverCall
(this=this@entry=0x1c47690, object=object@entry=0x1d460b0, msg=...,
metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951
#23 0x7fc5949f52f9 in QDBusConnectionPrivate::activateCall
(this=this@entry=0x1c47690, object=0x1d460b0, flags=flags@entry=337, msg=...)
at qdbusintegrator.cpp:856
#24 0x7fc5949f5ddd in QDBusConnectionPrivate::activateObject
(this=0x1c47690, node=..., msg=..., pathStartPos=) at
qdbusintegrator.cpp:1427
#25 0x7fc5949f5eab in QDBusActivateObjectEvent::placeMetaCall
(this=0x1d30680) at qdbusintegrator.cpp:1541
#26 0x7fc5976b5c1e in QObject::event (this=this@entry=0x7fff86f193d0,
e=e@entry=0x1d30680) at kernel/qobject.cpp:1194
#27 0x7fc5976a1cfc in QCoreApplication::event
(this=this@entry=0x7fff86f193d0, e=e@entry=0x1d30680) at
kernel/qcoreapplication.cpp:1765
#28 0x7fc596a36ed3 in QApplication::event (this=0x7fff86f193d0,
e=0x1d30680) at kernel/qapplication.cpp:2549
#29 0x7fc596a31e2c in QApplicationPrivate::notify_helper
(this=this@entry=0x1c5d3e0, receiver=receiver@entry=0x7fff86f193d0,
e=e@entry=0x1d30680) at kernel/qapplication.cpp:4567
#30 0x7fc596a384a0 in QApplication::notify (this=this@entry=0x7fff86f193d0,
receiver=receiver@entry=0x7fff86f193d0, e=e@entry=0x1d30680) at
kernel/qapplication.cpp:4353
#31 0x7fc598429d1a in KApplication::notify (this=0x7fff86f193d0,
receiver=0x7fff86f193d0, event=0x1d30680) at
../../kdeui/kernel/kapplication.cpp:311
#32 0x7fc59769d4dd in QCoreApplication::notifyInternal
(this=0x7fff86f193d0, receiver=receiver@entry=0x7fff86f193d0,
event=event@entry=0x1d30680) at kernel/qcoreapplication.cpp:953
#33 0x7fc5976a0b3d in sendEvent (event=0x1d30680, receiver=0x7fff86f193d0)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#34 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x1a0d150) at
kernel/qcoreapplication.cpp:1577
#35 0x7fc5976a0fe3 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, 

[krita] [Bug 359561] Tablet bindings bugged between 2.9.x and 3.0pa2

[Kurin via KDE Bugzilla]

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

--- Comment #2 from Kurin  ---
Created attachment 97291
  --> https://bugs.kde.org/attachment.cgi?id=97291=edit
Krita 3.0pa2 log of tablet events.

Krita version 3.0pa2 events which should be nearly the same, input-wise, as
2.9.

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

[krita] [Bug 359561] Tablet bindings bugged between 2.9.x and 3.0pa2

[Kurin via KDE Bugzilla]

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

--- Comment #1 from Kurin  ---
Created attachment 97290
  --> https://bugs.kde.org/attachment.cgi?id=97290=edit
Krita 2.9.x log of tablet events.

log of events from 'regular use' from version 2.9.x

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

[krita] [Bug 359561] New: Tablet bindings bugged between 2.9.x and 3.0pa2

[Kurin via KDE Bugzilla]

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

Bug ID: 359561
   Summary: Tablet bindings bugged between 2.9.x and 3.0pa2
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: marupa.as...@gmail.com

Krita 2.9.x (stable 2.9.10) allows you to use lower barrel (middle mouse
button) on its own to pan, and shift+lower barrel to rotate the canvas.

Krita 3.0 pre-alpha 2, despite having identical bindings fails to do this
regularly.


Either action may be accomplished only if you are re-focusing the window after
alt-tabbing.  For example, if you alt-tab away from Krita, then hover over the
Krita window with the tablet, and hold down lower barrel, it will allow you to
pan.  The same while holding shift will allow you to rotate.  Upon an attempt
at second invocation, or while Krita is the current window, it simply invokes
the color dropper and refuses to do anything else even with shift, ctrl, alt,
or even space held down.

Using Windows 10 64bit on AMD processor, nVidia GPU, Cintiq 13HD DTK-1300 and
Krita 2.9.10 installed alongside 3.0pa2.

Wacom Control Panel version 6.3.15-2, Driver version 6.3.15-2.  Pro Pen
settings have been changed from default so that upper barrel is right-click,
lower barrel is middle-click.

Reproducible: Always

Steps to Reproduce:
0.  Set Wacom Control Panel settings as above.
1.  Open Krita 2.9.x, use middle mouse button to manipulate canvas twice. 
Works as expected.
2.  Open Krita 3.0pa2, use middle mouse button to manipulate canvas.  First
time works, second time does not.
3.  Alt-tab away from Krita (to anything else).
4.  Hover over Krita 3.0 window and use middle-mouse button to manipulate
canvas twice.
5.  First time works as expected (Window becomes active, canvas is manipulated.
 Second time only invokes color dropper.



Workaround is to just alt-tab every time you want to manipulate the canvas, but
that's kind of not all that much of a workaround.

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

[kdenlive] [Bug 359541] Color grading tools mismatching colors in monitors

[via KDE Bugzilla]

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

bryanwors...@hotmail.com changed:

   What|Removed |Added

 CC||bryanwors...@hotmail.com

--- Comment #2 from bryanwors...@hotmail.com ---
Me also, with KDenLive 15.12.0 on Kubuntu 15.10 (AMD 64), as discussed here
with further screen-shot examples:
https://forum.kde.org/viewtopic.php?f=270=131116#p351828

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

[systemsettings] [Bug 301622] Mouse pointer gets huge if a second large screen is connected

[Maxime Deraspe via KDE Bugzilla]

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

Maxime Deraspe  changed:

   What|Removed |Added

 CC||maximilien...@gmail.com

--- Comment #26 from Maxime Deraspe  ---
bump !

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

[Spectacle] [Bug 359560] New: Spectacle's "cross-hair" cursor is quite hard (impossible) to see

[Jeff Bai via KDE Bugzilla]

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

Bug ID: 359560
   Summary: Spectacle's "cross-hair" cursor is quite hard
(impossible) to see
   Product: Spectacle
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: jeffbaich...@gmail.com

When trying to create a screenshot with Spectacle with the "rectangular area"
mode, the cursor to create a rectangular area - or a "cross hair" - is nearly
impossible to see the cursor, and the dimmed background certainly wouldn't help
either.

This can create issue when trying to create a screenshot, and this is probably
an a11y issue as well.

Reproducible: Always

Steps to Reproduce:
1. Open spectacle.
2. Choose "rectangular area" mode.
3. "New screenshot".

Actual Results:  
The "cross hair" cursor is not quite visible.

Expected Results:  
The "cross hair" should be clear to see.

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

[krita] [Bug 359559] New: Move tool can't move selected layers

[via KDE Bugzilla]

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

Bug ID: 359559
   Summary: Move tool can't move selected layers
   Product: krita
   Version: 2.9.11
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: katearche...@yandex.ru

If I choose a couple of layers and use move tool with "move current layer"
option the tool moves only one of the layers, the layer that was selected last.

What's even more confusing, if the option "move the whole group" is selected,
layers(under the cursor) can be moved that way regardless the fact what layers
was chosen.


Reproducible: Always

Steps to Reproduce:
1.Create two layers
2. Select both of them
3. Try to use move tool

Actual Results:  
Only one of the layers moves

Expected Results:  
If several layers are chosen, move tool will move all of the layers that was
selected, not the last selected only.

I suppose the behaviour of the tool should be altered to be able to move
selected layers by default or at least add another option to the tool to move
selected layers, not just layers that are situated under the cursor.

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

[calligracommon] [Bug 359511] Changing line spacing removes text formatting.

[Camilla Boemann via KDE Bugzilla]

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

--- Comment #1 from Camilla Boemann  ---
The ParagraphFormattingCommand despite using the new visitor gets it wrong.
Will have to investigate the cause more thoroughly

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

[calligracommon] [Bug 359511] Changing line spacing removes text formatting.

[Camilla Boemann via KDE Bugzilla]

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

Camilla Boemann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Product|calligrawords   |calligracommon
  Component|usability   |text-tool
 Status|UNCONFIRMED |CONFIRMED
 OS|Linux   |All
Version|2.9.11  |3.0 Alpha
 CC||c...@boemann.dk
   Platform|Kubuntu Packages|unspecified

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

[kdenlive] [Bug 359541] Color grading tools mismatching colors in monitors

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
i reproduce this.

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

[parley] [Bug 356239] Only system languages can be selected as collection languages

[via KDE Bugzilla]

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

s...@friedrichs.be changed:

   What|Removed |Added

 CC||s...@friedrichs.be

--- Comment #2 from s...@friedrichs.be ---
Hello Dimitris,
I'm happy that you fixed it. Do you know, when the fix will be uploaded in
https://github.com/KDE/parley/ ?
CU Sven

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

[rkward] [Bug 359404] Problem viewing graphic output in Windows

[Leszek Pawlowicz via KDE Bugzilla]

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

--- Comment #4 from Leszek Pawlowicz  ---
Sorry for the delay - out of town on work. Ran the script, create a plot, and
it showed up correctly in the output window.

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

[kdevelop] [Bug 359496] KDev hang with too many threads

[Milian Wolff via KDE Bugzilla]

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

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Milian Wolff  ---
pasting important part inline: 
Thread 33 (Thread 0x7f4027429700 (LWP 28197)):
#0  0x0030008df3ad in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00300300a2a2 in poll (__timeout=-1, __nfds=1, __fds=0x7f4027428d50)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0xfe86e0, cond=cond@entry=0xfe8720,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x00300300be2f in xcb_wait_for_event (c=0xfe86e0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7f40278c7539 in QXcbEventReader::run (this=0xff2db0) at
qxcbconnection.cpp:1229
#5  0x00300869ea73 in QThreadPrivate::start (arg=0xff2db0) at
thread/qthread_unix.cpp:331
#6  0x003000c07324 in start_thread (arg=0x7f4027429700) at
pthread_create.c:333
#7  0x0030008e81cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 32 (Thread 0x7f401eefe700 (LWP 28199)):
#0  0x0030008b833d in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x00300873974d in qt_nanosleep (amount=...) at
tools/qelapsedtimer_unix.cpp:185
#2  0x00300869dfe4 in QThread::usleep (usecs=usecs@entry=500) at
thread/qthread_unix.cpp:475
#3  0x7f4027d75cde in KDevelop::DUChainLock::lockForWrite(unsigned int)
(this=0x7f40282a58a0 , timeout=0)
at
/home/pedro.ferreira/src/kdev/kdevplatform/language/duchain/duchainlock.cpp:155
#4  0x7f4027d75dcc in KDevelop::DUChainWriteLocker::lock()
(this=0x7f401eefdda0) at
/home/pedro.ferreira/src/kdev/kdevplatform/language/duchain/duchainlock.cpp:249
#5  0x7f4027d3254c in KDevelop::DUChainPrivate::doMoreCleanup(int, bool)
(this=0x7f40282a5880 ,
retries=retries@entry=1, 
needLockRepository=needLockRepository@entry=true) at
/home/pedro.ferreira/src/kdev/kdevplatform/language/duchain/duchain.cpp:699
#6  0x7f4027d352c1 in KDevelop::DUChainPrivate::CleanupThread::run()
(this=0x414d460) at
/home/pedro.ferreira/src/kdev/kdevplatform/language/duchain/duchain.cpp:289
#7  0x00300869ea73 in QThreadPrivate::start (arg=0x414d460) at
thread/qthread_unix.cpp:331
#8  0x003000c07324 in start_thread (arg=0x7f401eefe700) at
pthread_create.c:333
#9  0x0030008e81cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

... way too many threadweaver threads waiting for jobs to be assigned

Thread 14 (Thread 0x7f3fc194f700 (LWP 28221)):
#0  0x0030008df3ad in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x003002048f34 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f3fbc0031b0, timeout=-1, context=0x7f3fbc000990) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7f3fbc000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3803
#3  0x00300204903c in g_main_context_iteration (context=0x7f3fbc000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869
#4  0x003004a7 in QEventDispatcherGlib::processEvents
(this=0x7f3fbc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#5  0x00300883c69a in QEventLoop::exec (this=this@entry=0x7f3fc194ed90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x00300869a20c in QThread::exec (this=this@entry=0x4673200) at
thread/qthread.cpp:503
#7  0x7f4027df10f6 in run (this=0x4673200) at
/home/pedro.ferreira/src/kdev/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#8  0x00300869ea73 in QThreadPrivate::start (arg=0x4673200) at
thread/qthread_unix.cpp:331
#9  0x003000c07324 in start_thread (arg=0x7f3fc194f700) at
pthread_create.c:333
#10 0x0030008e81cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f3fc08ed700 (LWP 28292)):
#0  0x0030008df3ad in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x003002048f34 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f3fb4002e70, timeout=-1, context=0x7f3fb4000990) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7f3fb4000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3803
#3  0x00300204903c in g_main_context_iteration 

[frameworks-kio] [Bug 353195] Copy error for folders with mixed files & folders in Split View

[Robert Spillner via KDE Bugzilla]

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

Robert Spillner  changed:

   What|Removed |Added

 CC||robert.spill...@gmx.de

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

[plasmashell] [Bug 359558] System tray creating ghost entries

[hector acosta via KDE Bugzilla]

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

--- Comment #1 from hector acosta  ---
url is screenshot of the problem

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

[plasmashell] [Bug 359558] New: System tray creating ghost entries

[hector acosta via KDE Bugzilla]

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

Bug ID: 359558
   Summary: System tray creating ghost entries
   Product: plasmashell
   Version: master
  Platform: Other
   URL: http://i.imgur.com/nQLJWfE.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: hector.aco...@gmail.com

My system tray will create spurious entries. Setting those entries to hidden
will remove the whitespace.

Reproducible: Always

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

[plasmashell] [Bug 358211] Plasma crash when re-activating screen

[Stephan Diestelhorst via KDE Bugzilla]

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Stephan Diestelhorst via KDE Bugzilla]

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[kde] [Bug 359557] New: Plasma crashes when manually starting KMix

[Alexis Kauffmann via KDE Bugzilla]

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

Bug ID: 359557
   Summary: Plasma crashes when manually starting KMix
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: l...@gehspace.com

Application: plasma-desktop (4.11.13)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.3.0-0.bpo.1-amd64 x86_64
Distribution: Debian GNU/Linux 8.3 (jessie)

-- Information about the crash:
- What I was doing when the application crashed: It's been a few days that KMix
is not loading on system tray at startup. When I start it manually, the Plasma
desktop crashes.

-- Backtrace:
Application: Shell da área de trabalho do 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 0x7fcade06b800 (LWP 2736))]

Thread 11 (Thread 0x7fcaabde3700 (LWP 2739)):
#0  0x7fcadd95cd3d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fcad0973ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcad0973ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcada41ed37 in QEventDispatcherGlib::processEvents
(this=0x7fcaa40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fcada3ee271 in QEventLoop::processEvents
(this=this@entry=0x7fcaabde2d80, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fcada3ee5d5 in QEventLoop::exec (this=this@entry=0x7fcaabde2d80,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fcada2e2e99 in QThread::exec (this=this@entry=0xad66c0) at
thread/qthread.cpp:538
#7  0x7fcada3ceac3 in QInotifyFileSystemWatcherEngine::run (this=0xad66c0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fcada2e570f in QThreadPrivate::start (arg=0xad66c0) at
thread/qthread_unix.cpp:349
#9  0x7fcad12970a4 in start_thread (arg=0x7fcaabde3700) at
pthread_create.c:309
#10 0x7fcadd96587d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7fcaa89dc700 (LWP 2749)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcad6a69dea in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7fcad6a69e19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7fcad12970a4 in start_thread (arg=0x7fcaa89dc700) at
pthread_create.c:309
#4  0x7fcadd96587d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7fcaaa3da700 (LWP 3923)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcada2e5c66 in wait (time=18446744073709551615, this=0x118a250) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1156e28, mutex=0x113c540,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7fcad5cc986c in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1156e00,
th=0x2a38bb0) at ../../../threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7fcad5ccc743 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x11599e0, th=0x2a38bb0, previous=0x179adc0) at
../../../threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7fcad5ccb22f in ThreadWeaver::Thread::run (this=0x2a38bb0) at
../../../threadweaver/Weaver/Thread.cpp:98
#6  0x7fcada2e570f in QThreadPrivate::start (arg=0x2a38bb0) at
thread/qthread_unix.cpp:349
#7  0x7fcad12970a4 in start_thread (arg=0x7fcaaa3da700) at
pthread_create.c:309
#8  0x7fcadd96587d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 8 (Thread 0x7fcaa93d8700 (LWP 3924)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcada2e5c66 in wait (time=18446744073709551615, this=0x118a250) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1156e28, mutex=0x113c540,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7fcad5cc986c in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1156e00,
th=0x3a04d40) at ../../../threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7fcad5ccc743 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x11599e0, th=0x3a04d40, previous=0x3a58140) at
../../../threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7fcad5ccb22f in ThreadWeaver::Thread::run (this=0x3a04d40) at
../../../threadweaver/Weaver/Thread.cpp:98
#6  0x7fcada2e570f in QThreadPrivate::start (arg=0x3a04d40) at
thread/qthread_unix.cpp:349
#7  0x7fcad12970a4 in start_thread (arg=0x7fcaa93d8700) at
pthread_create.c:309
#8  0x7fcadd96587d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

[valgrind] [Bug 359133] m_deduppoolalloc.c:258 (vgPlain_allocEltDedupPA): Assertion 'eltSzB <= ddpa->poolSzB' failed.

[Philippe Waroquiers via KDE Bugzilla]

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

--- Comment #8 from Philippe Waroquiers  ---
(In reply to David Hallas from comment #7)
> I have attached a reduced test case that shows the problem. I have tested
> with gcc-4.9.3 and clang-3.7.1 using a 64bit Linux PC. I compiled it like
> this:
> 
> g++ -std=c++11 main.cpp -o test
> 
> I also verified that the latest master fixes the problem.
> 
> Let me know if there is anything else you need

Thanks for the test case.
Test added in revision 15799

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

[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.

[David Jarvie via KDE Bugzilla]

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

--- Comment #3 from David Jarvie  ---
I tried out an email alarm with the email address configured in the same way as
yours in the settings, but it was sent successfully.

Could you please set up an email alarm and then attach your KAlarm
configuration file (in ~/.kde/share/config/kalarmrc or ~/.config/kalarmrc or
some similar directory), and also your calendar file (to find out its location,
select menu View -> Show Calendars, and then right click on the active alarm
calendar and select Show Details - the location is labelled "File:"). If you
want to hide personal information in the calendar file, just replace it with
other text before attaching the file.

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

[plasmashell] [Bug 358894] File tooltips cover context menu

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
  Latest Commit|https://quickgit.kde.org/?p |http://commits.kde.org/plas
   |=plasma-desktop.git=commi |ma-framework/eccf7cf0b22c17
   |t=017a1c426baf27c8a7e028f |0c0f642c3ae376a3e3ff600b91
   |ac9df142aeaf9fa6b   |
 Resolution|--- |FIXED

--- Comment #7 from Kai Uwe Broulik  ---
Git commit eccf7cf0b22c170c0f642c3ae376a3e3ff600b91 by Kai Uwe Broulik.
Committed on 18/02/2016 at 20:58.
Pushed by broulik into branch 'master'.

[ToolTip] Stop show timer if hideTooltip is called

This prevents the tooltip from showing up if hideTooltip was called
before it was shown.

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

M  +1-0src/declarativeimports/core/tooltip.cpp

http://commits.kde.org/plasma-framework/eccf7cf0b22c170c0f642c3ae376a3e3ff600b91

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

[okular] [Bug 359555] New: Scalable Vector Graphics (SVG) support

[Thomas Fischer via KDE Bugzilla]

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

Bug ID: 359555
   Summary: Scalable Vector Graphics (SVG) support
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: New backend wishes
  Assignee: okular-de...@kde.org
  Reporter: fisc...@unix-ag.uni-kl.de

Back in the KDE4 days, there was a SVG rendering KPart that allowed viewing SVG
files (Scalable Vector Graphics) from within Konqueror. Said SVG KPart seems to
be dead now, the latest code commit is from 2011.
My proposal is to scrap whatever code is useful (it relies most likely on Qt's
QSvgRenderer class) and build a backend for Okular. I would even assume that
parts of the PDF renderer can be re-used, as a SVG graphics (apart from
animations that I personally see as non-essential) is in many aspects like a
single-page PDF file.

Reproducible: Always

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

[Spectacle] [Bug 359554] New: Wrong screen region captured when capturing a window on i3

[via KDE Bugzilla]

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

Bug ID: 359554
   Summary: Wrong screen region captured when capturing a window
on i3
   Product: Spectacle
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: nicolas...@live.fr

I'm using spectacle with the i3 window manager, and in some circumstances the
region captured is incorrect. It's possible that this problem stems from i3 not
setting properly the window properties. However I don't remember having this
issue with KSnapshot, and other snapshot tools with similar functionalities
produce the expected result.

Reproducible: Always

Steps to Reproduce:
1. Use i3wm
2. Set a window floating (away from the top left corner of the screen), or in
an vertical split, not on the left hand side of the screen.
3. Start spectacle and select windows under cursor
4. Take a screenshot of the floating window or a window on the right hand side
of a vertical split.

Actual Results:  
Spectacles captures a region that appears to be of the right size, but instead
of it being the window clicked on, it is a region starting on the top left
corner of the screen.

Expected Results:  
Actually take a screenshot of the window that was clicked on.

A few examples demonstrating the issue:

First setup, trying to capture a dialog window:
- Desktop: https://i.imgur.com/oRYaX5o.png
- Screenshot obtained by clicking on the dialog window:
https://i.imgur.com/1d1abEu.png

Second setup, trying to capture a window on a right hand side of a vertical
split:
- Desktop: https://i.imgur.com/vtr02W6.png
- Screenshot obtained by clicking on the terminal on the right:
https://i.imgur.com/UtKrnb0.png

Third setup, slightly more complicated splits:
- Desktop: https://i.imgur.com/7TkhPdB.png
- Screenshot obtained by clicking on the terminal on the bottom right:
https://i.imgur.com/kCK8fjO.png

In this third case, clicking on the two other windows produces the expected
result.

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

[kmail2] [Bug 359553] New: Lauching kmail5 crash

[Bruno Friedmann via KDE Bugzilla]

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

Bug ID: 359553
   Summary: Lauching kmail5 crash
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: br...@ioda-net.ch

Application: kmail (5.1.1)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-rc4-2.gea92baf-default x86_64
Distribution: "openSUSE Tumbleweed (20160212) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Launch kmail by hotkey,
krunner, or menu the first time the desktop is opened this crash dialog box
appear a few secondes before the main windows start.
After the main windows start, kmail seems to work correctly.

The crash can be reproduced every time.

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

Thread 16 (Thread 0x7f3d82820700 (LWP 3883)):
#0  0x7f3da559c24d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3d9852b432 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f3d8281fb80) at /usr/include/bits/poll2.h:46
#2  0x7f3d9852b432 in _xcb_conn_wait (c=c@entry=0xd26570,
cond=cond@entry=0xd265b0, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x7f3d9852d007 in xcb_wait_for_event (c=0xd26570) at xcb_in.c:693
#4  0x7f3d84b79e29 in QXcbEventReader::run() (this=0xd33790) at
qxcbconnection.cpp:1229
#5  0x7f3da5ea394f in QThreadPrivate::start(void*) (arg=0xd33790) at
thread/qthread_unix.cpp:331
#6  0x7f3d9b9344a4 in start_thread (arg=0x7f3d82820700) at
pthread_create.c:334
#7  0x7f3da55a4bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f3d7bfff700 (LWP 3900)):
#0  0x7f3d9b45a554 in g_mutex_unlock (mutex=0x7f3d740009b0) at
gthread-posix.c:1350
#1  0x7f3d9b416e6a in g_main_context_dispatch
(context=context@entry=0x7f3d740009b0) at gmain.c:3772
#2  0x7f3d9b4172f8 in g_main_context_iterate
(context=context@entry=0x7f3d740009b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3840
#3  0x7f3d9b41739c in g_main_context_iteration (context=0x7f3d740009b0,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f3da60c852b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3d740008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f3da607263a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3d7bffec90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f3da5e9eb1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f3da5ea394f in QThreadPrivate::start(void*) (arg=0xeccc80) at
thread/qthread_unix.cpp:331
#8  0x7f3d9b9344a4 in start_thread (arg=0x7f3d7bfff700) at
pthread_create.c:334
#9  0x7f3da55a4bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f3d79994700 (LWP 6142)):
#0  0x7f3da559c24d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3d9b417294 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f3d68002e70, timeout=, context=0x7f3d68002cd0) at
gmain.c:4135
#2  0x7f3d9b417294 in g_main_context_iterate
(context=context@entry=0x7f3d68002cd0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f3d9b41739c in g_main_context_iteration (context=0x7f3d68002cd0,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f3da60c852b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3d68002c00, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f3da607263a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3d79993c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f3da5e9eb1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f3da5ea394f in QThreadPrivate::start(void*) (arg=0xef59a0) at
thread/qthread_unix.cpp:331
#8  0x7f3d9b9344a4 in start_thread (arg=0x7f3d79994700) at
pthread_create.c:334
#9  0x7f3da55a4bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f3d7a3ad700 (LWP 6144)):
#0  0x7f3da559c24d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3d9b417294 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f3d64003040, timeout=, context=0x7f3d64002ef0) at
gmain.c:4135
#2  0x7f3d9b417294 in g_main_context_iterate
(context=context@entry=0x7f3d64002ef0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f3d9b41739c in g_main_context_iteration (context=0x7f3d64002ef0,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f3da60c852b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3d64002e20, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  

[kipiplugins] [Bug 359478] kipi flickr export plugin crashed on creating new set

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
  Latest Commit||http://commits.kde.org/kipi
   ||-plugins/d45acc3babcb756fba
   ||b72f5d142e03f34adf5565
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Maik Qualmann  ---
Git commit d45acc3babcb756fbab72f5d142e03f34adf5565 by Maik Qualmann.
Committed on 18/02/2016 at 20:44.
Pushed by mqualmann into branch 'master'.

fix possible crash in flickr tool if photo sets list has not been created
FIXED-IN: 5.0.0

M  +2-1NEWS
M  +2-1flickr/flickrtalker.cpp
M  +5-1flickr/flickrwindow.cpp

http://commits.kde.org/kipi-plugins/d45acc3babcb756fbab72f5d142e03f34adf5565

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

[kdevelop] [Bug 359552] implement Class::function fails to show when inside namespace

[Radu Benea via KDE Bugzilla]

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

--- Comment #1 from Radu Benea  ---
Created attachment 97289
  --> https://bugs.kde.org/attachment.cgi?id=97289=edit
testcase for this bugreport

a ultra-minimalistic testcase showing all observed behaviours

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

[kdevelop] [Bug 359552] New: implement Class::function fails to show when inside namespace

[Radu Benea via KDE Bugzilla]

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

Bug ID: 359552
   Summary: implement Class::function fails to show when inside
namespace
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kitanat...@gmail.com

The problem is only reproducible if the same namespace and a different class is
defined in an include from the first included file from the cpp

I will attach a testcase proving exactly what the issue is and all known
workarounds from me.

Reproducible: Always

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

[kmymoney4] [Bug 342401] allow different payees on splits

[Jack via KDE Bugzilla]

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

--- Comment #8 from Jack  ---
Interestingly I just ran into this - I had made a deposit earlier in the year,
including checks I received from three different sources.  I had a great deal
of trouble finding that transaction, since searching by payee obviously didn't
work, since the three payees were not mentioned in the transaction.  I only
found it by a text search.
I don't know what proper bookkeeping would require here, but I think the real
user need is just simplicity in data entry, and having a single split for the
bank deposit side, so it matches the bank statement.

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

[kdelibs] [Bug 359551] New: knotify crashed with segmentations fault

[Helmuth via KDE Bugzilla]

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

Bug ID: 359551
   Summary: knotify crashed with segmentations fault
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: knotify
  Assignee: ogoff...@kde.org
  Reporter: helmuth.egg...@t-online.de

Application: knotify4 (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-32-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

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

Entering  triggered the beginning-of-line notification(sound) which in
turn triggered notify, which crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: KNotify (knotify4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc7957a2800 (LWP 3565))]

Thread 2 (Thread 0x7fc7823a3700 (LWP 3566)):
#0  0x7fc79002e8e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc78ffec299 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc78ffecb03 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc78ffeccec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc7931050de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7fc7930d6e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fc7930d7165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7fc792fd40bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7fc7930b8783 in  () at /usr/lib64/libQtCore.so.4
#9  0x7fc792fd679f in  () at /usr/lib64/libQtCore.so.4
#10 0x7fc790a090a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fc79298b08d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc7957a2800 (LWP 3565)):
[KCrash Handler]
#5  0x7fc7929ca06c in __strcmp_ssse3 () at /lib64/libc.so.6
#6  0x7fc7732d0fee in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags, QMetaObject const*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fc7737d0f57 in  () at /usr/lib64/libQt5Gui.so.5
#8  0x7fc7956208ea in call_init.part () at /lib64/ld-linux-x86-64.so.2
#9  0x7fc7956209d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#10 0x7fc795624b08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#11 0x7fc7956207a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#12 0x7fc7956242fb in _dl_open () at /lib64/ld-linux-x86-64.so.2
#13 0x7fc78e16302b in dlopen_doit () at /lib64/libdl.so.2
#14 0x7fc7956207a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#15 0x7fc78e1635dd in _dlerror_run () at /lib64/libdl.so.2
#16 0x7fc78e1630c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#17 0x7fc7810a459f in  () at /usr/lib64/libvlccore.so.7
#18 0x7fc78108dd5d in  () at /usr/lib64/libvlccore.so.7
#19 0x7fc78108e057 in  () at /usr/lib64/libvlccore.so.7
#20 0x7fc78108e2c9 in  () at /usr/lib64/libvlccore.so.7
#21 0x7fc78108e534 in  () at /usr/lib64/libvlccore.so.7
#22 0x7fc78108ea87 in  () at /usr/lib64/libvlccore.so.7
#23 0x7fc78102649d in libvlc_InternalInit () at /usr/lib64/libvlccore.so.7
#24 0x7fc780df7623 in libvlc_new () at /usr/lib64/libvlc.so.5
#25 0x7fc781356ec9 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#26 0x7fc78133c728 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#27 0x7fc78133d1eb in qt_plugin_instance () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#28 0x7fc7930bc641 in QPluginLoader::instance() () at
/usr/lib64/libQtCore.so.4
#29 0x7fc781999f8b in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#30 0x7fc78199a773 in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#31 0x7fc794d77c76 in  () at /usr/lib64/libphonon.so.4
#32 0x7fc794d78317 in Phonon::Factory::backend(bool) () at
/usr/lib64/libphonon.so.4
#33 0x7fc794d788e3 in  () at /usr/lib64/libphonon.so.4
#34 0x7fc794d709b9 in  () at /usr/lib64/libphonon.so.4
#35 0x7fc794d6e896 in  () at /usr/lib64/libphonon.so.4
#36 0x0040e771 in _start ()

Reported using DrKonqi

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

[gwenview] [Bug 359550] New: SVG Masks not rendering

[Sorunome via KDE Bugzilla]

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

Bug ID: 359550
   Summary: SVG Masks not rendering
   Product: gwenview
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: m...@sorunome.de
CC: myr...@kde.org

When viewing SVG images which have masks said masks aren't been rendered,
resulting in pretty odd-looking images if the SVG has a mask.

Reproducible: Always

Steps to Reproduce:
1. open an SVG image which has a mask

Actual Results:  
The mask isn't rendered, resulting in the paths not being cropped

Expected Results:  
The paths should be cropped to the mask

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

[Spectacle] [Bug 358641] Have Spectacle remember filename

[Quiralta via KDE Bugzilla]

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

Quiralta  changed:

   What|Removed |Added

 CC||rjquira...@gmail.com

--- Comment #2 from Quiralta  ---
Yep, this features are really missed from Spectacle, for example as I paint in
Krita, I like to take snapshots of the process, with Ksnapshot, this was a
breeze, In spectacle, for every screenshot one must manually add the name, file
extension plus navigate to the desired folder. Its just not usable for my
purposes and predefine a folder on the settings is not intuitive, I would have
to change this every time a do a painting :D, I really hope this becomes a
future feature.

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

[kde] [Bug 359549] Crash when try to remove a file from the recycling bin

[Ovel Diaz Garcia via KDE Bugzilla]

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

Ovel Diaz Garcia  changed:

   What|Removed |Added

   Platform|unspecified |Mageia RPMs
Version|unspecified |4.14.1

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

[kde] [Bug 359549] New: Crash when try to remove a file from the recycling bin

[Ovel Diaz Garcia via KDE Bugzilla]

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

Bug ID: 359549
   Summary: Crash when try to remove a file from the recycling bin
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ovel2...@gmail.com

Application: plasma-desktop (4.11.16)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.15-desktop-2.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
There where 3 files in the recycling bin, It have an arrow in the top left
corner, if you click in it, it open a floating windows with the files inside
the recycling bin. I right-click one of them and select remove, and them, the
desktop crash and refresh after few seconds. The 3 files are still there.

-- Backtrace:
Application: Shell de escritorio Plasma (plasma-desktop), signal: Segmentation
fault
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x2ab4fad6cd40 (LWP 5111))]

Thread 3 (Thread 0x2ab5361e0700 (LWP 5114)):
#0  0x2ab4fc2e31fd in read () at /usr/lib64/libpthread.so.0
#1  0x2ab50045bbf0 in g_wakeup_acknowledge () at
/usr/lib64/libglib-2.0.so.0
#2  0x2ab50041999c in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x2ab500419e5b in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#4  0x2ab500419fbc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x2ab4fbf99e3e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x2ab4fbf6b931 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x2ab4fbf6bc45 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#8  0x2ab4fbe69899 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#9  0x2ab4fbf4d3d3 in QInotifyFileSystemWatcherEngine::run() () at
/usr/lib64/libQtCore.so.4
#10 0x2ab4fbe6bfff in QThreadPrivate::start(void*) () at
/usr/lib64/libQtCore.so.4
#11 0x2ab4fc2db5bd in start_thread () at /usr/lib64/libpthread.so.0
#12 0x2ab4fd5ab5cd in clone () at /usr/lib64/libc.so.6

Thread 2 (Thread 0x2ab536c0a700 (LWP 5116)):
#0  0x2ab4fc2e067f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib64/libpthread.so.0
#1  0x2ab50fde573a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtScript.so.4
#2  0x2ab50fde5769 in  () at /usr/lib64/libQtScript.so.4
#3  0x2ab4fc2db5bd in start_thread () at /usr/lib64/libpthread.so.0
#4  0x2ab4fd5ab5cd in clone () at /usr/lib64/libc.so.6

Thread 1 (Thread 0x2ab4fad6cd40 (LWP 5111)):
[KCrash Handler]
#5  0x2ab4fc6b0e00 in QActionPrivate::setShortcutEnabled(bool,
QShortcutMap&) () at /usr/lib64/libQtGui.so.4
#6  0x2ab4fc6b305d in QAction::setEnabled(bool) () at
/usr/lib64/libQtGui.so.4
#7  0x2ab5244bb3fc in PopupView::showContextMenu(QWidget*, QPoint const&,
QList const&) [clone .part.53] () at
/usr/lib64/kde4/plasma_applet_folderview.so
#8  0x2ab5244bb7f4 in PopupView::contextMenuRequest(QWidget*, QPoint
const&) () at /usr/lib64/kde4/plasma_applet_folderview.so
#9  0x2ab5244bb943 in PopupView::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.54] () at
/usr/lib64/kde4/plasma_applet_folderview.so
#10 0x2ab4fbf8088a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#11 0x2ab52449dba7 in AbstractItemView::contextMenuRequest(QWidget*, QPoint
const&) () at /usr/lib64/kde4/plasma_applet_folderview.so
#12 0x2ab5244a7529 in
IconView::contextMenuEvent(QGraphicsSceneContextMenuEvent*) () at
/usr/lib64/kde4/plasma_applet_folderview.so
#13 0x2ab4fcc63343 in QGraphicsItem::sceneEvent(QEvent*) () at
/usr/lib64/libQtGui.so.4
#14 0x2ab4fcc8a7db in
QGraphicsScene::contextMenuEvent(QGraphicsSceneContextMenuEvent*) () at
/usr/lib64/libQtGui.so.4
#15 0x2ab4fcca0ccc in QGraphicsScene::event(QEvent*) () at
/usr/lib64/libQtGui.so.4
#16 0x2ab4fc6b779c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#17 0x2ab4fc6bde40 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#18 0x2ab4fb19d25a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#19 0x2ab4fbf6ccad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#20 0x2ab4fccb8947 in QGraphicsView::contextMenuEvent(QContextMenuEvent*)
() at /usr/lib64/libQtGui.so.4
#21 0x2ab4fc707388 in QWidget::event(QEvent*) () at
/usr/lib64/libQtGui.so.4
#22 0x2ab4fcaab5ae in QFrame::event(QEvent*) () at /usr/lib64/libQtGui.so.4
#23 0x2ab4fccb83f1 in QGraphicsView::viewportEvent(QEvent*) () at
/usr/lib64/libQtGui.so.4
#24 0x2ab4fbf6ce16 in

[lokalize] [Bug 359548] New: Search on file reference

[Karl Ove Hufthammer via KDE Bugzilla]

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

Bug ID: 359548
   Summary: Search on file reference
   Product: lokalize
   Version: 2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: editor
  Assignee: sha...@ukr.net
  Reporter: k...@huftis.org

It’s currently possible to search/filter the list of strings by source, target,
comment, message context, but not ‘reference’, i.e. file reference. It’s
sometimes useful to filter on file reference, for example to translate all
strings from a certain (important file).

So this is a wish for support for searching on file references, i.e. lines
beginning with #: in the .po file.

Reproducible: Always

Steps to Reproduce:
1. Open a .po file which contains lines beginning #:
2. Set the ‘Search columns’ to ‘All’.
3. Try to search for a file name listed in a #: line

Actual Results:  
No results are listed.

Expected Results:  
Strings extracted from the file name should be listed.

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

[systemsettings] [Bug 359547] New: KDE System Settings Crash

[dildovsky via KDE Bugzilla]

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

Bug ID: 359547
   Summary: KDE System Settings Crash
   Product: systemsettings
   Version: 5.5.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: uzuno...@etna-alternance.net

Application: systemsettings5 (5.5.4)

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

-- Information about the crash:
- What I was doing when the application crashed:
Changing the desktop image
- Unusual behavior I noticed:
After login no desktop wallpaper, and other visuals missing

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f80aca93780 (LWP 2663))]

Thread 5 (Thread 0x7f809a50c700 (LWP 2664)):
#0  0x7f80a87e2bbd in poll () from /lib64/libc.so.6
#1  0x7f80a55bd422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f80a55bf00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f809c8613c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f80a8edb32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f80a4d470a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f80a87eafed in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f8087e46700 (LWP 2672)):
#0  0x7f80a87e2bbd in poll () from /lib64/libc.so.6
#1  0x7f80a482ae64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f80a482af7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f80a910dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f80a90b4d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f80a8ed661a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f80a745ddf8 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f80a8edb32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f80a4d470a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f80a87eafed in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f8076512700 (LWP 2674)):
#0  0x7f80a486cd14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f80a482ae0e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f80a482af7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f80a910dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f80a90b4d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f80a8ed661a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f80a745ddf8 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f80a8edb32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f80a4d470a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f80a87eafed in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f807e189700 (LWP 2775)):
#0  0x7f80a87dec8d in read () from /lib64/libc.so.6
#1  0x7f80a486bb60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f80a482a999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f80a482adf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f80a482b19a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#5  0x7f807e693426 in ?? () from /usr/lib64/libgio-2.0.so.0
#6  0x7f80a484ff65 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7f80a4d470a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f80a87eafed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f80aca93780 (LWP 2663)):
[KCrash Handler]
#6  0x7f80a90e9349 in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () from /usr/lib64/libQt5Core.so.5
#7  0x7f808aa8c485 in KParts::PartManager::~PartManager() () from
/usr/lib64/libKF5Parts.so.5
#8  0x7f808aa8c629 in KParts::PartManager::~PartManager() () from
/usr/lib64/libKF5Parts.so.5
#9  0x7f80a90e563c in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#10 0x7f80a90ef2cc in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#11 0x7f808b1cc4a6 in KHTMLPart::~KHTMLPart() () from
/usr/lib64/libKF5KHtml.so.5
#12 0x7f808b1cc659 in KHTMLPart::~KHTMLPart() () from
/usr/lib64/libKF5KHtml.so.5
#13 0x7f80a90e7b18 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#14 0x7f80aabd9e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#15 0x7f80aabdecc8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#16 0x7f80a90b6e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#17 0x7f80a90b9057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, 

[kdevelop] [Bug 359031] KDevelop Crashes while Clang is parsing

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
   |elop/c81aeaec8297361a7491c0 |elop/f68cf6e2c247ccc6f5b5d5
   |7a11b71e7c4a9d8ae8  |913104f37c3056a986
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Kevin Funk  ---
Git commit f68cf6e2c247ccc6f5b5d5913104f37c3056a986 by Kevin Funk, on behalf of
Milian Wolff.
Committed on 18/02/2016 at 19:09.
Pushed by kfunk into branch 'master'.

Revert "Workaround clang parsing problems when includes are missing"

This patch introduces crashes and also has multiple other style and
performance issues. Please resubmit from Phabricator or Reviewboard
so that we can peer review it properly.

CCMAIL: david.nolden@art-master.de

Really revert it. Merge via d9787a3 apparently dropped this commit.
CCMAIL: i...@milianw.de

This reverts commit 1dffa94f333098bca2830c9da96367156fc9b505.

(cherry picked from commit c81aeaec8297361a7491c07a11b71e7c4a9d8ae8)

M  +0-2languages/clang/clangparsejob.cpp
M  +1-70   languages/clang/duchain/parsesession.cpp
M  +0-9languages/clang/duchain/parsesession.h
M  +0-11   languages/clang/duchain/unsavedfile.cpp
M  +0-4languages/clang/duchain/unsavedfile.h

http://commits.kde.org/kdevelop/f68cf6e2c247ccc6f5b5d5913104f37c3056a986

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

[trojita] [Bug 359545] cannot access GMail: Too many commands before auth

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #1 from Thomas Lübking  ---
Can you please confirm you enabled this:
https://support.google.com/accounts/answer/6010255

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

[trojita] [Bug 359546] New: need to manage multiple accounts

[Kevin Coonan via KDE Bugzilla]

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

Bug ID: 359546
   Summary: need to manage multiple accounts
   Product: trojita
   Version: 0.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: IMAP
  Assignee: trojita-b...@kde.org
  Reporter: kevin.coo...@gmail.com

Why only one account?  Most people have many email accounts.

Reproducible: Always



Expected Results:  
Add as many IMAP accounts + their corresponding identity and SMTP settings as
needed.

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

[trojita] [Bug 359545] New: cannot access GMail: Too many commands before auth

[Kevin Coonan via KDE Bugzilla]

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

Bug ID: 359545
   Summary: cannot access GMail:  Too many commands before auth
   Product: trojita
   Version: 0.5
  Platform: openSUSE RPMs
   URL: imap.gmail.com
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: IMAP
  Assignee: trojita-b...@kde.org
  Reporter: kevin.coo...@gmail.com

When attempting to connect to GMail I receive an error:  "Too many commands
before auth [some string of alphanumerics]"and 9(!) popups saying "The server
sent the following ALERT:
Please log in via your web browser:
https://support.google.com/mail/accounts/answer/78754 (Failure)".
I am attempting to connect via "Network Connection" (which works, BTW, and I
have used many other IMAP clients to connect to GMail with these same settings.
 I can access via web browser and have been through GMail's trouble shooting)
to imap.gmail.com on 993 with "Forced encryption (TLS)".  My refresh interval
is increased to 15min to avoid any issues w/ too frequent connection attempts.  



NB:  Connection settings work fine w/ my ISP provided email services.

Reproducible: Always

Steps to Reproduce:
1.  Attempt to connect to GMail


Actual Results:  
My log shows:
12:35:30.837 Network Session Switched to network configuration IWantAPuppy
(WLAN, /org/freedesktop/NetworkManager/Settings/4)
12:35:30.837 Network Session Opening network session
12:35:30.837 Network Session Session is open (configuration[my home WiFi]),
online state:online
12:35:31.967 Imap::Mailbox::ListChildMailboxesTask Listing stuff below mailbox 
Failed: The connection is being killed for unspecified reason
12:35:31.967 Imap::Mailbox::GetAnyConnectionTask Failed: The connection is
being killed for unspecified reason


Expected Results:  
Reading my email

Using openSuSE 42.1 (same problem under KDE Plasma, LXQt and RazorQT).

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

[kontact] [Bug 359544] New: Kontact crash after selecting mail folder with unread mails

[rainer via KDE Bugzilla]

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

Bug ID: 359544
   Summary: Kontact crash after selecting mail folder with unread
mails
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@munin-soft.de

Application: kontact (5.1.1)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-3-default x86_64
Distribution: "openSUSE Tumbleweed (20160212) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I activated Kontact to check whether new mails arrived. On seeing the bold text
in the folder tree signaling the presence of unread messages i selected the
respective folder (POP3 inbox of one of my email accounts).
The view was updated accordingly, showing two (if I recall correctly) unread
messages in the list (I use the classic - non threaded view sorted by date
descending).
During moving the mous towards the list entries to select the first (I have a
reading pane below the list) Kontact crashed.

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

Thread 24 (Thread 0x7f2eae8fa700 (LWP 2632)):
#0  0x7f2ec9a2724d in poll () at /lib64/libc.so.6
#1  0x7f2ec319c432 in  () at /usr/lib64/libxcb.so.1
#2  0x7f2ec319e007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f2eb0a48e29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f2eca32e94f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f2ea75ef700 (LWP 2666)):
#0  0x7f2ec2d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2ec75c93bb in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f2ec75c93f9 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f2e628bb700 (LWP 2670)):
#0  0x7f2ec9a2724d in poll () at /lib64/libc.so.6
#1  0x7f2ec255d294 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f2ec255d39c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f2eca55352b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f2eca4fd63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2eca329b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f2eca32e94f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f2e55b05700 (LWP 2693)):
#0  0x7f2ec2d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2ec72d7764 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f2ec75f8441 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f2e55304700 (LWP 2694)):
#0  0x7f2ec2d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2ec72d8793 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f2ec75f8441 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f2e54b03700 (LWP 2695)):
#0  0x7f2ec2d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2ec72d8793 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f2ec75f8441 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f2e4700 (LWP 2696)):
#0  0x7f2ec2d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2ec72d8793 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f2ec75f8441 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f2e4f7fe700 (LWP 2697)):
#0  0x7f2ec2d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2ec72d8793 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f2ec75f8441 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f2ec2d784a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2ec9a2fbdd in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f2e4effd700 (LWP 2698)):
#0  0x7f2ec2d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () 

[akregator] [Bug 359543] when changing the list of shown to unread the whole feed quickly becomes read

[Roman via KDE Bugzilla]

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

Roman  changed:

   What|Removed |Added

   Keywords||usability

--- Comment #1 from Roman  ---
Also getting some strange crash after repeating the bug:

Thread 1 (Thread 0x7fe4ff8af940 (LWP 7390)):
[KCrash Handler]
#6  0x7fe4fe49e8b2 in KActionCollection::action(QString const&) const ()
from /usr/lib64/libKF5XmlGui.so.5
#7  0x7fe4d61f4921 in ?? () from /usr/lib64/qt5/plugins/akregatorpart.so
#8  0x7fe4d61f49a8 in ?? () from /usr/lib64/qt5/plugins/akregatorpart.so
#9  0x7fe4d6200071 in
Akregator::ArticleViewer::slotShowSummary(Akregator::TreeNode*) () from
/usr/lib64/qt5/plugins/akregatorpart.so
#10 0x7fe4d6227213 in
Akregator::MainWidget::slotNodeSelected(Akregator::TreeNode*) () from
/usr/lib64/qt5/plugins/akregatorpart.so
#11 0x7fe4fc120e17 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#12 0x7fe4d623f59f in ?? () from /usr/lib64/qt5/plugins/akregatorpart.so
#13 0x7fe4d61e65c4 in ?? () from /usr/lib64/qt5/plugins/akregatorpart.so
#14 0x7fe4fc120e17 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#15 0x7fe4fc0a766a in QItemSelectionModel::currentChanged(QModelIndex
const&, QModelIndex const&) () from /usr/lib64/libQt5Core.so.5
#16 0x7fe4fc0a783d in QItemSelectionModel::setCurrentIndex(QModelIndex
const&, QFlags) () from
/usr/lib64/libQt5Core.so.5
#17 0x7fe4fd9e998c in QAbstractItemView::mousePressEvent(QMouseEvent*) ()
from /usr/lib64/libQt5Widgets.so.5
#18 0x7fe4fda2db07 in QTreeView::mousePressEvent(QMouseEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#19 0x7fe4fd7e3679 in QWidget::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#20 0x7fe4fd8daa2e in QFrame::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#21 0x7fe4fd9f0a24 in QAbstractItemView::viewportEvent(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#22 0x7fe4fda2d3ec in QTreeView::viewportEvent(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#23 0x7fe4fc0f3b25 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib64/libQt5Core.so.5
#24 0x7fe4fd7a28ac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#25 0x7fe4fd7a8511 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#26 0x7fe4fc0f3cf3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#27 0x7fe4fd7a7082 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib64/libQt5Widgets.so.5
#28 0x7fe4fd7fcdd3 in ?? () from /usr/lib64/libQt5Widgets.so.5
#29 0x7fe4fd7ff33b in ?? () from /usr/lib64/libQt5Widgets.so.5
#30 0x7fe4fd7a28cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#31 0x7fe4fd7a79d6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#32 0x7fe4fc0f3cf3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#33 0x7fe4fc63a79e in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib64/libQt5Gui.so.5
#34 0x7fe4fc63c305 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib64/libQt5Gui.so.5
#35 0x7fe4fc6219f8 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib64/libQt5Gui.so.5
#36 0x7fe4dedebed0 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#37 0x7fe4f41ad0c7 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#38 0x7fe4f41ad2f8 in ?? () from /usr/lib64/libglib-2.0.so.0
#39 0x7fe4f41ad39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#40 0x7fe4fc14750f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#41 0x7fe4fc0f163a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#42 0x7fe4fc0f92fd in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#43 0x0040a330 in main ()

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

[akregator] [Bug 359543] New: when changing the list of shown to unread the whole feed quickly becomes read

[Roman via KDE Bugzilla]

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

Bug ID: 359543
   Summary: when changing the list of shown to unread the whole
feed quickly becomes read
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: niflhe...@tut.by

When the list of the shown types of news is changed to "unread", the whole feed
quickly becomes read, as the news seems to be read automatically.

Reproducible: Always

Steps to Reproduce:
1. Select the feed with unread news.
2. Change the list of viewed from "all" to "unread".
3. Watch the counter of unread decreases.

Actual Results:  
The news become read automatically, disappearing from the feed.

Expected Results:  
The news become read, their color changes, but they are still in the list until
the other feed is chosen.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #6 from OlafLostViking  ---
Created attachment 97288
  --> https://bugs.kde.org/attachment.cgi?id=97288=edit
output of "kscreen outputs"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #5 from OlafLostViking  ---
Created attachment 97287
  --> https://bugs.kde.org/attachment.cgi?id=97287=edit
output of "kscreen json"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #4 from OlafLostViking  ---
Created attachment 97286
  --> https://bugs.kde.org/attachment.cgi?id=97286=edit
output of "kscreen config"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #3 from OlafLostViking  ---
Created attachment 97285
  --> https://bugs.kde.org/attachment.cgi?id=97285=edit
output of "kscreen"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #2 from OlafLostViking  ---
Created attachment 97284
  --> https://bugs.kde.org/attachment.cgi?id=97284=edit
output of "kscreen bug"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #1 from OlafLostViking  ---
Created attachment 97283
  --> https://bugs.kde.org/attachment.cgi?id=97283=edit
output of kscreen

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

[KScreen] [Bug 359542] New: Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

Bug ID: 359542
   Summary: Waking up notebook from sleep after undocking leaves
display turned off
   Product: KScreen
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

After putting my notebook to sleep with external monitors attached to the
docking station it's currently connected to and waking it up on the road
(obviously without anything attached) the display stays off.

I can switch with CTRL+ALT+F2 to a text console, but I didn't manage to
reactivate the display from there. There I called kscreen-console; I will
attach the output to the following comments.

The severity was set to "grave" as this is equivalent to a crash with data loss
(at least until I know how to reactivate the screen from a text console ;-) )
when all applications are force-shutdown when rebooting the machine.

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

[kdenlive] [Bug 359541] New: Color grading tools mismatching colors in monitors

[via KDE Bugzilla]

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

Bug ID: 359541
   Summary: Color grading tools mismatching colors in monitors
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
   URL: https://forum.kde.org/viewtopic.php?f=270=131116
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: legocef...@yahoo.fr

I have a problem with my color grading tools on Kdenlive. I'm on ubuntu 15.10
Wily with the las stable kdenlive from sunab repository.

The problem is, if I use the color grading tools, I have an anomaly and I want
to know if it's a problem with my system or not. 

http://i.imgur.com/k9YSE54.png

If you look at the above picture, you can see the Cyan color on the clip
monitor. The anomaly is that, the tools for color grading (the RGB parade and
Vectorscope) on kdenlive indicate that the color is rather yellow : 

- RGB Parade : this tool show the red and green bars at the top, and the blue
bar at the bottom : red + green = yellow
- Vectorscope : the yellow arrow in the picture, that I added to it, indicate
the point printed by the vectorscope. So this point is in the yellow small
circle.

Instead of this, we should have the green and blue (green + blue = cyan) at the
top, and the vectorscope should indicate in the Cy small circle.

By examining this problem by varying the color in all the color spectrum and
observing the vectorscope. The result of this is that, the colors in the line
passing trough the green and magenta are corrects, they match what I see in the
monitor clip. But if I quit the Green point in the clip monitor and want to go
to the yellow color, the vectorscope will show me that I am going rather to the
opposite direction, meaning to the cyan. 

After this, I installed the last unstable kdenlive from sunab, ... same result,
even with the last version from official ubuntu repo, I have the same result. 



Reproducible: Always

Steps to Reproduce:
1. Add a red color clip (or other primary/secondary color) in the bin
2. Click on it to print the clip on the monitor
3. open some color grading tools, preferably "RGB Parade" and "Vectorscope"


Actual Results:  
If it is the red clip, the tools will show it as Blue color. Below you have the
behaviour of the tool, depending on the color of the clip : 
- Green is presented correctly
- Blue is presented as Red
- Cyan is presented as Yellow
- Magenta is presented correctly
- Yellow is presented as Cyan

Expected Results:  
In normal way the color granding tools should indicate :
-  red as red
- Green as green 
- ... and so on

 I'm on ubuntu 15.10 Wily with the last stable kdenlive from sunab repository.
After the problem, I tried this. I installed the last unstable kdenlive from
sunab, ... same result, even with the last version from official ubuntu repo, I
have the same result.

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

[okular] [Bug 351849] Margins often cut when printing

[James Funk via KDE Bugzilla]

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

--- Comment #4 from James Funk  ---
(In reply to James Funk from comment #3)
> I wonder if my problem is the same? Or is mine a similar problem?  When I
> try to print the PDF at
> http://www.ritetemp-thermostats.com/80XX/images/8082C_operation_guide.pdf  ,
> the printout has only part of the page. It is as if the page image had been
> enlarged, and the part of it gets printed on my 8.5 inch by 11 inch paper.

I neglected to mention some things. I'm using a Brother HL-5140 laser printer,
OpenSuSE 13.2

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

[okular] [Bug 351849] Margins often cut when printing

[James Funk via KDE Bugzilla]

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

James Funk  changed:

   What|Removed |Added

 CC||marathon...@yahoo.com

--- Comment #3 from James Funk  ---
I wonder if my problem is the same? Or is mine a similar problem?  When I try
to print the PDF at
http://www.ritetemp-thermostats.com/80XX/images/8082C_operation_guide.pdf  ,
the printout has only part of the page. It is as if the page image had been
enlarged, and the part of it gets printed on my 8.5 inch by 11 inch paper.

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

[digikam] [Bug 359540] Digikam crash

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from caulier.gil...@gmail.com ---


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

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

[digikam] [Bug 329697] digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite)

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||shadow7...@lycos.com

--- Comment #157 from caulier.gil...@gmail.com ---
*** Bug 359540 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 359518] No icons in the interface.

[Leny via KDE Bugzilla]

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

--- Comment #2 from Leny  ---
I've solved the problem by installing KDE.runtime on Ubuntu 15:10 Wily Werewolf
.
Note: my Kdenlive is at version 15.12.0 . 
Another suggestion along with a rectangle type tool to select the part you want
to zoom in would be useful and more facíl.
Poderiam also add a tool callouts , such as arrows, circles ... etcs type
callouts .

> From: bugzilla_nore...@kde.org
> To: morfheu...@hotmail.com
> Subject: [kdenlive] [Bug 359518] No icons in the interface.
> Date: Thu, 18 Feb 2016 00:21:36 +
> 
> https://bugs.kde.org/show_bug.cgi?id=359518
> 
> farid  changed:
> 
>What|Removed |Added
> 
>  CC||snd.no...@gmail.com
> 
> --- Comment #1 from farid  ---
> ehich version of kdenlive? do you have the breeze icons installed?
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
   =

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

[konsole] [Bug 356223] konsole crashes when external monitor is unplugged

[via KDE Bugzilla]

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

ric...@nakts.net changed:

   What|Removed |Added

 CC||ric...@nakts.net

--- Comment #2 from ric...@nakts.net ---
also reported for opensuse :
https://bugzilla.opensuse.org/show_bug.cgi?id=957060

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

[digikam] [Bug 359540] New: Digikam crash

[via KDE Bugzilla]

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

Bug ID: 359540
   Summary: Digikam crash
   Product: digikam
   Version: 4.0.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: shadow7...@lycos.com

Application: digikam (4.0.0)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.19.0-32-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed:
... changing folder/directory.  Chrome was also open on seperate monitor

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

Thread 7 (Thread 0x7fc02815b700 (LWP 4125)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc04f3ec816 in wait (time=18446744073709551615, this=0x2653270) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1f9a9f0,
mutex=mutex@entry=0x1f9a9e8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x005e3d9e in Digikam::ScanController::run (this=0x2506d30) at
/build/buildd/digikam-4.0.0/core/digikam/database/scancontroller.cpp:725
#4  0x7fc04f3ec32f in QThreadPrivate::start (arg=0x2506d30) at
thread/qthread_unix.cpp:349
#5  0x7fc048c7f754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x7fc049bee182 in start_thread (arg=0x7fc02815b700) at
pthread_create.c:312
#7  0x7fc04d71347d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7fc02795a700 (LWP 4126)):
#0  0x7fc04d70612d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc046661fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc0466620ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc04f51b7be in QEventDispatcherGlib::processEvents
(this=0x7fc0180008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7fc04f4ed0af in QEventLoop::processEvents
(this=this@entry=0x7fc027959a20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fc04f4ed3a5 in QEventLoop::exec (this=this@entry=0x7fc027959a20,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fc04f3e9c5f in QThread::exec (this=this@entry=0x20269f0) at
thread/qthread.cpp:537
#7  0x7fc04f4ce823 in QInotifyFileSystemWatcherEngine::run (this=0x20269f0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fc04f3ec32f in QThreadPrivate::start (arg=0x20269f0) at
thread/qthread_unix.cpp:349
#9  0x7fc048c7f754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#10 0x7fc049bee182 in start_thread (arg=0x7fc02795a700) at
pthread_create.c:312
#11 0x7fc04d71347d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7fc027159700 (LWP 4152)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc04f3ec816 in wait (time=18446744073709551615, this=0x261acb0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x2098dd0,
mutex=mutex@entry=0x2098dc8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7fc051c2c8aa in Digikam::ParkingThread::run (this=0x2098db0) at
/build/buildd/digikam-4.0.0/core/libs/threads/threadmanager.cpp:119
#4  0x7fc04f3ec32f in QThreadPrivate::start (arg=0x2098db0) at
thread/qthread_unix.cpp:349
#5  0x7fc048c7f754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x7fc049bee182 in start_thread (arg=0x7fc027159700) at
pthread_create.c:312
#7  0x7fc04d71347d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fc0260d3700 (LWP 4153)):
#0  0x7ffeca9e4cb6 in ?? ()
#1  0x7fc0545b4000 in ?? ()
#2  0x0001 in ?? ()
#3  0x00024f3e2244 in ?? ()
#4  0x7fc010002f30 in ?? ()
#5  0x7fc0260d2868 in ?? ()
#6  0x7fc0260d2800 in ?? ()
#7  0x7fff in ?? ()
#8  0x7fc0260d2870 in ?? ()
#9  0x7fc04d72192d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#10 0x7fc04f440ad7 in do_gettime (frac=0x7fc0260d27b0, sec=0x7fc0260d27a8)
at tools/qelapsedtimer_unix.cpp:127
#11 qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#12 0x7fc04f51cf05 in updateCurrentTime (this=0x1) at
kernel/qeventdispatcher_unix.cpp:354
#13 QTimerInfoList::timerWait (this=0x1, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#14 0x7fc04f51b67c in timerSourcePrepareHelper (src=,
timeout=0x7fc0260d2864) at kernel/qeventdispatcher_glib.cpp:143
#15 0x7fc04f51b725 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:176
#16 

[partitionmanager] [Bug 346787] There are, still, some bugs assigned to Volker Lanz. Maybe there's an automatic mechanism to assign bugs to him

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

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

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

[partitionmanager] [Bug 356556] Support for Allocation Unit Size

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[partitionmanager] [Bug 355051] Will not allow me to use any part of the interface to manage device partitions

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Andrius Štikonas  ---
Version 1.0.3 is too old (about  6 years old). Newer version should work.

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

[partitionmanager] [Bug 354925] HTML visible in "Missing File System Support Packages" alert

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/part
   ||itionmanager/d2a013222ea783
   ||5ad9d14f3ee9f96bba7a482412

--- Comment #5 from Andrius Štikonas  ---
Git commit d2a013222ea7835ad9d14f3ee9f96bba7a482412 by Andrius Štikonas.
Committed on 18/02/2016 at 14:59.
Pushed by stikonas into branch 'master'.

Use KLocalizeStrings to avoid nested xi18n calls.
Nested xi18n calls cause QStrings to be escaped and makes HTML
visible in KMessageBox.

M  +20   -21   src/gui/mainwindow.cpp

http://commits.kde.org/partitionmanager/d2a013222ea7835ad9d14f3ee9f96bba7a482412

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

[plasmashell] [Bug 359539] New: Plasma frequently crashes with new installation

[WeBeGood via KDE Bugzilla]

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

Bug ID: 359539
   Summary: Plasma frequently crashes with new installation
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: webeg...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

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

-- Information about the crash:
- What I was doing when the application crashed: Nothing in particular, just
using the KDE Plasma desktop. The Plasma crashing has occured regularly since I
freshly installed opensuse.

The crash can be reproduced every time.

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

Thread 14 (Thread 0x7f4252760700 (LWP 1700)):
#0  0x7f4263ae9c1d in poll () at /lib64/libc.so.6
#1  0x7f4268a15422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f4268a1700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f4254ee33c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f42641e132f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f42632f30a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4263af204d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f4247cc8700 (LWP 1716)):
#0  0x7f4263ae9c1d in poll () at /lib64/libc.so.6
#1  0x7f42601cbe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f42601cbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4264413d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f42643bad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f42641dc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f42674c7df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f42641e132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f42632f30a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4263af204d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f423c112700 (LWP 1727)):
#0  0x7f4263ae9c1d in poll () at /lib64/libc.so.6
#1  0x7f42601cbe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f42601cbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4264413d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f42643bad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f42641dc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f42674c7df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f42641e132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f42632f30a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4263af204d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f423a77e700 (LWP 1738)):
#0  0x7f4263ae5ced in read () at /lib64/libc.so.6
#1  0x7f425bca3f75 in  () at /usr/lib64/tls/libnvidia-tls.so.352.79
#2  0x7f426020cb60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f42601cb999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f42601cbdf8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f42601cbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f4264413d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f42643bad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f42641dc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f42674c7df8 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f42641e132f in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f42632f30a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f4263af204d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f4238e5a700 (LWP 1750)):
#0  0x7f4263ae5ced in read () at /lib64/libc.so.6
#1  0x7f425bca3f75 in  () at /usr/lib64/tls/libnvidia-tls.so.352.79
#2  0x7f426020cb60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f42601cb999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f42601cbdf8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f42601cbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f4264413d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f42643bad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f42641dc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f42674c7df8 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f42641e132f in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f42632f30a4 in start_thread () at /lib64/libpthread.so.0
#12 

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Thiago Oliveira via KDE Bugzilla]

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

Thiago Oliveira  changed:

   What|Removed |Added

 CC||strat...@gmail.com

--- Comment #33 from Thiago Oliveira  ---
One year has been passed since the first entry in the bug track and no solution
so far... :(

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

[calligraplan] [Bug 359537] New: Calligra Plan Crash every time when try to start a templet

[rana via KDE Bugzilla]

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

Bug ID: 359537
   Summary: Calligra Plan Crash every time when try to start a
templet
   Product: calligraplan
   Version: 2.9.11
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kosse...@kde.org
  Reporter: eierajat@gmail.com

Application: calligraplan (2.9.11)
KDE Platform Version: 4.14.16
Qt Version: 4.8.6
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: I am just trying to start a
templet and Calligra Plan every time crash. 

- Unusual behavior I noticed:
If I reboot my system several time then again for 1 time its start and if i
exit the project without saving the crash again starts.

The crash can be reproduced every time.

-- Backtrace:
Application: Plan (calligraplan), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7fdac527d1de in QObject::objectName() const () at
/usr/lib64/libQtCore.so.4
#7  0x7fdab223cb95 in
KPlato::Report::findReportData(QList const&, QString
const&) () at /usr/lib64/libkplatoui.so.14
#8  0x7fdab2235cb5 in KPlato::ReportDesigner::setReportData(QString const&)
() at /usr/lib64/libkplatoui.so.14
#9  0x7fdac52800fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#10 0x7fdab222b7d2 in  () at /usr/lib64/libkplatoui.so.14
#11 0x7fdab224164f in  () at /usr/lib64/libkplatoui.so.14
#12 0x7fdab222b776 in  () at /usr/lib64/libkplatoui.so.14
#13 0x7fdac52800fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#14 0x7fdac603b561 in QComboBox::currentIndexChanged(int) () at
/usr/lib64/libQtGui.so.4
#15 0x7fdac603b5c1 in  () at /usr/lib64/libQtGui.so.4
#16 0x7fdac603b86c in  () at /usr/lib64/libQtGui.so.4
#17 0x7fdac603babf in QComboBox::setCurrentIndex(int) () at
/usr/lib64/libQtGui.so.4
#18 0x7fdab2241b4f in  () at /usr/lib64/libkplatoui.so.14
#19 0x7fdab2235e2f in KPlato::ReportDesigner::setData() () at
/usr/lib64/libkplatoui.so.14
#20 0x7fdab2236060 in KPlato::ReportDesigner::setData(QDomDocument const&)
() at /usr/lib64/libkplatoui.so.14
#21 0x7fdab223608c in KPlato::ReportView::loadXML(QDomDocument const&) ()
at /usr/lib64/libkplatoui.so.14
#22 0x7fdab25b693e in KPlato::View::createViews() () at
/usr/lib64/libplanprivate.so.14
#23 0x7fdab25b76ee in KPlato::View::initiateViews() () at
/usr/lib64/libplanprivate.so.14
#24 0x7fdab25b9215 in  () at /usr/lib64/libplanprivate.so.14
#25 0x7fdac52800fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#26 0x7fdac5288f6a in  () at /usr/lib64/libQtCore.so.4
#27 0x7fdac52842b1 in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#28 0x7fdac5c7679c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#29 0x7fdac5c7ccdd in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#30 0x7fdac67a7e37 in KoApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkomain.so.14
#31 0x7fdac526c18d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#32 0x7fdac529bbbc in  () at /usr/lib64/libQtCore.so.4
#33 0x7fdac5298e39 in  () at /usr/lib64/libQtCore.so.4
#34 0x7fdac1f75c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#35 0x7fdac1f75ed8 in  () at /usr/lib64/libglib-2.0.so.0
#36 0x7fdac1f75f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#37 0x7fdac5298fbe in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#38 0x7fdac5d136a6 in  () at /usr/lib64/libQtGui.so.4
#39 0x7fdac526ad4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#40 0x7fdac526b045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#41 0x7fdac5270499 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#42 0x7fdac6dfa965 in kdemain () at /usr/lib64/libkdeinit4_calligraplan.so
#43 0x7fdac6a73b05 in __libc_start_main () at /lib64/libc.so.6
#44 0x0040075e in _start ()

Reported using DrKonqi

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

[systemsettings] [Bug 359536] New: systemsettings crashes when trying to set automatic date/time change

[Arruor]

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

Bug ID: 359536
   Summary: systemsettings crashes when trying to set automatic
date/time change
   Product: systemsettings
   Version: 5.5.4
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: arr...@gmail.com

Application: systemsettings5 (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.4.1 x86_64
Distribution (Platform): Slackware Packages

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

systemsettings crashed when tryting to set automatic date / time change in
Regininal Settings.
When try to set NTP server and/or change time zone systemsettings5 shows error
message like "Unable to authenticate/execute the action: 4, " after providing
root password.
After showing the error - it crashes on exit (either with Alt+F4 or by clicking
on close button in titlebar).

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f871d65c7c0 (LWP 20709))]

Thread 5 (Thread 0x7f870aa46700 (LWP 20710)):
#0  0x7f871798b4fd in poll () at /lib64/libc.so.6
#1  0x7f87144c9102 in  () at /usr/lib64/libxcb.so.1
#2  0x7f87144cac8f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f870c88ca49 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f871859ff3f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8713c76704 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8717996f8d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f86e3fff700 (LWP 20736)):
#0  0x7f871798b4fd in poll () at /lib64/libc.so.6
#1  0x7f87132e7954 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f87132e7a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f87132e7a99 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f871330d1e5 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f8713c76704 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8717996f8d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f86e319e700 (LWP 20737)):
#0  0x7f871798b4fd in poll () at /lib64/libc.so.6
#1  0x7f87132e7954 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f87132e7cd2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f86ecc7ba56 in  () at /usr/lib64/../lib64/libgio-2.0.so.0
#4  0x7f871330d1e5 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f8713c76704 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8717996f8d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f86ded7e700 (LWP 20767)):
#0  0x7f8717991139 in syscall () at /lib64/libc.so.6
#1  0x7f871332aa34 in g_cond_wait_until () at /usr/lib64/libglib-2.0.so.0
#2  0x7f87132bd319 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f87132bd90b in g_async_queue_timeout_pop () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f871330dc2a in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f871330d1e5 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x7f8713c76704 in start_thread () at /lib64/libpthread.so.0
#7  0x7f8717996f8d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f871d65c7c0 (LWP 20709)):
[KCrash Handler]
#6  0x0050 in  ()
#7  0x7f87187a1479 in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () at /usr/lib64/libQt5Core.so.5
#8  0x7f86f79fb576 in KParts::PartManager::~PartManager() () at
/usr/lib64/libKF5Parts.so.5
#9  0x7f86f79fb709 in KParts::PartManager::~PartManager() () at
/usr/lib64/libKF5Parts.so.5
#10 0x7f871879b76b in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#11 0x7f87187a4f70 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#12 0x7f86f81492fb in KHTMLPart::~KHTMLPart() () at
/usr/lib64/libKF5KHtml.so.5
#13 0x7f86f81493f9 in KHTMLPart::~KHTMLPart() () at
/usr/lib64/libKF5KHtml.so.5
#14 0x7f871879dfa0 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#15 0x7f871a53b11c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#16 0x7f871a540236 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7f87187703f3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#18 0x7f8718772716 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#19 0x7f87187c3813 in  () at /usr/lib64/libQt5Core.so.5
#20 0x7f87132e7787 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#21 0x7f87132e79b8 in  () at /usr/lib64/libglib-2.0.so.0
#22 0x7f87132e7a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0

[Powerdevil] [Bug 359535] New: Activity Settings have "Act like" selectbox even on desktop computers

[Thomas Pfeiffer via KDE Bugzilla]

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

Bug ID: 359535
   Summary: Activity Settings have "Act like" selectbox even on
desktop computers
   Product: Powerdevil
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: colo...@autistici.org

The Power Management KCM does not distinguish between AC, battery and low
battery when on a machine without a battery (which makes perfect sense), but
the "Activity Settings" tab there is still the "Act like" selectbox, which
doesn't make sense in this situation.

Reproducible: Always

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

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

[David Brůha via KDE Bugzilla]

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

David Brůha  changed:

   What|Removed |Added

 CC||sal...@albatani.cz

--- Comment #19 from David Brůha  ---
I can confirm this behaviour as well on Kubuntu Wily (KMail 5.0.2, Aconadi
5.0.51) when communicating with Courier IMAP server (both non deleting messages
and excessive amount of transmitted data). Other accounts connecting to Dovecot
are not affected.

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

[plasmashell] [Bug 359534] panels ignore alignment and stick to the left screen

[Pavel S . via KDE Bugzilla]

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

Pavel S.  changed:

   What|Removed |Added

  Attachment #97281|application/vnd.osgi.dp |text/plain
  mime type||

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

[plasmashell] [Bug 359534] panels ignore alignment and stick to the left screen

[Pavel S . via KDE Bugzilla]

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

--- Comment #1 from Pavel S.  ---
Created attachment 97281
  --> https://bugs.kde.org/attachment.cgi?id=97281=edit
xrandr output for the failing configuration

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

[plasmashell] [Bug 359534] New: panels ignore alignment and stick to the left screen

[Pavel S . via KDE Bugzilla]

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

Bug ID: 359534
   Summary: panels ignore alignment and stick to the left screen
   Product: plasmashell
   Version: 5.5.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: codeatst...@googlemail.com

I have a problem with the dual screen setup on my T410 laptop. My laptop screen
is set up to be the primary display. The second screen has a large resolution
and is  set up to be on the left of the primary laptop screen. 

Reproducible: Always

Steps to Reproduce:
1. connect the second screen and set it up to be left of the primary screen,
that contains a panel
the configuration should correspond to
xrandr --output LVDS-1 --mode 1440x900 --pos 1680x267 --rotate normal --primary
--output DP-3 --mode 1680x1050 --pos 0x0 --rotate normal
2. log out and disconnect the second screen
3. log in
4. connect second screen during the session

Actual Results:  
The panel from the primary (right) screen is moved to the secondary screen on
the left as soon as is becomes available, the alignment setting, that I thought
to be the culprit has no effect.

Expected Results:  
The panel should stay on the primary screen no matter what.

machine: TinkPad T410
gpu: NVIDIA Corporation GT218M [NVS 3100M] (rev a2)
driver: nouveau
kernel: 4.3.5-300.fc23.x86_64

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

[partitionmanager] [Bug 353333] partitionmanager crashed on start

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

--- Comment #3 from Andrius Štikonas  ---
*** Bug 351423 has been marked as a duplicate of this bug. ***

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

[partitionmanager] [Bug 351423] KDE Partition Manager crash on starting

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

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

--- Comment #2 from Andrius Štikonas  ---


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

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

[partitionmanager] [Bug 353333] partitionmanager crashed on start

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kpmc
   ||ore/20bb8eba7ec9c57da4e2441
   ||5e54a3b84909744c1
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Andrius Štikonas  ---
Git commit 20bb8eba7ec9c57da4e24415e54a3b84909744c1 by Andrius Štikonas.
Committed on 18/02/2016 at 13:39.
Pushed by stikonas into branch 'master'.

Get btrfs used capacity from btrfs filesystem show --raw
It's output looks like:

Label: 'test'  uuid: d23f3138-c8ea-449e-9155-015ce4f6e2e6
Total devices 1 FS bytes used 131072
devid1 size 981467136 used 252706816 path /dev/sdb1

FS bytes used number is actual data on btrfs volume. However,
to resize successfully we need to know actual space used by data
and metadata. That's why we read size from devid (i.e. 252706816).

Btrfs volumes can span over multiple devices, so we must make sure
that we are reading devid corresponding to the correct device node.

M  +2-2src/fs/btrfs.cpp

http://commits.kde.org/kpmcore/20bb8eba7ec9c57da4e24415e54a3b84909744c1

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #6 from Christian Stadelmann  ---
> Obviously the problem here is that gtk hard depends on an unreleased, not
> standardized interface. It should check whether it exists and if not either
> exit (heck one could also use X11, no need to crash just because there's a
> Wayland socket) or fall back to wl_shell as Qt does.

That's the core problem and Gtk+ people are fixing it. See
https://bugzilla.gnome.org/show_bug.cgi?id=762258

Sorry for the noise.

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #5 from Martin Gräßlin  ---
(In reply to Jonas Ådahl from comment #4)
> > Sorry we don't use bugs to track progress, but I have a task on
> > todo.kde.org: https://todo.kde.org/?controller=task=show_id=1612
> 
> That link was password protected.

meh sorry. It's also available to public under
https://todo.kde.org/?controller=board=readonly=0ef6e11806f1410bf0a3ba50e2bbb22ccfaf2c0f2b52b1c1726f25c2ce3d

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Jonas Ådahl via KDE Bugzilla]

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

--- Comment #4 from Jonas Ådahl  ---
(In reply to Martin Gräßlin from comment #3)
> (In reply to Jonas Ådahl from comment #2)
> > That being said, it would be appreciated if kwin would support xdg_shell (or
> > at least the next version xdg_shell that is in the making that fixes various
> > issues with the current version) as an experimental feature at least.
> 
> I hope to find time for it, but I cannot promise anything. The unstable
> aspect makes it really hard to implement support for it. As soon as we
> export it, QtWayland would use it and break as we would have a newer version
> than Qt. This makes it just a terrible hassle to work with it as it means my
> desktop breaks.

Yes, this is the reason I would like it to be declared stable not to far into
the future. I think v6 might be a candidate for this, but exactly how it'll
look is undecided. You should be able to find a couple of patches on the
mailing list with that changes the interface object tree structure and adding a
non-grabbing popup. One part that is not on the list is a popup positioning
system enabling declarative menu positioning, but it'll be sent to the list
quite soon.

So far the v6 has only one semantical change merged so far, please see the
current wip branch:
https://cgit.freedesktop.org/wayland/wayland-protocols/log/?h=wip%2Fxdg-shell-unstable-v6

> 
> Similar I would not even be able to test GTK applications with it as I use
> distro packages of GTK.
> 
> > Not
> > only to make future gtk+ clients testable but also to improve the
> > cross-desktop-ness of xdg_shell, given that we receive feedback.
> 
> well I can have a look at the latest draft and provide feedback on it. I
> think I did so in the past already ;-)
> 
> > The option
> > we have is to declare some future version stable without there being a kwin
> > implementation, and we would either need to live with that version (as a
> > base) or stay incompatible indefinitely.
> > 
> > If you create a bug tracking that progress, please CC me so I can stay
> > updated.
> 
> Sorry we don't use bugs to track progress, but I have a task on
> todo.kde.org: https://todo.kde.org/?controller=task=show_id=1612

That link was password protected.

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

[krita] [Bug 359533] New: Pop Up Palette Colour Selector is Too Small

[Chris Jones via KDE Bugzilla]

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

Bug ID: 359533
   Summary: Pop Up Palette Colour Selector is Too Small
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: color selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: ch...@outlook.com

As modern displays continue to increase in resolution, it is becoming ever more
difficult to accurately select colours with the popup palette.  Enlarging the
pop up colour selector would allow the Advanced Colour Selector to be dispensed
with, thereby freeing up screen real estate, which is especially valuable on
smaller screens such as tablets.

Reproducible: Always

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Jonas Ådahl via KDE Bugzilla]

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

--- Comment #2 from Jonas Ådahl  ---
(In reply to Martin Gräßlin from comment #1)
> xdg_shell is not yet a standardized protocol with API compatibility
> guarantees. This makes it almost impossible to wrap it in an ABI stable
> library as KWayland is.
> 
> Even if we added support for it, it is unlikely that this would solve the
> problem of gtk applications crashing. Due to the unstable xdg_shell one
> needs to have exactly the same version of the unstable protocol to have it
> working. As GTK+, Wayland, Qt and KWin releases are not synced it becomes
> unlikely that all of them have the same magic version. KWin would probably
> follow the version used in the QtWayland release of the Qt build dep. That's
> about 1 year behind what Wayland has and thus most likely also behind what
> GTK+ has. Given that it would still not work.
> 
> Overall that's the reason why I so far refused to spend time on adding
> support for xdg_shell. I simply don't see how it would fix anything of this
> compatibility issue. I have it on my todo list, but it will be hidden behind
> an explicit compile time flag. This is the only way how we can solve the API
> instability problem in our stable KWayland library.
> 
> Obviously the problem here is that gtk hard depends on an unreleased, not
> standardized interface. It should check whether it exists and if not either
> exit (heck one could also use X11, no need to crash just because there's a
> Wayland socket) or fall back to wl_shell as Qt does.
> 
> I'm setting to INVALID as the bug in question is in GTK and not in KWin.
> Support for xdg_shell will be added eventually but I do not see the lack of
> support for an unstable interface as a bug in KWin.

I agree that this bug should be marked as invalid since this is about actually
about a gtk+ bug. And FWIW, last time I tested gtk+ would fail gracefully and
fallback on X11, so this seems to be a regression.

That being said, it would be appreciated if kwin would support xdg_shell (or at
least the next version xdg_shell that is in the making that fixes various
issues with the current version) as an experimental feature at least. Not only
to make future gtk+ clients testable but also to improve the cross-desktop-ness
of xdg_shell, given that we receive feedback. The option we have is to declare
some future version stable without there being a kwin implementation, and we
would either need to live with that version (as a base) or stay incompatible
indefinitely.

If you create a bug tracking that progress, please CC me so I can stay updated.

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

[k3b] [Bug 359532] New: Burning speed can´t be reduced

[Armin Mohring via KDE Bugzilla]

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

Bug ID: 359532
   Summary: Burning speed can´t be reduced
   Product: k3b
   Version: 2.0.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Burning/Hardware
  Assignee: k...@kde.org
  Reporter: armin_mohr...@web.de
CC: mich...@jabster.pl, tr...@kde.org

It is meaningful, if it is possible to set the burning speed to the user
preferences.
E.g.: 4x, 6x, 8x, and so on.

Reproducible: Always

Steps to Reproduce:
1. Start K3B
2. Insert CD-RW or DVD-RW
3. Start burning
4. Can´t set burning speed to e.g.: 4x, 

Actual Results:  
The burning speed to set to the CD-RW s maximum.

Expected Results:  
Set to 4x or 6x or 8x

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
xdg_shell is not yet a standardized protocol with API compatibility guarantees.
This makes it almost impossible to wrap it in an ABI stable library as KWayland
is.

Even if we added support for it, it is unlikely that this would solve the
problem of gtk applications crashing. Due to the unstable xdg_shell one needs
to have exactly the same version of the unstable protocol to have it working.
As GTK+, Wayland, Qt and KWin releases are not synced it becomes unlikely that
all of them have the same magic version. KWin would probably follow the version
used in the QtWayland release of the Qt build dep. That's about 1 year behind
what Wayland has and thus most likely also behind what GTK+ has. Given that it
would still not work.

Overall that's the reason why I so far refused to spend time on adding support
for xdg_shell. I simply don't see how it would fix anything of this
compatibility issue. I have it on my todo list, but it will be hidden behind an
explicit compile time flag. This is the only way how we can solve the API
instability problem in our stable KWayland library.

Obviously the problem here is that gtk hard depends on an unreleased, not
standardized interface. It should check whether it exists and if not either
exit (heck one could also use X11, no need to crash just because there's a
Wayland socket) or fall back to wl_shell as Qt does.

I'm setting to INVALID as the bug in question is in GTK and not in KWin.
Support for xdg_shell will be added eventually but I do not see the lack of
support for an unstable interface as a bug in KWin.

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Jonas Ådahl via KDE Bugzilla]

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

Jonas Ådahl  changed:

   What|Removed |Added

 CC||jad...@gmail.com

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

[plasmashell] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

  Component|Icons-only Task Manager |general
   Assignee|h...@kde.org|k...@davidedmundson.co.uk
 CC||bhus...@gmail.com

--- Comment #13 from Eike Hein  ---
Nothing has changed in Icontasks whatsoever.

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

[konsole] [Bug 345403] "Terminal Size" setting in profile ignored

[Radics Péter via KDE Bugzilla]

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

--- Comment #36 from Radics Péter  ---
(In reply to subdiff from comment #35)

Yes, I can use the workaround for now (in fact, I have been using another
workaround on my main computer until now ;), just wanted to let you know that
the fix is not "perfect" :)

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

URL||https://bugzilla.gnome.org/
   ||show_bug.cgi?id=762258

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

[konsole] [Bug 345403] "Terminal Size" setting in profile ignored

[subdiff via KDE Bugzilla]

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

--- Comment #35 from subdiff  ---
Thanks for feedback. Did I understand correctly that this is only a non
critical problem because there is the workaround of just applying some
different size (in your case 80x23 instead of 80x25)?

In this case I would ignore that for the moment, because there seems to be some
bigger transition going on in the Konsole Source (moving away from
KUniqueApplication), which also could affect our fix for this bug.

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

[partitionmanager] [Bug 353333] partitionmanager crashed on start

[Teo Mrnjavac via KDE Bugzilla]

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

Teo Mrnjavac  changed:

   What|Removed |Added

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

--- Comment #1 from Teo Mrnjavac  ---
This is also triggered in Calamares, it seems to be a KPMcore issue triggered
by the presence of a Btrfs volume.
We got a full backtrace at https://calamares.io/bugs/browse/CAL-355

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

[kwin] [Bug 359531] New: [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 359531
   Summary: [wayland] add support for xdg_shell should stop gtk3
applications from crashing
   Product: kwin
   Version: 5.5.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dah5a...@genodeftest.de

Currently, any gtk+ 3.x application (with wayland rendering backend enabled by
default) starting inside kwin+wayland will crash.


Reproducible: Always

Steps to Reproduce:
1. Run a kwin_wayland session, even a nested one works:
   $ kwin_wayland --xwayland --windowed
2. Start any gtk3 based application
   $ gnome-calculator

Actual Results:  
segfault in wl_proxy_marshal_constructor() because the proxy is NULL.

Expected Results:  
No crash

According to Oliver Fourdan (RedHat) this is because kwin@wayland doesn't
implement the xdg_shell protocol yet.

I am posting this here so nobody will wonder why gtk+ 3.x applications always
crash on start.

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 wl_proxy_marshal_constructor at src/wayland-client.c:678
 #1 gdk_wayland_window_create_xdg_surface at
../../gdk/wayland/xdg-shell-client-protocol.h:151
 #3 gdk_wayland_window_show at gdkwindow-wayland.c:1394
 #5 gdk_window_show_internal at gdkwindow.c:5013
 #6 gtk_window_map at gtkwindow.c:6099

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

[plasma4] [Bug 359530] New: Applications goes under the main panel

[kkolle via KDE Bugzilla]

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

Bug ID: 359530
   Summary: Applications goes under the main panel
   Product: plasma4
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: containment-panel
  Assignee: plasma-b...@kde.org
  Reporter: k...@kolle.com

I cannot find plasma5 in the list of products to choose from!

I use to have the main panel on the left side of the screen in vertical mode -
it gives me more screen estate in the height to work on.

When moving an application it goes under the panel - this can be alright. 

After a start of the laptop the applications started to the left of the screen
always goes under the panel.

The panel does not respect the setting "Always visible" - which I reads as do
not place application windows under the panel.

Reproducible: Always

Steps to Reproduce:
1. Place an application next to the panel
2. log out
3. log in again and the application window is now under the panel

Actual Results:  
the application window is now under the panel

Expected Results:  
Application to be placed where I left it before logging out

KDE Plasma Version 5.5.4
QT version 5.5.1
Kernel version 4.3.5-300.fc23.x86_64

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