[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout
https://bugs.kde.org/show_bug.cgi?id=348194 Andrea Scarpino changed: What|Removed |Added CC|scarp...@kde.org| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours
https://bugs.kde.org/show_bug.cgi?id=369099 J.O. Aho changed: What|Removed |Added Resolution|WAITINGFORINFO |BACKTRACE -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369023] I want to downgrade to 16.04.3 because 16.08.1 is essentially unusable for me
https://bugs.kde.org/show_bug.cgi?id=369023 Vincent PINON changed: What|Removed |Added Resolution|WONTFIX |FIXED --- Comment #11 from Vincent PINON --- After fixing urgent problems on other PPAs, I've setup the one you asked for: https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-oldstable/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369264] Fedora 24 i686 and vex x86->IR: unhandled instruction bytes: 0xC5 0xF8 0x10 0x3
https://bugs.kde.org/show_bug.cgi?id=369264 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment #1 from Mark Wielaard --- That is vmovups which is only supported by valgrind as amd64 (x86_64) instruction. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368515] Kmail crashing some time after start
https://bugs.kde.org/show_bug.cgi?id=368515 --- Comment #2 from Linder --- Error is still existing in kmail after last updates of SuSE tumbleweed (now using kernel 4.7.4-1default). kmail is still reporting version 5.3.0. Crash report looks quite similar to me, but for helping tracking the bug I have attached it below again: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe21740e940 (LWP 2484))] Thread 34 (Thread 0x7fe0fd7d8700 (LWP 2571)): #0 0x7fe20a04110f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe200527d49 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fe200528460 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fe200528630 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fe20052523d in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fe20a03b454 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe2141b13ff in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7fe17f6e8700 (LWP 2556)): #0 0x7fe20a04110f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe1fafea7e4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fe1fafea829 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fe20a03b454 in start_thread () from /lib64/libpthread.so.0 #4 0x7fe2141b13ff in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7fe180954700 (LWP 2544)): #0 0x7fe2141bdc8d in __libc_disable_asynccancel () from /lib64/libc.so.6 #1 0x7fe2141a86f9 in poll () from /lib64/libc.so.6 #2 0x7fe209815876 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe20981598c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe214ce7aab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe214c8f6fa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe214ab53c3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7fe214aba2e8 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fe20a03b454 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe2141b13ff in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7fe1817c8700 (LWP 2541)): #0 0x7fe214ab2419 in QMutex::unlock() () from /usr/lib64/libQt5Core.so.5 #1 0x7fe214ce72b5 in ?? () from /usr/lib64/libQt5Core.so.5 #2 0x7fe209815269 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe209815814 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe20981598c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe214ce7aab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe214c8f6fa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe214ab53c3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fe214aba2e8 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7fe20a03b454 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe2141b13ff in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7fe184019700 (LWP 2534)): #0 0x7fe20985ae89 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe209814760 in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe209815725 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe20981598c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe214ce7aab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe214c8f6fa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe214ab53c3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7fe214aba2e8 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fe20a03b454 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe2141b13ff in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7fe18481a700 (LWP 2524)): #0 0x7fe2141bdbcb in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7fe2141bf684 in __fprintf_chk () from /lib64/libc.so.6 #2 0x7fe214aa54b0 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x7fe214a9f7b8 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x7fe214aa064c in QMessageLogger::warning(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #5 0x7fe214ce70d2 in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x7fe209815269 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #7 0x7fe209815814 in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x7fe20981598c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x7fe214ce7a8f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #10 0x7fe214c8f6fa in QEventLoop::
[Akonadi] [Bug 309474] akonadictl fsck : item has no RID
https://bugs.kde.org/show_bug.cgi?id=309474 Chris Samuel changed: What|Removed |Added CC||k...@csamuel.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365968] scrolling is unusable slow with libinput in dolphin places and folders panel
https://bugs.kde.org/show_bug.cgi?id=365968 João Vidal da Silva changed: What|Removed |Added CC||joao.vidal.si...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 369247] Kontact 5.3.1: settings between Kontact and components (e.g. KMail) are not synchronized
https://bugs.kde.org/show_bug.cgi?id=369247 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Ok could you give me an example please ? -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 369259] Regression: owncloud account creation wizard uses 'dav' instead of 'caldav' and 'carddar' in URL completion
https://bugs.kde.org/show_bug.cgi?id=369259 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #2 from Laurent Montel --- In wizard which type of owncloud type do you use to configure it ? owncloud ? owncloud <5 owncloud between 6 and 9 ? ? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361597] Firewire capture not working in version 15.12.1
https://bugs.kde.org/show_bug.cgi?id=361597 --- Comment #10 from Andrew Fomin --- If you are not going to support firewire anymore, the least you could do is provide the .9.10 version in with all dependencies rolled up into a tarball. Using a command line program gets problematic when you have many tapes to transfer. All those powerful features are useless if you can't get your content into the program. On Fri, Sep 23, 2016 at 2:18 PM, Martin Wolf via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=361597 > > --- Comment #9 from Martin Wolf --- > Hi Farid, > > ok - I understand that a few people cannot do all work. I use dvgrab now, > and > try to view the film directly with vlc. vlc is about one second behind, > it's > not perfect but works after a fashion. > The only reason to use kdenlive (after kino had died) was that it could > grab > from firewire - so there is no special reason for me to use it in future. > Will > see ... > > Nevertheless, thanks and regards > Martin > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369249] Copying/Moving a file onto itself in folderview crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=369249 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #1 from Fabian Vogt --- I made a fix for this on https://phabricator.kde.org/D2847 and the reporter confirms that it works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369200] translation file for plasma_applet_kdeobservatory.pot is missing in svn repository
https://bugs.kde.org/show_bug.cgi?id=369200 --- Comment #5 from Freek de Kruijf --- The file plasma_applet_kdeobservatory.po is still in kde-l10n-nl-16.08.0.tar.xz from the download site of kde.org. Should it be removed? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 369276] New: KActionCollection, menu/action reuse and the native Mac menubar
https://bugs.kde.org/show_bug.cgi?id=369276 Bug ID: 369276 Summary: KActionCollection, menu/action reuse and the native Mac menubar Product: frameworks-kxmlgui Version: unspecified Platform: Other OS: OS X Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: rjvber...@gmail.com I'm making another attempt at raising awareness about a Qt platform limitation on Mac that has potentially severe implications for reuse of QMenus, QActions and QActionWidgets in multiple menus if one of those is attached to a native QMenuBar. In short, this is not possible (because items attached to the native menubar are reparented away from their original parent), and according to the documentation it can lead to the menu items (be they actions or submenus) not appearing or remaining disabled. The documentation isn't explicit which instances might not appear or remain disabled; practical experience suggests this only occurs in menus under the toplevel menubar. Qt versions before 5.3 were not affected to the best of my knowledge; 5.4 and 5.5 would print error messages each time the software added an item to or removed it from an additional menu. In other words, the KActionCollection class is compromised on OS X, and that's not exactly a class that sees only limited use. The big problem here is that it is near impossible to predict which instances will be affected. With earlier KTextEditor and Qt versions, for instance, I had to disable the paste history and bookmarks menus to stop the error messages. With Qt 5.6.1 and KTextEditor 5.24.0 it is the Mode and Highlighting menus that are populated almost exclusively with disabled submenus. The fact that items are reparented suggests that reusing them may also lead to memory leak, accessing stale objects or double freeing (and indeed I have seen some crashes that appeared related to menu item reuse). The most effective solution I've found until now is to disable the native menubar. Evidently this isn't ideal if the goal is to make KDE applications look and behave as natively as possible. Also, just setting the Qt::AA_DontUseNativeMenuBar attribute before any menus are created isn't enough for all applications. Some may (like KHelpCenter) never show the menubar, some (those that do not offer a hide/show menu feature like KDevelop) may start unpredictably with the menubar in hidden state, or hide it at runtime in reaction to some event. The alternative solution is to avoid reuse on OS X, either in the source code or in the ui.rc definition files but it is my experience that it isn't always trivial to figure out what to disable where. I've tried to get some answers about the underlying limitation from the Qt team on one of their mailing lists, but it is probably worthwhile to start thinking of workarounds independently. After all the official Qt stance may be "software just shouldn't do this", like with QMenu::addSection() (which doesn't add a named section on all platforms). Reproducible: Sometimes Steps to Reproduce: 1. Create QMenu, QAction and/or QActionWidget instances 2. Add them to a QMenuBar that corresponds to the Mac native, toplevel menubar in addition to one or more other menu(bar)s Actual Results: the instances (or items therein) may not appear or remain disabled, a priori only in the toplevel menubar (but that may depend on the order of attribution). Expected Results: All instances in all menu(bar)s appear and are enabled as expected I'm hesitating between calling this a wishlist ticket and something stronger. KActionCollection sees considerably widespread use, so I'm going to settle with "Major". -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 369232] cmake fails on missing rcc, it's a runtime dep though
https://bugs.kde.org/show_bug.cgi?id=369232 --- Comment #3 from Jarosław Staniek --- "I cannot think of a single packaging environment where build environment == run environment." This is stronger requirement Kexi does not have. No need to use this argument. "The rcc being there at buildtime doesn't mean anything WRT runtime." Yes but only in worst case, when the intent of person compiling is rather wrong. Based on what I know packagers (with intent to ship properly) are rather grateful for pointers they get from the configure time. And people that build Kexi for the first time in order to start contributing. On top of that Kexi properly communicates what's required and recommended dependency at configure time, that's the case since the older times of KOffice and Calligra. Thanks for double checking this. Also I think we would change the subject "cmake fails on missing rcc" because it's failure in doing something, not overlook, it's a programmed behaviour with clear messages in English. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #21 from Martin Schnitkemper --- It's not solved for me. I have also not installed xf86-input-libinput on my desktop system but scrolling in the left folder- or places panel in dolphin is still unusable slow, in the main windows its OK. It seems new to me after upgrading to 16.08. Distribution is Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)
https://bugs.kde.org/show_bug.cgi?id=367639
--- Comment #42 from Thomas Schmitt ---
Hi,
> libk3b / projects / datacd / k3bdatamultisessionparameterjob.cpp
I hate to say it, but it looks like there is already handling
for growisofs multi-session on overwritable media in this source file.
Just a few lines above your code addition there is:
// FIXME: Does BD-RE really behave like DVD+RW here?
if( info.mediaType() & (K3b::Device::MEDIA_DVD_PLUS_RW|
K3b::Device::MEDIA_DVD_PLUS_RW_DL|
K3b::Device::MEDIA_DVD_RW_OVWR|
K3b::Device::MEDIA_BD_RE) ) {
It refers to DVD+RW, DVD+RW DL, overwritable DVD_RW, and BD-RE.
But it does not refer to pseudo-overwritable BD-R, which caused this
bug report. (Arrrghhh !!!)
It is quite likely that the fix for this bug is simply to add the
profile for pseudo-overwritable BD-R to the list.
libk3bdevice/k3bdevicetypes.h has it probably as MEDIA_BD_R_SRM_POW:
enum MediaType {
...
/** Writable Blu-ray Disc (BD-R) */
MEDIA_BD_R_SRM_POW = 0x200,
It could need a change from "Writable" to "Pseudo-Overwritable"
in its comment to distinguish it from unformatted MEDIA_BD_R_SRM.)
Except the occurence in setupMultiSessionParameters(), there is
another one in determineMultiSessionModeFromMedium(), where you
should add the MEDIA_BD_R_SRM_POW too.
Reasoning:
MEDIA_BD_R_SRM_POW gets recognized in libk3bdevice/k3bdevice.cpp line 1872
by
case 0x41: {
if( featureCurrent( FEATURE_BD_PSEUDO_OVERWRITE ) == 1 )
return MEDIA_BD_R_SRM_POW;
else
return MEDIA_BD_R_SRM;
The profile number 0x41 indicates BD-R which are not formatted to
Random Recording Mode (which is not used by growisofs).
libk3bdevice / k3bdevicetypes.h has
const unsigned short FEATURE_BD_PSEUDO_OVERWRITE = 0x038;
The MMC feature 0x38 indeed indicates Pseudo-Overwrite formatting on
profile 0x41. (MMC-5 5.3.28: BD-R Pseudo-Overwrite (POW) Feature.)
--
Darn. Your newest change really looks as if we were nearly there.
Error throwing was not sufficient yet. And when i looked for a code
example how to do it, i came to that list of overwritable profiles.
We should have first searched for the correct place in the program
architecture and only then have tried to implement it.
One never stops learning ...
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching all bug changes.
[kdeplasma-addons] [Bug 361870] mediaframe: Randomize items disabled but still randomized
https://bugs.kde.org/show_bug.cgi?id=361870 --- Comment #3 from Joachim --- Ahh, I found the root of the issue. It's not that the random setting gets ignored. The problem is that the files are not added to the list in alphabetical order, but for me it was in inverse creation order. I assume more precisely it's inverse whatever-order-the-filesystem-returns. So for directories that have seen lots of changes it could also be some order that appears random. But as long as nobody touches that directory it will always be the same. I can see the use of reading the files in alphabetical order. Would be nice to have. But that makes it a bit more difficult. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 369277] New: LessCSS syntax problem
https://bugs.kde.org/show_bug.cgi?id=369277
Bug ID: 369277
Summary: LessCSS syntax problem
Product: kate
Version: Git
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: syntax
Assignee: kwrite-bugs-n...@kde.org
Reporter: jtam...@gmail.com
this simple css is not well parsed with the LESSCSS syntax after
@screen-sm-min. It is well parsed with CSS or CleanCSS (for example).
.nav-justified {
width: 100%;
@media (min-width: @screen-sm-min) {
> li {
display: table-cell;
}
}
}
Reproducible: Always
Steps to Reproduce:
create a new blank document, paste the css code and select the syntax.
Actual Results:
@screen-sm-min) {
> li {
display: table-cell;
}
}
}
is underlined and in red
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 369218] Icon location on Desktop is not kept during reboot / shutdown
https://bugs.kde.org/show_bug.cgi?id=369218 Eike Hein changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Eike Hein --- Do you notice anything unusual during/after login like a screen resolution change? -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 369278] New: debugger toolbar should remain put where user left it (and maintain its visibility)
https://bugs.kde.org/show_bug.cgi?id=369278 Bug ID: 369278 Summary: debugger toolbar should remain put where user left it (and maintain its visibility) Product: kdevplatform Version: git master Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com CC: niko.s...@gmail.com The debugger toolbar has the nasty habit of reverting to its default location, and reappearing in views where it's supposed to be hidden Reproducible: Sometimes Steps to Reproduce: 1. Put the debugger toolbar where you want it to be, possibly hiding it in the standard code view 2. Quit the session 3. Reopen the session, possibly after having opened other sessions or with another session open that has been kept open. Actual Results: The debugger toolbar may or may not restore its previous location and visibility. Expected Results: The debugger toolbar reappears where it was told to be, and remains hidden if it was told so. Locking the toolbars has no effect whatsoever contrary to what one might expect. The "reset" appears to be triggered when anything else in the overall windowstate changed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369279] New: plasma crashes when quitting chromium
https://bugs.kde.org/show_bug.cgi?id=369279 Bug ID: 369279 Summary: plasma crashes when quitting chromium Product: plasmashell Version: 5.7.4 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: arthur.ma...@internode.on.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.7.4) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.8.0-rc7+ x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: when I quit chromium previously the panel disappeared and reappeared but on this occasion when I quit chromium plasma crashed and I had the option to report the bug. The crash can be reproduced sometimes. -- 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 0x7f9c7ac857c0 (LWP 4075))] Thread 9 (Thread 0x7f9bd3fff700 (LWP 4266)): #0 0x003011d59832 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x003011ed90c9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x003011ed9675 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x003011edaa0e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x003003c49ed9 in g_main_context_prepare (context=context@entry=0x7f9bcc000990, priority=priority@entry=0x7f9bd3ffecc0) at ././glib/gmain.c:3499 #5 0x003003c4a8fb in g_main_context_iterate (context=context@entry=0x7f9bcc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3907 #6 0x003003c4aaec in g_main_context_iteration (context=0x7f9bcc000990, may_block=1) at ././glib/gmain.c:3988 #7 0x003011edb51b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x003011e8319a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x003011ca8e53 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x003011cadd78 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x003000c07464 in start_thread (arg=0x7f9bd3fff700) at pthread_create.c:333 #12 0x0030004e897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 8 (Thread 0x7f9bd885e700 (LWP 4265)): #0 0x003003c90009 in g_mutex_lock (mutex=mutex@entry=0x7f9bd4000990) at ././glib/gthread-posix.c:1336 #1 0x003003c4a121 in g_main_context_query (context=context@entry=0x7f9bd4000990, max_priority=2147483647, timeout=timeout@entry=0x7f9bd885dca4, fds=fds@entry=0x7f9bd40013c0, n_fds=n_fds@entry=1) at ././glib/gmain.c:3604 #2 0x003003c4a948 in g_main_context_iterate (context=context@entry=0x7f9bd4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909 #3 0x003003c4aaec in g_main_context_iteration (context=0x7f9bd4000990, may_block=1) at ././glib/gmain.c:3988 #4 0x003011edb51b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x003011e8319a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x003011ca8e53 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9bd88b1b45 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #8 0x003011cadd78 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x003000c07464 in start_thread (arg=0x7f9bd885e700) at pthread_create.c:333 #10 0x0030004e897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7f9c65b40700 (LWP 4224)): #0 0x003000c0d18f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9c66622493 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f9c66621bd7 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x003000c07464 in start_thread (arg=0x7f9c65b40700) at pthread_create.c:333 #4 0x0030004e897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7f9c67df7700 (LWP 4223)): #0 0x003000c0d18f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x003061f7c574 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x003061f7c5b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x003000c07464 in start_thread (arg=0x7f9c67df7700) at pthread_create.c:333 #4 0x0030004e897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f9c7197b700 (LWP 4214)): #0 0x0030004db57d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x003003c
[plasmashell] [Bug 369249] Copying/Moving a file onto itself in folderview crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=369249 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-desktop/c8d3546a9e3ea1df ||db1853a33172824e7ff46feb --- Comment #2 from David Edmundson --- Git commit c8d3546a9e3ea1dfdb1853a33172824e7ff46feb by David Edmundson, on behalf of Fabian Vogt. Committed on 24/09/2016 at 10:25. Pushed by davidedmundson into branch 'Plasma/5.8'. Set parent for folderview context menu actions This fixes a crash when a file action opens a window. Differential Revision: https://phabricator.kde.org/D2848 M +1-1containments/desktop/plugins/folder/foldermodel.cpp http://commits.kde.org/plasma-desktop/c8d3546a9e3ea1dfdb1853a33172824e7ff46feb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369280] New: krita crashes every 5 mins
https://bugs.kde.org/show_bug.cgi?id=369280 Bug ID: 369280 Summary: krita crashes every 5 mins Product: krita Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: shrinidhi...@gmail.com Please help here. We are trying to use Krita in our studio and its giving problems like crazy . crashing randomly every 5 - 10 mins . Artists are feeling very uncomfortable . This is the outputs in the log files everytime krita crashes Sep 24 15:54:55 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:54:57 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:54:57 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:54:57 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:54:57 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:01 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:07 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:55:07 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:55:07 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:55:07 localhost krita[16507]: QObject::connect: invalid null parameter Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost krita[16507]: QCursor: Cannot create bitmap cursor; invalid bitmap(s) Sep 24 15:55:10 localhost
[krita] [Bug 369280] krita crashes every 5 mins
https://bugs.kde.org/show_bug.cgi?id=369280 Shrinidhi Rao changed: What|Removed |Added CC||shrinidhi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342763] Crash In Task Manager Item Changed
https://bugs.kde.org/show_bug.cgi?id=342763 David Edmundson changed: What|Removed |Added CC||arthur.ma...@internode.on.n ||et --- Comment #239 from David Edmundson --- *** Bug 369279 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369279] plasma crashes when quitting chromium
https://bugs.kde.org/show_bug.cgi?id=369279 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 342763 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369280] krita crashes every 5 mins
https://bugs.kde.org/show_bug.cgi?id=369280 --- Comment #1 from Shrinidhi Rao --- qt 5.7 plasma 5.8.90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369200] translation file for plasma_applet_kdeobservatory.pot is missing in svn repository
https://bugs.kde.org/show_bug.cgi?id=369200 --- Comment #6 from David Edmundson --- the giant translation bundles contain translations for all KDE software - including stuff that you happen to not be using. I don't understand what you think the problem is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368080] KInfoCenter is not included in the Computer Tab
https://bugs.kde.org/show_bug.cgi?id=368080 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364907] Crash with a SIGABT when importing many clips
https://bugs.kde.org/show_bug.cgi?id=364907 Benoit Touron changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Benoit Touron --- Seems fixed in the last version. Probably linked with the bug 367904 which gas been fixed. Changed to Fixed. Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369280] krita crashes every 5 mins
https://bugs.kde.org/show_bug.cgi?id=369280 --- Comment #2 from Shrinidhi Rao --- FYI : we also work in a hostile environment where the home directory and production storage are network based. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination for multithreaded process terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 Philippe Waroquiers changed: What|Removed |Added Summary|Inconsistent termination|Inconsistent termination |when an instrumented|for multithreaded process |multithreaded process is|terminated by signal |terminated by signal| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369281] New: Restore original default audio output device after it is available again
https://bugs.kde.org/show_bug.cgi?id=369281 Bug ID: 369281 Summary: Restore original default audio output device after it is available again Product: plasmashell Version: 5.7.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: codestr...@posteo.org CC: bhus...@gmail.com, plasma-b...@kde.org In the Audio Volume Settings under the tab "Output Devices" it is possible to set the default device. I have the following configuration: 1 laptop 1 dockingstation When the laptop is connected I set the default audio output device to soundcard of the dockingstation. When I disconnect the laptop the new default output device is the built-in soundcard. Wish: It would be nice if the laptop is reconnected again, the default output device is switch back to the original default. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 --- Comment #22 from Shlomi Fish --- Hi all, (In reply to Martin Schnitkemper from comment #21) > It's not solved for me. I have also not installed xf86-input-libinput on my > desktop system but scrolling in the left folder- or places panel in dolphin > is still unusable slow, in the main windows its OK. It seems new to me > after upgrading to 16.08. Distribution is Arch Linux. please see this Mageia bug - https://bugs.mageia.org/show_bug.cgi?id=19362 - scrolling is low in dolphin on non-Plasma5-desktops without libinput installed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369282] New: Taskbar crashes with auto-restart after vpn is started from system tray
https://bugs.kde.org/show_bug.cgi?id=369282 Bug ID: 369282 Summary: Taskbar crashes with auto-restart after vpn is started from system tray Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dgp...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-38-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I started a vpn through network conections in the system tray - Unusual behavior I noticed: The whole taskbar crashed - then to be auto-restarted (sometimes, rarely, it does not restart and a logout is needed to get the taskbar back). The crash can be reproduced every time. -- 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 0x7fc8814888c0 (LWP 2248))] Thread 8 (Thread 0x7fc7ba8d0700 (LWP 2272)): #0 0x7fc87bb98e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc87892e39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc87892e4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc87c4c5a9b in QEventDispatcherGlib::processEvents (this=0x7fc7b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fc87c46cdea in QEventLoop::exec (this=this@entry=0x7fc7ba8cfcc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fc87c2898a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fc7bcdae7d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7fc87c28e84e in QThreadPrivate::start (arg=0x4f27180) at thread/qthread_unix.cpp:331 #8 0x7fc87b37b6fa in start_thread (arg=0x7fc7ba8d0700) at pthread_create.c:333 #9 0x7fc87bba4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fc7cbfff700 (LWP 2257)): #0 0x7fc87892e31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc87892e4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc87c4c5a9b in QEventDispatcherGlib::processEvents (this=0x7fc7c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #3 0x7fc87c46cdea in QEventLoop::exec (this=this@entry=0x7fc7cbffec90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #4 0x7fc87c2898a4 in QThread::exec (this=this@entry=0x298e4b0) at thread/qthread.cpp:503 #5 0x7fc87f4b7ed6 in QQuickPixmapReader::run (this=0x298e4b0) at util/qquickpixmapcache.cpp:817 #6 0x7fc87c28e84e in QThreadPrivate::start (arg=0x298e4b0) at thread/qthread_unix.cpp:331 #7 0x7fc87b37b6fa in start_thread (arg=0x7fc7cbfff700) at pthread_create.c:333 #8 0x7fc87bba4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fc852fbc700 (LWP 2256)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc880ed6bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fc880ed6c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fc87b37b6fa in start_thread (arg=0x7fc852fbc700) at pthread_create.c:333 #4 0x7fc87bba4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fc858a81700 (LWP 2255)): #0 0x7fc878972ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc87892dddc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc87892e340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc87892e4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc87c4c5a9b in QEventDispatcherGlib::processEvents (this=0x7fc84c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fc87c46cdea in QEventLoop::exec (this=this@entry=0x7fc858a80ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fc87c2898a4 in QThread::exec (this=this@entry=0x27093e0) at thread/qthread.cpp:503 #7 0x7fc87eb313c5 in QQmlThreadPrivate::run (this=0x27093e0) at qml/ftw/qqmlthread.cpp:141 #8 0x7fc87c28e84e in QThreadPrivate::start (arg=0x27093e0) at thread/qthread_unix.cpp:331 #9 0x7fc87b37b6fa in start_thread (arg=0x7fc858a81700) at pthread_create.c:333 #10 0x7fc87bba4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fc85a909700 (LWP 2254)): #0 0x7fc87c4c4e1b in timerSourcePrepare (source=0x7fc854002c70, timeout=0x7fc85a908b24) at kernel/qeventdispatcher_glib.cpp
[valgrind] [Bug 361615] Inconsistent termination for multithreaded process terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 Philippe Waroquiers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #14 from Philippe Waroquiers --- Fixed in revision 15982. Note that the fix committed consists in calling VG_(reap_threads)(tid); after nuke all threads. Thanks for the bug report and the test case. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 361870] mediaframe: Randomize items disabled but still randomized
https://bugs.kde.org/show_bug.cgi?id=361870 --- Comment #4 from Joachim --- Created attachment 101255 --> https://bugs.kde.org/attachment.cgi?id=101255&action=edit sort contents of directories alphabetically Attached a patch that makes directory contents added alphabetically. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #92 from ghost53...@gmail.com --- I am waiting to Arch Linux to get 5.8, seems that 5.7.5 broke the multi screen again for my system. The panel also now won't move to another screen no matter what screen I set as the primary display. So it seems that the change to make the primary screen also the screen that the panel will display on, that commit has been undone by someone for some reason. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 ghost53...@gmail.com changed: What|Removed |Added CC||ghost53...@gmail.com --- Comment #6 from ghost53...@gmail.com --- I am having the same issue the panel is now always on the left most screen. There was a commit to make the panel go to the primary screen, it seems that has been undo for some reason. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 --- Comment #7 from ghost53...@gmail.com --- The issue was fixed for me until I updated to plasma 5.7.5 and that broke is again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369242] Services that can be executed are shown in Kicker with empty buttons
https://bugs.kde.org/show_bug.cgi?id=369242 Olivier Churlaud changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369242] Services that can be executed are shown in Kicker with empty buttons
https://bugs.kde.org/show_bug.cgi?id=369242 --- Comment #3 from Olivier Churlaud --- Fixed in http://commits.kde.org/plasma-desktop/5c966a42554fc0db374326b5fcdeb03e30d6cd6e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369282] Taskbar crashes with auto-restart after vpn is started from system tray
https://bugs.kde.org/show_bug.cgi?id=369282 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||dgp...@gmail.com --- Comment #162 from David Edmundson --- *** Bug 369282 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369267] Blank shortcuts for recent settings-actions in dashboard
https://bugs.kde.org/show_bug.cgi?id=369267 Olivier Churlaud changed: What|Removed |Added CC||oliv...@churlaud.com Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Olivier Churlaud --- Should be fixed with http://commits.kde.org/plasma-desktop/5c966a42554fc0db374326b5fcdeb03e30d6cd6e Feel free to reopen if not. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 365963] Try to take the screenshot ASAP on startup
https://bugs.kde.org/show_bug.cgi?id=365963 tesfab...@gmail.com changed: What|Removed |Added CC||tesfab...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 369259] Regression: owncloud account creation wizard uses 'dav' instead of 'caldav' and 'carddar' in URL completion
https://bugs.kde.org/show_bug.cgi?id=369259 --- Comment #3 from Achim Bohnet --- Hi Laurent, I used the 'owncloud' entry in the account wizard (not the owncloud < 5). Owncloud server is running v8.* -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043 skywatche...@hotmail.fr changed: What|Removed |Added CC||skywatche...@hotmail.fr --- Comment #42 from skywatche...@hotmail.fr --- I'm having this very problem on Kubuntu 16.04 since today's update... (I just have one screen.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342763] Crash In Task Manager Item Changed
https://bugs.kde.org/show_bug.cgi?id=342763 --- Comment #240 from Luís Henrique Camargo Quiroz --- (In reply to Thomas Weinhold from comment #234) > I found something out: There seem to be a relationship to the "Windowlist" > widget (in german it is "Fensterliste" so i guess it is "Windowlist" or > "Tasklist" in english). > When I place this widget on my desktop or in one of my taskbars I have the > crash problem. If I remove it, also the crash problem is not present anymore. > > Can anyone reproduce this? Yes sir!I removed my "lista de janelas" (portuguese) (window list) and my desktop became stable! I just reinstalled it, after about two weeks without, just to see if the problems reappear... I think they will :( -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 369259] Regression: owncloud account creation wizard uses 'dav' instead of 'caldav' and 'carddar' in URL completion
https://bugs.kde.org/show_bug.cgi?id=369259 --- Comment #4 from Laurent Montel --- so you need to use entry in wizard named "owncloud between 6 and 9 ?" -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369283] New: Ark crash when I close it
https://bugs.kde.org/show_bug.cgi?id=369283 Bug ID: 369283 Summary: Ark crash when I close it Product: ark Version: 16.08.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: mustafa10...@gmail.com CC: rak...@freebsd.org, rthoms...@gmail.com Application: ark (16.08.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.21-2-default x86_64 Distribution: "openSUSE Leap 42.2 Beta" -- Information about the crash: - What I was doing when the application crashed: I opened an rpm package, while it was loading, I closed ark and it crashed, tried several times, happen every time. The crash can be reproduced every time. -- Backtrace: Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f842728d880 (LWP 18060))] Thread 4 (Thread 0x7f8408a81700 (LWP 18063)): [KCrash Handler] #6 0x7f8423d6c494 in QObjectPrivate::isSignalConnected (signal_index=4, this=0x4545454545454545) at kernel/qobject_p.h:250 #7 QMetaObject::activate (sender=sender@entry=0xd9e210, signalOffset=3, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7f8408a80c50) at kernel/qobject.cpp:3605 #8 0x7f8423d6c6f7 in QMetaObject::activate (sender=sender@entry=0xd9e210, m=m@entry=0x7f84270b9860 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7f8408a80c50) at kernel/qobject.cpp:3595 #9 0x7f8426e9f90a in Kerfuffle::ReadOnlyArchiveInterface::error (this=this@entry=0xd9e210, _t1=..., _t2=...) at /usr/src/debug/ark-16.08.0/build/kerfuffle/moc_archiveinterface.cpp:234 #10 0x7f840909c892 in LibarchivePlugin::list (this=0xd9e210) at /usr/src/debug/ark-16.08.0/plugins/libarchive/libarchiveplugin.cpp:112 #11 0x7f8426e703ba in Kerfuffle::ListJob::doWork (this=0xd2b9b0) at /usr/src/debug/ark-16.08.0/kerfuffle/jobs.cpp:211 #12 0x7f8426e6e821 in Kerfuffle::Job::Private::run (this=0xd9cfb0) at /usr/src/debug/ark-16.08.0/kerfuffle/jobs.cpp:62 #13 0x7f8423b7f9e9 in QThreadPrivate::start (arg=0xd9cfb0) at thread/qthread_unix.cpp:341 #14 0x7f841f8a1734 in start_thread () from /lib64/libpthread.so.0 #15 0x7f8423493d3d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8410126700 (LWP 18062)): #0 0x7f842348b49d in poll () from /lib64/libc.so.6 #1 0x7f841f16d314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f841f16d42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8423d9230b in QEventDispatcherGlib::processEvents (this=0xaf0e80, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f8423d3ffbb in QEventLoop::exec (this=this@entry=0x7f8410125d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f8423b7af1a in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f84211e21d5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f8423b7f9e9 in QThreadPrivate::start (arg=0x7f842144ace0) at thread/qthread_unix.cpp:341 #8 0x7f841f8a1734 in start_thread () from /lib64/libpthread.so.0 #9 0x7f8423493d3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f84143bd700 (LWP 18061)): #0 0x7f842348b49d in poll () from /lib64/libc.so.6 #1 0x7f841ca233e2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f841ca24fcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f8416917529 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f8423b7f9e9 in QThreadPrivate::start (arg=0xaa2640) at thread/qthread_unix.cpp:341 #5 0x7f841f8a1734 in start_thread () from /lib64/libpthread.so.0 #6 0x7f8423493d3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f842728d880 (LWP 18060)): #0 0x7f841f8a60af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8423b8065b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xd9cb00) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=this@entry=0xd9c620, mutex=mutex@entry=0xd9c600, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f8423b7f5e6 in QThread::wait (this=, time=time@entry=18446744073709551615) at thread/qthread_unix.cpp:672 #4 0x7f8426e6e050 in Kerfuffle::Job::~Job (this=0xd2b9b0, __in_chrg=) at /usr/src/debug/ark-16.08.0/kerfuffle/jobs.cpp:91 #5 0x7f8426ea2314 in Kerfuffle::ListJob::~ListJob (this=0xd2b9b0, __in_chrg=) at /usr/src/debug/ark-16.08.0/kerfuffle/jobs.h:92 #6 Kerfuffle::ListJob::~ListJob (this=0xd2b9b0, __in_chrg=) at /usr/src/debug/ark-16.08.0/kerfuffle/jobs.h:92 #7 0x7f8423d6d190 in QObject::event (this=0xd2b9b0, e=) at kernel/qobject.cpp:1247 #8 0x7f8424a48e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widget
[plasmashell] [Bug 369218] Icon location on Desktop is not kept during reboot / shutdown
https://bugs.kde.org/show_bug.cgi?id=369218 --- Comment #2 from Jón Frímann --- There is no change in screen resolution. I was checking a other problem that was making kactivitymanager crash (Bug 348194). One of the solution (comment 27) suggested there was that I deleted the following directories. ~/.local/share/kactivitymanagerd/resources/database and ~/.local/share/kscreen/* After deleting those databases and folders the icons did go into mess, but after moving them around as I wanted they have stayed on the correct location since. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)
https://bugs.kde.org/show_bug.cgi?id=367639
--- Comment #43 from Thomas Schmitt ---
Hi,
Surprise: growisofs does not inspect the ISO with BD-R profile 0x41 !
So adding MEDIA_BD_R_SRM_POW will not be correct.
Do Not Commit, Please.
I rather see in growisofs_mmc.cpp a special handling for pseudo-overwritable
BD-R which i did not remember to have seen in the SCSI MMC related code
of K3B:
cmd[0] = 0x52; // READ TRACK INFORMATION
cmd[1] = 1;
cmd[4] = next_track>>8;
cmd[5] = next_track;// ask for last track
cmd[8] = sizeof(buf);
cmd[9] = 0;
err = cmd.transport (READ,buf,sizeof(buf));
...
if (mmc_profile==0x41 && bdr_plus_pow && buf[7]&1) // NWA_V
{ next_session = buf[12]<<24;
next_session |= buf[13]<<16;
next_session |= buf[14]<<8;
next_session |= buf[15];
}
else
{ next_session = buf[8]<<24; // Track Start Address
next_session |= buf[9]<<16;
next_session |= buf[10]<<8;
next_session |= buf[11];
}
The first case is for what K3B recognizes as MEDIA_BD_R_SRM_POW.
I will now revisit the code of K3B which asks the drive for the
Next Writable Address.
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching all bug changes.
[kaddressbook] [Bug 369259] Regression: owncloud account creation wizard uses 'dav' instead of 'caldav' and 'carddar' in URL completion
https://bugs.kde.org/show_bug.cgi?id=369259 Achim Bohnet changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from Achim Bohnet --- Oh. oh. oh. That works. Brown paper bag bug report :-(.I'm so used to select 'owncloud' that I never read further down the list. Sorry for wasting your time. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)
https://bugs.kde.org/show_bug.cgi?id=362038 --- Comment #5 from Ahmed Hussein --- Sorry, It just work Friday and Saturday. While I was working on this project I use Shell project as start project and parse argument to get search string. Then I pass QString to Shell::openDocument - I override openDocument to take two arguments. Now I want to pass search text to Okular::Document after opening url. I am stuck here. Should I access Okular::part using singal same as "enableStartWithPrint" then use m_document or that is wrong?! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368565] G'Mic does not work in Krita 3.0.1 Win10. Error "No display available".
https://bugs.kde.org/show_bug.cgi?id=368565 Louis Mcarvy changed: What|Removed |Added CC||louis.mca...@yahoo.com --- Comment #4 from Louis Mcarvy --- When going in to G'mic, I get the same problem as well as a visual error, when I got to Filter, G'mic, Black and white, the input time for B&W Photograph says "B&W photograph" I think it may have to do with the problem but I am not sure. I'm very new to this and I love using Krita, I hope to get it fixed soon. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)
https://bugs.kde.org/show_bug.cgi?id=362038 --- Comment #6 from nicholas --- sorry, all this framework stuff outside of my scope of expertise. On 24 September 2016 at 15:00, Ahmed Hussein via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=362038 > > --- Comment #5 from Ahmed Hussein --- > Sorry, It just work Friday and Saturday. While I was working on this project I > use Shell project as start project and parse argument to get search string. > Then I pass QString to Shell::openDocument - I override openDocument to take > two arguments. Now I want to pass search text to Okular::Document after > opening > url. I am stuck here. Should I access Okular::part using singal same as > "enableStartWithPrint" then use m_document or that is wrong?! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)
https://bugs.kde.org/show_bug.cgi?id=362038 --- Comment #7 from Ahmed Hussein --- Could you recommend someone to help me?! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)
https://bugs.kde.org/show_bug.cgi?id=367639
--- Comment #44 from Thomas Schmitt ---
Hi,
libk3bdevice/k3bdevice.cpp , K3b::Device::Device::getNextWritableAdress()
has
// Read start address of the incomplete track
if( readTrackInformation( trackData, 0x1, nextTrack ) ) {
nextWritableAdress = from4Byte( &trackData[8] );
which matches the else-case of growisofs_mmc.cpp
cmd[0] = 0x52; // READ TRACK INFORMATION
...
if (mmc_profile==0x41 && bdr_plus_pow && buf[7]&1) // NWA_V
{ next_session = buf[12]<<24;
next_session |= buf[13]<<16;
next_session |= buf[14]<<8;
next_session |= buf[15];
}
else
{ next_session = buf[8]<<24; // Track Start Address
next_session |= buf[9]<<16;
next_session |= buf[10]<<8;
next_session |= buf[11];
}
There is no counterpart for the bdr_plus_pow case.
In K3B the equivalent would have to look like
// Read start address of the incomplete track
if( readTrackInformation( trackData, 0x1, nextTrack ) ) {
if (m == MEDIA_BD_R_SRM_POW && (trackData[7] & 1))
nextWritableAdress = from4Byte( &trackData[12] );
else
nextWritableAdress = from4Byte( &trackData[8] );
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 362823] Message List Panel Missing (5.2.0)
https://bugs.kde.org/show_bug.cgi?id=362823 Achim Bohnet changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||a...@mpe.mpg.de --- Comment #1 from Achim Bohnet --- Same with kmail 5.3 (neon dev stable): Reproduce: fresh user, 1st kmail startup & 1st IMAP Accout setup ==> No message view (and mail message view) is shown (see screenshot) . Changing folders does not help. Workaround the 1st usage bug: Menu: Go -> Next message ==> and the message list view and mail message view show up. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362823] Message List Panel Missing (5.2.0 & 5.3.0)
https://bugs.kde.org/show_bug.cgi?id=362823 Achim Bohnet changed: What|Removed |Added Summary|Message List Panel Missing |Message List Panel Missing |(5.2.0) |(5.2.0 & 5.3.0) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362823] Message List Panel Missing (5.2.0 & 5.3.0)
https://bugs.kde.org/show_bug.cgi?id=362823 --- Comment #2 from Achim Bohnet --- Created attachment 101256 --> https://bugs.kde.org/attachment.cgi?id=101256&action=edit Unexpected: Main window after 1st start of kmail and 1st imap account creation -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362823] Message List Panel Missing (5.2.0 & 5.3.0)
https://bugs.kde.org/show_bug.cgi?id=362823 --- Comment #3 from Achim Bohnet --- Comment on attachment 101256 --> https://bugs.kde.org/attachment.cgi?id=101256 Unexpected: Main window after 1st start of kmail and 1st imap account creation I would expect, that when one selects a folder on the left, the message list view and the mail message view are shown -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)
https://bugs.kde.org/show_bug.cgi?id=362038 Yuri Chornoivan changed: What|Removed |Added CC||yurc...@ukr.net --- Comment #8 from Yuri Chornoivan --- (In reply to Ahmed Hussein from comment #7) > Could you recommend someone to help me?! The replies to this bug report are in the okular-devel@ mailing list. So all current developers are informed about this question. Just wait until somebody of them answer it. There are also IRC channels on freenode, #okular and #kde-devel to discuss development questions. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)
https://bugs.kde.org/show_bug.cgi?id=362038 --- Comment #9 from Ahmed Hussein --- Thank you, I will wait. I ask that question at IRC yesterday and today and no answer :D -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369217] G'mic Colorize[interactive] crashes
https://bugs.kde.org/show_bug.cgi?id=369217 Louis Mcarvy changed: What|Removed |Added CC||louis.mca...@yahoo.com --- Comment #1 from Louis Mcarvy --- I've been getting a similar problem, I also seem to have a problem with the B&W Photograph, it's been completely jumbled up saying "B&W photograph." I'm wondering if anyone else is getting a similar problem. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 369284] New: blank screen at program start
https://bugs.kde.org/show_bug.cgi?id=369284 Bug ID: 369284 Summary: blank screen at program start Product: ktouch Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: sebastiangottfr...@web.de Reporter: gr...@gmx.de When i try to start KTouch, it opens a blank window (headline says either “ktouch“ or “typewriting trainer“). >From researching this bug, some users have claimed that installing the package qtdeclarative4-kqtquickcharts-1 solved the problem. But both this package and ktouch itself are on the newest version. Reproducible: Always Steps to Reproduce: 1. open ktouch 2. wait 3. nope, it's really a blank screen. Actual Results: blank screen. Expected Results: show me the ktouch program Linux Mint 17.2 rafaela Linux 3.16.0-38-generic x86_64 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369285] New: I want to close the icons of upload manager showing on the bottom
https://bugs.kde.org/show_bug.cgi?id=369285 Bug ID: 369285 Summary: I want to close the icons of upload manager showing on the bottom Product: dolphin Version: 15.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: robledo...@yahoo.com I want to close the icons of upload manager showing on the bottom Reproducible: Always Actual Results: nothing, how to clear it. Takes up space Expected Results: clear scape -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 --- Comment #4 from Michael --- Any news here? Facing the same problem (same with akregator) Version kmail2 5.3.0 (QtWebEngine) KDE Frameworks 5.26.0 Qt 5.6.1 (kompiliert gegen 5.6.1) Fedora 24 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369283] Ark crash when I close it
https://bugs.kde.org/show_bug.cgi?id=369283 --- Comment #1 from Elvis Angelaccio --- I think I know where the problem is, but I cannot reproduce the crash so I cannot test the fix. How big was the RPM archive? Does it crash if you try with a big tar.gz file? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369286] New: dolphin 16.08.1's Mousewheel scrolling is very small at all settings in non-Plasma5-desktops (regression from 16.04)
https://bugs.kde.org/show_bug.cgi?id=369286 Bug ID: 369286 Summary: dolphin 16.08.1's Mousewheel scrolling is very small at all settings in non-Plasma5-desktops (regression from 16.04) Product: dolphin Version: unspecified Platform: Mageia RPMs URL: https://bugs.mageia.org/show_bug.cgi?id=19362 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: shlo...@shlomifish.org When I'm using dolphin in detailed view in JWM or Xfce, then the mousewheel scrolling is small regardless of the systemsettings5 setting for number of lines to scroll. This is fine in the Plasma5 desktop. It also happens in a new user. This is not working in dolphin 16.08.1 and is fine in a dolphin 16.04.3 package that I built from an old svn checkout Reproducible: Always Steps to Reproduce: 1. New user. 2. startx as JWM or Xfce (non-plasma5). 3. start dolphin in detailed files mode. 4. scroll using the mousewheel. Actual Results: The scrolling does not scroll a lot. Expected Results: The scrolling should be more substantial. I'm on Mageia x86-64 v6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342763] Crash In Task Manager Item Changed
https://bugs.kde.org/show_bug.cgi?id=342763 --- Comment #241 from Juan J. Magaña --- Exactly the same for me. No window list, no crashes at all. With window list, random crashes when closing some windows/tasks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...
https://bugs.kde.org/show_bug.cgi?id=356098 wizard10...@gmail.com changed: What|Removed |Added CC||wizard10...@gmail.com --- Comment #12 from wizard10...@gmail.com --- I'm removing them with a nightly cron job but they are annoying. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...
https://bugs.kde.org/show_bug.cgi?id=356098 --- Comment #13 from wizard10...@gmail.com --- Also, can confirm on KDE 5.7.4 w/frameworks 5.25.0 on Debian Unstable. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 369287] New: Help text for rectangular region mode appears in between dual monitors.
https://bugs.kde.org/show_bug.cgi?id=369287 Bug ID: 369287 Summary: Help text for rectangular region mode appears in between dual monitors. Product: Spectacle Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: masonj...@gmail.com When taking a screenshot with the Rectangular Region option using two monitors, the help text appears in between both monitors which looks really odd. Image of the bug: http://imgur.com/OLZohXE Reproducible: Always Steps to Reproduce: 1. Have two monitors setup 2. Set capture mode area to Rectangular Region 3. Click Take a New Screenshot Possible fixes: 1. Display the help text centered over the primary monitor only 2. Display the help text centered over all monitors 3. Display the help text on the center of the currently moused over monitor. Personally I like option 3. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 369247] Kontact 5.3.1: settings between Kontact and components (e.g. KMail) are not synchronized
https://bugs.kde.org/show_bug.cgi?id=369247 --- Comment #2 from Till Schäfer --- sure, this is the example where I observed it first: 1. goto Settings -> Configure KMail -> Composer -> "Reply and forward using HTML if present" and change the setting to enabeld (lets assume it was disabled and we have enabled it now / it also works vice versa) and press OK. 2. goto Settings -> Configure Kontact -> Mail -> Composer -> "Reply and forward using HTML if present". The setting is still disabled. I have observed, that this is one way only. I.e. you need to change the components setting first and check the kontact setting afterwards. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 Till Schäfer changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #8 from Till Schäfer --- today i also observed the bug again. therefore, the new nvidia-driver does not fix the problem, but makes it less likely. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 Till Schäfer changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369283] Ark crash when I close it
https://bugs.kde.org/show_bug.cgi?id=369283 --- Comment #2 from Elvis Angelaccio --- Created attachment 101257 --> https://bugs.kde.org/attachment.cgi?id=101257&action=edit Possible fix -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 325513] Always offline after KDE start
https://bugs.kde.org/show_bug.cgi?id=325513 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] New: hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 Bug ID: 369288 Summary: hfsplus-tools commands renamed in some distributions Product: partitionmanager Version: 2.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it After the switch to hfsplus-tools in bug #364233 I realized that Fedora renames the standard hfsplus-tools executables. Specifically, newfs_hfs is renamed to mkfs.hfsplus and fsck_hfs is renamed to fsck.hfsplus I've opened a request in Fedora bugzilla for using symlinks instead of renaming executables, but I then realized that other distributions like Ubuntu and Debian are using mkfs.hfsplus and fsck.hfsplus commands, so maybe would be better if partitionmanager checks if those commands are present in the system and uses those instead of native names? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 Andrius Štikonas changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Andrius Štikonas --- Yeah, I think I'll switch it so symlinks. I also didn't realize that other distributions just rename executables instead of using symlinks. Thanks for the report. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 --- Comment #23 from Rindert Vonk --- (In reply to Shlomi Fish from comment #22) > Hi all, > > (In reply to Martin Schnitkemper from comment #21) > > It's not solved for me. I have also not installed xf86-input-libinput on my > > desktop system but scrolling in the left folder- or places panel in dolphin > > is still unusable slow, in the main windows its OK. It seems new to me > > after upgrading to 16.08. Distribution is Arch Linux. > > please see this Mageia bug - https://bugs.mageia.org/show_bug.cgi?id=19362 - > scrolling is low in dolphin on non-Plasma5-desktops without libinput > installed. I have the same problem as Martin. I'm also using arch distro as well. libinput is installed (it is a qt5-base dependency). But I have not installed xf86-input-libinput. I'm using dolphin inside plasma-5 desktop, kde applications and kde frameworks (KDE is default at my system). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 --- Comment #2 from Andrius Štikonas --- Do you think make sense to switch HFS to the same utilities away from hfsutils? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369286] dolphin 16.08.1's Mousewheel scrolling is very small at all settings in non-Plasma5-desktops (regression from 16.04)
https://bugs.kde.org/show_bug.cgi?id=369286 --- Comment #1 from Shlomi Fish --- According to git bisect: << 8d61c9c7b6f5a97803bf154529b413ee69bc2a1c is the first bad commit commit 8d61c9c7b6f5a97803bf154529b413ee69bc2a1c Author: Martin T. H. Sandsmark Date: Wed Jul 13 00:29:15 2016 +0200 Fix scrolling on hidpi screens Scrolling with libinput was unbearably slow. QScrollBar is much better at scrolling than us, so let it handle it. REVIEW: 128432 BUG: 357618 :04 04 356cc733e7cfb01d864d645b63919fe8beccce03 33b98e096f14a4ca83ff3ab5640aba301cf014a6 M src shlomif@telaviv1:~/Download/unpack/kde/dolphin/dolphin$ > -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||http://commits.kde.org/kpmc ||ore/aa5daf03786a3eb2a8ca783 ||868f2d2ddd869e1ac --- Comment #3 from Andrius Štikonas --- Git commit aa5daf03786a3eb2a8ca783868f2d2ddd869e1ac by Andrius Štikonas. Committed on 24/09/2016 at 16:10. Pushed by stikonas into branch 'master'. Use symlinks to hfsplus (diskdev_cmds) commands. Some distributions rename those commands to mkfs.hfsplus and fsck.hfsplus. M +2-2src/fs/hfsplus.cpp http://commits.kde.org/kpmcore/aa5daf03786a3eb2a8ca783868f2d2ddd869e1ac -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 --- Comment #4 from Mattia --- (In reply to Andrius Štikonas from comment #2) > Do you think make sense to switch HFS to the same utilities away from > hfsutils? I don't know if hfsplus-tools can handle HFS too. I don't personally use HFS or HFS+. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 354865] "Eye" and "Blank" symbols appear superimposed
https://bugs.kde.org/show_bug.cgi?id=354865 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Elvis Angelaccio --- This was a bug in QLineEdit which was fixed in 5.6.x, closing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 368899] .desktop starter containing cmdline won't be executed anymore
https://bugs.kde.org/show_bug.cgi?id=368899 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #3 from Wolfgang Bauer --- Should be fixed by https://quickgit.kde.org/?p=kio.git&a=commit&h=c784a879eaba0babc6274bc32e761772add3d4f8, I suppose. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added
https://bugs.kde.org/show_bug.cgi?id=369172 --- Comment #5 from Michał Dybczak --- I'm using Manjaro KDE with newest plasma 5.7.5 Here is mine info about the crash (probably repetition of the report above): Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f474ebb2800 (LWP 844))] Thread 10 (Thread 0x7f46527fb700 (LWP 3263)): #0 0x7f47435d3f84 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f474358f5ac in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7f474358ff8b in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f474359017c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f4748be659b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f4748b900da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f47489b30f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f474bd15445 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7f47489b7d78 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f4747ac7454 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f47482cd7df in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f4677f64700 (LWP 1195)): #0 0x7f474358fa8c in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #1 0x7f4743590004 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f474359017c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f4748be659b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f4748b900da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f47489b30f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f47489b7d78 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f4747ac7454 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f47482cd7df in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f4689778700 (LWP 968)): #0 0x7f474358f5a0 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #1 0x7f474358ff8b in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f474359017c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f4748be659b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f4748b900da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f47489b30f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f468bc9d0a7 in KCupsConnection::run() () from /usr/lib/libkcupslib.so #7 0x7f47489b7d78 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f4747ac7454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f47482cd7df in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f469600c700 (LWP 872)): #0 0x7ffc0fbf1959 in ?? () #1 0x7ffc0fbf1c2d in clock_gettime () #2 0x7f47482da6b6 in clock_gettime () from /usr/lib/libc.so.6 #3 0x7f4748a5d191 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f4748be4239 in QTimerInfoList::updateCurrentTime() () from /usr/lib/libQt5Core.so.5 #5 0x7f4748be47e5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/libQt5Core.so.5 #6 0x7f4748be5b6e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f474358f5b9 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #8 0x7f474358ff8b in ?? () from /usr/lib/libglib-2.0.so.0 #9 0x7f474359017c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #10 0x7f4748be659b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #11 0x7f4748b900da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #12 0x7f47489b30f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #13 0x7f474c8b48a6 in ?? () from /usr/lib/libQt5Quick.so.5 #14 0x7f47489b7d78 in ?? () from /usr/lib/libQt5Core.so.5 #15 0x7f4747ac7454 in start_thread () from /usr/lib/libpthread.so.0 #16 0x7f47482cd7df in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f4725370700 (LWP 871)): #0 0x7f4747acd10f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f474e347ac4 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f474e347b09 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f4747ac7454 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f47482cd7df in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f472704d700 (LWP 870)): #0 0x7f47489aef49 in QMutex::lock() () from /usr/lib/libQt5Core.so.5 #1 0x7f4748be5d0f in ?? () from /usr/lib/libQt5Core.so.5 #2 0x7f474358f5b9 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #3 0x7f474358ff8b in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f474359017c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f4748be659b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f4748b900da in QEventLoop::
[kipiplugins] [Bug 369289] New: dngconverter crashes when converting Olympus (.ORF) files
https://bugs.kde.org/show_bug.cgi?id=369289 Bug ID: 369289 Summary: dngconverter crashes when converting Olympus (.ORF) files Product: kipiplugins Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kde-imag...@kde.org Reporter: arzi...@gmail.com Application: dngconverter (4.12.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-38-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Crash happens after pushing "Convert" in the GUI with one or more files loaded in the window. This is on Xubuntu (dngconverter is the only KDE installed program. Xubuntu installer has also installed prereq libraries and other stuff). The crash can be reproduced every time. -- Backtrace: Application: DNG Image Converter (dngconverter), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1942e32980 (LWP 9965))] Thread 8 (Thread 0x7f1916d3a700 (LWP 9974)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #5 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f193ffe16fa in start_thread (arg=0x7f1916d3a700) at pthread_create.c:333 #7 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f191753b700 (LWP 9973)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #5 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f193ffe16fa in start_thread (arg=0x7f191753b700) at pthread_create.c:333 #7 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f1917d3c700 (LWP 9972)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f19421709bc in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f193ffe16fa in start_thread (arg=0x7f1917d3c700) at pthread_create.c:333 #8 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f192501e700 (LWP 9971)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f19421709bc in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f193ffe16fa in start_thread (arg=0x7f192501e700) at pthread_create.c:333 #8 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f192581f700 (LWP 9970)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f1942615a14 in KDcrawIface::RActionThreadBase::run() () from /usr/lib/libkdcraw.so.23 #3 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f193ffe16fa in start_thread (arg=0x7f192581f700) at pthread_create.c:333 #5 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f1926020700 (LWP 9969)): #0 __li
[kipiplugins] [Bug 367859] DNGConverter crashed after trying to nconvert CR2 file
https://bugs.kde.org/show_bug.cgi?id=367859 caulier.gil...@gmail.com changed: What|Removed |Added CC||arzi...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- *** Bug 369289 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 369289] dngconverter crashes when converting Olympus (.ORF) files
https://bugs.kde.org/show_bug.cgi?id=369289 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 367859 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368794] digiKam crashes with lossy dng image
https://bugs.kde.org/show_bug.cgi?id=368794 --- Comment #6 from caulier.gil...@gmail.com --- herb, Do you seen my previous comment ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369061] Expand clip hangs when producers cannot be loaded/relative resource paths in library clips
https://bugs.kde.org/show_bug.cgi?id=369061 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Wegwerf --- Jean-Baptiste, I've submitted a patch for my report: https://git.reviewboard.kde.org/r/129011/ -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 314239] mail body not displayed but on disk
https://bugs.kde.org/show_bug.cgi?id=314239 Denis Kurz changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Denis Kurz --- This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 275745] "KMail Folders: Cannot add email to folder trash because there is no email content"
https://bugs.kde.org/show_bug.cgi?id=275745 Denis Kurz changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Denis Kurz --- This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 335415] segfault when replying to mail
https://bugs.kde.org/show_bug.cgi?id=335415 Denis Kurz changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Denis Kurz --- This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311957] apply filter to remove messages from inbox and they are put back. I don't have keep messages selected.
https://bugs.kde.org/show_bug.cgi?id=311957 Denis Kurz changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Denis Kurz --- This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 303175] KMail and IMAP AOL: Unable to fetch item from backend
https://bugs.kde.org/show_bug.cgi?id=303175 Denis Kurz changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Denis Kurz --- This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. -- You are receiving this mail because: You are watching all bug changes.
