from:"Piotr Mierzwinski via KDE Bugzilla"

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

2016-10-20 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #12 from Piotr Mierzwinski  ---
@Sven. Thanks for clear explanation. I hope Milian will find some solution on
this annoying issue :/.

@Ian. I set it on 4500 ms, but it doesn't help. Still after comment one line I
have to wait couple seconds.

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

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

2016-10-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #9 from Piotr Mierzwinski  ---
Sorry I'm not sure I got you fully :/. Parser is not slow, only delay(s) make
it works slow :/. I understand that parser has to finish its work before I can
generate completion list or helper content. So how to decrease this delay? I
observe similar delays on i5 Sandy Bridge and i7 SkyLake (~3 sec.) and for sure
there is big difference in power between both CPUs, so why this delay is so
similar? I don't understand why processor speed can't help here. So what will
help? I don't type super fast. Sometimes faster, sometimes slower. Function
completer is due to helps me in completing code. Waiting on parser till it
finish its work discourages  of using completing or helper tool :-/.

For me parser is slow, because simple commenting makes I have to wait couple
seconds. Looking at I my example, what parser has to make analysis? This is
couple lines of function and loop with one line body :/. I'm not aware how this
parser works, but this is very uncomfortable during work on code :-(.

> The parser is slow because parsing C++ correctly is complicated.
Parser in KDevelop 4.7.x works much faster. For me it looks like some issue
related with clang. I suppose that in previous KDevelop parser didn't base on
clang. I don't know maybe its parsing wan't enough correctly :/.

Some times ago Milian made some optimizations in parser. I was hope that parser
thanks that will speed up, but this didn't happen :(.

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

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

2016-10-17 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #6 from Piotr Mierzwinski  ---
Parser must be run automatically after every change. This is obvious.
So I repeat the question: "Why the parser running for kdev-clang is such slow,
even on strong hardware?"
@Sven. You said: "we explicitly added a longer delay for some edit". Is this
delay hard coded? Is this delay can't depend on power of processor? Is not
possible to create bigger cache and hold it in memory? I think IDE is not the
application running couple times a day.

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

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

2016-10-17 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #3 from Piotr Mierzwinski  ---
@Ian Haber I think parser working in background is required to properly update
the "Problems". I mean update on a regular basis.
I wonder why parser running for kdev-clang is such slow, even on strong
hardware?

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

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

2016-10-17 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages
 CC||piotr.mierzwin...@gmail.com

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

[kdevelop] [Bug 371018] New: CPP parser responds very slow after user action

2016-10-17 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 371018
   Summary: CPP parser responds very slow after user action
   Product: kdevelop
   Version: 5.0.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

CPP parser responds in couple seconds for helper tool or for simple commenting
line.
For example 
applying comment:for one line in file (~30kb) from:
- my project takes about 3 seconds
-  kdevelop takes about 4 seconds
Similar time I get for helper tool. I need to wait couple seconds! This is not
much comfortable behavior comparing to my hardware (check end this report).

In my opinion this is serious regression comparing to kdevelop-4.7.x, where
application responds in less than 1 second.
I tested kdevelp-4.7.3 on Mageia 5 distribution where all are working on Sandy
Bridge i5-2410M







Reproducible: Always

Steps to Reproduce:
1. Open project kdevelop
2. Wait till kdevduchain cache finishes its building
3. Open file following file:
kdevelop-git/src/kdevelop/projectmanagers/cmake/cmakemanager.cpp
4. Jump to line: 193
In my version of kdevelop source this points to inside of loop for function:
CMakeManager::targets(). Please check below all function:
QList CMakeManager::targets() const
{
QList ret;
foreach(IProject* p, m_projects.keys())
{
ret+=p->projectItem()->targetList();
}
return ret;
}

I comment line starting with: "ret+="


Actual Results:  
need to wait at least 3 seconds for applying comment (changing color this line)

Expected Results:  
applying comment (changing color this line) should take less than 1 seconds (at
least on processor compared to i5 Sandy Bridge / Ivy Bridge).

My hardware is following: SkyLake i7-6700 + SSD m4 Crucial 128GB. I observe the
same behavior (the need of waiting couple seconds on respond) on Sandy Bridge
i5-2410M  + HDD.

My settings for "Background parser" are following:
- checked: "Enabled Background Parser"
- Delay: 500ms
- Maximum Number of threads

My settings for "Clang Language Support" are following:
all checked, so:
- Add macros to code-completion
- Enable Look-ahead code-completion
- Forward declare assistant

I tested on version (day of build: 2016/10/17):
kdevplatform-git-debug-5.0.2.r13464
kdevelop-git-debug-5.0.2.r23476

Running environment:  Plasma 5.8.1, Qt-5.7.0, KF-5.27, kernel 4.7.6-1-ARCH
x86_64
Distribution Antergos (up-to-date).

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

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

2016-10-16 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #7 from Piotr Mierzwinski  ---
OK. Sorry for not clear report. I didn't get a crash in result my activities
only main window of KDevelop disappears. Crash happens later.
Main windows of KDevelop disappears, but I can see working process in list of
processes. I'm not able to restore it (main window). I kill it and I get crash,
what is result of killing I suppose.

I can reproduce it every time. My steps are following:
1. To dependencies I add some subdirectory (main->sub1->sub2->sub3) of my
project ("Launch configuration", Action: Build)
2. I modify any file from this directory
3. I invoke "Run -> Execute Launch" (with selected top directory of project). 
In this moment main window of KDevelop may disappears, if not I can see message
like below.
This is output from Build view:
/run/media/piotra/FreeAgent/piotr/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build>
make -j8 zipsubsystem.o
*** Killed process ***
Seems like KDevelop think that something is running, because both tool buttons
related with stopping running jobs are enabled. In first "Menu allowing to stop
individual jobs" I can see: "my_project_name, changed_file_name: build"
4. Again I invoke "Run -> Execute Launch" 
In this moment main window of KDevelop disappears.

When I select as target binary file (I mean entry with the same icon like
already put by default executable file) also main window of KDevelop
disappears.

When I run it from konsole I can see such output in last lines:
Launch Configuration: "qtcmd2" "No environment group specified, looks like a
broken configuration, please check run configuration 'qtcmd2'. Using default
environment group."
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
The X11 connection broke: No error (code 0)
XIO:  fatal IO error 13 (Brak dostępu) on X server ":0"
  after 6882 requests (6882 known processed) with 0 events remaining.

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

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

2016-10-15 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #5 from Piotr Mierzwinski  ---
Sorry. Errata about sending signal. As you can check in attached dbg output I
send also SIGTERM. Sending CONT and command "cont" in dbg leads to never ending
loop. I repeated it couple times after that.

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

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

2016-10-15 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #4 from Piotr Mierzwinski  ---
Created attachment 101575
  --> https://bugs.kde.org/attachment.cgi?id=101575=edit
KDevelop dbg session

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

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

2016-10-15 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #3 from Piotr Mierzwinski  ---
In dbg output I got also message like this:

Launch Configuration: "qtcmd2" "No environment group specified, looks like a
broken configuration, please check run configuration 'qtcmd2'. Using default
environment group."

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

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

2016-10-15 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #2 from Piotr Mierzwinski  ---
Sorry. This was what produced by DrKonqi when I wanted close working in
background KDevelop process. Before KDevelop only closed itself. I wasn't be
able to run it again, because in background I had working KDevelop. I killed
this process and this triggered DrKonqi.

Today I tried to reproduce crash running KDevelop in dbg, but again KDevelop
just closed its main window. I had to send couple times signal "CONT" (from
System activity tool - invoked by Ctrl+Esc), to get prompt of dbg. After that I
run command "cont" and again no prompt and nothing happened. I repeat this
couple of time. Finally I run "kill -CONT kdevelop_pid" from konsole and after
"cont" command in dbg  returned: "Thread 1 "kdevelop" received signal SIGSEGV,
Segmentation fault.". In backtrace I noticed that this is again crash in
MainWindow:

#8  0x77a8701b in KDevelop::MainWindow::~MainWindow()
(this=this@entry=0x8e4f50, __in_chrg=, __vtt_parm=)
at
/home/piotra/build-repos/kdevplatform-git/src/kdevplatform/shell/mainwindow.cpp:158

I attach dbg output.

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

[kdevelop] [Bug 370311] New: KDevelop crashed during quit

2016-10-08 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 370311
   Summary: KDevelop crashed during quit
   Product: kdevelop
   Version: 5.0.1
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Application: kdevelop (5.0.1)

Qt Version: 5.6.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.1-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
I run application and got message that run is not possible. After that I wanted
quit KDevelop and it crashed.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fef60f05800 (LWP 17331))]

Thread 5 (Thread 0x7feef37fe700 (LWP 19260)):
#0  0x7fef71796c4f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fef6cd4d234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7fef6cd4d279 in  () at /lib64/libQt5Script.so.5
#3  0x7fef7179166d in start_thread () at /lib64/libpthread.so.0
#4  0x7fef77910ded in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fef1bfff700 (LWP 17541)):
#0  0x7fef77904f9d in poll () at /lib64/libc.so.6
#1  0x7fef70901a54 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fef70901b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fef7820d3ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fef781b8c9a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fef77ff237c in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fef7179166d in start_thread () at /lib64/libpthread.so.0
#8  0x7fef77910ded in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fef52efd700 (LWP 17338)):
#0  0x7fef71796ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fef77ff7d06 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fef75a16568 in KDevelop::DUChainPrivate::CleanupThread::run()
(this=0x2acb150) at
/usr/src/debug/kdevplatform-5.0.1/language/duchain/duchain.cpp:282
#3  0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7fef7179166d in start_thread () at /lib64/libpthread.so.0
#5  0x7fef77910ded in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fef5af91700 (LWP 17334)):
#0  0x7fef77904f9d in poll () at /lib64/libc.so.6
#1  0x7fef70901a54 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fef70901b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fef7820d3ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fef781b8c9a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fef77ff237c in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fef7a337615 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fef7179166d in start_thread () at /lib64/libpthread.so.0
#9  0x7fef77910ded in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fef60f05800 (LWP 17331)):
[KCrash Handler]
#6  0x057ae1c0 in  ()
#7  0x7fef752c1376 in NotifyByAudio::~NotifyByAudio() () at
/lib64/libKF5Notifications.so.5
#8  0x7fef752c1409 in NotifyByAudio::~NotifyByAudio() () at
/lib64/libKF5Notifications.so.5
#9  0x7fef781e45f3 in QObjectPrivate::deleteChildren() () at
/lib64/libQt5Core.so.5
#10 0x7fef781ed1a4 in QObject::~QObject() () at /lib64/libQt5Core.so.5
#11 0x7fef752a4bf9 in (anonymous
namespace)::Q_QGS_s_self::innerFunction()::Holder::~Holder() () at
/lib64/libKF5Notifications.so.5
#12 0x7fef77851478 in __run_exit_handlers () at /lib64/libc.so.6
#13 0x7fef778514c5 in  () at /lib64/libc.so.6
#14 0x7fef7783b607 in __libc_start_main () at /lib64/libc.so.6
#15 0x0040c0f9 in _start () at ../sysdeps/x86_64/start.S:118

Reported using DrKonqi

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

[plasmashell] [Bug 368659] Possibility of selecting (raising) window from list of windows placed on tool tip shown by Pager

2016-09-11 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 CC||piotr.mierzwin...@gmail.com

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

[plasmashell] [Bug 368659] New: Possibility of selecting (raising) window from list of windows placed on tool tip shown by Pager

2016-09-11 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 368659
   Summary: Possibility of selecting (raising) window from list of
windows placed on tool tip shown by Pager
   Product: plasmashell
   Version: 5.7.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Pager
  Assignee: plasma-b...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

In my opinion would be good to be able select and raise any window from Pager
windows list. Current behavior is following. When we move mouse cursor over
Pager, it shows tool tip contains list of applications placed on specified
desktop. And now when we move cursor placed over Pager to its tool tip, it just
disappears.
Would be nice to just click on any of window title and raise it.


Reproducible: Always

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

[kdevplatform] [Bug 343124] Use "Close all other output views" is breaking filtered Output in not closed view

2016-09-08 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #6 from Piotr Mierzwinski  ---
My system. 
Linux 4.7.2-1-ARCH
KF-5.25, Qt-5.7.0
Packages built from git (at 2016/09/05), brach 5.0.
kdevelop-git-debug-5.0.0.r23429.f5cf3c6
kdevplatform-git-debug-5.0.0.r13375.d5aa9f3

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

[kdevplatform] [Bug 343124] Use "Close all other output views" is breaking filtered Output in not closed view

2016-09-08 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 Resolution|FIXED   |---
   Platform|Mageia RPMs |Archlinux Packages
 Status|RESOLVED|REOPENED
Version|1.7.0   |5.0.0

--- Comment #5 from Piotr Mierzwinski  ---
In KDevelop 5 this bug still persist.
Below I remind the steps to reproduce this bug.

1. Run ("Execute Launch") your application in KDevelop what produce some
output. Close it
2. Run again your application
Now there is two Run outputs.
3. Put something in filter what matches to some string in Run output
You should receive some result, for example couple matching lines instead
of 100 (original output)
4. Click button on Run output with description "Close all other output views"
In result: 
 - filter filed is cleaned 
