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

[thomi_ch via KDE Bugzilla]

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

--- Comment #87 from thomi_ch  ---
(In reply to Andreas Krohn from comment #85)
> I might have found something to help fix this:
> In my case the panel always appears on the screen containing the mouse. So
> if I login and quickly move the mouse to the "correct" screen (the one I
> want to have the panel on), everything is fine. If I leave the mouse on the
> "wrong" screen, the panel is on that screen as well.
> 
> Is that just me or can anyone confirm this behavior?

hy

i tried it while logged in to plug/unplug external VGA monitor.. but for the
moment panel keeps on correct screen > laptop screen... strange... i only
notice, that mouse jumps around if i plug/unplug external monitor.

i don't know, if that helps, but does panel position do have to do also with
laptop state? i mean, if i unplug external monitor i normally set my laptop
into standby mode.. use it later w/o external monitor, put it again in standby
and use it after with external monitor and sometimes then panel position is on
external monitor and i need to restart plasma stuff...

regards
thomi

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

[digikam] [Bug 362472] Provide a way to install Digikam 4.14 in (K)Ubuntu 16.04 (Xenial)

[via KDE Bugzilla]

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

--- Comment #4 from y...@riseup.net ---
Just in case somebody else stumbles upon this post: I contacted Philip Johnsson
who maintains the PPA at https://launchpad.net/~philip5/+archive/ubuntu/extra
and he told me that he is working on packages of digikam 4.14 and digikam 5
beta 6 for Ubuntu 16.04 right now that he will upload to his PPA. But there are
still some issues with geolocation and maps that he hasn't been able to solve
yet.

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

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

[Kishore via KDE Bugzilla]

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

--- Comment #86 from Kishore  ---
(In reply to Andreas Krohn from comment #85)
> I might have found something to help fix this:
> In my case the panel always appears on the screen containing the mouse. So
> if I login and quickly move the mouse to the "correct" screen (the one I
> want to have the panel on), everything is fine. If I leave the mouse on the
> "wrong" screen, the panel is on that screen as well.
> 
> Is that just me or can anyone confirm this behavior?

Very interesting. I shall try this as soon as i get home.

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

[konsole] [Bug 306062] konsolepart should provide default shortcut for increasing/decreasing font size

[via KDE Bugzilla]

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

andydecle...@gmail.com changed:

   What|Removed |Added

 CC||andydecle...@gmail.com

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

[digikam] [Bug 362569] digicam-dbg package incompatible with current version of digikam.

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
UPSTREAM problem. Report this to Debian team.

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

[plasmashell] [Bug 362536] Setting 'no icons on buttons' is not taken into account

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|major   |minor

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

[marble] [Bug 362314] crash after close

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[krita] [Bug 362571] New: Clicking outside of Color Adjustment Curves window AND outside of image area, using Wacom intuos pro pen, leads to Krita hanging

[via KDE Bugzilla]

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

Bug ID: 362571
   Summary: Clicking outside of Color Adjustment Curves  window
AND outside of image area, using Wacom intuos pro pen,
leads to Krita hanging
   Product: krita
   Version: 2.9.11
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: kritau...@biketrials.com

If a wacom intuos pro pen is used to click outside of the Color Adjustment
Curves window, in the gray area OUTSIDE of the image, Krita enters a weird
state. Trying to bring up the Color Adjustment Curves window again then causes
Krita to hang (i.e. become unresponsive, covered with white overlay).

If a mouse is used to do the same thing, no problem.

Reproducible: Always

Steps to Reproduce:
0. Wacom Intuos Pro Small 
* Wacom Control Panel/Driver version: 6.3.11-4
* Settings: Pen tip = left click, Lower Pen Button (closer to tip) = right
click.
* Everything else disabled (to be explicit: pen eraser, upper pen button,
tablet buttons, tablet touchring, tablet touch capability, and tablet wireless
capability are all disabled)
* Settings apply to all applications; no individual applications are
identified.

1. Run Krita 2.9.11

2. Create a new file: File > New
* The new file's dimensions are defined so that there is gray area around
the image (I defined a 2048x2048 pixel square image).

3. Brush tool (basic circle) is the active tool

4. Filter > Adjust > color Adjustment Curves: the curves window pops up

5. USING THE WACOM PEN: 
* Left click (using the tip) on the gray area around the image.
* The curves window disappears
* The cursor becomes a black circle with a diagonal slash through it.

6. Try to bring up the curves window again using Filter > Adjust > Color
Adjustment curves: Krita hangs, and has to be killed from Windows Task Manager.

Actual Results:  
Krita hangs, and has to be killed from Windows Task Manager. 


Expected Results:  
If step 5 is performed using the mouse instead of the wacom pen,  the curves
window disappears, but the cursor is still the regular circle brush cursor
(circle). The curves window can be opened again successfully, and nothing bad
happens.

Alternate procedure/result:
In step 6, instead of trying to bring up the Adjustment Curve window again,
close krita instead
using the X button at the top right. At the prompt to save, click no. Krita
will appear to close. 
However, open up Windows Task Manager: in the Processes tab, Krita is still
listed as running, and is using a larger amount of memory than usual. If the
user tries to run another instance of Krita at this point, it will NOT start
the GUI (i.e. it looks like Krita doesn't start anymore). If Krita is killed in
the Windows Task Manager Processes tab, Krita can then be started again
normally.

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

[plasmashell] [Bug 362524] 16.04 launcher menu impossible to make 100% opaque

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk
  Component|general |general
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org
Version|unspecified |5.5.5
Product|kde |plasmashell
   Target Milestone|--- |1.0

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

[plasma4] [Bug 362498] Pass the mouse over a given odt file crashes plasma

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |plasma4
  Component|general |general
   Assignee|unassigned-b...@kde.org |plasma-b...@kde.org

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

[marble] [Bug 362495] Plamsa crash when switching from Pattern to Globe Wallpaper selection.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |marble
  Component|general |wallpaper
   Assignee|unassigned-b...@kde.org |marble-b...@kde.org

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

[dolphin] [Bug 362506] Occasional crash when browsing Owncloud-synced directory

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[QtCurve] [Bug 362523] Amarok was terminated

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
   Assignee|amarok-bugs-d...@kde.org|yyc1...@gmail.com
 CC||h...@kde.org,
   ||myr...@kde.org
  Component|general |general
 Status|UNCONFIRMED |NEEDSINFO
   Target Milestone|2.9 |---
Product|amarok  |QtCurve
Version|2.8.0   |unspecified

--- Comment #1 from Myriam Schweingruber  ---
Looks like a crash with Qtcurve, but the debugging symbols are missing. Could
you please install those and provide a new backtrace? See also
https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Kubuntu

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

[phonon-backend-vlc] [Bug 335111] vlc crashes phonon by mixing qt4 and qt5

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||decoster.tho...@gmail.com

--- Comment #62 from Christoph Feck  ---
*** Bug 362459 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 362459] Dolphin crashes when moving file to trash

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---


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

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

[dolphin] [Bug 362494] No video thumbnails/previews

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |INVALID

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

[Touchpad-KCM] [Bug 362547] Could not start ksmserver. Check your installation

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |rajeeshknamb...@gmail.com
  Component|general |daemon
Version|unspecified |5.5.5
Product|kde |Touchpad-KCM

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

[systemsettings] [Bug 362520] kwin_x11 constantly crashing

[Joe via KDE Bugzilla]

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

--- Comment #2 from Joe  ---
Note: Crashes often, not just during exit of Settings.

Additional note:  This happened when set to use OpenGL 2/3
Setting to use XRender I haven't had a repeat of the issue.

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

[user-manager] [Bug 362558] Better resize of user login avatar and/or option to resize it

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Product|systemsettings  |user-manager
  Component|general |kcontrol module
   Assignee|plasma-b...@kde.org |afies...@kde.org

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

[systemsettings] [Bug 362564] KDE crashes when appearance settings (theme) changed

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[systemsettings] [Bug 355711] System Settings crashed during exit processing.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mariana.mar...@outlook.com

--- Comment #34 from Christoph Feck  ---
*** Bug 362564 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 355711] System Settings crashed during exit processing.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||ra...@crimson.net

--- Comment #33 from Christoph Feck  ---
*** Bug 362520 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 362520] kwin_x11 constantly crashing

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[kdevelop] [Bug 362562] First time wizard must run before the other options

