[digikam] [Bug 357168] New: digikam goes reset
https://bugs.kde.org/show_bug.cgi?id=357168 Bug ID: 357168 Summary: digikam goes reset Product: digikam Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: fa372...@scarlet.be Application: digikam (4.12.0) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 4.2.0-22-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed:selecting another photo for inspection, photo was on the camera Nikkon coolpix s9200 wich was not detected automaticly and neither is in the database so I deceded to use "s9100" in place. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9da52d5b40 (LWP 11341))] Thread 7 (Thread 0x7f9d7fe42700 (LWP 11345)): #0 0x7f9d9e52b8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f9d8a6e512c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x7f9d9ba426aa in start_thread (arg=0x7f9d7fe42700) at pthread_create.c:333 #3 0x7f9d9e536eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f9d7bd54700 (LWP 11350)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9d9f091286 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1e35e00) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1e35d40, mutex=mutex@entry=0x1e35d38, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x005fffb4 in Digikam::ScanController::run (this=0x1e43360) at /build/digikam-131Z2v/digikam-4.12.0/core/app/database/scancontroller.cpp:725 #4 0x7f9d9f090d1c in QThreadPrivate::start (arg=0x1e43360) at thread/qthread_unix.cpp:349 #5 0x7f9d9ba426aa in start_thread (arg=0x7f9d7bd54700) at pthread_create.c:333 #6 0x7f9d9e536eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f9d7b553700 (LWP 11351)): #0 0x7f9d98021884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9d97fdc1ee in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9d97fdd0a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9d97fdd2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9d9f1d120e in QEventDispatcherGlib::processEvents (this=0x7f9d6c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7f9d9f19f0d1 in QEventLoop::processEvents (this=this@entry=0x7f9d7b552a40, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f9d9f19f445 in QEventLoop::exec (this=this@entry=0x7f9d7b552a40, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f9d9f08e4f9 in QThread::exec (this=this@entry=0x1ed68e0) at thread/qthread.cpp:538 #8 0x7f9d9f17f133 in QInotifyFileSystemWatcherEngine::run (this=0x1ed68e0) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x7f9d9f090d1c in QThreadPrivate::start (arg=0x1ed68e0) at thread/qthread_unix.cpp:349 #10 0x7f9d9ba426aa in start_thread (arg=0x7f9d7b553700) at pthread_create.c:333 #11 0x7f9d9e536eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f9d7ad52700 (LWP 11365)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9d9f091286 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x209da00) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1f7cdf0, mutex=mutex@entry=0x1f7cde8, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f9da340ef02 in Digikam::ParkingThread::run (this=0x1f7cdd0) at /build/digikam-131Z2v/digikam-4.12.0/core/libs/threads/threadmanager.cpp:119 #4 0x7f9d9f090d1c in QThreadPrivate::start (arg=0x1f7cdd0) at thread/qthread_unix.cpp:349 #5 0x7f9d9ba426aa in start_thread (arg=0x7f9d7ad52700) at pthread_create.c:333 #6 0x7f9d9e536eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f9d7906b700 (LWP 11367)): #0 0x7f9d9e52b8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f9d97fdd1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9d97fdd2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9d9f1d120e in QEventDispatcherGlib::processEvents (this=0x7f9d640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f9d9f19f0d1 in QEventLoop::processEvents (this=this@entry=0x7f9d7906aa40, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f9d9f19f445 in QEventL
[plasmashell] [Bug 357169] New: Plasma crash, when using programs menu
https://bugs.kde.org/show_bug.cgi?id=357169 Bug ID: 357169 Summary: Plasma crash, when using programs menu Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sla...@lach.art.pl CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.2.1-1-desktop x86_64 Distribution: "openSUSE Tumbleweed (20151124) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: When I run evolution on programs menu(I don't know it's kicker or kickof). It cause when running evolution by search. The crash can be reproduced sometimes. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f997da9e8c0 (LWP 1651))] Thread 13 (Thread 0x7f996707f700 (LWP 1653)): #0 0x7f997705f24d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f997bf1c432 in () at /usr/lib64/libxcb.so.1 #2 0x7f997bf1e007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f99691cee29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f997775094f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f99768664a4 in start_thread (arg=0x7f996707f700) at pthread_create.c:334 #6 0x7f9977067bdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f995700 (LWP 1920)): #0 0x7f9973755767 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9973756193 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f997375636c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f997797552b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f997791f63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f997774bb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f997a9f79a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f997775094f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f99768664a4 in start_thread (arg=0x7f995700) at pthread_create.c:334 #9 0x7f9977067bdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f99531ee700 (LWP 1932)): #0 0x7ffce7708c41 in clock_gettime () #1 0x7f99770747d6 in __GI___clock_gettime (clock_id=1, tp=0x7f99531edaa0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f99777fc1a6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f99779730e9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f99779735f5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f997797498e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f997375588d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f9973756193 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f997375636c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f997797552b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f997791f63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f997774bb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f997a9f79a5 in () at /usr/lib64/libQt5Qml.so.5 #13 0x7f997775094f in () at /usr/lib64/libQt5Core.so.5 #14 0x7f99768664a4 in start_thread (arg=0x7f99531ee700) at pthread_create.c:334 #15 0x7f9977067bdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f99517cb700 (LWP 1979)): #0 0x7ffce7708c41 in clock_gettime () #1 0x7f99770747d6 in __GI___clock_gettime (clock_id=1, tp=0x7f99517caaa0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f99777fc1a6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f99779730e9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f99779735f5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f997797498e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f997375588d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f9973756193 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f997375636c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f997797552b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f997791f63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f997774bb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f997a9f79a5 in () at /usr/lib64/libQt5Qml.so.5 #13 0x7f997775094f in () at /usr/lib64/libQt5Core.so.5 #14 0x7f99768664a4 in start_thread (arg=0x7f99517cb700) at pthread_create.c:334 #
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 --- Comment #7 from Viktor Kuzmin --- konsole-4 have no problems with infinality. Also getting rid of infinality is really not an option IMHO. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 --- Comment #8 from Sven Brauch --- Yes I guess this is a Qt5.5+ bug, no? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357168] digikam goes reset
https://bugs.kde.org/show_bug.cgi?id=357168 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Import CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 357170] New: plasmashell loaded longer than ksplash
https://bugs.kde.org/show_bug.cgi?id=357170
Bug ID: 357170
Summary: plasmashell loaded longer than ksplash
Product: ksplash
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: l.lu...@kde.org
Reporter: bigworm...@mail.ru
When I start plasma, I see ksplash, but when it dissapear I see that plasma
still downloading(black screen, then wallpaper and widgets). When I start
plasma with openbox, I have another issue - ksplash loading is longer than
should be.
Reproducible: Always
.xserver-errors
startkde: Starting up...
Service started, version: 6.2.0
Baloo File Indexing has been disabled
Не вдається відкрити бібліотеку «/usr/lib/libkdeinit5_lib/kdeconnectd».
Cannot load library /usr/lib/libkdeinit5_lib/kdeconnectd:
(/usr/lib/libkdeinit5_lib/libkdeconnectd.so: не вдалося відкрити файл об’єктів
спільного використання: Немає такого файла або каталогу)
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 740/PCIe/SSE2
OpenGL version string: 4.5.0 NVIDIA 358.16
OpenGL shading language version string: 4.50 NVIDIA
Driver: NVIDIA
Driver version: 358.16
GPU class: Unknown
OpenGL version: 4.5
GLSL version: 4.50
X server version: 1.18
Linux kernel version: 4.2.5
Requires strict binding:no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine:no
kscreen: Primary output changed from KScreen::Output(Id: 638 , Name: "VGA-0" )
( "VGA-0" ) to KScreen::Output(Id: 638 , Name: "VGA-0" ) ( "VGA-0" )
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
last screen is < 0 so putting containment on screen 0
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
No metadata file in the package, expected it at:
"/home/bugworm/Картинки//metadata.desktop"
No metadata file in the package, expected it at:
"/home/bugworm/Картинки//metadata.desktop"
No metadata file in the package, expected it at:
"/home/bugworm/Картинки//metadata.desktop"
kscreen: Primary output changed from KScreen::Output(Id: 638 , Name: "VGA-0" )
( "VGA-0" ) to KScreen::Output(Id: 638 , Name: "VGA-0" ) ( "VGA-0" )
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
kbuildsycoca4 running...
yakuake(2611)/kdecore (KLibrary) findLibraryInternal: plugins should not have a
'lib' prefix: "libkonsolepart.so"
qml: Reading townStrings from configuration:
[{"placeAlias":"Dniprodzerzhyns’k","townString":"Ukraina/Dnipropetrovsk/Dniprodzerzhyns’k"}]
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
yakuake(2611)/konsole Konsole::Session::run: Attempted to re-run an alrea
[kdenlive] [Bug 357155] Deleting any video/audio track causes kdenlive to crash with a segmentation fault
https://bugs.kde.org/show_bug.cgi?id=357155 --- Comment #5 from Anton Eliasson --- That was quick! I already had frei0r-plugins installed, version 1.4.0+git20151222.2bef628f-0ubuntu0~sunab~vivid1 from the PPA. I found that it lacks the cairoblend transition (/usr/lib/frei0r-1/cairoblend.so). Downgrading to version 1.4-3 from vivid/universe made the crash go away. I'll talk to sunab about why it is missing from his package. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357171] New: Create new symlink dialog shows directories but not files
https://bugs.kde.org/show_bug.cgi?id=357171 Bug ID: 357171 Summary: Create new symlink dialog shows directories but not files Product: dolphin Version: 15.08.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: p.r.worr...@gmail.com Right Click => Create New => Basic Link to File or Directory => Browse This does not show files in the browser dialog, only directories Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 357112] Amarok
https://bugs.kde.org/show_bug.cgi?id=357112 Myriam Schweingruber changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |INVALID --- Comment #3 from Myriam Schweingruber --- (In reply to Reinhard Auner from comment #2) >Hello, dear Myriam, I am really sorry, but I am not able to reproduce >this bug, but what I am currently doing is to install all the >debuginfo-packages of my openSUSE in order to be able to produce more >detailed and helpful reports for you develpoers in the future, ok? >yours, Reinhard Auner * Gesendet:* Freitag, 25. Dezember 2015 um 16:36 >Uhr Yes, no problem. I will close this report as invalid, if it is not reproducible there is sadly not much we can do about with the current information. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 299218] Amarok script API track signals are unreliable, undocumented
https://bugs.kde.org/show_bug.cgi?id=299218 --- Comment #11 from Myriam Schweingruber --- (In reply to mg from comment #10) > how can I access the code to work on fixing this bug? Please see the links I gave in comment #8, every necessary information is there :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357172] New: Plasma crashed filling in a new conjunction to a program into the desktop
https://bugs.kde.org/show_bug.cgi?id=357172 Bug ID: 357172 Summary: Plasma crashed filling in a new conjunction to a program into the desktop Product: plasmashell Version: 5.4.3 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: stau...@holzbau-mobil.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) (Compiled from sources) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was on the desktop Folder. Then i filled a new conjuntion in. Then plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7f125107c0 (LWP 1646))] Thread 7 (Thread 0x7f7efbf9a700 (LWP 1648)): #0 0x7f7f0ba60c1d in poll () at /lib64/libc.so.6 #1 0x7f7f10987422 in () at /usr/lib64/libxcb.so.1 #2 0x7f7f1098900f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f7efe0eac29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f7f0c15755f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f7f0b26a0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7f0ba6904d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f7ef914a700 (LWP 1689)): #0 0x7f7f08183cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f7f08141028 in g_main_context_release () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7f08141e0e in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7f08141f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7f0c388a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7f0c32fa63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f7f0c15284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f7f0f43b5f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f7f0c15755f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f7f0b26a0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f7f0ba6904d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f7ee204d700 (LWP 1804)): #0 0x7f7f0c389450 in () at /usr/lib64/libQt5Core.so.5 #1 0x7f7f081418f1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7f08141df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7f08141f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7f0c388a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7f0c32fa63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f7f0c15284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f7f0f43b5f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f7f0c15755f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f7f0b26a0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f7f0ba6904d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f7edbfff700 (LWP 1863)): #0 0x7f7f0813f1ca in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f7f0814144b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7f08141d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7f08141f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7f0c388a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7f0c32fa63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f7f0c15284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f7f0f43b5f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f7f0c15755f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f7f0b26a0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f7f0ba6904d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f7edabd7700 (LWP 1894)): #0 0x7f7f0b26e05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7f11bee7eb in () at /usr/lib64/libQt5Script.so.5 #2 0x7f7f11bee819 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f7f0b26a0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f7f0ba6904d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f7e4d868700 (LWP 1917)): #0 0x7f7f0813f244 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f7f0814144b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7f08141d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7f08141f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7f0c388a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7f0c32fa63 in QEventLoop::exec(QFlags)
[kdenlive] [Bug 357151] Crashes when trying to render
https://bugs.kde.org/show_bug.cgi?id=357151 --- Comment #2 from Jean-Baptiste Mardelle --- You seem to be using an old development version of Kdenlive. Please update to a stable release or current git. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357173] New: Krita crashes on close - segmentation fault
https://bugs.kde.org/show_bug.cgi?id=357173 Bug ID: 357173 Summary: Krita crashes on close - segmentation fault Product: krita Version: 2.9.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: genmav...@gmail.com Application: krita (2.9.10) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 4.2.0-22-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I had saved the file I was working on, and clicked on File>Exit, and the program crashed instead of exiting cleanly. The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe023ec7840 (LWP 12333))] Thread 4 (Thread 0x7fe001d2a700 (LWP 12341)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe021a3e286 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3cbad60) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0x3cbad10, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fe021a3a063 in QSemaphore::acquire (this=this@entry=0x3cbaa30, n=n@entry=1) at thread/qsemaphore.cpp:144 #4 0x7fe01e63c74b in KisTileDataPooler::waitForWork (this=0x3cbaa20) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/image/tiles3/kis_tile_data_pooler.cc:165 #5 KisTileDataPooler::run (this=0x3cbaa20) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/image/tiles3/kis_tile_data_pooler.cc:187 #6 0x7fe021a3dd1c in QThreadPrivate::start (arg=0x3cbaa20) at thread/qthread_unix.cpp:349 #7 0x7fe01b8026aa in start_thread (arg=0x7fe001d2a700) at pthread_create.c:333 #8 0x7fe021159eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fdff6ad9700 (LWP 12342)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fe021a3c79a in thread_sleep (ti=ti@entry=0x7fdff6ad8da0) at thread/qthread_unix.cpp:492 #2 0x7fe021a3d07d in QThread::msleep (msecs=msecs@entry=700) at thread/qthread_unix.cpp:518 #3 0x7fe01e6650da in KisTileDataSwapper::run (this=0x3cbaa60) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:97 #4 0x7fe021a3dd1c in QThreadPrivate::start (arg=0x3cbaa60) at thread/qthread_unix.cpp:349 #5 0x7fe01b8026aa in start_thread (arg=0x7fdff6ad9700) at pthread_create.c:333 #6 0x7fe021159eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fdff72da700 (LWP 12343)): #0 0x7fe021150743 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fe021b7aeff in qt_safe_select (nfds=16, fdread=fdread@entry=0x7fdff0540808, fdwrite=fdwrite@entry=0x7fdff0540aa0, fdexcept=fdexcept@entry=0x7fdff0540d38, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:79 #2 0x7fe021b80c5f in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fdff0540d38, writefds=0x7fdff0540aa0, readfds=0x7fdff0540808, nfds=, this=0x7fdff910) at kernel/qeventdispatcher_unix.cpp:649 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fdff0540650, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223 #4 0x7fe021b81118 in QEventDispatcherUNIX::processEvents (this=0x7fdff910, flags=...) at kernel/qeventdispatcher_unix.cpp:944 #5 0x7fe021b4c0d1 in QEventLoop::processEvents (this=this@entry=0x7fdff72d9d40, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fe021b4c445 in QEventLoop::exec (this=this@entry=0x7fdff72d9d40, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fe021a3b4f9 in QThread::exec (this=this@entry=0x3efae50) at thread/qthread.cpp:538 #8 0x7fe021b2c133 in QInotifyFileSystemWatcherEngine::run (this=0x3efae50) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x7fe021a3dd1c in QThreadPrivate::start (arg=0x3efae50) at thread/qthread_unix.cpp:349 #10 0x7fe01b8026aa in start_thread (arg=0x7fdff72da700) at pthread_create.c:333 #11 0x7fe021159eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fe023ec7840 (LWP 12333)): [KCrash Handler] #6 QMutex::lock (this=this@entry=0x60) at thread/qmutex.cpp:150 #7 0x7fe021b517a9 in QCoreApplication::postEvent (receiver=0x1a3871f0, event=0x19b7c4d0, priority=priority@entry=0) at kernel/qcoreapplication.cpp:1360 #8 0x7fe021b51ac7 in QCoreApplication::postEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1313 #9 0x7fe021b60a74 in QObject::deleteLater (this=) at kernel/q
[plasmashell] [Bug 356874] Warn user about locked widgets in wallpaper settings
https://bugs.kde.org/show_bug.cgi?id=356874 --- Comment #4 from Elvis Stansvik --- Yea, that'll work. I would have found that when I was first searching around. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 356337] Error
https://bugs.kde.org/show_bug.cgi?id=356337 Myriam Schweingruber changed: What|Removed |Added Product|systemsettings |plasma4 Component|general |widget-clock -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357174] New: KMail5 Crash when moving folder to inbox
https://bugs.kde.org/show_bug.cgi?id=357174 Bug ID: 357174 Summary: KMail5 Crash when moving folder to inbox Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: a.skemb...@gmail.com Application: kmail (5.0.3) Qt Version: 5.5.1 Operating System: Linux 4.3.3-1-default x86_64 Distribution: "openSUSE Tumbleweed (20151221) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I imported a large number of e-mails from another computer. Moving the imported folders to the main "inbox" folder (so that all folders are under "inbox" instead of the container of the imports) causes the crash. It does not happen everytime, but 2 out of 3 times Kmail will crash. Also, the folder is eventually moved - restarting KMail shows the folder in the intended location. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5469e17940 (LWP 4544))] Thread 8 (Thread 0x7f5443aec700 (LWP 4545)): #0 0x7f5466e0e24d in poll () from /lib64/libc.so.6 #1 0x7f545a4f2432 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f545a4f4007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f5445814e29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f546771694f in QThreadPrivate::start (arg=0x9d93e0) at thread/qthread_unix.cpp:331 #5 0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5466e16bdd in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f5439456700 (LWP 4555)): #0 0x7f5466e0a22d in read () from /lib64/libc.so.6 #1 0x7f545d00e210 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f545cfcbd94 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f545cfcc208 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f545cfcc36c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f546793b52b in QEventDispatcherGlib::processEvents (this=0x7f54340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f54678e563a in QEventLoop::exec (this=this@entry=0x7f5439455c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f5467711b1c in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f546771694f in QThreadPrivate::start (arg=0xf807c0) at thread/qthread_unix.cpp:331 #9 0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f5466e16bdd in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f5433fff700 (LWP 4556)): #0 0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f545835e3bb in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f545835e3f9 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5466e16bdd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f53f2698700 (LWP 4563)): #0 0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f545806c764 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5466e16bdd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f53f1e97700 (LWP 4564)): #0 0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f545806d793 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5466e16bdd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f53f1696700 (LWP 4565)): #0 0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f545806d793 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5466e16bdd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f53f0e95700 (LWP 4566)): #0 0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f545806d793 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5466e16bdd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5469e17940 (LWP 4544)): [KCrash Handler] #6 count (this=0x50004) at ../../src/corelib/tools/qvector.h:203 #7 QSortFilterProxyModel::sibling (this=, row=1, column=1, idx=...) at itemmodels/qsortfilterproxy
[kcalc] [Bug 356355] KCalc shouldn't keep formatting of copied number
https://bugs.kde.org/show_bug.cgi?id=356355 dimon...@gmail.com changed: What|Removed |Added CC||dimon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357175] New: dolphin 4.13.3 ignore Drag & Drop action type
https://bugs.kde.org/show_bug.cgi?id=357175 Bug ID: 357175 Summary: dolphin 4.13.3 ignore Drag & Drop action type Product: dolphin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: c...@raymisoft.de In my Qt5 application will drag action starts with code fragment: drag->exec(Qt::CopyAction, Qt::CopyAction); Dolphin show correct mouse symbol (+) for copy action. But after dropping, popped up the context menu to choose: copy, move and link. All three menu items are enabled and be executed. But only the action copy should allowed. Krusader have this identical problem. A cross check with GNOME nautilus and Xfce thunar is a proof, than my QT5 application working correct. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 357164] Saving PNG image with custom name.
https://bugs.kde.org/show_bug.cgi?id=357164 --- Comment #1 from Boudhayan Gupta --- I understand English may not be your first language, but I do not understand what you're trying to say. Could you explain once again what you're trying to do and what happens? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 330676] PIcture download
https://bugs.kde.org/show_bug.cgi?id=330676 --- Comment #11 from Gabor Fekete --- Created attachment 96300 --> https://bugs.kde.org/attachment.cgi?id=96300&action=edit New crash information added by DrKonqi digikam (4.0.0) on KDE Platform 4.14.2 using Qt 4.8.6 - What I was doing when the application crashed: The program crashed each time I tried to download pictures from Nikon D3200 -- Backtrace (Reduced): #6 Digikam::Album::globalID (this=0x0) at /build/buildd/digikam-4.0.0/core/digikam/album/album.cpp:227 #7 0x007d3d43 in Digikam::ImportUI::slotDownload (this=0x423e040, onlySelected=, deleteAfter=, album=0x0) at /build/buildd/digikam-4.0.0/core/utilities/importui/main/importui.cpp:1475 #8 0x007d4d26 in slotDownloadSelected (this=) at /build/buildd/digikam-4.0.0/core/utilities/importui/main/importui.cpp:1395 #9 Digikam::ImportUI::qt_static_metacall (_o=0x423e040, _c=69889032, _id=0, _a=0x10) at /build/buildd/digikam-4.0.0/obj-x86_64-linux-gnu/core/utilities/importui/importui.moc:199 [...] #11 0x7f5bec5b7a62 in QAction::triggered (this=this@entry=0x5a81b40, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 330676] PIcture download
https://bugs.kde.org/show_bug.cgi?id=330676 Gabor Fekete changed: What|Removed |Added CC||gabor.fek...@flamma.eu -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 357176] New: volume mount failed after upgrade of the parallel system to Win10
https://bugs.kde.org/show_bug.cgi?id=357176 Bug ID: 357176 Summary: volume mount failed after upgrade of the parallel system to Win10 Product: unknown Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ruediger.muelle...@t-online.de Beim Zugriff auf „Volume“ ist ein Fehler aufgetreten, die Meldung lautet: The requested operation has failed: Error mounting /dev/sdb1 at /media/me15tera11erkla55en/Volume : Command-line 'mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdb1" "/media/me15tera11erkla55en/Volume"' exited with non-zero exit status 14 : The disk contains an unclean file system (0,0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sdb1/' : Operation not permitted. The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Reproducible: Always Steps to Reproduce: 1. mount at system-start failed 2. manual mount at konsole with kdesudo failed 3. ? security or user changed within the upgrade of Windows ? two devices sda: windows10 works with all C: and D: (without linux) sdb: Linux only works with the linux-partition of D: the mount of the rest of D: and device C: is impossible the use of Thunderbird is so far truncated to the postal-input -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 357177] New: krunner crashes when using wayland
https://bugs.kde.org/show_bug.cgi?id=357177 Bug ID: 357177 Summary: krunner crashes when using wayland Product: krunner Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: windows Assignee: m...@vhanda.in Reporter: alinm.el...@gmail.com start a wayland session try to start krunner nothing happens. start it from konsole... seg fault bt attached. Reproducible: Always Steps to Reproduce: see above 1. 2. 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357178] New: Crash when copying files
https://bugs.kde.org/show_bug.cgi?id=357178 Bug ID: 357178 Summary: Crash when copying files Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: supp...@bb-services.co.za CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.0) Qt Version: 5.5.1 Operating System: Linux 4.2.7-300.fc23.i686+PAE i686 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: Copied a single folder from an extern hard drive using drag 'n drop. The copy process when I clicked on the + button on the information screen to track progress -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb18a8840 (LWP 2052))] Thread 12 (Thread 0xb1462b40 (LWP 2059)): #0 0x in __kernel_vsyscall () #1 0x in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x in _xcb_conn_wait () at /lib/libxcb.so.1 #3 0x in xcb_wait_for_event () at /lib/libxcb.so.1 #4 0x in QXcbEventReader::run() () at /lib/libQt5XcbQpa.so.5 #5 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5 #6 0x in start_thread (arg=0xb1462b40) at pthread_create.c:334 #7 0x in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 11 (Thread 0xaff1eb40 (LWP 2078)): #0 0x in __kernel_vsyscall () #1 0x in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x in g_poll () at /lib/libglib-2.0.so.0 #3 0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0 #4 0x in g_main_context_iteration () at /lib/libglib-2.0.so.0 #5 0x in QEventDispatcherGlib::processEvents(QFlags) () at /lib/libQt5Core.so.5 #6 0x in QEventLoop::processEvents(QFlags) () at /lib/libQt5Core.so.5 #7 0x in QEventLoop::exec(QFlags) () at /lib/libQt5Core.so.5 #8 0x in QThread::exec() () at /lib/libQt5Core.so.5 #9 0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5 #10 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5 #11 0x in start_thread (arg=0xaff1eb40) at pthread_create.c:334 #12 0x in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 10 (Thread 0xad352b40 (LWP 2094)): #0 0x in __vdso_clock_gettime () #1 0x in __GI___clock_gettime (clock_id=1, tp=0xad351ed4) at ../sysdeps/unix/clock_gettime.c:115 #2 0x in qt_gettime() () at /lib/libQt5Core.so.5 #3 0x in QTimerInfoList::updateCurrentTime() () at /lib/libQt5Core.so.5 #4 0x in QTimerInfoList::timerWait(timespec&) () at /lib/libQt5Core.so.5 #5 0x in timerSourcePrepare(_GSource*, int*) () at /lib/libQt5Core.so.5 #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/libQt5Core.so.5 #10 0x in QEventLoop::processEvents(QFlags) () at /lib/libQt5Core.so.5 #11 0x in QEventLoop::exec(QFlags) () at /lib/libQt5Core.so.5 #12 0x in QThread::exec() () at /lib/libQt5Core.so.5 #13 0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5 #14 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5 #15 0x in start_thread (arg=0xad352b40) at pthread_create.c:334 #16 0x in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 9 (Thread 0xabfb5b40 (LWP 2095)): #0 0x in __vdso_clock_gettime () #1 0x in __GI___clock_gettime (clock_id=1, tp=0xabfb4ed4) at ../sysdeps/unix/clock_gettime.c:115 #2 0x in qt_gettime() () at /lib/libQt5Core.so.5 #3 0x in QTimerInfoList::updateCurrentTime() () at /lib/libQt5Core.so.5 #4 0x in QTimerInfoList::timerWait(timespec&) () at /lib/libQt5Core.so.5 #5 0x in timerSourcePrepare(_GSource*, int*) () at /lib/libQt5Core.so.5 #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/libQt5Core.so.5 #10 0x in QEventLoop::processEvents(QFlags) () at /lib/libQt5Core.so.5 #11 0x in QEventLoop::exec(QFlags) () at /lib/libQt5Core.so.5 #12 0x in QThread::exec() () at /lib/libQt5Core.so.5 #13 0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5 #14 0x in QThreadPrivate::start(void*) () at /lib/libQt5Co
[krunner] [Bug 357177] krunner crashes when using wayland
https://bugs.kde.org/show_bug.cgi?id=357177 --- Comment #1 from Alin M Elena --- Created attachment 96301 --> https://bugs.kde.org/attachment.cgi?id=96301&action=edit bt bt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357168] digikam goes reset
https://bugs.kde.org/show_bug.cgi?id=357168 --- Comment #1 from caulier.gil...@gmail.com --- Problem is probably fixed with most recent digiKam releases as 4.13.0 or 4.14.0 Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 347352] Shortcut for keyboard layout switcher is not remembered
https://bugs.kde.org/show_bug.cgi?id=347352 Rafis Kamaliev changed: What|Removed |Added CC||ra...@pisem.net --- Comment #5 from Rafis Kamaliev --- openSUSE Leap 42.1 (x86_64)" Linux linux-b5px 4.1.13-5-default #1 SMP PREEMPT Thu Nov 26 16:35:17 UTC 2015 (49475c3) x86_64 x86_64 x86_64 GNU/Linux KDE 4.14.10 Plasma5 5.4.3-6.1 Shortcut for keyboard layout switcher is assigned but not working. Layout indicator is not displayed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356312] DVD wizard freezes
https://bugs.kde.org/show_bug.cgi?id=356312 --- Comment #4 from noeb...@web.de --- It seems to depend on the graphic driver. If I use NVIDIA 352.63 the problem occurs. If I use X.Org-X-Server (Nouveau), it works. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356820] Open Filename in Kate causes crash
https://bugs.kde.org/show_bug.cgi?id=356820 Sandro Mathys changed: What|Removed |Added CC||san...@mathys.io --- Comment #2 from Sandro Mathys --- Got the same issue, with kate 15.08.3, also on Fedora 23. Not running Compiz (not even installed). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357179] New: Email remains in inbox after moving it to a folder
https://bugs.kde.org/show_bug.cgi?id=357179 Bug ID: 357179 Summary: Email remains in inbox after moving it to a folder Product: kmail2 Version: 4.14.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl When an email is moved from inbox to another folder, it re-appears in inbox ( the copy in the other folder stays there btw ). Reproducible: Always Steps to Reproduce: 1. receive an email 2. move it from inbox to another folder 3. verify that the email has been moved to the other folder 4. go back to the inbox 5. the moved email appears again in the inbox This behavior is the same for messages moved manually as well as filtered emails Actual Results: The moved email re-appears in inbox Expected Results: The moved email should not re-appear in the inbox, as it has been copied to another folder. I'm using pop email. I recently updated from openSUSE_13.1 where emails moving and filtering worked just great ( as expected ). Currently running kmail-4.14.10. Looks a bit similar to bug report: 350059 But indeed also for me email filters are at the moment not usuable. Restarting akonadictl does not help. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356820] Open Filename in Kate causes crash
https://bugs.kde.org/show_bug.cgi?id=356820 --- Comment #3 from Kåre Särs --- Can you try to disable compositing or set the rendering engine to XRender? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357180] New: Segfault after trying to select unreadably small text in konsole 15.12
https://bugs.kde.org/show_bug.cgi?id=357180 Bug ID: 357180 Summary: Segfault after trying to select unreadably small text in konsole 15.12 Product: konsole Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: p...@konecny.at Application: konsole (15.12.0) Qt Version: 5.5.1 Operating System: Linux 4.2.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Trying to select any text because after a recent Arch update I can only see very small white dots isntead of text. - Unusual behavior I noticed: The unreadably small (?) text. I can't even resize it. Trying to select anything with the mouse causes this segfault. See attached screencast. - Custom settings of the application: None that I know of. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8107d1e840 (LWP 3912))] Thread 2 (Thread 0x7f80fc358700 (LWP 3914)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f80ff9b6b33 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f80ff9b6287 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8112f664a4 in start_thread (arg=0x7f80fc358700) at pthread_create.c:334 #4 0x7f811ac5113d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f8107d1e840 (LWP 3912)): [KCrash Handler] #5 0x7f811a8c4d6c in Konsole::Screen::copyLineToStream (this=this@entry=0xbe79a0, line=line@entry=594, start=0, count=1658, count@entry=-1, decoder=decoder@entry=0x7ffc0a24ac00, appendNewLine=appendNewLine@entry=true, preserveLineBreaks=true, trimTrailingSpaces=false) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/Screen.cpp:1273 #6 0x7f811a8c51b1 in Konsole::Screen::writeToStream (this=this@entry=0xbe79a0, decoder=decoder@entry=0x7ffc0a24ac00, startIndex=startIndex@entry=984175, endIndex=endIndex@entry=987495, preserveLineBreaks=preserveLineBreaks@entry=true, trimTrailingSpaces=trimTrailingSpaces@entry=false) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/Screen.cpp:1184 #7 0x7f811a8c5ef0 in Konsole::Screen::text (this=0xbe79a0, startIndex=984175, endIndex=987495, preserveLineBreaks=preserveLineBreaks@entry=true, trimTrailingSpaces=trimTrailingSpaces@entry=false, html=false) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/Screen.cpp:1137 #8 0x7f811a8c5fba in Konsole::Screen::selectedText (this=, preserveLineBreaks=preserveLineBreaks@entry=true, trimTrailingSpaces=trimTrailingSpaces@entry=false, html=html@entry=false) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/Screen.cpp:1115 #9 0x7f811a8929cf in Konsole::Emulation::checkSelectedText (this=0xc15380) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/Emulation.cpp:98 #10 0x7f81177231a7 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #11 0x7f811a8f55d6 in Konsole::TerminalDisplay::extendSelection (this=this@entry=0xdaf400, position=...) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/TerminalDisplay.cpp:2295 #12 0x7f811a8f29ea in Konsole::TerminalDisplay::mouseMoveEvent (this=0xdaf400, ev=0x7ffc0a24b3a0) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/TerminalDisplay.cpp:2134 #13 0x7f811802a9c8 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f811a8f975a in Konsole::TerminalDisplay::event (this=0xdaf400, event=0x7ffc0a24b3a0) at /home/paul/rebuild/konsole/src/konsole-15.12.0/src/TerminalDisplay.cpp:3151 #15 0x7f8117fe79ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f8117fed589 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #17 0x7f81176f4bab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #18 0x7f8117fec492 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/libQt5Widgets.so.5 #19 0x7f8118044f3b in ?? () from /usr/lib/libQt5Widgets.so.5 #20 0x7f81180474fb in ?? () from /usr/lib/libQt5Widgets.so.5 #21 0x7f8117fe79ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x7f8117fece86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #23 0x7f81176f4bab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #24 0x7f8117a355f1 in QGuiApplicationPriv
[konsole] [Bug 357180] Segfault after trying to select unreadably small text in konsole 15.12
https://bugs.kde.org/show_bug.cgi?id=357180 --- Comment #1 from Paul Konecny --- Created attachment 96302 --> https://bugs.kde.org/attachment.cgi?id=96302&action=edit Screencast showing the text glitch and segfault -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356820] Open Filename in Kate causes crash
https://bugs.kde.org/show_bug.cgi?id=356820 --- Comment #4 from Sandro Mathys --- Neither changed anything. -- You are receiving this mail because: You are watching all bug changes.
[taglib] [Bug 357181] New: taglib-extras unable to find taglib version > 1.9 because of wrong comparison
https://bugs.kde.org/show_bug.cgi?id=357181 Bug ID: 357181 Summary: taglib-extras unable to find taglib version > 1.9 because of wrong comparison Product: taglib Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: e-...@wthack.de CC: lalin...@gmail.com Hi, could you please apply the following fix to your FindTaglib.cmake file: https://github.com/exi/nixpkgs/commit/5303351c72b725b2138daa87ef4f852dd826bdd2 FindTaglib.cmake uses STRLESS to compare version which should be VERSION_LESS. Would be cool if you could tag a new taglib-extras version with the fix so we can drop our workaround. Reproducible: Always Steps to Reproduce: 1. Try to build with taglib version 1.10 Actual Results: Unable to find taglib version that satisfies taglib > 1.7 although 1.10 is installed Expected Results: Should compile just fine -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 356216] Time selection is truncated
https://bugs.kde.org/show_bug.cgi?id=356216 felix_ma...@web.de changed: What|Removed |Added CC||felix_ma...@web.de --- Comment #3 from felix_ma...@web.de --- same here with korganizer 15.12.0, also on Arch Linux. Is this an Arch Linux specific problem? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357182] New: Plasma crash on user switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=357182 Bug ID: 357182 Summary: Plasma crash on user switch with NVIDIA Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: carls...@workingcode.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.3.3-1-default x86_64 Distribution: "openSUSE Tumbleweed (20151221) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Switching between sessions using C-A-F7, C-A-F8. System is running OpenSuSE Tumbleweed and has NVIDIA driver installed for GTX 950. Works fine most of the time, but when switching sessions, the previous user gets a Plasma crash every time. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), 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 [Current thread is 1 (Thread 0x7fa19f0f2900 (LWP 11817))] Thread 8 (Thread 0x7fa186dd1700 (LWP 11819)): #0 0x7fa1986ab24d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa19d568432 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7fa186dd0bc0) at /usr/include/bits/poll2.h:46 #2 0x7fa19d568432 in _xcb_conn_wait (c=c@entry=0x266b400, cond=cond@entry=0x266b440, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7fa19d56a007 in xcb_wait_for_event (c=0x266b400) at xcb_in.c:693 #4 0x7fa189551e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #5 0x7fa198d9c94f in () at /usr/lib64/libQt5Core.so.5 #6 0x7fa197eb24a4 in start_thread (arg=0x7fa186dd1700) at pthread_create.c:334 #7 0x7fa1986b3bdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fa17fbe2700 (LWP 11821)): #0 0x7fa1986ab24d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa194da2264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa194da236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa198fc152b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa198f6b63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa198d97b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa19c0439a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fa198d9c94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa197eb24a4 in start_thread (arg=0x7fa17fbe2700) at pthread_create.c:334 #9 0x7fa1986b3bdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fa173cf8700 (LWP 11828)): #0 0x7fa1986ab24d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa194da2264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa194da236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa198fc152b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa198f6b63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa198d97b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa19c0439a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fa198d9c94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa197eb24a4 in start_thread (arg=0x7fa173cf8700) at pthread_create.c:334 #9 0x7fa1986b3bdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fa172314700 (LWP 11831)): #0 0x7fa1986ab24d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa194da2264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa194da236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa198fc152b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa198f6b63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa198d97b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa19c0439a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fa198d9c94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa197eb24a4 in start_thread (arg=0x7fa172314700) at pthread_create.c:334 #9 0x7fa1986b3bdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fa1709d9700 (LWP 11832)): #0 0x7fa197eb807f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa19e7d7a84 in () at /usr/lib64/libQt5Script.so.5 #2 0x7fa19e7d7ac9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fa197eb24a4 in start_thread (arg=0x7fa1709d9700) at pthread_create.c:334 #4 0x7fa1986b3bdd in clone () at ../sysdeps/unix/sysv/l
[plasmashell] [Bug 357183] New: Plasma crash while switching windows
https://bugs.kde.org/show_bug.cgi?id=357183 Bug ID: 357183 Summary: Plasma crash while switching windows Product: plasmashell Version: 5.4.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: davidsbo...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.4.2 Operating System: Linux 4.2.0-22-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Switching to another window from Chrome. Not sure if using alt-tab or another method such as the taskbar or just minimizing the Chrome window. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f68eb7c2800 (LWP 2453))] Thread 20 (Thread 0x7f68d5320700 (LWP 2454)): #0 0x7f68e5f8e8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f68e9fd5bd2 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f68e9fd774f in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f68d7efea39 in QXcbEventReader::run() (this=0x9ade40) at qxcbconnection.cpp:1105 #4 0x7f68e66812be in QThreadPrivate::start(void*) (arg=0x9ade40) at thread/qthread_unix.cpp:337 #5 0x7f68e57706aa in start_thread (arg=0x7f68d5320700) at pthread_create.c:333 #6 0x7f68e5f99eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7f68c8572700 (LWP 2520)): #0 0x7f68e5f8e8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f68e2d3c1ec in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f68c0003270, timeout=, context=0x7f68c9b0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:4135 #2 0x7f68e2d3c1ec in g_main_context_iterate (context=context@entry=0x7f68c9b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3835 #3 0x7f68e2d3c2fc in g_main_context_iteration (context=0x7f68c9b0, may_block=may_block@entry=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #4 0x7f68e68b829b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f68c8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f68e685e75a in QEventLoop::exec(QFlags) (this=this@entry=0x7f68c8571da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f68e667c3d4 in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7f68e8ea4f85 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f68e66812be in QThreadPrivate::start(void*) (arg=0xc5b900) at thread/qthread_unix.cpp:337 #9 0x7f68e57706aa in start_thread (arg=0x7f68c8572700) at pthread_create.c:333 #10 0x7f68e5f99eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f68bd14d700 (LWP 2552)): #0 0x7f68e2d3bbc3 in g_main_context_check (context=context@entry=0x7f68b8000990, max_priority=2147483647, fds=fds@entry=0x7f68b8003270, n_fds=n_fds@entry=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3751 #1 0x7f68e2d3c190 in g_main_context_iterate (context=context@entry=0x7f68b8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3837 #2 0x7f68e2d3c2fc in g_main_context_iteration (context=0x7f68b8000990, may_block=may_block@entry=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #3 0x7f68e68b829b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f68b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f68e685e75a in QEventLoop::exec(QFlags) (this=this@entry=0x7f68bd14cda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f68e667c3d4 in QThread::exec() (this=) at thread/qthread.cpp:503 #6 0x7f68e8ea4f85 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f68e66812be in QThreadPrivate::start(void*) (arg=0xa13500) at thread/qthread_unix.cpp:337 #8 0x7f68e57706aa in start_thread (arg=0x7f68bd14d700) at pthread_create.c:333 #9 0x7f68e5f99eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f68b677c700 (LWP 2560)): #0 0x7f68e2d3b710 in g_main_context_prepare (context=context@entry=0x7f68a8000990, priority=priority@entry=0x7f68b677bc70) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3420 #1 0x7f68e2d3c11b in g_main_context_iterate (context=context@entry=0x7f68a8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3820 #2 0x7f68e2d3c2fc in g_main_context_iteration (context=0x7f68a8000990, may_block=may_bloc
[kontact] [Bug 357184] New: kontact crashed switching from kmail to korganizer
https://bugs.kde.org/show_bug.cgi?id=357184 Bug ID: 357184 Summary: kontact crashed switching from kmail to korganizer Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: yehi...@mail.ru Application: kontact (4.14.10) KDE Platform Version: 4.14.14 Qt Version: 4.8.6 Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: - What I was doing when the application crashed: I have raised the kontact window and clicked on the korganizer icon to switch from kmail to korganizer. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbaffd18900 (LWP 2573))] Thread 4 (Thread 0x7fbab42df700 (LWP 2593)): #0 0x003cbc80c540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x0034b4f8af61 in JSC::BlockAllocator::blockFreeingThreadMain() () at /lib64/libQtWebKit.so.4 #2 0x0034b52896d6 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQtWebKit.so.4 #3 0x7fbb023ee754 in () at /lib64/libGL.so.1 #4 0x003cbc807555 in start_thread () at /lib64/libpthread.so.0 #5 0x003cbbd02b9d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fbaa8440700 (LWP 3478)): #0 0x003cbc80f29d in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x003cbc809906 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7fbb023e89f2 in () at /lib64/libGL.so.1 #3 0x7fbb023ed290 in () at /lib64/libGL.so.1 #4 0x7fbb023ed766 in () at /lib64/libGL.so.1 #5 0x7fbb0212bbf7 in () at /lib64/tls/libnvidia-tls.so.304.128 #6 0x003cbdc8db00 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #7 0x003cbdc498b4 in g_main_context_check () at /lib64/libglib-2.0.so.0 #8 0x003cbdc49d60 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #9 0x003cbdc49ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #10 0x0034a0fba4ee in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #11 0x0034a0f88791 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #12 0x0034a0f88b05 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #13 0x0034a0e78289 in QThread::exec() () at /lib64/libQtCore.so.4 #14 0x0034a0e7aaac in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #15 0x7fbb023ee754 in () at /lib64/libGL.so.1 #16 0x003cbc807555 in start_thread () at /lib64/libpthread.so.0 #17 0x003cbbd02b9d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fbaa4eb0700 (LWP 3786)): #0 0x003cbbcf2fad in read () at /lib64/libc.so.6 #1 0x7fbb023ed73c in () at /lib64/libGL.so.1 #2 0x7fbb0212bbf7 in () at /lib64/tls/libnvidia-tls.so.304.128 #3 0x003cbdc8db00 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #4 0x003cbdc498b4 in g_main_context_check () at /lib64/libglib-2.0.so.0 #5 0x003cbdc49d60 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #6 0x003cbdc49ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #7 0x0034a0fba4ee in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #8 0x0034a0f88791 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #9 0x0034a0f88b05 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #10 0x0034a0e78289 in QThread::exec() () at /lib64/libQtCore.so.4 #11 0x0034a0f68863 in QInotifyFileSystemWatcherEngine::run() () at /lib64/libQtCore.so.4 #12 0x0034a0e7aaac in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #13 0x7fbb023ee754 in () at /lib64/libGL.so.1 #14 0x003cbc807555 in start_thread () at /lib64/libpthread.so.0 #15 0x003cbbd02b9d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fbaffd18900 (LWP 2573)): [KCrash Handler] #6 0x0034a3c3e29e in KSelectionProxyModelPrivate::mapTopLevelToSource(int, int) const () at /lib64/libkdeui.so.5 #7 0x0034a3c3e531 in KSelectionProxyModel::mapToSource(QModelIndex const&) const () at /lib64/libkdeui.so.5 #8 0x0034a3c399c3 in KSelectionProxyModel::data(QModelIndex const&, int) const () at /lib64/libkdeui.so.5 #9 0x0034b9e3ec5f in Akonadi::CalFilterProxyModel::filterAcceptsRow(int, QModelIndex const&) const () at /lib64/libakonadi-calendar.so.4 #10 0x0034a27842c7 in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int, int, Qt::Orientation) () at /lib64/libQtGui.so.4 #11 0x0034a278457f in QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) () at /lib64/libQtGui.so.4 #12 0x0034a0f9e0c0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void*
[systemsettings] [Bug 356988] System-Config crashed sometime by speedy mouse click in module workspace effects
https://bugs.kde.org/show_bug.cgi?id=356988 --- Comment #2 from Artur Puzio --- Also the backtrace is from version without debugging symbols, so it's not useful for developers. Please install debugging symbols for systemsettings and post the version obtained after installing them. You can learn how to do it here: https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356876] Online Accounts crashing on "configure"
https://bugs.kde.org/show_bug.cgi?id=356876 --- Comment #2 from Artur Puzio --- Also the backtrace is from version without debugging symbols, so it's not useful for developers. When you will want to post another bug please install debugging symbols for the problematic app and post the version obtained after installing them. You can learn how to do it here: https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 357162] Hardcoded reference to inexistent URL
https://bugs.kde.org/show_bug.cgi?id=357162 Michael Pyne changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||16.01 Latest Commit||http://commits.kde.org/kdes ||rc-build/c7d70b8659a319752a ||a5e556edbc981a3afc120e --- Comment #1 from Michael Pyne --- Git commit c7d70b8659a319752aa5e556edbc981a3afc120e by Michael Pyne. Committed on 26/12/2015 at 19:20. Pushed by mpyne into branch 'master'. Update doc URLs to reflect move of documentation to docs.kde.org The docs have been at docs.kde.org for a long time, now they're the one and only recommended location. But I forgot to update the URLs referenced by the script itself. :( FIXED-IN:16.01 M +2-2README M +1-1doc/man-kdesrc-build-setup.1.docbook M +1-1doc/man-kdesrc-build.1.docbook M +1-1kdesrc-buildrc-kf5-sample M +1-1kdesrc-buildrc-sample M +3-3modules/ksb/Application.pm http://commits.kde.org/kdesrc-build/c7d70b8659a319752aa5e556edbc981a3afc120e -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 334652] Changes not pushed to Google Calendar
https://bugs.kde.org/show_bug.cgi?id=334652 --- Comment #2 from Russell Greene --- Works fine for me, did you choose the right calendar when creating the event? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 334652] Changes not pushed to Google Calendar
https://bugs.kde.org/show_bug.cgi?id=334652 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #1 from Russell Greene --- Works fine for me, did you choose the right calendar when creating the event? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 356337] Error
https://bugs.kde.org/show_bug.cgi?id=356337 --- Comment #2 from Artur Puzio --- Also please change the title to something more meaningful like: "widget-clock crashes after changing time manually" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 357185] New: open header plugin not working
https://bugs.kde.org/show_bug.cgi?id=357185 Bug ID: 357185 Summary: open header plugin not working Product: kate Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: erben...@comcast.net OpenSuse 13.1 x86_64 KDE 4.11.5 Kate 3.11.5 The "open header" plugin is checked and enabled but if i right click on "#include " for example, there is no option to load that file, also i dont see anything on the menus. Reproducible: Always Steps to Reproduce: 1. in Settings, Configure Kate, Plugins, enable "Open Header" plugin 2. Load a .C program and 3. Right click on one of the #include <> files. e.g #include Actual Results: There is no available option to load the file on the right click menu There is no main menu option either (that i could find) Expected Results: option on right click menu to open the include file under the cursor -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 357186] New: “ fatal error: phonon/backendcapabilities.h: No such file or directory” when building kdepim
https://bugs.kde.org/show_bug.cgi?id=357186 Bug ID: 357186 Summary: “ fatal error: phonon/backendcapabilities.h: No such file or directory” when building kdepim Product: kalarm Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: djar...@kde.org Reporter: shlo...@shlomifish.org When I build kdepim (from source) on Mageia x86-64 v6/Cauldron I am getting this compilation error: [ 62%] Building CXX object kalarm/CMakeFiles/kalarm_bin.dir/soundpicker.cpp.o /home/shlomif/Download/unpack/kde/To-del/kdepim-15.12.0/kalarm/soundpicker.cpp:36:40: fatal error: phonon/backendcapabilities.h: No such file or directory compilation terminated. Reproducible: Always Steps to Reproduce: 1. unpack the kdepim-15.12.0 distribution on Mageia v6 x86-64 Cauldron. 2. Install the dependencies (one can use urpmi --buildrequires for that). 3. mkdir build 4. cd build 5. cmake .. 6. cd kalarm 7. make -j4 Actual Results: Got a build error. Expected Results: Build should be successful. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 357187] New: The "Find" functionality needs to be able to search more than the current visible page
https://bugs.kde.org/show_bug.cgi?id=357187 Bug ID: 357187 Summary: The "Find" functionality needs to be able to search more than the current visible page Product: khelpcenter Version: 4.11.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: erben...@comcast.net currently the "Find" function only searches whatever page is visible in the help center window.There needs to be an additional find button/menu item that can: 1. search all of the help topic selected 2. search all of help (entirely) also, and this is unrelated to "Find" specificly, but the various kate plugins are VERY poorly documented. for example in the help we find this: Project Plugin - Project plugin for kate Thats it!? Help should document how to use it, what menu its on and more (the more the better) I find this kind of thing to be rue for a lot of topics in help center. Reminds me of Borland, the company nearly died due to bad help documentation, dont let this happen to KDE - PLEASE! Reproducible: Always Steps to Reproduce: 1. Open Help 2. Select a topic e.g office (any topic in contents) on left sidebar 3. click the Find button Actual Results: searches ONLY the visible page. Expected Results: should search the entire topic -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 332921] Can't expand Meta Information or hide Semantic Info
https://bugs.kde.org/show_bug.cgi?id=332921 Frank Steinmetzger changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #12 from Frank Steinmetzger --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 357188] New: Tap-and-Drag Gesture should be disabled when One finger Mouse Click Emulation is set to "No action"
https://bugs.kde.org/show_bug.cgi?id=357188 Bug ID: 357188 Summary: Tap-and-Drag Gesture should be disabled when One finger Mouse Click Emulation is set to "No action" Product: Touchpad-KCM Version: 5.5.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: rajeeshknamb...@gmail.com Reporter: kdeb...@toeai.com The Tap-and-Drag Gesture does not function if you have Mouse Click Emulation for One finger set to "No action". As such, it should be disabled / grayed-out when this is selected. Observed on Kubuntu 14.04 (KDE 4) and Manjaro 15.12 (KDE 5.5.1). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 334652] Changes not pushed to Google Calendar
https://bugs.kde.org/show_bug.cgi?id=334652 --- Comment #3 from Russell Greene --- As this bug is very old, and non-reproducable, I would suggest that it be closed. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 134145] Kontact's components are not very consistent and intuitive
https://bugs.kde.org/show_bug.cgi?id=134145 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #2 from Russell Greene --- This is not a bug, but a feature request, and one that probably has been addressed. I suggest that if you still feel this way you should reopen this as a wishlist item. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357189] New: Plasmashell stürzt mit Segmentation Fault 11 beim Systemstart ab
https://bugs.kde.org/show_bug.cgi?id=357189 Bug ID: 357189 Summary: Plasmashell stürzt mit Segmentation Fault 11 beim Systemstart ab Product: plasmashell Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manfredkel...@freenet.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.2) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: First I made a System upgrade via DVD from openSUSE 13.2 x64 to openSUSE LEAP 42.1 x 64. The upgrade was done without any problems and I tryed, after the last reboot do modify the mini programs. Suddenly plasmashell crashs. Online search with google dosn't give matching results. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d83fb47c0 (LWP 12326))] Thread 17 (Thread 0x7f2d6d82d700 (LWP 12327)): #0 0x7f2d7d462c1d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2d823f9422 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f2d6d82cd00) at /usr/include/bits/poll2.h:46 #2 0x7f2d823f9422 in _xcb_conn_wait (c=c@entry=0x7c8020, cond=cond@entry=0x7c8060, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7f2d823fb00f in xcb_wait_for_event (c=0x7c8020) at xcb_in.c:693 #4 0x7f2d6f9a5c29 in QXcbEventReader::run() (this=0x7d65b0) at qxcbconnection.cpp:1214 #5 0x7f2d7db6055f in QThreadPrivate::start(void*) (arg=0x7d65b0) at thread/qthread_unix.cpp:331 #6 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d6d82d700) at pthread_create.c:309 #7 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 16 (Thread 0x7f2d66b35700 (LWP 12329)): #0 0x7f2d7d462c1d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2d79ad9e64 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f2d60003070, timeout=-1, context=0x7f2d6990) at gmain.c:4103 #2 0x7f2d79ad9e64 in g_main_context_iterate (context=context@entry=0x7f2d6990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3803 #3 0x7f2d79ad9f7c in g_main_context_iteration (context=0x7f2d6990, may_block=1) at gmain.c:3869 #4 0x7f2d7dd91a5b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f2d68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f2d7dd38a63 in QEventLoop::exec(QFlags) (this=this@entry=0x7f2d66b34df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f2d7db5b84a in QThread::exec() (this=this@entry=0x8b83c0) at thread/qthread.cpp:503 #7 0x7f2d80e9e5f8 in QQmlThreadPrivate::run() (this=0x8b83c0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7f2d7db6055f in QThreadPrivate::start(void*) (arg=0x8b83c0) at thread/qthread_unix.cpp:331 #9 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d66b35700) at pthread_create.c:309 #10 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 15 (Thread 0x7f2d58f25700 (LWP 12330)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2d5f9d1023 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2d5f9d0b97 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d58f25700) at pthread_create.c:309 #4 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 14 (Thread 0x7f2d58724700 (LWP 12331)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2d5f9d1023 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2d5f9d0b97 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d58724700) at pthread_create.c:309 #4 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 13 (Thread 0x7f2d57f23700 (LWP 12332)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2d5f9d1023 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2d5f9d0b97 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d57f23700) at pthread_create.c:309 #4 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 12 (Thread 0x7f2d57722700 (LWP 12333)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/
[plasmashell] [Bug 357189] Plasmashell stürzt mit Segmentation Fault 11 beim Systemstart ab
https://bugs.kde.org/show_bug.cgi?id=357189 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Looks like the Web browser widget is crashing, at least it's crashing in QtWebkit -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 355439] kontact crashed after updating an event
https://bugs.kde.org/show_bug.cgi?id=355439 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #1 from Russell Greene --- Could you tell us what you were doing when this crash occurred (if you remember)? That would make it possible to try to reproduce the bug. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration
https://bugs.kde.org/show_bug.cgi?id=354437 --- Comment #7 from Maciej Mrozowski --- Then KDE4 kscreen must have had some own randr polling mechanism, because there, it detects my dock-station/monitor hot-plug events immediately. It's just with KDE5 kscreen I have those output detection problems: https://bugs.kde.org/show_bug.cgi?id=340120 https://bugs.kde.org/show_bug.cgi?id=356505 https://bugs.kde.org/show_bug.cgi?id=351025 https://bugs.kde.org/show_bug.cgi?id=346535 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 354292] Crash Reporting Assistant login button is always disabled
https://bugs.kde.org/show_bug.cgi?id=354292 sederic changed: What|Removed |Added CC||sebastian.end...@online.de --- Comment #3 from sederic --- The same here on fedora 23. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 355279] Kontact crashes on App Start
https://bugs.kde.org/show_bug.cgi?id=355279 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #1 from Russell Greene --- Do you remember what you were doing two days ago when it stopped working? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357190] New: random plasma crash
https://bugs.kde.org/show_bug.cgi?id=357190 Bug ID: 357190 Summary: random plasma crash Product: plasmashell Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: p...@free.fr CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-19-lowlatency x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I was doing nothing special - Unusual behavior I noticed: I guess the time was changing end a redraw was occuring on the clock applet (digital version) -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f848101a800 (LWP 15684))] Thread 17 (Thread 0x7f846c682700 (LWP 15686)): #0 0x7f847b7d68dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f847f81dbd2 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f847f81f74f in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f846e9cca39 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #4 0x7f847bec92be in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f847afb86aa in start_thread (arg=0x7f846c682700) at pthread_create.c:333 #6 0x7f847b7e1eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f8469fdc700 (LWP 15690)): #0 0x7f847c1002a1 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f847c0a675a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f847bec43d4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f847e6ecf85 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7f847bec92be in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f847afb86aa in start_thread (arg=0x7f8469fdc700) at pthread_create.c:333 #6 0x7f847b7e1eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f845a907700 (LWP 15691)): #0 0x7f847b7d68dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f84785831ec in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f8454002e70, timeout=, context=0x7f8454000990) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:4135 #2 0x7f84785831ec in g_main_context_iterate (context=context@entry=0x7f8454000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3835 #3 0x7f84785832fc in g_main_context_iteration (context=0x7f8454000990, may_block=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #4 0x7f847c10029b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f847c0a675a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f847bec43d4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f847e6ecf85 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f847bec92be in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f847afb86aa in start_thread (arg=0x7f845a907700) at pthread_create.c:333 #10 0x7f847b7e1eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f8453fff700 (LWP 15695)): #0 0x7f847b7d68dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f84785831ec in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f8448003070, timeout=, context=0x7f8448000990) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:4135 #2 0x7f84785831ec in g_main_context_iterate (context=context@entry=0x7f8448000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3835 #3 0x7f84785832fc in g_main_context_iteration (context=0x7f8448000990, may_block=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #4 0x7f847c10029b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f847c0a675a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f847bec43d4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f847e6ecf85 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f847bec92be in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f847afb86aa in start_thread (arg=0x7f8453fff700) at pthread_create.c:333 #10 0x7f847b7e1eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f84527bb700 (LWP 1
[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration
https://bugs.kde.org/show_bug.cgi?id=354437 --- Comment #8 from Maciej Mrozowski --- But that's of course not relevant in this bug. I can also confirm behaviour reported here - not restoring latest monitor configuration. (in previous comments just wanted say that imho root cause is with not working autodetection, like in the case of bugs where user cannot change monitor resolution occasionally because kscreen has outdated/mismatching EDID information on monitor (like list of supported resolutions), I suspect this might be the case with automatically trying to apply previous config as well) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356848] New themed icons for configure Kdenlive dialog section "Project Defaults"
https://bugs.kde.org/show_bug.cgi?id=356848 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kden ||live/87e410db946b3077c14bde ||738b28d571bcacab4c --- Comment #3 from Jean-Baptiste Mardelle --- Git commit 87e410db946b3077c14bde738b28d571bcacab4c by Jean-Baptiste Mardelle. Committed on 26/12/2015 at 20:53. Pushed by mardelle into branch 'Applications/15.12'. Icon for project settings in config dialog M +2-0data/pics/CMakeLists.txt M +1-1src/dialogs/kdenlivesettingsdialog.cpp http://commits.kde.org/kdenlive/87e410db946b3077c14bde738b28d571bcacab4c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357032] KWin crashes after RubyMine sync window close
https://bugs.kde.org/show_bug.cgi?id=357032 --- Comment #4 from Mykola Krachkovsky --- Created attachment 96303 --> https://bugs.kde.org/attachment.cgi?id=96303&action=edit KWin support info There is KWin support information. It looks like KWin doesn't met asserts, just line number changed on 2: Thread 1 (Thread 0x77f83840 (LWP 8891)): #0 0x774d109d in KWin::Scene::Window::buildQuads(bool) const (this=0x6e4140, force=) at /usr/src/debug/kwin-5.5.90git~20151218T172621~ecce036/scene.cpp:832 #1 0x774cfaee in KWin::Scene::paintSimpleScreen(int, QRegion) (this=this@entry=0x856520, orig_mask=orig_mask@entry=0, region=...) at /usr/src/debug/kwin-5.5.90git~20151218T172621~ecce036/scene.cpp:302 Should I add full stack trace? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356832] Plasma crashed when I try to use settings for Activities
https://bugs.kde.org/show_bug.cgi?id=356832 Ivan Čukić changed: What|Removed |Added Latest Commit||http://commits.kde.org/kact ||ivities/eeb2e500d6b75b818b0 ||d9570d517323f93598f65 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Ivan Čukić --- Git commit eeb2e500d6b75b818b0d9570d517323f93598f65 by Ivan Čukić. Committed on 26/12/2015 at 21:06. Pushed by ivan into branch 'master'. Streamlined the QML loading for KCM - QML path mangling no uses the same variable as CMakeLists - If the setup is broken, the user will get a nice message - Fixed crash on non-existent root object M +2-3src/workspace/settings/ActivitiesTab.cpp M +11 -1src/workspace/settings/CMakeLists.txt M +4-3src/workspace/settings/PrivacyTab.cpp M +3-1src/workspace/settings/imports/CMakeLists.txt M +37 -10 src/workspace/settings/imports/dialog.cpp A +6-0src/workspace/settings/kactivities-kcm-features.h.cmake M +16 -0src/workspace/settings/utils.h http://commits.kde.org/kactivities/eeb2e500d6b75b818b0d9570d517323f93598f65 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356832] Plasma crashed when I try to use settings for Activities
https://bugs.kde.org/show_bug.cgi?id=356832 --- Comment #3 from Ivan Čukić --- If David was right, the commit above should fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 313825] Kontact crashes when replying to an email
https://bugs.kde.org/show_bug.cgi?id=313825 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #2 from Russell Greene --- Could you try upgrading to kontact 5.0.2 and see if the problem still exists? Also, has this always happened or is this recent? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777
Xuân Baldauf changed:
What|Removed |Added
CC||development--2015--bugs.kde
||.o...@medium.net
--- Comment #20 from Xuân Baldauf
---
I'm experiencing the same issue.
The bug is that in this code
https://quickgit.kde.org/?p=plasma-workspace.git&a=blob&h=17ce61b57f71332b9b4029d44301462ef90d3dfd&hb=1f826604749f36e899034d55d02a910e31584f60&f=shell%2Fshellcorona.cpp
>DesktopView *view = new DesktopView(this, newScreen);
>
>Plasma::Containment *containment =
> (m_activityController->currentActivity(), m_views.count());
>Q_ASSERT(containment);
>
>QAction *removeAction =
> containment->actions()->action(QStringLiteral("remove"));
"m_views" is empty, and thus "m_views.count()" is zero. Hence "containment" is
NULL, so dereferencing this pointer triggers the crash.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 357032] KWin crashes after RubyMine sync window close
https://bugs.kde.org/show_bug.cgi?id=357032
--- Comment #5 from Thomas Lübking ---
Updated backtrace won't be necessary.
Do you get the crashes when disabling unredirection of fullscreen windows?
("kcmshell5 kwincompositing", "suspend compositing for fullscreen windows")
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 354638] Autohide does not work when similar windows are grouped together
https://bugs.kde.org/show_bug.cgi?id=354638 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #1 from Russell Greene --- Created attachment 96304 --> https://bugs.kde.org/attachment.cgi?id=96304&action=edit Show correct behaviour -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354638] Autohide does not work when similar windows are grouped together
https://bugs.kde.org/show_bug.cgi?id=354638 --- Comment #2 from Russell Greene --- Is that what you want? Works fine here. I'm also on 5.4.2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357032] KWin crashes after RubyMine sync window close
https://bugs.kde.org/show_bug.cgi?id=357032 --- Comment #6 from Mykola Krachkovsky --- Tried to switch it off, still crashes. Btw, windows aren't fullscreen, just maximized. Noticed, not only RubyMine is affected, NetBeans too. And I've got crash only when window was initially maximized (coincedense?) and window is closing immediatly, if app doing something and close after a while, kwin won't crash (also not sure, but it looks like that). Not java (swing?) windows aren't affected (at least all crashes I had was with RubyMine and NetBeans). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356827] KWrite crashes when clicking "save as" on a blank file
https://bugs.kde.org/show_bug.cgi?id=356827 Maxim Therrien changed: What|Removed |Added CC||acersp...@gmail.com --- Comment #5 from Maxim Therrien --- Created attachment 96305 --> https://bugs.kde.org/attachment.cgi?id=96305&action=edit Backtrace DrKonqi didn't want to attach this report to the thread for some reason. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354527] The panel doesn't retain it's size when it's being moved
https://bugs.kde.org/show_bug.cgi?id=354527 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #2 from Russell Greene --- I can reproduce this with the same steps. I am also running plasmashell 5.4.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355341] Plasma 5 keeps crashing on my Kubuntu 15.04
https://bugs.kde.org/show_bug.cgi?id=355341 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #1 from Russell Greene --- When you start in, start a console and enter this: killall plasmashell kstart plasmashell Tell me the results. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354704] Plasma crash while installing Icon theme
https://bugs.kde.org/show_bug.cgi?id=354704 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #4 from Russell Greene --- I cannot reproduce this but, it works flawlessly. Icon theme installed, no crash. plasmashell version 5.4.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354643] kdeinit5 crashed when rebooting
https://bugs.kde.org/show_bug.cgi?id=354643 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #1 from Russell Greene --- Because there is no known way to reproduce this error, there is no way to fix this bug. Suggesting it be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354102] Show Desktop, then choose Leave from Plasma menu shows => Windows overlapping
https://bugs.kde.org/show_bug.cgi?id=354102 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #3 from Russell Greene --- Created attachment 96307 --> https://bugs.kde.org/attachment.cgi?id=96307&action=edit Correct behavior -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354102] Show Desktop, then choose Leave from Plasma menu shows => Windows overlapping
https://bugs.kde.org/show_bug.cgi?id=354102 --- Comment #4 from Russell Greene --- Works fine for me. The windows just stay away. plasmashell version 5.4.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357032] KWin crashes after RubyMine sync window close
https://bugs.kde.org/show_bug.cgi?id=357032 --- Comment #7 from Thomas Lübking --- => Tried to disable the maximize effect? (I wasn't even aware about the maximization relation, just thought the unredirection might have caused a dangeling EffectWindow pointer there somewhen, hitting on later occasions) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355397] task manager widget removed from taskbar
https://bugs.kde.org/show_bug.cgi?id=355397 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #3 from Russell Greene --- Has this happened before? If not, do you remember if you updated anything or anything of that nature before it stopped working? Thank you for the persistence. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357191] New: Incorrect panel edges displayed when more than one panel exists
https://bugs.kde.org/show_bug.cgi?id=357191 Bug ID: 357191 Summary: Incorrect panel edges displayed when more than one panel exists Product: plasmashell Version: 5.5.0 Platform: openSUSE RPMs URL: http://i.imgur.com/y3OcpKW.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: obno...@gmail.com Edges of an already created panel are wrongly replaced to match the edges of a newly created panel. Having more than one panel always causes visual inconsistencies. My current panel setup consists of a maximized bottom panel and an unmaximized panel on the right side of the screen. If I first create the maximized bottom panel, it is displayed perfectly. The moment I add a second panel, the edges of the preexisting bottom panel change to match that of the new panel. This means the bottom panel has visible left and top-left corners even though it is maximized and, as such, should only have a top edge. Removing the left-panel fixes it immediately. Similarly, putting the second panel on the left side of the screen causes right and top-right borders to appear on the bottom panel, and putting in on the top hides all borders on the bottom panel, including the top border. If I instead create the maximized bottom panel second, the first panel ends up having only a top-border. This can easily be visualized by using with the attached panel-background.svg file. Reproducible: Always Steps to Reproduce: 1. Have an existing panel (A) 2. Add a second panel (B) Actual Results: Panel B's edges replace Panel A's Expected Results: Each panel keeps its own edges. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357191] Incorrect panel edges displayed when more than one panel exists
https://bugs.kde.org/show_bug.cgi?id=357191 --- Comment #1 from obno...@gmail.com --- Created attachment 96308 --> https://bugs.kde.org/attachment.cgi?id=96308&action=edit Color-coded SVG for easy visualization of the problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357192] New: Disabling notifications in tray area shows no progress window for file copy
https://bugs.kde.org/show_bug.cgi?id=357192 Bug ID: 357192 Summary: Disabling notifications in tray area shows no progress window for file copy Product: plasmashell Version: 5.4.3 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: mklape...@kde.org Reporter: tipos...@tiscali.it CC: plasma-b...@kde.org I have disabled the notification widget within the tray area. I have done so because of this bug: https://bugreports.qt.io/browse/QTBUG-45959 which causes my CPU to go to 100% while there is a spinner being shown. I don't even have an nvidia card, they are approaching it wrong. But regardless of that, in the old days of KDE 4, disabling the notification applet would mean that rather than getting something as a notification while copying a file, I would get a window displaying the progress. One window per copy/move operation. And notifications would still appear, just in an uglier window. That is what I was hoping would happen when I disabled the notifications. What actually happened is that I had no way of knowing whether the file copy was complete or not. Could you please reimplement this missing feature? Or, if you think that the notifications are necessary, just remove the option to disable the plasmoid. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356904] File transfer windows don't show up
https://bugs.kde.org/show_bug.cgi?id=356904 Kai Uwe Broulik changed: What|Removed |Added CC||tipos...@tiscali.it --- Comment #4 from Kai Uwe Broulik --- *** Bug 357192 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357192] Disabling notifications in tray area shows no progress window for file copy
https://bugs.kde.org/show_bug.cgi?id=357192 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@privat.broulik.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 356904 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 357193] New: KDEConnect does not handle secound batterie in phone
https://bugs.kde.org/show_bug.cgi?id=357193 Bug ID: 357193 Summary: KDEConnect does not handle secound batterie in phone Product: kdeconnect Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: m.w...@web.de My Android phone (an Innos D6000) has two batteries. KDEconnect so far only seems recognise one of them and show it's status in KDE. Would be cool if KDEconnect would be able to handle both. I am not sure if this is a problem of the KDEpart, the Android app or both. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353356] Powerdevil does not respect the critical level configuration
https://bugs.kde.org/show_bug.cgi?id=353356 Salvo "LtWorf" Tomaselli changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #3 from Salvo "LtWorf" Tomaselli --- asd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357192] Disabling notifications in tray area shows no progress window for file copy
https://bugs.kde.org/show_bug.cgi?id=357192 --- Comment #2 from Kai Uwe Broulik --- Also, we have significantly improved this area in the latest KDE frameworks release. See if this fixes the high CPU usage for you. -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 357117] Changed ActivePerl version
https://bugs.kde.org/show_bug.cgi?id=357117 Patrick Spendrin changed: What|Removed |Added CC||ps...@gmx.de Severity|grave |normal --- Comment #1 from Patrick Spendrin --- Which branch are you working on? Please keep in mind that all non-master branches are basically not maintained... -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352331] Two audio icons after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=352331 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Rex Dieter --- kmix-15.08.3 (and newer) includes kconf scripts to disable itself, so should be resolved now -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352331] Two audio icons after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=352331 --- Comment #5 from Rex Dieter --- Sorry, make that plasma-pa includes the kconf_update script -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 357134] Ark is unable to open RAR archives after update to 15.12
https://bugs.kde.org/show_bug.cgi?id=357134 --- Comment #2 from Ongun Kanat --- I've updated the package to version 15.12.0-2 however I cannot open the file here: https://goo.gl/LDoaJ7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357032] KWin crashes after RubyMine sync window close
https://bugs.kde.org/show_bug.cgi?id=357032 --- Comment #8 from Mykola Krachkovsky --- Disabled maximize effect — still crashes. Same for fade, blur, contrast, wobbly windows. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 345909] digiKam crashedwhen taging multimple pohotos
https://bugs.kde.org/show_bug.cgi?id=345909 Rebecca changed: What|Removed |Added CC||r.j.you...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 345909] digiKam crashedwhen taging multimple pohotos
https://bugs.kde.org/show_bug.cgi?id=345909 --- Comment #2 from Rebecca --- Created attachment 96309 --> https://bugs.kde.org/attachment.cgi?id=96309&action=edit New crash information added by DrKonqi digikam (4.7.0) on KDE Platform 4.14.6 using Qt 4.8.6 I was tagging faces. I had already succeeded in running scan to find faces and tagged some faces. -- Backtrace (Reduced): #6 0x7feec8a3126b in QString (other=..., this=0x7ffe6104e720) at /usr/include/qt4/QtCore/qstring.h:725 #7 Digikam::DigikamKCategorizedView::Private::visualRectInViewport (this=this@entry=0x2552a30, index=...) at /build/buildd/digikam-4.7.0/core/libs/widgets/itemview/digikamkcategorizedview.cpp:144 #8 0x7feec8a31b89 in Digikam::DigikamKCategorizedView::Private::cacheIndex (this=this@entry=0x2552a30, index=...) at /build/buildd/digikam-4.7.0/core/libs/widgets/itemview/digikamkcategorizedview.cpp:375 #9 0x7feec8a31cc1 in Digikam::DigikamKCategorizedView::Private::cachedRectIndex (this=this@entry=0x2552a30, index=...) at /build/buildd/digikam-4.7.0/core/libs/widgets/itemview/digikamkcategorizedview.cpp:402 #10 0x7feec8a31ce6 in Digikam::DigikamKCategorizedView::Private::visualRect (this=0x2552a30, index=...) at /build/buildd/digikam-4.7.0/core/libs/widgets/itemview/digikamkcategorizedview.cpp:424 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357194] New: Chosen keyboard layout doesn't work when plasma-desktop reboots.
https://bugs.kde.org/show_bug.cgi?id=357194 Bug ID: 357194 Summary: Chosen keyboard layout doesn't work when plasma-desktop reboots. Product: systemsettings Version: 5.5.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keyboard_layout Assignee: ary...@gmail.com Reporter: korg...@yandex.com After configuring the keyboard to Portuguese (Brazilian) and removing the English layout, it works nicely. However, after rebooting, the system goes back to the English layout, although System Settings still shows that the Portuguese keyboard is active. You must go into the configuration and change something (anything, it seems) to that the keys start (again) to work with the Portuguese layout. My guess is that this happens with other layouts, too. Reproducible: Always Steps to Reproduce: 1. Go to System Settings -> Hardware -> Input Devices -> Keyboard -> Layouts 2. Enable lyout configuration 3. Add a new keyboard layout (in my case, Portuguese, Brazil, br) 4. Remove the English layout 5. Apply the changes 6. Test the changes in the Hardware tab, inside the test area 7. Go back to All configurations 8. Close system settings 9. Perform a clean exit (shutdown) from the system, using the graphical menu. 10. Turn on the computer again 11. Login into plasma desktop 12. Open any application 13. Try to use any Portuguese from Brazil specific layout key, such as "ç". 14. It was expected to have a "ç" character on screen, but we get ";" (which is the ";" location of standard English keyboards). 15. Go back to system settings and notice that only the Portuguese, Brazil, keyboard layout is selected. 16. go back to the Hardware tab, test area, and observe that the active layout is the English one (although it was removed from the system and the Portuguese, Brazil, one is selected). 17. Change anything or perform the selection again. 18. The correct layout works until the next reboot Actual Results: The English keyboard layout is always active when the system initializes (after a cold boot or a reboot). Expected Results: The selected Portuguese, Brazil, keyboard layout should be active at all times, including after reboots. I've upgraded to Plasma 5 from KDE 4 when Archlinux dropped support for KDE 4. I've tried to manually erase all old KDE configuration files before performing the upgrade, just to be sure nothing would break. My system is up-to-date as of today December, 22, 2015. This is an annoying bug because there are other people on the house the use this system and they are not computer savvy enough to figure out how to change the keyboard layout. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 357193] KDEConnect does not handle secound batterie in phone
https://bugs.kde.org/show_bug.cgi?id=357193 Albert Vaca changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354372] taskbar preview doesnt goes away when mouse is no longer hovering
https://bugs.kde.org/show_bug.cgi?id=354372 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #2 from Russell Greene --- The most useful thing would be a quick 10 second video. Do either of you think you could do that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357189] Plasmashell stürzt mit Segmentation Fault 11 beim Systemstart ab
https://bugs.kde.org/show_bug.cgi?id=357189 Manfred changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Manfred --- Thank you for your contribution. This was the right way. I searched in YAST for libQt5WebKit.so.5 and tried some packages of WebKit delete . That was not easy, because it has a lot of dependencies , but at last I could delete the package webkitpart . After restarting the system there was no crash anymore, so I could remove the Web browser widget. I think this problem is solved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355988] I have to press twice some keyboard combinations
https://bugs.kde.org/show_bug.cgi?id=355988 Russell Greene changed: What|Removed |Added CC||russellgree...@gmail.com --- Comment #1 from Russell Greene --- What apps does this not work in? All applications? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357195] New: Plasma desktop or the KCM for the Display settings loses the chosen resolution and configuration
https://bugs.kde.org/show_bug.cgi?id=357195 Bug ID: 357195 Summary: Plasma desktop or the KCM for the Display settings loses the chosen resolution and configuration Product: systemsettings Version: 5.5.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: korg...@yandex.com After choosing the proper monitor configuration (DVI-0 as primary, HDMI-0 as secondary on the left of the DVI-0 monitor) and the proper resolutions, DVI-0 as 1920x1200 and HDMI-0 as 1920x1080 and saving everything the system sometimes "forgets" every setting. Reproducible: Sometimes Steps to Reproduce: 1. Go to system Settings and Display configuration 2. Drag the HDMI-0 display to the right side of the DVI-0 display 3. Click on DVI-0 and set its native resolution (instead of the 720xSomething that is selected), confirm 4. Click on HDMI-0 and set its native resolution (instead of the 720xSomething that is selected, confirm 5. Set the DVI-0 monitor as the primary 6. Click apply, exit system configuration and perform a clean shutdown of the system using the graphical menu Actual Results: You can see that in the transition from SDDM to Plasma Desktop that the resolution changes. Inside plasma you will notice that the monitor is stretching a very poor resolution to fill all available pixels. Inside System Settings -> Display configuration you'll see that both monitors are piled one on top of the other, the resolutions have fallen back to 720xSomething and the primary monitor reverted to HDMI-0. Expected Results: Whenever the system boots again or a new user session is created plasma desktop will keep all the settings that were specified. I have a two monitor setup. My primary monitor is a 1920x1200 flat screen. My second monitor is a regular FullHD TV that sits to the right side of the primary. I use the HDMI screen once in a while. Most of the time it's either turned off or displaying regular TV. It is very difficult for me to plug and unplug the HDMI cable, because it is hidden behind the fixed desk. Starting another user session is almost a sure way to mess up the Display configuration afterwards (after a reboot). -- You are receiving this mail because: You are watching all bug changes.