-  we are no able to restore original content of "Run" output

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

[kdevelop] [Bug 365437] Rename local variable using "Rename" assistant breaks code

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Version|git master  |5.0.0

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

[kdevplatform] [Bug 368423] New: After back from "Review patch" document gets title "Overview" instead of file name, and document becomes "Read only"

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 368423
   Summary: After back from "Review patch" document gets title
"Overview" instead of file name, and document becomes
"Read only"
   Product: kdevplatform
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: patchreview
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
CC: david.nolden@art-master.de

As in title "Review patch" option makes that after back to "Code" context
document lose title on tab and becomes read only. Refresh doesn't help. There
is need to close and open file again.

Reproducible: Always

Steps to Reproduce:
1. Open KDevelop with some (versioned) project (I use git).
2. Open some document
3. Make some changes, save file
4. Use "Git -> Show differences"
5. Back from "Review" using "Finish review"
6. Clicking RMB in document should be visible "Patch review" option - click
into it
7. In this view click "Update" and "Finish review"
8. Being in "Code" context check title of changed document and try modify it

Actual Results:  
Title on tab gets name "Overview" instead of actual file name and this document
becomes read only.

Expected Results:  
Title on tab should has the same name as original file. Should be possible to
edit this document.

KF-5.25, Qt-5.7.0
Packages built from git (at 2016/09/05), branch 5.0.
kdevelop-git-debug-5.0.0.r23429.f5cf3c6
kdevplatform-git-debug-5.0.0.r13375.d5aa9f3

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