[patrick via KDE Bugzilla]

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

patrick  changed:

   What|Removed |Added

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

--- Comment #1 from patrick  ---
Bug fixed by commit 73e803fbb20516b95b59c475bee0cf0853123d96

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

[KScreen] [Bug 362570] Kscreen settings no longer shows display ID since 16.04 update

[jamese via KDE Bugzilla]

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

--- Comment #1 from jamese  ---
Created attachment 98741
  --> https://bugs.kde.org/attachment.cgi?id=98741=edit
Highlighting where Display ID is missing

Only way to see display ID is in the rectangular highlighted area.
Clicking the (I)nfo  icon does show the Display ID along with Manufacturer and
Model #

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

[KScreen] [Bug 362570] New: Kscreen settings no longer shows display ID since 16.04 update

[jamese via KDE Bugzilla]

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

Bug ID: 362570
   Summary: Kscreen settings no longer shows display ID since
16.04 update
   Product: KScreen
   Version: 5.5.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: se...@kde.org
  Reporter: james.el...@gmail.com

Upgraded to to Kubuntu 16.04 and the kscreen Display Configuration settings no
longer shows DP1-2 or DP1-1.  The kscreen in 15.10 did show this, it was very
useful to quickly identify screens, but it's been removed.

My screen setup has a laptop screen with 2 Displayport panels of the same
manufacturer and model - without the display ID in the panel layout it's
difficult to work out which screen is which without clicking each one and
looking in the details area below.

See upcoming screenshot for suggestion on putting display ID back in for
quicker recognition.

Occurred in whatever version shipped with Kubuntu 16.04, I'm having a go at KDE
Neon at the moment and the same thing happens.

Plasma : 5.6.3
Qt : 5.5.1
KDE : 5.21.0






Reproducible: Always

Steps to Reproduce:
1. Plug in screens
2. Go to rearrange screens
3. Can't quickly check which screen is which.


Expected Results:  
The Panel layout should show

Manufacturer
Model
Display ID (e.g HDMI1, DP1, DP1-2 etc)

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

[digikam] [Bug 362569] New: digicam-dbg package incompatible with current version of digikam.

[John via KDE Bugzilla]

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

Bug ID: 362569
   Summary: digicam-dbg package incompatible with current version
of digikam.
   Product: digikam
   Version: 4.4.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: johnne...@gmail.com

The current version of digikam-dbg available on debian jessie is
4:2.6.0-1+deb7u1.  It refuses to install because the current version of digikam
does not match.  Current version of Digikam available is 4:4.4.0-1.1

when I try to install it I get a message that says this:
digikam-dbg:
  Depends: digikam (=4:2.6.0-1+deb7u1) but 4:4.4.0-1.1 is to be installed
  Depends: showfoto (=4:2.6.0-1+deb7u1) but 4:4.4.0-1.1 is to be installed


The crash report program needs the dbg program to provide a useful crash
report.

Reproducible: Always

Steps to Reproduce:
1.using Synaptic package manager
2.try to install the digikam-dbg package
3.

Actual Results:  
The package does not install.

Expected Results:  
It should install 

Debian 8.4 (i686)
cinnamon version 2.2.16
linux kernel 3.16.0-4-686-pae
processor intel core 17-2670qm cpu @ 2.20GHz X 4
Memory 15.8 GiB

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

[kdenlive] [Bug 362230] Git master 2016-04-25: Video Stabilize issue

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #3 from Evert Vorster  ---
It works fine now, thanks for the fix.

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

[plasmashell] [Bug 361175] Right side of the panel randomly disappears for a few seconds

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #4 from Rex Dieter  ---
For me most often happens when starting or quitting an application (dolphin in
particular)

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

[kdenlive] [Bug 362568] New: The clip monitor is not showing any transitions or effects applied to it - plus two other things

[Mark via KDE Bugzilla]

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

Bug ID: 362568
   Summary: The clip monitor is not showing any transitions or
effects applied to it - plus two other things
   Product: kdenlive
   Version: 16.04.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: thinkingbeyondthesqu...@gmail.com

Any effect or transition made to the video isnt shown on the clip monitor.
Secondly clicking on the timeline to select frame position has no effect on the
clip monitor. And sometimes muting the video on the time line makes no
difference to the clip monitor either - it continues to show the same clip. If
i was to guess I would say it is looking at the clip in the Project Bin and not
the main video/timeline.

Hope this info helps improve kdenlive as atm it is unusable for me (and ive
used it alot over the years).

Cheers

Mark

Reproducible: Always

Steps to Reproduce:
1.import any video
2. drop video to timeline
3.apply any effect to it
4.hit play on clip monitor - effect is not shown (though does render if i
render the timeline)

Actual Results:  
the clip monitor is not showing applied effects

Expected Results:  
shown the applied effects/transitions

I installed the latest kdenlive software on the chance that the latest dev
version may have fixed the issue, (i was using the latest on Ubuntu 16.04 but
it too was failing - from memory i think it was something like 15.5.4 -
whatever is the current state of kdenlive in ubuntu 16.04 repo)

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

[calligracommon] [Bug 260482] when using a stylus, 2nd and 3rd buttons act as 1st button

[Marcelo Sales via KDE Bugzilla]

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

--- Comment #2 from Marcelo Sales  ---
I'm experiencing this problem right now using Kubuntu packages. I'm running
Kubuntu 14.04.04, with the KDE Backports PPA. KDE version is 4.14.13. My tablet
is a Intuos Pro Small (PTH-451).
The strange thing is that I run the same KDE version on another computer, a
notebook, and everything works fine there, with the very same tablet. Also, I
was running Kubuntu 14.10 on the problematic computer before downgrading to
14.04.04 (fresh install), and the stylus buttons were working fine then too.
If I uninstall the xserver-xorg-input-wacom package, the tablet is not detect
as a tablet (as expected), but I still can use it as a mouse and the stylus
buttons work fine (as middle and right buttons). However, with this package
installed, the tablet is detected correctly and all of its functions are
available, including the Input Devices settings in KDE System Settings, except
for the stylus buttons, which always work as left clicks, no matter what I set
them up to do in System Settings.
It looks like a configuration problem, rather than a bug, but I have no idea
how to fix this...

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

