[krita] [Bug 396219] Group Layer Export Wish : Autotrim to Visible Checkmark
https://bugs.kde.org/show_bug.cgi?id=396219 --- Comment #2 from reptilli...@live.com --- And finally, I thought that .kra and .psd should preserve information as much as possible. So, that should be another feature in mind. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 318454] Seam with Sharpen and Blur filters.
https://bugs.kde.org/show_bug.cgi?id=318454 reptilli...@live.com changed: What|Removed |Added Attachment #113791|Very beautiful seams|Seams on Sharpen Filter description|results with Sharpen| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 318454] Seam with Sharpen and Blur filters.
https://bugs.kde.org/show_bug.cgi?id=318454 reptilli...@live.com changed: What|Removed |Added Attachment #113791|Just as the title say, the |Very beautiful seams description|seams shows.|results with Sharpen -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 318454] Seam with Sharpen and Blur filters.
https://bugs.kde.org/show_bug.cgi?id=318454 reptilli...@live.com changed: What|Removed |Added CC||reptilli...@live.com --- Comment #4 from reptilli...@live.com --- Created attachment 113791 --> https://bugs.kde.org/attachment.cgi?id=113791=edit Just as the title say, the seams shows. There is now seam back on Krita 4.2. It shows up on the sharpen sections only. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396183] Selecting a timezone randomly selects other timezones
https://bugs.kde.org/show_bug.cgi?id=396183 --- Comment #2 from Franz Fellner --- (In reply to David Edmundson from comment #1) > Can't reproduce and not seen any other reports. > > can you make a video and upload? Here you are: https://www.dropbox.com/s/m6mbzqx752cbzl9/configure_timezone.ogv?dl=0 Nothing but local (Bukarest) selected in the beginning. Selected Berlin and just scrolled down until Rothera (~30 sec). Then scrolled back up until selected Kaliningrad becomes visible. Then scrolled down and up several times - note how with every direction change different timezones are selected. Finally scrolled further up and deselected Honolulu - and finally all auto-selected are gone, just Berlin selected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396233] New: The "layer" docker cannot be changed width wise like all the other dockers. It takes up much more space than necessary.
https://bugs.kde.org/show_bug.cgi?id=396233 Bug ID: 396233 Summary: The "layer" docker cannot be changed width wise like all the other dockers. It takes up much more space than necessary. Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: vaughn.s...@yahoo.com Target Milestone: --- Please fix this, it is very annoying. It takes up too much space on screen and really does not need to. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396232] New: Krita crashes after deselecting final colour channel.
https://bugs.kde.org/show_bug.cgi?id=396232 Bug ID: 396232 Summary: Krita crashes after deselecting final colour channel. Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: jordanferra...@gmail.com Target Milestone: --- If I uncheck a colour channel being the only one, other than alpha as far as I know, Krita crashes (possibly because the channels start disagreeing with each other because there is nothing for the Alpha layer to shade in or something). The picture also mysteriously turns into a grayscale when you have one channel open, even though goes white-to-C/M/Y when you have two colour channels open. Not sure if it is or is not meant to happen, though. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396231] New: kdf does not appear in the install list of space information of 'moretools'
https://bugs.kde.org/show_bug.cgi?id=396231 Bug ID: 396231 Summary: kdf does not appear in the install list of space information of 'moretools' Product: dolphin Version: 17.04.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mort...@comcast.net CC: elvis.angelac...@kde.org Target Milestone: --- kdf (KDiskFree) does not appear in the list of installed tools even though it is installed. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 396230] New: Kfind crashes
https://bugs.kde.org/show_bug.cgi?id=396230 Bug ID: 396230 Summary: Kfind crashes Product: kfind Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mort...@comcast.net Target Milestone: --- Application: kfind (2.0.0) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.138-59-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Searching content of all files in home directory for specific string The crash can be reproduced every time. -- Backtrace: Application: KFind (kfind), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe018edc940 (LWP 6652))] Thread 3 (Thread 0x7fdffbfff700 (LWP 6654)): #0 0x7fe014c5330d in poll () at /lib64/libc.so.6 #1 0x7fe00f9c1314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe00f9c142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe01555f1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe01550cbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe015347f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe011efd295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fe01534ca29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe0100f5724 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe014c5be8d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fe00304e700 (LWP 6653)): #0 0x7fe014c5330d in poll () at /lib64/libc.so.6 #1 0x7fe00d85d3c2 in () at /usr/lib64/libxcb.so.1 #2 0x7fe00d85efaf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fe0055b10d9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe01534ca29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe0100f5724 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe014c5be8d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe018edc940 (LWP 6652)): [KCrash Handler] #6 0x7fe014ba3f67 in raise () at /lib64/libc.so.6 #7 0x7fe014ba533a in abort () at /lib64/libc.so.6 #8 0x7fe014fad545 in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib64/libstdc++.so.6 #9 0x7fe014fab336 in () at /usr/lib64/libstdc++.so.6 #10 0x7fe014fab381 in () at /usr/lib64/libstdc++.so.6 #11 0x7fe014fab5c3 in () at /usr/lib64/libstdc++.so.6 #12 0x7fe015333ae2 in () at /usr/lib64/libQt5Core.so.5 #13 0x7fe0153d6e85 in QString::reallocData(unsigned int, bool) () at /usr/lib64/libQt5Core.so.5 #14 0x7fe0153d74a4 in QString::append(QString const&) () at /usr/lib64/libQt5Core.so.5 #15 0x7fe01545839f in () at /usr/lib64/libQt5Core.so.5 #16 0x7fe01545b7e9 in QTextStream::readLineInto(QString*, long long) () at /usr/lib64/libQt5Core.so.5 #17 0x7fe01545ba8e in QTextStream::readLine(long long) () at /usr/lib64/libQt5Core.so.5 #18 0x00423a32 in () #19 0x00422324 in () #20 0x004225e3 in () #21 0x00429ae8 in () #22 0x7fe0155387d1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #23 0x7fe0182e2994 in KIO::ListJob::entries(KIO::Job*, QList const&) () at /usr/lib64/libKF5KIOCore.so.5 #24 0x7fe0182e3cec in () at /usr/lib64/libKF5KIOCore.so.5 #25 0x7fe0182e431d in () at /usr/lib64/libKF5KIOCore.so.5 #26 0x7fe0155387d1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #27 0x7fe0182cce25 in KIO::SlaveInterface::listEntries(QList const&) () at /usr/lib64/libKF5KIOCore.so.5 #28 0x7fe0182cfa44 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () at /usr/lib64/libKF5KIOCore.so.5 #29 0x7fe0182cd178 in KIO::SlaveInterface::dispatch() () at /usr/lib64/libKF5KIOCore.so.5 #30 0x7fe0182d158e in KIO::Slave::gotInput() () at /usr/lib64/libKF5KIOCore.so.5 #31 0x7fe018350275 in () at /usr/lib64/libKF5KIOCore.so.5 #32 0x7fe0155387d1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #33 0x7fe01827e077 in () at /usr/lib64/libKF5KIOCore.so.5 #34 0x7fe015539e26 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #35 0x7fe01620f28c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #36 0x7fe0162138ea in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #37 0x7fe01550ebe5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #38 0x7fe0155109ca in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #39 0x7fe01555fb03 in () at /usr/lib64/libQt5Core.so.5
[systemsettings] [Bug 396214] wayland: crash when opening systemsettings5 -> fonts after setting 'antialiasing' to enabled
https://bugs.kde.org/show_bug.cgi?id=396214 Christoph Feck changed: What|Removed |Added CC||unassigned-b...@kde.org Component|general |kcm_fonts Assignee|plasma-b...@kde.org |unassigned-b...@kde.org Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 396229] Keyboard shortcut/button to pause data updates (feature request)
https://bugs.kde.org/show_bug.cgi?id=396229 joshleiven...@outlook.com changed: What|Removed |Added CC||joshleiven...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 396229] New: Keyboard shortcut/button to pause data updates (feature request)
https://bugs.kde.org/show_bug.cgi?id=396229 Bug ID: 396229 Summary: Keyboard shortcut/button to pause data updates (feature request) Product: ksysguard Version: 5.13.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: joshleiven...@outlook.com Target Milestone: --- It would be great if we could easily pause tabs from updating, to look at something before it changes. This can be done by setting the tab refresh rate to 0, but that's too arduous to do often. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396228] New: Discover Unexpectedly Closes When It Checks for Available Updates to 3 Packages
https://bugs.kde.org/show_bug.cgi?id=396228 Bug ID: 396228 Summary: Discover Unexpectedly Closes When It Checks for Available Updates to 3 Packages Product: Discover Version: 5.13.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: irodrigue...@gmail.com Target Milestone: --- Application: plasma-discover (5.13.0) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.16.13-2-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I logged in, I saw and clicked on the notification for available package updates then, it instantly force-closed. The necessary updates do show, as in, Discover shows an available update to ffmpeg and freedesktop.org Application Platform Version 1.6 Sadly once it finishes loading that panel showing me the package names, it closes automatically. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f333f433800 (LWP 2187))] Thread 23 (Thread 0x7f326bfff700 (LWP 2282)): #0 0x7f333a9bf0f9 in syscall () at /usr/lib/libc.so.6 #1 0x7f3334eb352d in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f3334e3e903 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f3334e3 in g_async_queue_timeout_pop () at /usr/lib/libglib-2.0.so.0 #4 0x7f3334e95541 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f3334e94a2a in () at /usr/lib/libglib-2.0.so.0 #6 0x7f33370a2075 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f333a9c453f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f32b77fe700 (LWP 2217)): #0 0x7f33370a83f6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f333b0d522d in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f333b0ccc54 in () at /usr/lib/libQt5Core.so.5 #3 0x7f333b0d4b95 in () at /usr/lib/libQt5Core.so.5 #4 0x7f33370a2075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f333a9c453f in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f32d0ff9700 (LWP 2214)): #0 0x7f33370a83f6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f333b0d522d in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f333b0ccc54 in () at /usr/lib/libQt5Core.so.5 #3 0x7f333b0d4b95 in () at /usr/lib/libQt5Core.so.5 #4 0x7f33370a2075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f333a9c453f in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f32d1ffb700 (LWP 2212)): #0 0x7f33370a83f6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f333b0d522d in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f333b0ccc54 in () at /usr/lib/libQt5Core.so.5 #3 0x7f333b0d4b95 in () at /usr/lib/libQt5Core.so.5 #4 0x7f33370a2075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f333a9c453f in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f32d27fc700 (LWP 2211)): #0 0x7f33370a83f6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f333b0d522d in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f333b0ccc54 in () at /usr/lib/libQt5Core.so.5 #3 0x7f333b0d4b95 in () at /usr/lib/libQt5Core.so.5 #4 0x7f33370a2075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f333a9c453f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f32d37fe700 (LWP 2209)): #0 0x7f33370a83f6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f333b0d522d in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f333b0ccc54 in () at /usr/lib/libQt5Core.so.5 #3 0x7f333b0d4b95 in () at /usr/lib/libQt5Core.so.5 #4 0x7f33370a2075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f333a9c453f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f32d3fff700 (LWP 2208)): #0 0x7f33370a83f6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f333b0d522d in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f333b0ccc54 in () at /usr/lib/libQt5Core.so.5 #3 0x7f333b0d4b95 in () at /usr/lib/libQt5Core.so.5 #4 0x7f33370a2075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f333a9c453f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f32e8ff9700 (LWP 2207)): #0 0x7f333a9b5934 in read () at /usr/lib/libc.so.6 #1
[krita] [Bug 396179] Krita crashing randomly
https://bugs.kde.org/show_bug.cgi?id=396179 --- Comment #4 from Mohammad --- (In reply to Mohammad from comment #3) Never mind that. For some reason it crashes a lot as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394420] Folder view applet is expanded when in panel
https://bugs.kde.org/show_bug.cgi?id=394420 --- Comment #29 from North --- The bug report I filed related to the File View widget. ( https://bugs.kde.org/show_bug.cgi?id=396037 ) I have just noticed that this report relates to an applet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394420] Folder view applet is expanded when in panel
https://bugs.kde.org/show_bug.cgi?id=394420 --- Comment #28 from North --- (In reply to Michail Vourlakos from comment #27) > (In reply to North from comment #26) > > (In reply to Andreas Blochberger from comment #12) > > I can't reset the icon size for panel. Nothing happens when I select > > 'panel'. > > you can choose Breeze icons to change the panel icon size to 256px. and > afterwards you choose your icon theme If I change the icons theme, ALL my panel icons will change to that theme. The last time I changed the icons theme, all the icons became nondescript blobs. They remained so after I changed the theme back to what it had been. I then had to change each icon individually. I had and have about 28 icons in Quicklaunch widgets on the panel. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #7 from David Edmundson --- >From the comment above: Other report was on resume from suspend, which means it's probably fallout from that nvidia graphics reset and us not resetting the vertex. I'll look into it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 David Edmundson changed: What|Removed |Added CC||wesley.gr...@gmail.com --- Comment #6 from David Edmundson --- *** Bug 396227 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396227] KWin Seg Fault on Resume from Suspend
https://bugs.kde.org/show_bug.cgi?id=396227 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 372305 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #13 from David Edmundson --- DRM modes not being available, not kwin's scope. system settings not showing the right stuff first boot is interesting.. But it gets complex when a bug report ends up with two issues. Launching from sddm should be fine. You're clearly running in wayland. How did you start systemsettings? Is this on every reboot and reproducible? Can you type "env" in a terminal and paste output. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396224] layer styles are not applied when exporting as png or jpg
https://bugs.kde.org/show_bug.cgi?id=396224 eggy.s...@gmail.com changed: What|Removed |Added CC||eggy.s...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396179] Krita crashing randomly
https://bugs.kde.org/show_bug.cgi?id=396179 --- Comment #3 from Mohammad --- (In reply to Antti Savolainen from comment #1) > Can you attach your kritarc file? We have a lot of people doing long > projects without experiencing any crashes so I assume it's your personal > config. After posting it, you can delete the file to test if the program > crashes with the default settings. Let me know. > Also, would you have any pointers on what you were doing before the crash? I downgraded to 4.1.0 beta 2 and now it works even better, since in the official 4.1.0 "stable" release I couldn't open the pop up palette when I right clicked with my stylus. Now I can open the pop up palette, and Krita doesn't crash every 5 minutes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383174] google photo, export stops after a random quantity of photos
https://bugs.kde.org/show_bug.cgi?id=383174 --- Comment #5 from Thanh Trung Dinh --- Hi, I found a way to work around. I don't have too many images to test, but I think that this bug will be fixed in 6.0.0. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395442] Framework 5.47 bug with systray notifications: list empty and other issues
https://bugs.kde.org/show_bug.cgi?id=395442 --- Comment #7 from el...@seznam.cz --- Created attachment 113790 --> https://bugs.kde.org/attachment.cgi?id=113790=edit Empty list -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395442] Framework 5.47 bug with systray notifications: list empty and other issues
https://bugs.kde.org/show_bug.cgi?id=395442 el...@seznam.cz changed: What|Removed |Added CC||el...@seznam.cz --- Comment #6 from el...@seznam.cz --- I have the same issue and when this happens there are another side effects: - Clicking on arrow icon opens Status & Notification. This is fine. However clicking it again does not close Status & Notifications as expected. Also arrow icon does not change its orientation. Only way to close it is clicking elsewhere on desktop. - Clicking on any tray icon (like Volume, Clipboard Contents, Networks, Bluetooth...) always opens Status & Notification and therefore I'm unable to change any settings. I believe this makes it higher priority bug. - When I open Status & Notification and then click on Touchpad icons which shows question in popup window, Status & Notification stays open forever and will not close. -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 396223] Aviso de erro de deletar e de recortar
https://bugs.kde.org/show_bug.cgi?id=396223 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 377880 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 377880] Gwenview There are two actions (Cut, Delete)
https://bugs.kde.org/show_bug.cgi?id=377880 Christoph Feck changed: What|Removed |Added CC||sampaio.controlline@gmail.c ||om --- Comment #48 from Christoph Feck --- *** Bug 396223 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396227] New: KWin Seg Fault on Resume from Suspend
https://bugs.kde.org/show_bug.cgi?id=396227 Bug ID: 396227 Summary: KWin Seg Fault on Resume from Suspend Product: kwin Version: 5.13.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: wesley.gr...@gmail.com Target Milestone: --- Application: kwin_x11 (5.13.2) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: I resumed from a suspended state. After logging into my existing session, KWin reported it had crashed. Besides the report of a crash, I did not notice any other odd behavior. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7715ecf940 (LWP 1838))] Thread 4 (Thread 0x7f76e0e22700 (LWP 1915)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7711bc5e04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f7711bc5e49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f770e9316ba in start_thread (arg=0x7f76e0e22700) at pthread_create.c:333 #4 0x7f77158e441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f76f258e700 (LWP 1906)): #0 0x7f77158d8811 in __GI_ppoll (fds=fds@entry=0x7f76e8000ae8, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f7712c93651 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f76e8000ae8) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7f76e8000ae8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7f7712c94ce2 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f7712c3f1ca in QEventLoop::exec (this=this@entry=0x7f76f258dc50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f7712a745e4 in QThread::exec (this=) at thread/qthread.cpp:522 #7 0x7f770d5cfcf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f7712a7f727 in QThreadPrivate::start (arg=0x24fa2f0) at thread/qthread_unix.cpp:367 #9 0x7f770e9316ba in start_thread (arg=0x7f76f258e700) at pthread_create.c:333 #10 0x7f77158e441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f76f3fff700 (LWP 1887)): #0 0x7f77158d8811 in __GI_ppoll (fds=fds@entry=0x7f76ec00f408, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f7712c93651 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f76ec00f408) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7f76ec00f408, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7f7712c94ce2 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f7712c3f1ca in QEventLoop::exec (this=this@entry=0x7f76f3ffec40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f7712a745e4 in QThread::exec (this=) at thread/qthread.cpp:522 #7 0x7f770c4ddf35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f7712a7f727 in QThreadPrivate::start (arg=0x7f770c756d60) at thread/qthread_unix.cpp:367 #9 0x7f770e9316ba in start_thread (arg=0x7f76f3fff700) at pthread_create.c:333 #10 0x7f77158e441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7715ecf940 (LWP 1838)): [KCrash Handler] #6 KWin::ContrastEffect::uploadRegion (this=this@entry=0x2421030, map=@0x7ffef82e02b8: 0x7f76f0288700, region=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:281 #7 0x7f77121cb9a4 in KWin::ContrastEffect::uploadGeometry (this=this@entry=0x2421030, vbo=vbo@entry=0x2a16ea0, region=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:299 #8 0x7f77121ccea4 in KWin::ContrastEffect::doContrast (this=this@entry=0x2421030, w=w@entry=0x2e50b30, shape=..., screen=..., opacity=0, screenProjection=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:442 #9 0x7f77121cd929 in KWin::ContrastEffect::drawWindow (this=this@entry=0x2421030, w=w@entry=0x2e50b30, mask=mask@entry=2, region=..., data=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:419 #10 0x7f771546516e in KWin::EffectsHandlerImpl::drawWindow (this=0x2a4ef80,
[krita] [Bug 396226] New: [Wish] Review the Tools and the Toolbox
https://bugs.kde.org/show_bug.cgi?id=396226 Bug ID: 396226 Summary: [Wish] Review the Tools and the Toolbox Product: krita Version: 4.1.0 Platform: unspecified OS: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: kapyia@gmail.com Target Milestone: --- Created attachment 113789 --> https://bugs.kde.org/attachment.cgi?id=113789=edit Current Toolbox There's recently been talks about trying to condense and/or reorganize the contents of the Toolbox docker, so I'm making a wishlist ticket for it. Some ideas are: - Making the Toolbox customizable, allowing users to hide/reveal icons of tools. - A context sensitive Toolbox that hides (and disables) tools that won't work for the type of layer that's currently selected (eg. hiding the Calligraphy tool on Paint Layers and hiding the Brush tool on Vector Layers). - Merging tools that produce similar results and move the differing functionality into the Tool Options (eg. merging Polygon/Polyline into one, making Dynamic Brush into a smoothing mode for the Freehand Brush, and making a single "Shape Tool" that can be used to make line, ellipses, rectangles, and polygons) - Or maybe a little bit of everything, if someone's feeling really pumped :P While not necessary, it may not be such a bad idea to look over how the tools are organized in the Toolbox as well. There might be better ways to sort them by, or maybe at least least small ways to improve the order (eg. putting the three Brush tools next to each other). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #12 from Mike Lothian --- So what is the correct avenue to get this issue resolved? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391609] autostart script is not executed, log claims it is
https://bugs.kde.org/show_bug.cgi?id=391609 --- Comment #6 from francisco_t --- (In reply to Arek Guzinski from comment #5) > > @francisco_t: many of the things xmodmap does, would be overwritten when kde > sets the keyboard layout. are you sure that's not happening? (i don't think > it should, but.. maybe..) > as a workaround, you could try a script with the line > (sleep 5; xmodmap ~/.xmodmaprc)& It's working! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396225] When importing a ofx/qif file, it does not show me all my accounts
https://bugs.kde.org/show_bug.cgi?id=396225 --- Comment #1 from Beetle B. --- Small correction: Finally got the CSV file to import - it showed me all accounts. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396225] New: When importing a ofx/qif file, it does not show me all my accounts
https://bugs.kde.org/show_bug.cgi?id=396225 Bug ID: 396225 Summary: When importing a ofx/qif file, it does not show me all my accounts Product: kmymoney Version: 5.0.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: mu...@nawaz.org Target Milestone: --- Steps: 1. Download QIF file from bank 2. Import QIF 3. KMyMoney doesn't know which account it is associated with. It shows me a list of Asset accounts to tie it into. The problem is, the list is very incomplete. It shows probably only half the accounts I have. Same problem if I import OFX. Same problem if I use the Web OFX (mapping to online account). When I try to use CSV import, I go through all the steps of selecting the columns, etc - but at the end nothing gets imported! (No error either). Note I have successfully used QIF import for a credit card account (the account was in the list of Liabilities accounts...) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396225] When importing a ofx/qif file, it does not show me all my accounts
https://bugs.kde.org/show_bug.cgi?id=396225 Beetle B. changed: What|Removed |Added CC||mu...@nawaz.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396183] Selecting a timezone randomly selects other timezones
https://bugs.kde.org/show_bug.cgi?id=396183 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Can't reproduce and not seen any other reports. can you make a video and upload? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396217] cant start shell script from launcher anymore
https://bugs.kde.org/show_bug.cgi?id=396217 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Sounds more like your setup is wrong. Please upload your .desktop file and I'll take a look -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392516] Please bring back "Back to code" button
https://bugs.kde.org/show_bug.cgi?id=392516 --- Comment #1 from Eugene Shalygin --- The description above is wrong. Instead, please, add those buttons to regular actions and menu, because they are unavailable when global menu is active. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 97813] Info node for emacs-21 not working in khelpcenter or konqueror
https://bugs.kde.org/show_bug.cgi?id=97813
Julian Schraner changed:
What|Removed |Added
Product|kio |kio-extras
Ever confirmed|0 |1
Assignee|hoel...@kde.org |plasma-b...@kde.org
Component|info|default
CC||juliquad...@gmail.com
Status|UNCONFIRMED |CONFIRMED
Version|unspecified |18.04.2
--- Comment #13 from Julian Schraner ---
This bug is now more than a decade old, and interestingly enough I am still
able to reproduce this: running
kioclient5 exec info:/emacs-24/emacs
returns an error (" The Info node emacs in Info file /usr/share/info/emacs-24
does not exist."). I'll therefore move this bug report over to kio-extras, but
it might take another decade until this is fixed ;)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 396221] Pasted vector layers always pasted at top, or in same vector layer
https://bugs.kde.org/show_bug.cgi?id=396221 --- Comment #2 from kaz.fox...@gmail.com --- Thanks for the quick response. The best result would depend on consistency with other layer-type paste results. Ideally, "paste as new layer" and "paste into layer" options would exist for paint, vector, and mask layers. "Paste as new layer" could be the default Ctrl-V for any layer type, but there could be an alternate menu/right-click option for the other types (like "Paste in Place" is an option in Photoshop). I've seen posts in forums asking about ability to paste into an existing paint layer (I Googled it, wanting to know the same) and there was some explanation why it supposedly wasn't necessary, but I think "paste on same layer" is a good option, like if I want to add something copied from a paint layer to a mask layer, or add to a layer w/ a different blend mode, but creating a new layer and merging the two resets the blend back to Normal and creates extra steps. For more consistency, there'd need to be an option to merge vector layers without turning them into a paint layer. As far as pasting a new vector layer, I think it should act the same way as pasting a new paint layer and go above the currently selected layer. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 159818] can't read automake's info page from kdevelop
https://bugs.kde.org/show_bug.cgi?id=159818 Julian Schraner changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED CC||juliquad...@gmail.com --- Comment #3 from Julian Schraner --- AFAIK, KDevelop does not have an info page anymore -> I'll close this bug. If for some reason you do still have an info page for KDevelop & it can still not be read by the kioslave, please open a new bug over in kio-extras. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396224] layer styles are not applied when exporting as png or jpg
https://bugs.kde.org/show_bug.cgi?id=396224 --- Comment #1 from eggy.s...@gmail.com --- I forgot to mention that this was working as normal in the 4.0.4 release -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396099] [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 --- Comment #4 from Andrius Štikonas --- So today I tried to add a virtual hard drive to my Fedora 28 virtual machine. KPM seemed to work. It correctly asked for password using polkit dialog. I could switch to dummy backend too. Although, later I observed crash on exit which I don't see on my main system... Maybe Qt 5.10? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396224] New: layer styles are not applied when exporting as png or jpg
https://bugs.kde.org/show_bug.cgi?id=396224 Bug ID: 396224 Summary: layer styles are not applied when exporting as png or jpg Product: krita Version: 4.1.0 alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: eggy.s...@gmail.com Target Milestone: --- Created attachment 113788 --> https://bugs.kde.org/attachment.cgi?id=113788=edit example save file Hello, I'm currently running the latest 4.1 release downloaded from the main website on windows 8.1 I've tested a couple of different layer styles and they don't seem to be being applied when exporting the image (I tried .png and .jpg and both have the same problem) Here is a file I have been working on, as an example. On my computer the exported image is in black & white as the colour is added via a color overlay -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 396223] New: Aviso de erro de deletar e de recortar
https://bugs.kde.org/show_bug.cgi?id=396223 Bug ID: 396223 Summary: Aviso de erro de deletar e de recortar Product: abakus Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k.h...@gmx.de Reporter: sampaio.controll...@gmail.com Target Milestone: --- Created attachment 113787 --> https://bugs.kde.org/attachment.cgi?id=113787=edit Aviso de erro do KDE, solicitando informar bugs.kde.org. Aviso de erro do KDE, solicitando informar bugs.kde.org. Control+D => Delete e Recorte... -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 229261] Print to file paper size setting reverts to A4 every time
https://bugs.kde.org/show_bug.cgi?id=229261 Steve Kelem changed: What|Removed |Added Ever confirmed|0 |1 CC||st...@kelem.net Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #9 from Steve Kelem --- Five years later... This bug is still present in Okular 1.3.3 on Ubuntu 18.04. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390571] Mediaframe: Width of "Fill mode" drop down is not enough to show selected setting
https://bugs.kde.org/show_bug.cgi?id=390571 Dr. Chapatin changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390571] Mediaframe: Width of "Fill mode" drop down is not enough to show selected setting
https://bugs.kde.org/show_bug.cgi?id=390571 --- Comment #6 from Dr. Chapatin --- Created attachment 113786 --> https://bugs.kde.org/attachment.cgi?id=113786=edit screenshot taken in plasma 5.13.2 Bug persists in plasma 5.13.2. -- You are receiving this mail because: You are watching all bug changes.
[Rocs] [Bug 396222] New: qml-module-qtqml-statemachine is not in dependency
https://bugs.kde.org/show_bug.cgi?id=396222 Bug ID: 396222 Summary: qml-module-qtqml-statemachine is not in dependency Product: Rocs Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: script engine Assignee: rocs-bugs-n...@kde.org Reporter: kelalaka...@gmail.com Target Milestone: --- Running Rocs from command line gave the output; org.kde.rocs.graphtheory.general: "qrc:/libgraphtheory/qml/Scene.qml:25 module \"QtQml.StateMachine\" is not installed\n" After searching a installed qml-module-qtqml-statemachine manually. It must be in the dependency to work. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396221] Pasted vector layers always pasted at top, or in same vector layer
https://bugs.kde.org/show_bug.cgi?id=396221 David REVOY changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Severity|normal |wishlist CC||i...@davidrevoy.com Ever confirmed|0 |1 --- Comment #1 from David REVOY --- Hi @kaz.foxsen, I switch this report as a Wishlist; because it is not really a bug, but more a part that needs a bit more polishing. But it is for bug triage logic; I totally do agree it is confusing: I confirm also the ticket. What would be the correct behavior? Create a vector layer above the current layer selected (even if it is a vector layer) and paste the vector object in the content? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396220] vex x86->IR: unhandled instruction bytes: 0xC4 0xE2 0x41 0xF7
https://bugs.kde.org/show_bug.cgi?id=396220 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #2 from Tom Hughes --- VEX prefixed instructions, and recent additions to the instruction set in general, are not supported by the x86 backend and are unlikely ever to be. They are generally supported by the amd64/x86_64 backend, so compile in 64 bit mode if you want to use them. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396220] vex x86->IR: unhandled instruction bytes: 0xC4 0xE2 0x41 0xF7
https://bugs.kde.org/show_bug.cgi?id=396220 --- Comment #1 from John F.X. Galea --- The instruction in question is: 81521dd: c4 e2 41 f7 c0 shlx %edi,%eax,%eax -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396220] New: vex x86->IR: unhandled instruction bytes: 0xC4 0xE2 0x41 0xF7
https://bugs.kde.org/show_bug.cgi?id=396220 Bug ID: 396220 Summary: vex x86->IR: unhandled instruction bytes: 0xC4 0xE2 0x41 0xF7 Product: valgrind Version: 3.13.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: johnce...@hotmail.com Target Milestone: --- Hi, I am trying to run Valgrind on SPEC CPU benchmark, and encountered the following error: Essentially, Valgrind aborted with the following error: vex x86->IR: unhandled instruction bytes: 0xC4 0xE2 0x41 0xF7 I'd be happy to check a patch when available to confirm a fix. 1530817135.71: ==27439== Nulgrind, the minimal Valgrind tool 1530817135.71: ==27439== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. 1530817135.71: ==27439== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info 1530817135.71: ==27439== Command: ../run_base_refrate_mytest-m32.0003/perlbench_r_base.mytest-m32 -I./lib checkspam.pl 2500 5 25 11 150 1 1 1 1 1530817135.71: ==27439== 1530817135.71: vex x86->IR: unhandled instruction bytes: 0xC4 0xE2 0x41 0xF7 1530817135.71: ==27439== valgrind: Unrecognised instruction at address 0x81521dd. 1530817135.71: ==27439==at 0x81521DD: Perl_sv_upgrade (sv.c:1522) 1530817135.71: ==27439==by 0x815676F: Perl_sv_setpvn (sv.c:4927) 1530817135.71: ==27439==by 0x81577F7: Perl_newSVpvn (sv.c:9202) 1530817135.71: ==27439==by 0x80A756B: perl_construct (perl.c:249) 1530817135.71: ==27439==by 0x804ADDD: main (perlmain.c:114) 1530817135.71: ==27439== Your program just tried to execute an instruction that Valgrind 1530817135.71: ==27439== did not recognise. There are two possible reasons for this. 1530817135.71: ==27439== 1. Your program has a bug and erroneously jumped to a non-code 1530817135.71: ==27439==location. If you are running Memcheck and you just saw a 1530817135.71: ==27439==warning about a bad jump, it's probably your program's fault. 1530817135.71: ==27439== 2. The instruction is legitimate but Valgrind doesn't handle it, 1530817135.71: ==27439==i.e. it's Valgrind's fault. If you think this is the case or 1530817135.71: ==27439==you are not sure, please let us know and we'll try to fix it. 1530817135.71: ==27439== Either way, Valgrind will now raise a SIGILL signal which will 1530817135.71: ==27439== probably kill your program. 1530817135.71: ==27439== 1530817135.71: ==27439== Process terminating with default action of signal 4 (SIGILL) 1530817135.71: ==27439== Illegal opcode at address 0x81521DD 1530817135.71: ==27439==at 0x81521DD: Perl_sv_upgrade (sv.c:1522) 1530817135.71: ==27439==by 0x815676F: Perl_sv_setpvn (sv.c:4927) 1530817135.71: ==27439==by 0x81577F7: Perl_newSVpvn (sv.c:9202) 1530817135.71: ==27439==by 0x80A756B: perl_construct (perl.c:249) 1530817135.71: ==27439==by 0x804ADDD: main (perlmain.c:114) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396221] New: Pasted vector layers always pasted at top, or in same vector layer
https://bugs.kde.org/show_bug.cgi?id=396221 Bug ID: 396221 Summary: Pasted vector layers always pasted at top, or in same vector layer Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: kaz.fox...@gmail.com Target Milestone: --- I'm using Krita 4.1 on Win10 and the results of copying and pasting vectors is inconsistent (and potentially confusing) with results of pasting paint layers. RASTER paste behavior: -Creates new paint layer above currently selected layer. VECTOR paste: - If current layer is non-vector, a new vector layer is added (as expected) but it's above all layers instead of currently selected one. Dragging and dropping each vector layer into place gets cumbersome if dealing with 10s or 100+ layers. Ex. I'm making a cut-paper look image so each vector shape needs its own clipping group so I can add paper texture rotated at different angles. - If current layer is vector, adds the shape to same layer (a feature that people would like to see available for paint layers, but is inconsistent with raster paste behavior). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396217] cant start shell script from launcher anymore
https://bugs.kde.org/show_bug.cgi?id=396217 --- Comment #1 from farmb...@googlemail.com --- It doesnt work under X11 either, dont even get an error message there :facepalm: -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 388035] Cannot add EWS outbound transport in KMail
https://bugs.kde.org/show_bug.cgi?id=388035 --- Comment #4 from Benjamin Buch --- If you use KDE neon as Linux distribution it is in your package manager without any additions ;-) Install it with: sudo apt install kmailtransport-akonadi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396219] Group Layer Export Wish : Autotrim to Visible Checkmark
https://bugs.kde.org/show_bug.cgi?id=396219 --- Comment #1 from reptilli...@live.com --- I forgot to mention that the trimming should either be canvas-based (fully non-destructive) or deleting pixels, but trimmed to visible (not fully non-destructive). I guess that makes 3 dropdown options. 1. No trims 2. Canvas based trimmed using visible data on group layer 3. Pixels-removed trimming using visible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396219] New: Group Layer Export Wish : Autotrim to Visible Checkmark
https://bugs.kde.org/show_bug.cgi?id=396219 Bug ID: 396219 Summary: Group Layer Export Wish : Autotrim to Visible Checkmark Product: krita Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: reptilli...@live.com Target Milestone: --- At the moment, Export Group Layer into images doesn't trim images into visible area, and there are cases where you wouldn't want that to happen. Thus, I think an additional feature for this would be a way to trim to visible. It would enable one to have something akin to Image Slices via my tutorial on reddit without the need to save and keeping it as non-destructive as possible - https://old.reddit.com/r/krita/comments/8wd4ic/krita_tutorial_image_slices/ . -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 299385] Cantor stops responding when R returns a matrix 50̣×50
https://bugs.kde.org/show_bug.cgi?id=299385 Nikita Sirgienko changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Nikita Sirgienko --- I think, it's now not relevant, because i tried this code and all works fast, so I close it But you have a point there, for large ouptut we plan add warning and question "Should Cantor show this output?". And also we thinking about show/hide feature for results. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 396218] New: Crash on log-in
https://bugs.kde.org/show_bug.cgi?id=396218 Bug ID: 396218 Summary: Crash on log-in Product: frameworks-baloo Version: 5.45.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: aramgrigor...@protonmail.ch Target Milestone: --- Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.4-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Each time i log in to the system after fresh boot i see this crash message. After this checking if baloo is running shows that it does. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5ff72d6100 (LWP 2683))] Thread 3 (Thread 0x7f1fe7dfe700 (LWP 3079)): [KCrash Handler] #6 0x7f5ff4d5c47f in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #7 0x7f5ff62dfa93 in memcpy (__len=65026, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f1fe7dfd997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7f5ff62d0f64 in Baloo::PostingDB::get (this=this@entry=0x7f1fe7dfda80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7f5ff62dd180 in Baloo::WriteTransaction::commit (this=0x5602211ff520) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259 #11 0x7f5ff62d64c2 in Baloo::Transaction::commit (this=this@entry=0x7f1fe7dfdb90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262 #12 0x560220c936cd in Baloo::NewFileIndexer::run (this=0x5602211ff360) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/newfileindexer.cpp:75 #13 0x7f5ff5743372 in QThreadPoolThread::run (this=0x5602211ff7a0) at thread/qthreadpool.cpp:99 #14 0x7f5ff57460ce in QThreadPrivate::start (arg=0x5602211ff7a0) at thread/qthread_unix.cpp:368 #15 0x7f5ff3d51559 in start_thread () from /lib64/libpthread.so.0 #16 0x7f5ff4cfa82f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5fec9fc700 (LWP 2692)): #0 0x7f5ff4cebb78 in read () from /lib64/libc.so.6 #1 0x7f5ff141d420 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5ff13d8bf7 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5ff13d90b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f5ff13d921c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f5ff5969bef in QEventDispatcherGlib::processEvents (this=0x7f5fe8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #6 0x7f5ff591209a in QEventLoop::exec (this=this@entry=0x7f5fec9fbca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f5ff57414da in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f5ff6b86985 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f5ff57460ce in QThreadPrivate::start (arg=0x7f5ff6df6d60) at thread/qthread_unix.cpp:368 #10 0x7f5ff3d51559 in start_thread () from /lib64/libpthread.so.0 #11 0x7f5ff4cfa82f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5ff72d6100 (LWP 2683)): #0 0x7f5ff4cf008b in poll () from /lib64/libc.so.6 #1 0x7f5ff13d9109 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5ff13d921c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5ff5969c0b in QEventDispatcherGlib::processEvents (this=0x560220f99d60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5ff591209a in QEventLoop::exec (this=this@entry=0x7fffb19f1810, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f5ff591a9e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1289 #6 0x560220c8b21c in main (argc=, argv=) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/main.cpp:104 Possible duplicates by query: bug 395996, bug 394404, bug 392701, bug 391803, bug 390610. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396179] Krita crashing randomly
https://bugs.kde.org/show_bug.cgi?id=396179 --- Comment #2 from Mohammad --- Created attachment 113785 --> https://bugs.kde.org/attachment.cgi?id=113785=edit kritarc file Here's the kritarc file. And as far as I know, I haven't done anything that might have caused the crashes, but there's a program that I tried to use (Silky Shark) that didn't work with Krita and was very buggy. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396217] New: cant start shell script from launcher anymore
https://bugs.kde.org/show_bug.cgi?id=396217 Bug ID: 396217 Summary: cant start shell script from launcher anymore Product: plasmashell Version: 5.13.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: farmb...@googlemail.com Target Milestone: 1.0 I have an application launcher added to the menu which starts a shell script. When I click on this launcher I get the error message: Could not find the program '' This is a regression to Plasma 5.12. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 396215] New: 2.8.0 playlist looses information about tracks on the local filesystem
https://bugs.kde.org/show_bug.cgi?id=396215 Bug ID: 396215 Summary: 2.8.0 playlist looses information about tracks on the local filesystem Product: amarok Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Playlists/Saved Playlists Assignee: amarok-bugs-d...@kde.org Reporter: the...@gmx.at CC: bart.cerne...@kde.org Target Milestone: kf5 Amarok 2.8.0 under KDE 4.14.33 OpenSUSE 42.3 I only use local sources for music on my notebook. I created a playlist from various Albums, which are stored as files in a subdirectory of $HOME. When being the current playlist, playing worked fine. Finally I saved the playlist to the Amarok-Database. After flushing the current playlist and closing amarok, I started it again. Since then Amarok was not able to play that saved playlist. The playlist is still there and can be copied to the current playlist. It has all informations except the path to the respective track. When I select "edit metadata", I get the following error under "Note:": "Das SStück kann nicht wiedergegeben werden. When Amarok was last closed, this track was at , but Amarok cannot find this track on the filesystem or in any of your collections anymore. Qou may try plugging in the device this track might be on." As I said the files are all locally stored and have not been moved. Best regards Thomas -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 396216] New: amarok switches pulse 'sink' unexpectedly
https://bugs.kde.org/show_bug.cgi?id=396216 Bug ID: 396216 Summary: amarok switches pulse 'sink' unexpectedly Product: amarok Version: 2.9.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Playback Assignee: amarok-bugs-d...@kde.org Reporter: minsonj2...@gmail.com CC: ma...@laitl.cz Target Milestone: kf5 Created attachment 113784 --> https://bugs.kde.org/attachment.cgi?id=113784=edit both debug and debug-audio turned on Fedora 28 Amarok 2.9.0 Using 'pulseaudio-dlna' to connect to Chromecast Audio devices I have been using the pulseaudio-dlna software and 2 Chromecast audio devices for about 6 months . On Fedora 27 and its version of Amarok I had great success with this setup . After installing Fedora 28/Amarok 2.9.0 Amarok will unexpectedly change pulse 'sinks' between songs . The attached debug log contains info for when the 'sink' changed from 'Porch' to 'Built In Audio Analog' . I ran a looping playlist using 'Clementine Music Player' for > 12 hours to one of the CC Audio devices with no issues . I marked this as 'critical' as this makes Amarok unusable for me . -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396155] Reference images tool lacks features
https://bugs.kde.org/show_bug.cgi?id=396155 --- Comment #4 from Quiralta --- Hm, just realized I pasted the wrong link above (responding to someone in the forum) This is the phabricator link: https://phabricator.kde.org/T5805 (In reply to Storm Engineer from comment #3) > (In reply to Quiralta from comment #2) > > Just want to make a "cross reference" with the dialog in the phabricator and > > google+ > Thank you! :) I would appreciate if you also add any points I'm having here > that may not be in those discussions yet - since you are already familiar > with those, and I have very little time right now. I think the tool just needs some settling, so far is working ok and since is a svg tool variation, it looks like reuses code that is already on Krita making it easy to maintain. (I think) Aside from the pan/zoom/rotation, I would like to see a hide/unhide feature to it maybe with a button on the tools options. My usage for it is very basic thus can't think what else could be missing that is crucial. Now, I circumvent the lack of "been on top" by using a sub-window and then use the images there, would be interesting if someone can step in with a python docker that can do this, but that must come from outside (and I have no programming knowledge) we also have now the window layouts that can complement this tool, with views of windows (instead of docker) with ref images. Anyway, I guess we need first to see what the devs think is doable and possible within the tool in its current form. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395105] GTK3/4 apps (with CSD) cant be resized or moved after trying to resize
https://bugs.kde.org/show_bug.cgi?id=395105 mthw0 changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from mthw0 --- Closing this one as resolved upstream for now as recommended on gtk gitlab. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396209] Reference image transform handles leave a trail
https://bugs.kde.org/show_bug.cgi?id=396209 Quiralta changed: What|Removed |Added CC||rjquira...@gmail.com --- Comment #1 from Quiralta --- I can't reproduce, although that looks like a redraw problem, more likely to be related to the graphic drivers/card/opengl? but I can be wrong. Git master here too, on Arch with nvidia system. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396214] New: wayland: crash when opening systemsettings5 -> fonts after setting 'antialiasing' to enabled
https://bugs.kde.org/show_bug.cgi?id=396214 Bug ID: 396214 Summary: wayland: crash when opening systemsettings5 -> fonts after setting 'antialiasing' to enabled Product: systemsettings Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: starting systemsettings5, then selecting fonts - Unusual behavior I noticed: at first i could open this part of the settings. after changing settings 'aliasing' to 'enabled', this part of the settings crashes the whole systemsettings5 app The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f67b9caecc0 (LWP 2097))] Thread 17 (Thread 0x7f675696b700 (LWP 2116)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f6757fff700 (LWP 2113)): #0 0x7f67b52e52c9 in poll () from /lib64/libc.so.6 #1 0x7f67ae5292c6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f67ae5293ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f67b5bf2b3b in QEventDispatcherGlib::processEvents (this=0x7f674c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f67b5ba2b3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f67b5a01326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f67b36f4085 in QQmlThreadPrivate::run (this=0x564bf428d300) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #7 0x7f67b5a0a8ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #8 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #9 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f6765f4f700 (LWP 2112)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f6766a8c700 (LWP 2111)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f67677fe700 (LWP 2110)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f6767fff700 (LWP 2109)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f676df61700 (LWP 2108)): #0 0x7f67b52e52c9 in poll () from /lib64/libc.so.6 #1 0x7f67ae5292c6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f67ae5293ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f67b5bf2b3b in QEventDispatcherGlib::processEvents (this=0x7f6768000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f67b5ba2b3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f67b5a01326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f67b36f4085 in QQmlThreadPrivate::run (this=0x564bf3be1080) at
[elisa] [Bug 392989] Spacebar should always play/pause irrespective of focus
https://bugs.kde.org/show_bug.cgi?id=392989 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 396213] New: Create Flatpak package for Kate in Flathub
https://bugs.kde.org/show_bug.cgi?id=396213 Bug ID: 396213 Summary: Create Flatpak package for Kate in Flathub Product: kate Version: unspecified Platform: Flatpak OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: s...@roeper.biz Target Milestone: --- Create a Flatpak package for Kate on Flathub, as there already is for Krita, Okular... See https://flathub.org/apps/search/kde -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #11 from Martin Flöser --- Sorry but bug reports are not user support forum. You reopened this report several times and when I asked you to not do this your reply was rather rude. I am personally not interested to spend any more time on it. -- You are receiving this mail because: You are watching all bug changes.
[sweeper] [Bug 302530] sweeper should clean okular data too
https://bugs.kde.org/show_bug.cgi?id=302530 Donna James changed: What|Removed |Added CC||dj217...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396212] New: Discover crashes upon launch
https://bugs.kde.org/show_bug.cgi?id=396212 Bug ID: 396212 Summary: Discover crashes upon launch Product: Discover Version: 5.12.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: tsbutterfi...@ucdavis.edu Target Milestone: --- Application: plasma-discover (5.12.4) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: I attempted to update a number of processes on a new installation. Simultaneously, I attempted to install some softwares through Discover. Discover crashed during the update process and consistently crashes upon launch. I have restarted the computer, but the problem persists. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f11238f1f40 (LWP 1902))] Thread 13 (Thread 0x7f10ce9ec700 (LWP 1918)): #0 0x7f111efddbf9 in __GI___poll (fds=0x7f10c8004e10, nfds=1, timeout=9646) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f11198cc439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f11198cc54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f111f92b90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f111f8d09ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f111f6ef22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f111f6f416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f111b7f16db in start_thread (arg=0x7f10ce9ec700) at pthread_create.c:463 #8 0x7f111efea88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f10f093e700 (LWP 1916)): #0 0x7f1119911cf4 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f11198cb327 in g_main_context_acquire () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f11198cc2f5 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f11198cc54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f111f92b90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f111f8d09ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f111f6ef22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1122ace2a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f111f6f416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f111b7f16db in start_thread (arg=0x7f10f093e700) at pthread_create.c:463 #10 0x7f111efea88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f10f113f700 (LWP 1913)): #0 0x7f111b7f79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5634b804c988) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f111b7f79f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5634b804c938, cond=0x5634b804c960) at pthread_cond_wait.c:502 #2 0x7f111b7f79f3 in __pthread_cond_wait (cond=0x5634b804c960, mutex=0x5634b804c938) at pthread_cond_wait.c:655 #3 0x7f10fd437b7b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f10fd4378a7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f111b7f16db in start_thread (arg=0x7f10f113f700) at pthread_create.c:463 #6 0x7f111efea88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f10f1940700 (LWP 1912)): #0 0x7f111b7f79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5634b804c988) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f111b7f79f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5634b804c938, cond=0x5634b804c960) at pthread_cond_wait.c:502 #2 0x7f111b7f79f3 in __pthread_cond_wait (cond=0x5634b804c960, mutex=0x5634b804c938) at pthread_cond_wait.c:655 #3 0x7f10fd437b7b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f10fd4378a7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f111b7f16db in start_thread (arg=0x7f10f1940700) at pthread_create.c:463 #6 0x7f111efea88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f10f2141700 (LWP 1911)): #0 0x7f111b7f79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5634b804c8a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f111b7f79f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5634b804c850, cond=0x5634b804c878)
[tellico] [Bug 396211] New: Plot summary does not alway work
https://bugs.kde.org/show_bug.cgi?id=396211 Bug ID: 396211 Summary: Plot summary does not alway work Product: tellico Version: 3.1.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: josc...@gmx.de Target Milestone: --- Hello, I've got the problem that the plot summary isn't always transfered correctly from Amazon to Tellico. Example: https://www.amazon.de/dp/B0143R4K24 (The Diabolical Blu Ray) shows "Das Haus der Familie Heller wird jede Nacht von unheimlichen..." as "Produktbeschreibung" but adding this film to tellico the plot summary is "Besonderheiten: FSK 16 Jahre". This doesn't match. Thanks for help -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396210] Disable This Popup option causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=396210 --- Comment #1 from 3ndymion <3ndymio...@gmail.com> --- Created attachment 113783 --> https://bugs.kde.org/attachment.cgi?id=113783=edit A picture showing the popup menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381486] Switching activity don't change focus
https://bugs.kde.org/show_bug.cgi?id=381486 André Vitor de Lima Matos changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #2 from André Vitor de Lima Matos --- Can confirm this happens. I think it may be related to the "Remember the current virtual desktop for each activity (needs restart)", as looks like the problem is triggered more often when switching activities also makes the desktop switch: the focused window in the later desktop on the former activity receives the focus while not shown (as the window shown is the focused window on the later desktop on the later activity). Focus Stealing Prevention is None, and Focus policy is Click to Focus. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #10 from Mike Lothian --- Martin, you want people to switch to Wayland, you've made clear that X11 is in maintenance only How on earth are people supposed to use Wayland as a daily driver when switching causes issues? I realise this bug might now be in kwin_wayland itself - it could possibly be in SDDM or some other component, but currently when I first start this machine with wayland it does one thing and when I restart the session it does another - that I hope you can see is a bug You say start a proper wayland session but you don't say _how_ if I'm making a mistake, please point it out. I was under the impression that simply changing the default session in SDDM was enough -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396210] New: Disable This Popup option causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=396210 Bug ID: 396210 Summary: Disable This Popup option causes plasma to crash. Product: plasmashell Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: 3ndymio...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: When I try to copy a file in Dolphin, either with the right-click menu "copy" or with Control-C, a pop up menu appears, showing Kate, Kwrite, & a couple of other things. One of the options is "Disable This Popup". Choosing that option causes plasma to completely crash. This popup menu seems to be part of the clipboard. I have never seen this before. I don't know why this strange popup suddenly started appearing, but it is very annoying. Copying a file does not require an extra popup menu after copying the file. Any help on how to get rid of this, & fixing the bug, would be greatly appreciated. Thanks. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd8ed65dc0 (LWP 9874))] Thread 8 (Thread 0x7fccc11cc700 (LWP 10131)): #0 0x7fcd87e7bea9 in poll () at /usr/lib/libc.so.6 #1 0x7fcd819e6523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd819e663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd88798054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fcd8874394c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fcd8858ca99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fccc3b7e1da in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fcd88596b45 in () at /usr/lib/libQt5Core.so.5 #8 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fccd4a5f700 (LWP 10033)): #0 0x7fcd819e3332 in () at /usr/lib/libglib-2.0.so.0 #1 0x7fcd819e5983 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd819e644e in () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd819e663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fcd88798054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fcd8874394c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fcd8858ca99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fcd8c50223b in () at /usr/lib/libQt5Quick.so.5 #8 0x7fcd88596b45 in () at /usr/lib/libQt5Core.so.5 #9 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fcce30fb700 (LWP 9959)): #0 0x7fcd8773affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcce368d124 in () at /usr/lib/dri/i965_dri.so #2 0x7fcce368ce18 in () at /usr/lib/dri/i965_dri.so #3 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fcd6dfae700 (LWP 9950)): #0 0x7fcd8773affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd8e44eaac in () at /usr/lib/libQt5Script.so.5 #2 0x7fcd8e44eac9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fcd6700 (LWP 9930)): #0 0x7fcd87e77934 in read () at /usr/lib/libc.so.6 #1 0x7fcd81a2bed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd819e5ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd819e64c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fcd819e663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fcd88798054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fcd8874394c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fcd8858ca99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fcd8c0859c9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fcd88596b45 in () at /usr/lib/libQt5Core.so.5 #10 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fcd75eab700 (LWP 9917)): #0 0x7fcd88797fa0 in () at /usr/lib/libQt5Core.so.5
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Martin Flöser changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INVALID --- Comment #9 from Martin Flöser --- Closing properly -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Martin Flöser changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383666] KCM Plymouth - error when changing theme
https://bugs.kde.org/show_bug.cgi?id=383666 --- Comment #3 from Mihai Sorin Dobrescu --- Sorry, I have not added the following info: - Plymouth 0.8.9_pre1-r3~0. - Plasma 5.47.0~0. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383666] KCM Plymouth - error when changing theme
https://bugs.kde.org/show_bug.cgi?id=383666 Mihai Sorin Dobrescu changed: What|Removed |Added CC||msdobre...@gmail.com --- Comment #2 from Mihai Sorin Dobrescu --- I can confirm on Sabayon, up to date - 64 bit, 4.16.0-sabayon #1 SMP Tue Jul 3 09:06:27 UTC 2018 x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396173] kwin_x11 --replace ignores other virtual desktops
https://bugs.kde.org/show_bug.cgi?id=396173 --- Comment #4 from magnus.gros...@gmail.com --- I didn't know you were the guy from latte. Thank you so much for your dock :) Well, if you don't know what's the problem, we will have to wait if someone else knows what may be the issue. Otherwise I will have to use `git bisect` to find the problematic commit between 5.12 and 5.13. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396201] MinimizeAll kwin script does not restore focus and alt+tab ordering
https://bugs.kde.org/show_bug.cgi?id=396201 --- Comment #3 from Till Schäfer --- ok, thx 4 info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396209] New: Reference image transform handles leave a trail
https://bugs.kde.org/show_bug.cgi?id=396209 Bug ID: 396209 Summary: Reference image transform handles leave a trail Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: antti.s...@gmail.com Target Milestone: --- Video demonstration: https://youtu.be/MEqBdcLNGto There's nothing more than what the video shows. I insert an image and move it around and it leaves a trail. The trail disappears if you drag the image below or to the right of the markings or if you click on any other tool Build & Platform: krita 4.2.0-pre-alpha (git c16dbae) Xubuntu 17.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395833] [Kicker/Kickoff] Some icons always re-pin after being un-pinned from Favorites
https://bugs.kde.org/show_bug.cgi?id=395833 Øystein Steffensen-Alværvik changed: What|Removed |Added Version|5.13.1 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395833] [Kicker/Kickoff] Some icons always re-pin after being un-pinned from Favorites
https://bugs.kde.org/show_bug.cgi?id=395833 --- Comment #1 from Øystein Steffensen-Alværvik --- Not just Kate, now Falkon won't unpin. I set it to be pinned on *all* Activities. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Mike Lothian changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|REOPENED --- Comment #8 from Mike Lothian --- When the bug is resolved to my satisfaction I'll close the bug How does one start a proper Wayland session? Is starting Plasma (Wayland) from SDDM not enough? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395833] [Kicker/Kickoff] Some icons always re-pin after being un-pinned from Favorites
https://bugs.kde.org/show_bug.cgi?id=395833 Øystein Steffensen-Alværvik changed: What|Removed |Added Summary|[Kicker/Kickoff] Kate |[Kicker/Kickoff] Some icons |always re-pins after being |always re-pin after being |un-pinned from Favorites|un-pinned from Favorites -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396170] Gallery creation error
https://bugs.kde.org/show_bug.cgi?id=396170 --- Comment #1 from Chris N D --- I have found a 'workaround' for this problem. Its a bit tedious but it works, viz: 1. Use showphoto with all the photos to create folders and thumbnails. 2. When it fails, repeat procedure but without the images that cause the failure. 3. Edit the index.html file to add in all the other images with their respective thumbnails. It still doesn't explain why the program thinks some of the images are dodgy though. Is it looking for particular tags somewhere? Chris -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396089] Calendar Bug advance about 10 days and KStars crashes.
https://bugs.kde.org/show_bug.cgi?id=396089 --- Comment #3 from Jasem Mutlaq --- Ok you specified "Ubuntu Packages" and "Linux" in the bug report. Will take a look at this, thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396201] MinimizeAll kwin script does not restore focus and alt+tab ordering
https://bugs.kde.org/show_bug.cgi?id=396201 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX Severity|normal |wishlist --- Comment #2 from Martin Flöser --- I'm sorry but the script does what it says: it minimized all windows and unminimizes them again. As soon as a window gets minimized it makes it impossible to restore the focus. What you are looking for is the show desktop functionality which keeps state. The minimize all script was added for those users who prefer minimize all instead of show desktop. Due to that it does exactly that. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396089] Calendar Bug advance about 10 days and KStars crashes.
https://bugs.kde.org/show_bug.cgi?id=396089 --- Comment #2 from VTVL --- On 05/07/18 15:35, Jasem Mutlaq wrote: > https://bugs.kde.org/show_bug.cgi?id=396089 > > --- Comment #1 from Jasem Mutlaq --- > I just tried all the above and none caused a crash. You have any backtrace > from > the crash? > I used this instruction: https://stackoverflow.com/questions/44954314/swift-debugging-on-linux-missing-backtrace ATTENTION: Great news though, there is a bash script which does all the work for you. Instruction's are slight, but this is what you need to do: Download this script: https://raw.githubusercontent.com/apple/swift/master/utils/symbolicate-linux-fatal Execute your crashing app. |$ myApp &>crash.log| Then execute the script. |$ ./symbolicate-linux-fatal myApp crash.log Adjusted: ||$ kstars %U &>crash.log| Then execute the script. |$ ./symbolicate-linux-fatal.sh kstars crash.log| The crash log is attached. -- John || -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Martin Flöser changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INVALID --- Comment #7 from Martin Flöser --- Please don't reopen the report. Your systemsettings is started as an X11 application and due to that not offering to change resolution. Please use a proper Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396173] kwin_x11 --replace ignores other virtual desktops
https://bugs.kde.org/show_bug.cgi?id=396173 --- Comment #3 from Michail Vourlakos --- (In reply to magnus.gross21 from comment #2) > (In reply to Michail Vourlakos from comment #1) > I hope that helps, do you have any idea what could be the cause for this? propably something in KWin behavior but I dont know what. It reminds me an issue that I had with upcoming version of Latte. In upcoming version of Latte (v0.8) it is supported different Latte docks at different Activties. Every time an Activity was closed the Latte docks even at other Activities were become invisible. I had to add a workaround internally in Latte code in order to catch the case and enforce to be visible again. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395520] Konsole KPart blur does not work/incorrect warning message
https://bugs.kde.org/show_bug.cgi?id=395520 --- Comment #4 from Christian Muehlhaeuser --- If that's the case, why is there a "Blur" setting in the profile setting? Shouldn't it be an application setting then? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396173] kwin_x11 --replace ignores other virtual desktops
https://bugs.kde.org/show_bug.cgi?id=396173 --- Comment #2 from magnus.gros...@gmail.com --- (In reply to Michail Vourlakos from comment #1) > 1. Have you tried to disable in Latte filtering based on desktops that can > be found at Tasks configuration tab? > 2. Just to confirm, after the switch to kwin the windows for desktop 2 are > not accesible in any way e.g. Alt+Tab? > 3. If you use ksysguard are the windows that can not be accessed still > running or they have been closed during the switch? First, thanks for answering so quickly. 1. Yes, that is the setting that I use Latte all the time with. 2. Yes, the windows are completely lost. They appear neither in Latte nor in Alt+Tab (yes, i made sure alt+tab doesn't filter for desktops or activities) 3. The process is still alive. As such I see it in ksysguard and if I click on `Show Application Window`, the window magically appears on the current desktop and is both visible in Latte and Alt+Tab again. Note that if I didn't click on `Show Application Window` and the window is still lost in KDE, if I then switch to bspwm with `bspc wm -o`, bspwm will find the lost window again on its own and put it on the current desktop. I hope that helps, do you have any idea what could be the cause for this? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389012] Support snap channels
https://bugs.kde.org/show_bug.cgi?id=389012 Aleix Pol changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dis ||cover/67293df0f26ff8a4497dc ||5596df3a8aa1a04f021 Resolution|--- |FIXED --- Comment #2 from Aleix Pol --- Git commit 67293df0f26ff8a4497dc5596df3a8aa1a04f021 by Aleix Pol. Committed on 05/07/2018 at 15:39. Pushed by apol into branch 'master'. Snap: Support configuring used snap channels Adds a dialog that allows to choose the channel in use for a snap. M +97 -3libdiscover/backends/SnapBackend/SnapResource.cpp M +16 -1libdiscover/backends/SnapBackend/SnapResource.h A +58 -0libdiscover/backends/SnapBackend/qml/ChannelsButton.qml [License: BSD] M +1-0libdiscover/backends/SnapBackend/snapui.qrc M +10 -0libdiscover/utils.h https://commits.kde.org/discover/67293df0f26ff8a4497dc5596df3a8aa1a04f021 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 396208] New: Can't open .xmi file from smb remote location
https://bugs.kde.org/show_bug.cgi?id=396208 Bug ID: 396208 Summary: Can't open .xmi file from smb remote location Product: umbrello Version: 2.25.2 (KDE Applications 18.04.2) Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: wzygmuntowicz.zygmuntow...@gmail.com Target Milestone: --- Created attachment 113781 --> https://bugs.kde.org/attachment.cgi?id=113781=edit output_with_screenshots The problem is every time I try to open file from smb remote location I get the error "The file does not exist.". It only works when I mount the smb share manually and then open the same file. In the attachment there is an output from console where I typed "umbrello5 2>&1 | tee umbrello.log" (the moment when I tried to open is near the 103th line) and three screenshots presenting what I have been doing. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 394274] Akonadi not start
https://bugs.kde.org/show_bug.cgi?id=394274 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Daniel Vrátil --- Hi, thanks for the report. Could you please provide more details? What happens when you open the Konsole, and run the following command: QT_LOGGING_RULES="*=true" akonadictl start Does Kontact become usable afterwards? If not, could you please copy here the stuff that the the command above prints? Thanks -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 396207] New: please make Help Center 'handbook searchable'
https://bugs.kde.org/show_bug.cgi?id=396207 Bug ID: 396207 Summary: please make Help Center 'handbook searchable' Product: khelpcenter Version: 5.7.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: erben...@comcast.net Target Milestone: --- Help center only searches the currently visible page. The search should be able to find topics and other words via searching the entire handbook (stay withi9n the application handbook). For example, if I bring up the Kate Handbook I should be able to find any page in the handbook that contains the word (or partial word) 'diff' in it so i can find out about Kates diff view but it should not bring up other applications info. I dont want info on the command line app diff for example only as it relates to Kate (in my example) although this could be some kind of checkbox option much like 'man -K' -- You are receiving this mail because: You are watching all bug changes.