[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #8 from Piotr Mierzwinski  ---
I realized that the reason of "KDevelop crashed and didn't want to run again"
was working kdevelop process in background. When I finish it I was able to
report bug by Konqi. After that I was able to run KDevelop again.

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

[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #7 from Piotr Mierzwinski  ---
Below please find "error" what I can see after  "Run -> Execute Launch" (with
adding one dependency)
/run/media/piotra/FreeAgent/piotr/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build>
make -j8
*** Killed process ***

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

[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages
Version|git master  |5.0.0

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

[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #6 from Piotr Mierzwinski  ---
Created attachment 100977
  --> https://bugs.kde.org/attachment.cgi?id=100977=edit
CMakeLists.txt from main directory

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

[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #5 from Piotr Mierzwinski  ---
The issue still persist in current version of KDevelop (app.built at
2016/09/05, from branch 5.0).

In this moment my "Launch Configuration" is default (no dependencies skipping
main binary/executable file suggested by KDevelop). In my structure of
directories, invoking of F8 (with selected top directory) made building files
in whole project. I mean all files including subdirectories. Proper rules are
defined in CMakeLists.txt, so I think this is currect result. Unfortunately
when I invoke "Run -> Execute Launch" or "Run -> Debug Launch" only changed
files which are located in main directory are built. Others (in subdirectories)
don't. So after change some file in subdirectory I need to remember to invoke
build (F8) and then "Execute Launch". OK. Maybe this is because I don't have
defined any dependencies for subdirectories.
So I added this: "qtcmd2/plugins/preview/textviewer". I modified file inside
this directory, saved. And invoked "Run -> Execute Launch" (with selected top
directory). Unfortunately I got error in Build view. Sorry, I don't remember
what. OK. So I run build and when finished again I invoked "Run -> Execute
Launch". After this, KDevelop crashed and didn't want to run again :(.
I reported this bug as Bug 368420.

Below please find directories structure of my project (located here:
git://git.qtcmd.org/qtcmd2.git).

qtcmd2
qtcmd2/templates
qtcmd2/libs
qtcmd2/libs/xdgmime
qtcmd2/libs/widgets
qtcmd2/libs/utils
qtcmd2/plugins
qtcmd2/plugins/preview
qtcmd2/plugins/preview/archiveviewer
qtcmd2/plugins/preview/videoviewer
qtcmd2/plugins/preview/audioviewer
qtcmd2/plugins/preview/textviewer
qtcmd2/plugins/preview/imageviewer
qtcmd2/plugins/vfs
qtcmd2/plugins/vfs/rarsubsystem
qtcmd2/plugins/vfs/zipsubsystem
qtcmd2/plugins/vfs/localsubsystem
qtcmd2/plugins/vfs/ftpsubsystem
qtcmd2/plugins/vfs/tarsubsystem
qtcmd2/src
qtcmd2/src/ui
qtcmd2/src/preview
qtcmd2/src/vfs

Below rules from CMakeLists.txt:
add_subdirectory(libs/widgets)
add_subdirectory(libs/utils)
add_subdirectory(libs/xdgmime)
add_subdirectory(src)
add_subdirectory(plugins/vfs/localsubsystem)
add_subdirectory(plugins/vfs/rarsubsystem)
add_subdirectory(plugins/vfs/tarsubsystem)
add_subdirectory(plugins/vfs/zipsubsystem)
add_subdirectory(plugins/vfs/ftpsubsystem)
add_subdirectory(plugins/preview/textviewer)
add_subdirectory(plugins/preview/imageviewer)
add_subdirectory(plugins/preview/videoviewer)
add_subdirectory(plugins/preview/audioviewer)
add_subdirectory(plugins/preview/archiveviewer)

In any case I attach my main CMakeLists.txt.

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

[kdevelop] [Bug 368420] New: KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 368420
   Summary: KDevelop crashes when invoking Execute Launch after
adding dependencies in Launch Configuration
   Product: kdevelop
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Application: kdevelop (5.0.0)

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.7.2-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

 I added detepdency as subdirectory of my project. I modified file inside this
directory, saved. And invoked "Run -> Execute Launch" (with selected top
directory of project). Unfortunately I got error in Build view. Sorry, I don't
remember what. OK. So I run build and when finished again I invoked "Run ->
Execute Launch". After this, KDevelop crashed and didn't want to run again.

This backtrace is generated after I wanted finish the process in tool (called
Ctrl+Esc).

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8fcd2e7800 (LWP 3405))]

Thread 18 (Thread 0x7f8f3effd700 (LWP 4536)):
#0  0x7f8fc39bf10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f8fbe28fac4 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f8fbe28fb09 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f8fc39b9454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f8fca0e97df in clone () from /usr/lib/libc.so.6

Thread 17 (Thread 0x7f8f5dffb700 (LWP 3710)):
#0  0x7f8fca0e048d in poll () from /usr/lib/libc.so.6
#1  0x7f8fc19b7066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f8fc19b717c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f8fcaa0259b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f8fca9ac0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f8fca7cf0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f8fca7d3d78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f8fc39b9454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f8fca0e97df in clone () from /usr/lib/libc.so.6

Thread 16 (Thread 0x7f8f5e7fc700 (LWP 3439)):
#0  0x7f8fca0e048d in poll () from /usr/lib/libc.so.6
#1  0x7f8fc19b7066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f8fc19b717c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f8fcaa0259b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f8fca9ac0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f8fca7cf0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f8fca7d3d78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f8fc39b9454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f8fca0e97df in clone () from /usr/lib/libc.so.6

Thread 15 (Thread 0x7f8f5f7fe700 (LWP 3434)):
#0  0x7f8fc39bf10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f8fca7d4c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f8fbf0c236b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() from /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f8fbf0c7d30 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f8fbf0c2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f8fbf0c2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f8fbf0c2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f8fbf0c2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7f8fbf0c2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7f8fbf0c2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7f8fbf0c51f9 in ThreadWeaver::Thread::run() () from
/usr/lib/libKF5ThreadWeaver.so.5
#16

[kdevelop] [Bug 368415] New: KDevelop crashes during logging out or shutting down Plasma

2016-09-07 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 368415
   Summary: KDevelop crashes during logging out or shutting down
Plasma
   Product: kdevelop
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Almost every time when I logout/shutdown from Plasma KDevelop crashes. DrKoqi
shows info about crash and after that all is quickly closing (Plasma is
closing).
Sometime in KDevelop I  run build, and sometime nothing (work in idle mode). I
don't modify any opened document. I logout from Plasma and KDevelop crashes.

Sorry for missing debug backtrace but I don't know how to could I catch it. I
click in DrKonqi and it is automatically closed.

KDevelop is restored in every start of Plasma. Cache: kdevduchain is
regenerated every start.
It happens in 95% cases when I finish work in Plasma.

Reproducible: Sometimes

Steps to Reproduce:
1. Run KDevelop with some project and opened couple documents.
2. Run buid or wait about 10 min.
3. Logout of shutdown Plasma

Actual Results:  
KDevelop crashes

Expected Results:  
KDevelop should not crash.

This issue might be related with: "Bug 364437 - kdevelop crash when logging out
too quickly."
https://bugs.kde.org/show_bug.cgi?id=364437

KF-5.25, Qt-5.7.0
Packages built from git (at 2016/09/05), brach 5.0.
kdevelop-git-debug-5.0.0.r23429.f5cf3c6
kdevplatform-git-debug-5.0.0.r13375.d5aa9f3

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

[kdevplatform] [Bug 353343] CRASH in AssistantPopup::executeHideAction - assistantpopup.cpp:351

2016-09-06 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #3 from Piotr Mierzwinski  ---
No problem. Some time ago I switched to 5.0.

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

[kdevelop] [Bug 367905] New: Breakpoint marker disappears from bar in editor after stopping application in debug mode

2016-08-27 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 367905
   Summary: Breakpoint marker disappears from bar in editor after
stopping application in debug mode
   Product: kdevelop
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
CC: niko.s...@gmail.com

As in title. After click in breakpoint in Breakpoints view is highlighted
proper line in editor but on left bar there is no breakpoint marker (icon).
Looks like something wasn't redraw.
Uses icons style: Breeze.

Reproducible: Always

Steps to Reproduce:
1. Open at least two documents in KDevelop.
2. In first document set breakpoint (clicking in left bar in editor) and switch
to second document
3. Run application in debug mode and make that application will stop on
breakpoint (meet some conditions causing that falls into the trap)
4. Stop debugging by clicking button: "Stop all currently running jobs"
5. Open "Breakpoints" view and click into proper breakpoint (referring to
previously set)


Actual Results:  
In editor is highlighted correct line with breakpoint, but on left bar is
missing breakpoint marker (icon)

Expected Results:  
In editor is highlighted correct line with breakpoint, and on left bar is
preset breakpoint marker (icon)

kdevelop 5.0.0.r23419.7314e99  (built 22/08/2016, branch: 5.0)
kdevplatform 5.0.0.r13346.09a1848  (built 22/08/2016, branch: 5.0)
KFrameworks 5.25, Qt-5.7.0

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

[konsole] [Bug 355421] Konsole crashed on login

2016-08-27 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #9 from Piotr Mierzwinski  ---
Created attachment 100810
  --> https://bugs.kde.org/attachment.cgi?id=100810=edit
New crash information added by DrKonqi

konsole (16.04.3) using Qt 5.7.0

- What I was doing when the application crashed:

Situation the same as reported by Fedora users.
Powered on the machine, logged in, and konsole cashed during Plasma session was
restoring.

Used componenets: Plasma 5.7.3, KF-5.25, Qt-5.7.0

-- Backtrace (Reduced):
#5  0x7ff0309d9970 in Konsole::Session::sessionId() const () from
/usr/lib/libkonsoleprivate.so.16
#6  0x7ff030a0fb48 in
Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) () from
/usr/lib/libkonsoleprivate.so.16
#7  0x7ff030a11bdf in Konsole::ViewManager::createView(Konsole::Session*,
Konsole::ViewContainer*, int) () from /usr/lib/libkonsoleprivate.so.16
#8  0x7ff030a16150 in Konsole::ViewManager::createView(Konsole::Session*)
() from /usr/lib/libkonsoleprivate.so.16
#9  0x7ff030a16c71 in Konsole::ViewManager::restoreSessions(KConfigGroup
const&) () from /usr/lib/libkonsoleprivate.so.16

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

[konsole] [Bug 355421] Konsole crashed on login

2016-08-27 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

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

[kdevelop] [Bug 367735] New: Problem in semantic analysis - cannot rename all variables after click in usage this variable

2016-08-23 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 367735
   Summary: Problem in semantic analysis - cannot rename all
variables after click in usage this variable
   Product: kdevelop
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

There is an example of code:

foo()
{
QString sFileName  = QFileDialog::getSaveFileName(this, tr("Save as"),
m_InitialPath);

if (! sFileName.isEmpty()) {
if (QFileInfo(sFileName).exists()) {
// file already exists
}
else
   saveFile(sFileName);
}
}

I rename declaration of sFileName to sFileName2, so now first line looks like
this:
QString sFileName2  = QFileDialog::getSaveFileName(this, tr("Save as"),
m_InitialPath);

All occurrences for not declared variable  are underlined. OK. I move cursor
over declaration and I get: Solution (1): Rename "sFileName" to "sFileName2".
But wait. In this place variable is already renamed :/. OK. Nevermind. I click
"Solution (1)" and all occurrences are renamed. Great. This is what I wanted.
I undo all changes, and again rename declaration in the same way. Now I move
cursor over first usage. This is mentioned line:
 if (! sFileName.isEmpty()) 
I get the same tool tip, so again I click in "Solution (1)". After that only
occurrence under cursor is renamed. This is happen on every next usages of
variable. Why?
I'm not sure, but I think it was working before change with tool tip: "Problem
in semantic analysis". I mean all occurrences were always renamed.


Reproducible: Always

Steps to Reproduce:
1. Rename declaration of local variable
2. Try to use "Semantic analysis helper" for any usage of variable not for
declaration
3. Click "Solution (1)"

Actual Results:  
Only occurrence under cursor is renamed

Expected Results:  
All occurrences for selected variable should be renamed.
Thanks that kdevelop will avoid forcing an user to go back to declaration and
again back to current code.

kdevelop 5.0.0.r23419.7314e99  (built 22/08/2016, branch: 5.0)
kdevplatform 5.0.0.r13346.09a1848  (built 22/08/2016, branch: 5.0)
KFrameworks 5.25, Qt-5.7.0

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

[kdevelop] [Bug 367690] Git option in RMB is not available after click in any place of versioned file

2016-08-22 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com
Summary|Git option in RMB is not|Git option in RMB is not
   |available when I click in   |available after click in
   |any place of versioned file |any place of versioned file

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

[kdevelop] [Bug 367690] New: Git option in RMB is not available when I click in any place of versioned file

2016-08-22 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 367690
   Summary: Git option in RMB is not available when I click in any
place of versioned file
   Product: kdevelop
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Several weeks ago after click by RMB in any place in versioned (by GIT)
document was available option "Git". Recently this option is only available
when we click in function name or member name or type of member. Click in other
place shows menu without this option.

For me it looks like regression. I don't know is this feature or bug.

Reproducible: Always

Steps to Reproduce:
1. open any project versioned with git
2. click RMB in any place of document, skipping function name, member name,
member type
3. check availability of "Git" option"

Actual Results:  
missing "Git" option in popping up menu invoked by RMB

Expected Results:  
"Git" option should be placed in this menu no matter where user click (by RMB)
in document

kdevelop 5.0.0.r23419.7314e99  (built 22/08/2016, branch: 5.0)
kdevplatform 5.0.0.r13346.09a1848  (built 22/08/2016, branch: 5.0)
KFrameworks 5.25, Qt-5.7.0

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

[konsole] [Bug 365413] Session restore of Konsole does not work if a tab's shell was in a folder not yet re-mounted

2016-07-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #3 from Piotr Mierzwinski  ---
>From my end I can confirm this issue. 
I experienced randomly not restored session of konsole. I wondered what is
wrong, but one day I discovered the issue.

Very often I run konsole with  pure bash shell and two mc sessions. Sometimes I
mount (manually - using tool from taskbar) external hard disk and open in mc
some directory from this disk. I shut down system not changing this directory.
Next day I power on computer and login into Plasma. Konsole is not restored. To
be sure I did some tests with automatically mounted my external hard disk. In
this case konsole was restored. In this moment this is my work around for this
issue.

I use Antergos, with: Plasma 5.7.1, KF 5.24, KApplications 16.04.3, Qt-5.7.0

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

[kdevelop] [Bug 365437] Rename local variable using "Rename" assistant breaks code

2016-07-11 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
Second example:
The same, as described above, is happened when I try to rename argument "e" in
below function to "e2"

void MyClass::foo2( QEvent *e )
{
bool stat = true;
int a = 1;
if (stat) {
if (a == 1)
e->accept();
else
e->ignore();
}
}

After using Rename assistant I get following code:
void MyClass::foo2( QEvent *e2 )
{
bool stat = true;
int a = 1;
if (stat) {
if (a == 1)
 {
e2->accept();
else
 {
e2->ignore();
}
}

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

[kdevelop] [Bug 365437] New: Rename local variable using "Rename" assistant breaks code

2016-07-11 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 365437
   Summary: Rename local variable using "Rename" assistant breaks
code
   Product: kdevelop
   Version: git master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

There is following code:
void MyClass::foo( bool param )
{
bool stat;
QString string;
if (param) {
if (string.isEmpty())
stat = true;
else
stat = false;
}
}

I rename "stat" variable to "stat2". Choosing "Rename stat to stat2" makes that
in code are inserted two (opening) curly brackets.

Reproducible: Always

Steps to Reproduce:
1. Rename local variable what is used inside of block of code like above
2. Choose "Rename old_name to new_name"
3.

Actual Results:  
void MyClass::foo( bool param )
{
bool stat2;
QString string;
if (param) {
if (string.isEmpty())
 {
stat2 = true;
else
 {
stat2 = false;
}
}

Expected Results:  
void MyClass::foo( bool param )
{
bool stat2;
QString string;
if (param) {
if (string.isEmpty())
stat2 = true;
else
stat2 = false;
}
}


KDevelop and KDevPlatform cloned and built from branch 5.0, at 08-07.2016.
Plasma 5.7.0, KFrameworks 5.23, Qt-5.7.0

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

[kdevelop] [Bug 358799] Use of "Update definition signature" in "Adapt Signature" breaks declaration of function if its argument has default value

2016-07-11 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Version|4.90.91 |git master
Summary|Function "Update|Use of "Update definition
   |declaration signature"  |signature" in "Adapt
   |breaks declaration if   |Signature" breaks
   |inside there is default set |declaration of function if
   |parameter   |its argument has default
   ||value
   Platform|Kubuntu Packages|Archlinux Packages

--- Comment #3 from Piotr Mierzwinski  ---
Below please fine example for the  version of KDevelop and KDevPlatform cloned
and built from branch 5.0, at 08-07.2016.

There is simple function:
declaration:
void foo( bool param = true );

definition:
void MyClass::foo( bool param )
{
}

In declaration of function I rename param to param2. And now choosing "Update
definition signature" from "Adapt Signature" helper breaks declaration. I get
code like this:

declaration
void MyClass::foo ( bool param2 )
;

definition (no change):
void MyClass::foo( bool param )
{
}

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

[kdevelop] [Bug 365420] New: Use of "Adapt signature" for rename argument in constructor inserts keyword void in declaration

2016-07-11 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 365420
   Summary: Use of "Adapt signature" for rename argument in
constructor inserts keyword void in declaration
   Product: kdevelop
   Version: git master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

I rename argument in constructor definition (cpp file). After choosing "Update
declaration signature" in "Adapt Signature" helper I get constructor as void
type in declaration (header).

There is code
cpp file:
MyClass::MyClass( int *pointer, const QString  )
{

}

header file:
MyClass( int *pointer, const QString  );

For example I rename string to string2 and chose  "Update declaration
signature" in "Adapt Signature".

Reproducible: Always

Steps to Reproduce:
1. Rename one of parameter in constructor
2. Choose "Update declaration signature" in "Adapt Signature"
3. Check header file

Actual Results:  
MyClass::MyClass( int *pointer, const QString  )
{

}

header file:
void MyClass ( int *pointer, const QString  );

Expected Results:  
MyClass::MyClass( int *pointer, const QString  )
{

}

header file:
 MyClass ( int *pointer, const QString  );

KDevelop and KDevPlatform cloned and built from branch 5.0, at 08-07-2016
Plasma 5.7.0, KFrameworks 5.23, Qt-5.7

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

[kdevelop] [Bug 364906] Adapt signature breaks code if in declaration of function there is no parameter name

2016-06-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
Sorry for mistake.
Expected Results:  
header:
  void slotUrlActivated ( const QUrl & );

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

[kdevelop] [Bug 364906] New: Adapt signature breaks code if in declaration of function there is no parameter name

2016-06-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 364906
   Summary: Adapt signature breaks code if in declaration of
function there is no parameter name
   Product: kdevelop
   Version: git master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

There is following code:
declaration (header file):
void slotUrlActivated(const QUrl&);

definition (cpp file):
void MainWindow::slotUrlActivated( const QUrl  )
{
  qDebug() << "MainWindow::slotUrlActivated" << u.path();
}

Being in header file.
In above declaration I insert single space before "const" and after ampersand.
Appears helper: "Adapt signature 1. Update definition signature  0. Hide".  I
choose 1
In result code becomes broken - a bit in declaration, and more in definition.


Reproducible: Always


Actual Results:  
header:
  void MainWindow::slotUrlActivated ( const QUrl & )
;

definition:
void MainWindow::slotUrlActivated( const QUrl  )
{ 
  qDebug() << "MainWindow::slotUrlActivated" << .path();
}

Expected Results:  
header:
  void MainWindow::slotUrlActivated ( const QUrl & );

definition:
void MainWindow::slotUrlActivated( const QUrl  )
{ 
  qDebug() << "MainWindow::slotUrlActivated" << u.path();
}

KDevelop and KDevplatform cloned and built at Jun 13, 2016. Branch 5.0.
Plasma 5.6.5, KF-5.23 built with Qt-5.6.0

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-06-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #67 from Piotr Mierzwinski  ---
I think I found reason why konsole is not restored.
Very often in konsole in run pure bash shell and two mc sessions. Sometimes I
mount (manually - using tool from taskbar) external hard disk and open in mc
some directory from this disk. I shut down system didn't changed directory.
Next day I power on computer and login into Plasma. Konsole is not restored. To
be sure I did some tests with automatically mounted my external hard disk. In
this case konsole was restored.

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

[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave

2016-06-26 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #63 from Piotr Mierzwinski  ---
(In reply to Leslie Zhai from comment #61)
> Yup also worked for ArchLinux now ;-)

I use Antergos (Arch based distro) and I observed next problem. I mean that
konsole is not restored in such case. One day I shut down system (calling
proper option in K menu) and when next day I login konsole is not restored,
wheras kwrite, kate, dolphin, okular are restored. This issue not happens when
I shut down computer and run it again the same day. Additionally I tried shut
down using qdbus command like this: "qdbus org.kde.ksmserver /KSMServer logout
0 2 2", but with the same result.

So I wonder if this issue is related only for Arch based distributions or this
is some bug in konsole :/.

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

[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave

2016-06-26 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #62 from Piotr Mierzwinski  ---
(In reply to Storm Engineer from comment #58)
> (In reply to Thomas Lübking from comment #57)
> > Firefox or cairo-dock were certainly not targetted or affected by the
> > related patches.
> 
> I did some more testing, and indeed Qt apps (or at least most of them) seem
> to get restored properly now. The following get restored:
>  - Dolphin
>  - Konversation
>  - Konsole
>  - Ksysguard
>  - KDE system settings
> 
> The following do NOT get restored:
>  - Firefox
>  - Google Chrome
>  - VLC Media Player
>  - Cairo-Dock
> 
> Isn't Chrome using Qt tho? I don't know.
> 
> And I have no idea what may lie beneath this issue, I'm just a noob and all
> I can do is telling what I experience.
> 
> I have another issue which may be related, but the two are spanning across
> different time frames so it doesn't seem likely. This issue is shutdown
> being halt with "A stop job is running for session c2 of user" with a 1:30
> timeout counter. However, session restore was broken ever since I use
> Plasma/KDE 5, which is more than a year I think, while this issue only
> started 1-2 months ago. Also, the "stop job is running" issue appears
> randomly, while session restore always failed consistently.

The problem not restored GTK+ applications in Plasma 5.6.x (built with Qt
5.6.x) was cased removing support for XSM protocol:
https://quickgit.kde.org/?p=plasma-workspace.git=commit=5f0ca1305db4a925dbdbf927f541497be334feff
https://bugs.kde.org/show_bug.cgi?id=362671
I reported bug related with restoring GTK+ applications, and before couple of
days it has been restored. Check this report: 
https://bugs.kde.org/show_bug.cgi?id=362671 (fix applied in branch 5.6, branch
5.7 and master).

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-06-23 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #66 from Piotr Mierzwinski  ---
@Wolfgang Bauer
Thanks for explanation.
On begin I can say that happened what I supposed. So today after first login to
Plasma, konsole has not been restored, at all. Maybe this is some bug in
konsole. Yesterday, before shutting down the system I also run okular, and
kate. Today all of them have been restored.

> restoring them should work (or not) the same for both
> But in the end it's the client's (i.e. the application's) job to save its 
> state correctly
I know that in the moment of closing application its destructor are calling,
actually QApplication/KApplication. So what is the difference in type of
shutting (by server). When I log off (calling log off in Plasma) or shut down
system (calling "turn of" in Plasma) then shutting should work the same. in
This is my suspicion.
The only one job what can do application in shutting down moment is saving it's
state into some configuration file. Every other actions are managed by
Qt/KF/ksmsever. As I suppose.  And this is doing correct for login off and
restart.

For me it should just work for both (konsole and kwrite) the same.
Sorry I repeat my self. Yesterday I reloged couple of times, also I restarted
system. And konsole was restored every time. When yesterday  I shut down the
system and run it today,  konsole has not been restored. I don't understand
this.
I don't know how exactly Plasma closing/shutting down its session, I suppose is
using some qdbus command (example of shutting down: "qdbus org.kde.ksmserver
/KSMServer logout 0 2 2"). Is this implemented by distribution or in K menu?

And on end. You are comparing two Qt versions. Why openSuse doesn't use the
newest Qt version, only its developers backported some fixes? Maybe in last Qt
still persists some bug related with closing applications. 

@Chris
I don't know what situation you meant, saying "konsole never ever get restored
for me."?
If this is just rerun of konsole thats OK. For me either konsole wasn't
restored.
If this is relogin/restart/shut down and run then in my opinion konsole should
be restored every times when Plasma session is starting and proper option is
turned on in Plasma setting (for example: "Restore previous session" in System
settings).

Maybe this is distro related. I don know. :/. I'll try to report it.

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-06-22 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #63 from Piotr Mierzwinski  ---
I don't think that good idea is blamed konsole for this. As I said this happens
randomly. Today, after your post, I made couple of tests (several relogin and
restarts) and every time all tabs were restored. In the same time I'm not sure
that when I run computer tomorrow then konsole will be restored. This is
happens sometimes. And I observed it couple of times within month. Today was
last time when run computer fist time after back from work. Issue is a bit
similar to this one placed in Qt 5.5.x. In this moment I'm not able to
replicate the issue. I don't know why kwrite is restoring properly every time.
I think that both are using the same XSMP protocol, what is probably built in
KF libraries.

I know that konsole does not restore running application after its restart. In
my opinion it's shame. For me enough would be only run tabs with defined
profile, so for example with pure terminal, mc, other defined profiles running
in moment of closing. If automatically restoration is not possible then useful
would be option what force running of saved tabs. I know, this is wish for
konsole. I'm aware that this option option is not really needed if konsole is
properly restored after relogin or restart.

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-06-22 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #61 from Piotr Mierzwinski  ---
As I said earlier I'm working on Antergos (on this day) with the newest Plasma
(5.6.5), with the newest KF (5.23), the newest Qt 5 (5.6.1) and KDE
Applications 16.04.2.

I use konsole very often with running couple of cards (for example: pure
terminal, couple mc, and sometime mc run with root privileges - executed like
this: "sudo mc %s"). Konsole is opened every time when I work in Plasma desk.,
so I expect that after rerun of the system it will be restored. Unfortunately
doesn't. Recently I observed that sometimes is happened that konsole is not
restored when I run systemem next day. I suppose that this is related with
running root session ("sudo mc %s" session) in moment of system close or even
run and closed root session. As I remember, almost every time when I run such
session, konsole will be not restored, at all. This is a bit annoying, because
konsole has no option "Load saved/recent session/cards". Issue seems to be
happen randomly.
In my every Plasma session I run always one or more KWrite application(s), and
they are restored every time.

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

[kate] [Bug 363375] Spelling call causes drawing over status bar - incorrect words are not highlighted

2016-05-21 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
Created attachment 99121
  --> https://bugs.kde.org/attachment.cgi?id=99121=edit
status bar after use Spelling option

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

[kate] [Bug 363375] New: Spelling call causes drawing over status bar - incorrect words are not highlighted

2016-05-21 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 363375
   Summary: Spelling call causes drawing over status bar -
incorrect words are not highlighted
   Product: kate
   Version: Git
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

I open kwrite or kate. I have selected default language.
I wrote couple incorrect words and called spelling.
Automatic Spell Checking is turned on and nothing is highlighted.
Calling...
1. Option: Tools -> Spelling -> Spelling... - nothing happened after first use
in case of next is showing dialog "Check spelling" with OK button and on status
bar is drawing message about unknown word overlapping existing information.
Please check attached screen.
2. Option: Tools -> Spelling -> Spelling (from cursor) - message about unknown
word is drawing on status bar overlapping existing information. Please check
attached screen.

Change of dictionary doesn't help at all.


Reproducible: Always

Steps to Reproduce:
1. run kate/kwrite
2. write something incorrect in editor
3. call any Spelling option

Actual Results:  
drawing error messages over statusbar

Expected Results:  
incorrect words should be highlighted and in moment of calling Spelling should
be appeared some helper dialog

KWrite/Kate ver. 16.04.1;  KFrameworks 5.22; Plasma 5.6.4

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-05-19 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #55 from Piotr Mierzwinski  ---
(In reply to Wolfgang Bauer from comment #54)

> > I don't how it's possible that restoring Firefox is working in openSUSE :/.
> > You or someone else told about it. 
> > Is it possible that they somehow patched plasma-workspace?
> 
> No.
> 
> But now that I come to think of it, openSUSE's Firefox (and Thunderbird)
> packages include some custom KDE(4) integration. This *might* make the
> difference between it being restored in openSUSE but not in other
> distributions...
> Though I'm not sure if that detail is really relevant here, the integration
> is more about using the KDE file dialog and certain KDE settings (like
> preferred applications and proxy settings), things like that.

Yes. I agree. It seems to be not related.  So my question still remains opened
:/..

> > If you are using openSUSE then could you please check at least new Opera, if
> > it will be restore after relogin.
> 
> Well, I did install Opera now (37.0.2178.32), and indeed it is not restored
> (nor saved to ksmserverrc).
> 
> But I tried with KDE4 too, and it isn't restored/saved there as well.

I can confirm. I tested it in Mageia 5 and new Opera is not restored as well.

BTW.
Recently, using Antergos I observed that konsole is restored randomly. Every
few running (of Plasma) is not restored. It looks similar to behavior Kubuntu
15.x with Plasma 5.4.x

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

2016-05-19 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
I made next test.
Being in System Settings I switched from "Restore previous session" to "Restore
manually saved session" (in Plasma eng. version options might be call a bit
different, I translated from polish).
After that in K menu in "Leave" tab I found option "Save session". I clicked it
and checked ksmserverrc file - last modification date was changed.
Unfortunately turned out that neither Thunderbird nor Opera is not saved. After
that I run Firefox and repeated procedure. And again in ksmserverrc file there
wasn't nothing about Firefox, Thunderbird and Opera :(. Nothing about any GTK
application has been saved.

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

[kdevelop] [Bug 363237] Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code

2016-05-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

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

[kdevelop] [Bug 363237] New: Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code

2016-05-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 363237
   Summary: Breakpoints (Breakpoints View) are not updated after
removing/adding couple lines of code
   Product: kdevelop
   Version: git master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
CC: niko.s...@gmail.com

I have set breakpoint on begin, in the middle and on end of some C/C++ file.
Being in the middle of code I remove/add couple lines of code. Now I check
breakpoints view and I can see that breakpoint(s) placed after removed/added
code still points to the same row number. I click into it and as I expect I'm
moving to wrong line. Whereas breakpoint icon placed on left bar is set next to
correct row. 
In this moment changing breakpoint(s) by clicking in correct place sometimes
might provide to CRASH.


Reproducible: Always

Steps to Reproduce:
1. Open C/C++ file
2. Set couple of breakpoints
3. Delete couple of lines of code placed before any breakpoint(s)

Actual Results:  
All breakpoints placed after removed code now indicate invalid lines.

Expected Results:  
Number of row for all breakpoints placed after removed code should be properly
updated (in Breakpoints view).

KDevelop and KDevplatform cloned at 14.05.2016 from brach 5.0
Bug is related with #353101, but it refers to old KDevelop line (in this case
4.7.1)

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-05-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #53 from Piotr Mierzwinski  ---
(In reply to Wolfgang Bauer from comment #52)
> PS: there's another thing you could try to possibly narrow down the issue:
> Switch to "Start with a previously saved session" in
> systemsettings5->Startup and Shutdown->Session Management, manually save the
> session (a corresponding entry should appear in the application menu in the
> "Leave" tab  or in "Powermanagement/Session" if using Kicker after you
> logged out and in again), and see whether your applications are
> saved/restored correctly then.
>
OK. I switched from "Restore previous session" to "Restore manually saved
session" (in Plasma eng. version options might be call a bit different, I
translated from polish). And in "Leave" tab I found option "Save session". I
clicked it and checked ksmserverrc file - last modification date was changed.
Unfortunately turned out that neither Thunderbird nor Opera is not saved. After
that I run Firefox and repeated procedure. And again in ksmserverrc file there
wasn't nothing about Firefox, Thunderbird and Opera :(. Nothing about any GTK
application has been saved.

I don't how it's possible that restoring Firefox is working in openSUSE :/. You
or someone else told about it. 
Is it possible that they somehow patched plasma-workspace?

If you are using openSUSE then could you please check at least new Opera, if it
will be restore after relogin.

> This worked even with Qt5/KF5 applications before the problem was solved
> there.

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-05-17 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #50 from Piotr Mierzwinski  ---
(In reply to Wolfgang Bauer from comment #48)
> (In reply to Piotr Mierzwinski from comment #47)
> > None of the tested by me applications are not restored after
> > relogin/restart.
> 
> Where's the problem then?
Problem is that applications mentioned in next sentence are not restored after
relogin. 

> I suppose there is a typo in there... ;-)
Sorry for typo. English grammar is not my strength, se better would be when
"are" has been replaced with "were" or usage: "there are not restored".

> > I tested: Firefox, Thunderbird and new Opera. I think all
> > of them are based on GTK2. 
> 
> Actually not.
> At least Firefox can be build against GTK3 since a while and I think at
> least some distributions do that (openSUSE not, yet).
OK. About Firefox you are right. I retested it again and I can say that in
Antergos Firefox is built using GTK3.

> So this might just be your point of regression...
The regression is that none of GTK2 and GTK3 applications there are not
restored. This is regression comparing to previous Plasma, because In ver.
5.5.x it was working. I tested  Kubuntu 16.04. BTW in Plasma 5 provided by this
distribution applications based on KF are not restored. I'm not going to evolve
this topic. Anyway they plan update to Plasma 5.6.x.

> No idea about the others though.
But I'm sure that the last two were built using GTK2. My test was following. I
changed "Style of GNOME application" in "System Settings" and just restarted
all tested applications.

> > All tested by me KF applications (konsole,
> > kwrite, dolphin) are restored correctly (including virtual desktop number).
> 
> This proves IMHO that your problem is unrelated to *this* bug report, or the
> other one I marked this as duplicate of, which is about a problem in Qt5 as
> explained.
Subject is "Plasma doesn't restore everything after a reboot". So maybe is too
general. Author reported this bug wrote about problem with Konsole, Dolphin,
Kate and restoring them including their opened tabs. After several posts
someone started typing about most general problems with restoring other
applications. Never mind.
So maybe my problem is only partially related to reported problem.

> > In Plasma 5.5.4 (ksmserver probably has the same version) Firefox and
> > Thunderbird were restored correctly.
> 
> There has been no change to ksmserver (except see above), so another prove
> that this is not the same bug.
So where is placed the bug? In Plasma 5.5.4 GTK applications are restored
correctly and in 5.6.4 don't.
>From my perspective it looks like some informations necessary to restore GTK
based applications are not saved into ksmserverrc. Even after hardcoded them in
this file, they exist only till first relogin/restart. After that they
disappear. How it might be explained?

> > Looking what you are saying: 'I have heard of other users having problems
> > with Firefox in this regard since upgrading Plasma to 5.6 (or the beta).". I
> > also other persons also saying about problems, so maybe this is plasma 5.6.x
> > (ksmserver) bug.
> 
> As mentioned, ksmserver hasn't been changed between 5.5 and 5.6.
> Except for this:
> https://quickgit.kde.org/?p=plasma-workspace.
> git=commit=5f0ca1305db4a925dbdbf927f541497be334feff
So I'm asking again. What happened? Developers of couple distributions made
some mistake?
In the past I tested also KaOS with Plasma 5.4.x and later after update to
Plasma 5.6.x. Testing the newest KaOS I observe the same issue like in
Antergos. KaOS doesn't base on Arch packages instead of Antergos.
I wonder what will bring Plasma 5.6.4 (currently tested) in Kubuntu 16.04. I
mean of course issue of restoring GTK and KF5 applications.

> According to the commit message it shouldn't be a problem though...
For me it is hard to say if XSM technology could affect on restoring GTK
applications. I don't know what testes made author this fix after applying it
in code.
I mean simple test: whether GTK and KF applications are restored or not.
I and others can say only that it stopped work.

> If you are able to build plasma/ksmserver from source, I would recommend to
> do so with this patch reverted and see if it works then.
This is the easiest way to prove/not prove that author of this patch didn't
retest your fix properly.
Yes. I'm able to build plasma-workspace package, what contains ksmserver. Maybe
I will make such test in the future.

> > And if for you and for Paolo Carlini it is working then to who should to
> > report the bug?
> 
> Good question, I don't know really.
> Maybe GTK3, or the applications affected.
As I mentioned issue is related to GTK2 (new Opera, thunderbird) and GTK3
(Firefox).

> Or, as it might be a ksmserver bug after all (I never ruled that out), file
> a *new* bug report here.
Some time ago (May 4th) I just reported it here in bug: 362671 (no answer).
I reported it also in Antergos forum (with no

[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't expand automatically vertically

2016-05-16 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Summary|In debug session "Variable  |In debug session "Variable
   |ToolTip" doesn't resize |ToolTip" doesn't expand
   |vertically  |automatically vertically

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

[kdevelop] [Bug 362485] After refresh editor (F5) already set breakpoint(s) are disappearing

2016-05-16 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Summary|Debug mode. After refresh   |After refresh editor (F5)
   |editor (F5) already set |already set breakpoint(s)
   |breakpoint(s) are   |are disappearing
   |disappearing|

--- Comment #2 from Piotr Mierzwinski  ---
I happens also in Code perspective.
Tested with KDevelop and KDevplatform cloned from 5.0 branch at 14.05.2016

Steps to Reproduce:
1. Open any cpp file
2. Set breakpoint
3. Refresh editor (press  F5)

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

[ksmserver] [Bug 362671] New: GTK applications are not restored in Plasma 5.6.x after relogin

2016-05-04 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 362671
   Summary: GTK applications are not restored in Plasma 5.6.x
after relogin
   Product: ksmserver
   Version: 5.6.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

None of gtk applications tested by me are not restored after relogin/restart
Plasma 5.6.x.

I tested: Firefox, Thunderbird and new Opera. I think all of them are based on
GTK2. All tested by me KF applications (konsole, kwrite, dolphin) are restored
correctly (including virtual desktop #number).

I'm not sure if this is ksmserver problem or integration of Plasma in Antergos
or KaOS. I noticed that in Mageia Cauldron (not stable, but based on the newest
Qt and newest Plasma) only thunderbird is restored, but no KF applications).
Here (in Antergos and KaOS) only KF applications are restored.

I made also some test to be sure this is no GTK problem. This test was relying
on hardcoding in ksmserverrc file properly lines that forced running
thunderbird. Result. After login (because changes I made in text terminal)
thunderbird has been run. Unfortunately after relogin thunderbird has not been
run, because during closing of the session my entry disappeared from
ksmserverrc file.

I read that for someone using openSUSE Leap it's working :/. This is strange.
Check this https://bugs.kde.org/show_bug.cgi?id=343518

Reproducible: Always

Steps to Reproduce:
1. Login to plasma 5.6.x
2. run konsole, kwrite, thunderbird, firefox or opera
3. logout from session
4. login again

Actual Results:  
After relogin restored are only konsole and kwrite

Expected Results:  
Should be run all applications working before logout, so in this case: konsole,
kwritem thunderbird or opera

Tested on Antergos distribution (this is rolling) with all update on a day of
writing this bug report.
 Qt 5.6.0, Plasma 5.6.3 and KDE Frameworks 5.21.0, kernel 4.5.1
Tested also on KaOS with recent updates with the same result.

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

[kdevelop] [Bug 362486] New: Debug mode. After refresh editor (F5) already set shortcut (F10) is restored to default

2016-04-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 362486
   Summary: Debug mode. After refresh editor (F5) already set
shortcut (F10) is restored to default
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
CC: niko.s...@gmail.com

Being in debug mode. I change key shortcut F10, because is ambigous (F10 also
exists in Kate) to Stop Over function. Starting this moment this shortcut is
working. I refresh editor window pressing F5. When I try to use F10 then this
shortcut doesn't work like before refresh.


Reproducible: Always

Steps to Reproduce:
1
2
3


Actual Results:  
Set in Debug mode shortcut is restored to default value.

Expected Results:  
Set in Debug mode shortcut(s) should not be restored to default value.

My system is based on: Qt-5.6.0, Plasma-5.6.3, KDE Frameworks 5.21. Antergos
(Arch based) distribution.
KDevelop and KDevplatform cloned from 5.0 branch at 26.04.2016

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

[kdevelop] [Bug 362485] Debug mode. After refresh editor (F5) already set breakpoint(s) are disappearing

2016-04-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #1 from Piotr Mierzwinski  ---
Description of problem:
Being in debug mode, and having set some breakpoint(s), invoking F5 (refresh
editor) made that all breakpoints disappearing (from editor window and from
Breakpoints view).

Reproducible: Always

Steps to Reproduce:
1
2
3

Actual Results:  
All breakpoints disappearing after refresh of editor window

Expected Results:  
The breakpoints should not disappear after refresh of editor window

Additional Information:
My system is based on: Qt-5.6.0, Plasma-5.6.3, KDE Frameworks 5.21. Antergos
(Arch based) distribution.
KDevelop and KDevplatform cloned from 5.0 branch at 26.04.2016

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

[kdevelop] [Bug 362485] Debug mode. After refresh editor (F5) already set breakpoint(s) are disappearing

2016-04-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

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

[kdevelop] [Bug 362485] New: Debug mode. After refresh editor (F5) already set breakpoint(s) are disappearing

2016-04-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 362485
   Summary: Debug mode. After refresh editor (F5) already set
breakpoint(s) are disappearing
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
CC: niko.s...@gmail.com

Being in debug mode, and having set some breakpoint(s), invoking F5 (refresh
editor) made that all breakpoints disappearing (from editor window and from
Breakpoints view).

Reproducible: Always

Steps to Reproduce:
All breakpoints disappearing after refresh of editor window

Actual Results:  
The breakpoints should not disappear after refresh of editor window

Expected Results:  
My system is based on: Qt-5.6.0, Plasma-5.6.3, KDE Frameworks 5.21. Antergos
(Arch based) distribution.
KDevelop and KDevplatform cloned from 5.0 branch at 26.04.2016

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

[kdevelop] [Bug 362483] Helper "Adapt Signature" disappears when I try to enter parameter name

2016-04-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

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

[kdevelop] [Bug 362483] New: Helper "Adapt Signature" disappears when I try to enter parameter name

2016-04-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 362483
   Summary: Helper "Adapt Signature" disappears when I try to
enter parameter name
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

I have such method implementation:
void InputTextDialog::slotRadioButtonClicked()
I put cursor between of the brackets and I start typying: "bool", so I in
result I get something like this:
void InputTextDialog::slotRadioButtonClicked( bool )
Cursor is placed after "l" letter in bool word. I get helper "Adapt Signature".
Great, but I didn't write yet parameter name. So I continue typing with: " b".
Helper "Adapt Signature" disappears and don't want to display again - even when
I change parameter name.


Reproducible: Always


Actual Results:  
"Adapt Signature" helper disappears when I try to enter parameter name

Expected Results:  
"Adapt Signature" helper should not disappear when I try to enter parameter
name

My system is based on: Qt-5.6.0, Plasma-5.6.3, KDE Frameworks 5.21. Antergos
(Arch based) distribution.
KDevelop and KDevplatform cloned from 5.0 branch at 26.04.2016

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

2016-04-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #47 from Piotr Mierzwinski  ---
Antergos system with Qt 5.6.0, Plasma 5.6.3 and KDE Frameworks 5.21.0 with the
newest updates on today (writing this message).

None of the tested by me applications are not restored after relogin/restart. I
tested: Firefox, Thunderbird and new Opera. I think all of them are based on
GTK2. All tested by me KF applications (konsole, kwrite, dolphin) are restored
correctly (including virtual desktop number).

In Plasma 5.5.4 (ksmserver probably has the same version) Firefox and
Thunderbird were restored correctly. The problem only was with new Opera. I
tested it on Kubuntu 15.10. In version 5.6, the most likely, it has been
broken. So I don't think so that this is GTK problem. I think this is again
some regression. Second argument it might be ksmserver but is following. I made
some test relying on hardcoding in ksmserver configuration file properly lines
that forced running thunderbird. Result. After login thunderbird has been run.
Unfortunately after relogin thunderbird not run, because during closing the
session my entry has been removed from ksmserver configuration file.
Looking at this situation I wonder are there any regression tests made (by
ksmserver developers) for this case :/. Or maybe here are guilty persons
preparing Plasma packages in Arch/Antergos (this distribution based on Arch
repository). I don't know.

@Wolfgang Bauer
Looking what you are saying: 'I have heard of other users having problems with
Firefox in this regard since upgrading Plasma to 5.6 (or the beta).". I also
other persons also saying about problems, so maybe this is plasma 5.6.x
(ksmserver) bug.
And if for you and for Paolo Carlini it is working then to who should to report
the bug?

I can add that the environment itself is pretty stable. I'm using it couple of
weeks and I didn't observe any crash.

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

[kdevelop] [Bug 361693] New: Crash when removing breakpoint in Review mode (commit action)

2016-04-12 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 361693
   Summary: Crash when removing breakpoint in Review mode (commit
action)
   Product: kdevelop
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Application: kdevelop (4.90.92)

Qt Version: 5.5.1
Frameworks Version: 5.21.0
Operating System: Linux 4.5.0-040500-generic x86_64
Distribution: KDE neon on 15.10

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

KDevelop crashed when I tried to remove breakpoint in Review mode (commit
action).

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6799194800 (LWP 31330))]

Thread 17 (Thread 0x7f677c424700 (LWP 31332)):
#0  0x7f67962ee88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f678a94cbd2 in ?? () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f678a94e74f in xcb_wait_for_event () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f677e7967e9 in ?? () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f67969e4a6e in ?? () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f678f9bd6aa in start_thread (arg=0x7f677c424700) at
pthread_create.c:333
#6  0x7f67962f9e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f6770867700 (LWP 31339)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f67969e5c46 in QWaitCondition::wait(QMutex*, unsigned long) () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f67944124e8 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x38679a0) at
/home/piotrek/kf5/src/kdevplatform/language/duchain/duchain.cpp:281
#3  0x7f67969e4a6e in ?? () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f678f9bd6aa in start_thread (arg=0x7f6770867700) at
pthread_create.c:333
#5  0x7f67962f9e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f6766a8f700 (LWP 31341)):
[KCrash Handler]
#31 0x7f67962ee88d in poll () at ../sysdeps/unix/syscall-template.S:81
#32 0x7f678ee321ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x7f678ee322fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x7f6796c1c4ef in
QEventDispatcherGlib::processEvents(QFlags) ()
from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#35 0x7f6796bc350a in
QEventLoop::exec(QFlags) () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x7f67969dfac4 in QThread::exec() () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#37 0x7f67969e4a6e in ?? () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x7f678f9bd6aa in start_thread (arg=0x7f6766a8f700) at
pthread_create.c:333
#39 0x7f67962f9e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f6757bc6700 (LWP 31344)):
#0  0x7f678ee76869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f678ee321d2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f678ee322fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6796c1c50b in
QEventDispatcherGlib::processEvents(QFlags) ()
from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6796bc350a in
QEventLoop::exec(QFlags) () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f67969dfac4 in QThread::exec() () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6794504d6b in KDevelop::CompletionWorkerThread::run
(this=0x4151b60) at
/home/piotrek/kf5/src/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f67969e4a6e in ?? () from
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f678f9bd6aa in start_thread (arg=0x7f6757bc6700) at
pthread_create.c:333
#9  0x7f67962f9e9d in clone

[kdevelop] [Bug 358799] Function "Update declaration signature" breaks declaration if inside there is default set parameter

2016-03-09 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #2 from Piotr Mierzwinski  ---
Created attachment 97806
  --> https://bugs.kde.org/attachment.cgi?id=97806=edit
Settings of "Source Formatter" - tab Other

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

[kdevelop] [Bug 358799] Function "Update declaration signature" breaks declaration if inside there is default set parameter

2016-03-09 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
And the second example (met today):

I have declaration of method like in below code:
namespace MyNameSpace {
..
class MyClass : public AnotherClass
{
Q_OBJECT
public:
void  init( QSettings *pSettings, QWidget *pParent );
...

Definition looks like this:
void MyClass::init( QSettings *pSettings, QWidget *pParent )
{
..
}

In declaration I insert on end of parameter list following string: ", bool
bInvokeDetection=false", and then declaration looks like this:
void  init( QSettings *pSettings, QWidget *pParent, bool
bInvokeDetection=false );
I get helper "Adapt signature: Adapt definition signature" and I select "1".

Actual Results:
In result in definition file I get following change:

void MyNameSpace::MyNameSpace::MyClass::init(QSettings* pSettings, QWidget*
pParent, bool bInvokeDetection)

// body
}

As you can see. Definition has been totally broken. Even opening brace
disappeared.
Skipping that Source Formatter doesn't work (in attachment my setting).

Expected Results:
In result I expected something like this:
void MyClass::init( QSettings *pSettings, QWidget *pParent, bool
bInvokeDetection )
{
// body
}


Tested with KDevelop and KDevplatform cloned at February 28th, 2016 after 10pm
(branch 5.0).

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

[systemsettings] [Bug 360130] System Settings crashes after opening "Look of workspace"

2016-03-05 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Summary|System Settings crashing|System Settings crashes
   |after opening "Look of  |after opening "Look of
   |workspace"  |workspace"

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

[systemsettings] [Bug 360130] System Settings crashing after opening "Look of workspace"

2016-03-05 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com
Summary|Crash after open System |System Settings crashing
   |Settings adn selectin "Look |after opening "Look of
   |of workspace"   |workspace"

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

[systemsettings] [Bug 360130] New: Crash after open System Settings adn selectin "Look of workspace"

2016-03-05 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 360130
   Summary: Crash after open System Settings adn selectin "Look of
workspace"
   Product: systemsettings
   Version: 5.5.95
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Application: systemsettings5 (5.5.95)

Qt Version: 5.6.0
Frameworks Version: Unknown
Operating System: Linux 4.4.4-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
I've opened System Settings, selected "Look of workspace" and after ~2 sec. it
crashed.

-- Backtrace:
Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb96587e800 (LWP 21579))]

Thread 4 (Thread 0x7fb954336700 (LWP 21580)):
#0  0x7fb961f4ff5d in poll () at /lib64/libc.so.6
#1  0x7fb95ff03ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fb95ff05697 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fb956866809 in QXcbEventReader::run() (this=0xb103c0) at
qxcbconnection.cpp:1313
#4  0x7fb962641649 in QThreadPrivate::start(void*) (arg=0xb103c0) at
thread/qthread_unix.cpp:340
#5  0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0
#6  0x7fb961f5bdad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fb94bfff700 (LWP 21581)):
#0  0x7fb95f1b3a64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fb95f170409 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fb95f17051c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fb962856a4b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb9440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fb96280234a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb94bffeda0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7fb96263ca3c in QThread::exec() (this=this@entry=0x7fb965a2dd40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#6  0x7fb9659bd3e5 in QDBusConnectionManager::run() (this=0x7fb965a2dd40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#7  0x7fb962641649 in QThreadPrivate::start(void*) (arg=0x7fb965a2dd40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#8  0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0
#9  0x7fb961f5bdad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb942e7a700 (LWP 21586)):
#0  0x7fb95f1b3a64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fb95f16fa30 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7fb95f170343 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fb95f17051c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fb962856a4b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb93c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fb96280234a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb942e79db0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fb96263ca3c in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fb960fda835 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7fb962641649 in QThreadPrivate::start(void*) (arg=0xf3b5e0) at
thread/qthread_unix.cpp:340
#9  0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0
#10 0x7fb961f5bdad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb96587e800 (LWP 21579)):
[KCrash Handler]
#6  0x7fb941dd9eb2 in QQuickStyleItem::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) (this=) at
/usr/lib64/qt5/include/QtQuick/5.6.0/QtQuick/private/qquickitem_p.h:877
#7  0x7fb941dd9eb2 in QQuickStyleItem::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) (this=0x10a2050, node=0x0) at
Private/qquickstyleitem.cpp:1830
#8  0x7fb96129f460 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) ()
at /lib64/libQt5Quick.so.5
#9  0x7fb96129fc50 in QQuickWindowPrivate::updateDirtyNodes() () at
/lib64/libQt5Quick.so.5
#10 0x7fb9612a0bee in QQuickWindowPrivate::syncSceneGraph() () at
/lib64/libQt5Quick.so.5
#11 0x7fb961270e56 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
() at /lib64/libQt5Quick.so.5
#12 0x7fb961272420 in
QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*) () at
/lib64/libQt5Quick.so.5
#13 0x7fb963746c5b in QWindow::event(QEvent*) (this=0x102f0a0,
ev=) at kernel/qwindow.cpp:2096
#14 0x7fb9612a9c65 in QQuickWindow::event(QEvent*) () at
/lib64/libQt5Quick.so.5
#15 0x7fb963d5440c in

[kdevelop] [Bug 359970] Methods of QSettings (Qt4) class are not parsed

2016-03-02 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||piotr.mierzwin...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Piotr Mierzwinski  ---
Sorry. I close bug report due to my fault :(.

When I added proper paths into "Project Configuration -> Language support ->
Includes/Imports" parsing started work in mini test project, but I don't know
why in big project (even after rebuild of cache) issue still persists :(.
Probably some different parsing bugs block parsing these members :/. Neither
refresh nor reopen file doesn't  help. I observed that every methods which are
inherited from QWidget (i.e.: setEnabled, setFocus) are correctly parsed, other
don't. It refers also to other classes (like QLabel, QTimer, QPushButton) not
only mentioned QSettings.

Saying "proper paths" I meant paths to headers instead of paths to files
contains bunch of headers inside.
Proper paths for Kubuntu 15.10.
/usr/include/qt4/QtCore/
/usr/include/qt4/QtGui/
/usr/include/qt4/QtNetwork/

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

[kdevelop] [Bug 359970] New: Methods of QSettings (Qt4) class are not parsed

2016-03-01 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 359970
   Summary: Methods of QSettings (Qt4) class are not parsed
   Product: kdevelop
   Version: 4.90.91
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

There is simple code like below:
QSettings st("Foo");
QString sValue = st.value("key").toString();
st.setValue("key", "value");
sValue.remove("a");

When I move mouse cursor over "value" or "setValue" then nothing happen, and
this string is black.
When I do the same for "remove" then I get helper tooltip and this string is
colored.

It looks like QSettings methods would not be parsed.

Reproducible: Always


Actual Results:  
Not parsed QSettings methods.

Expected Results:  
QSettings methods should parsed.

I also added path to QSettings class into" Project Configuration -> Language
support -> Includes/Imports", but it didn't help. BTW. Cache regenerated took
much more time than after KDevelop restart.
Till now I had only paths to files with bunch of includes related with QtCore,
QtGui and QtNetwork.

Tested with KDevelop and KDevplatform cloned at February 28th, 2016 after 10pm
(branch 5.0).

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

[kdevelop] [Bug 359942] Files ui_CLASSNAME.h generated during building are not parsed and as result their members are not highlighted properly

2016-03-01 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #3 from Piotr Mierzwinski  ---
Project is building without errors. Includes (ui_CLASSNAME.h) are generated
during building, probably on begin.
I understand that error what I noticed is inevitable, but the problem is that
all of these files are not reparsed later. It happened in KDevelop 4.7.x. For
me it looks like regression.

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

[kdevelop] [Bug 357407] No semantic syntax highlighting due to "libclang: crash detected during parsing"

2016-02-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #7 from Piotr Mierzwinski  ---
Some kind of proof (existing the C files):
$ ls -l
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmime.c
-rw-rw-r-- 1 piotrek piotrek 21203 lis 24 17:23
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmime.c
$ ls -l
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmimeparent.c
-rw-rw-r-- 1 piotrek piotrek 4812 lis 24 17:23
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmimeparent.c
$
$ ls -l
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build/libs/xdgmime/CMakeFiles/qtcmd2xdgmime.dir/xdgmime.c.o
-rw-rw-r-- 1 piotrek piotrek 40688 lut 29 00:40
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build/libs/xdgmime/CMakeFiles/qtcmd2xdgmime.dir/xdgmime.c.o
$ ls -l
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build/libs/xdgmime/CMakeFiles/qtcmd2xdgmime.dir/xdgmimeparent.c.o
-rw-rw-r-- 1 piotrek piotrek 2 lut 29 00:40
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build/libs/xdgmime/CMakeFiles/qtcmd2xdgmime.dir/xdgmimeparent.c.o

And one more thing. When you open attached text file you will notice that on
end are errors referring to not existing files. For this please check bug
report: Bug 359942

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

[kdevelop] [Bug 357407] No semantic syntax highlighting due to "libclang: crash detected during parsing"

2016-02-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Version|4.90.90 |4.90.91

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

[kdevelop] [Bug 359942] Files ui_CLASSNAME.h generated during building are not parsed and as result their members are not highlighted properly

2016-02-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
Created attachment 97616
  --> https://bugs.kde.org/attachment.cgi?id=97616=edit
kdevelop_libclang_crashes_20160229 KDEV_CLANG_DISPLAY_DIAGS=1

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

[kdevelop] [Bug 359942] New: Files ui_CLASSNAME.h generated during building are not parsed and as result their members are not highlighted properly

2016-02-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 359942
   Summary: Files ui_CLASSNAME.h generated during building are not
parsed and as result their members are not highlighted
properly
   Product: kdevelop
   Version: 4.90.91
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Before running KDevelop I exported variable "KDEV_CLANG_DISPLAY_DIAGS=1" and
removed kdevduchain cache. In attached file I put the output generated by
KDevelop just after loading when parsing finished.

When you open attached text file you will be able to notice that on end there
are errors referring to not existing files. Example:
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/widgets/multiprogressdialog.h:22:10:
fatal error: 'ui_multiprogressdlg.h' file not found
/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/widgets/mediacontrolwidget.h:22:10:
fatal error: 'ui_mediacontrolwidgetgui.h'file not found

This is because both of them will be created during compilation/building the
project. In the project there is a class (header file) where such file is
included and class inherits by class located in ui_CLASSNAME.h.

For example I have such file multiprogressdialog.h contains:
#include "ui_multiprogressdlg.h"
#include 

class MultiProgressDialog : public QDialog, Ui::MultiProgressDlg
{
...
}
whilst:
  Ui::MultiProgressDlg is located in ui_multiprogressdlg.h

In MultiProgressDialog I'm using members from MultiProgressDlg. Unfortunately
all of these members are not parsed, and as a result not highlighted. As far as
remember in KDevelop 4.7.x when project has been rebuild then all of these
members were parsed and properly highlighted.

Note.
Above convention is used in Qt4 projects. I'm not aware whether the same is
used in Qt5 projects.

Reproducible: Always


Actual Results:  
Members from ui_* header generated during project building are not parsed at
all

Expected Results:  
Members from ui_* header generated during project building should be parsed

Tested with KDevelop and KDevplatform cloned at February 28th, 2016 after 10pm
(branch 5.0).

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

[kdevelop] [Bug 357407] No semantic syntax highlighting due to "libclang: crash detected during parsing"

2016-02-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #6 from Piotr Mierzwinski  ---
Every C files exist, are valid, well-formed and are used in the project. I
build from them dynamic library and link with main binary. All of them coming
from: git://anongit.freedesktop.org/xdg/xdgmime

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

[kdevelop] [Bug 357407] No semantic syntax highlighting due to "libclang: crash detected during parsing"

2016-02-29 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #5 from Piotr Mierzwinski  ---
Created attachment 97611
  --> https://bugs.kde.org/attachment.cgi?id=97611=edit
kdevelop_libclang_crashes_20160229 KDEV_CLANG_DISPLAY_DIAGS=1

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

[kdevelop] [Bug 357407] No semantic syntax highlighting due to "libclang: crash detected during parsing"

2016-02-28 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #2 from Piotr Mierzwinski  ---
I tested KDevelop and KDevplatform cloned at February 28th, 2016 after 10pm
(branch 5.0).
Before run of newly built KDevelop I cleaned kdevduchain cache.
Settings in this test:
Configure KDevelop -> CMake
* "Default generator" = "Unix Makefiles"
Project configuration:
* CMake Variable: CMAKE_MAKE_PROGRAM points to "/usr/bin/make"

I noticed crashes only for files located in "build/CMakeFiles" (check
attachment). Second crashing thing are files in C used in my project. 
Below please find part of output produced by KDevelop during running:

libclang: crash detected during parsing: {
  'source_filename' :
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build/CMakeFiles/3.2.2/CompilerIdCXX/CMakeCXXCompilerId.cpp'
  'command_line_args' : ['-ferror-limit=100', '-fspell-checking',
'-Wdocumentation', '-Wunused-parameter', '-Wunreachable-code', '-Wall',
'-std=c++11', '-nostdinc', '-nostdinc++', '-xc++', '-isystem',
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/share/kdevclangsupport/wrappedQtHeaders',
'-isystem',
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/share/kdevclangsupport/wrappedQtHeaders/QtCore',
'-include/usr/include/qt4/Qt/QtCore', '-include/usr/include/qt4/Qt/QtGui',
'-include/usr/include/qt4/Qt/QtNetwork',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/c++/5',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/x86_64-linux-gnu/c++/5',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/c++/5/backward',
'-isystem/usr/local/include',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/llvm-3.6/lib/clang/3.6.2/include',
'-isystem/usr/include/x86_64-linux-gnu', '-isystem/usr/include', '-imacros',
'/tmp/kdevelop.yJ4066'],
  'unsaved_files' : [],
  'options' : 45,
}
kdevelop(4066)/(default) unknown: clang_parseTranslationUnit2 return with error
code 2
kdevelop(4066)/(default) unknown:   (start KDevelop with
`KDEV_CLANG_DISPLAY_DIAGS=1 kdevelop` to see more diagnostics)
kdevelop(4066)/(default) unknown: Failed to parse translation unit:
"/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build/CMakeFiles/3.2.2/CompilerIdCXX/CMakeCXXCompilerId.cpp"
libclang: crash detected during parsing: {
  'source_filename' :
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmime.c'
  'command_line_args' : ['-ferror-limit=100', '-fspell-checking',
'-Wdocumentation', '-Wunused-parameter', '-Wunreachable-code', '-Wall',
'-std=c++11', '-nostdinc', '-nostdinc++', '-xc++', '-isystem',
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/share/kdevclangsupport/wrappedQtHeaders',
'-isystem',
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/share/kdevclangsupport/wrappedQtHeaders/QtCore',
'-include/usr/include/qt4/Qt/QtCore', '-include/usr/include/qt4/Qt/QtGui',
'-include/usr/include/qt4/Qt/QtNetwork',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/c++/5',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/x86_64-linux-gnu/c++/5',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/c++/5/backward',
'-isystem/usr/local/include',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/llvm-3.6/lib/clang/3.6.2/include',
'-isystem/usr/include/x86_64-linux-gnu', '-isystem/usr/include', '-imacros',
'/tmp/kdevelop.yJ4066'],
  'unsaved_files' : [],
  'options' : 45,
}
kdevelop(4066)/(default) unknown: clang_parseTranslationUnit2 return with error
code 2
kdevelop(4066)/(default) unknown:   (start KDevelop with
`KDEV_CLANG_DISPLAY_DIAGS=1 kdevelop` to see more diagnostics)
kdevelop(4066)/(default) unknown: Failed to parse translation unit:
"/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmime.c"
libclang: crash detected during parsing: {
  'source_filename' :
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmimeparent.c'
  'command_line_args' : ['-ferror-limit=100', '-fspell-checking',
'-Wdocumentation', '-Wunused-parameter', '-Wunreachable-code', '-Wall',
'-std=c++11', '-nostdinc', '-nostdinc++', '-xc++', '-isystem',
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/share/kdevclangsupport/wrappedQtHeaders',
'-isystem',

[kdevelop] [Bug 298511] Change returned type of static function in it's definition (cpp file) made remove word "static" in it's declaration (header)

2016-02-06 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #7 from Piotr Mierzwinski  ---
And about current (today [06.02.2016] evening [after 10pm] cloned source from
origin/5.0 branch) version.
I retested it and here noting changed comparing to issue sent in the post made
at "2016-01-30 23:58:48 CET", so definition/declaration is not updated. I'm not
sure where is the issue :/.

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

[kdevelop] [Bug 298511] Change returned type of static function in it's definition (cpp file) made remove word "static" in it's declaration (header)

2016-02-06 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #6 from Piotr Mierzwinski  ---
[Kevin] @Piotr: It works for me using latest 5.0 branch. Are you sure?
I've retested it again using kdevelop-4.90.91 built by packager from Mageia
Cauldron distribution.
I can say that change of returned type of static function made in header file
works (cpp file is properly updated).

Only left minor bug(s).
After click in "1" on "Adapt signature" window/toolTip, this window still
visible on the screen and I expect that disappear. It doesn't happen when I
press shortcut "Alt+1" ("Adapt signature" disappear).
Second issue is that, in cpp definition noting happen after changing return
type.

[Kevin] Why do we have two bug reports for this to begin with? Marking as
duplicate. Please report on that one.
For me it was two things, because involved two behaviours (actions made by user
to get an error).
In bug 356179 "static" word was removed after removing last parameter in the
function/method (which was declared static). And here definition/declaration is
not updated after changing the type.

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

[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't resize vertically

2016-01-31 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Version|4.90.90 |4.90.91

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

[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't resize vertically

2016-01-31 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Summary|In debug session "Variable  |In debug session "Variable
   |ToolTip" doesn't resizing   |ToolTip" doesn't resize
   |vertically  |vertically

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

[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't resizing vertically

2016-01-31 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #2 from Piotr Mierzwinski  ---
Your welcome. This is only one thing what I can do now. Sorry.

Fixing requires more or less diving in source code and analyze how does it
work. I don't have so much time for this :(. You have a lot of experiences with
KDevelop code, so for you it's a lot easier.

Recently I discover one thing, maybe will be helpful. Namely, KDevelop beta1
(mentioned on your homesite and packaged in couple of distributions - KaOS,
Mageia Cauldron) doesn't have this bug. The same for bug 355159.

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

[kdevplatform] [Bug 358798] Source formatter every time selects language as "C"

2016-01-31 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #3 from Piotr Mierzwinski  ---
@Kevin. This is just regular bug report. Fixing the problem is not urgent for
me. I didn't mark it anywhere as important/urgent. Milian (in one of bug
report) told me, if I find any in sourceformatter then I might to report it.
I understand that release blockers are more important, and this bug doesn't
block release.
Would be nice if someone mark it as confirmed.

I know that any patches are highly appreciated. You told me about it earlier
(bug related with "crash in debugger"). Unfortunately I don't have so much time
to dive in not known source code, analyze how does it work, fix, test and
prepare patch. Sorry.
Anyway. I can report bugs. I hope this is helpful.

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

[plasmashell] [Bug 358076] Crash after try of getting context menu from one of system tray application by RMB

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com
Summary|Crash after try of getting  |Crash after try of getting
   |context menu from one of|context menu from one of
   |system try application by   |system tray application by
   |RMB |RMB

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

[kdevplatform] [Bug 358801] New: Formatter removes all white characters placed between type of function and its name

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 358801
   Summary: Formatter removes all white characters placed between
type of function and its name
   Product: kdevplatform
   Version: 4.90.91
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sourceformatter
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

In formatter configuration there is not option to configure whether formatter
should or not remove spaces between type of function and its name. I mean
"Other->Padding" box. And default behaviour is removing every white character
from this place. Example. 

Padding configuration as following: 
  Pad parenthesis: "Inside only"
  Add spaces after parenthesis headers: "Checked"  (tested also with "Not
checked")
  Add spaces around operators: "Not checked"

Declaration (header file):
void   foo( bool param );

Definition (cpp file):
void MyClass::foo( bool param )
{
if (param)
;
}

Being in definition I add new parameter, for example "bool a" in header of
definition of function, so result would looked like this: "void MyClass::foo(
bool param, bool a )".
"Update declaration signature" pops up and after pressing "Alt+1" I get
following modification in header file:
void foo( bool param, bool a );

As you can see the spaces placed between type of function and its name
disappeared.

Reproducible: Always

Steps to Reproduce:
1. Having function with default setting parameter add new one in definition of
function
2. In "Update declaration signature" press Alt+1


Actual Results:  
void foo( bool param, bool a );


Expected Results:  
void   foo( bool param, bool a );


KDevelop, KDevplatform cloned at 30.12.2016 (at evening) from 5.0 branch.

I observed also some strange behaviour with automatically invoking of "Update
declaration signature". Namely when I rolled back my changes in this way:
header file: Ctrl+Z, F5 (refresh)
cpp file: Cltr+Z, F5 (refresh)
then when I tried add new parameter again in definition of function header like
described above. I observed that "Update declaration signature" is popping up
just after when I finish type of parameter type, so here it's "bool" and when I
put parameter name then nothing happened. I waited couple of minutes. It looks
like "Update declaration signature" stopped work, because I tried do this also
in different function in the same file. KDevelop restart helps.

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

[kdevelop] [Bug 355356] Function "Adapt signature" doesn't work correct (renaming argument) for constructor of class

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #5 from Piotr Mierzwinski  ---
@Milian: Yes. Some times ago I configured "Source formatter" with my own
formatter. You mentioned me about this when I reported different bug. I found
some bug related with this function and soon I'm going to report it.

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

[kdevelop] [Bug 358799] New: Function "Update declaration signature" breaks declaration if inside there is default set parameter

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 358799
   Summary: Function "Update declaration signature" breaks
declaration if inside there is default set parameter
   Product: kdevelop
   Version: 4.90.91
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

I tried to add parameter to function which one had default set last parameter.
I added parameter in definition.
I'm not sure if what I got is correct behaviour or not, but I expected
something else :/.
Simple example. I have defined one function

Declaration (header file):
void foo( bool param=false );

Definition (cpp file)
void MyClass::foo( bool param )
{
if (param)
;
}

Being in definition I add new parameter, for example "bool a" in header of
definition of function, so result would looked like this:  "void MyClass::foo(
bool param, bool a )"
"Update declaration signature" pops up and after pressing "Alt+1" I get
following modification in header file

void foo( bool param = false, bool a = {} /* TODO */ );

This not what I expected.
I'm skipping here that formatting have not been met, despite I had defined one,
where "Add spaces around operators" wasn't set.

Reproducible: Always

Steps to Reproduce:
1. Having function with default setting parameter add new one in definition of
function
2. Made "Update declaration signature"


Actual Results:  
Together with new parameter is added such string: " = {} /* TODO */". Example:
void foo( bool param = false, bool a = {} /* TODO */ );

Expected Results:  
Default setting of parameter is removed and new parameter added. Example:
void foo( bool param, bool a );
and alternatively should be shown warning that "Current setting parameters
might be broke due to set default parameter. Do you want to continue?"

KDevelop, KDevplatform cloned at 30.12.2016 (at evening) from 5.0 branch.

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

[kdevelop] [Bug 298511] Change returned type of static function in it's definition (cpp file) made remove word "static" in it's declaration (header)

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

   Platform|Mandriva RPMs   |Kubuntu Packages
Version|git master  |4.90.91
  Component|Language Support: CPP   |Language Support: CPP
   ||(Clang-based)

--- Comment #3 from Piotr Mierzwinski  ---
In KDevelop 5.0 (beta2) it doesn't work at all :-(.

When I try to change returned type being in definition then nothing happen.
When I try to change returned type being in declaration then I'm getting
"Update definition signature" pop up, so I choose 1 (Alt+1) and nothing happen,
and "Update definition signature" still hangs on the screen.

KDevelop, KDevplatform cloned at 30.12.2016 (at evening) from 5.0 branch.

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

[kdevplatform] [Bug 358798] New: Source formatter every time selects language as "C"

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 358798
   Summary: Source formatter every time selects language as "C"
   Product: kdevplatform
   Version: 4.90.91
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sourceformatter
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

I think configuration of "Source formatter" it's not clear, because every time
when I open this option I can see that selected is "Language: C". I'm not sure
from where KDevelop knows that I use C, whereas I'm working on C++ project :-/.

And some idea.
I think would be nice to have "Source formatter" assigned to project, so
configured in project configuration. In KDevelop settings I would configured
the settings of "Source formatter" and in project configuration just set it. In
this moment KDevelop every time select "Language: C", but when I select "C++"
then on list below is highlighted last used formatter - for me newly defined.

Reproducible: Always


Actual Results:  
After defined/selected own "Source formatter" with different than C language -
every next invoking this option showing "Language: C".

Expected Results:  
After defined/selected own "Source formatter" with different than C language -
every next invoking this option should show selected language.

KDevelop, KDevplatform cloned at 30.12.2016 (at evening) from 5.0 branch.

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

[kdevelop] [Bug 355356] Function "Adapt signature" doesn't work correct (renaming argument) for constructor of class

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #6 from Piotr Mierzwinski  ---
And BTW. I'm not sure if this is correct approach to use "Source formatter" in
functions: "Adapt signature" or/and "Update declaration signature". Here I was
confused, because I thought that "Source formatter" is used only in options:
"Edit->Reformat source" and "Edit->Reformat line" :-/.

What if I would like to have different formatting in header of function
declaration and different in code (body of function). For example I would like
to format default parameter in header of function declaration like this: "void
foo( bool param=true)", and in body of function I like such format: "bool
localParam = false". As you can see padding is different in both places. Now
when I  use option: "Edit->Reformat source" then one of them will be broken
:-(. In this moment I have to use same formatting every where. I like such
format: "void foo( bool param=true)", because this takes less space in row.
This if of course is not problem when I have wide monitor or break line on
every parameter.

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

[kde] [Bug 357767] New: Crash after changing icons theme to Breeze

2016-01-09 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 357767
   Summary: Crash after changing icons theme to Breeze
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Application: akonadi_migration_agent (4.89.0)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-040303-generic x86_64
Distribution: Ubuntu 15.10

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

I changed icons theme from nuoveXT 2.2 to Breeze and crash heppended.
I did it after installation Plasma 5.5.3 and KDE Releases Frameworks 5.18.0,
before I have nuoveXT 2.2 theme.

-- Backtrace:
Application: Akonadi Agent (akonadi_migration_agent), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb14942f840 (LWP 1485))]

Thread 2 (Thread 0x7fb147236700 (LWP 1492)):
#0  0x7fb157cdb8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb153647bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fb15364974f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fb148f5c7e9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fb1585e8a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb1532246aa in start_thread (arg=0x7fb147236700) at
pthread_create.c:333
#6  0x7fb157ce6eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb14942f840 (LWP 1485)):
[KCrash Handler]
#6  0x7fb15322faf0 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#7  __lll_unlock_elision (lock=0x7fb1454eb008, private=128) at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#8  0x7fb158fc3cfa in KSharedDataCache::clear() () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#9  0x7fb156b49a46 in KIconLoader::reconfigure(QString const&, QStringList
const&) () from /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#10 0x7fb156b49cb3 in KIconLoader::newIconLoader() () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#11 0x7fb156b49d9e in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#12 0x7fb1587f88ea in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fb156b40b1e in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#14 0x7fb156b4be5b in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#15 0x7fb15b38d963 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x7fb1587f97b1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fb1597fa9dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fb1597ffea6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fb1587c9d7b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fb1587cc176 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fb1588200e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fb152d04ff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fb152d05250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fb152d052fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fb1588204ef in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7fb1587c750a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7fb1587cf5ec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7fb15afb2e66 in Akonadi::AgentBase::init(Akonadi::AgentBase*) () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#29 0x00416b48 in int
Akonadi::AgentBase::init(int, char**) ()
#30 0x7fb157c00a40 in __libc_start_main (main=0x416210 , argc=3,
argv=0x7ffc67e30598, init=, fini=,
rtld_fini=, stack_end=0x7ffc67e30588) at libc-start.c:289
#31 0x00416399 in _start ()

Reported using DrKonqi

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

[kdevelop] [Bug 357774] New: C source files are not parsed by new Clang parser in mixed (C and C++) project

2016-01-09 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 357774
   Summary: C source files are not parsed by new Clang parser in
mixed (C and C++) project
   Product: kdevelop
   Version: 4.90.90
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

My project includes C and C++ files. When I run kdevelop from terminal
(konsole) I can see a lot of messages saying: "libclang: crash detected during
parsing". They all are referring to C source files.

Example of message:
kdevelop(2058)/(default) unknown: Failed to parse translation unit:
"/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmimeparent.c"
libclang: crash detected during parsing: {
  'source_filename' :
'/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/home/piotrek/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/libs/xdgmime/xdgmimeint.c'
  'command_line_args' : ['-ferror-limit=100', '-fspell-checking',
'-Wdocumentation', '-Wunused-parameter', '-Wunreachable-code', '-Wall',
'-std=c++11', '-nostdinc', '-nostdinc++', '-xc++',
'-include/usr/include/qt4/Qt/QtCore', '-include/usr/include/qt4/Qt/QtGui',
'-include/usr/include/qt4/Qt/QtNetwork',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/c++/5',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/x86_64-linux-gnu/c++/5',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/include/c++/5/backward',
'-isystem/usr/local/include',
'-isystem/media/piotrek/FreeAgent/linux_containers/kubuntu_15.10/usr/lib/llvm-3.6/lib/clang/3.6.2/include',
'-isystem/usr/include/x86_64-linux-gnu', '-isystem/usr/include', '-imacros',
'/tmp/kdevelop.If2058'],
  'unsaved_files' : [],
  'options' : 45,
}
kdevelop(2058)/(default) unknown: clang_parseTranslationUnit2 return with error
code 2

And because of this I think that C files are not parsed properly. More visible
effect is lack of semantic highlighting of source in editor.

All C files coming from xdgmime project:
git://anongit.freedesktop.org/xdg/xdgmime

Clicking "Show imports" in "Problems view" showing empty list.
My setting for clang are default, so in "Language Support" I have set "Compiler
for path: Clang" and auto-detected is Clang and GCC (in this order). I use
"Predefined profile c++11".

Now I realized that maybe this bug report has no sense, because used standard
"c++11" in Clang parser. Could somebody confirm it?
And one more question. Whether it is possible to get semantic highlighting of C
source file in editor in mixed (C++ and C) project?


Reproducible: Always

Steps to Reproduce:
1. Open mixed project (C and C++) in kdevelop

Actual Results:  
no semantic highlighting of C source file in editor

Expected Results:  
would be nice to have semantic highlighting of C source file in editor

kdevelop and kdevplatform cloned at January 8-th 2016 (branch 5.0.0).

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

[kdevelop] [Bug 119929] sort variables list alphabetically

2016-01-08 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #15 from Piotr Mierzwinski  ---
The same happen when we unfold QStringList contains more than 10 items. I aware
that QStringList is vector variation contains strings instead of numbers. It
was only next example.
This issue probably happens because there are sorting strings (presenting
indexes) and not numbers.

Some solution for this could be adding 0 to the left side of indexes, making
that them length (as string) would be equal. I mean left padding every indexes
shortest than one longest (counting number of digits). I think, example will
show the best what I mean.
There is QStringList contains 12 strings. This vector/list would be presented
in Variable view like this.

myStrList
 |-[00] aa
 |-[01] bb
 |-[02] cc
 |-[03] dd
 |-[04] ee
 |-[05] ff
 |-[06] gg
 |-[07] hh
 |-[08] ii
 |-[09] jj
 |-[10] kk
  \-[11] ll

Thanks leading "0", change of sorting would not broke the order of items.

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

[krunner] [Bug 357406] New: CRASH when I try to run kwrite using KRunner

2016-01-01 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 357406
   Summary: CRASH when I try to run kwrite using KRunner
   Product: krunner
   Version: 5.5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: piotr.mierzwin...@gmail.com

Application: krunner (5.5.1)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-2-default i686
Distribution: "openSUSE Tumbleweed (20151229) (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
Just after Plasma5 started
1. Invoke Alt+F2
2. type kwrite and ENTER
CRASH

This is not happen everytime. Application kwrite is installed.
In this start of system plasma session was restored. In previous were running:
- first desktop: firefox, konsole
- second desktop: kwrite

Application kwrite from second desktop wasn't restored only firefox and konsole
from first one.

The system (up-to-date on day 2016-01-01) is running on VirtualBox 5.0.10 with
turned off OpenGL acceleration.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb35bf7c0 (LWP 1685))]

Thread 9 (Thread 0xb1b3db40 (LWP 1686)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libxcb.so.1
#3  0x in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#4  0x in  () at /usr/lib/libQt5XcbQpa.so.5
#5  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#6  0x in start_thread () at /lib/libpthread.so.0
#7  0x in clone () at /lib/libc.so.6

Thread 8 (Thread 0xaecf9b40 (LWP 1690)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/dri/swrast_dri.so
#4  0x in  () at /usr/lib/dri/swrast_dri.so
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 7 (Thread 0xae4f8b40 (LWP 1691)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/dri/swrast_dri.so
#4  0x in  () at /usr/lib/dri/swrast_dri.so
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 6 (Thread 0xacaa9b40 (LWP 1700)):
#0  0x in __kernel_vsyscall ()
#1  0x in read () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libglib-2.0.so.0
#3  0x in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#4  0x in  () at /usr/lib/libglib-2.0.so.0
#5  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#6  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#7  0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#8  0x in QEventLoop::exec(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#9  0x in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in  () at /usr/lib/sse2/libQt5Qml.so.5
#11 0x in  () at /usr/lib/sse2/libQt5Core.so.5
#12 0x in start_thread () at /lib/libpthread.so.0
#13 0x in clone () at /lib/libc.so.6

Thread 5 (Thread 0xa5199b40 (LWP 1976)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/sse2/libQt5Core.so.5
#4  0x in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
() at /usr/lib/libKF5ThreadWeaver.so.5
#5  0x in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x in  () at /usr/lib/libKF5ThreadWeaver.so.5
#7  0x in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*,
bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in start_thread () at /lib/libpthread.so.0
#11 0x in clone () at /lib/libc.so.6

Thread 4 (Thread 0xa4998b40 (LWP 1977)):
[KCrash Handler]
#7  0x in  () at /usr/lib/liblmdb-0.9.16.so
#8  0x in mdb_txn_begin () at /usr/lib/liblmdb-0.9.16.so
#9  0x in Baloo::Transaction::Transaction(Baloo::Database const&,
Baloo::Transaction::TransactionType) () at /usr/lib/libKF5BalooEngine.so.5
#10 0x

[kdevelop] [Bug 357088] New: KDevelop crashed when I saved all (Ctrl+L) 3 changed files in Review mode

2015-12-22 Thread Piotr Mierzwinski via KDE Bugzilla

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

Bug ID: 357088
   Summary: KDevelop crashed when I saved all (Ctrl+L) 3 changed
files in Review mode
   Product: kdevelop
   Version: 4.7.2
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Application: kdevelop (4.7.2)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.3.2-server-1.mga6 i686
Distribution: "Mageia 5"

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

1. In Edit mode I changed 3 files and saved them (Ctrl+L)
2. Invoked git->Show Differences (RMB in Project view)
3. In Review mode I changed again all 3 files (in every i moved 1 line)
4. tried save all invoking Ctrl+L
KDevelop crashed

KDevelop-4.7.2 and KDevplatform-1.7.2, Qt-4.8.6
All packages come from Mageia 5 32bit

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Current thread is 1 (Thread 0xb012d780 (LWP 30313))]

Thread 15 (Thread 0xad8f9b40 (LWP 30314)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/i686/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/i686/libc.so.6
#3  0x in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib/libQtScript.so.4
#4  0x in  () at /lib/libQtScript.so.4
#5  0x in start_thread () at /lib/i686/libpthread.so.0
#6  0x in clone () at /lib/i686/libc.so.6

Thread 14 (Thread 0xaab30b40 (LWP 30315)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib/i686/libpthread.so.0
#2  0x in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/i686/libc.so.6
#3  0x in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/libQtCore.so.4
#4  0x in KDevelop::DUChainPrivate::CleanupThread::run()
(this=0xa2c1160) at
/usr/src/debug/kdevplatform-1.7.2/language/duchain/duchain.cpp:283
#5  0x in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#6  0x in start_thread () at /lib/i686/libpthread.so.0
#7  0x in clone () at /lib/i686/libc.so.6

Thread 13 (Thread 0xa908eb40 (LWP 30321)):
#0  0x in __kernel_vsyscall ()
#1  0x in clock_gettime () at /lib/i686/libc.so.6
#2  0x in qt_gettime() () at /lib/libQtCore.so.4
#3  0x in QTimerInfoList::timerWait(timeval&) () at /lib/libQtCore.so.4
#4  0x in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib/libQtCore.so.4
#5  0x in g_main_context_prepare () at /lib/libglib-2.0.so.0
#6  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#7  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#8  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#9  0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#10 0x in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#11 0x in QThread::exec() () at /lib/libQtCore.so.4
#12 0x in QThread::run() () at /lib/libQtCore.so.4
#13 0x in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#14 0x in start_thread () at /lib/i686/libpthread.so.0
#15 0x in clone () at /lib/i686/libc.so.6

Thread 12 (Thread 0xa6803b40 (LWP 30323)):
#0  0x in __kernel_vsyscall ()
#1  0x in clock_gettime () at /lib/i686/libc.so.6
#2  0x in qt_gettime() () at /lib/libQtCore.so.4
#3  0x in QTimerInfoList::timerWait(timeval&) () at /lib/libQtCore.so.4
#4  0x in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib/libQtCore.so.4
#5  0x in timerSourcePrepare(_GSource*, int*) () at /lib/libQtCore.so.4
#6  0x in g_main_context_prepare () at /lib/libglib-2.0.so.0
#7  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#8  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#9  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#10 0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#11 0x in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#12 0x in QThread::exec() () at /lib/libQtCore.so.4
#13 0x in KDevelop::CompletionWorkerThread::run() (this=0xa516ce0) at
/usr/src/debug/kdevplatform-1.7.2/language/codecompletion/codecompletionmodel.cpp:84
#14 0x in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#15 0x in start_thread () at /lib/i686/libpthread.so.0
#16 0x in clone () at /lib/i686/libc.so.6

Thread 11 (Thread 0x9a8c2b40 (LWP 30333)):
#0  0x in __kernel_vsyscall ()
#1  0x in clock_gettime () at

[klipper] [Bug 356837] One cannot clear history when first time is not confirmed

2015-12-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #5 from Piotr Mierzwinski  ---
I did it accidentally and blocked myself possibility to cleaning history in the
future. Of course the final solution is remove/rename all configuration, but
this is not much nice - we are losing our entire configuration :(.

I think this option is quite dangerous for regular users. Checking it doesn't
warn user that any further cleaning will be blocked/doesn't possible. Regular
user can lock cleaning history in this way and will don't know how to restore
it (there is no any option in configuration). I don't think good solution for
him/her would be looking for properly option in some configuration file. Not
everyone are the geeks who like "to poke around the files" :/.

I thing good solution could be reset this setting after relogin of user. I
think this is solution chose by many users (working before on the most popular
OS).

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

[plasmashell] [Bug 356843] Plasmashell segfault after use Alt+F2 and putting any letter in edit box when there are at least two virtual desktops

2015-12-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Summary|Plasmashell segfault after  |Plasmashell segfault after
   |use Alt+F2 and putting any  |use Alt+F2 and putting any
   |letter in edit box  |letter in edit box when
   ||there are at least two
   ||virtual desktops

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

[klipper] [Bug 356837] One cannot clear history when first time is not confirmed

2015-12-18 Thread Piotr Mierzwinski via KDE Bugzilla

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

--- Comment #7 from Piotr Mierzwinski  ---
Now there is no problem with clearing configuration, because Plasma 5 in this
moment is not my "production" system/desktop. I just test it and from time to
time encounter bugs, most often causing crash plasmashell.

OK. So if you can, could you please tell me some about workaround/temporary
solution fixing this. For example what should I change and in which
configuration file or any other workaround, if exists.

BTW.
I've made small research in configuration files. In directories: ~/.config and
~/.local I was looking for strings: "clipboa" and "Clipboa". I found some
occurrences in:
~/.config/plasma-org.kde.plasma.desktop-appletsrc looking like this:
[Containments][1][Applets][5][Configuration][Containments][9][Applets][13]
immutability=1
plugin=org.kde.plasma.clipboard
I'm not sure is this refers for unlocking "Clear history" function, because I
can see similar settings for couple of other plugins :/.
And couple in ~/.config/kglobalshortcutsrc, where one in [plasmashell] section,
is looking like this:
clear-history=none,none,Wyczyść historię schowka
But I think this refers to keyshortcuts, and none value means that there is no
one shortcut assigned to this function.
I was looking also following occurrences: "klipper" and "Klipper", but I have
not found nothing interested.
Conclusion: I don't know where is this hidden. :/

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

1 2 >

1 - 100 of 130 matches

Mail list logo