[kwin] [Bug 362567] New: Grade das áreas de trabalho

[Erick Rijo Jr via KDE Bugzilla]

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

Bug ID: 362567
   Summary: Grade das áreas de trabalho
   Product: kwin
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: erick.soluci...@gmail.com

Application: kwin_x11 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
Quando eu aciono a Grade de áreas de trabalho o Plasma, eventualmente para,
bordas das janelas, animações do KWin... em fim... tudo para.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f78e046a900 (LWP 2033))]

Thread 8 (Thread 0x7f78c184b700 (LWP 2050)):
#0  0x7ffde8820caf in clock_gettime ()
#1  0x7f78dff7dfb6 in __GI___clock_gettime (clock_id=1,
tp=tp@entry=0x7f78c184aa60) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f78de5e7c16 in qt_clock_gettime (ts=0x7f78c184aa60, clock=) at tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#5  0x7f78de76c529 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f78b4001118) at kernel/qtimerinfo_unix.cpp:84
#6  0x7f78de76b90b in QEventDispatcherUNIXPrivate::doSelect
(this=this@entry=0x7f78b40008e0, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:171
#7  0x7f78de76c13e in QEventDispatcherUNIX::processEvents
(this=0x7f78b40008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#8  0x7f78de715dea in QEventLoop::exec (this=this@entry=0x7f78c184aca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#9  0x7f78de5328a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#10 0x7f78d90483c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f78de53784e in QThreadPrivate::start (arg=0x1235600) at
thread/qthread_unix.cpp:331
#12 0x7f78d9eeb6fa in start_thread (arg=0x7f78c184b700) at
pthread_create.c:333
#13 0x7f78dff6fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f78b8c14700 (LWP 2071)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f78dd6bfbd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f78dd6bfc19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f78d9eeb6fa in start_thread (arg=0x7f78b8c14700) at
pthread_create.c:333
#4  0x7f78dff6fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f782c51a700 (LWP 4471)):
#0  0x7ffde8820caf in clock_gettime ()
#1  0x7f78dff7dfb6 in __GI___clock_gettime (clock_id=1,
tp=tp@entry=0x7f782c519b60) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f78de5e7c16 in qt_clock_gettime (ts=0x7f782c519b60, clock=) at tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#5  0x7f78de76c529 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f78240f20a8) at kernel/qtimerinfo_unix.cpp:84
#6  0x7f78de76ca95 in QTimerInfoList::timerWait
(this=this@entry=0x7f78240f20a8, tm=...) at kernel/qtimerinfo_unix.cpp:381
#7  0x7f78de76c080 in QEventDispatcherUNIX::processEvents
(this=0x7f78240817c0, flags=...) at kernel/qeventdispatcher_unix.cpp:594
#8  0x7f78de715dea in QEventLoop::exec (this=this@entry=0x7f782c519ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#9  0x7f78de5328a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#10 0x7f78d90483c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f78de53784e in QThreadPrivate::start (arg=0x17a5760) at
thread/qthread_unix.cpp:331
#12 0x7f78d9eeb6fa in start_thread (arg=0x7f782c51a700) at
pthread_create.c:333
#13 0x7f78dff6fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f78b9c07700 (LWP 4781)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f78de538aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x17b28c0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x1be7200,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f78d952f92e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f78d95301b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f78de53784e in QThreadPrivate::start (arg=0x1be7180) at
thread/qthread_unix.cpp:331
#6  0x7f78d9eeb6fa in start_thread 

[Baloo] [Bug 362566] New: Random crash while maximizing openbox

[via KDE Bugzilla]

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

Bug ID: 362566
   Summary: Random crash while maximizing openbox
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: jwoj...@charter.net
CC: pinak.ah...@gmail.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
Maximizing on KDE a session of Openbox running Windows 8.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f11d63a48c0 (LWP 2102))]

Thread 2 (Thread 0x7f108b2f0700 (LWP 2960)):
#0  0x7f11d44b0e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f11d168131c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f11d168142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f11d50e6a9b in QEventDispatcherGlib::processEvents
(this=0x7f10840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f11d508ddea in QEventLoop::exec (this=this@entry=0x7f108b2efbc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00420cd8 in Baloo::FileContentIndexer::run (this=0x1f8ac40) at
../../../src/file/filecontentindexer.cpp:71
#6  0x7f11d4eac343 in QThreadPoolThread::run (this=0x1fe5700) at
thread/qthreadpool.cpp:93
#7  0x7f11d4eaf84e in QThreadPrivate::start (arg=0x1fe5700) at
thread/qthread_unix.cpp:331
#8  0x7f11d3b136fa in start_thread (arg=0x7f108b2f0700) at
pthread_create.c:333
#9  0x7f11d44bcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f11d63a48c0 (LWP 2102)):
[KCrash Handler]
#6  Baloo::getVarint32Ptr (value=0x7ffe5f074124, limit=0x7f108bde9f86 "\b",
p=0x0) at ../../../src/codecs/coding.h:120
#7  Baloo::getDifferentialVarInt32 (p=0x0, p@entry=0x7f108bde9f86 "\b",
limit=limit@entry=0x7f108bde9f86 "\b", values=values@entry=0x7ffe5f074188) at
../../../src/codecs/coding.cpp:158
#8  0x7f11d55996b5 in Baloo::PositionCodec::decode
(this=this@entry=0x7ffe5f0741ef, arr=...) at
../../../src/codecs/positioncodec.cpp:55
#9  0x7f11d5583fb4 in Baloo::PositionDB::get
(this=this@entry=0x7ffe5f0742e0, term=...) at
../../../src/engine/positiondb.cpp:101
#10 0x7f11d55969a4 in Baloo::WriteTransaction::commit (this=) at ../../../src/engine/writetransaction.cpp:299
#11 0x7f11d558e032 in Baloo::Transaction::commit
(this=this@entry=0x7ffe5f074370) at ../../../src/engine/transaction.cpp:262
#12 0x0042a02b in Baloo::MetadataMover::moveFileMetadata
(this=0x1fcc2c0, from=..., to=...) at ../../../src/file/metadatamover.cpp:58
#13 0x7f11d50bee4f in QtPrivate::QSlotObjectBase::call (a=0x7ffe5f0744d0,
r=0x7ffe5f074b90, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#14 QMetaObject::activate (sender=sender@entry=0x1faa090,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffe5f0744d0) at kernel/qobject.cpp:3698
#15 0x7f11d50bf7d7 in QMetaObject::activate (sender=sender@entry=0x1faa090,
m=m@entry=0x644cc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffe5f0744d0)
at kernel/qobject.cpp:3578
#16 0x0042aaba in KInotify::moved (this=this@entry=0x1faa090, _t1=...,
_t2=...) at ./moc_kinotify.cpp:330
#17 0x0042cbff in KInotify::slotEvent (this=,
socket=) at ../../../src/file/kinotify.cpp:421
#18 0x7f11d50bee4f in QtPrivate::QSlotObjectBase::call (a=0x7ffe5f074760,
r=0x1faa090, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#19 QMetaObject::activate (sender=sender@entry=0x1fb66c0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffe5f074760) at kernel/qobject.cpp:3698
#20 0x7f11d50bf7d7 in QMetaObject::activate (sender=sender@entry=0x1fb66c0,
m=m@entry=0x7f11d52d9780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe5f074760)
at kernel/qobject.cpp:3578
#21 0x7f11d513e51e in QSocketNotifier::activated
(this=this@entry=0x1fb66c0, _t1=13) at .moc/moc_qsocketnotifier.cpp:134
#22 0x7f11d50cb47b in QSocketNotifier::event (this=0x1fb66c0, e=) at kernel/qsocketnotifier.cpp:260
#23 0x7f11d509060c in QCoreApplication::notify (event=0x7ffe5f074820,
receiver=0x1fb66c0, this=0x7ffe5f074af0) at kernel/qcoreapplication.cpp:1038
#24 QCoreApplication::notifyInternal (this=0x7ffe5f074af0, receiver=0x1fb66c0,
event=event@entry=0x7ffe5f074820) at kernel/qcoreapplication.cpp:965
#25 0x7f11d50e6f45 in QCoreApplication::sendEvent 

