[plasmashell] [Bug 371015] wayland : X applications have default X icon.

2016-10-19 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371015

--- Comment #2 from Martin Bednar  ---
I just read the blog post :) you guys are awesome. I suppose this could be
closed...
I'd suggest linking to this errata page directly from the desktop of the Neon
liveCD. And I don't know which channel to go through for that to happen...

Thanks.

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

[plasmashell] [Bug 371015] New: wayland : X applications have default X icon.

2016-10-17 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371015

Bug ID: 371015
   Summary: wayland : X applications have default X icon.
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: martin+...@serafean.cz
CC: plasma-b...@kde.org

Running Kde Neon wayland liveCD (yesterday's build) , when I open Firefox (or
VLC), the taskbar icon is that of X11, not of Firefox.

Reproducible: Always

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

[plasmashell] [Bug 364529] Wayland : No title in Task manager for Systemsettings

2016-10-17 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364529

Martin Bednar  changed:

   What|Removed |Added

 CC||martin+...@serafean.cz

--- Comment #6 from Martin Bednar  ---
As of today (17/10/2016) half of the bug is still present : the system settings
entry in task bar has no title (icon is ok) when in its default screen. The
window has no title too.
Using yesterday's Neon wayland spin. Should I open a new bug?

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

[Touchpad-KCM] [Bug 371014] Touchpad KCM segfault under wayland (neon)

2016-10-17 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371014

--- Comment #2 from Martin Bednar  ---
Forgot to mention : Wayland edition.

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

[Touchpad-KCM] [Bug 371014] Touchpad KCM segfault under wayland (neon)

2016-10-17 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371014

Martin Bednar  changed:

   What|Removed |Added

 CC||martin+...@serafean.cz

--- Comment #1 from Martin Bednar  ---
Created attachment 101603
  --> https://bugs.kde.org/attachment.cgi?id=101603=edit
coredump

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

[Touchpad-KCM] [Bug 371014] New: Touchpad KCM segfault under wayland (neon)

2016-10-17 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371014

Bug ID: 371014
   Summary: Touchpad KCM segfault under wayland (neon)
   Product: Touchpad-KCM
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: rajeeshknamb...@gmail.com
  Reporter: martin+...@serafean.cz

I booted up the kde neon LiveCD (Current) , went to the touchpad KCM, and got a
segfault.
Attaching coredump.

Reproducible: Always

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

[kdevelop] [Bug 368401] vim mark and breakpoint icon draw over each other

2016-09-07 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368401

--- Comment #1 from Martin Bednar  ---
Created attachment 100968
  --> https://bugs.kde.org/attachment.cgi?id=100968=edit
only mark set

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

[kdevelop] [Bug 368401] vim mark and breakpoint icon draw over each other

2016-09-07 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368401

Martin Bednar  changed:

   What|Removed |Added

 CC||martin+...@serafean.cz

--- Comment #2 from Martin Bednar  ---
Created attachment 100969
  --> https://bugs.kde.org/attachment.cgi?id=100969=edit
mark and breakpoint set

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

[kdevelop] [Bug 368401] New: vim mark and breakpoint icon draw over each other

2016-09-07 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368401

Bug ID: 368401
   Summary: vim mark and breakpoint icon draw over each other
   Product: kdevelop
   Version: 5.0.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: martin+...@serafean.cz

Kdevelop in vim mode, I set a mark, this is shown in the side bar.
If I the set a breakpoint, the breakpoint icon is drawn over the mark icon.
see screenshots.

Reproducible: Always

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

[frameworks-ktexteditor] [Bug 364816] KDevelop crashes on saving file on vim mode

2016-09-05 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364816

--- Comment #4 from Martin Bednar  ---
Awesome! Thanks.

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

[kdevelop] [Bug 364816] KDevelop crashes on saving file on vim mode

2016-09-04 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364816

Martin Bednar  changed:

   What|Removed |Added

 CC||martin+...@serafean.cz

--- Comment #1 from Martin Bednar  ---
This just happened to me. KDevelop 5.0.0, KF 5.25, qt 5.6.1. The backtrace
looks very similar.
Happens randomly.

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

[kwin] [Bug 368073] New: logout effect on wrong screen

2016-08-31 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368073

Bug ID: 368073
   Summary: logout effect on wrong screen
   Product: kwin
   Version: 5.7.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: multihead
  Assignee: kwin-bugs-n...@kde.org
  Reporter: martin+...@serafean.cz

