[okular] [Bug 358061] [Usability] Improved/consistent mechanism to add/modify inline note
https://bugs.kde.org/show_bug.cgi?id=358061 --- Comment #1 from Simone Gaiarin --- Given that someone gave some love to the inline note I bump this bug which is related. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358059] Inline note text not fully visible
https://bugs.kde.org/show_bug.cgi?id=358059 --- Comment #2 from Simone Gaiarin --- Given that someone gave some love to the inline note I bump this bug which is related. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358064] Popup note icon size is too big and not configurable
https://bugs.kde.org/show_bug.cgi?id=358064 --- Comment #1 from Simone Gaiarin --- Given that someone gave some love to the inline note I bump this bug which is related. --- Comment #2 from Simone Gaiarin --- Ops.. I commented on the wrong bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358064] Popup note icon size is too big and not configurable
https://bugs.kde.org/show_bug.cgi?id=358064 --- Comment #1 from Simone Gaiarin --- Given that someone gave some love to the inline note I bump this bug which is related. --- Comment #2 from Simone Gaiarin --- Ops.. I commented on the wrong bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373440] konsole --new-tab opens window instead
https://bugs.kde.org/show_bug.cgi?id=373440 --- Comment #32 from Martin Kostolný --- OK, I've now replicated the behaviour as well. Sorry about the previous comment. When Konsole is started without --new-tab parameter, then subsequent "konsole --new-tab" opens a new window. Workaround is indeed checking "Run all Konsole windows in a single process". If I start first konsole process with --new-tab. The next --new-tab starts append a new tab as expected. No need for the workaround. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379414] [Data Loss] - TaskManager loses launchers from alternative Activities
https://bugs.kde.org/show_bug.cgi?id=379414 Michail Vourlakos changed: What|Removed |Added Severity|normal |major Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 379427] 'C:\Program' not recognized as internal or external command in compilation of zlib.
https://bugs.kde.org/show_bug.cgi?id=379427 Hannah von Reth changed: What|Removed |Added CC||vonr...@kde.org --- Comment #5 from Hannah von Reth --- Please remove mingw-w64 6.3 from your path. We only support the mings version installed by craft. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379466] New: Drag on selection outline to move the selection
https://bugs.kde.org/show_bug.cgi?id=379466 Bug ID: 379466 Summary: Drag on selection outline to move the selection Product: krita Version: 3.1.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Following on a discussion with Dmitry on IRC Krita currently lacks an intuitive way to move selections. There's the global selection mask, but it can be slow and inconvenient on documents with a lot of layers (as it sits at the top of the layer stack). Aseprite 1.2 beta 8 introduced a solution to move the selection: with a selection tool, click and drag on the selection's outline. Demo: http://imgur.com/yFPZOwx It works that way, when the selection tool is active: 1. Drag inside the selection to transform it (there's no separate transform tool as in Krita that's aware of the selection) 2. If you drag on the selection's outline, you move the selection. 3. If you click outside of the selection it creates a new one. 4. If you use a modifier key, you can still move the selection but not transform its content. How it could work in Krita. With a selection tool active and selection in marching ants mode: - Change the icon when you hover the selection's outline or content. The user clicks and drags to move the selection. - If a modifier key is pressed, always draw a new selection. - If you click once, as it works now, deselect everything - if you draw outside the selection, create a new selection. These suggestions take the overlay selection display mode in account. As there's not always a clear outline, you could interact the same way with both modes. Anyway, it's up for discussion. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379279] NetworkManager "Ask For Password" Popup Focus
https://bugs.kde.org/show_bug.cgi?id=379279 --- Comment #7 from Nick Cross --- Ok after checking out that code and installing an awful lot of build dependencies :-) I first tried without the diff (to see if the Fedora build was doing something strange) but could still reproduce the problem. I have just now tried with the diff and it seems to be working! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 375409] Browser can't render (libGL error: failed to create drawable)
https://bugs.kde.org/show_bug.cgi?id=375409 --- Comment #3 from Knut Andre Tidemann --- This problem was solved for me on Arch Linux by rebuilding the libkgapi and kdepim-runtime packages. Not sure if both needs to be rebuilt, but it didn't work with only rebuilding libkgapi. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379467] New: Display "Date:" header in sender's local timezone
https://bugs.kde.org/show_bug.cgi?id=379467 Bug ID: 379467 Summary: Display "Date:" header in sender's local timezone Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: j...@dbzero.it Target Milestone: --- In the message view the "Date:" header is always shown in user's local timezone, with no reference to sender's original one, so the only possible way to find out the original time is to manually inspect the raw message, and look at the Date: header. It would be useful to give the user the choice to choose whether to display the message date in his own or in the sender's timezone, maybe keeping the local timezone in the message list and the original one in the headers view, so to facilitate the message sorting while avoiding the need to manually inspect the message. Example (my timezone is UTC+2): (header)Date: Thu, 27 Apr 2017 14:19:49 -0400 (message view) 27/04/17 20:19 (message list) giovedì 20:19 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379468] New: Weather widget configured with yr.no crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=379468 Bug ID: 379468 Summary: Weather widget configured with yr.no crashes Plasmashell Product: plasmashell Version: 5.9.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cyberan...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.4.0-77-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: I have a weather widget on my taskbar, and have it configured to check the weather from yr.no for two locations. Oslo (Place identifier: Norway/Oslo/Oslo/Oslo) and Athens (Place identifier: Greece/Attica/Athens). In the "Appearance" settings I don't have the option "Render meteogram for yr.no" ticked, I am using the "Compact" layout type, and "Active timeout" is set to 3600sec. These settings provide me with a nice compact widget on my taskbar that shows the temperature and a small icon based on the current weather conditions (sun, clouds etc). When I click on the widget a window that shows the Meteogram and more detailed weather info for the current location slides up, that also gives me the option to change to the next configured location. And here is when the crash happens sometimes. After I reboot the system, if I click on the widget sometimes the whole plasmashell is crashing and reloading. The crash happens quite often, but not always. Once I get one or two plasmashell crashes, if I do not reboot the system then the weather widget works as expected each subsequent time I click on it. I assume it may have something to do with fetching the meteogram for the first time after a reboot. Moreover, DrKonqi is also asking me to install a bunch of debug symbols that I have managed to install all except for "plasmashell". Does anyone know what is the KDE Neon package that provides debug symbols for "plasmashell"? The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3641227900 (LWP 4947))] Thread 15 (Thread 0x7f3547ffe700 (LWP 7230)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f363c2709fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x302d920) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x2550ec0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f363f29247d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f363f292d55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f363c26fb48 in QThreadPrivate::start (arg=0x2550e40) at thread/qthread_unix.cpp:368 #6 0x7f363b1156ba in start_thread (arg=0x7f3547ffe700) at pthread_create.c:333 #7 0x7f363bb7c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f355112a700 (LWP 5431)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f363c2709fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x496b3f0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x5626600, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f363f29247d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f363f292d55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f363c26fb48 in QThreadPrivate::start (arg=0x5626580) at thread/qthread_unix.cpp:368 #6 0x7f363b1156ba in start_thread (arg=0x7f355112a700) at pthread_create.c:333 #7 0x7f363bb7c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f355374c700 (LWP 5419)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f363c2709fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x49b3590) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x49b5900, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f363f29247d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f363f292d55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f363c26fb48 in QThreadPrivate::start (arg=0x49b5880) at thread/qthread_unix.cpp:368 #6 0x7f363b1156ba in start_thread (arg=0x7f355374c700) at pthread_create.c:333 #7 0x7f363bb7c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f355b068700 (LWP 5389)): #0 0x
[kmail2] [Bug 379467] Display "Date:" header in sender's local timezone
https://bugs.kde.org/show_bug.cgi?id=379467 Juri Vitali changed: What|Removed |Added CC||j...@dbzero.it -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 378995] Suspended RSIBreak with Hanging Notification
https://bugs.kde.org/show_bug.cgi?id=378995 --- Comment #7 from promike1...@gmail.com --- (In reply to Albert Astals Cid from comment #5) > I'll go with just reshowing the notification since this seems like very > corner-case to really spend much effort in making it perfect. That's okay. Having been fixed, rsibreak is working great now! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379469] New: Can not drag and drop the image from Google Chrome / FF to the desktop to set the wallpaper
https://bugs.kde.org/show_bug.cgi?id=379469 Bug ID: 379469 Summary: Can not drag and drop the image from Google Chrome / FF to the desktop to set the wallpaper Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: idmresettr...@gmail.com Target Milestone: 1.0 *** Steps to reproduce: 1, Open a wallpaper website in Google Chrome or Firefox. For example: https://alpha.wallhaven.cc/wallpaper/503877 or https://wallpapers.wallhaven.cc/wallpapers/full/wallhaven-503877.png 2, Drag and drop the image to the desktop and choose: Wallpaper / Image from the context menu *** Expected Result: - The desktop wallpaper CHANGES to that image IMMEDIATELY. *** Actual Result: - Nothing changes, the desktop wallpaper DOES NOT change. I'm using: KDE Plasma Version: 5.9.4, KDE Frameworks Version: 5.33.0, Qt Version: 5.8.0, all the other things are up to date on Manjaro KDE. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379279] NetworkManager "Ask For Password" Popup Focus
https://bugs.kde.org/show_bug.cgi?id=379279 --- Comment #8 from Nick Cross --- Could this patch be applied to the 5.9.x series? I can enter an issue into Fedora upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379469] Can not set the wallpaper by drag and drop the image from Google Chrome / FF to the desktop
https://bugs.kde.org/show_bug.cgi?id=379469 idmresettrial changed: What|Removed |Added Summary|Can not drag and drop the |Can not set the wallpaper |image from Google Chrome / |by drag and drop the image |FF to the desktop to set|from Google Chrome / FF to |the wallpaper |the desktop -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379279] NetworkManager "Ask For Password" Popup Focus
https://bugs.kde.org/show_bug.cgi?id=379279 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #9 from Jan Grulich --- I can backport that patch to Fedora, I just wasn't able to verify that it fixes this problem, let me test it again. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 379057] not showing greek letters in some documents
https://bugs.kde.org/show_bug.cgi?id=379057 Albert Astals Cid changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||aa...@kde.org Resolution|--- |INVALID --- Comment #5 from Albert Astals Cid --- There's nothing we can do here, at most it would be a poppler bug. What poppler does is you don't have the font, asks fontconfig for a substitute font and tries to use it as best as it can. Either the font fontconfig returns is not a good substitute or poppler is misusing it, anyway it wouldn't be an Okular bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379470] New: Crash when performing face detection or recognition on large collection
https://bugs.kde.org/show_bug.cgi?id=379470 Bug ID: 379470 Summary: Crash when performing face detection or recognition on large collection Product: digikam Version: 5.5.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Faces-Management Assignee: digikam-de...@kde.org Reporter: gen...@moin.fi Target Milestone: --- When I select the button "Scan collection for faces" (doesn't matter whether I pick the option "Detect faces" or "Detect and recognize faces"), Digikam crashes after a while. (Same if I engage this function through the "Tools/Maintenance..." command.) It's a large collection and I don't think the crash is related to a particular image. Here's a backtrace from gdb: Program received signal SIGBUS, Bus error. [Switching to Thread 0x7fff52ffd700 (LWP 6303)] QMapData::createNode (left=false, parent=0x0, v=..., k=..., this=0x7fff3c5ed800) at /usr/include/qt5/QtCore/qmap.h:224 224 (gdb) bt #0 QMapData::createNode (left=false, parent=0x0, v=..., k=..., this=0x7fff3c5ed800) at /usr/include/qt5/QtCore/qmap.h:224 #1 QMapNode::copy (this=0x666f53676e697373, d=d@entry=0x7fff3c5ed800) at /usr/include/qt5/QtCore/qmap.h:254 #2 0x766f56c1 in QMap::detach_helper (this=0xb4ddb48) at /usr/include/qt5/QtCore/qmap.h:993 #3 QMap::detach (this=0xb4ddb48) at /usr/include/qt5/QtCore/qmap.h:360 #4 QMap::insert (this=0xb4ddb48, akey=..., avalue=...) at /usr/include/qt5/QtCore/qmap.h:691 #5 0x76862fd0 in Digikam::DImg::setAttribute (this=this@entry=0xb479390, key=..., value=...) at /var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/libs/dimg/dimg.cpp:1043 #6 0x769034bf in Digikam::LoadSaveThread::exifRotate (image=..., filePath=...) at /var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/libs/threadimageio/loadsavethread.cpp:334 #7 0x76915689 in Digikam::PreviewLoadingTask::execute (this=0xb479170) at /var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/libs/threadimageio/previewtask.cpp:392 #8 0x769031ed in Digikam::LoadSaveThread::run (this=0x3b77e50) at /var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/libs/threadimageio/loadsavethread.cpp:133 #9 0x7693faae in Digikam::DynamicThread::DynamicThreadPriv::run (this=0x3b83d30) at /var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/libs/threads/dynamicthread.cpp:183 #10 0x749fb7ad in QThreadPoolThread::run (this=0x7fff68013620) at thread/qthreadpool.cpp:99 #11 0x749fe90a in QThreadPrivate::start (arg=0x7fff68013620) at thread/qthread_unix.cpp:368 #12 0x7178b5c6 in start_thread (arg=0x7fff52ffd700) at pthread_create.c:333 #13 0x73c598cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 (gdb) info threads Id Target Id Frame 3781 Thread 0x7fff53fff700 (LWP 11512) "Thread (pooled)" futex_wait (val=35000, addr=0x7fff582cc014) at /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/libgomp/config/linux/x86/futex.h:45 3724 Thread 0x7fff537fe700 (LWP 11437) "Thread (pooled)" _dl_fixup (l=0x77fb9000, reloc_arg=) at ../elf/dl-runtime.c:83 1872 Thread 0x7fff7bae5700 (LWP 8889) "Thread (pooled)" futex_wait (val=76832, addr=0x7fff6c03f744) at /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/libgomp/config/linux/x86/futex.h:45 1832 Thread 0x7fff7aae3700 (LWP 8841) "Thread (pooled)" pthread_cond_timedwait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 685 Thread 0x7fff49ffb700 (LWP 7294) "Thread (pooled)" futex_wait (val=123104, addr=0x7fff740775b4) at /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/libgomp/config/linux/x86/futex.h:45 651 Thread 0x7fff79ae1700 (LWP 7238) "Thread (pooled)" 0x73c5042d in poll () at ../sysdeps/unix/syscall-template.S:84 585 Thread 0x7fff46ff5700 (LWP 7122) "Thread (pooled)" futex_wait (val=162920, addr=0x7fff5dee0124) at /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/libgomp/config/linux/x86/futex.h:45 577 Thread 0x7fff7b2e4700 (LWP 7114) "Thread (pooled)" 0x73c5042d in poll () at ../sysdeps/unix/syscall-template.S:84 195 Thread 0x7fff792e0700 (LWP 6525) "Thread (pooled)" 0x7fffef2da9f7 in cv::HaarEvaluator::OptFeature::calc (ptr=0x7fffd0c7b7d8, this=0x7fffd4192370) at /var/tmp/portage/media-libs/opencv-3.1.0-r7/work/opencv-3.1.0/modules/objdetect/src/cascadedetect.hpp:403 97 Thread 0x7fff4bfff700 (LWP 6421) "Thread (pooled)" futex_wait (val=147760, addr=0x7fff54914b74) at /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/libgomp/config/linux/x86/futex.h:45 60 Thread 0x7fff7a2e2700 (LWP 6347) "Thread (pooled)" 0x7fffef2d81e8 in cv::HaarEvaluator::setWindow ( this=0x7fff6805a590, pt=..., s
[digikam] [Bug 379470] Crash when performing face detection or recognition on large collection
https://bugs.kde.org/show_bug.cgi?id=379470 Christian changed: What|Removed |Added CC||gen...@moin.fi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379471] New: network issue
https://bugs.kde.org/show_bug.cgi?id=379471 Bug ID: 379471 Summary: network issue Product: Discover Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: michele4st...@gmail.com Target Milestone: --- is impossible to see or install icon, theme, ecc. , discovery doesn't show anything for this category, from system the error indicated is: network issue .4, thanks in advice for your work and your support -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379472] Kwin crashes when attempting to start session.
https://bugs.kde.org/show_bug.cgi?id=379472 kishor...@gmail.com changed: What|Removed |Added Platform|Other |Archlinux Packages Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379471] network issue
https://bugs.kde.org/show_bug.cgi?id=379471 michele4st...@gmail.com changed: What|Removed |Added Platform|Other |Neon Packages Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379472] New: Kwin crashes when attempting to start session.
https://bugs.kde.org/show_bug.cgi?id=379472 Bug ID: 379472 Summary: Kwin crashes when attempting to start session. Product: kwin Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 105323 --> https://bugs.kde.org/attachment.cgi?id=105323&action=edit Backtrace of one such crash. when I select the plasma wayland session, I get a black screen for a second or two, but then get returned to the DM (SDDM). The logs mention that kwin_wayland has crashed (with messages like the following) May 03 15:07:23 arch-testing systemd-coredump[738]: Process 736 (kwin_wayland) of user 1001 dumped core. I have attached a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379378] Discover search crash
https://bugs.kde.org/show_bug.cgi?id=379378 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 379337 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379337] Discover Crashed
https://bugs.kde.org/show_bug.cgi?id=379337 Christoph Feck changed: What|Removed |Added CC||niko...@magnussen.tf --- Comment #1 from Christoph Feck --- *** Bug 379378 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 379450] drag and drop a URL from a browser fails to create a shortcut with the right URL
https://bugs.kde.org/show_bug.cgi?id=379450 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Component|general |general Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org CC||elvis.angelac...@kde.org, ||kdelibs-b...@kde.org Status|UNCONFIRMED |NEEDSINFO Product|dolphin |frameworks-kio --- Comment #1 from Elvis Angelaccio --- Works fine here. What's your KIO version? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379295] System error bell should be wired up to a more pleasant sound by default
https://bugs.kde.org/show_bug.cgi?id=379295 Christoph Feck changed: What|Removed |Added Product|qaccessibilityclient|systemsettings Assignee|gladh...@kde.org|gun...@schmi-dt.de Component|general |kcm_accessibility -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 379354] Control and shift conquer
https://bugs.kde.org/show_bug.cgi?id=379354 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Christoph Feck --- Did you select the 'QtCurve' category by accident, or did you verify that the issue is only visible when using this style engine? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 379254] ksmserver errors after updating to Plasma 5.9.5
https://bugs.kde.org/show_bug.cgi?id=379254 --- Comment #19 from Lubos Lunak --- As this bugreport shows, throwing such errors to stderr means that nobody will notice them, and then distros will happily ship broken apps (that said, I've noticed that kcm_autostart does not one let do anything with global autostart files, not even show them, so if a distro manages to do this, the user won't have an easy way to handle the problem). KRun does a number of things that KProcess-based code doesn't (KDesktopExecParser, KAuthorized, CWD, DiscreteGPU). If they wouldn't be needed for launching .desktop files, then there would be no point in having them in KRun either. And it seems lame to require every place that wants to run a .desktop file to do this manually. I guess it'll be better to move this discussion to kde-core-devel. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379422] not download kde theme debian 8.7.1
https://bugs.kde.org/show_bug.cgi?id=379422 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- Reported as bug 379423. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379473] New: MIPS: add support for rdhwr cycle counter register
https://bugs.kde.org/show_bug.cgi?id=379473 Bug ID: 379473 Summary: MIPS: add support for rdhwr cycle counter register Product: valgrind Version: 3.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: james...@cowgill.org.uk Target Milestone: --- Running valgrind on an executable (n64 little endian) linked against openblas gives: vex mips->IR: unhandled instruction bytes: 0x3B 0x10 0x10 0x7C ==9377== valgrind: Unrecognised instruction at address 0x4aa6dd8. ==9377==at 0x4AA6DD8: ??? (in /usr/lib/libopenblas_mipsp-r0.2.19.so) ==9377==by 0x4AA6D98: ??? (in /usr/lib/libopenblas_mipsp-r0.2.19.so) ==9377== Your program just tried to execute an instruction that Valgrind ==9377== did not recognise. There are two possible reasons for this. ==9377== 1. Your program has a bug and erroneously jumped to a non-code ==9377==location. If you are running Memcheck and you just saw a ==9377==warning about a bad jump, it's probably your program's fault. ==9377== 2. The instruction is legitimate but Valgrind doesn't handle it, ==9377==i.e. it's Valgrind's fault. If you think this is the case or ==9377==you are not sure, please let us know and we'll try to fix it. ==9377== Either way, Valgrind will now raise a SIGILL signal which will ==9377== probably kill your program. ==9377== ==9377== Process terminating with default action of signal 4 (SIGILL): dumping core ==9377== Illegal opcode at address 0x4AA6DD8 ==9377==at 0x4AA6DD8: ??? (in /usr/lib/libopenblas_mipsp-r0.2.19.so) ==9377==by 0x4AA6D98: ??? (in /usr/lib/libopenblas_mipsp-r0.2.19.so) This instruction is: 1bedd8: 7c10103brdhwr s0,hwr_cc I see from the sources there is no support for reading the cycle counter using rdhwr (rd == 2). Given that there is already support for reading the Cavium specific count register, it would seem logical to add support for reading the generic MIPS one. I expect you want to implement reading the ccres register to go with this (rd == 3). The ISA manual states that all R2 processors support these registers. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 379045] Searching in Simple Menu / Application Launcher / KRunner spikes CPU usage ranging from 25% to 100%
https://bugs.kde.org/show_bug.cgi?id=379045 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #9 from Christoph Feck --- Thanks for the update; closing. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 379354] Control and shift conquer
https://bugs.kde.org/show_bug.cgi?id=379354 --- Comment #2 from Hamid --- Made a guess. How to verify? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 379254] ksmserver errors after updating to Plasma 5.9.5
https://bugs.kde.org/show_bug.cgi?id=379254 --- Comment #20 from Harald Sitter --- As I have said, the problem aren't distributions, they are third party developers/apps. In either case the user is neither the distribution nor the third party developer, so you'd be messaging the wrong party if you'd throw a visible error. Relevant list is plasma-devel mind you. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379474] New: KScreen wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 Bug ID: 379474 Summary: KScreen wakes up the monitor right after going to sleep Product: KScreen Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kded Assignee: se...@kde.org Reporter: now...@gmail.com Target Milestone: --- Created attachment 105324 --> https://bugs.kde.org/attachment.cgi?id=105324&action=edit kscreen log when external monitor goes to sleep My laptop is in docking station with external monitor connected (HDMI-2 in the log). Laptop screen is turned off, external monitor is the only output. When external monitor goes to sleep (either automatically after inactivity or with xset dpms force off) it turns off and enables back again right after. The issue is that KScreen kded turns it back on. Unloading kscreen kded module fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 379354] Control and shift conquer
https://bugs.kde.org/show_bug.cgi?id=379354 --- Comment #3 from Christoph Feck --- Please check the active widget style via 'kcmshell5 style'. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 332167] KMail is failing to encrypt PGP/Inline for non-signed key
https://bugs.kde.org/show_bug.cgi?id=332167 --- Comment #9 from kolAflash --- Still not working on openSUSE 42.2 with GnuPG-2.0.24 and KMail-16.08.2. http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/suse/src/gpg2-2.0.24-5.5.src.rpm http://download.opensuse.org/update/leap/42.2/oss/src/kdepim-16.08.2-2.2.1.src.rpm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379475] New: activateLauncherMenu launches wrong launcher with multiple screens
https://bugs.kde.org/show_bug.cgi?id=379475 Bug ID: 379475 Summary: activateLauncherMenu launches wrong launcher with multiple screens Product: plasmashell Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sit...@kde.org CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 shellcoronoa's activateLauncherMenu launches the first launcher it encounters in any panel. When one is using two screens, both with a launcher, this will result in any of them getting launched rather than the most suitable (the one with the active window). -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 310482] nfs share in fstab ganerates 2 mounts in media-list, and 3 after mounting
https://bugs.kde.org/show_bug.cgi?id=310482 fathom changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from fathom --- Not present any more -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 379459] Krusader no longer minimizes to system tray.
https://bugs.kde.org/show_bug.cgi?id=379459 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net --- Comment #1 from Alex Bikadorov --- "Minimize to tray" does what it says: *minimizing* to tray. See Bug 350920. I assume you want a "close to tray" option? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379476] New: Renaming attachments should also change their Content-Disposition/filename attribute
https://bugs.kde.org/show_bug.cgi?id=379476 Bug ID: 379476 Summary: Renaming attachments should also change their Content-Disposition/filename attribute Product: kmail2 Version: 5.4.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: kdeb...@customcdrom.de Target Milestone: --- 1) Attach a file to a message. 2) Right-click the attachment, choose Properties and change the attachment's name. Result: The "Content-Type" "name" attribute is changed, as follows: Content-Type: application/pdf; name="new_name.pdf" The "Content-Disposition" "filename" attribute stays unchanged, though: Content-Disposition: attachment; filename="orig_name.pdf" Somewhat counter-intuitive, this will in most cases cause the attachment to be called "orig_name.pdf" on the receiver's side, not "new_name.pdf" as one might expect when using the properties dialog. By default, the name and filename attributes are set to the same values by kMail, as far as I can see. Either the "name" field should change both values, or there should be a separate "File Name" property. Maybe interesting in this regard: https://mailarchive.ietf.org/arch/msg/ietf-smtp/KtN0TdoHDayKvKycNbsFD-GB-e4# Wishlist item Bug #311179 may be related. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 --- Comment #6 from vst --- Unfortunately I cannot test this now, because I don't have access to an OTP-enabled OpenVPN server. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4
https://bugs.kde.org/show_bug.cgi?id=378827
--- Comment #10 from Francis Herne ---
Correction, it's related to the use of MacOS Classic (why?!) line endings -
i.e. just a carriage return but no newline.
Many places in kdev-python assume that lines can be split with \n, so we should
probably normalise these earlier.
Alternative patch that solves this particular case:
diff --git a/parser/astbuilder.cpp b/parser/astbuilder.cpp
index 0e19f367..15df40a9 100644
--- a/parser/astbuilder.cpp
+++ b/parser/astbuilder.cpp
@@ -98,7 +98,8 @@ private:
class RangeFixVisitor : public AstDefaultVisitor {
public:
RangeFixVisitor(const QString& contents)
-: lines(contents.split('\n')) { };
+// Split on all three variants - \r, \n or \r\n
+: lines(contents.split(QRegExp("\\r\\n?|\\n"))) { };
void visitNode(Ast* node) override {
AstDefaultVisitor::visitNode(node);
--
You are receiving this mail because:
You are watching all bug changes.
[QtCurve] [Bug 379354] Control and shift conquer
https://bugs.kde.org/show_bug.cgi?id=379354 Hamid changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #4 from Hamid --- The active widget style is Breeze. Then I should file this bug somewhere else regarding keyboard input. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379477] New: The file manager does not save file changes on the remote serve
https://bugs.kde.org/show_bug.cgi?id=379477 Bug ID: 379477 Summary: The file manager does not save file changes on the remote serve Product: dolphin Version: 17.04.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kozackunis...@gmail.com Target Milestone: --- I opened the remote directory sftp://root@myHostIP:22/fileToEdit And I tried to edit the file. "Open with ..." of different editors Atom (1.16.0-1) A local copy of the file was created. After the file was modified nothing happened. After the editor was closed, a dialogue appeared to load the local copy of the file to the remote server. Visual Studio Code (1.11.2-1) A local copy of the file was created. After the file was modified nothing happened. After the editor was closed nothing happened. Sublime Text (3.3126-1) A local copy of the file was created. After the file was modified nothing happened. After the editor was closed nothing happened. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379474] KScreen wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 --- Comment #1 from David Rosca --- The issue is when monitor is turned off, KScreen emits output disconnected and KScreenDaemon::outputConnectedChanged reapplies config which turns the monitor back on. I'm not sure what would be correct fix, my workaround is to query DPMS state in KScreenDaemon::outputConnectedChanged and if DPMS state is off, skip the reconfiguration. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 379354] Control and shift conquer
https://bugs.kde.org/show_bug.cgi?id=379354 --- Comment #5 from Hamid --- For anyone's reference, there was a conflict between the keyboard layout change mechanism (Ctrl + Shift) and the normal use of these keys in applications. Changed the keyboard layout change sequence to something else and the symptom is gone. Still it shouldn't interfere, it worked fine in Kubuntu 16.10 and before. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 374300] Option to change the font color on the lock screen
https://bugs.kde.org/show_bug.cgi?id=374300 kishor...@gmail.com changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[libkface] [Bug 377425] libkface FTBFS against opencv-3.2.0
https://bugs.kde.org/show_bug.cgi?id=377425 --- Comment #2 from Rex Dieter --- Re-confimed with 17.04.0 release (and master/ branch which as of now, has no relevant commits beyond v17.04.0 tag as far as I can tell) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379478] New: Plasma Discover Crash on search
https://bugs.kde.org/show_bug.cgi?id=379478 Bug ID: 379478 Summary: Plasma Discover Crash on search Product: Discover Version: 5.9.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: t.m.inbox...@gmail.com Target Milestone: --- Application: plasma-discover (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.8.0-51-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: any time i perfrome a second search in Plasma Discover or press the backspace key in search box 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 0x7efdf61078c0 (LWP 6149))] Thread 9 (Thread 0x7efd7a7fc700 (LWP 7808)): #0 QMutex::lock (this=this@entry=0x1bbd0e0) at thread/qmutex.cpp:225 #1 0x7efdf305f029 in QMutexLocker::QMutexLocker (m=0x1bbd0e0, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:137 #2 QThreadData::canWaitLocked (this=0x1bbd0b0) at ../../include/QtCore/5.7.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253 #3 postEventSourcePrepare (timeout=, s=0x7efd64001810) at kernel/qeventdispatcher_glib.cpp:259 #4 postEventSourceCheck (source=0x7efd64001810) at kernel/qeventdispatcher_glib.cpp:269 #5 0x7efded80bdc1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7efded80c330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7efded80c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7efdf305f75b in QEventDispatcherGlib::processEvents (this=0x7efd64002230, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #9 0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efd7a7fbd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #10 0x7efdf2e39f64 in QThread::exec (this=) at thread/qthread.cpp:507 #11 0x7efdf2e3eb48 in QThreadPrivate::start (arg=0x54849a0) at thread/qthread_unix.cpp:368 #12 0x7efdef8c76ba in start_thread (arg=0x7efd7a7fc700) at pthread_create.c:333 #13 0x7efdf244282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7efd98ff9700 (LWP 7802)): #0 0x7efded850a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7efded80c34e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efded80c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efdf305f75b in QEventDispatcherGlib::processEvents (this=0x7efd80001c90, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efd98ff8d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7efdf2e39f64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7efdf2e3eb48 in QThreadPrivate::start (arg=0x2792e00) at thread/qthread_unix.cpp:368 #7 0x7efdef8c76ba in start_thread (arg=0x7efd98ff9700) at pthread_create.c:333 #8 0x7efdf244282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7efdbf7fe700 (LWP 6159)): #0 0x7efded850a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7efded80b9a0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efded80c2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efded80c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efdf305f75b in QEventDispatcherGlib::processEvents (this=0x7efdac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efdbf7fdd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7efdf2e39f64 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7efdf2e3eb48 in QThreadPrivate::start (arg=0x2a8e0a0) at thread/qthread_unix.cpp:368 #8 0x7efdef8c76ba in start_thread (arg=0x7efdbf7fe700) at pthread_create.c:333 #9 0x7efdf244282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7efdc5ec1700 (LWP 6156)): #0 0x7efdf2436b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7efded80c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efded80c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efdf305f75b in QEventDispatcherGlib::processEvents (this=0x7efdc8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efdc5ec0d00, flags=..., flags@entry=...) at k
[kmail2] [Bug 379479] New: Frequent crashes with kmail in Ubuntu 17.04 (updated kmail)
https://bugs.kde.org/show_bug.cgi?id=379479 Bug ID: 379479 Summary: Frequent crashes with kmail in Ubuntu 17.04 (updated kmail) Product: kmail2 Version: 5.4.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: and...@bolager.com Target Milestone: --- Application: kmail (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-20-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Almost always when selecting a message to view, the program crash. At the longest, I managed to work in it (watching messages, even sending one) for about 20 minutes or so. Usually, it crash right after startup. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f093d633b80 (LWP 3388))] Thread 27 (Thread 0x7f086b9c1700 (LWP 3452)): #0 0x7f09301f4510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f09208582c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f0920858309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f09301ee6da in start_thread (arg=0x7f086b9c1700) at pthread_create.c:456 #4 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 26 (Thread 0x7f08719c0700 (LWP 3440)): #0 0x7f093a5a618d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f092e421576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f092e42168c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f093b0e0f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f093b08a88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f093aeb7fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f093aebcc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f09301ee6da in start_thread (arg=0x7f08719c0700) at pthread_create.c:456 #8 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 25 (Thread 0x7f0896ffd700 (LWP 3420)): #0 0x7f09301f4510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0925b1dc09 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f0925b1e209 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f0925b1e3c0 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0925b1ad5c in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f09301ee6da in start_thread (arg=0x7f0896ffd700) at pthread_create.c:456 #6 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 24 (Thread 0x7f08977fe700 (LWP 3419)): #0 0x7f093a5a1cad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0912b7c611 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #2 0x7f091bdec21e in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f091bdecc90 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f091bdecd50 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f091bdfad39 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f0912bab7d8 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #7 0x7f09301ee6da in start_thread (arg=0x7f08977fe700) at pthread_create.c:456 #8 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 23 (Thread 0x7f0897fff700 (LWP 3418)): #0 0x7f093a5c013c in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f093a5c1d44 in ___fprintf_chk (fp=0x7f093a86d750 <_IO_stdfile_2_lock>, flag=1, format=0x7f0918b737b4 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f0918b5b51e in () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #3 0x7f0918b5b714 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #4 0x7f0918b5fd38 in () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #5 0x7f0918b49efa in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #6 0x7f0925ac92aa in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0925b05a84 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0925aef9d5 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0925b1e9ea in () at /usr/lib/x86_64-linux-gnu/libQt5Web
[dolphin] [Bug 357542] [Feature request] Working "Recently used files / folders"
https://bugs.kde.org/show_bug.cgi?id=357542 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379480] New: Random kWin crashes
https://bugs.kde.org/show_bug.cgi?id=379480 Bug ID: 379480 Summary: Random kWin crashes Product: kwin Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: aaroncdcalc...@gmail.com Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-20-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Setting up a virtual machine using Oracle Virtual Box version 5.1.18 (Just closed the virtual machine Settings window by clicking OK). The error reproduces constantly whenever I do the same thing. - Unusual behavior I noticed: This error also happens when I'm using Gwenview, sometimes when I start it, other times when I move or resize the window, but it's not constant. The whole desktop restarts, and the windows move around a bit when it starts again. The crash can be reproduced every time. -- 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 0x7fa5f76f5980 (LWP 1808))] Thread 6 (Thread 0x7fa5cacb9700 (LWP 2258)): #0 0x7fa5f0828510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa5f47cab4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa5efc59495 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fa5efc59d8a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fa5f47c9c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa5f08226da in start_thread (arg=0x7fa5cacb9700) at pthread_create.c:456 #6 0x7fa5f712e17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7fa5bb5ef700 (LWP 1968)): #0 0x7fa5f7122251 in __GI_ppoll (fds=0x7fa5b4000ae8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fa5f49e9251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa5f49eab4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa5f499788a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa5f47c4fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa5ef58fdf5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fa5f47c9c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa5f08226da in start_thread (arg=0x7fa5bb5ef700) at pthread_create.c:456 #8 0x7fa5f712e17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7fa5ba604700 (LWP 1914)): #0 0x7fa5f0828510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa5f3b532c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fa5f3b53309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fa5f08226da in start_thread (arg=0x7fa5ba604700) at pthread_create.c:456 #4 0x7fa5f712e17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fa5c97f3700 (LWP 1906)): #0 0x7fa5f7122251 in __GI_ppoll (fds=0x7fa5cae8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fa5f49e9251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa5f49eab4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa5f499788a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa5f47c4fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa5ef58fdf5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fa5f47c9c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa5f08226da in start_thread (arg=0x7fa5c97f3700) at pthread_create.c:456 #8 0x7fa5f712e17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fa5db833700 (LWP 1821)): #0 0x7fa5f712218d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa5ebd4c576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa5ebd4c68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa5f49edf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa5f499788a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa5f47c4fe3 in QThread::exec() () at /usr
[Breeze] [Bug 374300] Option to change the font color on the lock screen
https://bugs.kde.org/show_bug.cgi?id=374300 Rog131 changed: What|Removed |Added CC||samrog...@hotmail.com --- Comment #3 from Rog131 --- Dublicate / same kind of as Bug 369676 - White lockscreen text's readability depends on background - https://bugs.kde.org/show_bug.cgi?id=369676 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369676] White lockscreen text's readability depends on background
https://bugs.kde.org/show_bug.cgi?id=369676 --- Comment #5 from Rog131 --- Dublicate / same kind of as Bug 374300 - Option to change the font color on the lock screen - https://bugs.kde.org/show_bug.cgi?id=374300 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 379481] New: would like ability to manually sort menu items
https://bugs.kde.org/show_bug.cgi?id=379481 Bug ID: 379481 Summary: would like ability to manually sort menu items Product: kmenuedit Version: 5.9.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: wizard10...@gmail.com Target Milestone: --- Wishlist item - I use the classic desktop menu in Plasma 5.9.5 and would like the ability to manually sort the applications I stick in this menu. For example, dolphin comes up first on the menu even though I'd prefer it was google-chrome and shutdown is in the bottom third of the application list although I'd really like to have it at the bottom. Coming from fluxbox and openbox my workflow is kinda used to having my top ten applications on a right-click menu in the order I specify. Can we add an option to manually sort these items if the user doesn't want to sort by name or description? Thank you - -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 170124] set as wallpaper option
https://bugs.kde.org/show_bug.cgi?id=170124 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com --- Comment #20 from Dr. Chapatin --- Almost nine years later and this feature is still missing... Dear devs, give us this useful feature please. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379465] kwin_x11 crashes after mpv is set to fullscreen
https://bugs.kde.org/show_bug.cgi?id=379465 Martin Gräßlin changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- As always for arch users the backtrace is completely useless as it's missing debug symbols. Nothing we can do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379480] Random kWin crashes
https://bugs.kde.org/show_bug.cgi?id=379480 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- *** 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 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 Martin Gräßlin changed: What|Removed |Added CC||aaroncdcalc...@gmail.com --- Comment #67 from Martin Gräßlin --- *** Bug 379480 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379472] Kwin crashes when attempting to start session.
https://bugs.kde.org/show_bug.cgi?id=379472 Martin Gräßlin changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortuntely the debug symbols for Qt are missing and it crashes directly when creating the QApplication. Given the information we have from it: do you have the KWin QPA plugin installed to the correct location so that Qt finds it? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379476] Renaming attachments should also change their Content-Disposition/filename attribute
https://bugs.kde.org/show_bug.cgi?id=379476 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org --- Comment #1 from Laurent Montel --- It's already fixed in 5.5.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379482] New: Krita does not recognize touch input on Windows 10 TrekStore SurfTab twin 11.6
https://bugs.kde.org/show_bug.cgi?id=379482 Bug ID: 379482 Summary: Krita does not recognize touch input on Windows 10 TrekStore SurfTab twin 11.6 Product: krita Version: 3.1.3 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: task Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: m.pat...@hotmail.de Target Milestone: --- Created attachment 105325 --> https://bugs.kde.org/attachment.cgi?id=105325&action=edit Mouse movemend between line 56 and 174, Line 101 and 103 mousebutton: both "Blocked" Krita doesen't move the Cursor on the painting-screen. Other Actions work. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368179] Freehand brush tool does not support touch screen painting
https://bugs.kde.org/show_bug.cgi?id=368179 Boudewijn Rempt changed: What|Removed |Added CC||m.pat...@hotmail.de --- Comment #4 from Boudewijn Rempt --- *** Bug 379482 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379482] Krita does not recognize touch input on Windows 10 TrekStore SurfTab twin 11.6
https://bugs.kde.org/show_bug.cgi?id=379482 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |DUPLICATE CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 368179 *** -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 379082] Unit tests are failing in Debian Stretch (9)
https://bugs.kde.org/show_bug.cgi?id=379082 Milian Wolff changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Milian Wolff --- commit 3ddc8ba3c751436fddd2969ba349a76ab6b7f8d1 Author: Milian Wolff Date: Wed May 3 17:35:18 2017 +0200 Filter zero frames from the end of the stack returned by libunwind Some (older) versions of libunwind eratically return zero frames at the end of the stack. This happened on Debian and Ubuntu with the distro provided libunwind. In such situations, we now skip these uninteresting frames. BUG: 379082 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379472] Kwin crashes when attempting to start session.
https://bugs.kde.org/show_bug.cgi?id=379472 --- Comment #2 from kishor...@gmail.com --- (In reply to Martin Gräßlin from comment #1) > Given the information we have from it: do > you have the KWin QPA plugin installed to the correct location so that Qt > finds it? How can I check if I have it? I'm not sure if this is related, but when I type 'kwin_wayland --version', I get the following output: kwin_wayland --version This application failed to start because it could not find or load the Qt platform plugin "wayland-org.kde.kwin.qpa" in "". Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Reinstalling the application may fix this problem. fish: “kwin_wayland --version” terminated by signal SIGABRT (Abort) However, typing 'kwin_x11 --version' gives just the application name and version number as expected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372672] File Renaming Options sidebar is missing
https://bugs.kde.org/show_bug.cgi?id=372672 --- Comment #5 from John --- I'm running Digikam 5.4 (build 4:5.4.0-0ubuntu3, the distribution's version) with Ubuntu 17.04 x64 (upgrade) and the problem has returned. https://www.flickr.com/photos/39126243@N03/34045069610/in/dateposted-public/ Only the GeoLocations sidebar is shown - can I get the Settings sidebar to display on the Import window with this version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379472] Kwin crashes when attempting to start session.
https://bugs.kde.org/show_bug.cgi?id=379472 --- Comment #3 from kishor...@gmail.com --- On further digging, I found that this happens when I'm using qt 5.9 beta 3. Using qt 5.8, the wayland session launches normally. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378679] Intel modeseting drive intense tear with Skylake CPUs
https://bugs.kde.org/show_bug.cgi?id=378679 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #3 from Christoph Feck --- To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 379483] New: ktorrent PID: 5740 Señal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=379483 Bug ID: 379483 Summary: ktorrent PID: 5740 Señal: Segmentation fault Product: ktorrent Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: ernestopereslo...@yahoo.es Target Milestone: --- Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9b70d98840 (LWP 5740))] Thread 10 (Thread 0x7f9b0d7fa700 (LWP 5789)): #0 0x7f9b66308b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9b6b9994c6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f9b6b994bc4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f9b0700 (LWP 5786)): #0 0x7f9b66308b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9b6b9994c6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f9b6b994bc4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f9aed7fa700 (LWP 5780)): #0 0x7f9b66308756 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9b6b99958b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f9b706a6388 in ?? () from /usr/lib/libktorrent.so.6 #3 0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f9aedffb700 (LWP 5778)): #0 0x7f9b6ad72889 in syscall () from /usr/lib/libc.so.6 #1 0x7f9b6b98f865 in QBasicMutex::lockInternal() () from /usr/lib/libQt5Core.so.5 #2 0x7f9b6b98f922 in QMutex::lock() () from /usr/lib/libQt5Core.so.5 #3 0x7f9b706a2d3c in ?? () from /usr/lib/libktorrent.so.6 #4 0x7f9b706a3589 in ?? () from /usr/lib/libktorrent.so.6 #5 0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f9aee7fc700 (LWP 5777)): [KCrash Handler] #6 0x7f9b6ba13fd4 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f9b706e6f66 in ?? () from /usr/lib/libktorrent.so.6 #8 0x7f9b706e7d94 in ?? () from /usr/lib/libktorrent.so.6 #9 0x7f9b706e5508 in ?? () from /usr/lib/libktorrent.so.6 #10 0x7f9b706e62a3 in ?? () from /usr/lib/libktorrent.so.6 #11 0x7f9b706a887f in ?? () from /usr/lib/libktorrent.so.6 #12 0x7f9b706a4a24 in ?? () from /usr/lib/libktorrent.so.6 #13 0x7f9b706a39ca in ?? () from /usr/lib/libktorrent.so.6 #14 0x7f9b706a3551 in ?? () from /usr/lib/libktorrent.so.6 #15 0x7f9b706a3589 in ?? () from /usr/lib/libktorrent.so.6 #16 0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5 #17 0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0 #18 0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f9b44f9a700 (LWP 5748)): #0 0x7f9b66308ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9b4704ee44 in ?? () from /usr/lib/libGLX_nvidia.so.0 #2 0x7f9b45d66394 in ?? () from /usr/lib/libnvidia-glcore.so.378.13 #3 0x7f9b4704e12c in ?? () from /usr/lib/libGLX_nvidia.so.0 #4 0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f9b53fff700 (LWP 5745)): #0 0x7fffdcda5939 in ?? () #1 0x7fffdcda5bc5 in clock_gettime () #2 0x7f9b6ad84826 in clock_gettime () from /usr/lib/libc.so.6 #3 0x7f9b6bbc7231 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f9b6bbc59f9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/libQt5Core.so.5 #5 0x7f9b6bbc5fa5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/libQt5Core.so.5 #6 0x7f9b6bbc7904 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f9b63ce4e8d in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #8 0x7f9b63ce58db in ?? () from /usr/lib/libglib-2.0.so.0 #9 0x7f9b63ce5acc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #10 0x7f9b6bbc809b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #11 0x7f9b6bb718ca in QEventLoop::exec(QFlag
[kdevelop] [Bug 379484] New: KDevelop disregards target property OUTPUT_NAME
https://bugs.kde.org/show_bug.cgi?id=379484 Bug ID: 379484 Summary: KDevelop disregards target property OUTPUT_NAME Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: CMake Assignee: kdevelop-bugs-n...@kde.org Reporter: aspotas...@gmail.com Target Milestone: --- KDevelop disregards target property OUTPUT_NAME when auto-detecting executable path for launch configuration. Steps to reproduce: 1. Create a cmake target (e.g. "abc"); set its property OUTPUT_NAME to something else, e.g. "xyz_binary": set_property(TARGET abc PROPERTY OUTPUT_NAME "xyz_binary") 2. Go to Run -> Run Configurations... 3. Use the "Add" drop-down to add a run configuration for the target "abc". 4. Press Shift+F9 to run the target. Actual results: it tries to run "abc" which does not exist. Expected results: run "xyz_binary". -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 379483] ktorrent PID: 5740 Señal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=379483 --- Comment #1 from ernestopereslo...@yahoo.es --- Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb69f7da840 (LWP 6449))] Thread 8 (Thread 0x7fb60700 (LWP 6487)): #0 0x7fb694d48756 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb69a3d958b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fb69f0e6388 in ?? () from /usr/lib/libktorrent.so.6 #3 0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7fb6997b754f in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7fb624ff9700 (LWP 6484)): #0 0x7fb6997b2889 in syscall () from /usr/lib/libc.so.6 #1 0x7fb69a3cf865 in QBasicMutex::lockInternal() () from /usr/lib/libQt5Core.so.5 #2 0x7fb69a3cf922 in QMutex::lock() () from /usr/lib/libQt5Core.so.5 #3 0x7fb69f0e2d3c in ?? () from /usr/lib/libktorrent.so.6 #4 0x7fb69f0e3589 in ?? () from /usr/lib/libktorrent.so.6 #5 0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7fb6997b754f in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fb6257fa700 (LWP 6483)): [KCrash Handler] #6 0x7fb69a459ecc in QString::indexOf(QChar, int, Qt::CaseSensitivity) const () from /usr/lib/libQt5Core.so.5 #7 0x7fb69f126f66 in ?? () from /usr/lib/libktorrent.so.6 #8 0x7fb69f127d94 in ?? () from /usr/lib/libktorrent.so.6 #9 0x7fb69f125508 in ?? () from /usr/lib/libktorrent.so.6 #10 0x7fb69f1262a3 in ?? () from /usr/lib/libktorrent.so.6 #11 0x7fb69f0e887f in ?? () from /usr/lib/libktorrent.so.6 #12 0x7fb69f0e4a24 in ?? () from /usr/lib/libktorrent.so.6 #13 0x7fb69f0e39ca in ?? () from /usr/lib/libktorrent.so.6 #14 0x7fb69f0e3551 in ?? () from /usr/lib/libktorrent.so.6 #15 0x7fb69f0e3589 in ?? () from /usr/lib/libktorrent.so.6 #16 0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5 #17 0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0 #18 0x7fb6997b754f in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fb66dc52700 (LWP 6456)): #0 0x7fb694d48ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb66fd06e44 in ?? () from /usr/lib/libGLX_nvidia.so.0 #2 0x7fb66ea1e394 in ?? () from /usr/lib/libnvidia-glcore.so.378.13 #3 0x7fb66fd0612c in ?? () from /usr/lib/libGLX_nvidia.so.0 #4 0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7fb6997b754f in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fb682ab2700 (LWP 6454)): #0 0x7fb69a60785e in ?? () from /usr/lib/libQt5Core.so.5 #1 0x7fb692724e8d in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7fb6927258db in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fb692725acc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fb69a60809b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb69a5b18ca in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fb69a3d3a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fb6997b754f in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb6822a2700 (LWP 6453)): #0 0x7fb6997ad67d in poll () from /usr/lib/libc.so.6 #1 0x7fb6927259b6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fb692725acc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fb69a60809b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fb69a5b18ca in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb69a3d3a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fb6997b754f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb6832da700 (LWP 6451)): #0 0x7fb69276b1c9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7fb6927249b4 in g_main_context_release () from /usr/lib/libglib-2.0.so.0 #2 0x7fb69272596a in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fb692725acc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fb69a60809b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb69a5b18ca in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fb69a3d3a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fb698d11125 in ?? () from /usr/lib/libQt5DBus.so.5 #8 0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5
[kile] [Bug 379435] The settings menu mising kile config item
https://bugs.kde.org/show_bug.cgi?id=379435 --- Comment #1 from Jonathan Verner --- I have more info: Although the Configure Keyboard Shortcuts menu entry is also missing, I can assign a global shortcut to this action in systemsettings. Then, I use this shortcut to open the config in kile and assign a shortcut to the settings dialog. However, the settings dialog does not open even after activating it via this new keyboard shortcut. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379485] New: infinit switch
https://bugs.kde.org/show_bug.cgi?id=379485 Bug ID: 379485 Summary: infinit switch Product: KScreen Version: 5.9.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: common Assignee: se...@kde.org Reporter: t...@tuor.org Target Milestone: --- Created attachment 105326 --> https://bugs.kde.org/attachment.cgi?id=105326&action=edit printf "[Rules]\nkscreen.*=true" >> ~/.config/QtProject/qtlogging.ini; kscreen-console bug > $(tempfile) Hi Folks I'm running KDE Neon 5.9 (current version, all up to date). Symptom: Infinit wwitching of Display configurations. It does just switch and switch and switch an so on. It just don't stop. When does it occure? Most of the time when I just connected a new screen. But sometimtes when i unlock my screen. For example I'm off wokring for 30 minutes, come back, unlock the screen and it happens. It ONLY happens, when I have a secondary screen connected. Workaround: reboot! After a reboot all is fine again. How often? Today 3 Times! Other days never. From time to time it just happens randomly. Like 2 times a week. Pleas tell me if I can do something to get this bug solved! Salutations Aaron -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #190 from Frits Spieker --- But is one of the developers actually looking at this? The duplication of the messages, combined with the akonadi hanging itself out to dry when deleting messages (resulting in the famous "retrieving folder content" screen) makes KMail basically unusable. I'm really baffled how such a crucial piece of software (unless developers use other program to read email) can be so broken for so long. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378931] Add ISA 3.0B additional isnstructions, add OV32, CA32 setting support
https://bugs.kde.org/show_bug.cgi?id=378931 Carl Love changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Carl Love --- Attached patch was committed, Vex commit 3359 The test case result files, test case changes are in Valgrind commit 16329 There is a lot of changes to the test case outputs. I think it is all fine but will leave this Bug open until I verify the regression tests are OK. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #191 from Martin Koller --- I am currently looking into this and have already implemented some patches which hopefully improve the situation (although I have no final fix yet). E.g. https://phabricator.kde.org/D5667 It's very complicated and has to do with timing of messages between 3 processes ... -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 379486] New: Konqueror UI is hard to use for people with limited eyesight.
https://bugs.kde.org/show_bug.cgi?id=379486 Bug ID: 379486 Summary: Konqueror UI is hard to use for people with limited eyesight. Product: konqueror Version: 5.0.97 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: r03...@gmail.com Target Milestone: --- Hello, I am not the one experiencing the problem, but there was a user (who wished to not submit a report themselves) that was having trouble using the newest version of Konquerer due to UI changes and poor eyesight. 2. The menu shows no icons, only text; buttons like open new tab/close current tab show no icons, making difficult to guess. <...> 7. Konqueror Introduction page, no icons; unless I hover over them, hyperlinked titles shown in dark grey over a blue background. I know my eye sight is not as good as it used to be, but this is really akin to usability sabotage. This was, of course, accompanied by other complaints, but I feel this issue is important enough to take out of context for submission to this tracker. If I had to guess I think the issue stems from the adoption, knowingly or unknowingly, of what is now called "material design"*. While I quite like most interfaces produced using design guidelines that one could say are material design please take note that it is very very easy to produce incomprehensible UIs following Google's guidelines (and Google has done some of this). * Material design actually existed for a number of years before Google started using it under that name. It was "created" by FOSS projects who didn't have any artists that decided to draw colored rectangles with text in them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379442] AppImage package does not find the files needed for panorama
https://bugs.kde.org/show_bug.cgi?id=379442 --- Comment #2 from philippe.quag...@laposte.net --- Yes, it works well. Many thanks ! The «export to remote folder» function has been removed until it works again ? Is there another mean to copy an image to another folder ? Best regards. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #57 from Eugene Shalygin --- With the patch from comment 54 applied, it crashes with Qt 5.9.0 beta 3 with the following stacktrace: #6 0x7f42b7f24981 in QInternal::unregisterCallback(QInternal::Callback, bool (*)(void**)) () from /usr/lib64/libQt5Core.so.5 #7 0x7f42a73bbdde in QtCurve::StylePlugin::~StylePlugin() () from /usr/lib64/qt5/plugins/styles/qtcurve.so #8 0x7f42a73bbe89 in QtCurve::StylePlugin::~StylePlugin() () from /usr/lib64/qt5/plugins/styles/qtcurve.so #9 0x7f42b80bef11 in QLibraryPrivate::unload(QLibraryPrivate::UnloadFlag) () from /usr/lib64/libQt5Core.so.5 #10 0x7f42b80b5b32 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() () from /usr/lib64/libQt5Core.so.5 #11 0x7f42b80b5c59 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() () from /usr/lib64/libQt5Core.so.5 #12 0x7f42b80f57c7 in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #13 0x7f42b80b5001 in QFactoryLoader::~QFactoryLoader() () from /usr/lib64/libQt5Core.so.5 #14 0x7f42b896d4b9 in (anonymous namespace)::Q_QGS_loader::innerFunction()::Holder::~Holder() () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f42b72249e0 in __run_exit_handlers () from /lib64/libc.so.6 #16 0x7f42b7224a3a in exit () from /lib64/libc.so.6 #17 0x7f42b7fe04b4 in QCommandLineParser::showHelp(int) () from /usr/lib64/libQt5Core.so.5 #18 0x0040f9b1 in main () -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379442] AppImage package does not find the files needed for panorama
https://bugs.kde.org/show_bug.cgi?id=379442 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.6.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from caulier.gil...@gmail.com --- yes, Remote storage tool is disabled in AppImage. It fact KIO dependencies do not work at run time. An alternative need to be found to replace it. Q : Does Panorama tool work as expected to stitch images together ? Which Hugin version do you use exactly ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #58 from RJVB --- Quick reaction: are you using the latest version in git - if not, could you please pull the latest version and rebuild with debug info so I can see how you get into `unregisterCallback()`? This is running `foo --help`? -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #59 from Eugene Shalygin --- Latest version of QtCurve? Yes. Thread 1 "kdialog" received signal SIGSEGV, Segmentation fault. 0x7235c981 in QInternal::unregisterCallback(QInternal::Callback, bool (*)(void**)) () from /usr/lib64/libQt5Core.so.5 (gdb) bt #0 0x7235c981 in QInternal::unregisterCallback(QInternal::Callback, bool (*)(void**)) () from /usr/lib64/libQt5Core.so.5 #1 0x7fffe17ce489 in QtCurve::StylePlugin::~StylePlugin (this=0x680500, __in_chrg=) at /usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:153 #2 0x7fffe17ce4e4 in QtCurve::StylePlugin::~StylePlugin (this=0x680500, __in_chrg=) at /usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:159 #3 0x724f6f11 in QLibraryPrivate::unload(QLibraryPrivate::UnloadFlag) () from /usr/lib64/libQt5Core.so.5 #4 0x724edb32 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() () from /usr/lib64/libQt5Core.so.5 #5 0x724edc59 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() () from /usr/lib64/libQt5Core.so.5 #6 0x7252d7c7 in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #7 0x724ed001 in QFactoryLoader::~QFactoryLoader() () from /usr/lib64/libQt5Core.so.5 #8 0x72da54b9 in (anonymous namespace)::Q_QGS_loader::innerFunction()::Holder::~Holder() () from /usr/lib64/libQt5Widgets.so.5 #9 0x7165c9e0 in __run_exit_handlers () from /lib64/libc.so.6 #10 0x7165ca3a in exit () from /lib64/libc.so.6 #11 0x724184b4 in QCommandLineParser::showHelp(int) () from /usr/lib64/libQt5Core.so.5 #12 0x0040f9b1 in main () This is from running `gdb kdialog` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)
https://bugs.kde.org/show_bug.cgi?id=371494 Lukas Polacek changed: What|Removed |Added CC||lu...@ksp.sk -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #60 from Eugene Shalygin --- BTW, https://codereview.qt-project.org/180231 & https://codereview.qt-project.org/180232 are applied too. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 376395] libreoffice and the xorg-xserver-video-intel-native-modesetting
https://bugs.kde.org/show_bug.cgi?id=376395 --- Comment #4 from PK --- I'm sorry for the very late reaction. I really don't think the kde-integration of libreoffice could be the real guilty one. I mean this started after neon switched to the new intel video driver (native-modesetting). And that driver isn't at all developed by LibreOffice. I tried to go back to the old video driver but that doesn't seem possible any more. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 379477] The file manager does not save file changes on the remote serve
https://bugs.kde.org/show_bug.cgi?id=379477 Elvis Angelaccio changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org Component|general |general CC||elvis.angelac...@kde.org, ||kdelibs-b...@kde.org Product|dolphin |frameworks-kio Version|17.04.0 |unspecified --- Comment #1 from Elvis Angelaccio --- Can you try again making sure to have only ONE instance of Atom or VSCode or Sublime running? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379226] digiKam Properties Metadata not shown in Editor Captions
https://bugs.kde.org/show_bug.cgi?id=379226 --- Comment #2 from Geoff King --- Okay that fixed it. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379226] digiKam Properties Metadata not shown in Editor Captions
https://bugs.kde.org/show_bug.cgi?id=379226 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED Version Fixed In||5.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372672] File Renaming Options sidebar is missing
https://bugs.kde.org/show_bug.cgi?id=372672 --- Comment #6 from caulier.gil...@gmail.com --- The tab view exists but are reduced to the minimum due to lack of icon on your system. Use Universal Linux AppImage instead. Current pre-version 5.6.0 is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #61 from RJVB --- That looks like it should be unrelated at least to the purpose of my patch. There is a tiny possibility though that the event callback is called during destruction, and that it obtains a stale pointer to the object's style. Could you try moving the if with the unregisterCallback() call to immediately after the qtcInfo call and report back, please? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #192 from Frits Spieker --- Excellent! Good to know there is some progress. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #62 from Eugene Shalygin --- Moved, but the stack trace is the same: #6 0x7f9b4acea981 in QInternal::unregisterCallback(QInternal::Callback, bool (*)(void**)) () from /usr/lib64/libQt5Core.so.5 #7 0x7f9b3a160364 in QtCurve::StylePlugin::~StylePlugin (this=0x21efe50, __in_chrg=) at /usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:144 #8 0x7f9b3a1604e4 in QtCurve::StylePlugin::~StylePlugin (this=0x21efe50, __in_chrg=) at /usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:159 #9 0x7f9b4ae84f11 in QLibraryPrivate::unload(QLibraryPrivate::UnloadFlag) () from /usr/lib64/libQt5Core.so.5 #10 0x7f9b4ae7bb32 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() () from /usr/lib64/libQt5Core.so.5 #11 0x7f9b4ae7bc59 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() () from /usr/lib64/libQt5Core.so.5 #12 0x7f9b4aebb7c7 in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #13 0x7f9b4ae7b001 in QFactoryLoader::~QFactoryLoader() () from /usr/lib64/libQt5Core.so.5 #14 0x7f9b4b7334b9 in (anonymous namespace)::Q_QGS_loader::innerFunction()::Holder::~Holder() () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f9b49fea9e0 in __run_exit_handlers () from /lib64/libc.so.6 #16 0x7f9b49feaa3a in exit () from /lib64/libc.so.6 #17 0x7f9b4ada64b4 in QCommandLineParser::showHelp(int) () from /usr/lib64/libQt5Core.so.5 #18 0x0040f9b1 in main () -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 379487] New: Elisa doesn’t handle non-default font/display settings
https://bugs.kde.org/show_bug.cgi?id=379487 Bug ID: 379487 Summary: Elisa doesn’t handle non-default font/display settings Product: elisa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: k...@huftis.org Target Milestone: --- Created attachment 105327 --> https://bugs.kde.org/attachment.cgi?id=105327&action=edit Screenshot showing layout problems in Elisa Elisa doesn’t seem to handle non-default font/display settings properly. It’s a bit difficult to explain the problem, so I’ll attach a screenshot showing how Elisa looks on my system. Here’s the problems I observe: - Overlapping text - Too small spacing between lines of text - Inconsistent font size - Parts of application window hidden (lower right part) - Non-working widgets (because of overlapping text) Note that I use a larger font size than the default. Other KDE applications handle this fine, but Elisa doesn’t. (Perhaps due to pixel-based hardcoding of element positions instead of letting Qt and its layout algorithms take care of it?) -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #63 from RJVB --- And you don't get that crash without the patch? See https://phabricator.kde.org/D5702 for a version which already moved the unregisterCallback() call. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #64 from Eugene Shalygin --- (In reply to RJVB from comment #63) > And you don't get that crash without the patch? With 5.9 it crashes under any conditions, albeit with different stack traces. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 376395] libreoffice and the xorg-xserver-video-intel-native-modesetting
https://bugs.kde.org/show_bug.cgi?id=376395 --- Comment #5 from Martin Gräßlin --- You reported this bug against Plasma-integration. Neither Neon, nor libreoffice, nor the libreoffice-kde integration are developed by Plasma developers. I'm sorry, you are wrong here. -- You are receiving this mail because: You are watching all bug changes.