[parley] [Bug 362565] "conjugations" training mode gives error message

[Juergen via KDE Bugzilla]

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

--- Comment #1 from Juergen  ---
Created attachment 98740
  --> https://bugs.kde.org/attachment.cgi?id=98740=edit
one verb test file

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

[parley] [Bug 362565] New: "conjugations" training mode gives error message

[Juergen via KDE Bugzilla]

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

Bug ID: 362565
   Summary: "conjugations" training mode gives error message
   Product: parley
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: b4tas...@auroville.org.in

I am trying to use parley practice in the "conjugations" mode but I always get
the error following error:
The vocabulary document contains no entries that can be used for the chosen
type of practice.

I tried to troubleshoot the problem and created a new unit with only one verb
in it and entered the right conjugation form for the present tense Spanish.

Then I tried it again but I am still getting the same error. I am not sure
what/if I am doing something wrong. Is anyone using that mode in parley? Any
insights or hints would be greatly appreciated.
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
parley version 4:15.12.3-0ubuntu1

I am using Parley several years now and I never got the conjugation training
working. I always get this error. Find the one verb file attached.
Thank you! 



Reproducible: Always

Steps to Reproduce:
1. got to training mode
2. choose conjugations
3.

Actual Results:  
Error: The vocabulary document contains no entries that can be used for the
chosen type of practice.


Expected Results:  
I can learn conjugations

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

[kdevplatform] [Bug 362545] Project Manager View plugin has hardcoded/fixed shortcuts

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org

--- Comment #2 from Aleix Pol  ---
Can you please submit the patch to reviewboard or phabricator? it's easier to
discuss there.

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

[kalgebra] [Bug 362507] Factorial(13) does not return correct results, factorial(12) is correct.

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #4 from Aleix Pol  ---
That's a technology limitation. You're hitting the precision limit c++ double
has.

Maybe we should adopt a multi precision library.

What's your use case?

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

[kalgebra] [Bug 362507] Factorial(13) does not return correct results, factorial(12) is correct.

[Aleix Pol via KDE Bugzilla]

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

--- Comment #3 from Aleix Pol  ---
Git commit 5c4ff0778bead3e80299b58dae43c32b7b1f6d8c by Aleix Pol.
Committed on 01/05/2016 at 22:51.
Pushed by apol into branch 'master'.

Use cmath implementation for factorial

M  +3-8analitza/operations.cpp
M  +3-0analitza/tests/analitzatest.cpp

http://commits.kde.org/analitza/5c4ff0778bead3e80299b58dae43c32b7b1f6d8c

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

[kdenlive] [Bug 362230] Git master 2016-04-25: Video Stabilize issue

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Should be fixed now, please test

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

[kdenlive] [Bug 362532] vidstab on 1080p50 footage results in p25 mlt file which cannot be used/loaded

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 566982b06c48ae8e5220a939bca46ea0ef3cc2c3 by Jean-Baptiste Mardelle.
Committed on 01/05/2016 at 22:32.
Pushed by mardelle into branch 'Applications/16.04'.

Fix vidstab filter

M  +14   -9src/project/jobs/meltjob.cpp

http://commits.kde.org/kdenlive/566982b06c48ae8e5220a939bca46ea0ef3cc2c3

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

[okular] [Bug 329704] Okular is unable to display a printed manual page.

[Albert Astals Cid via KDE Bugzilla]

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

--- Comment #12 from Albert Astals Cid  ---
There's nothing we can do if CUPS breaks.

Regarding 

> I could not find anything related against 9.07 ...

A quick search for "ghostscript 9.07 locale bug" in google gives me
http://bugs.ghostscript.com/show_bug.cgi?id=693843

So yeah, thanks for not trusting my word and making me lose 5 minutes of my
live.

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

[okular] [Bug 329704] Okular is unable to display a printed manual page.

[cheesus via KDE Bugzilla]

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

--- Comment #11 from cheesus  ---
Yes you are right, the messages are from a (failed) print preview.
Printing just stalls in CUPS.

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

[plasmashell] [Bug 362123] Plasmashell crashes after upgrade from Kubuntu 15.10 to 16.04

[Gary Triplett via KDE Bugzilla]

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

--- Comment #4 from Gary Triplett  ---
(In reply to Gary Triplett from comment #3)
> I purged the Nvidia kernel module rebooted the system and now have a
> 1024x768 resolution.  I reinstalled several different release versions of
> NVidia and get the original black screen plasmashell error results.
> Running the KDE Driver Manager, it just stalls at "Collecting information
> about your system".
> It seems as if the system is now unable to recognize the NVidia card as
> being present.
--
Output of lspci:

00:00.0 Host bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 (rev
02)
00:01.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express
Root Port 1 (rev 02)
00:01.1 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express
Root Port 1 (rev 02)
00:02.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express
Root Port 2 (rev 02)
00:02.2 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express
Root Port 2 (rev 02)
00:03.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express
Root Port 3 (rev 02)
00:05.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Address Map, VTd_Misc, System Management (rev 02)
00:05.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Hot
Plug (rev 02)
00:05.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 RAS,
Control Status and Global Errors (rev 02)
00:05.4 PIC: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC (rev 02)
00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR
(rev 05)
00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA
Controller [AHCI mode] (rev 05)
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host
Controller (rev 05)
00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI
Controller #1 (rev 05)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V
(rev 05)
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced
Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio
Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root
Port #1 (rev d5)
00:1c.3 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root
Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root
Port #5 (rev d5)
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced
Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller
(rev 05)
00:1f.2 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev
05)
00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev
05)
01:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450]
(rev a1)
01:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio Controller
(rev a1)
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
Connection
07:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless
Network Adapter (rev 03)
08:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host
Controller
ff:0b.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3
QPI Link 0 & 1 Monitoring (rev 02)
ff:0b.1 Performance counters: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
R3 QPI Link 0 & 1 Monitoring (rev 02)
ff:0b.2 Performance counters: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
R3 QPI Link 0 & 1 Monitoring (rev 02)
ff:0c.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Unicast Registers (rev 02)
ff:0c.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Unicast Registers (rev 02)
ff:0c.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Unicast Registers (rev 02)
ff:0c.3 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Unicast Registers (rev 02)
ff:0c.4 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Unicast Registers (rev 02)
ff:0c.5 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Unicast Registers (rev 02)
ff:0f.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Buffered Ring Agent (rev 02)
ff:0f.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
Buffered Ring Agent (rev 02)
ff:0f.4 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
System Address Decoder & Broadcast Registers (rev 02)
ff:0f.5 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
System Address Decoder & Broadcast Registers (rev 02)
ff:0f.6 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7
System Address Decoder & Broadcast Registers (rev 02)
ff:10.0 System peripheral: Intel Corporation Xeon 