Created attachment 100869
  --> https://bugs.kde.org/attachment.cgi?id=100869=edit
case 1

I have a dual screen setup. 
When I click "leave" on one desktop , the logout effect kicks in but always on
the "other" screen, while keeping its geometry for the screen on which I
clicked.


A picture being worth a thousand words, Photo27 (case 1)  happens when I click
leave on the screen to the right (the one of which you can see a flame in the
middle).
Photo28 (case 2) happens when I click leave on the screen to the left.
This happens every time.

If you think this may be fixed in 5.8, I will install the beta when it comes
out.

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

[kwin] [Bug 368073] logout effect on wrong screen

2016-08-31 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368073

--- Comment #1 from Martin Bednar  ---
Created attachment 100870
  --> https://bugs.kde.org/attachment.cgi?id=100870=edit
case 2

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

[kmail2] [Bug 366862] kmail crash while syncing

2016-08-23 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366862

--- Comment #2 from Martin Bednar  ---
That is possible, I had pressed delete on something befoore it crashed (I
distinctly remember because it was an accident).

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

[kmail2] [Bug 366862] New: kmail crash while syncing

2016-08-16 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366862

Bug ID: 366862
   Summary: kmail crash while syncing
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: martin+...@serafean.cz

Application: kmail (5.2.80 beta1 (QtWebEngine))
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.7.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

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

Leaving KMail do its sync stuff on the background.
About 2 weeks of mails in 4 accounts to sync.

- Custom settings of the application:
Using PostgreSQL.

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

