[korganizer] [Bug 358249] Remote ICS file does not populate calendar
https://bugs.kde.org/show_bug.cgi?id=358249 --- Comment #1 from Franco Pellegrini --- Sorry, I'm using Kubuntu 15.10 and the actual KOrganizer version is 15.08.3 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 358249] New: Remote ICS file does not populate calendar
https://bugs.kde.org/show_bug.cgi?id=358249 Bug ID: 358249 Summary: Remote ICS file does not populate calendar Product: korganizer Version: 15.08.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: frap...@gmail.com I have a remote ics file from the Office 365 Calendar. I go to KOrganizer, right click in the calendars list, "Add Calendar" -> "ICal Calendar File". Then, in "Filename" I enter the complete public URL for my calendar. The "Enable file monitoring" is blurred out, so it does recognize it is a remote resource. Click "Ok". None of the events are added to the calendar... I then go to a terminal, wget the same URL, and then go and add the calendar.ics file that was downloaded. All of the expected events are now visible in the calendar view. Reproducible: Always Steps to Reproduce: 1. Add remote ics file Actual Results: No events show up in the calendar view Expected Results: My events to show up in the calendar view It does work with the same ics file if it was previously downloaded -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied
https://bugs.kde.org/show_bug.cgi?id=347602 --- Comment #36 from pfoo --- I had, I'm experiencing the issue, and yes the bug will appear again when new updates are released by ubuntu. I'm fully aware of this. And yes, this is a -temporary or hot if you wish- fix as it makes your systray looks as it should for the time being. I'm just pointing that this hotfix is working on other(s ?) bugreports, and that It may be related (systray not updating icons as it should ?) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355309] Selecting Multimedia Audio and Video Settings with phonon-backend-vlc crashes knotify4 and Amarok
https://bugs.kde.org/show_bug.cgi?id=355309 --- Comment #6 from Myriam Schweingruber --- (In reply to Roman Bysh from comment #5) > If this is resolved where is the patched phonon-backend-vlc package? You need to ask your distribution to provide it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 mrl...@gmail.com changed: What|Removed |Added CC||mrl...@gmail.com --- Comment #12 from mrl...@gmail.com --- I think that this problem is possibly related to breeze desktop theme. Because if using any other desktop theme than breeze (but not breeze based theme), kscreenlocker works normally. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 Michal Hlavinka changed: What|Removed |Added CC||mhlav...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 358225] Amarok does not react when clicking on play
https://bugs.kde.org/show_bug.cgi?id=358225 Myriam Schweingruber changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Myriam Schweingruber --- I presume you do not have the gstreamer codecs for mp3, those are not shipped by default and need to be installed separately. This is not an Amarok bug, as it is totally out of our control. FWIW: your distribution should automatically tell you that you need to install those codecs, please report this to your distribution, there is obviously some packaging error. FWIW2: mp3 codecs are never shipped by default, as those are patent-encumbered. It is up to the user to decide whether they want to use them or not. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 357229] amarok: skips track, jumps to middle of next track, when switching to next song in playlist
https://bugs.kde.org/show_bug.cgi?id=357229 --- Comment #11 from Myriam Schweingruber --- (In reply to Florian Lindner from comment #10) > I have produced another log with using amarok --debug --debug-audio. > > This times it hasn't just skipped the track but jumped at the middle instead > of starting from beginning. Thanks for the output, but it would be nice if you could reduce that to the 50 or so lines when the problem happens (or at least tell me which track is skipped so I can find that) -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied
https://bugs.kde.org/show_bug.cgi?id=347602 --- Comment #35 from Tim Goodwin --- (In reply to pfoo from comment #34) > Could this be related to #352055 plasma-pa plasmoid not shown in systemtray > after startup ? (https://bugs.kde.org/show_bug.cgi?id=352055) > > Unchecking the Update icon in the System Tray Settings, applying, then > checking it again and applying again make the issue disappears. > The fix is the same for bug #352055 involving plasma-pa at startup This is *not* a fix. It simply makes the issue go away until the next updates appear. Then the issue comes back. I wish people would read the comments before they say that things are 'fixed' when they obviously are not. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied
https://bugs.kde.org/show_bug.cgi?id=347602 --- Comment #34 from pfoo --- Could this be related to #352055 plasma-pa plasmoid not shown in systemtray after startup ? (https://bugs.kde.org/show_bug.cgi?id=352055) Unchecking the Update icon in the System Tray Settings, applying, then checking it again and applying again make the issue disappears. The fix is the same for bug #352055 involving plasma-pa at startup -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358248] New: Absturz bei Rechtschreibprüfung / abort during spell checking
https://bugs.kde.org/show_bug.cgi?id=358248 Bug ID: 358248 Summary: Absturz bei Rechtschreibprüfung / abort during spell checking 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: juergen.voll...@informatik-vollmer.de Application: kmail (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-29-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I pressed "spell checking" This bug is triggered from time to time I use the german lanuage for spell checking The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6f7742f800 (LWP 25676))] Thread 4 (Thread 0x7f6f506e7700 (LWP 25690)): #0 0x7f6f7258d05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6f67c8a686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f6f67c8a6b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f6f725890a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6f7478808d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f6f0f554700 (LWP 25691)): #0 0x7f6f7258d05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6f679fce7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f6f67cb21e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f6f725890a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6f7478808d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f6f0e915700 (LWP 25692)): #0 0x7f6f7477fc5d in poll () at /lib64/libc.so.6 #1 0x7f6f6c4b6be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6f6c4b6cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6f75dda0de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f6f75dabe6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f6f75dac165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f6f75ca90bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f6f75cab79f in () at /usr/lib64/libQtCore.so.4 #8 0x7f6f725890a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f6f7478808d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f6f7742f800 (LWP 25676)): [KCrash Handler] #5 0x7f6f521218f4 in aspeller::AffixMgr::suffix_check(aspeller::LookupInfo const&, acommon::ParmString, acommon::CheckInfo&, aspeller::GuessInfo*, int, aspeller::AffEntry*) const () at /usr/lib64/libaspell.so.15 #6 0x7f6f52121fad in aspeller::AffixMgr::affix_check(aspeller::LookupInfo const&, acommon::ParmString, acommon::CheckInfo&, aspeller::GuessInfo*) const () at /usr/lib64/libaspell.so.15 #7 0x7f6f520fa226 in () at /usr/lib64/libaspell.so.15 #8 0x7f6f520ffe0d in () at /usr/lib64/libaspell.so.15 #9 0x7f6f5210df74 in aspeller::SpellerImpl::suggest(acommon::MutableString) () at /usr/lib64/libaspell.so.15 #10 0x7f6f5213933f in aspell_speller_suggest () at /usr/lib64/libaspell.so.15 #11 0x7f6f52395539 in () at /usr/lib64/enchant/libenchant_aspell.so #12 0x7f6f5259ba1b in enchant_dict_suggest () at /usr/lib64/libenchant.so.1 #13 0x7f6f527dcea2 in () at /usr/lib64/kde4/kspell_enchant.so #14 0x7f6f76946185 in Sonnet::Speller::suggest(QString const&) const () at /usr/lib64/libkdecore.so.5 #15 0x7f6f7694988d in () at /usr/lib64/libkdecore.so.5 #16 0x7f6f76949370 in Sonnet::BackgroundChecker::suggest(QString const&) const () at /usr/lib64/libkdecore.so.5 #17 0x7f6f76f02bce in Sonnet::Dialog::updateDialog(QString const&) () at /usr/lib64/libkdeui.so.5 #18 0x7f6f76f03ac6 in Sonnet::Dialog::slotMisspelling(QString const&, int) () at /usr/lib64/libkdeui.so.5 #19 0x7f6f75dc11fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #20 0x7f6f76949453 in Sonnet::BackgroundChecker::misspelling(QString const&, int) () at /usr/lib64/libkdecore.so.5 #21 0x7f6f75dc11fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #22 0x7f6f769498d3 in () at /usr/lib64/libkdecore.so.5 #23 0x7f6f7694997b in () at /usr/lib64/libkdecore.so.5 #24 0x7f6f75dc559e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #25 0x7f6f7514676c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #26 0x7f6f7514ccad in QApplication:
[krita] [Bug 358247] New: "Tile leaked" critical message when closing Krita
https://bugs.kde.org/show_bug.cgi?id=358247 Bug ID: 358247 Summary: "Tile leaked" critical message when closing Krita Product: krita Version: 2.9.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tile manager Assignee: krita-bugs-n...@kde.org Reporter: samuel.fric...@gmail.com When closing krita, the following message always appears in terminal. exact message: "CRITICAL: According to statistics of the KisTileDataStore some tiles have leaked from the Krita control! CRITICAL: Tiles in memory: 933 Total tiles: 1209" ubuntu 14.04 LTS uname -a: Linux ** 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux lspci: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 4850 512MB GDDR3 Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at d000 (64-bit, prefetchable) [size=256M] Memory at fe8e (64-bit, non-prefetchable) [size=64K] I/O ports at b000 [size=256] Expansion ROM at fe8c [disabled] [size=128K] Capabilities: Kernel driver in use: radeon Reproducible: Always Steps to Reproduce: 1. open a file in Krita (opened via terminal) 2. Manipulate a bit 3. Close Krita and watch terminal Actual Results: The critical message appears in the terminal -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 357833] Valgrind is broken on recent linux kernel
https://bugs.kde.org/show_bug.cgi?id=357833 --- Comment #4 from Mark Wielaard --- Replicated it now with the fedora rawhide kernel 4.5.0-0.rc0.git6.1.fc24.i686+PAE Not setting the RLIMIT_DATA to zero in coregrind/m_main.c (valgrind_main) does indeed work around it. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358200] tiny size on panel with KF 5.18
https://bugs.kde.org/show_bug.cgi?id=358200 Antonio Rojas changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #4 from Antonio Rojas --- 11937533e83659dc4dab6f7e8e6019863a28ddae doesn't fix this one -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358246] New: Plasma crash -konqueror, writer and kmail loaded and being used
https://bugs.kde.org/show_bug.cgi?id=358246 Bug ID: 358246 Summary: Plasma crash -konqueror, writer and kmail loaded and being used Product: plasmashell Version: 5.5.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ianse...@yahoo.co.uk CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20151124) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: -konqueror - opening and closing tabs, - writer -editting document - kmail - chec king mail -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f965f1ec8c0 (LWP 7159))] Thread 9 (Thread 0x7f9645b25700 (LWP 7167)): #0 0x7f965876524d in poll () from /lib64/libc.so.6 #1 0x7f9654e59264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9654e5936c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f965907b52b in QEventDispatcherGlib::processEvents (this=0x7f96380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f965902563a in QEventLoop::exec (this=this@entry=0x7f9645b24cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f9658e51b1c in QThread::exec (this=this@entry=0xd2a7a0) at thread/qthread.cpp:503 #6 0x7f965c1219a5 in QQmlThreadPrivate::run (this=0xd2a7a0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7f9658e5694f in QThreadPrivate::start (arg=0xd2a7a0) at thread/qthread_unix.cpp:331 #8 0x7f9657f6c4a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f965876dbdd in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f9633e52700 (LWP 7184)): #0 0x7f9657f7207f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f963e9fe0b3 in cnd_wait (mtx=0xff6e20, cond=0xff6e48) at ../../../../include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0xff6e20) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 thread_function (init_data=init_data@entry=0xff6d78) at lp_rast.c:805 #4 0x7f963e9fdf37 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7f9657f6c4a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f965876dbdd in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f9633651700 (LWP 7185)): #0 0x7f9657f7207f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f963e9fe0b3 in cnd_wait (mtx=0xff6f88, cond=0xff6fb0) at ../../../../include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0xff6f88) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 thread_function (init_data=init_data@entry=0xff6ee0) at lp_rast.c:805 #4 0x7f963e9fdf37 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7f9657f6c4a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f965876dbdd in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f962d7e5700 (LWP 7187)): #0 0x7f9654e58843 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9654e59193 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9654e5936c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f965907b52b in QEventDispatcherGlib::processEvents (this=0x7f96280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f965902563a in QEventLoop::exec (this=this@entry=0x7f962d7e4cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f9658e51b1c in QThread::exec (this=this@entry=0xee9970) at thread/qthread.cpp:503 #6 0x7f965c1219a5 in QQmlThreadPrivate::run (this=0xee9970) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7f9658e5694f in QThreadPrivate::start (arg=0xee9970) at thread/qthread_unix.cpp:331 #8 0x7f9657f6c4a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f965876dbdd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f9627fff700 (LWP 7189)): #0 0x7f9654e9c4b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9654e58899 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9654e59193 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9654e5936c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f965907b52b in QEventDispatcherGlib::processEvents (this=0x7f9628c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f965902563a in QEventLoop::exec (this=this@entry=0x7f9627ffecf0, flags=..., flags@entry=...) at kernel/qeven
[krita] [Bug 357796] Two clicks needed to open Edit Brush Settings if not closed with "X"
https://bugs.kde.org/show_bug.cgi?id=357796 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Glen, I'm not sure I've understood the report correctly. Here, * I don't have a close button on the brush editor if it's attached to the toolbar * if it's detached, it doesn't hide on painting, but stays on top. So I'm a bit puzzled. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 344322] Okteta frozen for a long time at startup
https://bugs.kde.org/show_bug.cgi?id=344322 Friedrich W. H. Kossebau changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WORKSFORME --- Comment #5 from Friedrich W. H. Kossebau --- Hi, thanks for reporting this problem (and sorry for not having replied in all the time). I could see that problem as well on some machines, but never came around to dig into it. And on my current system there is no such issue. >From the problem description it seems that the KF5 filedialog and filebrowser classes are blocked on some sync calls and that those return only after some timeout (or never). Not sure what is done wrong in Okteta code using those classes. To see debug output from KF5 classes, please start Okteta from the commandline with "QT_LOGGING_RULES="kf5.*=true okteta" Better would be to start it in the debugger and get a backtrace from the time when Okteta is blocked in the UI. But perhaps the respective bugs in KF5 classes got fixed meanwhile in newer releases? So do you still have these problems? https://bugs.kde.org/show_bug.cgi?id=349222 hints that at least the filedialog issue disappeared with Okteta 0.17 (or rather newer versions of KF5/Qt5). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358200] tiny size on panel with KF 5.18
https://bugs.kde.org/show_bug.cgi?id=358200 David Rosca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from David Rosca --- Same as BUG 358039 http://commits.kde.org/plasma-framework/11937533e83659dc4dab6f7e8e6019863a28ddae -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching
https://bugs.kde.org/show_bug.cgi?id=342186 --- Comment #16 from Piotr --- > Plasma: 5.4.3 > > Meta+Q open the activities bar, Meta+Tab does not work. Assigning a > different key combination (e.g. Ctrl+Tab) has also no effect. I still have this error also In Plasma 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357864] nvidia, windows10, wacom
https://bugs.kde.org/show_bug.cgi?id=357864 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Boudewijn Rempt --- I'm sorry, but I still cannot reproduce this. It looks like some settings in the nvidia driver are incompatible with the way Krita uses opengl. You can try playing with the nvidia settings, but there's nothing we can do, I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358200] tiny size on panel with KF 5.18
https://bugs.kde.org/show_bug.cgi?id=358200 Antonio Rojas changed: What|Removed |Added CC||now...@gmail.com --- Comment #2 from Antonio Rojas --- Bisected to commit 344dbeb: AppletQuickItem: Drop timer to create full representation -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 349222] okteta freezes on file browse dialog
https://bugs.kde.org/show_bug.cgi?id=349222 --- Comment #2 from Friedrich W. H. Kossebau --- Hi Matteo, thanks for the report, and also for telling that the problem finally disappeared again. Can you help me a little more and tell which version of KF5 you have been using, when Okteta 0.17 was no longer having the described issue? Because this seems a problem in KF5 classes, nothing in Okteta code was changed for 0.17. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357961] Color Picker not working through new transparent layer
https://bugs.kde.org/show_bug.cgi?id=357961 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Boudewijn Rempt --- Hi, Thanks for your report. I haven't been able to reproduce with 2.9, but I _can_ reproduce it with the 3.0 pre-alpha. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357987] Krita closes itself immediately after trying to load the specified file
https://bugs.kde.org/show_bug.cgi?id=357987 Boudewijn Rempt changed: What|Removed |Added Latest Commit|http://commits.kde.org/call |http://commits.kde.org/krit |igra/d664bb98d7882e5f63616b |a/8f7603ccd2a013695e5737c5a |a08c8876ab5eacc886 |8b9058885c2f041 --- Comment #9 from Boudewijn Rempt --- Git commit 8f7603ccd2a013695e5737c5a8b9058885c2f041 by Boudewijn Rempt. Committed on 20/01/2016 at 11:10. Pushed by rempt into branch 'master'. If the clone layers clone a layer above the clones in the stack, the original isn't available during loading. Krita shouldn't recalculate the project at this point, but merging already starts before the original is available, so add a temporary dummy fallback paint device that can be used until the original becomes available. M +4-2krita/image/kis_clone_layer.cpp http://commits.kde.org/krita/8f7603ccd2a013695e5737c5a8b9058885c2f041 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357987] Krita closes itself immediately after trying to load the specified file
https://bugs.kde.org/show_bug.cgi?id=357987 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/call ||igra/d664bb98d7882e5f63616b ||a08c8876ab5eacc886 --- Comment #8 from Boudewijn Rempt --- Git commit d664bb98d7882e5f63616ba08c8876ab5eacc886 by Boudewijn Rempt. Committed on 20/01/2016 at 11:03. Pushed by rempt into branch 'calligra/2.9'. If the clone layers clone a layer above the clones in the stack, the original isn't available during loading. Krita shouldn't recalculate the project at this point, but merging already starts before the original is available, so add a temporary dummy fallback paint device that can be used until the original becomes available. M +4-2krita/image/kis_clone_layer.cpp http://commits.kde.org/calligra/d664bb98d7882e5f63616ba08c8876ab5eacc886 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.
https://bugs.kde.org/show_bug.cgi?id=346768 --- Comment #54 from Wolfram --- (In reply to John Stanley from comment #53) > (In reply to George R. Goffe from comment #52) > > Hi, > > John/everyone, > > > > I have been thinking about this situation. > > > > I have multiple Fedora systems (F22/23/24). Generally they seem to be > > working ok now... more or less, including the Konsole and tabs problem. > > > > As I visualize it, the developers add config items, remove config items, > > change config items as they develop. Anything they don't hit directly would > > tend to remain. After a while, the config(s) would tend to have stuff that's > > no longer needed, wanted, or changed, or doesn't work any more as a result. > > I would like to suggest some form of migration of config(s) be performed by > > the developers in the install scripts (think rpmsave) to help eliminate the > > unused "stuff". For example, my fedora 22 system with KDE, starts the apps > > that I have running at the time of the save but it also starts things that > > ARE NOT REFERENCED by the save of configuration process AND/OR are NOT even > > running... so they remain. I don't know enough of the config process to > > isolate where the extra apps/config items are located. I don't want to > > remove everything and re-config. > > > > There's a kde-testing repo for Fedora systems but whoever builds/maintains > > needs to rebuild the repo index or other files AFTER update so the repodata > > can be syncronized. I wrote a bug on this... > > > > Have you tried removing .config and .kde/share/apps/ ... Like what would > > happen for a brand new user? > > > > Good luck, > > > > George... > Actually, during testing the patches I posted I removed .config/session + > .config/ksmserverrc frequently. More generally, after several frameworks > and/or plasma5 updates I had graphics/opengl artifacts and removing .config > entirely fixed the problems. For the latest update > (plasma-5.5.3/frameworks-5.18.0), no issues whatsoever, so an improvement. > > I'm curious, what version of konsole do have installed? Since yesterday I have plasma-5.5.3/frameworks-5.18.0 running on my Kubuntu 15.10 wokplace-system via backports-ppa. The session-problems still exist, so I tried your suggestion regarding .config in the following way: Logged out, renamed .config to .config_save in a konsole-session and logged in again. The result was, that I was not able to get my two screens running in kde anymore. Luckily I had saved my old .config and could switch back. Then I tried it with a new user. Here the two screens worked, but the session problem still exist. Maybe my environment is kind of strange: Two screens, folder-view on one screen, desktop-view on the other, four virtual desktops with different sessions running in each of them. But all this worked on in kde4 with no problems ! Since the forced change to kde5 in kubuntu (I promise to stick to LTS-release next time), my daily workaround is this: starting a new konsole window (and the tabs i need) if missing, if the positions of the desktop icons are messed up, copying ~/.config/plasma-org.kde.plasma.desktop-appletsrc.save to ~/.config/plasma-org.kde.plasma.desktop-appletsrc, then logging off and back in. If the konsole window appears, the tabs exist (this seems to be fixed), if not, I have to start a new konsole window again. Sometimes I also have to spread the the sessions back to the virtual desktops where they belong. It is frustrating ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357987] Krita closes itself immediately after trying to load the specified file
https://bugs.kde.org/show_bug.cgi?id=357987 --- Comment #7 from Boudewijn Rempt --- Hm, it actually hasn't got anything to do with fill layers at all -- the clones don't seem to be from the fill, but a single paint layer. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 345253] Folder I'm currently in not restored when selecting "Open file" with remote protocol
https://bugs.kde.org/show_bug.cgi?id=345253 Kevin Funk changed: What|Removed |Added CC||kf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 358208] Remember last-used location for attachment storage and downloads
https://bugs.kde.org/show_bug.cgi?id=358208 --- Comment #4 from Jan Kundrát --- Git commit ad89c0fa5c035774ca6b4eed9b72c62a5e506e21 by Jan Kundrát, on behalf of Thomas Lübking. Committed on 20/01/2016 at 10:06. Pushed by gerrit into branch 'master'. remember last dir for saving attachments Change-Id: I20322cc72d9aa2a742b951b49041807b5b739129 M +6-1src/Gui/AttachmentView.cpp http://commits.kde.org/trojita/ad89c0fa5c035774ca6b4eed9b72c62a5e506e21 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 357833] Valgrind is broken on recent linux kernel
https://bugs.kde.org/show_bug.cgi?id=357833 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment #3 from Mark Wielaard --- Looks like this commit went into linux git tree recently: commit 84638335900f1995495838fe1bd4870c43ec1f67 Author: Konstantin Khlebnikov AuthorDate: Thu Jan 14 15:22:07 2016 -0800 Commit: Linus Torvalds CommitDate: Thu Jan 14 16:00:49 2016 -0800 mm: rework virtual memory accounting So it should be possible to replicate this now with a "normal" linux git master build. But I haven't done so yet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 --- Comment #1 from Jürgen Scholz --- Created attachment 96749 --> https://bugs.kde.org/attachment.cgi?id=96749&action=edit Back trace of plasmashell 5.5.3 freeze after resume -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358245] New: plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=358245 Bug ID: 358245 Summary: plasmashell unresponsive/freezes after resuming from suspend to RAM Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: juergen.scholz...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org I am using ubuntu 15.10/wily with the kubuntu backports PPA, which at the moment provides plasmashell 5.5.3. Every time I resume my computer from suspend to RAM plasmashell freezes and does not react to any input. At the same time krunner is working fine and I can start applications or use already open ones normally. The situation can be resolved by issuing killall plasmashell; plasmashell in krunner. Additionally the mouse cursor is reacting with a lot of jitter to mouse movements, until a notification that eth0 has been re-connected appears. Sometimes there is a notification that eth0 has gone down (probably a delayed notification from the suspend process). I created a back trace with gdb - I hope the information necessary to diagnose the problem is in there. If not, I am happy to provide additional details on request. Reproducible: Always Steps to Reproduce: 1. Start KDE session. 2. Suspend machine to RAM. 3. Resume machine. Actual Results: Plasmashell does not react to input. Applications and krunner work. Expected Results: Plasmashell does react to inputs. Applications and krunner work. There is a similar bug report for version 5.4.0, which also showed this behavior on my machine. Please see https://bugs.kde.org/show_bug.cgi?id=352337 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358224] breeze dark plasma look and feel: KDE4 applications are using mixed (light and dark) colors, rendering text unreadable
https://bugs.kde.org/show_bug.cgi?id=358224 Christian Stadelmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Christian Stadelmann --- I don't know how themes did mess up so much, but this issue is now gone after deleting and reconfiguring themes several times. I hope it'll stay that way. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357987] Krita closes itself immediately after trying to load the specified file
https://bugs.kde.org/show_bug.cgi?id=357987 --- Comment #6 from Boudewijn Rempt --- Looks we also should consider saving the pattern in the generator layer, because just having the filename there is going to cause big trouble. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 357846] cursor barely visible for rectangle region
https://bugs.kde.org/show_bug.cgi?id=357846 --- Comment #5 from Boudhayan Gupta --- This *is* an usability bug at Spectacle's end. I intend to make the mask colour configurable - I'm undecided on whether to offer a colour selection dialog or just a choice between black and white. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 358226] Error while trying to send mail with Kmail from the address book.
https://bugs.kde.org/show_bug.cgi?id=358226 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Laurent Montel --- it works fine here. 4.13.2 is very old. Please retest on new version. Regards -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 340676] KGpg should support GnuPG 2.1
https://bugs.kde.org/show_bug.cgi?id=340676 --- Comment #16 from Christian Stadelmann --- Yes, the warning is gone with gpg2 (2.1.9). Fedora 23's version of KGpg seems to prefer gpg 1.x over gpg2 on installation. So this is a packaging issue. Thanks for your help and sorry for the noise! As far as this issue affects gpg2 2.1.x, I think it can be closed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357987] Krita closes itself immediately after trying to load the specified file
https://bugs.kde.org/show_bug.cgi?id=357987 --- Comment #5 from Boudewijn Rempt --- It's not simply that fill layers or clone layers with fill layers are broken, there's something more going on. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 300527] Okteta fails tests
https://bugs.kde.org/show_bug.cgi?id=300527 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Friedrich W. H. Kossebau --- Closing as resolved as none of the activated tests are failing on KDE CI (and locally for me) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357987] Krita closes itself immediately after trying to load the specified file
https://bugs.kde.org/show_bug.cgi?id=357987 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357987] Krita closes itself immediately after trying to load the specified file
https://bugs.kde.org/show_bug.cgi?id=357987 --- Comment #4 from Boudewijn Rempt --- Crash with the original file: #0 0x76ce071e in KisCloneLayer::original() const (this=) at /home/boud/kde/src/calligra/krita/image/kis_clone_layer.cpp:116 #1 0x76d4d65f in KisLayer::projection() const (this=0x37a0730) at /home/boud/kde/src/calligra/krita/image/kis_layer.cc:717 #2 0x76d5527c in KisLayerProjectionPlane::apply(KisPainter*, QRect const&) (this=0x31956b0, painter=0x7fffc77fdd20, rect=...) at /home/boud/kde/src/calligra/krita/image/kis_layer_projection_plane.cpp:52 #3 0x76d19873 in KisAsyncMerger::startMerge(KisBaseRectsWalker&, bool) (rect=..., leaf=..., this=0x36c35b0) at /home/boud/kde/src/calligra/krita/image/kis_async_merger.cpp:344 #4 0x76d19873 in KisAsyncMerger::startMerge(KisBaseRectsWalker&, bool) (this=this@entry=0x36c35b0, walker=..., notifyClones=notifyClones@entry=true) at /home/boud/kde/src/calligra/krita/image/kis_async_merger.cpp:272 #5 0x76c69413 in KisUpdateJobItem::run() (this=0x36c3570) at /home/boud/kde/build/calligra/krita/image/../../../../src/calligra/krita/image/kis_update_job_item.h:77 #6 0x76c69413 in KisUpdateJobItem::run() (this=0x36c3570) at /home/boud/kde/build/calligra/krita/image/../../../../src/calligra/krita/image/kis_update_job_item.h:58 #7 0x71637ace in QThreadPoolThread::run() (this=0x36e9990) at concurrent/qthreadpool.cpp:108 #8 0x71643bbf in QThreadPrivate::start(void*) (arg=0x36e9990) at thread/qthread_unix.cpp:349 #9 0x713ad0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7037404d in clone () at /lib64/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358037] Filling a selection with bucket tool.
https://bugs.kde.org/show_bug.cgi?id=358037 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Hi Wayne, I'm afraid I cannot reproduce the issue. Could you check with the latest stable Krita release (2.9.10) and if possible with a clean config (rename AppData\Roaming\krita to krita.bak and start Krita)? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 344907] Zoom slider/buttons fail to appear in top toolbar on opening Krita
https://bugs.kde.org/show_bug.cgi?id=344907 Boudewijn Rempt changed: What|Removed |Added CC||mercurial.spectre.1990@gmai ||l.com --- Comment #12 from Boudewijn Rempt --- *** Bug 358093 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358093] Attempting to remap shortcut for "Zoom" has no effect
https://bugs.kde.org/show_bug.cgi?id=358093 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Boudewijn Rempt --- Hi, Thanks for your report. This is another thing that happens because in 2.9 the zoom actions are created at the wrong moment -- it's the same issue as 344907 *** This bug has been marked as a duplicate of bug 344907 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358137] Krita crashes after splash window is displayed
https://bugs.kde.org/show_bug.cgi?id=358137 Boudewijn Rempt changed: What|Removed |Added Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call |a/77b39d8425ab25e1743ab1a6c |igra/ce879edf72ebb3be59fcda |a6c84493c8081d8 |06db8d1a09de20a9e3 --- Comment #4 from Boudewijn Rempt --- Git commit ce879edf72ebb3be59fcda06db8d1a09de20a9e3 by Boudewijn Rempt. Committed on 20/01/2016 at 10:13. Pushed by rempt into branch 'calligra/2.9'. Related: bug 0 M +5-1krita/ui/kis_config.cc M +4-2krita/ui/widgets/kis_scratch_pad.cpp http://commits.kde.org/calligra/ce879edf72ebb3be59fcda06db8d1a09de20a9e3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358130] mouse won't work on canvas after using a tablet
https://bugs.kde.org/show_bug.cgi?id=358130 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Hi, Thanks for your report. Which type of tablet are you using? -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 351785] Crash when clicking 'Configure...' button in Accounts settings
https://bugs.kde.org/show_bug.cgi?id=351785 Sergio changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #67 from Sergio --- I see the same issue with plasma 5.5.3 and framework 5.18.0 with the latest kubuntu updates on ubuntu 15.10. Pressing configure crashes plasma. Is there anything that I am missing? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358137] Krita crashes after splash window is displayed
https://bugs.kde.org/show_bug.cgi?id=358137 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/krit ||a/77b39d8425ab25e1743ab1a6c ||a6c84493c8081d8 Resolution|--- |FIXED --- Comment #3 from Boudewijn Rempt --- Git commit 77b39d8425ab25e1743ab1a6ca6c84493c8081d8 by Boudewijn Rempt. Committed on 20/01/2016 at 10:14. Pushed by rempt into branch 'master'. Related: bug 0 M +5-1krita/ui/kis_config.cc M +4-2krita/ui/widgets/kis_scratch_pad.cpp http://commits.kde.org/krita/77b39d8425ab25e1743ab1a6ca6c84493c8081d8 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame
https://bugs.kde.org/show_bug.cgi?id=357388 k...@stieler.org changed: What|Removed |Added CC||k...@stieler.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 357331] Konsole does not work properly when opened on secondary screen
https://bugs.kde.org/show_bug.cgi?id=357331 k...@stieler.org changed: What|Removed |Added CC||k...@stieler.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358137] Krita crashes after splash window is displayed
https://bugs.kde.org/show_bug.cgi?id=358137 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- Looks like one monitor is identified as "-1" ? #14 KisConfig::getScreenProfile (screen=screen@entry=-1) at /build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/kis_config.cc:409 That's never going to work... I can code around it, though. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356186] Background not transparent when started with dual monitor
https://bugs.kde.org/show_bug.cgi?id=356186 k...@stieler.org changed: What|Removed |Added CC||k...@stieler.org -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 340676] KGpg should support GnuPG 2.1
https://bugs.kde.org/show_bug.cgi?id=340676 --- Comment #15 from Rolf Eike Beer --- KGpg will pick gpg2 first if you run the first start wizard. Afterwards it will stick with whatever was found there or what you explicitely set in the settings dialog. If you did never run the first start wizard because your distro shipped a default config file, then it may be a config issue, if gpg2 is actually the default gpg on your distro. > kgpg(5082) GnupgBinary::setBinary: checking version of GnuPG executable > "gpg2" > kgpg(5082) GnupgBinary::setBinary: version is "2.1.9" 131337 Is the warning about the non-running agent now gone? For the 1.4 version it will be actually be right as your agent was probably not started. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346430] Crop tool failed to recognize current document size after using it for once
https://bugs.kde.org/show_bug.cgi?id=346430 Boudewijn Rempt changed: What|Removed |Added Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call |a/85708743c62802840185db74e |igra/45316325d47d9f4b48d4f8 |05a85d35599a048 |4b69c0827bbcdb9844 --- Comment #10 from Boudewijn Rempt --- Git commit 45316325d47d9f4b48d4f84b69c0827bbcdb9844 by Boudewijn Rempt. Committed on 20/01/2016 at 10:09. Pushed by rempt into branch 'calligra/2.9'. Fix bug 346430 Make sure the crop tool allways uses the correct image size. Patch by Thorsten Zachmann M +1-3krita/plugins/tools/tool_crop/kis_tool_crop.cc http://commits.kde.org/calligra/45316325d47d9f4b48d4f84b69c0827bbcdb9844 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358202] kwin often stops partially working (Function not implemented)
https://bugs.kde.org/show_bug.cgi?id=358202 --- Comment #7 from Thomas Lübking --- Your post *is* helpful. I didn't mean to directly reply to your message but took it as confirmation that all of the issues in the report are caused by irregular server timestamps - and likely be caused by clusterssh. Thus marking it as a dupe (which it is, even iff there's a client beyond clusterssh causing this - from the KWin side it really doesn't matter who screws event times, fact is that we - and all of Qt5 - aren't sufficiently robust against that. The WM should ideally not be knocked out by some broken client) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] Crash when trying to open or create a file
https://bugs.kde.org/show_bug.cgi?id=358147 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org Resolution|--- |LATER --- Comment #4 from Boudewijn Rempt --- We know the issue and the reason for it -- this week we'll try to figure out a way to work around the broken Intel drivers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358160] Can not create a new image nor open files.
https://bugs.kde.org/show_bug.cgi?id=358160 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |LATER CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 353573] DBusActivatable is true in the .desktop file but Okteta is not DBusActivatable
https://bugs.kde.org/show_bug.cgi?id=353573 Friedrich W. H. Kossebau changed: What|Removed |Added Version Fixed In||0.18.2 --- Comment #2 from Friedrich W. H. Kossebau --- Thanks for reporting, seems I missed the complete picture when I added that during the KF5 port :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358202] kwin often stops partially working (Function not implemented)
https://bugs.kde.org/show_bug.cgi?id=358202 --- Comment #6 from Fredi --- I didn't said that it has to do with kwin, i wanted to be helpful adding some more info in case it's needed -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 353573] DBusActivatable is true in the .desktop file but Okteta is not DBusActivatable
https://bugs.kde.org/show_bug.cgi?id=353573 Friedrich W. H. Kossebau changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/okte ||ta/6efd8baece75e8fd2b2c18e0 ||866a33b46b0c1e84 Resolution|--- |FIXED --- Comment #1 from Friedrich W. H. Kossebau --- Git commit 6efd8baece75e8fd2b2c18e0866a33b46b0c1e84 by Friedrich W. H. Kossebau. Committed on 20/01/2016 at 09:56. Pushed by kossebau into branch 'Applications/15.12'. Remove wrong DBusActivatable entry from okteta's app desktop file M +0-1program/org.kde.okteta.desktop http://commits.kde.org/okteta/6efd8baece75e8fd2b2c18e0866a33b46b0c1e84 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358242] Krita-crashed while opening the attached file 20151120_094824.jpg with the option open with GIF-Image or JPEG-Image. It was send from a MobilePhone. You can see Hex using BlessHex
https://bugs.kde.org/show_bug.cgi?id=358242 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org Resolution|--- |UPSTREAM --- Comment #2 from Boudewijn Rempt --- Hi Josef, Krita says the same thing: Not a JPEG file: starts with 0x3f 0x3f I'm afraid that means that it just isn't a jpeg file -- it really isn't. It starts with "???/?Exif" -- my guess is that it's only metadata about the image. Krita, even 3.0 (2.8 is really old) crashes because the jpeg library crashes when confronted with the broken input. I'm afraid that this is a bug that Samsung should solve... Not that they will! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #7 from David Edmundson --- Note whilst I can still remember. xcb_generic_event_t.response_type == 102 103 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 --- Comment #7 from Robin Green --- That's fortunate, because QDBUS_DEBUG=1 doesn't work on my machine. Maybe it is something to do with the way the Fedora packages are built. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times
https://bugs.kde.org/show_bug.cgi?id=348569 Thomas Lübking changed: What|Removed |Added CC||softw...@moritz-augustin.de --- Comment #29 from Thomas Lübking --- *** Bug 358202 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358202] kwin often stops partially working (Function not implemented)
https://bugs.kde.org/show_bug.cgi?id=358202 Thomas Lübking changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Thomas Lübking --- In case you've another client that uses server timestamps of the 30ies century, please record them, but from the KWin side, this is the same problem (and likely is just clusterssh) *** This bug has been marked as a duplicate of bug 348569 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358244] KDE Plasma 5.5.3 with dual monitor: one screen has no wallpaper but left black on login
https://bugs.kde.org/show_bug.cgi?id=358244 Thomas Lübking changed: What|Removed |Added CC||bhus...@gmail.com, ||plasma-b...@kde.org Component|general |general Target Milestone|--- |1.0 Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- Assignee|kwin-bugs-n...@kde.org |k...@davidedmundson.co.uk Product|kwin|plasmashell --- Comment #3 from Thomas Lübking --- Please inform the plasmashell devs whether there's no desktop window or just no wallpaper. Rightclick the "no wallpaper" area and check whether a popup shows up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358244] KDE Plasma 5.5.3 with dual monitor: one screen has no wallpaper but left black on login
https://bugs.kde.org/show_bug.cgi?id=358244 --- Comment #2 from d...@dyle.org --- Well, after login the screen is black. But I can open up a window and drag it onto the black screen. There it is visible and fine. So, everything is fine, except the wallpaper is missing on the screen. When I disable/enable the screen in the Display Configuration then the wallpaper reappears. BUT: when I change the wallpaper in the Desktop Settings, only the Wallpaper of the "good" screen changes. I can't change the Wallpaper of the (once) black screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358202] kwin often stops partially working (Function not implemented)
https://bugs.kde.org/show_bug.cgi?id=358202 Fredi changed: What|Removed |Added CC||frederik.n...@gmail.com --- Comment #4 from Fredi --- Just some more info, i had the same behaviour with both firefox and thunderbird (XUL in common?) when using clusterssh. The menus wouldnt open. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #6 from David Edmundson --- Git commit 3936e2230d71948d4bd70c062f34d6cbc93e69c3 by David Edmundson. Committed on 20/01/2016 at 08:56. Pushed by davidedmundson into branch 'master'. Cache QX11Info::appRootWindow in eventFilter appRootWindow is (relatively) expensive and won't change. nativeEventFilter is called a lot This should speed things up. REVIEW: 126818 M +6-5src/platforms/xcb/kwindowsystem.cpp M +2-0src/platforms/xcb/kwindowsystem_p_x11.h http://commits.kde.org/kwindowsystem/3936e2230d71948d4bd70c062f34d6cbc93e69c3 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 134854] show read-only files in "File List" and editor tabs
https://bugs.kde.org/show_bug.cgi?id=134854 Kevin Funk changed: What|Removed |Added Depends on|154897 | Version Fixed In||5.0.0 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Kevin Funk --- Fixed. Note that the KTextEditor bug is *still* not resolved. I.e. the read-only state of a file is not deduced from its access rights represented on disk. You still have to mark a file as "read only" yourself. -> KTextEditor issue, though. commit abfa9b80fb61e74cd604473b7ec5810feb7ed5ff Author: Artur Puzio Date: Tue Jan 19 22:12:50 2016 +0100 MainWindow: Add indicator for read-only files Summary: This fixes the [[ https://bugs.kde.org/show_bug.cgi?id=134854 | Bug 134854 ]] If current file is read-only (checked with `ReadWritePart::isReadWrite()`) the window title changes - "(read only)" is added. To check if the read-only status changed `KTextEditor::Document::readWriteChanged` signal is used. Note: chmod-ing a file won't make in read only for `ReadWritePart::isReadWrite()`. Test Plan: Seams to work fine. BUG: 134854 Reviewers: kfunk Reviewed By: kfunk Subscribers: kdevelop-devel Differential Revision: https://phabricator.kde.org/D794 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 154897] read-only files: add visual indicator
https://bugs.kde.org/show_bug.cgi?id=154897 Kevin Funk changed: What|Removed |Added Blocks|134854 | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358236] plasmas shell segfault when connecting to vpn via network-manager applet
https://bugs.kde.org/show_bug.cgi?id=358236 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 346118 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 David Edmundson changed: What|Removed |Added CC||tsut...@gmail.com --- Comment #36 from David Edmundson --- *** Bug 358236 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358243] Plasma5 crashes on startup
https://bugs.kde.org/show_bug.cgi?id=358243 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Open GL drivers broken/missing. *** This bug has been marked as a duplicate of bug 345563 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed
https://bugs.kde.org/show_bug.cgi?id=345563 David Edmundson changed: What|Removed |Added CC||olivh...@yahoo.de --- Comment #63 from David Edmundson --- *** Bug 358243 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358244] KDE Plasma 5.5.3 with dual monitor: one screen has no wallpaper but left black on login
https://bugs.kde.org/show_bug.cgi?id=358244 Thomas Lübking changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Thomas Lübking --- Not kwin related, it's either a bug in kscreen or plasmashell. To know which: is it really the wallpaper or is there no desktop at all (is there a config button or can you rightclick the "no wallpaper" to get a config menu)? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 352097] Dolphin Version 15.08.0 trash strange behavior after deleting files.
https://bugs.kde.org/show_bug.cgi?id=352097 --- Comment #15 from Zoran Dimovski --- I confirm that the problem is gone after upgrade to Frameworks 5.18 KDE Plasma version: 5.5.3 KDE Frameworks: 5.18 KDE Applications: 15.12.1 Qt Version: 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358244] New: KDE Plasma 5.5.3 with dual monitor: one screen has no wallpaper but left black on login
https://bugs.kde.org/show_bug.cgi?id=358244 Bug ID: 358244 Summary: KDE Plasma 5.5.3 with dual monitor: one screen has no wallpaper but left black on login Product: kwin Version: 5.5.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: d...@dyle.org After manually disable/enable the screen in the Display Configuration the wallpaper reappears again. However, that's sort of pretty annoying everytime on login. Reproducible: Always Actual Results: No wallpaper on one of the screen. Expected Results: Wallpaper should be present. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.
https://bugs.kde.org/show_bug.cgi?id=346768 --- Comment #53 from John Stanley --- (In reply to George R. Goffe from comment #52) > Hi, > John/everyone, > > I have been thinking about this situation. > > I have multiple Fedora systems (F22/23/24). Generally they seem to be > working ok now... more or less, including the Konsole and tabs problem. > > As I visualize it, the developers add config items, remove config items, > change config items as they develop. Anything they don't hit directly would > tend to remain. After a while, the config(s) would tend to have stuff that's > no longer needed, wanted, or changed, or doesn't work any more as a result. > I would like to suggest some form of migration of config(s) be performed by > the developers in the install scripts (think rpmsave) to help eliminate the > unused "stuff". For example, my fedora 22 system with KDE, starts the apps > that I have running at the time of the save but it also starts things that > ARE NOT REFERENCED by the save of configuration process AND/OR are NOT even > running... so they remain. I don't know enough of the config process to > isolate where the extra apps/config items are located. I don't want to > remove everything and re-config. > > There's a kde-testing repo for Fedora systems but whoever builds/maintains > needs to rebuild the repo index or other files AFTER update so the repodata > can be syncronized. I wrote a bug on this... > > Have you tried removing .config and .kde/share/apps/ ... Like what would > happen for a brand new user? > > Good luck, > > George... Actually, during testing the patches I posted I removed .config/session + .config/ksmserverrc frequently. More generally, after several frameworks and/or plasma5 updates I had graphics/opengl artifacts and removing .config entirely fixed the problems. For the latest update (plasma-5.5.3/frameworks-5.18.0), no issues whatsoever, so an improvement. I'm curious, what version of konsole do have installed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358243] New: Plasma5 crashes on startup
https://bugs.kde.org/show_bug.cgi?id=358243 Bug ID: 358243 Summary: Plasma5 crashes on startup 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: olivh...@yahoo.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I always get black screen after X login since today 2016-01-20. System is Opensuse leap on a HP Elitebook 8570w with Nvidia driver. Latest patches are applied. Did try with a new user with same result. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8ccb068800 (LWP 6205))] Thread 3 (Thread 0x7f8cb3228700 (LWP 6207)): #0 0x7f8cc45bec1d in poll () at /lib64/libc.so.6 #1 0x7f8cc94ea422 in () at /usr/lib64/libxcb.so.1 #2 0x7f8cc94ec00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f8cb59ab3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f8cc4cb632f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cc3dc80a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cc45c704d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f8cab5ef700 (LWP 6224)): #0 0x7f8cc45bec1d in poll () at /lib64/libc.so.6 #1 0x7f8cc0ca0e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8cc0ca0f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8cc4ee8d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8cc4e8fd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cc4cb161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8cc7f9cdf8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f8cc4cb632f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8cc3dc80a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8cc45c704d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f8ccb068800 (LWP 6205)): [KCrash Handler] #6 0x7f8cc4517187 in raise () at /lib64/libc.so.6 #7 0x7f8cc4518538 in abort () at /lib64/libc.so.6 #8 0x7f8cc4ca47ce in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8cb59c1762 in QXcbWindow::create() () at /usr/lib64/libQt5XcbQpa.so.5 #10 0x7f8cb1ddb299 in () at /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-egl-integration.so #11 0x7f8cb59acc22 in QXcbIntegration::createPlatformWindow(QWindow*) const () at /usr/lib64/libQt5XcbQpa.so.5 #12 0x7f8cc53e9e25 in QWindowPrivate::create(bool) () at /usr/lib64/libQt5Gui.so.5 #13 0x7f8cc53ea0a8 in QWindow::winId() const () at /usr/lib64/libQt5Gui.so.5 #14 0x7f8ccaa7e9b5 in PlasmaQuick::Dialog::setType(PlasmaQuick::Dialog::WindowType) () at /usr/lib64/libKF5PlasmaQuick.so.5 #15 0x7f8ccaa817cc in () at /usr/lib64/libKF5PlasmaQuick.so.5 #16 0x7f8ccaa8332b in PlasmaQuick::Dialog::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/libKF5PlasmaQuick.so.5 #17 0x7f8cc7f05b68 in QQmlVMEMetaObject::metaCall(QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Qml.so.5 #18 0x7f8cc7f1f737 in QQmlPropertyPrivate::writeBinding(QObject*, QQmlPropertyData const&, QQmlContextData*, QQmlJavaScriptExpression*, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #19 0x7f8cc7f89823 in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #20 0x7f8cc7f9354a in () at /usr/lib64/libQt5Qml.so.5 #21 0x7f8cc7f261ea in () at /usr/lib64/libQt5Qml.so.5 #22 0x7f8cc7f26d2e in QQmlIncubationController::incubateFor(int) () at /usr/lib64/libQt5Qml.so.5 #23 0x7f8cc902499c in () at /usr/lib64/libKF5Declarative.so.5 #24 0x7f8cc7f269c5 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib64/libQt5Qml.so.5 #25 0x7f8cc7f2237c in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () at /usr/lib64/libQt5Qml.so.5 #26 0x7f8cc9014010 in KDeclarative::QmlObject::completeInitialization(QHash const&) () at /usr/lib64/libKF5Declarative.so.5 #27 0x7f8cc90140bc in () at /usr/lib64/libKF5Declarative.so.5 #28 0x7f8cc9014271 in () at /usr/lib64/libKF5Declarative.so.5 #29 0x00465cbb in Osd::Osd(ShellCorona*) () #30 0x00458e26 in ShellCorona::ShellCorona(QObject*) () #31 0x00462179 in ShellManager::loadHandlers() () #32 0x7f8cc4ec2ac6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #33 0x7f8cc620ae7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #34 0x7f8cc620fcc8 in QApplication::notify(QObjec
[kdenlive] [Bug 357710] wipe transition uses incorrect shape size when using a png lumas file
https://bugs.kde.org/show_bug.cgi?id=357710 --- Comment #4 from Jean-Baptiste Mardelle --- Git commit 331fd851d7a99afe6ef244c49630034f3e1dc541 by Jean-Baptiste Mardelle. Committed on 20/01/2016 at 08:19. Pushed by mardelle into branch 'master'. Revert luma files to pgm, faster and solves scaling issues Related: bug 358177 M +18 -18 data/lumas/CMakeLists.txt A +---data/lumas/bi-linear_x.pgm D +---data/lumas/bi-linear_x.png A +1445 -0data/lumas/bi-linear_y.pgm D +---data/lumas/bi-linear_y.png A +5-0data/lumas/burst.pgm D +---data/lumas/burst.png A +5005 -0data/lumas/checkerboard_small.pgm D +---data/lumas/checkerboard_small.png A +5-0data/lumas/clock.pgm D +---data/lumas/clock.png A +1379 -0data/lumas/cloud.pgm D +---data/lumas/cloud.png A +1213 -0data/lumas/curtain.pgm D +---data/lumas/curtain.png A +---data/lumas/horizontal_blinds.pgm D +---data/lumas/horizontal_blinds.png A +---data/lumas/linear_x.pgm D +---data/lumas/linear_x.png A +---data/lumas/linear_y.pgm D +---data/lumas/linear_y.png A +---data/lumas/radial-bars.pgm D +---data/lumas/radial-bars.png A +209 -0data/lumas/radial.pgm D +---data/lumas/radial.png A +5-0data/lumas/spiral.pgm D +---data/lumas/spiral.png A +5-0data/lumas/spiral2.pgm D +---data/lumas/spiral2.png A +125 -0data/lumas/square.pgm D +---data/lumas/square.png A +---data/lumas/square2-bars.pgm D +---data/lumas/square2-bars.png A +389 -0data/lumas/square2.pgm D +---data/lumas/square2.png A +---data/lumas/symmetric_clock.pgm D +---data/lumas/symmetric_clock.png http://commits.kde.org/kdenlive/331fd851d7a99afe6ef244c49630034f3e1dc541 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358177] Kdenlive-git - Issue with Wipe transition, not working properly. (video example included)
https://bugs.kde.org/show_bug.cgi?id=358177 --- Comment #2 from Jean-Baptiste Mardelle --- Git commit 331fd851d7a99afe6ef244c49630034f3e1dc541 by Jean-Baptiste Mardelle. Committed on 20/01/2016 at 08:19. Pushed by mardelle into branch 'master'. Revert luma files to pgm, faster and solves scaling issues Related: bug 357710 M +18 -18 data/lumas/CMakeLists.txt A +---data/lumas/bi-linear_x.pgm D +---data/lumas/bi-linear_x.png A +1445 -0data/lumas/bi-linear_y.pgm D +---data/lumas/bi-linear_y.png A +5-0data/lumas/burst.pgm D +---data/lumas/burst.png A +5005 -0data/lumas/checkerboard_small.pgm D +---data/lumas/checkerboard_small.png A +5-0data/lumas/clock.pgm D +---data/lumas/clock.png A +1379 -0data/lumas/cloud.pgm D +---data/lumas/cloud.png A +1213 -0data/lumas/curtain.pgm D +---data/lumas/curtain.png A +---data/lumas/horizontal_blinds.pgm D +---data/lumas/horizontal_blinds.png A +---data/lumas/linear_x.pgm D +---data/lumas/linear_x.png A +---data/lumas/linear_y.pgm D +---data/lumas/linear_y.png A +---data/lumas/radial-bars.pgm D +---data/lumas/radial-bars.png A +209 -0data/lumas/radial.pgm D +---data/lumas/radial.png A +5-0data/lumas/spiral.pgm D +---data/lumas/spiral.png A +5-0data/lumas/spiral2.pgm D +---data/lumas/spiral2.png A +125 -0data/lumas/square.pgm D +---data/lumas/square.png A +---data/lumas/square2-bars.pgm D +---data/lumas/square2-bars.png A +389 -0data/lumas/square2.pgm D +---data/lumas/square2.png A +---data/lumas/symmetric_clock.pgm D +---data/lumas/symmetric_clock.png http://commits.kde.org/kdenlive/331fd851d7a99afe6ef244c49630034f3e1dc541 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358242] New: Krita-crashed while opening the attached file 20151120_094824.jpg with the option open with GIF-Image or JPEG-Image. It was send from a MobilePhone. You can see is using Bles
https://bugs.kde.org/show_bug.cgi?id=358242 Bug ID: 358242 Summary: Krita-crashed while opening the attached file 20151120_094824.jpg with the option open with GIF-Image or JPEG-Image. It was send from a MobilePhone. You can see is using BlessHexEditor. Product: krita Version: 2.8.5 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: josef.overm...@yahoo.de Application: krita (2.8.5) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.13.0-37-generic x86_64 Distribution: Linux Mint 17.1 Rebecca -- Information about the crash: - What I was doing when the application crashed: Opening the attached File 20151120_094824.jpg with Krita and there with GIF or JPEG-Image - Custom settings of the application: The crash can be reproduced every time. -- 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 0x7fdaf6ecd7c0 (LWP 6186))] Thread 7 (Thread 0x7fdadcb23700 (LWP 6187)): #0 0x7fdaf673c12d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fdaeeab2fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdaeeab330a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdae46a6336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fdaeead7f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdaeef92182 in start_thread (arg=0x7fdadcb23700) at pthread_create.c:312 #6 0x7fdaf674947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7fdad7fff700 (LWP 6188)): #0 0x7fdaeeaf461a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fdaeeaf49a9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdaeeab20f0 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdaeeab2ea5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdaeeab30ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdaeeab3129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fdaeead7f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fdaeef92182 in start_thread (arg=0x7fdad7fff700) at pthread_create.c:312 #8 0x7fdaf674947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7fdabd0d4700 (LWP 6190)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fdaf4772816 in wait (time=18446744073709551615, this=0x59365f0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0x59365a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fdaf476e95b in QSemaphore::acquire (this=this@entry=0x59362d0, n=n@entry=1) at thread/qsemaphore.cpp:144 #4 0x7fdaf33b69fe in KisTileDataPooler::waitForWork (this=this@entry=0x59362c0) at /build/buildd/calligra-2.8.5/krita/image/tiles3/kis_tile_data_pooler.cc:162 #5 0x7fdaf33b6dcd in KisTileDataPooler::run (this=0x59362c0) at /build/buildd/calligra-2.8.5/krita/image/tiles3/kis_tile_data_pooler.cc:184 #6 0x7fdaf477232f in QThreadPrivate::start (arg=0x59362c0) at thread/qthread_unix.cpp:349 #7 0x7fdaeef92182 in start_thread (arg=0x7fdabd0d4700) at pthread_create.c:312 #8 0x7fdaf674947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7fdabc8d3700 (LWP 6191)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fdaf4772816 in wait (time=18446744073709551615, this=0x59369a0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0x5936950, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fdaf476ed63 in QSemaphore::tryAcquire (this=0x5936660, n=n@entry=1, timeout=timeout@entry=-1) at thread/qsemaphore.cpp:221 #4 0x7fdaf33d39e3 in KisTileDataSwapper::waitForWork (this=this@entry=0x59362f8) at /build/buildd/calligra-2.8.5/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #5 0x7fdaf33d3c6a in KisTileDataSwapper::run (this=0x59362f8) at /build/buildd/calligra-2.8.5/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #6 0x7fdaf477232f in QThreadPrivate::start (arg=0x59362f8) at thread/qthread_unix.cpp:349 #7 0x7fdaeef92182 in start_thread (arg=0x7fdabc8d3700) at pthread_create.c:312 #8 0x7fdaf674947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fdad77fe700 (LWP 6200)): #0 pthread_cond_wait@@GLIBC_2.3.2 ()
[krita] [Bug 358242] Krita-crashed while opening the attached file 20151120_094824.jpg with the option open with GIF-Image or JPEG-Image. It was send from a MobilePhone. You can see Hex using BlessHex
https://bugs.kde.org/show_bug.cgi?id=358242 Josef Overmann changed: What|Removed |Added Summary|Krita-crashed while opening |Krita-crashed while opening |the attached file |the attached file |20151120_094824.jpg with|20151120_094824.jpg with |the option open with|the option open with |GIF-Image or JPEG-Image. It |GIF-Image or JPEG-Image. It |was send from a |was send from a |MobilePhone. You can see is |MobilePhone. You can see |using BlessHexEditor. |Hex using BlessHexEditor. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358242] Krita-crashed while opening the attached file 20151120_094824.jpg with the option open with GIF-Image or JPEG-Image. It was send from a MobilePhone. You can see is using BlessHexE
https://bugs.kde.org/show_bug.cgi?id=358242 Josef Overmann changed: What|Removed |Added CC||josef.overm...@yahoo.de --- Comment #1 from Josef Overmann --- Created attachment 96748 --> https://bugs.kde.org/attachment.cgi?id=96748&action=edit The JPEG-file was send from SAMSUNG-Mobil to my Email-Adress, but there is no way to open it. Many Graphic-Programs fail (GIMP, FEH, KRITA and so on) When opening the file with ristretto, the error is displayed: not a jpg-file! File: starts with 0x3f 0x3f when opening with image magic the error is displayed: unknow format when opening with Gwenview the error is displayed: Loading 20151120_094824.jpg failed. Loading meta information failed. in the same way it fails with the programs okular, comics, and many others, but you can see it in a very small thumb on the file-manager thunar 1.6.3. But how to open with others? -- You are receiving this mail because: You are watching all bug changes.