[okular] [Bug 362446] Okular crashed wen open document with cyrillic characterset

[Albert Astals Cid via KDE Bugzilla]

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

--- Comment #4 from Albert Astals Cid  ---
What's the poppler version on the system that you say it works?

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

[plasmashell] [Bug 362536] Setting 'no icons on buttons' is not taken into account

[via KDE Bugzilla]

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

--- Comment #1 from slartibar...@gmail.com ---
it's not necessary to use cinnamon-DE, 
it is sufficient to switch over from 'breeze' widget style to 'gtk+ style' in
systemsettings5 / application style / widget style menu while being in
plasmashell5

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

[plasmashell] [Bug 362123] Plasmashell crashes after upgrade from Kubuntu 15.10 to 16.04

[via KDE Bugzilla]

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

--- Comment #3 from garystripl...@yahoo.com ---
I purged the Nvidia kernel module rebooted the system and now have a 1024x768
resolution.  I reinstalled several different release versions of NVidia and get
the original black screen plasmashell error results.
Running the KDE Driver Manager, it just stalls at "Collecting information about
your system".
It seems as if the system is now unable to recognize the NVidia card as being
present.

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

[plasmashell] [Bug 362548] Krusader display problem when renaming files running in gtk styling

[via KDE Bugzilla]

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

--- Comment #2 from slartibar...@gmail.com ---
it's not necessary to use cinnamon-DE, 
it is sufficient to switch over from 'breeze' widget style to 'gtk+ style' in
systemsettings5 / application style / widget style menu.

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

[plasmashell] [Bug 362548] Krusader display problem when renaming files running in gtk styling

[via KDE Bugzilla]

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

slartibar...@gmail.com changed:

   What|Removed |Added

Summary|Krusader display problem|Krusader display problem
   |when renaming files running |when renaming files running
   |in cinnamon-DE  |in gtk styling

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

[kate] [Bug 362402] saves new files in wrong location when called from commandline.

[Mark van Rossum via KDE Bugzilla]

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

--- Comment #1 from Mark van Rossum  ---
PS  I think there is something also wrong with the locations in the 'Open
Recent' list.

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

[kdenlive] [Bug 362532] vidstab on 1080p50 footage results in p25 mlt file which cannot be used/loaded

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||j...@kdenlive.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Jean-Baptiste Mardelle  ---
Thanks for your report. I am working on it.

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

[kdenlive] [Bug 362532] vidstab on 1080p50 footage results in p25 mlt file which cannot be used/loaded

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

   Assignee|vpi...@kde.org  |j...@kdenlive.org

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

[kwin] [Bug 362208] Screen blinking after leaving full screen app (mpv)

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #7 from Thomas Lübking  ---


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

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

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||mmboss...@gmail.com

--- Comment #64 from Thomas Lübking  ---
*** Bug 362208 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 362496] KWin crashed when unifying outputs

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #3 from Thomas Lübking  ---
No problem - just to ensure it fits the pattern (resp. doesn't extend it)

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

[krita] [Bug 362487] [Huion 610] Cursor is misaligned with brush/tools

[via KDE Bugzilla]

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

--- Comment #2 from zeuse...@gmail.com ---
Created attachment 98739
  --> https://bugs.kde.org/attachment.cgi?id=98739=edit
tablet log

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

[systemsettings] [Bug 362564] New: KDE crashes when appearance settings (theme) changed

[Mariana via KDE Bugzilla]

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

Bug ID: 362564
   Summary: KDE crashes when appearance settings (theme) changed
   Product: systemsettings
   Version: 5.5.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mariana.mar...@outlook.com

Application: systemsettings5 (5.5.5)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: i changed from previous
selected theme Oxigen to another and then back to Oxigen, this because no
network connexions were shown after upgrade to 16.04 and restart.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f62a057a8c0 (LWP 2190))]

Thread 6 (Thread 0x7f628ec41700 (LWP 2191)):
#0  0x7f629cc9fe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f629a987c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f629a9898d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6290f93629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f629d39584e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f629a1116fa in start_thread (arg=0x7f628ec41700) at
pthread_create.c:333
#6  0x7f629ccabb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f6276134700 (LWP 2923)):
#0  0x7ffe1cbfdba4 in clock_gettime ()
#1  0x7f629ccb9fb6 in __GI___clock_gettime (clock_id=1, tp=0x7f6276133a70)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f629d445c16 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f629d5ca529 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f629d5caa95 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f629d5cbe7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6299bef8ad in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f6299bf024b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f6299bf042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f629d5cca9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f629d573dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f629d3908a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f629d39584e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f629a1116fa in start_thread (arg=0x7f6276134700) at
pthread_create.c:333
#14 0x7f629ccabb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f6275933700 (LWP 2955)):
#0  0x7f6299bed3c4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6299befc7a in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6299bf02c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6299bf042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f629d5cca9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f629d573dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f629d3908a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f629bd0f3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f629d39584e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f629a1116fa in start_thread (arg=0x7f6275933700) at
pthread_create.c:333
#10 0x7f629ccabb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f626d01e700 (LWP 2972)):
#0  0x7f629cc9fe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6299bf031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6299bf042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f629d5cca9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f629d573dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f629d3908a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f629bd0f3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f629d39584e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f629a1116fa in start_thread 

[phonon-backend-gstreamer] [Bug 362468] With Gstreamer backend, playback stops when encountering broken or missing files

[via KDE Bugzilla]

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

--- Comment #2 from tamius@gmail.com ---
I'll check if the bug was filled with the backend, then. 

(Gstreamer version is 4.9.0)

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

[trojita] [Bug 362551] Some fixes in CMakeLists.txt that prevent a FTBFS

[Alf Gaida via KDE Bugzilla]

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

--- Comment #7 from Alf Gaida  ---
ok, i'm fine with, no big deal. And thanks again for pointing me into the right
direction - false ownership in the source dir preventing correct updates - so
trivial i overlooked it for a month.

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

[krdc] [Bug 333681] krdc mount only /media shared dir

[via KDE Bugzilla]

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

--- Comment #11 from hrvo...@jankovci.net ---
Well, it seems I have the latest version. This is what I get in Kubuntu 16.04:

user@probook:~$ man xfreerdp | grep version
   /version
user@probook:~$ xfreerdp /version
This is FreeRDP version 2.0.0-dev (git n/a)

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

[Akonadi] [Bug 361157] Akonadi does not work properly after Update to KDE FW 5.20, Plasma 5.6 and Qt5.6 on Opensuse Leap 42.1

[Erick Osorio via KDE Bugzilla]

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

--- Comment #13 from Erick Osorio  ---
I have this bug too... I installed:

