[umbrello] [Bug 381376] Umbrello doesn't honour paper size changes
https://bugs.kde.org/show_bug.cgi?id=381376 --- Comment #3 from David H. Gutteridge --- With "Version 2.35.2 (Applications 22.08.2)", this is different than before. I am now able to change the page size and it is reflected if I print immediately, where that did not work for me before. (The navigation to get to the feature is different now.) However, the reproduction steps I supplied still hold if "cancel" is selected instead. The document still retains the orientation change, but does not retain the paper size change. Not sure how significant one would consider that, but it is a little counterintuitive that one setting change would be retained and another one not. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 381376] Umbrello doesn't honour paper size changes
https://bugs.kde.org/show_bug.cgi?id=381376 David H. Gutteridge changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 381374] Boxes seemingly have an arbitrary size limit
https://bugs.kde.org/show_bug.cgi?id=381374 --- Comment #3 from David H. Gutteridge --- This is still reproducible with Umbrello Version 2.35.2 (Applications 22.08.2). Exactly the same as before. I can share a demonstration file, if need be (I would just have to remake it, as my real example I just re-tested with contains proprietary information). -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 381374] Boxes seemingly have an arbitrary size limit
https://bugs.kde.org/show_bug.cgi?id=381374 David H. Gutteridge changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 431767] New: Elisa crashes when I try to play a file directly
https://bugs.kde.org/show_bug.cgi?id=431767 Bug ID: 431767 Summary: Elisa crashes when I try to play a file directly Product: elisa Version: 20.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: shyd...@gmail.com Target Milestone: --- Application: elisa (20.12.1) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.4.0-62-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: Steps to replicate: 1) Open Elisa 2) Go to files 3) Click the Play button on a .mp3 / .ogg file Additional information: It seems Elisa cannot play files directly. i.e. navigate to Music folder in Dolphin and double-click a .mp3 file (correctly associated), Elisa opens up but instead of playing the file it just sits idle. Clicking the files after Elisa has been opened has no effect either. The crash can be reproduced every time. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [New LWP 1428] [New LWP 1429] [New LWP 1430] [New LWP 1431] [New LWP 1432] [New LWP 1433] [New LWP 1434] [New LWP 1436] [New LWP 1437] [New LWP 1438] [New LWP 1439] [New LWP 1440] [New LWP 1441] [New LWP 1442] [New LWP 1443] [New LWP 1444] [New LWP 1445] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f9d17478aff in __GI___poll (fds=0x7ffd8413fc68, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f9d12263180 (LWP 1427))] Thread 18 (Thread 0x7f9cb77fe700 (LWP 1445)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x555a702ebfe0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555a702ebf90, cond=0x555a702ebfb8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x555a702ebfb8, mutex=0x555a702ebf90) at pthread_cond_wait.c:638 #3 0x7f9d1780bd1b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9d1653f814 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f9d1653fc89 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f9d17805bac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9d15df4609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f9d17485293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f9cc7fff700 (LWP 1444)): #0 0x7f9d12d3a7a0 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #1 0x7f9d12d3d72b in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #2 0x7f9d12d3daea in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f9d12d3e37a in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #4 0x7f9d1546dba3 in pa_mainloop_dispatch () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f9d1546ded2 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f9d1546df70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f9d1547c11d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #8 0x7f9d12d4d72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #9 0x7f9d15df4609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f9d17485293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f9ce8ff9700 (LWP 1443)): #0 __GI___libc_read (nbytes=16, buf=0x7f9ce8ff8ad0, fd=26) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=26, buf=0x7f9ce8ff8ad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f9d1553689f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9d154edcfe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9d154ee152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9d154ee2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9d17a45fbb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9d179ea1ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9d17804a12 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f9d17805bac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9d15df4609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f9d17485293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f9ce97fa700 (LWP 1442)): #0 0x7f9d17478aff in __GI___poll (fds=0x7f9cc8005240, nfds=1, timeout=-1) at
[frameworks-solid] [Bug 379452] Plasma crash while searching for application from Application Launcher
https://bugs.kde.org/show_bug.cgi?id=379452 David H. Gutteridge changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 379452] Plasma crash while searching for application from Application Launcher
https://bugs.kde.org/show_bug.cgi?id=379452 --- Comment #8 from David H. Gutteridge --- I'm not able to reproduce this with Plasma 5.20.4 with Qt 5.15.1 and KDE Frameworks 5.75. I think it can be closed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 379452] Plasma crash while searching for application from Application Launcher
https://bugs.kde.org/show_bug.cgi?id=379452 David H. Gutteridge <dhgutteri...@hotmail.com> changed: What|Removed |Added Version|5.33.0 |5.38.0 --- Comment #6 from David H. Gutteridge <dhgutteri...@hotmail.com> --- This is still an issue for me with Plasma 5.10.5 with Qt 5.9.2 and KDE Frameworks 5.38. It just happened again; this time it brought down the Task Manager panel, which restored itself (albeit out of order) after around a minute. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 381376] New: Umbrello doesn't honour paper size changes
https://bugs.kde.org/show_bug.cgi?id=381376 Bug ID: 381376 Summary: Umbrello doesn't honour paper size changes Product: umbrello Version: 2.21.3 (KDE Applications 16.12.3) Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: dhgutteri...@hotmail.com Target Milestone: --- When trying to print a document on "US Legal" size paper rather than "US Letter", I'm simply unable to do so. Umbrello doesn't seem to honour or retain that setting, though it does retain a change from portrait to landscape orientation in the same print options widget. 1. Choose Print->Current Diagram->Properties. 2. Change Orientation to "Landscape". 3. Change Paper to "US Legal". 4. Print or click "Cancel". 5. In either case of 4, repeat step 1, and note that Orientation has persisted as "Landscape", while Paper has reverted to the default (with my settings) "US Letter". Note what prints is not what was selected. Same with PDF output. Both still end up as "US Letter". (I'm using 2.21.3, I can't comment on the 2.22 series, though I looked through the change logs and didn't see anything relevant listed.) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 381374] New: Boxes seemingly have an arbitrary size limit
https://bugs.kde.org/show_bug.cgi?id=381374 Bug ID: 381374 Summary: Boxes seemingly have an arbitrary size limit Product: umbrello Version: 2.21.3 (KDE Applications 16.12.3) Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: dhgutteri...@hotmail.com Target Milestone: --- When trying to expand a box around a large portion of a diagram, I've found it hits some sort of arbitrary limit and simply won't allow me to expand it any further. 1. Add box to a diagram that is fairly wide. (In my case, an activity diagram with eight concurrent sequences). 2. Click on the bottom right corner of the box to expand it. At a certain point, it simply won't expand any further. (In my case, I'm trying to put a box around five of the eight concurrent sequences. It won't expand beyond partway through the fourth sequence.) (I'm using 2.21.3, I can't comment on the 2.22 series, though I looked through the change logs and didn't see anything relevant listed.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 379452] Plasma crash while searching for application from Application Launcher
https://bugs.kde.org/show_bug.cgi?id=379452 David H. Gutteridge <dhgutteri...@hotmail.com> changed: What|Removed |Added Summary|Plasma crash while |Plasma crash while |searching for application |searching for application |from Application Lanucher |from Application Launcher -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379452] New: Plasma crash while searching for application from Application Lanucher
https://bugs.kde.org/show_bug.cgi?id=379452 Bug ID: 379452 Summary: Plasma crash while searching for application from Application Lanucher Product: plasmashell Version: 5.9.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dhgutteri...@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.10.13-200.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: While I was searching for an application using Application Launcher's search functionality, Plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9af048c3c0 (LWP 6638))] Thread 18 (Thread 0x7f9a00df1700 (LWP 10066)): #0 0x7f9afc68a460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9afdf4b04a in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f9a3ee48880 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #3 0x7f9a3ee4ca38 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7f9a3ee479fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f9a3ee4ca92 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f9a3ee479fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f9a3ee4a8c9 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #8 0x7f9afdf4a9ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f9afc6846ca in start_thread () from /lib64/libpthread.so.0 #10 0x7f9afd33df7f in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f9a015f2700 (LWP 10065)): #0 0x7f9afc68a460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9afdf4b04a in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f9a3ee48880 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #3 0x7f9a3ee4ca38 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7f9a3ee479fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f9a3ee4ca92 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f9a3ee479fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f9a3ee4ca92 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #8 0x7f9a3ee479fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #9 0x7f9a3ee4a8c9 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #10 0x7f9afdf4a9ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #11 0x7f9afc6846ca in start_thread () from /lib64/libpthread.so.0 #12 0x7f9afd33df7f in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f9a01df3700 (LWP 10064)): #0 0x7f9afc68a460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9afdf4b04a in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f9a3ee48880 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #3 0x7f9a3ee4ca38 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7f9a3ee479fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f9a3ee4ca92 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f9a3ee479fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f9a3ee4a8c9 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #8 0x7f9afdf4a9ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #239 from David H. <davinos...@gmail.com> --- Analogy time. Please bear with me, I promise that this is directly related to the bug report... Imagine you start a home business, and you set up a workshop in your garage to make or repair things. In that room you have a workbench, and on that bench you keep your various tools and working projects. Business is good, and you soon find yourself running out of space, so you set up a second bench near the first. And on it you have more tools, some of them being duplicates of those on the first bench, and others unique, so you can work on slightly different things. But you can also use the two benches in tandem when you have a really big project. Later on you add a third bench, and a fourth, and so on, to give you even more workspace. Now you also need an office to manage your business. That's in another room of your house. And in that room you have a desk with a computer, in/out-trays, pens and pencils, pads of paper, and other office supplies on it. As you become more successful you also put in a couple more tables, bookshelves, and cabinets and whatnot, each with its own collection of supplies, to help improve your productivity there too. In the rest of the house of course you also have a living area, with a TV, sofa, and various other facilities for relaxing, a kitchen/dining room for preparing food and eating it, a bedroom for sleeping, bathroom, whatever. Each room has its own purpose and its own unique set of accoutrements for fulfilling that purpose. And for the most part you keep each kind activity to its own space. You seldom, but not never, transfer what you're doing from one room to another. I hope you see where I'm going with this. Activities and Virtual Desktops, while being similar in many ways, are most definitely *not* the same thing. They categorize your work in different conceptual ways. Activities are like the various rooms, each focused *thematically* on a certain functional area. V.D.s are like the tables, benches, counters and other workspaces inside those rooms. They *spatially* organize the work you're doing and provide the actual tools with which to complete the various tasks within each area of activity. Now to apply this to the actual bug (and the proposed solutions and workarounds), I think most people are overlooking this foundational conceptual flaw that lies behind it -- the lack of recognition of the psychological separation between function space and work space, the differences in how we view them and react to them, and the differences in the work flows we set up within and between them. Activities and V.D.s perform complementary roles, not identical ones. Trying to replace or duplicate the one with the other is like saying four workshops with one bench each are basically the same thing as one workshop with four benches. They're not. Even if you put them right next to each other, cut doors between the rooms for easy access, and add pushcarts, conveyor belts, or whatever for the easy moving of projects between them, it's just never going to sit quite right in your mind or your behavior. You'd still be trying to fit a square peg into a round hole. Even worse, it could be seen as trying to put a workbench in your office, or an office desk in your workshop, or a toaster in your bathroom. Or say you do succeed in making the two experiences similar enough to not notice the difference. Then what was the point in changing it in the first place? Anyway, to my mind an ideal KDE set-up would provide the following: 1. The ability to set up one or more Activities, each of which can be centered around its own area of "business". 2. One or more Virtual Desktops inside each Activity, to provide the actual work areas in which to operate within that Activity's scope. 3. Full, individual, customizability of each Desktop inside each Activity, including... 3a. Setting the look and feel of each one so that it is clearly distinct from the others, the background being one of the most vital elements in creating that psychological, virtual "workspace". 3b. Individual customizability of the various widgets, toolbars and other features that populate each Desktop. 3c. The ability to set any single feature or tool as either unique to that Desktop or shared between all of them. Some features need to be always at hand, just as a workman might carry a toolbelt between workbenches with his most-used tools on it, while others can and should be confined to a certain workspace. 4. Multiple ways to quickly and easily navigate and move objects between Desktops, the ability to smoothly switch between Activities, and simple, but not necessarily as immediate, mechanisms for transferring and jumping to programs between Activities. Perhaps on occasion you really do need to put a toaster in the bathroom, but it will never be anywhere nearly as often as moving i
[kgpg] [Bug 373891] Autostart option is without effect on non-KDE desktop
https://bugs.kde.org/show_bug.cgi?id=373891 David H. Gutteridge <dhgutteri...@hotmail.com> changed: What|Removed |Added CC||dhgutteri...@hotmail.com --- Comment #2 from David H. Gutteridge <dhgutteri...@hotmail.com> --- I'm also seeing this issue. KAlarm previously had the same problem. (https://bugs.kde.org/show_bug.cgi?id=366562). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it
https://bugs.kde.org/show_bug.cgi?id=364915 David H. Gutteridge <dhgutteri...@hotmail.com> changed: What|Removed |Added CC||dhgutteri...@hotmail.com --- Comment #5 from David H. Gutteridge <dhgutteri...@hotmail.com> --- I've also been seeing this for a while. Today it was particularly pronounced: the desktop was shown for around ten seconds before the locker finally kicked in. (Usually it's less than a second.) During this time I could move the mouse around, though the windows weren't reactive. The machine in question is Ivy Bridge generation, and is running Linux 4.9.6, the Intel DRM driver (2.99.917.26.20160929), and KDE Plasma 5.8.5. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 --- Comment #6 from David H. Gutteridge <dhgutteri...@hotmail.com> --- Confirming this is fixed for me with the 16.08.1 release. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 David H. Gutteridge <dhgutteri...@hotmail.com> changed: What|Removed |Added CC||dhgutteri...@hotmail.com --- Comment #2 from David H. Gutteridge <dhgutteri...@hotmail.com> --- Under Gnome 3.20, KAlarm is starting for me when I've explicitly disabled start-at-login for it via the UI's settings panel. This is with KAlarm 2.11.7-5ak (KDE Applications 16.04.3) on Fedora 24. The final entry in /etc/xdg/autostart/kalarm.autostart.desktop is "X-KDE-autostart-condition=kalarmrc:General:AutoStart:false" but that has no effect (which is presumably because it's a KDE-specific directive). My .config/kalarmrc also contains "NoAutoStart=true". -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 269258] F15 kleopatra crashes (kdepim package)
https://bugs.kde.org/show_bug.cgi?id=269258 David H <thesunspot...@gmail.com> changed: What|Removed |Added CC||thesunspot...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 356583] File open/save dialog causes segfaults in several applications
https://bugs.kde.org/show_bug.cgi?id=356583 --- Comment #13 from David H. Gutteridge <dhgutteri...@hotmail.com> --- According to another Fedora bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1291003), this appears to be an issue with QT 5.5.1. They have a test fix in updates-testing available now. (https://bodhi.fedoraproject.org/updates/FEDORA-2016-4899ebd424). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356539] New: kate segfaults repeatedly during regular trivial use
https://bugs.kde.org/show_bug.cgi?id=356539 Bug ID: 356539 Summary: kate segfaults repeatedly during regular trivial use Product: kate Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dhgutteri...@hotmail.com Application: kate (15.08.1) Qt Version: 5.5.1 Operating System: Linux 4.2.7-300.fc23.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Once kate crashed when I tried to save a minor change to a file, another time it crashed when I tried to save a file, another time it crashed when I tried to open a file. This instability has suddenly appeared after upgrading to Plasma 5.5. The crash can be reproduced sometimes. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0412ebe900 (LWP 9458))] Thread 2 (Thread 0x7f03f3bcd700 (LWP 9459)): #0 0x7f040b7c3ffd in poll () from /lib64/libc.so.6 #1 0x7f04086d8272 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f04086d9ee7 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f03f6599da9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f040c3cc3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f040998860a in start_thread () from /lib64/libpthread.so.0 #6 0x7f040b7cfa9d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0412ebe900 (LWP 9458)): [KCrash Handler] #5 0x7f03f65b0f08 in QXcbWindow::setParent(QPlatformWindow const*) () from /lib64/libQt5XcbQpa.so.5 #6 0x7f040d44a8bb in QWindow::setParent(QWindow*) () from /lib64/libQt5Gui.so.5 #7 0x7f040dc255d5 in QWidgetPrivate::setParent_sys(QWidget*, QFlags) () from /lib64/libQt5Widgets.so.5 #8 0x7f040dc30fda in QWidget::setParent(QWidget*, QFlags) () from /lib64/libQt5Widgets.so.5 #9 0x7f040dc320cc in QWidget::setParent(QWidget*) () from /lib64/libQt5Widgets.so.5 #10 0x7f040dd1811c in QDialogButtonBox::addButton(QAbstractButton*, QDialogButtonBox::ButtonRole) () from /lib64/libQt5Widgets.so.5 #11 0x7f03f2d9de59 in KDEPlatformFileDialog::KDEPlatformFileDialog() () from /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so #12 0x7f03f2d9e282 in KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper() () from /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so #13 0x7f03f2d912fa in KdePlatformTheme::createPlatformDialogHelper(QPlatformTheme::DialogType) const () from /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so #14 0x7f040dde71b5 in QDialogPrivate::platformHelper() const () from /lib64/libQt5Widgets.so.5 #15 0x7f040ddfa958 in QFileDialogPrivate::init(QUrl const&, QString const&, QString const&) () from /lib64/libQt5Widgets.so.5 #16 0x7f040ddfac76 in QFileDialog::QFileDialog(QFileDialogArgs const&) () from /lib64/libQt5Widgets.so.5 #17 0x7f040ddfb22e in QFileDialog::getOpenFileUrls(QWidget*, QString const&, QUrl const&, QString const&, QString*, QFlags, QStringList const&) () from /lib64/libQt5Widgets.so.5 #18 0x7f0412b45918 in KateViewManager::slotDocumentOpen() () from /lib64/libkdeinit5_kate.so #19 0x7f0412b7f695 in KateViewManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libkdeinit5_kate.so #20 0x7f040c5dc2ea in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #21 0x7f040dbe37d2 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #22 0x7f040dbe5c58 in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #23 0x7f040dd68562 in QMenuPrivate::activateCausedStack(QListconst&, QAction*, QAction::ActionEvent, bool) () from /lib64/libQt5Widgets.so.5 #24 0x7f040dd6e82c in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) () from /lib64/libQt5Widgets.so.5 #25 0x7f040dd72730 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #26 0x7f040dc30428 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x7f040dd73173 in QMenu::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #28 0x7f040dbed41c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #29 0x7f040dbf2fe9 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #30 0x7f040c5ad77b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #31 0x7f040dd71f19 in QMenuPrivate::mouseEventTaken(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #32 0x7f040dd725b6 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #33 0x7f040dc30428 in QWidget::event(QEvent*) () from
