[korganizer] [Bug 364200] New: korganizer 5.1.3 does not save change of appointment date.
https://bugs.kde.org/show_bug.cgi?id=364200 Bug ID: 364200 Summary: korganizer 5.1.3 does not save change of appointment date. Product: korganizer Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: h6zb8-kdebugs20120...@yahoo.de When I want to change the date of an appointment in korganizer 5.1.3 and type it (keyboard), and hit the ok button, the new date is not saved, instead it keeps the old date. I expect it to save the new date. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro
https://bugs.kde.org/show_bug.cgi?id=342105 Rastaban26changed: What|Removed |Added CC||regulus2...@gmail.com --- Comment #32 from Rastaban26 --- I'm also experiencing this problem with the release version of Krita 3.0. Using Huion 610. Also middle mouse button (used from the stylus) is not working. Proposed workarounds are working fine for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 jameschanged: What|Removed |Added CC||jamesonr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #113 from Mohammed Arafa--- i take back what i said about it being fixed. this bug is random incarnate. when i unplug the laptop from the docking station, most times (i am generalising here) i will get my screen back. when i plug the laptop back into the docking station, sometimes i will get my screen. sometimes i have to switch vt to a console to get my screen, and sometimes the panel is missing and sometimes the panel is one third of the screen up. and when the panel is up there, sometimes, the plasmashell_hack.sh up there in one of the comments will work and sometimes not. when it doesnt i have to kill -9 plasmashell and then rerun the script twice (1st time coz it doesnt find the program in binary) so yeah, its a close relative of /dev/random which makes me think it is also related to /dev/null! -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 338012] Eclipse crashes in debug mode and using oxygen-gtk
https://bugs.kde.org/show_bug.cgi?id=338012 daniel.armbrust.l...@gmail.com changed: What|Removed |Added CC||daniel.armbrust.list@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 301622] Mouse pointer gets huge if a second large screen is connected
https://bugs.kde.org/show_bug.cgi?id=301622 daniel.armbrust.l...@gmail.com changed: What|Removed |Added CC||daniel.armbrust.list@gmail. ||com --- Comment #30 from daniel.armbrust.l...@gmail.com --- Can confirm this issue as well. The workaround of setting the mouse size to 24 only works temporarily, and oversize mouse pointers keep coming back at random times. Is there any way to forcibly disable the dynamic mouse sizing? Next best option, is there a way I can hack up a mouse theme such that it only has size 24 cursors? I've tried to find a different cursor set that is only offered in one size... but so far no luck (but it seems 80 percent of the cursor themes available in the them picker don't work at all - not sure if that has been a good test) Right now, I just have to keep going back to the settings dialog multiple times a day and toggling the mouse pointer size. -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 364199] Background Contrast and Blur desktop animation causes desktop element overlay when using kmag
https://bugs.kde.org/show_bug.cgi?id=364199 --- Comment #3 from Justin Campbell--- I made a mistake in my original posting. The issue is not with kmag itself, rather the Zoom desktop animation. -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 364199] Background Contrast and Blur desktop animation causes desktop element overlay when using kmag
https://bugs.kde.org/show_bug.cgi?id=364199 --- Comment #2 from Justin Campbell--- Created attachment 99449 --> https://bugs.kde.org/attachment.cgi?id=99449=edit Expected result A view of Konsole listing systemd unit files while zoomed in without Background Contrast or Blur desktop annimation enabled -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 364199] Background Contrast and Blur desktop animation causes desktop element overlay when using kmag
https://bugs.kde.org/show_bug.cgi?id=364199 --- Comment #1 from Justin Campbell--- Created attachment 99448 --> https://bugs.kde.org/attachment.cgi?id=99448=edit Actual results A view of Konsole listing systemd unit files while zoomed in with the default bottom panel and application menu outlines displayed when those elements are not part of the magnified screen area. It should be noted that the application menu was purposefully opened and does not always show on the screen. This was to demonstrate the problem. -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 364199] New: Background Contrast and Blur desktop animation causes desktop element overlay when using kmag
https://bugs.kde.org/show_bug.cgi?id=364199 Bug ID: 364199 Summary: Background Contrast and Blur desktop animation causes desktop element overlay when using kmag Product: kmag Version: 0.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: sar...@users.sourceforge.net Reporter: jtcm...@gmail.com While the Background Contrast and/or the Blur desktop animation is enabled, UI elements from the desktop remain persistent on the screen regardless of the zoom level. By disabling both of these animations, it makes using the magnifier quite usable. However, this makes using transparent elements difficult as the text is no longer on a blurred background. Reproducible: Always Steps to Reproduce: 1. Have Plasma >=5 2. Have Background Contrast and/or Blur desktop animation enabled 3. Zoom in using kmag in fullscreen mode Actual Results: See screenshot 1 Expected Results: See screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362991] Undesired empty space appears in panel layout
https://bugs.kde.org/show_bug.cgi?id=362991 tfkcp...@sharklasers.com changed: What|Removed |Added CC||tfkcp...@sharklasers.com --- Comment #6 from tfkcp...@sharklasers.com --- I confirm the bug exists. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 362902] Kdenlive crashes when adding volume effect from audio and preview it
https://bugs.kde.org/show_bug.cgi?id=362902 Shanechanged: What|Removed |Added CC||cont...@shane-brown.ca --- Comment #4 from Shane --- Also getting this in Arch Linux 64-bit with kdenlive 16.04.1 when applying volume effect to audio track. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364198] New: Item missing in icons-only task manager on a resizable panel when widgets unlocked.
https://bugs.kde.org/show_bug.cgi?id=364198 Bug ID: 364198 Summary: Item missing in icons-only task manager on a resizable panel when widgets unlocked. Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: igs...@gmail.com CC: plasma-b...@kde.org I have created a panel that I use as a dock (looks somewhat similar to the Docky app or the OS X dock). This panel basically have an Application Dashboard widget and Icons-only task manager. The panel is placed on the bottom edge of the screen and centered, and both minimum and maximum sizes are set. The icons-only task manager item has some launchers pinned. When I open a new app that doesn't have a launcher pinned, and the widgets aren't locked, the last entry in the task manager is missing (it's probably hidden in an invisible row, though I have set the maximum row numbers to 1). When the widgets are locked, all items are present in the task manager, but there is a tiny gap between the last item and the right edge of the panel (tolerable but ugly). Reproducible: Always Steps to Reproduce: 1. Create a panel. 2. Put Application Dashboard and Icons-only task manager onto it 3. Set minimum and maximum sizes to the panel 4. Pin some launchers to the task manager (so that their total width is more than the minimum width of the panel) 5. Set maximum number of rows to 1. 6. Open a new app that doesn't have a pinned launcher. 7. If widgets unlocked, the last unpinned entry is missing. Actual Results: The last item in the Icons-only task manager is missing Expected Results: The last item in the Icons-only task manager should be shown I'm using plasma 5.6 with Kubuntu 16.04 (installed from the backports rep), though the issue was there for the default (older) plasma version as well. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 364197] New: Autodetect plugged in USB LTE modem and ask the user for country and provider
https://bugs.kde.org/show_bug.cgi?id=364197 Bug ID: 364197 Summary: Autodetect plugged in USB LTE modem and ask the user for country and provider Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: lu...@kde.org Reporter: d33...@gmail.com CC: jgrul...@redhat.com My sister recently complained to me that she couldn't figure out how to connect her USB LTE modem on KDE 4 on Fedora. I checked and the steps were to: Reproducible: Always Steps to Reproduce: Under KDE 4, the steps to configure the device are: 1. Plug in the device, 2. Open the network manager applet, 3. Click on the settings icon, 4. Add a new connection, 5. Out of a myriad of options, select one related to mobile internet, 6. Select the device, 7. Pick a country, 8. Select an ISP, 9. Assume it's all fine and just click OK in the "connection details" window. Actual Results: I'm not sure what is the process like under KDE 5, but I assume it's similar. Expected Results: Could it be possible to show a pop-up instead that would say "hey, we detected a USB modem. Select your country and ISP. If you need to enter some additional settings, such as login credentials, clicked >>advanced settings>>"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #112 from Olivier Churlaud--- I realized that now, if I unplug my second screen, the panel disappear. I add a new panel (default one) and my panel comes back and the new is added. I can then remove the new one. So it seems it is just a problem of displaying the panels? Every other applet is at the right place and doesn't disappear. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 362476] No device listed in KCM Phonon, when Pulseaudio is disabled
https://bugs.kde.org/show_bug.cgi?id=362476 mathoj...@gmail.com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 362476] No device listed in KCM Phonon, when Pulseaudio is disabled
https://bugs.kde.org/show_bug.cgi?id=362476 --- Comment #4 from mathoj...@gmail.com --- Comment on attachment 99447 --> https://bugs.kde.org/attachment.cgi?id=99447 Not working AS you can see, I can add the same screeshot Yes we have a device listed : Default . But it's not really a device ! When selected, I still have no sound. And even if I had sound, the list is not correct as I have 2 soundcards. And one of them has a lot of inputs and outputs. In the past, when pulseaudio was disabled, phonon listed a big list of devices... and not just this default device which is nothing interesting and usable. I'm using the ubuntu repository version of phonon : 4.8.3 No, it's not working fine, and the bug is still active ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364193] Digikam5 crashed at start of the program all time. It worked fine until 2016-06-05
https://bugs.kde.org/show_bug.cgi?id=364193 --- Comment #2 from cd.graes...@gmail.com --- Am fredag 10 juni 2016, kl. 19:49:26 CEST schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=364193 > > --- Comment #1 from Maik Qualmann--- > Please rename the $HOME/.config/digikamrc. I had a similar crash a few weeks > ago already. It would then interesting which option caused this crash. > > Maik > > thanks Maik, Digikam5 is working again. I'll try to find if there is any systematic behavior behind, Have a nice weekend Christian -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 362476] No device listed in KCM Phonon, when Pulseaudio is disabled
https://bugs.kde.org/show_bug.cgi?id=362476 --- Comment #3 from mathoj...@gmail.com --- Created attachment 99447 --> https://bugs.kde.org/attachment.cgi?id=99447=edit Not working -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 Romanchanged: What|Removed |Added CC||subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355463] xembedsniproxy always crash when login
https://bugs.kde.org/show_bug.cgi?id=355463 Alejandro Villarchanged: What|Removed |Added CC||alx5...@alx5000.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354823] Plasma crashes on multiscreen setup activation
https://bugs.kde.org/show_bug.cgi?id=354823 Alejandro Villarchanged: What|Removed |Added CC||alx5...@alx5000.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364196] KWin crashed when clicked on icon in panel
https://bugs.kde.org/show_bug.cgi?id=364196 Thomas Lübkingchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Thomas Lübking --- see the first comment on the dupe. *** This bug has been marked as a duplicate of bug 363224 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358133] KWin Crashed After Resuming from Idle
https://bugs.kde.org/show_bug.cgi?id=358133 Thomas Lübkingchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Flags||NVIDIA+ Resolution|--- |UPSTREAM --- Comment #12 from Thomas Lübking --- Thanks for the update, however please notice that this bug can be heuristic (due to memory decay in the GPU) #344326 will likely be resolved by listening to NV_robustness_video_memory_purge once it's provided and utilized in kwin. For the time being, let's hope nvidia acts more robust wrt to their memory. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 Thomas Lübkingchanged: What|Removed |Added CC||b.gatessu...@gmail.com --- Comment #4 from Thomas Lübking --- *** Bug 364196 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364196] New: KWin crashed when clicked on icon in panel
https://bugs.kde.org/show_bug.cgi?id=364196 Bug ID: 364196 Summary: KWin crashed when clicked on icon in panel Product: kwin Version: 5.6.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: b.gatessu...@gmail.com Application: kwin_x11 (5.6.4) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.5.6-200.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: Clicked on icon in panel to start a (commercial) application -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbe1215d940 (LWP 28752))] Thread 6 (Thread 0x7fbe091de700 (LWP 28778)): #0 0x7fbe224b48a3 in select () at /lib64/libc.so.6 #1 0x7fbe23a0d29f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fbe23a0ecde in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /lib64/libQt5Core.so.5 #3 0x7fbe23a0f1f2 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fbe239ba4ca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fbe237e3f34 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fbe24d164b5 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fbe237e8d48 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fbe2521561a in start_thread () at /lib64/libpthread.so.0 #9 0x7fbe224be59d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fbe03124700 (LWP 28786)): #0 0x7fbe224b48a3 in select () at /lib64/libc.so.6 #1 0x7fbe23a0d29f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fbe23a0ecde in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /lib64/libQt5Core.so.5 #3 0x7fbe23a0f1f2 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fbe239ba4ca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fbe237e3f34 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fbe29ee9985 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fbe237e8d48 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fbe2521561a in start_thread () at /lib64/libpthread.so.0 #9 0x7fbe224be59d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fbde700 (LWP 28787)): #0 0x7fbe2521ab20 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbdf79a2fc3 in radeon_drm_cs_emit_ioctl () at /usr/lib64/dri/r600_dri.so #2 0x7fbdf79a2717 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7fbe2521561a in start_thread () at /lib64/libpthread.so.0 #4 0x7fbe224be59d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fbdef7fe700 (LWP 28789)): #0 0x7fbe224b48a3 in select () at /lib64/libc.so.6 #1 0x7fbe23a0d29f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fbe23a0ecde in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /lib64/libQt5Core.so.5 #3 0x7fbe23a0f1f2 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fbe239ba4ca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fbe237e3f34 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fbe29ee9985 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fbe237e8d48 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fbe2521561a in start_thread () at /lib64/libpthread.so.0 #9 0x7fbe224be59d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fbded7fb700 (LWP 28792)): #0 0x7fbe2521ab20 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbe2aebf2d4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fbe2aebf319 in () at /lib64/libQt5Script.so.5 #3 0x7fbe2521561a in start_thread () at /lib64/libpthread.so.0 #4 0x7fbe224be59d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fbe1215d940 (LWP 28752)): [KCrash Handler] #5 0x0018 in () #6 0x7fbe239eede0 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /lib64/libQt5Core.so.5 #7 0x7fbe2af01dbf in QScriptEnginePrivate::qobjectData(QObject*) () at /lib64/libQt5Script.so.5 #8 0x7fbe2af01e84 in QScriptEnginePrivate::newQObject(QObject*, QScriptEngine::ValueOwnership, QFlags const&) () at /lib64/libQt5Script.so.5 #9 0x7fbe2af02112 in QScriptEngine::newQObject(QObject*,
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #54 from Stephan Diestelhorst--- For me mysql complained about "You can't specify target for update in FROM clause". Wrapping things into another layer of SELECT did the trick: DELETE FROM pimitemtable WHERE pimitemtable.id in ( SELECT id FROM ( SELECT id FROM pimitemtable LEFT OUTER JOIN ( SELECT MIN(pimitemtable.id) as RowId, pimitemtable.remoteId, pimitemtable.collectionId FROM pimitemtable GROUP by pimitemtable.remoteId, pimitemtable.collectionId ) as KeepRows ON pimitemtable.id = KeepRows.RowId WHERE KeepRows.RowId IS NULL) AS foo) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 346608] Use Breeze Dark theme as program's default look?
https://bugs.kde.org/show_bug.cgi?id=346608 faridchanged: What|Removed |Added Attachment #99446|No icons without plasma |No icons without description|installed. |oxygen-icons installed. --- Comment #47 from farid --- Comment on attachment 99446 --> https://bugs.kde.org/attachment.cgi?id=99446 No icons without oxygen-icons installed. Shouldn't Breeze icons suffice? Or you need both? This should be clear for packagers -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 346608] Use Breeze Dark theme as program's default look?
https://bugs.kde.org/show_bug.cgi?id=346608 --- Comment #46 from farid--- Created attachment 99446 --> https://bugs.kde.org/attachment.cgi?id=99446=edit No icons without plasma installed. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364194] Now way to tell windows apart and to find which window is active when compositing is off
https://bugs.kde.org/show_bug.cgi?id=364194 Hugo Pereira Da Costachanged: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com --- Comment #2 from Hugo Pereira Da Costa --- Hi Ruslan, Agreed, this was not ported. You can however uncheck the new option "use the same color for the titlebar and the window content" This will make the decoration use the "active" and "inactive" colors, and fix the issue (in the same way as breeze does) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364193] Digikam5 crashed at start of the program all time. It worked fine until 2016-06-05
https://bugs.kde.org/show_bug.cgi?id=364193 --- Comment #1 from Maik Qualmann--- Please rename the $HOME/.config/digikamrc. I had a similar crash a few weeks ago already. It would then interesting which option caused this crash. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364193] Digikam5 crashed at start of the program all time. It worked fine until 2016-06-05
https://bugs.kde.org/show_bug.cgi?id=364193 Maik Qualmannchanged: What|Removed |Added Platform|unspecified |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364193] Digikam5 crashed at start of the program all time. It worked fine until 2016-06-05
https://bugs.kde.org/show_bug.cgi?id=364193 Maik Qualmannchanged: What|Removed |Added Component|general |general Version|unspecified |5.0.0 CC||metzping...@gmail.com Product|kde |digikam Assignee|unassigned-b...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363487] brush lags behind when making quick or long strokes
https://bugs.kde.org/show_bug.cgi?id=363487 --- Comment #13 from William Kensinger--- (In reply to Boudewijn Rempt from comment #12) > Since you're using an AMD card, can you check whether disabling the texture > buffer option makes a difference? Just tried that with what appears to be the newest build. No difference. Bizarrely enough, when attempting to test this, it took the bug the better part of an hour to manifest at all. It simply wasn't happening for awhile. I can't even begin to guess why that might be, since up until now it's appeared almost immediately after starting up the program. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358133] KWin Crashed After Resuming from Idle
https://bugs.kde.org/show_bug.cgi?id=358133 --- Comment #11 from Thierry--- Hi Thomas! Big update yesterday including the Nvidia drivers on openSUSE 42.1 Leap. What gives me as config: KDE Plasma: 5.6.4 KDE Frameworks: 5.22.0 Qt: 5.6.0 Kernel: 4.1.21-14-default Nvidia driver: 367.18 I can not reproduce the bug despite a dozen tests. The old version of the driver is, for me, the cause of the problems. Thank you for your help and consideration bug! Cordially -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364105] git master - Freezing then crashing when adding video clip to Project Bin
https://bugs.kde.org/show_bug.cgi?id=364105 --- Comment #6 from Jesse--- Created attachment 99445 --> https://bugs.kde.org/attachment.cgi?id=99445=edit backtrace data -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364105] git master - Freezing then crashing when adding video clip to Project Bin
https://bugs.kde.org/show_bug.cgi?id=364105 Jessechanged: What|Removed |Added CC||jesse.dub...@gmail.com --- Comment #5 from Jesse --- Restarting my PC fixed the backtrace issue. Including the data in an attachment. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364195] git master - crashes when trying to run in Mint 18 beta (backtrace included)
https://bugs.kde.org/show_bug.cgi?id=364195 --- Comment #3 from Jesse--- Of course! Thanks JB. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363487] brush lags behind when making quick or long strokes
https://bugs.kde.org/show_bug.cgi?id=363487 --- Comment #12 from Boudewijn Rempt--- Since you're using an AMD card, can you check whether disabling the texture buffer option makes a difference? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 340736] Very slow performance while changing layer orders
https://bugs.kde.org/show_bug.cgi?id=340736 --- Comment #22 from Boudewijn Rempt--- Hm, the file you sent me worked fine for me, but it's smaller than what you describe above. It also doesn't take oodles of memory. I've got another report about a file that matches your description and that went from taking 3gb of memory to 13gb, so when Dmitry is back from his vacation and has finished the gif exporter, I'll ask him to take a look. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 --- Comment #9 from Thomas Pfeiffer--- (In reply to Martin Steigerwald from comment #8) > Entirely your choice and in the end I don´t care, cause I do not intend to > use Neon. Yet, you mask bugs this way. Sure, I'm all for fixing the misbehaving applications, but "Let's expose other people's fuck-ups so they'll fix them" has not been a very successful approach for us in the past. Usually what happens is that those who fucked up don't do anything about it, and our users blame _us_ for the problems. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 329884] Color Scheme as per Activity Setting (kf5)
https://bugs.kde.org/show_bug.cgi?id=329884 Mircea Kitsunechanged: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 --- Comment #8 from Martin Steigerwald--- Entirely your choice and in the end I don´t care, cause I do not intend to use Neon. Yet, you mask bugs this way. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364195] git master - crashes when trying to run in Mint 18 beta (backtrace included)
https://bugs.kde.org/show_bug.cgi?id=364195 --- Comment #2 from Jean-Baptiste Mardelle--- The crash happens in VirtualBox's OpenGL driver. I made a few changes this morning to copy come behavior from Shotcut in the OpenGL code. Can you try when the PPA get updated ? If it still crashes I would like to know if Shotcut works in VirtualBox... maybe there are some OpenGL limitations... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 345403] "Terminal Size" setting in profile ignored
https://bugs.kde.org/show_bug.cgi?id=345403 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 359662] Terminal Rows are miscalculated if Menu Bar is turned off
https://bugs.kde.org/show_bug.cgi?id=359662 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363365] button "open" clicked from active remote sftp file tries to open nonexistent directory.
https://bugs.kde.org/show_bug.cgi?id=363365 Matt Lewischanged: What|Removed |Added CC||matthewwalkerle...@gmail.co ||m --- Comment #1 from Matt Lewis --- Also, if you have a remote document open and try to open another one from the same place you get the same message. I can then click on the actual directory in the file browser and open something from that directory. sftp: host > path > to > file > actual > directory > currentlyopenedfile.txt The dialog should just come up showing the stuff in path/to/file/actual/directory. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363739] Brush lag at zoom level 50 below
https://bugs.kde.org/show_bug.cgi?id=363739 William Kensingerchanged: What|Removed |Added CC||will89...@gmail.com --- Comment #10 from William Kensinger --- Just dropping in to say that this bug might be either related to, or a duplicate of, a bug I filed a little while ago: https://bugs.kde.org/show_bug.cgi?id=363487 Looking at the how the brush behaves, it does look like it performs much worse at below 50%, though it's the issue present at higher zoom levels for me. I haven't seen any odd behavior coming from the overview docker, but I wouldn't rule it out either since I don't use it too much. Most interesting to me, and what tells me that this might be the same bug, is that we have very similar graphics cards. My card is an ASUS Radeon R9 280X, which is apparently an AMD-based card from the same series. On a slightly-unrelated note, the bug I linked appears to be mislabeled as resolved, since I initially reported it as possibly fixed, when its behavior changed after I updated my graphics drivers. I should probably set that to something else, but I can't figure out for the life of me what I should relabel it to. Regardless, thanks for your time everyone, and here's to getting this bug solved! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364195] git master - crashes when trying to run in Mint 18 beta (backtrace included)
https://bugs.kde.org/show_bug.cgi?id=364195 --- Comment #1 from Jesse--- Created attachment 99444 --> https://bugs.kde.org/attachment.cgi?id=99444=edit Backtrace data pertaining to this crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364195] git master - crashes when trying to run in Mint 18 beta (backtrace included)
https://bugs.kde.org/show_bug.cgi?id=364195 Jessechanged: What|Removed |Added CC||jesse.dub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364195] New: git master - crashes when trying to run in Mint 18 beta (backtrace included)
https://bugs.kde.org/show_bug.cgi?id=364195 Bug ID: 364195 Summary: git master - crashes when trying to run in Mint 18 beta (backtrace included) Product: kdenlive Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jesse.dub...@gmail.com I know it's in beta, but it should still run off the ppa in Ubuntu-based Mint, yeah? When I try to run it, it goes through the wizard, but once it gets to the main window, Kdenlive crashes. See attached text file with backtrace data. Reproducible: Always Steps to Reproduce: 1. Terminal command: sudo apt-add-repository ppa:kdenlive/kdenlive-master 2. Terminal command: sudo apt install kdenlive 3. Run kdenlive from terminal or application launcher 4. Go through the initial start-up wizard Actual Results: Kdenlive crashes. Expected Results: Kdenlive doesn't crash, but goes into the main window. Bug discovered while using Linux Mint 18 beta x64 in Virtualbox VM -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364105] git master - Freezing then crashing when adding video clip to Project Bin
https://bugs.kde.org/show_bug.cgi?id=364105 --- Comment #4 from Jesse--- I got the bug to reoccur consistently, but trying to run "thread apply all bt full" in gdb gives this error: "thread apply all bt full". Any ideas how I can fix this to get the backtrace data? I tried both the backtrace technique from the link you gave me and from an e-mail Paul Konecny sent me a while back: 1. Install gdb (the GNU debugger) 2. open a terminal and run "gdb kdenlive" 3. wait till it says "reading symbols for kdenlive ... done" 4. the gdb shell (gdb) appears 5. tell it where to log with "set logging file /home/johndoe/janedoe.log" 6. Turn logging on with "set logging on" 7. type "run" to start the program 8. When the crash happened it will say so in the gdb shell 9. To run a backtrace type "thread apply all bt full" and keep hitting enter until you're back to the gdb shell 10. type quit and confirm to kill the inferior process. 11. Done. Now you can attach the log file to the bug report ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364118] present windows alternate activation key does not toggle
https://bugs.kde.org/show_bug.cgi?id=364118 --- Comment #2 from Jason Tibbitts--- I'm not sure how long it's going to take for Wayland to actually become a viable alternative to X, though. So in the meantime, if you have any hints as to where in the source that toggling is implemented I'd be happy to take a look (unless you're already planning to look into this yourself, of course). The last time I wrote C++ was using cfront, but I can probably make something work. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364194] Now way to tell windows apart and to find which window is active when compositing is off
https://bugs.kde.org/show_bug.cgi?id=364194 --- Comment #1 from Ruslan Kabatsayev--- Created attachment 99443 --> https://bugs.kde.org/attachment.cgi?id=99443=edit Screenshot of the problem -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 364194] New: Now way to tell windows apart and to find which window is active when compositing is off
https://bugs.kde.org/show_bug.cgi?id=364194 Bug ID: 364194 Summary: Now way to tell windows apart and to find which window is active when compositing is off Product: Oxygen Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: win deco Assignee: hugo.pereira.da.co...@gmail.com Reporter: b7.10110...@gmail.com In KF5 oxygen window decorations now lack "ugly shadows" which in KDE4 served at least two purposes: 1. Visually separate different windows 2. Indicate which window is active (similarly to shadow vs glow) In KF5, since no ugly shadows are drawn, oxygen window decoration without compositing is unusable. I'll attach a screenshot. Reproducible: Always Steps to Reproduce: 1. Turn off compositing 2. Open System Settings, on a page where much of the background is system background color — e.g. Compositor page 3. Open Konsole, move the window over the one opened in step 2, so that Konsole top is near the top of System Settings window top 4. Try to tell: a) where Konsole window ends and System Settings starts b) which one is active when you move them apart so that they don't overlap Actual Results: Step 4 is quite hard to do. Expected Results: Step 4 should be at least as easy as it was in KDE4. Tested on stock Kubuntu 16.04 LiveISO. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364105] git master - Freezing then crashing when adding video clip to Project Bin
https://bugs.kde.org/show_bug.cgi?id=364105 --- Comment #3 from Jesse--- Ugh... of course it's an intermittent issue. When it comes up again, I'll get the backtrace and send it along. Running a few more tests to try and trigger it, now. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 364193] New: Digikam5 crashed at start of the program all time. It worked fine until 2016-06-05
https://bugs.kde.org/show_bug.cgi?id=364193 Bug ID: 364193 Summary: Digikam5 crashed at start of the program all time. It worked fine until 2016-06-05 Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: cd.graes...@gmail.com Application: digikam5 (5.0.0-beta6) Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Starting the program: Result in Terminal: with two crashes: fam@fam-gross:~$ digikam5 digikam.general: AlbumWatch use QFileSystemWatcher QFileSystemWatcher::removePaths: list is empty digikam.general: Database Parameters:Type: "QSQLITE"DB Core Name: "/home/fam/Bilder/digikam4.db"DB Thumbs Name: "/home/fam/Bilder/thumbnails-digikam.db"DB Face Name: "/home/fam/Bilder/recognition.db"Connect Options: ""Host Name: ""Host port:-1Internal Server: false Internal Server Path: ""Username: ""Password: "" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 7 digikam.coredb: Core database: makeUpdates 7 to 7 digikam.database: Creating new Location "" uuid "volumeid:?uuid=6a2a1e61-5e3e-4439-b249-a7a8882e9a16" digikam.database: Creating new Location "/home/fam/Bilder" uuid "volumeid:?uuid=77d737fb-bba6-4c33-80e9-18a1df1c7e99" digikam.database: Creating new Location "/home/fam/Naemi" uuid "volumeid:?uuid=77d737fb-bba6-4c33-80e9-18a1df1c7e99" digikam.database: Creating new Location "/home/fam/ChrHandySamsungSM-N9005" uuid "volumeid:?uuid=77d737fb-bba6-4c33-80e9-18a1df1c7e99" digikam.database: Creating new Location "/home/fam/ChrHandySamsungSM-N9208" uuid "volumeid:?uuid=77d737fb-bba6-4c33-80e9-18a1df1c7e99" digikam.database: Creating new Location "/home/fam/Dropbox" uuid "volumeid:?uuid=77d737fb-bba6-4c33-80e9-18a1df1c7e99" digikam.database: location for "" is available false digikam.database: location for "/home/fam/Bilder" is available true digikam.database: location for "/home/fam/Naemi" is available true digikam.database: location for "/home/fam/ChrHandySamsungSM-N9005" is available true digikam.database: location for "/home/fam/ChrHandySamsungSM-N9208" is available true digikam.database: location for "/home/fam/Dropbox" is available true KMemoryInfo: Platform identified : "LINUX" KMemoryInfo: TotalRam: 8274894848 digikam.general: Allowing a cache size of 200 MB digikam.thumbsdb: Thumbs database: have a structure version "3" digikam.general: Thumbnails database ready for use digikam.database: Complete scan (file scanning deferred) took: 2658 msecs. digikam.dimg: ("/usr/share/color/icc", "/home/fam/.local/share/icc") digikam.dimg: No X.org XICC profile installed for screen 0 digikam.general: Camera XML data: "/home/fam/.local/share/digikam/cameras.xml" digikam.facedb: Face database: have a structure version "2" digikam.facesengine: Face database ready for use digikam.facesengine: Face database ready for use digikam.geoiface: "setting backend marble" digikam.general: Stacked View Mode : 0 digikam.geoiface: "setting backend marble" digikam.general: "browse_album" digikam.general: "browse_tag" digikam.general: "browse_labels" digikam.general: "browse_date" digikam.general: "browse_timeline" digikam.general: "browse_search" digikam.general: "browse_fuzzysearch" digikam.general: "browse_gpssearch" digikam.general: "browse_people" QFSFileEngine::open: No file name specified digikam.dimg: variant: QVariant(Digikam::LensFunIface::DevicePtr, ) digikam.dimg: dev: Asahi Optical Co.,Ltd :: Pentax Optio 430 :: 4.85 digikam.dimg: Search for camera "" - "" ==> false digikam.dimg: Search for lens "" ==> false digikam.dimg: updating data digikam.dimg: updating data digikam.general: Using 4 CPU core to run threads digikam.general: new search text settings: "" : hasResult = false , validRows = 0 QFSFileEngine::open: No file name specified digikam.widgets: Paths to color scheme : ("/usr/share/color-schemes") digikam.widgets: "Honeycomb" :: "/usr/share/color-schemes/Honeycomb.colors" digikam.widgets: "Honeycomb" :: "/usr/share/color-schemes/Honeycomb.colors" QFSFileEngine::open: No file name specified digikam.geoiface: digikam.general: Added root album called: "" digikam.general: Added root album called: "BilderCGlokal" digikam.general: Added root album called: "Naemi"
[amarok] [Bug 363929] Unreadable cyrillic tags when playing online stream
https://bugs.kde.org/show_bug.cgi?id=363929 --- Comment #3 from Myriam Schweingruber--- It is relevant insofar that it confirms the stream doesn't send UTF encoded tracks, but using the old obsolete ISO encoding. You should report this problem to the stream owners and ask them to encode their streams correctly. ISO is obsolete since the 1990ies ... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 249107] kdevelop crashes on startup
https://bugs.kde.org/show_bug.cgi?id=249107 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 214326] kdevelop crashes at startup
https://bugs.kde.org/show_bug.cgi?id=214326 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 340736] Very slow performance while changing layer orders
https://bugs.kde.org/show_bug.cgi?id=340736 --- Comment #21 from Janne Vuollet--- Updating a bit. Tried the file on surface pro 4. File worked fine, was compeletely workable. I think this surface is more powerfull than my laptop anyways so that might explain it. I then loaded the final psd I made with photoshop and it loaded as well. A bit slowly but eventually it did, wich is actually pretty awesome. That file however had one of those nested groups that recreated the problem. When moving single layers around everything is fine, but when trying to move that large nested group, krita goes unresponsive. Krita will unfreeze after I release the layers but I have no idea where it will end up in the layer stack. It feels like Krita is trying to select all individual layers at once rather than think the layer group as one single selection and move them around all the time while I'm deciding where to put them (yeah I don't understand the technicalities 8D) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364190] New: KDE not run
https://bugs.kde.org/show_bug.cgi?id=364190 Bug ID: 364190 Summary: KDE not run Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: samurai.unn...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.21-14-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: When I log does not start the KDE desktop environment and the screen is black The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1a5b9a77c0 (LWP 2167))] Thread 7 (Thread 0x7f1a4377e700 (LWP 2169)): #0 0x7f1a54e3bbbd in poll () at /lib64/libc.so.6 #1 0x7f1a59de2422 in () at /usr/lib64/libxcb.so.1 #2 0x7f1a59de400f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f1a45f373c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f1a5553a32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f1a546370a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1a54e43fed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1a3ff16700 (LWP 2171)): #0 0x7f1a54e3bbbd in poll () at /lib64/libc.so.6 #1 0x7f1a514aae64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1a514aaf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1a5576cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f1a55713d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f1a5553561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f1a5887fe18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f1a5553a32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f1a546370a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f1a54e43fed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1a3825e700 (LWP 2172)): #0 0x7f1a54e37c8d in read () at /lib64/libc.so.6 #1 0x7f1a514ebb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1a514aa999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1a514aadf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f1a514aaf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1a5576cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f1a55713d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f1a5553561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f1a5887fe18 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f1a5553a32f in () at /usr/lib64/libQt5Core.so.5 #10 0x7f1a546370a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f1a54e43fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f1a369de700 (LWP 2173)): #0 0x7f1a55532ccf in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f1a5576ccc5 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f1a514aa4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1a514aad80 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f1a514aaf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1a5576cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f1a55713d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f1a5553561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f1a5887fe18 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f1a5553a32f in () at /usr/lib64/libQt5Core.so.5 #10 0x7f1a546370a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f1a54e43fed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f1a35056700 (LWP 2174)): #0 0x7f1a5463b03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1a5b07a86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f1a5b07a899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f1a546370a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f1a54e43fed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f19b1a4e700 (LWP 2178)): #0 0x7f1a54e37c8d in read () at /lib64/libc.so.6 #1 0x7f1a514ebb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1a514aa999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1a514aadf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f1a514aaf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1a5576cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f1a55713d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7
[plasmashell] [Bug 364189] New: KDE not run
https://bugs.kde.org/show_bug.cgi?id=364189 Bug ID: 364189 Summary: KDE not run Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: samurai.unn...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.21-14-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: When I log does not start the KDE desktop environment and the screen is black The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe7fc6407c0 (LWP 2197))] Thread 7 (Thread 0x7fe7e4416700 (LWP 2201)): #0 0x7fe7f5ad3bbd in poll () at /lib64/libc.so.6 #1 0x7fe7faa7a422 in () at /usr/lib64/libxcb.so.1 #2 0x7fe7faa7c00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fe7e6bcf3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe7f61d232f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe7f52cf0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe7f5adbfed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fe7e0bae700 (LWP 2217)): #0 0x7fe7f5ad3bbd in poll () at /lib64/libc.so.6 #1 0x7fe7f2142e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe7f2142f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe7f6404d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe7f63abd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe7f61cd61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe7f9517e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fe7f61d232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe7f52cf0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe7f5adbfed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fe7d8ef6700 (LWP 2218)): #0 0x7fe7f5ad3bbd in poll () at /lib64/libc.so.6 #1 0x7fe7f2142e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe7f2142f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe7f6404d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe7f63abd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe7f61cd61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe7f9517e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fe7f61d232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe7f52cf0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe7f5adbfed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fe7d7676700 (LWP 2219)): #0 0x7fe7f5ad3bbd in poll () at /lib64/libc.so.6 #1 0x7fe7f2142e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe7f2142f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe7f6404d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe7f63abd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe7f61cd61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe7f9517e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fe7f61d232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe7f52cf0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe7f5adbfed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fe7d5cee700 (LWP 2220)): #0 0x7fe7f52d303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe7fbd1286b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fe7fbd12899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fe7f52cf0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe7f5adbfed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fe7526e6700 (LWP 2221)): #0 0x7fe7f5ad3bbd in poll () at /lib64/libc.so.6 #1 0x7fe7f2142e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe7f2142f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe7f6404d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe7f63abd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe7f61cd61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe7fa0c2282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7fe7f61d232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe7f52cf0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe7f5adbfed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe7fc6407c0 (LWP 2197)): [KCrash Handler] #6 0x7fe7f5a2c0a7 in raise () at /lib64/libc.so.6 #7 0x7fe7f5a2d458 in abort
[valgrind] [Bug 363858] Add IBM ISA 3.0 support, patch set 4
https://bugs.kde.org/show_bug.cgi?id=363858 Carl Lovechanged: What|Removed |Added CC||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363210] desktop right click show Activities (when you only have one activity)
https://bugs.kde.org/show_bug.cgi?id=363210 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied
https://bugs.kde.org/show_bug.cgi?id=347602 --- Comment #71 from Aleix Pol--- If you think it's a new issue, please open a new bug report. The original issue was fixed. -- You are receiving this mail because: You are watching all bug changes.
[konquest] [Bug 335016] konquest tries loading the non-existent objects with the ids planet_name_background and planet_ship_count_background from default_theme.svgz
https://bugs.kde.org/show_bug.cgi?id=335016 Frederik Schwarzerchanged: What|Removed |Added CC||schwar...@kde.org --- Comment #2 from Frederik Schwarzer --- In general unused code should be removed. But if it's a half-implemented feature, the feature could as well be implemented fully. That's a decision for the maintainer ... if there will be one again. You could put a patch on review board. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable
https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #13 from Camille Bissuel--- I installed the latest plasma desktop, tested Krita with it and the bug occurred, and the whole Plasma desktop became totally stuck in clicking state. So I was clicking everywhere by simply hovering any interface. This bug is driving me crazy, and basically I'll need to abandon Krita if this is not fixed a way or another… : I can't spend several hours a day rebooting because of this. I understand this is linked to some upstream bug, but can you PLEASE give me some advice on how to report this correctly and where in the QT/KDE maze ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Kwin crashes when trying to open configurations of the system tray
https://bugs.kde.org/show_bug.cgi?id=361236 Thomas Lübkingchanged: What|Removed |Added CC||phil...@stromberg.me --- Comment #9 from Thomas Lübking --- *** Bug 364121 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364121] Opening Dolphin crashes kwin almost every time
https://bugs.kde.org/show_bug.cgi?id=364121 Thomas Lübkingchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Thomas Lübking --- This will be the linked bug, upstream bug is https://bugreports.qt.io/browse/QTBUG-53452 There's unfortunately not much you can doother than not using aurorae. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable
https://bugs.kde.org/show_bug.cgi?id=363225 Camille Bissuelchanged: What|Removed |Added Summary|Sometimes the pen inputs|QT5 under Linux get stuck |events are locked in|in "clicking" state, and |"clicking" state on the |Krita become unusable |Krita interface, and the| |interface become unusable | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 364126] Cannot disable sound effects on search
https://bugs.kde.org/show_bug.cgi?id=364126 Yuri Chornoivanchanged: What|Removed |Added CC||yurc...@ukr.net --- Comment #1 from Yuri Chornoivan --- (In reply to 2460acc from comment #0) > If I search for a word in the document and it isn't found, then there is a > bell sound. I have muted system sounds so this must be coming from okular > itself. Looking in the menus, there is no ability to disable this sound. > Please can you add this option! Thanks. > > Reproducible: Always It should be a global KDE notification option. Can you try to open System Settings (KDE 4 but similar thing should work for KF5), then go to "Application and System Notification", then "Notification MAnagement", then "KDE Workspace" from drop-down list, then uncheck "Textcompletion: No Match"? Thanks in advance for testing this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364121] Opening Dolphin crashes kwin almost every time
https://bugs.kde.org/show_bug.cgi?id=364121 --- Comment #4 from phil...@stromberg.me --- That does appear to have fixed it. No more kwin crashes. This seems to have started for me after a recent Kubuntu 16.04 update. It did not cause me any trouble until a couple days before I submitted the ticket. Thank you for your help, Thomas. If there's anything else I can provide, let me know. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 364188] New: Konsole was crashed
https://bugs.kde.org/show_bug.cgi?id=364188 Bug ID: 364188 Summary: Konsole was crashed Product: konsole Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: anne-mariekra...@kabelmail.de Application: konsole (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-24-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I was update about Konsole/Terminal. Bevor I streamed somthing about Firefox. After that it crashed The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f414ab8b418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f414ab8d01a in __GI_abort () at abort.c:89 #8 0x7f414abcd72a in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f414ace66b0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f414abd5f4a in malloc_printerr (ar_ptr=, ptr=, str=0x7f414ace67c0 "double free or corruption (out)", action=3) at malloc.c:5007 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3868 #11 0x7f414abd9abc in __GI___libc_free (mem=) at malloc.c:2969 #12 0x7f4147800363 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f41478003b9 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f41477d7187 in QCoreApplication::removePostedEvents(QObject*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f41478026a2 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f41478027c9 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f414780ade8 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f4137647909 in QXcbConnection::~QXcbConnection() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #19 0x7f4137649056 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #20 0x7f4137649169 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x7f4147b0ccf3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7f41480c2089 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f414780ade8 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f41480c3e79 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f414af46d9c in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so #26 0x7f414ab76830 in __libc_start_main (main=0x400710 , argc=1, argv=0x7ffec9d89c08, init=, fini=, rtld_fini=, stack_end=0x7ffec9d89bf8) at ../csu/libc-start.c:291 #27 0x00400749 in _start () Possible duplicates by query: bug 363636, bug 360774, bug 359204, bug 358628, bug 358326. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363152] Form text not displayed for upside-down field
https://bugs.kde.org/show_bug.cgi?id=363152 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 318904] keystrokes break with standart neo layout
https://bugs.kde.org/show_bug.cgi?id=318904 --- Comment #30 from h.goe...@crazy-compilers.com --- I verified that adding some key with "NumLock" solves the problem: The following created an additional X11 symbols file defining key 253 (which is unused on my system) as NumLock and a keymap using de(neo) plus this additional symbols. The xkbcomp call will activate this keymap. 8<--- mkdir -p /tmp/xkb/symbols /tmp/xkb/keymaps cd /tmp/xkb cat > symbols/fixkdeaccell << EOF default partial keypad_keys xkb_symbols "numlock" { key { [ Num_Lock ] }; }; EOF setxkbmap -layout de -variant neo -print | \ sed 's/de(neo)+/de(neo)+fixkdeaccell(numlock)+/' > keymaps/xkbtest cat keymaps/xkbtest xkbcomp -I. keymaps/xkbtest $DISPLAY 8<--- Now you have both de(neo) and Alt-Tab working. When running QT_LOGGING_RULES="org.kde.kwindowsystem.keyserver.*.debug=true" $KF5/bin/kglobalaccel5 this shows NumLock is detected. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 364187] New: Skanlite freezes at some point
https://bugs.kde.org/show_bug.cgi?id=364187 Bug ID: 364187 Summary: Skanlite freezes at some point Product: Skanlite Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: aleix...@kde.org After selecting the device, it takes a while for it, but it ends up freezing. Here's a backtrace: Thread 1 "skanlite" received signal SIGINT, Interrupt. 0x7362468d in poll () from /usr/lib/libc.so.6 (gdb) where #0 0x7362468d in poll () from /usr/lib/libc.so.6 #1 0x7fffec88c235 in ?? () from /usr/lib/libusb-1.0.so.0 #2 0x7fffec88d1c3 in libusb_handle_events_timeout_completed () from /usr/lib/libusb-1.0.so.0 #3 0x7fffec88d300 in libusb_handle_events_completed () from /usr/lib/libusb-1.0.so.0 #4 0x7fffec88dbf1 in ?? () from /usr/lib/libusb-1.0.so.0 #5 0x7fffec88dcd9 in ?? () from /usr/lib/libusb-1.0.so.0 #6 0x7fffec88e09f in libusb_bulk_transfer () from /usr/lib/libusb-1.0.so.0 #7 0x733213bb in sanei_usb_read_bulk () from /usr/lib/libsane.so.1 #8 0x7fffcbddeb10 in sanei_pixma_read () from /usr/lib/sane/libsane-pixma.so.1 #9 0x7fffcbddf73f in sanei_pixma_cmd_transaction () from /usr/lib/sane/libsane-pixma.so.1 #10 0x7fffcbddf8e7 in sanei_pixma_exec () from /usr/lib/sane/libsane-pixma.so.1 #11 0x7fffcbde0c7a in ?? () from /usr/lib/sane/libsane-pixma.so.1 #12 0x7fffcbde0cda in ?? () from /usr/lib/sane/libsane-pixma.so.1 #13 0x7fffcbde007a in sanei_pixma_wait_event () from /usr/lib/sane/libsane-pixma.so.1 #14 0x7fffcbddb13b in ?? () from /usr/lib/sane/libsane-pixma.so.1 #15 0x7fffcbddc5f2 in sane_pixma_control_option () from /usr/lib/sane/libsane-pixma.so.1 #16 0x77bb6e52 in KSaneIface::KSaneOptSlider::readValue (this=0x842a30) at /home/apol/devel/frameworks/libksane/src/options/ksaneoptslider.cpp:71 #17 0x77bad8f8 in KSaneIface::KSaneWidgetPrivate::pollPollOptions (this=0x70f560) at /home/apol/devel/frameworks/libksane/src/ksanewidget_p.cpp:1172 #18 0x77bbc3ad in KSaneIface::KSaneWidgetPrivate::qt_static_metacall (_o=0x70f560, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd620) at src/moc_ksanewidget_p.cpp:151 #19 0x74427fc9 in QMetaObject::activate (sender=sender@entry=0x70f778, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3740 #20 0x744288e7 in QMetaObject::activate (sender=sender@entry=0x70f778, m=m@entry=0x74644c40 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3602 #21 0x7449dfd0 in QTimer::timeout (this=this@entry=0x70f778) at .moc/moc_qtimer.cpp:198 #22 0x74434858 in QTimer::timerEvent (this=0x70f778, e=) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qtimer.cpp:254 #23 0x74428d5b in QObject::event (this=0x70f778, e=) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:1285 #24 0x74cce2cc in QApplicationPrivate::notify_helper (this=, receiver=0x70f778, e=0x7fffd990) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3799 #25 0x74cd5461 in QApplication::notify (this=0x7fffe1b0, receiver=0x70f778, e=0x7fffd990) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3556 #26 0x743fe1a8 in QCoreApplication::notifyInternal2 (receiver=0x70f778, event=event@entry=0x7fffd990) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:988 #27 0x7444e77e in QCoreApplication::sendEvent (event=0x7fffd990, receiver=) at ../../include/QtCore/../../../../frameworks/qt5/qtbase/src/corelib/kernel/qcoreapplication.h:231 #28 QTimerInfoList::activateTimers (this=0x6924d0) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qtimerinfo_unix.cpp:644 #29 0x7444eca1 in timerSourceDispatch (source=) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:182 #30 0x7fffedcb2dd7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #31 0x7fffedcb3040 in ?? () from /usr/lib/libglib-2.0.so.0 #32 0x7fffedcb30ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #33 0x7444f75f in QEventDispatcherGlib::processEvents (this=0x68f940, flags=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #34 0x743fc72a in QEventLoop::exec (this=this@entry=0x7fffdbd0, flags=..., flags@entry=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:210 #35 0x7440482d in QCoreApplication::exec () at
[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3
https://bugs.kde.org/show_bug.cgi?id=353203 Alan Mimmschanged: What|Removed |Added CC||al...@unforgettable.com -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9
https://bugs.kde.org/show_bug.cgi?id=362805 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 362842] Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364121] Opening Dolphin crashes kwin almost every time
https://bugs.kde.org/show_bug.cgi?id=364121 --- Comment #3 from Thomas Lübking--- > Plugin: org.kde.kwin.aurorae quelle surprise... run "kcmshell5 kwindecoration" and switch to breeze, do the crashes still happen afterwards? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364121] Opening Dolphin crashes kwin almost every time
https://bugs.kde.org/show_bug.cgi?id=364121 --- Comment #2 from phil...@stromberg.me --- Created attachment 99442 --> https://bugs.kde.org/attachment.cgi?id=99442=edit output of 'qdbus org.kde.KWin /KWin supportInformation' as requested by Thomas Lübking -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364186] New: Plasma crashes on launching Dropbox
https://bugs.kde.org/show_bug.cgi?id=364186 Bug ID: 364186 Summary: Plasma crashes on launching Dropbox Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: chabot.dan...@free.fr CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.11-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: - What I was doing when the application crashed: I've just login my session, then say yes to install the new update, open Dolphin to watch something in my dropbox. when i launch the application to synchronise my dropbox i got a message "Sorry plasma has crsash". PS: I have try to link this bug with another witch seems the same but I never be able to do this. Wathever I do KDEbugreport say to me "You haven't select a bug, create a new one?". Thank you for jour job, Daniel. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f78e1bea900 (LWP 1852))] Thread 8 (Thread 0x7f78da8a4700 (LWP 1861)): #0 0x0030ca4f757d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0030ce00a182 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f78da8a3bc0) at /usr/include/bits/poll2.h:46 #2 0x0030ce00a182 in _xcb_conn_wait (c=c@entry=0xa547a0, cond=cond@entry=0xa547e0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x0030ce00bc77 in xcb_wait_for_event (c=0xa547a0) at xcb_in.c:648 #4 0x7f78daf06da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #5 0x0032a0ca33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x0030cac07555 in start_thread (arg=0x7f78da8a4700) at pthread_create.c:333 #7 0x0030ca502ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f78d3dfa700 (LWP 1899)): #0 0x0030ca4f323d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x0030ccc8db00 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7f78d3df9aa0, __fd=) at /usr/include/bits/unistd.h:44 #2 0x0030ccc8db00 in g_wakeup_acknowledge (wakeup=0x7f78d40015b0) at gwakeup.c:210 #3 0x0030ccc498b4 in g_main_context_check (context=context@entry=0x7f78cc000990, max_priority=2147483647, fds=fds@entry=0x7f78cc003070, n_fds=n_fds@entry=1) at gmain.c:3600 #4 0x0030ccc49d60 in g_main_context_iterate (context=context@entry=0x7f78cc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3805 #5 0x0030ccc49ecc in g_main_context_iteration (context=0x7f78cc000990, may_block=1) at gmain.c:3869 #6 0x0032a0edaecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x0032a0e81eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x0032a0c9e434 in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x00371e0d99b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #10 0x0032a0ca33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #11 0x0030cac07555 in start_thread (arg=0x7f78d3dfa700) at pthread_create.c:333 #12 0x0030ca502ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f78c92db700 (LWP 1908)): #0 0x0030ca4f757d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0030ccc49dbc in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f78c4002e70, timeout=, context=0x7f78c4000990) at gmain.c:4103 #2 0x0030ccc49dbc in g_main_context_iterate (context=context@entry=0x7f78c4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3803 #3 0x0030ccc49ecc in g_main_context_iteration (context=0x7f78c4000990, may_block=1) at gmain.c:3869 #4 0x0032a0edaecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x0032a0e81eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x0032a0c9e434 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x00371e0d99b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x0032a0ca33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x0030cac07555 in start_thread (arg=0x7f78c92db700) at pthread_create.c:333 #10 0x0030ca502ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f78c3822700 (LWP 1920)): #0 0x0030ca4f757d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0030ccc49dbc in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f78bc003070, timeout=, context=0x7f78bc000990) at gmain.c:4103 #2
[krita] [Bug 340736] Very slow performance while changing layer orders
https://bugs.kde.org/show_bug.cgi?id=340736 --- Comment #20 from Janne Vuollet--- Hello Normally my work has around 100-300 layers (lots clipping masks etc.) in alot of nested groups with some simple layer effects for some groups (gradient fill etc). image size is around 6000x3000 to 10 000x5000 usually the starting point is multiples of 1920x1080. colours nothing fancy, RGB 8bit With Krita I didn't get more than a few layers and the lagging started. I'll email a file for you. It is the one I started working on but abandoned after the lag got too severe. It was just on initial sketching phase. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364182] segmentation fault after trying opening an avi-file with kaffeine
https://bugs.kde.org/show_bug.cgi?id=364182 Mauro Carvalho Chehabchanged: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mauro Carvalho Chehab --- Kaffeine 1.2.x has several troubles opening different file formats. It is based on an old backend using libXine. Since Kaffeine 1.3.x, it is using libVLC. So, this bug should be already fixed upstream. As this bug was filled for a too old version, I'm closing it. If it happens with Kaffeine 2.0, feel free to re-open. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 310694] Kmail thinks it is offline, switching online as offered does not work
https://bugs.kde.org/show_bug.cgi?id=310694 Michael Seifertchanged: What|Removed |Added CC||mseif...@error-reports.org -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 172231] WISH - one click sound output change button
https://bugs.kde.org/show_bug.cgi?id=172231 Mauro Carvalho Chehabchanged: What|Removed |Added Latest Commit||http://commits.kde.org/kaff ||eine/71e5f187b16d6898f755e7 ||81d74b64bc2f1d041f Resolution|UNMAINTAINED|FIXED Status|VERIFIED|RESOLVED --- Comment #4 from Mauro Carvalho Chehab --- Git commit 71e5f187b16d6898f755e781d74b64bc2f1d041f by Mauro Carvalho Chehab. Committed on 10/06/2016 at 14:36. Pushed by mauroc into branch 'master'. mediawidget: add support to select the audio device Allow the user to dynamically change the audio device directly in Kaffeine. Signed-off-by: Mauro Carvalho Chehab M +11 -0src/abstractmediawidget.cpp M +5-0src/abstractmediawidget.h M +37 -0src/backend-vlc/vlcmediawidget.cpp M +2-0src/backend-vlc/vlcmediawidget.h M +29 -0src/mediawidget.cpp M +3-0src/mediawidget.h http://commits.kde.org/kaffeine/71e5f187b16d6898f755e781d74b64bc2f1d041f -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 359178] Kaddressbook does not download new contacts from Google Contacts
https://bugs.kde.org/show_bug.cgi?id=359178 jrohwerchanged: What|Removed |Added CC||j.m.roh...@gmail.com --- Comment #2 from jrohwer --- I can confirm this. Kubuntu 16.04 kaddressbook 5.1.3 KDE frameworks 5.18.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 318904] keystrokes break with standart neo layout
https://bugs.kde.org/show_bug.cgi?id=318904 --- Comment #29 from h.goe...@crazy-compilers.com --- Trying to compile this was much more complicated (I do not have Debian nor kde 5), but I succeeded at last. Indeed, KGlobalAccelImpl::x11MappingNotify() and calculateGrabMasks() are both gets called when setting a keymap - as expected. This morning I missed that initializeMods() is called be x11MappingNotify() and thus the modifiers are really updated as I first assumed: setxkbmap -layout de g_keyModMaskXAccel = 77 g_keyModMaskXOnOrOff = 146 setxkbmap -layout de -variant neo g_keyModMaskXAccel = 77 g_keyModMaskXOnOrOff = 2 So my analysis was correct: kglobalaccel does not filter NumLock since KKeyServer does not report it as a modifier lock. Addendum: I was now able to build and run kglobalaccel 5.22.0, too. But here x11MappingNotify seams to be never called and nativeEventFilter seams to get not XCB_MAPPING_NOTIFY event at all. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 364185] New: K3b crashes burning DL DVD image
https://bugs.kde.org/show_bug.cgi?id=364185 Bug ID: 364185 Summary: K3b crashes burning DL DVD image Product: k3b Version: 2.0.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@kde.org Reporter: brian.marti...@seguratec.com.co CC: mich...@jabster.pl, tr...@kde.org Application: k3b (2.0.3) KDE Platform Version: 4.14.20 Qt Version: 4.8.7 Operating System: Linux 4.5.5-201.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: K3b crashes when attempting to burn a DL DVD image (4.5Gb). Occurrs in a 100% repeatable form on fully updated Fedora 23 system with no modifications or additions. The crash can be reproduced every time. -- Backtrace: Application: K3b (k3b), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9f5572a940 (LWP 7502))] Thread 3 (Thread 0x7f9f27c26700 (LWP 7504)): #0 0x7f9f4850d779 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f9f484c9172 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f9f484c929c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9f4e07de7e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #4 0x7f9f4e04c131 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #5 0x7f9f4e04c4a5 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #6 0x7f9f4df3ba99 in QThread::exec() () at /lib64/libQtCore.so.4 #7 0x7f9f4e02c203 in QInotifyFileSystemWatcherEngine::run() () at /lib64/libQtCore.so.4 #8 0x7f9f4df3e38c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #9 0x7f9f4dc9b61a in start_thread () at /lib64/libpthread.so.0 #10 0x7f9f4c17a59d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f9f24ff4700 (LWP 7532)): #0 0x7f9f4dca0ec9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9f4df3cd3a in thread_sleep(timespec*) () at /lib64/libQtCore.so.4 #2 0x7f9f4df3d633 in QThread::sleep(unsigned long) () at /lib64/libQtCore.so.4 #3 0x7f9f552eaaad in K3b::MediaCache::PollThread::run() () at /lib64/libk3blib.so.6 #4 0x7f9f4df3e38c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #5 0x7f9f4dc9b61a in start_thread () at /lib64/libpthread.so.0 #6 0x7f9f4c17a59d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f9f5572a940 (LWP 7502)): [KCrash Handler] #6 0x7f9f2c9e6e60 in Adwaita::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const () at /usr/lib64/qt4/plugins/styles/adwaita.so #7 0x7f9f552d5ff6 in K3b::ListViewItem::paintProgressBar(QPainter*, QColorGroup const&, int, int) () at /lib64/libk3blib.so.6 #8 0x7f9f552d63e2 in K3b::ListViewItem::paintCell(QPainter*, QColorGroup const&, int, int, int) () at /lib64/libk3blib.so.6 #9 0x7f9f50077b1e in Q3ListView::drawContentsOffset(QPainter*, int, int, int, int, int, int) () at /lib64/libQt3Support.so.4 #10 0x7f9f552d5be9 in K3b::ListView::drawContentsOffset(QPainter*, int, int, int, int, int, int) () at /lib64/libk3blib.so.6 #11 0x7f9f500c0a7f in Q3ScrollView::viewportPaintEvent(QPaintEvent*) () at /lib64/libQt3Support.so.4 #12 0x7f9f54949be9 in K3ListView::viewportPaintEvent(QPaintEvent*) () at /lib64/libkde3support.so.4 #13 0x7f9f500c25e0 in Q3ScrollView::eventFilter(QObject*, QEvent*) () at /lib64/libQt3Support.so.4 #14 0x7f9f50078d7e in Q3ListView::eventFilter(QObject*, QEvent*) () at /lib64/libQt3Support.so.4 #15 0x7f9f4e04da26 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #16 0x7f9f4ced691c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #17 0x7f9f4cedd796 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #18 0x7f9f4ed6163a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #19 0x7f9f4e04d8bd in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #20 0x7f9f4cf27787 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQtGui.so.4 #21 0x7f9f4cf2819f in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListconst&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQtGui.so.4 #22 0x7f9f4cf27316 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQtGui.so.4 #23 0x7f9f4cf2819f in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
[krita] [Bug 362445] Lags while drawing circular shapes (bended lines on Windows!)
https://bugs.kde.org/show_bug.cgi?id=362445 --- Comment #16 from eliotJ--- It looks like fixing this bug generating another: https://bugs.kde.org/show_bug.cgi?id=364183 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364168] Failed to load ldlinux.c32
https://bugs.kde.org/show_bug.cgi?id=364168 Harald Sitterchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Harald Sitter --- What I meant is does your VM virtualize 64bit. At any rate please use KVM or virtualbox. We neither test nor support vmware. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 361479] There was a problem saving:
https://bugs.kde.org/show_bug.cgi?id=361479 Luis Augusto Consularochanged: What|Removed |Added CC||consul...@gmail.com --- Comment #4 from Luis Augusto Consularo --- Same problem here, same solution in ubuntu 16.04: sudo apt-get install kio -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails
https://bugs.kde.org/show_bug.cgi?id=362958 Laurent Montelchanged: What|Removed |Added CC||mon...@kde.org --- Comment #13 from Laurent Montel --- nope. I think that Dan fixed it long time ago in next 5.2.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364184] Navigating Canvas is slow (Pan, Rotate, Zoom)
https://bugs.kde.org/show_bug.cgi?id=364184 eliotJchanged: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364184] New: Navigating Canvas is slow (Pan, Rotate, Zoom)
https://bugs.kde.org/show_bug.cgi?id=364184 Bug ID: 364184 Summary: Navigating Canvas is slow (Pan, Rotate, Zoom) Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: os...@jadamspam.pl I noticed that in v3.0 I have really worse performance in navigating the Canvas (Pan, Rotate, Zoom) compared to v2.9.10ae. On both versions I used 'Instant Preview' and 'OpenGL' and 'Scaling Mode >> High Quality Filtering". In v3.0 helps a lot (for me) turning off 'Display >> Use texture buffer' but still I get really worse performance than I have in v2.9.10ae. My PC: Intel Dual Core 2,2 Ghz, 4 GB Ram, Nvidia GeFroce G 103M, Win 7 64bit. >From IRC (discussion about these issue): it might be a change in Qt5 -- where Qt now forces double-buffering it's so incredibly hard... we started porting over a year ago, but only now we're really seeing the regressions, other than the most obvious ones! Even on small resolution of image I have slow down... what I think is also going is that 3.0 has memory problems compared to 2.9 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 364180] Invoking fast qdbus org.kde.klipper /klipper setClipboardContents "$line" leads to Panel freeze
https://bugs.kde.org/show_bug.cgi?id=364180 --- Comment #3 from mhrus...@redhat.com --- Maybe it is busy-looping, because longer "list" with 30 lines takes longer time than only 5 lines list. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364168] Failed to load ldlinux.c32
https://bugs.kde.org/show_bug.cgi?id=364168 --- Comment #2 from Daniel Kreuter--- A virtual machine with VMWare Player. Settings: 4GB RAM, 8 CPU cores, rest is default. and yes amd64 means 64 bit. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 364180] Invoking fast qdbus org.kde.klipper /klipper setClipboardContents "$line" leads to Panel freeze
https://bugs.kde.org/show_bug.cgi?id=364180 --- Comment #2 from mhrus...@redhat.com --- Created attachment 99441 --> https://bugs.kde.org/attachment.cgi?id=99441=edit gdb plasma-shell backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364159] Smoothing Option reset to last one used
https://bugs.kde.org/show_bug.cgi?id=364159 Scott Petrovicchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Severity|normal |wishlist Ever confirmed|0 |1 CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- This is a shared setting across multiple brush tools in the code. If we want this to save separately, we will need to figure out how to separate the setting or add extra logic so it knows what brush tool it is on. This setting has been shared for a while, so we probably need to get the feedback of some different artists before we would do this. I could see different artists prefer different ways for this to work. Marking as a potential wish list item. -- You are receiving this mail because: You are watching all bug changes.