openSUSE Leap.
Qt 5.6
Plasma 5.6.3
KDE apps 16.04
Kmail 5.2

This bug isn't fixed...

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

[kdevelop] [Bug 362563] New: Plugin crashes when shutting down

[patrick via KDE Bugzilla]

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

Bug ID: 362563
   Summary: Plugin crashes when shutting down
   Product: kdevelop
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Embedded systems support
  Assignee: patrickelect...@gmail.com
  Reporter: patrickelect...@gmail.com
CC: m...@svenbrauch.de

Plugin crashes when shutting down app

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

[kdevelop] [Bug 278482] KDevelop treats signed and unsigned chars as ints when used as template parameters

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.0
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Kevin Funk  ---
Fixed in KDevelop 5, indeed.

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

[calligracommon] [Bug 260482] when using a stylus, 2nd and 3rd buttons act as 1st button

[Marcelo Sales via KDE Bugzilla]

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

Marcelo Sales  changed:

   What|Removed |Added

 CC||mmtsa...@gmail.com

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

[kdevelop] [Bug 362562] New: First time wizard must run before the other options

[patrick via KDE Bugzilla]

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

Bug ID: 362562
   Summary: First time wizard must run before the other options
   Product: kdevelop
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Embedded systems support
  Assignee: patrickelect...@gmail.com
  Reporter: patrickelect...@gmail.com
CC: m...@svenbrauch.de

Plugin must be configured with first time wizard before running other options

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

[krita] [Bug 362561] Double click before to paint in Dell touch monitor

[via KDE Bugzilla]

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

daarant...@gmail.com changed:

   What|Removed |Added

 OS|MS Windows  |Windows CE

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

[krita] [Bug 362561] New: Double click before to paint in Dell touch monitor

[via KDE Bugzilla]

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

Bug ID: 362561
   Summary: Double click before to paint in Dell touch monitor
   Product: krita
   Version: 2.9.11
  Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: daarant...@gmail.com

Wenn I change the color, brush, opacity, etc.. and the wants to paint in the
canvas I have to touch one time before to paint. With the mouse it's OK

Reproducible: Always



Expected Results:  
I think it should be able to paint directly on canvas.

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

[plasmashell] [Bug 362560] New: gwenview fullscreen mode hangs when running in cinnamon-DE

[via KDE Bugzilla]

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

Bug ID: 362560
   Summary: gwenview fullscreen mode hangs when running in
cinnamon-DE
   Product: plasmashell
   Version: 5.6.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Open any image in gwenview, zooming, browsing and the like is all functional.
Now, press F11 or select fullscreen-mode when an image is on the display
Gwenview just hangs, no possibility to interact with it. Force killing is
necessary.
This behaviour is independent of the animation settings (e.g.
openGL/software/none)


Reproducible: Always

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

[kdevelop] [Bug 278482] KDevelop treats signed and unsigned chars as ints when used as template parameters

[chaitanya srinivas ponnapalli via KDE Bugzilla]

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

--- Comment #2 from chaitanya srinivas ponnapalli 
 ---
Created attachment 98738
  --> https://bugs.kde.org/attachment.cgi?id=98738=edit
Signed char used as template

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

[kdevelop] [Bug 278482] KDevelop treats signed and unsigned chars as ints when used as template parameters

[chaitanya srinivas ponnapalli via KDE Bugzilla]

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

chaitanya srinivas ponnapalli  changed:

   What|Removed |Added

 CC||cponnapalli@mail.csuchico.e
   ||du

--- Comment #1 from chaitanya srinivas ponnapalli 
 ---
Created attachment 98737
  --> https://bugs.kde.org/attachment.cgi?id=98737=edit
unsigned char when used as template

Reproduced the above steps:
1. Executed the code given.
2. Kdevelop does not treat the signed char type as signed int.
3. Similarly, unsigned char is not treated as unsigned int.
4. Attached the screen shots containing the code executed.

In accordance to the statement in expected result:

A char is both a character representation, but for the purposes of converting
to an int, it's also a int representation. A simple char is used to store
simple characters. However, if you are using character types as numbers then
use signed char(-127 t0 +127 range) and unsigned char(0 t0 255.)

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

[kate] [Bug 362288] Kate treats remote filesystems as locally mounted

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #7 from Dominik Haumann  ---
Possible fix, see review request https://git.reviewboard.kde.org/r/127805/

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

[kmail2] [Bug 362559] New: Regression since 5.0.2: Dragging addresses from kaddressbook to new message fails

[Gunter Ohrner via KDE Bugzilla]

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

Bug ID: 362559
   Summary: Regression since 5.0.2: Dragging addresses from
kaddressbook to new message fails
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@customcdrom.de

Dragging an address book entry from kAddressbook to kMail fails with following
message box:

> Interner Fehler
> Bitte senden Sie einen ausführlichen Problembericht an http://bugs.kde.org
> Akonadi::Exception: No remote identifier specified

This still worked before with kMail 5.0.2.

kMail Version 5.1.3
KDE Frameworks 5.18.0
Qt 5.5.1 (kompiliert gegen 5.5.1)
Das xcb Fenstersystem

kAddressbook Version 5.1.3
KDE Frameworks 5.18.0
Qt 5.5.1 (kompiliert gegen 5.5.1)
Das xcb Fenstersystem


Reproducible: Always

Steps to Reproduce:
1. Drag a kAddressbook entry from its entry list into a (plain text) editor
window in kmail.
2. A menu will appear asking if it should insert the address (URL) to the
message or the file as an attachment. Select "attach".

Actual Results:  
The failure message box will appear and nothing will be attached to the
message.

Expected Results:  
The vcard should be attached to the message, as it did in kMail 5.0.2 and
before.

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

[kmail2] [Bug 78629] MS Exchange mail support

[Krzysztof Nowicki via KDE Bugzilla]

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

--- Comment #48 from Krzysztof Nowicki  ---
Almost 6 months ago I have started the effort to bring native Exchange support
to Akonadi using the Exchange Web Services (EWS) protocol, which has become the
primary standard used to communicate with Exchange (Microsoft Outlook uses it
by default).

Today I have published an initial release with full e-mail support and partial
support for other items.

If you're interested in doing some testing please check the project website on
GitHub:

https://github.com/KrissN/akonadi-ews

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

[kmail2] [Bug 362280] KMail replaces addresses in the header by "Me"

[Alex6 via KDE Bugzilla]

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

Alex6  changed:

   What|Removed |Added

 CC||alex.pre...@laposte.net

--- Comment #2 from Alex6  ---
Same here  (5.2.0)
I know a (important) man called "ego", but no "Me"...
Worse: this thing is written in answers, quotations, forwardings... no more
aliases, only "Me"!!!

Please make that new "feature" optional!

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

[frameworks-baloo] [Bug 357300] plasmashell crash - mdb_env_pick_meta (env=0x7f634c178970) at mdb.c:3709

[via KDE Bugzilla]

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

--- Comment #6 from andreas.sturmlech...@gmail.com ---
Yes, it just crashed again after typing a few characters into krunner. The fun
bit here is that file search is disabled.

Current versions:
Qt-5.5.1
Frameworks 5.21
Plasma 5.6.3

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[David Roberts via KDE Bugzilla]

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

