[systemsettings] [Bug 292606] Setting a custom mail client has no effect on mailto

2016-10-06 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=292606

--- Comment #10 from Jiri Slaby  ---
(In reply to Tristan Miller from comment #9)
> Jiri, how did you "turn on debug" to get the output you posted in Comment
> #5?  I would like to try the same thing.

Via kdebugdialog.

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


[plasmashell] [Bug 359152] No application can be run after some uptime

2016-09-20 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359152

--- Comment #5 from Jiri Slaby  ---
(In reply to David Edmundson from comment #4)
> So you have the file when you log in, then at some point it disappears?

Exactly.

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


[plasmashell] [Bug 359152] No application can be run after some uptime

2016-09-11 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359152

Jiri Slaby  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #3 from Jiri Slaby  ---
(In reply to David Edmundson from comment #2)
> If that happens, you must be breaking your xauthority files.

Yes, $XAUTHORITY which is /tmp/xauth-500-_0 disappears when this happens. I
have to both
$ cp .Xauthority /tmp/xauth-500-_0
and
$ xhost +
to have it fixed.

> What display manager do you use?

sddm

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


[frameworks-knotifications] [Bug 364798] knotifications processes clicks wrong

2016-06-27 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #6 from Jiri Slaby  ---
And indeed, removing /usr/lib64/libKF5Notifications.so.5* makes the problem
disappear.

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


[frameworks-knotifications] [Bug 364798] knotifications processes clicks wrong

2016-06-27 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #5 from Jiri Slaby  ---
And yet, what should the activate numbers actually be:
QPlatformSystemTrayIcon::Context1
QPlatformSystemTrayIcon::DoubleClick2
QPlatformSystemTrayIcon::Trigger3
QPlatformSystemTrayIcon::MiddleClick4

according to:
http://doc.qt.io/qt-5/qplatformsystemtrayicon.html#ActivationReason-enum

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


[frameworks-knotifications] [Bug 364798] knotifications processes clicks wrong

2016-06-27 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #4 from Jiri Slaby  ---
Versions:
qt4: libqt4-4.8.7-4.1.x86_64
qt5: libQt5Core5-5.6.0-1.1.x86_64
KDE5: plasma-framework-5.22.0-1.1.x86_64
knotifications: libKF5Notifications5-5.22.0-1.2.x86_64

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


[frameworks-knotifications] [Bug 364798] knotifications processes clicks wrong

2016-06-27 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #3 from Jiri Slaby  ---
Created attachment 99716
  --> https://bugs.kde.org/attachment.cgi?id=99716&action=edit
KDE5+qt5 click backtrace

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


[frameworks-knotifications] [Bug 364798] knotifications processes clicks wrong

2016-06-27 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #2 from Jiri Slaby  ---
Created attachment 99715
  --> https://bugs.kde.org/attachment.cgi?id=99715&action=edit
KDE5+qt4 click backtrace

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


[frameworks-knotifications] [Bug 364798] knotifications processes clicks wrong

2016-06-27 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #1 from Jiri Slaby  ---
Created attachment 99714
  --> https://bugs.kde.org/attachment.cgi?id=99714&action=edit
icewm click backtrace

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


[frameworks-knotifications] [Bug 364798] New: knotifications processes clicks wrong

2016-06-27 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364798

Bug ID: 364798
   Summary: knotifications processes clicks wrong
   Product: frameworks-knotifications
   Version: 5.22.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mklape...@kde.org
  Reporter: jirisl...@gmail.com
CC: kdelibs-b...@kde.org

When I double click an icon in systemtray, it does nothing, but it should open
the main window of the relevant application. This works without knotifications
correctly, e.g. in icewm.

I noticed this problem on KDE 5 with psi+:
https://github.com/psi-plus/psi-plus-snapshots

FWIW middle and right clicks and scroll events are not passed down to the app
correctly too. 

For testing purposes, I wrote a minimalistic simple app creating only a
QSystemTrayIcon:
https://github.com/jirislaby/collected_sources/tree/master/qt5-icon

When I click on the icon in icewm (i.e. no knotifications), I get:
left button: activate 3
middle button: activate 4
right button: activate 1
double click: activate 3 & activate 2
scroll: wasn't tried

In KDE 5, the app built against qt5 (libQt5Core.so.5 =>
/usr/lib64/libQt5Core.so.5):
left button: activate 3
middle button: activate 1 (WRONG)
right button: NOTHING (WRONG)
double click: activate 3 & activate 3 (WRONG)
scroll: NOTHING (WRONG)

In KDE 5, the app built against qt4 (libQtCore.so.4 =>
/usr/lib64/libQtCore.so.4):
left button: activate 3
middle button: activate 4
right button: NOTHING (WRONG)
double click: activate 3 & activate 3 (WRONG)
scroll: eventFilter true 31

Reproducible: Always

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


[kmix] [Bug 363139] osd is displayed very small sometimes

2016-05-16 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363139

--- Comment #2 from Jiri Slaby  ---
$ rpm -q plasma5-session plasma5-workspace plasma-framework kmix
plasma5-session-5.6.3-1.1.noarch
plasma5-workspace-5.6.3-1.1.x86_64
plasma-framework-5.21.0-1.2.x86_64
kmix-15.12.3-1.2.x86_64

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


[kmix] [Bug 363139] New: osd is displayed very small sometimes

2016-05-16 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363139

Bug ID: 363139
   Summary: osd is displayed very small sometimes
   Product: kmix
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: On-Screen-Display (OSD)
  Assignee: es...@kde.org
  Reporter: jirisl...@gmail.com

When I press multimedia keys like volume up/down/mute, the OSD is shown as a
tiny rectangle.

I have a dual monitor setup. I suspect that this happens after switching
monitors.

Reproducible: Sometimes

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


[kmix] [Bug 363139] osd is displayed very small sometimes

2016-05-16 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363139

--- Comment #1 from Jiri Slaby  ---
Created attachment 99022
  --> https://bugs.kde.org/attachment.cgi?id=99022&action=edit
screenshot of the situation

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


[plasmashell] [Bug 361763] New: plasmashells always locks up with modesetting driver

2016-04-14 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361763

Bug ID: 361763
   Summary: plasmashells always locks up with modesetting driver
   Product: plasmashell
   Version: 5.6.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jirisl...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Currently, I use intel_drv with SNA. I have compositing enabled (opengl 3.1).

When I switch to modesetting_drv, plasmashell "locks up" few seconds after
start. The trigger is perhaps hovering over icons in the tray.

The lockup is that X spins with drm_ioctl_wait_vblank and other ioctls on one
CPU 100%. When I do:
killall plasmashell ; plasmashell
X stops spinning until I hover over the icons again.

So plasmashell has some problem with rendering, I suppose. I tried both OpenGL
and XRender compositing. Note that this also happens without compositing
enabled at all.

Reproducible: Always

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


[plasmashell] [Bug 360856] New: panel is shown on non-existing screen

2016-03-22 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360856

Bug ID: 360856
   Summary: panel is shown on non-existing screen
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: jirisl...@gmail.com

I unplugged external monitor, but panel did not appear on the notebook screen.
Plasmashell said:
kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) (
"LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )

But the panel is obviously on the second screen. When I replug the monitor, the
panel is there.

I had to change .config/plasma-org.kde.plasma.desktop-appletsrc in section
[Containments][1]
where
plugin=org.kde.panel
from
lastScreen=1
to
lastScreen=0
and restart plasma by:
killall plasmashell ; plasmashell
to have the panel on the notebook.

BTW sometimes, if I plug an external monitor, I have to do this to have the
panel on the primary (notebook's screen) output:
xrandr --noprimary
killall plasmashell
plasmashell >/dev/null 2>&1 &
sleep 5
xrandr --output LVDS1 --primary


Reproducible: Always

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


[systemsettings] [Bug 359850] Dolphin as default File Manager not possible

2016-03-02 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359850

Jiri Slaby  changed:

   What|Removed |Added

 CC||jirisl...@gmail.com

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


[krunner] [Bug 359488] New: krunner crashed while typing

2016-02-17 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359488

Bug ID: 359488
   Summary: krunner crashed while typing
   Product: krunner
   Version: 5.5.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: jirisl...@gmail.com

Application: krunner (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.1-17.g2b16688-default x86_64
Distribution: "openSUSE Tumbleweed (20160117) (x86_64)"

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

I wanted to start libreoffice writer. I wrote libre and clicked writer. Then it
crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
18562:movl(%rsp), %edi
[Current thread is 1 (Thread 0x7f1e95b498c0 (LWP 13666))]

Thread 11 (Thread 0x7f1e7b9ad700 (LWP 13668)):
#0  0x7f1e9184524d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1e90d4c432 in  () at /usr/lib64/libxcb.so.1
#2  0x7f1e90d4e007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f1e7dafce29 in QXcbEventReader::run() (this=0xc80a00) at
qxcbconnection.cpp:1229
#4  0x7f1e91f3594f in QThreadPrivate::start(void*) (arg=0xc80a00) at
thread/qthread_unix.cpp:331
#5  0x7f1e8f6be4a4 in start_thread (arg=0x7f1e7b9ad700) at
pthread_create.c:334
#6  0x7f1e9184dbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f1e72d7d700 (LWP 13669)):
#0  0x7f1e9184524d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1e8ed4e264 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1e8ed4e36c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1e9215a52b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f1e6c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f1e9210463a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f1e72d7ccf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f1e91f30b1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#6  0x7f1e945d09a5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f1e91f3594f in QThreadPrivate::start(void*) (arg=0x1131d40) at
thread/qthread_unix.cpp:331
#8  0x7f1e8f6be4a4 in start_thread (arg=0x7f1e72d7d700) at
pthread_create.c:334
#9  0x7f1e9184dbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f1e5d5e5700 (LWP 13672)):
#0  0x7f1e8f6c407f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1e91f36abb in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0xf9bb50) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f1e91f36abb in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0xeb1f30, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f1e6b598e37 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f1e6b59cd98 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f1e6b598059 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f1e6b59cde2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f1e6b598059 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f1e6b59cde2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f1e6b598059 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f1e6b59ae23 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f1e91f3594f in QThreadPrivate::start(void*) (arg=0x150ae90) at
thread/qthread_unix.cpp:331
#12 0x7f1e8f6be4a4 in start_thread (arg=0x7f1e5d5e5700) at
pthread_create.c:334
#13 0x7f1e9184dbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f1e5cde4700 (LWP 13673)):
[KCrash Handler]
#6  0x7f1e5da06bef in mdb_cursor_open (txn=0x7f1e4800e260, dbi=0,
ret=ret@entry=0x7f1e5cde34e0) at mdb.c:7189
#7  0x7f1e5dc26c44 in Baloo::PostingDB::prefixIter(QByteArray const&)
(this=0x1, this=0x1, prefix=..., validate=...) at
/usr/src/debug/baloo-5.18.0/src/engine/postingdb.cpp:211
#8  0x7f1e5dc26c44 in Baloo::PostingDB::prefixIter(QByteArray const&)
(this=this@entry=0x7f1e5cde35d0, prefix=...) at
/usr/src/debug/baloo-5.18.0/src/engine/postingdb.cpp:246
#9  0x7f1e5dc2ff3d in
Baloo::Transaction::postingIterator(Baloo::EngineQuery const&) const
(this=this@entry=0x7f1e5cde3960, query=..

[kmix] [Bug 359417] New: kwin occasionally crashes

2016-02-14 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359417

Bug ID: 359417
   Summary: kwin occasionally crashes
   Product: kmix
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: jirisl...@gmail.com

Application: kmix (4.6)

Qt Version: 5.5.1
Operating System: Linux 4.4.1-17.g2b16688-default x86_64
Distribution: "openSUSE Tumbleweed (20160117) (x86_64)"

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

It seems to crash after suspend/resume cycle sometimes. I have 2 sound cards:
$ cat /proc/asound/cards
 0 [Audio  ]: USB-Audio - DigiHug USB Audio
  FiiO DigiHug USB Audio at usb-:00:14.0-3.2, full
speed
 1 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xf253 irq 32

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMix (kmix), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f0bfa6d8940 (LWP 1928))]

Thread 2 (Thread 0x7f0bcfffd700 (LWP 3776)):
#0  0x7f0bf9fa124d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0bf954e681 in poll_func (__timeout=-1, __nfds=2,
__fds=0x7f0bc8001730) at /usr/include/bits/poll2.h:46
#2  0x7f0bf954e681 in poll_func (ufds=0x7f0bc8001730, nfds=2, timeout=-1,
userdata=0x1cf5a00) at pulse/thread-mainloop.c:69
#3  0x7f0bf95402b1 in pa_mainloop_poll (m=m@entry=0x1c4de70) at
pulse/mainloop.c:844
#4  0x7f0bf95408ee in pa_mainloop_iterate (m=0x1c4de70, block=, retval=0x0) at pulse/mainloop.c:926
#5  0x7f0bf95409a0 in pa_mainloop_run (m=0x1c4de70,
retval=retval@entry=0x0) at pulse/mainloop.c:944
#6  0x7f0bf954e5e6 in thread (userdata=0x1da2860) at
pulse/thread-mainloop.c:100
#7  0x7f0bf1ac5cc8 in internal_thread_func (userdata=0x19129a0) at
pulsecore/thread-posix.c:81
#8  0x7f0bf1f014a4 in start_thread (arg=0x7f0bcfffd700) at
pthread_create.c:334
#9  0x7f0bf9fa9bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0bfa6d8940 (LWP 1928)):
[KCrash Handler]
#6  0x7f0bfa25fd78 in main_arena () at /lib64/libc.so.6
#7  0x7f0be2188329 in QXcbWindow::mapToNative(QRect const&, QXcbScreen
const*) const (this=, rect=..., screen=0x1898700) at
qxcbwindow.cpp:203
#8  0x7f0be218d588 in QXcbWindow::create() (this=0x1cde3f0) at
qxcbwindow.cpp:490
#9  0x7f0be217a721 in QXcbIntegration::createPlatformWindow(QWindow*) const
(this=, window=0x1c147d0) at qxcbintegration.cpp:201
#10 0x7f0bf60aa0d7 in QWindowPrivate::create(bool) (this=0x1e63950,
recursive=recursive@entry=false) at kernel/qwindow.cpp:392
#11 0x7f0bf60aa2cb in QWindow::create() (this=this@entry=0x1c147d0) at
kernel/qwindow.cpp:548
#12 0x7f0bf6878c88 in QWidgetPrivate::create_sys(unsigned long long, bool,
bool) (this=this@entry=0x1cd1440, window=window@entry=0,
initializeWindow=initializeWindow@entry=true,
destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1456
#13 0x7f0bf6879269 in QWidget::create(unsigned long long, bool, bool)
(this=0x1cdaf40, window=0, initializeWindow=,
destroyOldWindow=) at kernel/qwidget.cpp:1319
#14 0x7f0bf6883739 in QWidget::setVisible(bool) (this=0x1cdaf40,
visible=) at kernel/qwidget.cpp:8060
#15 0x7f0bfa2c97dc in ViewSliders::configurationUpdate() (this=0x1de5110)
at /usr/src/debug/kmix-15.12.1/gui/viewsliders.cpp:378
#16 0x7f0bfa2c802d in ViewSliders::constructionFinished() (this=0x1de5110)
at /usr/src/debug/kmix-15.12.1/gui/viewsliders.cpp:332
#17 0x7f0bfa2c3d5e in ViewBase::createDeviceWidgets() (this=0x1de5110) at
/usr/src/debug/kmix-15.12.1/gui/viewbase.cpp:170
#18 0x7f0bfa2c7b04 in ViewSliders::controlsChange(int) (this=0x1de5110,
changeType=) at
/usr/src/debug/kmix-15.12.1/gui/viewsliders.cpp:98
#19 0x7f0bf5b6ac8a in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const
(this=this@entry=0x7fff2d6030f8, object=object@entry=0x1de5110,
connectionType=Qt::DirectConnection, connectionType@entry=761278848,
returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=...,
val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:2212
#20 0x7f0bf5b7004d in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument)
(obj=0x1de5110, member=

[plasmashell] [Bug 359152] No application can be run after some uptime

2016-02-10 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359152

--- Comment #1 from Jiri Slaby  ---
Happened again. .xsession-errors says:

kdeinit5: Got EXEC_NEW '/usr/bin/firefox' from launcher.
kdeinit5: preparing to launch '/usr/bin/firefox'
No protocol specified
Error: cannot open display: :0
kdeinit5: PID 3839 terminated.

The first "No protocol specified" is this:
UnmapNotify: 41943074
Unknown toplevel for MapNotify
UnmapNotify: 39907572
UnmapNotify: 18874378
UnmapNotify: 18874378
CreateNotify: 18874392
QXcbConnection: XCB error: 3 (BadWindow), sequence: 45553, resource id:
18874392, major code: 18 (ChangeProperty), minor code: 0
Grab Released
Transaction status changed: "finished" "(100%)"
Transaction "/1_adacdeda" finished with status "success" in 20 seconds
Cache transaction finished successfully
Updates changed, getting updates!
Transaction status changed: "wait" "(101%)"
Transaction status changed: "setup" "(101%)"
Transaction status changed: "query" "(101%)"
Transaction status changed: "refresh-cache" "(0%)"
Got update package: "kernel-default;4.4.1-3.1.g2b16688;x86_64;k:s" , summary:
"The Standard Kernel" , type: "enhancement"
Got update package: "youtube-dl;2016.02.09.1-302.1;noarch;packman" , summary:
"A tool for downloading from Youtube" , type: "enhancement"
Got update package: "libgstreamer-1_0-0;1.6.3-65.2;x86_64;packman" , summary:
"Streaming-Media Framework Runtime" , type: "enhancement"
Got update package: "gstreamer;1.6.3-65.2;x86_64;packman" , summary:
"Streaming-Media Framework Runtime" , type: "enhancement"
Got update package: "gstreamer-lang;1.6.3-65.2;noarch;packman" , summary:
"Languages for package gstreamer" , type: "enhancement"
Got update package: "openSUSE-2016-177;1;noarch;repo-update" , summary:
"Recommended update for libqt5-qtdeclarative" , type: "bugfix"
Got update package: "openSUSE-2016-178;1;noarch;repo-update" , summary:
"Recommended update for libqt5-qtbase" , type: "bugfix"
Got update package: "openSUSE-2016-174;1;noarch;repo-update" , summary:
"Recommended update for poppler, poppler-qt, poppler-qt5, kdepim" , type:
"bugfix"
Transaction "/2_cadccdbb" finished with status "success" in 1 seconds
Check updates transaction finished successfully
Total number of updates:  8
Transaction status changed: "finished" "(100%)"
No protocol specified
xcb_connection_has_error() returned true
No protocol specified
xcb_connection_has_error() returned true
No protocol specified
xcb_connection_has_error() returned true
No protocol specified
xcb_connection_has_error() returned true
No protocol specified
xcb_connection_has_error() returned true

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


[plasmashell] [Bug 359152] New: No application can be run after some uptime

2016-02-08 Thread Jiri Slaby via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359152

Bug ID: 359152
   Summary: No application can be run after some uptime
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jirisl...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

After some activity, maybe suspend/resume cycle is needed to reproduce, I
cannot run anything. .xsession-errors-:0 says:
No protocol specified
Error: couldn't open display :0

I can switch to text console 1 and run:
DISPLAY=:0 xterm 

It execs the xterm properly.

drkonqi does not trigger. So if anything crashes in the background, I don't
know what. Dmesg only reports segfaults in kactivitymanager like this:
kactivitymanage[929]: segfault at 7fc6daef5d10 ip 7fc6db13c69a sp
7ffec5560d38 error 4 in libQt5Sql.so.5.5.1[7fc6db127000+3f000]
But this looks like it happens on terminating the session.

Any ideas how to debug this?

$ rpm -q `rpmqpack |grep plasma|sort`
patterns-openSUSE-kde_plasma-20150918-12.1.x86_64
plasma-framework-5.16.0-3.1.x86_64
plasma-framework-components-5.16.0-3.1.x86_64
plasma-framework-lang-5.16.0-3.1.noarch
plasma-framework-private-5.16.0-3.1.x86_64
plasma-nm5-5.4.3-3.2.x86_64
plasma-nm5-lang-5.4.3-3.2.noarch
plasma-nm5-openvpn-5.4.3-3.2.x86_64
plasma-nm5-pptp-5.4.3-3.2.x86_64
plasma-nm5-vpnc-5.4.3-3.2.x86_64
plasma5-addons-5.4.3-3.1.x86_64
plasma5-addons-kimpanel-5.4.3-3.1.x86_64
plasma5-addons-lang-5.4.3-3.1.noarch
plasma5-desktop-5.4.3-6.2.x86_64
plasma5-desktop-branding-openSUSE-13.2-26.1.x86_64
plasma5-desktop-lang-5.4.3-6.2.noarch
plasma5-pa-5.4.3-3.1.x86_64
plasma5-pa-lang-5.4.3-3.1.noarch
plasma5-pk-updates-0.2-3.2.x86_64
plasma5-session-5.4.3-3.1.noarch
plasma5-workspace-5.4.3-6.1.x86_64
plasma5-workspace-branding-openSUSE-13.2-26.1.x86_64
plasma5-workspace-lang-5.4.3-6.1.noarch
plasma5-workspace-libs-5.4.3-6.1.x86_64
python-kde4-plasma-4.14.3-2.11.x86_64


Reproducible: Sometimes

Steps to Reproduce:
I don't know how to actually reproduce.

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