Thread 37 (Thread 0x7f78e8608700 (LWP 1165)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f78f1f904c3 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/r600_dri.so
#2  0x7f78f1f8fce7 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so
#3  0x7f791dab05c4 in start_thread (arg=0x7f78e8608700) at
pthread_create.c:334
#4  0x7f7926d8b39d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 36 (Thread 0x7f78e71f8700 (LWP 1166)):
#0  0x7f791bfba160 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f791bf78f09 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f791bf7902c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f79278ceb1b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f792788324b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f79276ebb0a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f7929863e35 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7f79276f001d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f791dab05c4 in start_thread (arg=0x7f78e71f8700) at
pthread_create.c:334
#9  0x7f7926d8b39d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 35 (Thread 0x7f78e5fe7700 (LWP 1168)):
#0  0x7ffc69ba1a80 in clock_gettime ()
#1  0x7f7926d97d56 in __GI___clock_gettime (clock_id=1, tp=0x7f78e5fe6b30)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f792778c1a3 in qt_gettime() () from /usr/lib64/libQt5Core.so.5
#3  0x7f79278cd1b9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7f79278ceed0 in timerSourceCheckHelper(GTimerSource*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f791bf789a1 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f791bf78ea8 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#7  0x7f791bf7902c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#8  0x7f79278ceb1b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#9  0x7f792788324b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f79276ebb0a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#11 0x7f79276f001d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#12 0x7f791dab05c4 in start_thread (arg=0x7f78e5fe7700) at
pthread_create.c:334
#13 0x7f7926d8b39d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 34 (Thread 0x7f78e57e6700 (LWP 1169)):
#0  0x7f7926d8257d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f791bf78f14 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f791bf7902c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f79278ceb1b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f792788324b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f79276ebb0a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f79276f001d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f791dab05c4 in start_thread (arg=0x7f78e57e6700) at
pthread_create.c:334
#8  0x7f7926d8b39d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 33 (Thread 0x7f78e4fe5700 (LWP 1171)):
#0  0x7ffc69ba1a80 in clock_gettime ()
#1  0x7f7926d97d56 in __GI___clock_gettime (clock_id=1, tp=0x7f78e4fe4ad0)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f792778c1a3 in qt_gettime() () from /usr/lib64/libQt5Core.so.5
#3  0x7f79278cd1b9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7f79278cd545 in

[plasma-nm] [Bug 366383] Applet keeps spinner as if still connecting even when connected

2016-08-03 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366383

--- Comment #1 from Martin Bednar  ---
After plasmashell restart, ip is in applet, and spinner is gone.

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

[plasma-nm] [Bug 366383] New: Applet keeps spinner as if still connecting even when connected

2016-08-03 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366383

Bug ID: 366383
   Summary: Applet keeps spinner as if still connecting even when
connected
   Product: plasma-nm
   Version: 5.7.2
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: martin+...@serafean.cz
CC: lu...@kde.org

Sometimes when connecting to a network (wired or wireless), the spinner that
notifies that connecting is in progress keeps spinning even when connection
gets state "connected" (visible in the applet).
The only unusual thing is the absence of ip address in the applet popup.

Combined with the fact that spinners in the tray are cpu power hogs, this makes
it a pretty serious issue.

Reproducible: Sometimes

Steps to Reproduce:
1. Initiate connection to network
2. wait for connected state
3. See internet working, state as connected and spinner still spinning.

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

[kwin] [Bug 364388] kwin crash on alt+tab

2016-06-17 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364388

--- Comment #7 from Martin Bednar  ---
(In reply to Thomas Lübking from comment #6)
> please check the output of "glxinfo" - if the other bug is right, your gl
> installation is broken. qtquick then simply doesn't work.

GL works ok : OpenGL renderer string: Gallium 0.4 on AMD CAYMAN (DRM 2.43.0,
LLVM 3.8.0)
Kodi is running right now, and warzone2100 starts.

This is weird : compositing gets disabled the moment I set kodi to
fullscreen... hadn't noticed that before.

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

[kwin] [Bug 364388] kwin crash on alt+tab

2016-06-17 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364388

--- Comment #5 from Martin Bednar  ---
(In reply to Martin Gräßlin from comment #3)
> Qt is using EGL instead of GLX and that probably doesn't work. Why did you
> compile Qt to prefer EGL?

TBH I don't remember actively making that choice, my combination of use flags
kind of forced me into it.

Right now I'm upgrading to qt 5.6.1 (with the same useflags) and I'll report
back when done.

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

[kwin] [Bug 364388] kwin crash on alt+tab

2016-06-16 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364388

Martin Bednar  changed:

   What|Removed |Added

 CC||seraf...@gmail.com

--- Comment #1 from Martin Bednar  ---
Created attachment 99534
  --> https://bugs.kde.org/attachment.cgi?id=99534=edit
kwin supportinformation

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

[kwin] [Bug 364388] New: kwin crash on alt+tab

2016-06-16 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364388

Bug ID: 364388
   Summary: kwin crash on alt+tab
   Product: kwin
   Version: 5.6.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: seraf...@gmail.com

Application: kwin_x11 (5.6.4)
 (Compiled from sources)
Qt Version: 5.5.1
Frameworks Version: 5.22.0
Operating System: Linux 4.6.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

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

Two screens, kodi playing fullscreen on one, browser on other.
Focus on browser, press alt+tab to switch window.
Kwin crash.

DrKonqui found quite a few possible dupes, but I'm not sure if it actually is
one. (those I quickly browsed mentioned a fix in qt 5.5, which I have)

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1c39cf7840 (LWP 5958))]

Thread 7 (Thread 0x7f1c22e2d700 (LWP 5961)):
#0  0x7f1c395ed57d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1c37a9ca92 in poll (__timeout=-1, __nfds=1, __fds=0x7f1c22e2cc80)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x24a2ab0, cond=cond@entry=0x24a2af0,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7f1c37a9e67f in xcb_wait_for_event (c=0x24a2ab0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7f1c236d1719 in QXcbEventReader::run (this=0x24b5ae0) at
qxcbconnection.cpp:1229
#5  0x7f1c37d51b63 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f1c398af5c4 in start_thread (arg=0x7f1c22e2d700) at
pthread_create.c:334
#7  0x7f1c395f639d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f1c1bec1700 (LWP 5969)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1c21a3e293 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/r600_dri.so
#2  0x7f1c21a3dab7 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so
#3  0x7f1c398af5c4 in start_thread (arg=0x7f1c1bec1700) at
pthread_create.c:334
#4  0x7f1c395f639d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f1c1938d700 (LWP 5975)):
#0  pthread_cond_timedwait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f1c37d52118 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f1c37d4f197 in QThreadPoolThread::run() () from
/usr/lib64/libQt5Core.so.5
#3  0x7f1c37d51b63 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f1c398af5c4 in start_thread (arg=0x7f1c1938d700) at
pthread_create.c:334
#5  0x7f1c395f639d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f1c13fff700 (LWP 5976)):
#0  0x7f1c395ef203 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1c37f34ad9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib64/libQt5Core.so.5
#2  0x7f1c37f36033 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib64/libQt5Core.so.5
#3  0x7f1c37f3644b in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f1c37eed75b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f1c37d4d51a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f1c3238f548 in QQmlThreadPrivate::run (this=0x270c4d0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f1c37d51b63 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f1c398af5c4 in start_thread (arg=0x7f1c13fff700) at
pthread_create.c:334
#9  0x7f1c395f639d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1c12ffe700 (LWP 5977)):
#0  pthread_cond_timedwait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f1c37d52118 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f1c37d4f197 in QThreadPoolThread::run() () from
/usr/lib64/libQt5Core.so.5
#3  0x7f1c37d51b63 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f1c398af5c4 in start_thread (arg=0x7f1c12ffe700) at
pthread_create.c:334
#5  0x7f1c395f639d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1c127fd700 (LWP 5978)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1c36e6911b in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f1c36f50c60 ) at

[kwin] [Bug 363778] logout effect fails to compile shader

2016-06-01 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363778

--- Comment #2 from Martin Bednar  ---
Created attachment 99299
  --> https://bugs.kde.org/attachment.cgi?id=99299=edit
supportInformation output

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

[kwin] [Bug 363778] New: logout effect fails to compile shader

2016-06-01 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363778

Bug ID: 363778
   Summary: logout effect fails to compile shader
   Product: kwin
   Version: 5.6.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: seraf...@gmail.com

When logout/shustdown/reboot is triggered for the first time since boot, 
Jun 01 10:13:41 ged kwin_x11[601]: libkwinglutils: Failed to compile fragment
shader: 
   "0:13(12): error: no matching function for
call to `smoothstep(int, float, float)'; candidates are:\n0:13(12): error:   
float smoothstep(float, float, float)\n0:13(12): error:vec2
smoothstep(float, float, vec2)\n0:13(12): error:vec3 smoothstep(float,
float, vec3)\n0:13(12): error:vec4 smoothstep(float, float,
vec4)\n0:13(12): error:vec2 smoothstep(vec2, vec2, vec2)\n0:13(12): error: 
  vec3 smoothstep(vec3, vec3, vec3)\n0:13(12): error:vec4 smoothstep(vec4,
vec4, vec4)\n\x00"
Jun 01 10:13:41 ged kwin_x11[601]: libkwinglutils: Failed to link shader: 
   "error: program lacks a fragment
shader\n\x00"

Appears in the log.
I have no idea if it's in kwin, or in the graphics driver, so I'm starting
here.
GPU is Radeon HD6950, driver is r600g on mesa 11.2.2.
OpenGl 3.1 rendering backend.

Reproducible: Always

Steps to Reproduce:
1. Boot, login
2. Watch journal
3. click logout

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

[KScreen] [Bug 358011] dual screen not setup after reboot

2016-05-09 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358011

--- Comment #6 from Martin Bednar  ---
Created attachment 98866
  --> https://bugs.kde.org/attachment.cgi?id=98866=edit
kded5 stderr with correct setup

After setting up the screen config, I killed kded5 and started it once more.
Config stayed ok. This is the stderr.

Sorry for the delay...

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

[KScreen] [Bug 358011] dual screen not setup after reboot

2016-05-09 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358011

--- Comment #5 from Martin Bednar  ---
Created attachment 98865
  --> https://bugs.kde.org/attachment.cgi?id=98865=edit
kded5 stderr

Restart of kded5 with the bad screen configuration, with subsequent setup of
correct configuration.

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

[KScreen] [Bug 358011] dual screen not setup after reboot

2016-05-09 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358011

--- Comment #3 from Martin Bednar  ---
Created attachment 98863
  --> https://bugs.kde.org/attachment.cgi?id=98863=edit
before reboot, all set up ok

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

[KScreen] [Bug 358011] dual screen not setup after reboot

2016-05-09 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358011

--- Comment #4 from Martin Bednar  ---
Created attachment 98864
  --> https://bugs.kde.org/attachment.cgi?id=98864=edit
After reboot, bad screen configuration

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

[KScreen] [Bug 358011] dual screen not setup after reboot

2016-05-09 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358011

--- Comment #7 from Martin Bednar  ---
for some reason, once a couple of minutes, kded5 keeps outputting 

kscreen: starting external backend launcher for ""
kscreen.kded: Change detected
kscreen.kded: Saving current config to file
kscreen.kded: Calculating config ID for KScreen::Config(0x1b82e50)
kscreen.kded:   Part of the Id:  "7a131aded027d4cee9b9d1bd9ced6cda"
kscreen.kded:   Part of the Id:  "76b62af2c36e3d5e9fdaeebe614093eb"
kscreen.kded:   Config ID: "43656861fc5bd49b298b3988a44c0fe9"
kscreen.kded: Config saved on: 
"/home/martin/.local/share/kscreen/43656861fc5bd49b298b3988a44c0fe9"

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

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

2016-03-24 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=346740

Martin Bednar  changed:

   What|Removed |Added

 CC||seraf...@gmail.com

--- Comment #44 from Martin Bednar  ---
I just hit this  (at least dr Konqui says so)  , also by fast clicking in the
system tray.
First happened by fast switch between klipper and telepathy contact list.
I reproduced it by fast switching between telepathy contact list and klipper
(that worked). Crash occured when I hit the bluetooth icon.

What I think is important is that in the first crash klipper had never been
shown before in this session (and system boot), the same goes for the bluetooth
widget (hadn't been shown before).

Trace :

[Current thread is 1 (Thread 0x7ff586714840 (LWP 14889))]

Thread 20 (Thread 0x7ff5730e6700 (LWP 14895)):
#0  0x7ff581013aed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff584edba92 in poll (__timeout=-1, __nfds=1, __fds=0x7ff5730e5c80)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0xbeeb80, cond=cond@entry=0xbeebc0,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7ff584edd67f in xcb_wait_for_event (c=0xbeeb80) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7ff57503a719 in QXcbEventReader::run (this=0xc01bd0) at
qxcbconnection.cpp:1229
#5  0x7ff58167bb63 in QThreadPrivate::start (arg=0xc01bd0) at
thread/qthread_unix.cpp:331
#6  0x7ff58081e314 in start_thread (arg=0x7ff5730e6700) at
pthread_create.c:333
#7  0x7ff58101c6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7ff56757c700 (LWP 14897)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff570c8df63 in cnd_wait (mtx=0xc54dd0, cond=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0xc54dd0) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0xc549a0) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:680
#4  0x7ff570c8d787 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:87
#5  0x7ff58081e314 in start_thread (arg=0x7ff56757c700) at
pthread_create.c:333
#6  0x7ff58101c6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7ff564f75700 (LWP 14903)):
#0  postEventSourcePrepare (s=0x7ff5600012d0,
timeout=timeout@entry=0x7ff564f74bc4) at kernel/qeventdispatcher_glib.cpp:255
#1  0x7ff57cf4455d in g_main_context_prepare
(context=context@entry=0x7ff56990, priority=priority@entry=0x7ff564f74c48)
at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3442
#2  0x7ff57cf44e30 in g_main_context_iterate
(context=context@entry=0x7ff56990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3820
#3  0x7ff57cf4502c in g_main_context_iteration (context=0x7ff56990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3901
#4  0x7ff58186237b in QEventDispatcherGlib::processEvents
(this=0x7ff568c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7ff58181775b in QEventLoop::exec (this=this@entry=0x7ff564f74d70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7ff58167751a in QThread::exec (this=this@entry=0xd39ae0) at
thread/qthread.cpp:503
#7  0x7ff583d9c548 in QQmlThreadPrivate::run (this=0xd39ae0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7ff58167bb63 in QThreadPrivate::start (arg=0xd39ae0) at
thread/qthread_unix.cpp:331
#9  0x7ff58081e314 in start_thread (arg=0x7ff564f75700) at
pthread_create.c:333
#10 0x7ff58101c6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7ff55c0a2700 (LWP 14912)):
#0  0x7ff581013aed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff57cf44f14 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7ff554002e70, timeout=-1, context=0x7ff554000990) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7ff554000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3835
#3  0x7ff57cf4502c in g_main_context_iteration (context=0x7ff554000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3901
#4  0x7ff58186237b in QEventDispatcherGlib::processEvents
(this=0x7ff5540008c0,

[dolphin] [Bug 360089] New: Dolphin crashes on startup

2016-03-04 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=360089

Bug ID: 360089
   Summary: Dolphin crashes on startup
   Product: dolphin
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: seraf...@gmail.com

Application: dolphin (15.12.2)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
Upon dolphin startup, it directly crashes. 

Additional information : Seeing that the crash goes into Baloo, I feel it might
be related to the disk failure I experienced lately. Data was recovered, but to
be honest, I can't guarantee integrity. I believe it shouldn't crash though  :)

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f592b927840 (LWP 18596))]

Thread 3 (Thread 0x7f591d4e0700 (LWP 18598)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5922be0053 in cnd_wait (mtx=0x159f860, cond=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x159f860) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0x159f430) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:680
#4  0x7f5922bdf877 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:87
#5  0x7f5934291314 in start_thread (arg=0x7f591d4e0700) at
pthread_create.c:333
#6  0x7f593cf5e6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f591969c700 (LWP 18599)):
#0  0x7f593cf55aed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f59321f1f14 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f5914003020, timeout=-1, context=0x7f5914000990) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f5914000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3835
#3  0x7f59321f202c in g_main_context_iteration (context=0x7f5914000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3901
#4  0x7f5937e8037b in QEventDispatcherGlib::processEvents
(this=0x7f59140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f5937e3575b in QEventLoop::exec (this=this@entry=0x7f591969bd90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f5937c9551a in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f5937c99b63 in QThreadPrivate::start (arg=0x19e20e0) at
thread/qthread_unix.cpp:331
#8  0x7f5934291314 in start_thread (arg=0x7f591969c700) at
pthread_create.c:333
#9  0x7f593cf5e6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f592b927840 (LWP 18596)):
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
#7  0x7f5937c9bd7c in memcpy (__len=28884880, __src=0x7f593d5dc8c8,
__dest=) at /usr/include/bits/string3.h:53
#8  QByteArray::QByteArray (this=0x7fff14d06620, data=0x7f593d5dc8c8 "",
size=28884880) at tools/qbytearray.cpp:1452
#9  0x7f5934b0dca0 in Baloo::DocumentDataDB::get
(this=this@entry=0x7fff14d065c0, docId=docId@entry=1103806595116) at
/var/tmp/portage/kde-frameworks/baloo-5.19.0/work/baloo-5.19.0/src/engine/documentdatadb.cpp:89
#10 0x7f5934b1fc3e in Baloo::Transaction::documentData
(this=this@entry=0x7fff14d06630, id=id@entry=1103806595116) at
/var/tmp/portage/kde-frameworks/baloo-5.19.0/work/baloo-5.19.0/src/engine/transaction.cpp:144
#11 0x7f593ada327f in Baloo::File::load (this=this@entry=0x7fff14d06750) at
/var/tmp/portage/kde-frameworks/baloo-5.19.0/work/baloo-5.19.0/src/lib/file.cpp:111
#12 0x7f593b33fc2b in Baloo::FileFetchJob::doStart (this=0x1a83990) at
/var/tmp/portage/kde-apps/baloo-widgets-15.12.2/work/baloo-widgets-15.12.2/src/filefetchjob.cpp:58
#13 0x7f5937e5dcee in QObject::event (this=0x1a83990, e=) at
kernel/qobject.cpp:1239
#14 0x7f59388288fc in QApplicationPrivate::notify_helper
(this=this@entry=0x1525ba0, receiver=receiver@entry=0x1a83990,
e=e@entry=0x1b8c3f0) at kernel/qapplication.cpp:3716
#15 0x7f593882d748 in QApplication::notify (this=0x7fff14d06ef0,
receiver=0x1a83990, e=0x1b8c3f0) at kernel/qapplication.cpp:3499
#16 0x7f5937e36b0d in QCoreApplication::notifyInternal

[kmail2] [Bug 358158] KMail crashes on email autocompletion

2016-01-18 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358158

--- Comment #1 from Martin Bednar  ---
Update : it doesn't happen on every contact (or at least not for the matches I
tried). I have one contact with which it happens every time.

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

[kmail2] [Bug 358158] New: KMail crashes on email autocompletion

2016-01-18 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358158

Bug ID: 358158
   Summary: KMail crashes on email autocompletion
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: seraf...@gmail.com

Application: kmail (5.1.1)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.3.3-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed:
I had a half written mail, started  writing in the "TO" field. Autocompletion
popped up.
I continued writing the name, KMail crashed.
Happened twice, haven't tried more times.

Special setup:
Akonadi using postgresql.

The crash can be reproduced every time.

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

Thread 20 (Thread 0x7f10d82ad700 (LWP 2224)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f10e17b6513 in cnd_wait (mtx=0x1b8e568, cond=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x1b8e568) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0x1b8e140) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:659
#4  0x7f10e17b5d37 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:87
#5  0x7f10fa2e3314 in start_thread (arg=0x7f10d82ad700) at
pthread_create.c:333
#6  0x7f110325883d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7f10d65e7700 (LWP 2225)):
#0  0x7f110324fc4d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f10f87e7b74 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f10d0003070, timeout=9990, context=0x7f10d990) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7f10d990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3803
#3  0x7f10f87e7c8c in g_main_context_iteration (context=0x7f10d990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869
#4  0x7f1103cb535c in QEventDispatcherGlib::processEvents
(this=0x7f10d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#5  0x7f1103c6a75b in QEventLoop::exec (this=this@entry=0x7f10d65e6d90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f1103aca51a in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f1103aceb63 in QThreadPrivate::start (arg=0x1c35470) at
thread/qthread_unix.cpp:331
#8  0x7f10fa2e3314 in start_thread (arg=0x7f10d65e7700) at
pthread_create.c:333
#9  0x7f110325883d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7f10d5dcd700 (LWP 2226)):
#0  0x7f110324fc4d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f10f87e7b74 in g_main_context_poll (priority=2147483647, n_fds=2,
fds=0x7f10c8002e20, timeout=-1, context=0x7f10c8000990) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7f10c8000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3803
#3  0x7f10f87e7c8c in g_main_context_iteration (context=0x7f10c8000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869
#4  0x7f1103cb535c in QEventDispatcherGlib::processEvents
(this=0x7f10c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#5  0x7f1103c6a75b in QEventLoop::exec (this=this@entry=0x7f10d5dccd90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f1103aca51a in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f1103aceb63 in QThreadPrivate::start (arg=0x1c6da60) at
thread/qthread_unix.cpp:331
#8  0x7f10fa2e3314 in start_thread (arg=0x7f10d5dcd700) at
pthread_create.c:333
#9  0x7f110325883d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f10d55cc700 (LWP 2227)):
#0  0x7f110324fc4d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f10f87e7b74 in g_main_context_poll (priority=2147483647, n_fds=2,
fds=0x7f10cc003020, timeout=-1, context=0x7f10cc000990) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:4103

[KScreen] [Bug 358011] New: dual screen not setup after reboot

2016-01-15 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358011

Bug ID: 358011
   Summary: dual screen not setup after reboot
   Product: KScreen
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kded
  Assignee: dvra...@kde.org
  Reporter: seraf...@gmail.com

I setup my two screens to be next to each other, after reboot they're in clone
mode.


Basically a dupe of 325277, the difference being that I think all (both) my
screens have a different EDID.

kscreen-console : 

START: Requesting Config
kscreen: Primary output changed from KScreen::Output(Id: 88 , Name: "DVI-0" ) (
"DVI-0" ) to KScreen::Output(Id: 88 , Name: "DVI-0" ) ( "DVI-0" )
kscreen: Primary output changed from KScreen::Output(Id: 88 , Name: "DVI-0" ) (
"DVI-0" ) to KScreen::Output(Id: 88 , Name: "DVI-0" ) ( "DVI-0" )
Received config. Took 22 milliseconds
Screen:
maxSize: QSize(16384, 16384)
minSize: QSize(320, 200)
currentSize: QSize(2880, 1200)

-

Id:  85
Name:  "DisplayPort-0"
Type:  "Unknown"
Connected:  false

-

Id:  86
Name:  "DisplayPort-1"
Type:  "Unknown"
Connected:  false

-

Id:  87
Name:  "HDMI-0"
Type:  "Unknown"
Connected:  false

-

Id:  88
Name:  "DVI-0"
Type:  "Unknown"
Connected:  true
Enabled:  true
Primary:  true
Rotation:  1
Pos:  QPoint(1280,0)
MMSize:  QSize(367, 275)
Size:  QSize(1600, 1200)
Clones:  None
Mode:  "91"
Preferred Mode:  "91"
Preferred modes:  ("91")
Modes: 
 "100"""   QSize(640, 480)   60
 "101"""   QSize(720, 400)   70.0817
 "91"""   QSize(1600, 1200)   60
 "92"""   QSize(1280, 1024)   75.0247
 "93"""   QSize(1280, 1024)   60.0197
 "94"""   QSize(1152, 864)   75
 "95"""   QSize(1024, 768)   75.0762
 "96"""   QSize(1024, 768)   60.0038
 "97"""   QSize(800, 600)   75
 "98"""   QSize(800, 600)   60.3165
 "99"""   QSize(640, 480)   75
EDID Info: 
Device ID:  "xrandr-DELL 2001FP-C088141F06YL"
Name:  "DELL 2001FP"
Vendor:  ""
Serial:  "C088141F06YL"
EISA ID:  ""
Hash:  "7a131aded027d4cee9b9d1bd9ced6cda"
Width:  41
Height:  31
Gamma:  2
Red:  QQuaternion(scalar:1, vector:(0.637695, 0.339844, 0))
Green:  QQuaternion(scalar:1, vector:(0.292969, 0.608398, 0))
Blue:  QQuaternion(scalar:1, vector:(0.146484, 0.0673828, 0))
White:  QQuaternion(scalar:1, vector:(0.3125, 0.328125, 0))

-

Id:  89
Name:  "DVI-1"
Type:  "Unknown"
Connected:  true
Enabled:  true
Primary:  false
Rotation:  1
Pos:  QPoint(0,0)
MMSize:  QSize(338, 270)
Size:  QSize(1280, 1024)
Clones:  None
Mode:  "92"
Preferred Mode:  "93"
Preferred modes:  ("93")
Modes: 
 "100"""   QSize(640, 480)   60
 "101"""   QSize(720, 400)   70.0817
 "102"""   QSize(1024, 768)   75.0286
 "103"""   QSize(832, 624)   74.5513
 "92"""   QSize(1280, 1024)   75.0247
 "93"""   QSize(1280, 1024)   60.0197
 "94"""   QSize(1152, 864)   75
 "95"""   QSize(1024, 768)   75.0762
 "96"""   QSize(1024, 768)   60.0038
 "97"""   QSize(800, 600)   75
 "98"""   QSize(800, 600)   60.3165
 "99"""   QSize(640, 480)   75
EDID Info: 
Device ID:  "xrandr-L1720B-105487"
Name:  "L1720B"
Vendor:  ""
Serial:  "105487"
EISA ID:  ""
Hash:  "76b62af2c36e3d5e9fdaeebe614093eb"
Width:  34
Height:  27
Gamma:  2
Red:  QQuaternion(scalar:1, vector:(0.640625, 0.339844, 0))
Green:  QQuaternion(scalar:1, vector:(0.291992, 0.611328, 0))
Blue:  QQuaternion(scalar:1, vector:(0.147461, 0.0683594, 0))
White:  QQuaternion(scalar:1, vector:(0.313477, 0.329102, 0))
kscreen: Primary output changed from KScreen::Output(Id: 88 , Name: "DVI-0" ) (
"DVI-0" ) to KScreen::Output(Id: 88 , Name: "DVI-0" ) ( "DVI-0" )
kscreen: Primary output changed from KScreen::Output(Id: 88 , Name: "DVI-0" ) (
"DVI-0" ) to KScreen::Output(Id: 88 , Name: "DVI-0" ) ( "DVI-0" )
Screen:
maxSize: QSize(16384, 16384)
minSize: QSize(320, 200)
currentSize: QSize(2880, 1200)

-

Id:  85
Name:  "DisplayPort-0"
Type:  "Unknown"
Connected:  false

-

Id:  86
Name:  "DisplayPort-1"
Type:  "Unknown"
Connected:  false

-

Id:  87
Name:  "HDMI-0"
Type:  "Unknown"

[Akonadi] [Bug 354536] Akonadi fails to migrate database from version 30 (foreign key constraint fails)

2015-12-13 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=354536

Martin Bednar  changed:

   What|Removed |Added

 CC||seraf...@gmail.com

--- Comment #3 from Martin Bednar  ---
I think I just got hit by this.
Log here : https://paste.kde.org/paxixlmnn

Using a system-wide mysql server. (also used for web development)

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

[kwin] [Bug 356076] Window decorations KCM looks bad with breeze-dark

2015-12-10 Thread Martin Bednar via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=356076

Martin Bednar  changed:

   What|Removed |Added

  Attachment #95803|0   |1
is obsolete||
 Status|RESOLVED|REOPENED
   Assignee|kwin-bugs-n...@kde.org  |seraf...@gmail.com
 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---

--- Comment #3 from Martin Bednar  ---
Created attachment 95986
  --> https://bugs.kde.org/attachment.cgi?id=95986=edit
5.5.0 look

just installed 5.5.0 (gentoo). This is how it looks now.
Sorry to say, still not good. Reopening...

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