David Roberts  changed:

   What|Removed |Added

 CC||robe...@tellink.net

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

[systemsettings] [Bug 362558] New: Better resize of user login avatar and/or option to resize it

[Luca Mastromatteo via KDE Bugzilla]

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

Bug ID: 362558
   Summary: Better resize of user login avatar and/or option to
resize it
   Product: systemsettings
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: lukycroci...@gmail.com

The usual manner of adding an avatar for users on the PC, makes the result
avatar image very ugly. There is the need everytime to resize it manually using
GIMP or other programs.

There should be a better system to resize the image correctly, making it less
pixelated, or implement builtin resize/crop system, something like that is
already implemented in GNOME.

Reproducible: Always

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

[plasmashell] [Bug 362557] New: Plasma chrashed after changing my gpu

[bogdan via KDE Bugzilla]

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

Bug ID: 362557
   Summary: Plasma  chrashed after changing my gpu
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bogdan.pet...@outlook.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I Was just apply the changes to use the nvidia graphics card instead of the
intel one then The Plasma Chrashed and rebooted

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f89b6c728c0 (LWP 16096))]

Thread 11 (Thread 0x7f89a2d4d700 (LWP 16098)):
#0  0x7f89b137de8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f89b5442c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f89b54448d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f89a54cd629 in QXcbEventReader::run (this=0x170f9b0) at
qxcbconnection.cpp:1253
#4  0x7f89b1a7384e in QThreadPrivate::start (arg=0x170f9b0) at
thread/qthread_unix.cpp:331
#5  0x7f89b0b606fa in start_thread (arg=0x7f89a2d4d700) at
pthread_create.c:333
#6  0x7f89b1389b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f899bfff700 (LWP 16102)):
#0  0x7f89b137de8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f89ae11331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f89ae11342c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f89b1caaa9b in QEventDispatcherGlib::processEvents
(this=0x7f89940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f89b1c51dea in QEventLoop::exec (this=this@entry=0x7f899bffece0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f89b1a6e8a4 in QThread::exec (this=this@entry=0x17dc890) at
thread/qthread.cpp:503
#6  0x7f89b43163c5 in QQmlThreadPrivate::run (this=0x17dc890) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f89b1a7384e in QThreadPrivate::start (arg=0x17dc890) at
thread/qthread_unix.cpp:331
#8  0x7f89b0b606fa in start_thread (arg=0x7f899bfff700) at
pthread_create.c:333
#9  0x7f89b1389b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f898f6c3700 (LWP 16118)):
#0  0x7f89ae157a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f89ae1132d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f89ae11342c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f89b1caaa9b in QEventDispatcherGlib::processEvents
(this=0x7f89880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f89b1c51dea in QEventLoop::exec (this=this@entry=0x7f898f6c2ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f89b1a6e8a4 in QThread::exec (this=this@entry=0x1aef210) at
thread/qthread.cpp:503
#6  0x7f89b43163c5 in QQmlThreadPrivate::run (this=0x1aef210) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f89b1a7384e in QThreadPrivate::start (arg=0x1aef210) at
thread/qthread_unix.cpp:331
#8  0x7f89b0b606fa in start_thread (arg=0x7f898f6c3700) at
pthread_create.c:333
#9  0x7f89b1389b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f898d818700 (LWP 16159)):
#0  0x7f89b137de8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f89ae11331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f89ae11342c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f89b1caaa9b in QEventDispatcherGlib::processEvents
(this=0x7f8988c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f89b1c51dea in QEventLoop::exec (this=this@entry=0x7f898d817ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f89b1a6e8a4 in QThread::exec (this=this@entry=0x1d0dbe0) at
thread/qthread.cpp:503
#6  0x7f89b43163c5 in QQmlThreadPrivate::run (this=0x1d0dbe0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f89b1a7384e in QThreadPrivate::start (arg=0x1d0dbe0) at
thread/qthread_unix.cpp:331
#8  0x7f89b0b606fa in start_thread (arg=0x7f898d818700) at
pthread_create.c:333
#9  0x7f89b1389b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f8987df7700 (LWP 16217)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f89b66bbbd4 in ?? () from

[plasmashell] [Bug 362556] Right click on legacy GTK tray icons does not work.

[Luca Mastromatteo via KDE Bugzilla]

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

Luca Mastromatteo  changed:

   What|Removed |Added

Summary|Right click on tray icon|Right click on legacy GTK
   |does not work.  |tray icons does not work.

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

[plasmashell] [Bug 362556] New: Right click on tray icon does not work.

[Luca Mastromatteo via KDE Bugzilla]

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

Bug ID: 362556
   Summary: Right click on tray icon does not work.
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: lukycroci...@gmail.com

Right clicking on the legacy GTK icons, in the icon tray, nothing happens. 

Reproducible: Always

Steps to Reproduce:
1. Have a GTK program which uses GTK legacy icon trays. (Like Pamac, or
redshift)
2.
3.

Actual Results:  
Nothing happens.

Expected Results:  
After right clicking on them, there should be a dropdown menu.

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

[Spectacle] [Bug 356831] cannot send image to clipboard in background mode

[GreggJS via KDE Bugzilla]

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

--- Comment #16 from GreggJS  ---
(In reply to Pastafarianist from comment #14)
> If you wish to have this option, Shutter is a good alternative. It sits in
> background (there is a tray icon) and thus works around the issue Boudhayan
> Gupta has described.

Thanks for the suggestion. I'll have a look.

Cheers,
Gregg

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

[Spectacle] [Bug 356831] cannot send image to clipboard in background mode

[GreggJS via KDE Bugzilla]

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

--- Comment #15 from GreggJS  ---
(In reply to Boudhayan Gupta from comment #13)
> This feature will always be broken, I'm afraid. There's nothing I can do
> about this - this is a limitation of X11. Maybe we'll revisit this in the
> Wayland era.
> 
> You do know you can just drag the image preview to your e-mail client /
> browser, right?

I did notice that before posting my comment. But that requires me to go back
through the files to preview or view to figure out what's what before dragging
and dropping instead of just taking the screenshot and pasting it where I want
it. One extra step for each screenshot (which I have to take lots of) just adds
up to inefficient way of doing things. I'm trying to adjust the way I do things
and maybe put all similar like files into subfolders - this way I can at least
do as you say with a clean pictures folder. Anyhow, still like the tool
(thanks!), love linux, and appreciate your comment. 

Cheers,
Gregg

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

[trojita] [Bug 362551] Some fixes in CMakeLists.txt that prevent a FTBFS

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #6 from Jan Kundrát  ---
Hi Alf, if there's a path about which various distributions agree that we could
use for these bits, I'm all for using that. However, last time I had this
conversation nobody offered any location. Using something like libexec/trojita
would require some RPATH hacking which seems quite fishy to me -- and the
distro guys agreed rather than saying "oh screw it, everybody does it that
way".

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

[kalarm] [Bug 362508] freeze

[felipe . facundes via KDE Bugzilla]

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

felipe.facundes  changed:

   What|Removed |Added

 CC||felipe.facun...@gmail.com

--- Comment #4 from felipe.facundes  ---
Created attachment 98736
  --> https://bugs.kde.org/attachment.cgi?id=98736=edit
freeze kmenu. opening kalarm

linux distribution: ArchLinux

Kalarm version 2.11.5-5ak

Plasma version 5.6.3

Kde framework 5.21.0


He froze for just open the kmenu and start kalarm



This also happens when I start kalarm in KRunner

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

[kalarm] [Bug 362508] freeze

[felipe . facundes via KDE Bugzilla]

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

--- Comment #3 from felipe.facundes  ---
linux distribution: ArchLinux

Kalarm version 2.11.5-5ak

Plasma version 5.6.3

Kde framework 5.21.0


He froze for just open the kmenu and start kalarm



This also happens when I start kalarm in KRunner

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

[kalarm] [Bug 362555] New: He froze for just open the kmenu and start kalarm

[felipe . facundes via KDE Bugzilla]

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

Bug ID: 362555
   Summary: He froze for just open the kmenu and start kalarm
   Product: kalarm
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Akonadi
  Assignee: djar...@kde.org
  Reporter: felipe.facun...@gmail.com

linux distribution: ArchLinux

Kalarm version 2.11.5-5ak

Plasma version 5.6.3

Kde framework 5.21.0


He froze for just open the kmenu and start kalarm



This also happens when I start kalarm in KRunner

Reproducible: Always

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

[plasmashell] [Bug 336079] plasmashell desktop crash with kactivitymanager segfault message libQtCore

[via KDE Bugzilla]

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

esi...@gmail.com changed:

   What|Removed |Added

 CC||esi...@gmail.com

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

[plasmashell] [Bug 358321] plasma crash while switchinig tasks

[via KDE Bugzilla]

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

esi...@gmail.com changed:

   What|Removed |Added

 CC||esi...@gmail.com

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

[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout

[via KDE Bugzilla]

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

esi...@gmail.com changed:

   What|Removed |Added

 CC||esi...@gmail.com

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

[kactivitymanagerd] [Bug 351985] kactivitymanage segfault

[via KDE Bugzilla]

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

esi...@gmail.com changed:

   What|Removed |Added

 CC||esi...@gmail.com

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

[kdevelop] [Bug 206516] parser, explicit destructor call

[Sumeet Tulsani via KDE Bugzilla]

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

--- Comment #4 from Sumeet Tulsani  ---
Thanks for the feedback Kevin, I will be careful henceforth.
On May 1, 2016 02:08, "Kevin Funk via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=206516
>
> Kevin Funk  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |FIXED
>Version Fixed In||5.0
>  Status|CONFIRMED   |RESOLVED
>
> --- Comment #3 from Kevin Funk  ---
> @Sumeet: Again, this is not about program execution. Please read the bug
> report
> carefully.
>
> Checked under KDevelop 5: No errors in above example code generated. Fixed.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

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

[kwin] [Bug 362496] KWin crashed when unifying outputs

[Kai Krakow via KDE Bugzilla]

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

--- Comment #2 from Kai Krakow  ---
Sorry for not mentioning... Yes, Nvidia proprietary.

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

[kscreenlocker] [Bug 361937] kscreenlocker didn't greeter screen when I want to wake up the session (KDE 5.6)

[Adnan Kurniawan via KDE Bugzilla]

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

Adnan Kurniawan  changed:

   What|Removed |Added

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

--- Comment #10 from Adnan Kurniawan  ---
make sure that all of your Qt5 library IS from
http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_13.2/ and not from
http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_13.2/  

open YAST, and then Software Management, click tab Repositories and then click
on Qt5 repository, click on switch system packages to the versions on this
repository (your Qt5 repos name) click Accept after you resolve every
dependency error and screen lock is work again

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

[Discover] [Bug 362284] discover search doesn't work

[Rune via KDE Bugzilla]

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

Rune  changed:

   What|Removed |Added

 CC||p...@runechristensen.com

--- Comment #2 from Rune  ---
I have the same problem, and can confirm that appstreamcli search chromium
returns 2 entries: Chromium Browser and Chromium B.S.U.

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

[trojita] [Bug 362551] Some fixes in CMakeLists.txt that prevent a FTBFS

[Alf Gaida via KDE Bugzilla]

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

--- Comment #5 from Alf Gaida  ---
then it would be better to install the lib outside of the search path as
private lib - prevent lintian complaining about it.

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

[trojita] [Bug 362551] Some fixes in CMakeLists.txt that prevent a FTBFS

[Pali Rohár via KDE Bugzilla]

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

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #4 from Pali Rohár  ---
Why soversion? That library does not have any public API/ABI, so versioning
does not make sense...

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

[Systemd KCM] [Bug 362554] New: systemd spelling

[Matthias via KDE Bugzilla]

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

Bug ID: 362554
   Summary: systemd spelling
   Product: Systemd KCM
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: rthoms...@gmail.com
  Reporter: shaloksha...@riseup.net

>From the official systemd webside:

Yes, it is written systemd, not system D or System D, or even SystemD. And it
isn't system d either. Why? Because it's a system daemon, and under Unix/Linux
those are in lower case, and get suffixed with a lower case d. And since
systemd manages the system, it's called systemd. 

https://wiki.freedesktop.org/www/Software/systemd/

Both, systemd kcm here in kde.bugs.org and in systemsettings use currently the
spelling with the huge S 

In systemsettings5 lead this to the situation, that systemd appears two times
in the search box

http://funkyimg.com/i/2bkTa.png

http://funkyimg.com/i/2bkT4.png

http://funkyimg.com/i/2bm3m.png

Reproducible: Always


Actual Results:  
2 entrys of systemd in systemsettings5

Expected Results:  
one entry of systemd in systemsettings5

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

[trojita] [Bug 362551] Some fixes in CMakeLists.txt that prevent a FTBFS

[Alf Gaida via KDE Bugzilla]

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

Alf Gaida  changed:

   What|Removed |Added

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

--- Comment #3 from Alf Gaida  ---
Shame on me, you are right. Fixed my checkout. The soversion/version thing
remains. Should i file a new bug?

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

[dolphin] [Bug 362045] Running dolphin from CLI (sudo dolphin) shows NO icons (folders, toolbar, or otherwise)!

[André Verwijs via KDE Bugzilla]

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

André Verwijs <dutchgig...@gmail.com> changed:

   What|Removed |Added

 CC||dutchgig...@gmail.com

--- Comment #3 from André Verwijs <dutchgig...@gmail.com> ---
the same for Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160501)
At least choose fallback theme set with system settings or use gtk 
based theme to show icons... like "PCManFM" file manager  


..

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

[ktorrent] [Bug 362553] Feature request: show total speed in the window title

[via KDE Bugzilla]

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

--- Comment #1 from vlao...@gmail.com ---
Created attachment 98734
  --> https://bugs.kde.org/attachment.cgi?id=98734=edit
Patch for ktorrent 5.0. Worked for 5.0.1 fine too

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

[ktorrent] [Bug 362553] New: Feature request: show total speed in the window title

[via KDE Bugzilla]

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

Bug ID: 362553
   Summary: Feature request: show total speed in the window title
   Product: ktorrent
   Version: 5.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: vlao...@gmail.com

Hello. I'm wrote this simply patch for ktorrent 4, and used for long time. Now
i'm adapted it for ktorrent 5, and i like to see it in upstream.

Reproducible: Always

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