[kalgebra] [Bug 402410] New: kalgebra crashed when edit a created function
https://bugs.kde.org/show_bug.cgi?id=402410 Bug ID: 402410 Summary: kalgebra crashed when edit a created function Product: kalgebra Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: nuria3es...@gmail.com Target Milestone: --- SUMMARY My teacher would to make some exercises in Kalgebra, when I do it, I discovered that when I would like to edit a creation function, and when I press any button, this crashed and leaves the app. STEPS TO REPRODUCE 1. Created a function. 2. Save it. 3. Edit the function to the right column. 4. Press any button. 5.The app crashes and leaves it. EXPECTED RESULT Edit the function. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.5.5 (available in About System) KDE Plasma Version: 5.5.5 KDE Frameworks Version: 5.5.5 Qt Version: 5.5.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402409] Save the last session when the funtion created by default
https://bugs.kde.org/show_bug.cgi?id=402409 eva4es...@gmail.com changed: What|Removed |Added Summary|Save the last session when |Save the last session when |the funtion created by the |the funtion created by |fault |default -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402409] Save the last session when the function created by default
https://bugs.kde.org/show_bug.cgi?id=402409 eva4es...@gmail.com changed: What|Removed |Added Summary|Save the last session when |Save the last session when |the funtion created by |the function created by |default |default -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402409] New: Save the last session when the funtion created by the fault
https://bugs.kde.org/show_bug.cgi?id=402409 Bug ID: 402409 Summary: Save the last session when the funtion created by the fault Product: kalgebra Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: eva4es...@gmail.com Target Milestone: --- SUMMARY: When I finish my session, the application does not save the session so I lost all my created functions. STEPS TO REPRODUCE 1. I start using the application. 2. I just used the application. 3.The application does not save the session. OBSERVED RESULT The application does not save the session. EXPECTED RESULT The application saves the session and I recover my function created. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.5.5 KDE Frameworks Version: 5.21.0 Qt Version: 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[step] [Bug 402408] New: I'll like a button to make come back the particle to the start point
https://bugs.kde.org/show_bug.cgi?id=402408 Bug ID: 402408 Summary: I'll like a button to make come back the particle to the start point Product: step Version: 0.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: stepcore Assignee: ks.vladi...@gmail.com Reporter: victor3es...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[step] [Bug 402408] I'll like a button to make come back the particle to the start point
https://bugs.kde.org/show_bug.cgi?id=402408 Pepito changed: What|Removed |Added Component|stepcore|general -- You are receiving this mail because: You are watching all bug changes.
[step] [Bug 402407] New: add explanations
https://bugs.kde.org/show_bug.cgi?id=402407 Bug ID: 402407 Summary: add explanations Product: step Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ks.vladi...@gmail.com Reporter: vicky3es...@gmail.com Target Milestone: --- SUMMARY Add a tab where you explain all the tools of the application Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402406] New: Need a tutorial
https://bugs.kde.org/show_bug.cgi?id=402406 Bug ID: 402406 Summary: Need a tutorial Product: kalgebra Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: pablo4eso...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402404] I will add operation buttons like a squaret button for example
https://bugs.kde.org/show_bug.cgi?id=402404 Pepito changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402405] New: delete an operation
https://bugs.kde.org/show_bug.cgi?id=402405 Bug ID: 402405 Summary: delete an operation Product: kalgebra Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: vicky3es...@gmail.com Target Milestone: --- SUMMARY when I want to delete an operation all are deleted. That only one operation be deleted SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402404] New: I will add operation buttons like a squaret button for example
https://bugs.kde.org/show_bug.cgi?id=402404 Bug ID: 402404 Summary: I will add operation buttons like a squaret button for example Product: kalgebra Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: victor3es...@gmail.com Target Milestone: --- SUMMARY I will add operation buttons like a squaret button for example -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402403] Save the last session when the funtion created by the fault
https://bugs.kde.org/show_bug.cgi?id=402403 eva4es...@gmail.com changed: What|Removed |Added Summary|Save the last session when |Save the last session when |the funtion created by the |the funtion created by the ||fault -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402403] New: Save the last session when the funtion created by the
https://bugs.kde.org/show_bug.cgi?id=402403 Bug ID: 402403 Summary: Save the last session when the funtion created by the Product: kalgebra Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: eva4es...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 302667] Cannot use fam15h_power sensor in Ksysguard
https://bugs.kde.org/show_bug.cgi?id=302667 --- Comment #7 from Domonkos Lezsák --- It looks like sometimes my `radeon-pci-0200` errors out, but `k10temp-pci-00xx` works always as excepted. I can't find a way to reproduce the radeon sensor issue. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 402402] New: gtk3-engines-breeze conflicts with breeze-gtk-theme from Kubuntu
https://bugs.kde.org/show_bug.cgi?id=402402 Bug ID: 402402 Summary: gtk3-engines-breeze conflicts with breeze-gtk-theme from Kubuntu Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: tonal.proms...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY gtk3-engines-breeze conflicts with breeze-gtk-theme from Kubuntu SOFTWARE/OS VERSIONS OS: KDE neon 5.14 Version KDE Plasma: 5.14.4 Version Qt: 5.11.2 Version KDE Frameworks: 5.53.0 Kernel version: 4.15.0-43-generic Arch: 64-bit Procs: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 19.5 gb ADDITIONAL INFORMATION Migrateв from Kubuntu 2-3 years ago. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401940] More than one Assistant Tool causes black rectangle to appear
https://bugs.kde.org/show_bug.cgi?id=401940 --- Comment #1 from weavermarqu...@gmail.com --- This may be helpful: This bug seems to not occur at any zoom level when I disable Canvas Graphics Acceleration in Settings -> Configure Krita -> Display. However, if I enable Canvas Graphics Acceleration at all, regardless of OpenGL or Direct3D 11 via ANGLE, regardless of scaling mode, and regardless of if texture buffer is enabled, this bug continues to occur. Thank you for your patience. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 392283] Kstars: git://anongit.kde.org/kstars.git
https://bugs.kde.org/show_bug.cgi?id=392283 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jasem Mutlaq --- Please check if it works now. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398925] Reporting bugs in KStars
https://bugs.kde.org/show_bug.cgi?id=398925 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 402012] kstars crash when updated orbital elements for comet
https://bugs.kde.org/show_bug.cgi?id=402012 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jasem Mutlaq --- Cannot reproduce. Can you retrigger it again? If yes, how? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 402043] Local horizon display broken in RA mode
https://bugs.kde.org/show_bug.cgi?id=402043 --- Comment #1 from Jasem Mutlaq --- Can you attach your userdb.sqlite file? or export the horizon data from it? I want to reproduce it here and work on it. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 402043] Local horizon display broken in RA mode
https://bugs.kde.org/show_bug.cgi?id=402043 --- Comment #2 from Jasem Mutlaq --- The file is located under ~/.local/share/kstars -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 400912] QWidget forward declaration errors
https://bugs.kde.org/show_bug.cgi?id=400912 Jasem Mutlaq changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Jasem Mutlaq --- Fixed in GIT. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 401935] Cooling of ASI stops 1.5C before target temp (ZWO ASI1600MM Pro)
https://bugs.kde.org/show_bug.cgi?id=401935 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from Jasem Mutlaq --- Cannot reproduce it with ASI. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 402227] Kstars does not remember last search
https://bugs.kde.org/show_bug.cgi?id=402227 Jasem Mutlaq changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||3.0.0 --- Comment #1 from Jasem Mutlaq --- Fixed in 3.0.0 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 402401] New: Falkon fails to build with Qt 5.12 and current Framworks
https://bugs.kde.org/show_bug.cgi?id=402401
Bug ID: 402401
Summary: Falkon fails to build with Qt 5.12 and current
Framworks
Product: Falkon
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: bluescreenaven...@gmail.com
Target Milestone: ---
Trying to build Falkon, I get this error:
[ 89%] Building CXX object
autotests/CMakeFiles/adblocktest.dir/qrc_autotests.cpp.o
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.cpp:
In constructor
‘KDEFrameworksIntegrationPlugin::KDEFrameworksIntegrationPlugin()’:
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.cpp:43:45:
error: no matching function for call to
‘Purpose::Menu::Menu(KDEFrameworksIntegrationPlugin*)’
, m_sharePageMenu(new Purpose::Menu(this))
^
In file included from /opt/include/KF5/purposewidgets/PurposeWidgets/Menu:1,
from
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.h:22,
from
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.cpp:18:
/opt/include/KF5/purposewidgets/purposewidgets/menu.h:35:14: note: candidate:
‘Purpose::Menu::Menu(QWidget*)’
explicit Menu(QWidget* parent = nullptr);
^~~~
/opt/include/KF5/purposewidgets/purposewidgets/menu.h:35:14: note: no known
conversion for argument 1 from ‘KDEFrameworksIntegrationPlugin*’ to ‘QWidget*’
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.cpp:
In member function ‘virtual void
KDEFrameworksIntegrationPlugin::populateWebViewMenu(QMenu*, WebView*, const
WebHitTestResult&)’:
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.cpp:104:57:
error: no matching function for call to ‘QJsonValue::QJsonValue(QUrl)’
{ QStringLiteral("urls"), QJsonValue(view->url()) },
^
In file included from /opt/include/QtCore/qjsonobject.h:43,
from /opt/include/QtCore/qplugin.h:45,
from /opt/include/QtCore/QtPlugin:1,
from /srcbuild/falkon/src/lib/plugins/plugininterface.h:21,
from
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.h:20,
from
/srcbuild/falkon/src/plugins/KDEFrameworksIntegration/kdeframeworksintegrationplugin.cpp:18:
/opt/include/QtCore/qjsonvalue.h:156:5: note: candidate:
‘QJsonValue::QJsonValue(QJsonPrivate::Data*, QJsonPrivate::Base*, const
QJsonPrivate::Value&)’
QJsonValue(QJsonPrivate::Data *d, QJsonPrivate::Base *b, const
QJsonPrivate::Value& v);
^~
Let me know if more info is needed?
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 401761] KBibTex changes LaTeX accents
https://bugs.kde.org/show_bug.cgi?id=401761 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401113] When you try to install Skype, the installation does not occur. Writes a message to disable the lock Snap.
https://bugs.kde.org/show_bug.cgi?id=401113 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400850] window manager crash after open a New Project in Netabeans 9.0
https://bugs.kde.org/show_bug.cgi?id=400850 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 332191] Kget crash after server authenticate cancel
https://bugs.kde.org/show_bug.cgi?id=332191 --- Comment #16 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 256605] KSMServer crashes everytime on shutdown or restart [~QRasterWindowSurface, ~QWidgetBackingStore, ..., KSelectionOwner::Private::~Private, KSelectionOwner::~KSelectionOwner]
https://bugs.kde.org/show_bug.cgi?id=256605 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 386926] notifications appearing all over the screen in Plasma with Wayland
https://bugs.kde.org/show_bug.cgi?id=386926 Christoph Feck changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Christoph Feck --- Is this still an issue with recent versions? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 386366] Add webcam wallpaper plugin
https://bugs.kde.org/show_bug.cgi?id=386366 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- Vallpaper can do this. https://www.opendesktop.org/p/1197828/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402400] Plasma crash (recovered) on startup
https://bugs.kde.org/show_bug.cgi?id=402400 --- Comment #1 from Szczepan Hołyszewski --- Didn't happen again after reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402400] New: Plasma crash (recovered) on startup
https://bugs.kde.org/show_bug.cgi?id=402400 Bug ID: 402400 Summary: Plasma crash (recovered) on startup Product: plasmashell Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rula...@wp.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.4) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.9-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Fired up my box. Right after I logged in, but before I did anything else other than reflexively launching Firefox, I saw the sad face icon in the system tray and proceeded to report this crash. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f58db4575c0 (LWP 8358))] Thread 9 (Thread 0x7f58a4823700 (LWP 8896)): #0 0x7f58d8c05afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f58d9d3cadc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f58d9d3cbca in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f58dbabd4cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f58dbabd73c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f58d9d369cc in () at /usr/lib/libQt5Core.so.5 #6 0x7f58d8bffa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f58d9a1bb23 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f58a7fff700 (LWP 8881)): #0 0x7f58d8c05afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f58d9d3cadc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f58d9d3cbca in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f58dbabd4cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f58dbabd73c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f58d9d369cc in () at /usr/lib/libQt5Core.so.5 #6 0x7f58d8bffa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f58d9a1bb23 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f58aede7700 (LWP 8841)): #0 0x7f58d8c05afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f58d9d3cadc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f58d9d3cbca in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f58dbabd4cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f58dbabd73c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f58d9d369cc in () at /usr/lib/libQt5Core.so.5 #6 0x7f58d8bffa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f58d9a1bb23 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f58bccdf700 (LWP 8742)): #0 0x7f58d9a10c21 in poll () at /usr/lib/libc.so.6 #1 0x7f58d7c9cee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f58d7c9cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f58d9f485c4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f58d9ef158c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f58d9d355c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f58b5e6935a in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f58d9d369cc in () at /usr/lib/libQt5Core.so.5 #8 0x7f58d8bffa9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f58d9a1bb23 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f58bd577700 (LWP 8630)): #0 0x7f58d7c4b414 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f58d7c9c79d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f58d7c9ce06 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f58d7c9cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f58d9f485c4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f58d9ef158c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f58d9d355c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f58dba35e5b in () at /usr/lib/libQt5Quick.so.5 #8 0x7f58d9d369cc in () at /usr/lib/libQt5Core.so.5 #9 0x7f58d8bffa9d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f58d9a1bb23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f58cb5ef700 (LWP 8566)): #0 0x7f58d9a10c21 in poll () at /usr/lib/libc.so.6 #1 0x7f58d7c9cee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f58d7c9cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f58d9f485c4 in
[Plasma Workspace Wallpapers] [Bug 346251] Default wallpaper cannot be found in desktop settings
https://bugs.kde.org/show_bug.cgi?id=346251 Christoph Feck changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Christoph Feck --- No response, and works for me. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 378823] EPOD POTD display header image instead of the real photo
https://bugs.kde.org/show_bug.cgi?id=378823 Christoph Feck changed: What|Removed |Added Component|general |Picture of the Day Product|Plasma Workspace Wallpapers |kdeplasma-addons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen
https://bugs.kde.org/show_bug.cgi?id=402392 S. Christian Collins changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from S. Christian Collins --- (In reply to David Edmundson from comment #2) > We need to find out which of those two modes we're in before progressing. > > Super lazy quick test is > > "killall xembedsniproxy" if the icon moves, it was using xembed. If it > stays, it was using the SNI. The icon doesn't move or change in any way with "killall xembedsniproxy". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kapidox] [Bug 372627] Qt Assistant rendering glitch
https://bugs.kde.org/show_bug.cgi?id=372627 --- Comment #3 from Christoph Feck --- Is the output of kapidox in HTML format also for usage in Assistant? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kjs] [Bug 401955] exported CompileState.h includes non exported opcodes.h and bytecodes/opcodes.h
https://bugs.kde.org/show_bug.cgi?id=401955 --- Comment #1 from Christoph Feck --- Does CompileState.h actually have exported API? My understanding is that it is internal, and only kjs/api is exported. -- You are receiving this mail because: You are watching all bug changes.
[kwrited] [Bug 386067] Use seperate notifications for each message
https://bugs.kde.org/show_bug.cgi?id=386067 --- Comment #1 from Christoph Feck --- Are messages separated by some fixed text? Otherwise I doubt it is fixable. -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 401699] Lỗi tính năng update hình: Không upload được profile picture trong Business Profile.
https://bugs.kde.org/show_bug.cgi?id=401699 Christoph Feck changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- Please ask for help in a forum. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-modemmanager-qt] [Bug 349478] Qualcomm 4G modem not recognised - Works under Gnome
https://bugs.kde.org/show_bug.cgi?id=349478 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #26 from Christoph Feck --- Paul, were you able to test with newer kernel? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdnssd] [Bug 349303] Compilation errors with MinGW
https://bugs.kde.org/show_bug.cgi?id=349303 --- Comment #2 from Christoph Feck --- According to our CI, kdnssd builds fine with MSVC, see https://build.kde.org/job/Frameworks/job/kdnssd/ Is this still an issue with MinGW? -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 402398] Juk playlist mis-sorts Collection List, History, and Play Queue with playlist entries after KF5
https://bugs.kde.org/show_bug.cgi?id=402398 Michael changed: What|Removed |Added CC||kde@callthecomputerdoctor.c ||om -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 --- Comment #5 from Filip F. --- (In reply to David Edmundson from comment #1) > Which plasma theme? Yes, we're not sure if it's theme specific. In the screenshot I uploaded the theme was Arc-Color (part of the "Arc KDE" package). With that theme I (rarely) also got a cut off wi-fi notification when I logged in: https://i.ibb.co/FbvGZ0Q/Whats-App-Image-2018-12-21-at-01-57-13.jpg I've also dug up Rooty's screenshots with his Breath (or maybe Breeze AlphaBlack, he's not sure) theme: https://i.ibb.co/7KqTTMD/Whats-App-Image-2018-12-07-at-16-48-34.jpg https://i.ibb.co/MDtL4hH/Whats-App-Image-2018-12-07-at-03-03-26.jpg I'm going to test with stock Breeze to see if it occurs with it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 402174] System settings crash upon clicking application style
https://bugs.kde.org/show_bug.cgi?id=402174 --- Comment #3 from Alexander M. --- In my case, I found out that the issues were caused by a rogue /etc/gtk-2.0/gtkrc link pointing to ~/.gtkrc, which includes /etc/gtk-2.0/gtkrc, which means it ended up including itself again and again in an infinite loop, which is what caused the crash. I'm 100% certain I've never created that link, so it's probably the result of some change between Plasma 5.12 and 5.13 (either upstream or downstream, by the Arch maintainers). In any case, deleting that link fixes the problem. Don't know if this is relevant to this bug after all, though. At the very least, since everything else works properly and I'm on an Arch system similar to the OP's, I can confirm that the issue is *NOT* "reproducible with all packages updated from consistent repositories". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 402258] fatal error "could not create collection outbox, resourceId: 7"
https://bugs.kde.org/show_bug.cgi?id=402258 Zion Nimchuk changed: What|Removed |Added CC||zionnimc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 --- Comment #4 from Rooty --- (In reply to Rooty from comment #3) > P.S. Just to clarity I don't get it just when I'm skipping tracks, it's just > the only surefire way of reproducing it that I know of (and even with all > the skipping, it takes a long time for it to show up). But it happens with > all kinds of other notifications too. clarify* Oh, and this happens with the built-in notification widget and with custom ones from the KDE store -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 401339] presentation: odd scaling/anti aliasing
https://bugs.kde.org/show_bug.cgi?id=401339 Dave Gilbert changed: What|Removed |Added CC||gilbertd+...@treblig.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 --- Comment #3 from Rooty --- P.S. Just to clarity I don't get it just when I'm skipping tracks, it's just the only surefire way of reproducing it that I know of (and even with all the skipping, it takes a long time for it to show up). But it happens with all kinds of other notifications too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #2 from Rooty --- I get the same problem when I open up Spotify or some other media player and switch tracks really fast, it eventually shows up. And I get it regardless of the theme I'm using (mostly Breath though, by Manjaro) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Which plasma theme? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] New: Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 Bug ID: 402399 Summary: Notification placement is wrong sometimes Product: plasmashell Version: 5.14.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 117037 --> https://bugs.kde.org/attachment.cgi?id=117037=edit Bad notification placement SUMMARY Notifications are sometimes spawned in the wrong position, resulting in a) a portion of the notification being cut off and b) an empty blurred region STEPS TO REPRODUCE No clear-cut way to reproduce it that I know of, my apologies, it seems to happen randomly from time to time. OBSERVED RESULT Wrong notification position. EXPECTED RESULT Proper notification position. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Visual proof is attached. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 401339] presentation: odd scaling/anti aliasing
https://bugs.kde.org/show_bug.cgi?id=401339 --- Comment #8 from Dr. David Alan Gilbert (rh) --- I built with debug and think I've tracked the problem down to the use of the tilemanager; and I think it's interacting with images rendered for previews/thumnails, so that it's using those small images. I noticed that document.cpp DocumentPrivate::snedGeneratorPixmapRequest has a 8MPixel limit and says: 'If the requested area is above 800 pixels, switch on the tile manager' well, uHD is 3840x2160=8294400 pixels - so that triggers. If I bodge that limit to 10M my problem goes away. So then I added a debug just under the 'fill the tiles manager with the last pixmap' around line 1342 after the 'if (pixmap)' and I see: org.kde.okular.core: Start using tiles on page 11 (3745x2160 px); org.kde.okular.core: tilesManager existing pixmap width=474 height=273 that 474x273 is the size of the preview shown in the main okular window in 'Overview' mode (and I'm running 9 slides visible). So you *might* not notice this if you were running full-page in your non-presentation window; however even then I managed to trigger it non-repeatably; and I think what's happening in that case is that if in the main window I have: a) Full size previews on my HD monitor (with menus/thumbnails/borders a bit less than 1920x1080) - OK they look a bit fuzzy when scaled to uHD but many might not notice or complain b) If you get unlucky you've not looked at the page in the preview, but you DO* have the thumbnail from the thumbnail side bar, and that's abysmal resolution; but it's the last one you've got so you scale it up. so I think the if (pixmap) test for reusing an existing pixmap needs to be smarter somehow; maybe it only uses the existing pixmap if the pixmap size actually fully matches? Or maybe you have to give it some slack for cases where the scaling has to round? e.g. if you weren't running previews then p -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396830] kwin_x11 crash when suspending compositing
https://bugs.kde.org/show_bug.cgi?id=396830 Vlad Zagorodniy changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/9ac2e5d5bb44934b6d30bda93 ||15210d544f33958 Version Fixed In||5.15.0 Status|CONFIRMED |RESOLVED --- Comment #20 from Vlad Zagorodniy --- Git commit 9ac2e5d5bb44934b6d30bda9315210d544f33958 by Vlad Zagorodniy. Committed on 21/12/2018 at 00:22. Pushed by vladz into branch 'master'. [effects] Make current OpenGL context per each unloaded effect Summary: Some effects may release the current context when they tear down, so we have to make the current context per each unloaded effect. FIXED-IN: 5.15.0 Test Plan: No longer able to reproduce bug 396830. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17716 M +36 -32 effects.cpp M +2-0effects.h https://commits.kde.org/kwin/9ac2e5d5bb44934b6d30bda9315210d544f33958 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377840] [Wayland] Shows windows from all activities and desktops, doesn't respect settings that should disable this functionality
https://bugs.kde.org/show_bug.cgi?id=377840 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kimagemapeditor] [Bug 144151] kimagemapeditor ftp support only "file not exists"
https://bugs.kde.org/show_bug.cgi?id=144151 Christoph Feck changed: What|Removed |Added CC||yurc...@ukr.net --- Comment #1 from Christoph Feck --- This might have been fixed with the KF5 port. If someone can re-test this, just add a comment. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 359747] Clipboard sharing not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=359747 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpeople] [Bug 372463] Plasma crash
https://bugs.kde.org/show_bug.cgi?id=372463 Christoph Feck changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Christoph Feck --- Comment #1 is an unrelated crash in NVIDIA driver. Comment #2 is an unrelated crash in Qt's QML engine. Bug from original reporter was fixed with https://commits.kde.org/kpeople/ea6fc3cb3b95548ea8a9ca89fc8b61dd80f9fd87 -- You are receiving this mail because: You are watching all bug changes.
[kubrick] [Bug 382701] No visible mouse hover highlight for on toolbar and menu on wayland
https://bugs.kde.org/show_bug.cgi?id=382701 --- Comment #1 from Christoph Feck --- Is this still reproducible with recent versions? Qt's wayland support improved with Qt 5.12. -- You are receiving this mail because: You are watching all bug changes.
[kalarmcal] [Bug 401526] kalarmcal-18.08.1 fails test kadatetimetest when run inside Plasma session
https://bugs.kde.org/show_bug.cgi?id=401526 --- Comment #1 from Christoph Feck --- Looks like the tests need to set LANG=C. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396689] Tab text color (for monitoring highlight?) does not reset
https://bugs.kde.org/show_bug.cgi?id=396689 let...@gmail.com changed: What|Removed |Added CC||let...@gmail.com --- Comment #3 from let...@gmail.com --- *** Bug 402394 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402394] Konsole tabs don't change color on program completion
https://bugs.kde.org/show_bug.cgi?id=402394 let...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from let...@gmail.com --- *** This bug has been marked as a duplicate of bug 396689 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402394] Konsole tabs don't change color on program completion
https://bugs.kde.org/show_bug.cgi?id=402394 --- Comment #2 from let...@gmail.com --- Probably... I made a test and opened a new tab where i entered the sleep command. The tab does indeed change it's color. However it doesn't change it back how it's supposed to. I was under the impression that the tab color in konsole doesn't ever change any more... -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 383614] Wrong task manager icon when multiple KCMs opened on Wayland
https://bugs.kde.org/show_bug.cgi?id=383614 David Edmundson changed: What|Removed |Added Keywords||wayland CC||k...@davidedmundson.co.uk --- Comment #5 from David Edmundson --- >I'm not sure whether it's allowed to change the app id In Xdg-shell it is not explicitly forbidden. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 397362] kcmshell doesn't close when CTRL+Q pressed
https://bugs.kde.org/show_bug.cgi?id=397362 David Edmundson changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 397362] kcmshell doesn't close when CTRL+Q pressed
https://bugs.kde.org/show_bug.cgi?id=397362 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifyconfig] [Bug 393153] Knotify does not show the text to speech option
https://bugs.kde.org/show_bug.cgi?id=393153 Christoph Feck changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Christoph Feck --- Could you please ask developers of your distribution if they build the knotifyconfig framework against the Qt5TextToSpeech dependency? -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 402398] New: Juk playlist mis-sorts Collection List, History, and Play Queue with playlist entries after KF5
https://bugs.kde.org/show_bug.cgi?id=402398 Bug ID: 402398 Summary: Juk playlist mis-sorts Collection List, History, and Play Queue with playlist entries after KF5 Product: juk Version: 18.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: lulosals...@gmail.com CC: mp...@kde.org Target Milestone: --- Created attachment 117036 --> https://bugs.kde.org/attachment.cgi?id=117036=edit Example of Juk mis-sorting special icon names in playlist SUMMARY Since the port of Juk to KF5, the playlist column has a regression with the way the "special icons" are sorted. The "special icons" are the "Collection List" icon, the "History" icon, and the "Play Queue" icon. These have special functions. The special icons used to be grouped at the top of the playlist view column, above all playlists, but now they are sorted alphabetically with the rest of the playlists. This is a problem if there are many playlists, as I have when I DJ. I used to be able to find the special icon right away, as they were right at the top, now I have to scroll and look for them, which is troublesome when I'm DJ'ing and I need to be fast, and this used to be the old functionality that brought me to Juk. See the attached screenshot to see our case where the special icons are buried in the playlist names. STEPS TO REPRODUCE 1. Make several mock playlists. Give each playlist a different name, like "B", "J", "Q". These names are designed so that you can see how all are sorting. 2. Look at the left hand side of the window, which is the Playlist area. You will see all the playlists and special icons sorting like this: B Collection List History J Play Queue Q OBSERVED RESULT You can see that the special icons are sorting in *in between* the playlist names. EXPECTED RESULT We should see the special icons *grouped together* at the top, the way it used to be before Juk was transitioned to KF5. Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.4 Qt Version: 5.11.2 KDE Frameworks Version: 5.53.0 Kernel Version: 4.15.0-43-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.6 GiB of RAM Thank you for time and your efforts, very much appreciated! -- You are receiving this mail because: You are watching all bug changes.
[kbackup] [Bug 396279] Support for compressing the whole target tarball once instead of each source file individually
https://bugs.kde.org/show_bug.cgi?id=396279 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Christoph Feck --- This would mean that whenever you need to restore a file from the backup, you would have to decompress the complete backup. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402361] Large search and replace operations cause Kate/KWrite to hang for long time
https://bugs.kde.org/show_bug.cgi?id=402361 --- Comment #3 from NiO --- (In reply to Kåre Särs from comment #1) > Hi, > > You are probably referring to the built-in search. > > This is a known issue for files with long lines in Kate/KWrite. > > There is now ongoing work to split the replacing into chunks so that it will > be possible to cancel the replace if it takes too long. > > A similar effort is also being done for the Search & Replace plugin. I'm > actually testing the S change at the moment. > > > Hopefully this will be a bit improved for Kate 19.04 Great to hear, thank you. I guess Christoph's dupe confirms this has been an issue for quite a while. I did search beforehand but didn't notice any similar reports. Apologies for the duplicate! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402397] New: Okular crashes while trying to re-open already deleted document at startup
https://bugs.kde.org/show_bug.cgi?id=402397 Bug ID: 402397 Summary: Okular crashes while trying to re-open already deleted document at startup Product: okular Version: 1.5.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: matth...@heizmann.name Target Milestone: --- Application: okular (1.5.3) (Compiled from sources) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.15.15-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: At startup the desktop environment tries to re-open all documents that were opened when I logged out from the desktop environent (good). This includes pdfs that firefox downloaded and saved to /tmp. However after a reboot these documents are gone (good). Now Okular should show an error that the document does not exist, instead Okular crashes with a segfault (bad) The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa9eb310280 (LWP 4725))] Thread 3 (Thread 0x7fa9c35f0700 (LWP 4732)): #0 0x7fa9e435057c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa9c3d97f0b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7fa9c3d97c37 in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7fa9e434996a in start_thread () from /lib64/libpthread.so.0 #4 0x7fa9e70e31af in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fa9ce981700 (LWP 4730)): #0 0x7fa9e70d2cd0 in read () from /lib64/libc.so.6 #1 0x7fa9e2064440 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa9e201fa37 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa9e201fef0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7fa9e202005c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fa9e7a3aaeb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fa9e79e6a4a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fa9e7848bda in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fa9e7e73de5 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #9 0x7fa9e785263f in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7fa9e434996a in start_thread () from /lib64/libpthread.so.0 #11 0x7fa9e70e31af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fa9eb310280 (LWP 4725)): [KCrash Handler] #6 0x7fa9e7854626 in qstrcmp(QByteArray const&, QByteArray const&) () from /usr/lib64/libQt5Core.so.5 #7 0x7fa9e95269ed in QMapData::findNode(KEntryKey const&) const () from /usr/lib64/libKF5ConfigCore.so.5 #8 0x7fa9e952bcab in KEntryMap::findEntry(QByteArray const&, QByteArray const&, QFlags) const () from /usr/lib64/libKF5ConfigCore.so.5 #9 0x7fa9e95202f7 in KConfigPrivate::lookupData(QByteArray const&, char const*, QFlags) const () from /usr/lib64/libKF5ConfigCore.so.5 #10 0x7fa9e95357dc in KConfigGroup::readEntry(char const*, QVariant const&) const () from /usr/lib64/libKF5ConfigCore.so.5 #11 0x55783ab42de3 in Shell::readProperties(KConfigGroup const&) () #12 0x7fa9ea4aca48 in KMainWindow::readPropertiesInternal(KConfig*, int) () from /usr/lib64/libKF5XmlGui.so.5 #13 0x7fa9ea4aca92 in KMainWindow::restore(int, bool) () from /usr/lib64/libKF5XmlGui.so.5 #14 0x55783ab3e0db in void kRestoreMainWindows() () #15 0x55783ab3b822 in main () Possible duplicates by query: bug 395539. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401376] Unnecessary confirmation for reloading
https://bugs.kde.org/show_bug.cgi?id=401376 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kte ||xteditor/82a1673746eacfe456 ||2b801c5cc45b7c3c0ee233 --- Comment #5 from Nicolas Fella --- Git commit 82a1673746eacfe4562b801c5cc45b7c3c0ee233 by Nicolas Fella. Committed on 20/12/2018 at 22:47. Pushed by nicolasfella into branch 'master'. Don't ask for confimation when reloading Summary: When reloading the document it is unnecessary to show the document modified dialog that offers to reload since that is what the user expects. Test Plan: Modify document externally, relaod via F5 -> no confirmation dialog Reviewers: #kate, ngraham, cullmann Reviewed By: #kate, cullmann Subscribers: cullmann, kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D17178 M +0-23 src/document/katedocument.cpp https://commits.kde.org/ktexteditor/82a1673746eacfe4562b801c5cc45b7c3c0ee233 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402396] New: Throwing exceptions from an event handler is not supported in Qt
https://bugs.kde.org/show_bug.cgi?id=402396 Bug ID: 402396 Summary: Throwing exceptions from an event handler is not supported in Qt Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jer...@acjlaw.net Target Milestone: --- Output from akonadictl started in konsole: org.kde.pim.akonadiserver: Received ModifySubscription command before RegisterSubscriber org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-jeremy.9k9RMP/akonadiserver-ntf.socket" Fontconfig error: Cannot scan config file "infinality/conf.d" ProtocolException thrown:Failed to write data to stream Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must not let any exception whatsoever propagate through Qt code. If that is not possible, in Qt 5 you must at least reimplement QCoreApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'Akonadi::ProtocolException' what(): Failed to write data to stream org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_akonotes_resource" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_akonotes_resource' crashed! 1 restarts left Linux/KDE Plasma: 4.9.76-gentoo-r1 / 18.08.2 (available in About System) KDE Plasma Version: 15.13.5 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 333077] Dolphin sais: Unable to request the SFTP subsystem. Make sure SFTP is enabled on the server.
https://bugs.kde.org/show_bug.cgi?id=333077 --- Comment #9 from adr.fant...@gmail.com --- This works if using openssh 7.9p1-1 instead of openssh-hpn-git 7.5.P1.r74.ga0c37a72-2 on the server -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396965] Falkon forces Ads
https://bugs.kde.org/show_bug.cgi?id=396965 --- Comment #4 from dS810 --- (In reply to KDErobo3me from comment #2) > why use adblock if you have pihole already? > > there are various blockers who do not harmonize, such as uBlock fights > Ghostery. > > I guess one has to settle for a single one. I use PiHole for my whole network. AdBlock is useful in hotels and public access points like train, bar etc.. Currently I have to switch on/off adblock in falcon. If I use chromium + uBlock so it works as expected and I haven't to desable it in my "PiHole" network. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401399] autostart a script from /.config/plasma-workspace/env won't work
https://bugs.kde.org/show_bug.cgi?id=401399 --- Comment #5 from David Edmundson --- Git commit fb1570f4804d289d4f7dc8adf367ac9c89d79f38 by David Edmundson. Committed on 20/12/2018 at 22:26. Pushed by davidedmundson into branch 'master'. Remove outdated note about autostart not working Summary: Just tested, worked fine. That line has been there since 5.0 days, I do vaguely recall fixing this at some point. Reviewers: #plasma Subscribers: plasma-devel, kde-doc-english Tags: #plasma, #documentation Differential Revision: https://phabricator.kde.org/D17709 M +1-3doc/kcontrol/autostart/index.docbook https://commits.kde.org/plasma-desktop/fb1570f4804d289d4f7dc8adf367ac9c89d79f38 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 333077] Dolphin sais: Unable to request the SFTP subsystem. Make sure SFTP is enabled on the server.
https://bugs.kde.org/show_bug.cgi?id=333077 adr.fant...@gmail.com changed: What|Removed |Added CC||adr.fant...@gmail.com Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #8 from adr.fant...@gmail.com --- I can confirm this happening for me too, also from Arch. dolphin 18.12.0-1 libssh 0.8.5-1 (both client and server) libssh2 1.8.0-3 (both client and server) openssh-hpn-git 7.5.P1.r74.ga0c37a72-2 (server) /etc/ssh/sshd_config https://pastebin.com/F0JzfnBQ SSH (fish://) works, sftp does not (both with the main user and the sftp chroot user called readonly). I have tried following https://techbase.kde.org/Development/Tutorials/Debugging/Debugging_IOSlaves/Debugging_kio_sftp#Logging but I get no output, even after running kdeinit5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen
https://bugs.kde.org/show_bug.cgi?id=402392 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- We need to find out which of those two modes we're in before progressing. Super lazy quick test is "killall xembedsniproxy" if the icon moves, it was using xembed. If it stays, it was using the SNI. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401399] autostart a script from /.config/plasma-workspace/env won't work
https://bugs.kde.org/show_bug.cgi?id=401399 --- Comment #4 from David Edmundson --- NP. Thanks for reporting back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402387] Let's talk about Plasma usability on the plain old PC desktop
https://bugs.kde.org/show_bug.cgi?id=402387 --- Comment #8 from David Edmundson --- >I knew this bug report will be completely disregarded I spent quite a while of my time clearly reading, and wrote a reply. That is not completely disregarding anything. >KDE developers don't want any input in regard to the usability of KDE because >you know better. That's not what was said. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402395] New: coregrind/vgdb-invoker-solaris.c: 2 * poor error checking ?
https://bugs.kde.org/show_bug.cgi?id=402395
Bug ID: 402395
Summary: coregrind/vgdb-invoker-solaris.c: 2 * poor error
checking ?
Product: valgrind
Version: 3.15 SVN
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: dcb...@hotmail.com
Target Milestone: ---
SUMMARY
1.
[valgrind/coregrind/vgdb-invoker-solaris.c:177]: (style) Checking if unsigned
variable 'bytes' is less than zero.
bytes = read(status_fd, , sizeof(pstatus));
if ((bytes < 0) || (bytes != sizeof(pstatus))) {
but
size_t bytes = sizeof(ctl.cmd) + sizeof(ctl.arg.flags);
The return type of read is ssize_t, not size_t, isn't it ?
2.
[valgrind/coregrind/vgdb-invoker-solaris.c:404]: (style) Checking if unsigned
variable 'bytes' is less than zero.
Duplicate.
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
MacOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7
https://bugs.kde.org/show_bug.cgi?id=386945
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #69 from Mark Wielaard ---
I believe this bug is finally resolved with the push of the following 7 commits
to master:
commit 3af8e12b0d49dc87cd26258131ebd60c9b587c74
Author: Julian Seward
Date: Wed Dec 12 13:55:01 2018 +0100
Fix memcheck/tests/undef_malloc_args failure.
Try harder to trigger a memcheck error if a value is (partially) undefined.
commit 01f1936b1238a3bbeaf2821b61ecb36ba0ae15b1
Author: Julian Seward
Date: Mon Dec 10 17:18:20 2018 +0100
Adjust ppc set_AV_CR6 computation to help Memcheck instrumentation.
* changes set_AV_CR6 so that it does scalar comparisons against zero,
rather than sometimes against an all-ones word. This is something
that Memcheck can instrument exactly.
* in Memcheck, requests expensive instrumentation of Iop_Cmp{EQ,NE}64
by default on ppc64le.
https://bugs.kde.org/show_bug.cgi?id=386945#c62
commit 3ef4b2c780ea76a80ae5beaa63c1cb1d6530988b
Author: Mark Wielaard
Date: Sun Dec 9 23:25:05 2018 +0100
Implement ppc64 lxvb16x as 128-bit vector load with reversed double words.
This makes it possible for memcheck to know which part of the 128bit
vector is defined, even if the load is partly beyond an addressable block.
Partially resolves bug 386945.
commit 8d12697b157bb50ad98467b565b3a7a39097bf31
Author: Mark Wielaard
Date: Sun Dec 9 14:26:39 2018 +0100
memcheck: Allow unaligned loads of 128bit vectors on ppc64[le].
On powerpc partial unaligned loads of vectors from partially invalid
addresses are OK and could be generated by our translation of lxvd2x.
Adjust partial_load memcheck tests to allow partial loads of 16 byte
vectors on powerpc64.
Part of resolving bug #386945.
commit 98a73de1c0c83918a63e736b62d428bc2f98c943
Author: Mark Wielaard
Date: Sun Dec 9 00:55:42 2018 +0100
Implement ppc64 lxvd2x as 128-bit load with double word swap for ppc64le.
This makes it possible for memcheck to know which part of the 128bit
vector is defined, even if the load is partly beyond an addressable block.
Partially resolves bug 386945.
commit 5ecdecdcd3efecadf149dcd6276140e833b7f8e6
Author: Mark Wielaard
Date: Sat Dec 8 13:47:43 2018 -0500
memcheck: Allow unaligned loads of words on ppc64[le].
On powerpc partial unaligned loads of words from partially invalid
addresses are OK and could be generated by our translation of ldbrx.
Adjust partial_load memcheck tests to allow partial loads of words
on powerpc64.
Part of resolving bug #386945.
commit 0ed17bc9f675c59cf1e93caa4290e0b21b84c0a0
Author: Mark Wielaard
Date: Fri Dec 7 10:42:22 2018 -0500
Implement ppc64 ldbrx as 64-bit load and Iop_Reverse8sIn64_x1.
This makes it possible for memcheck to analyse the new gcc strcmp
inlined code correctly even if the ldbrx load is partly beyond an
addressable block.
Partially resolves bug 386945.
Thanks to everybody for testing and feedback.
Note that you still need the latest gcc-8-branch (and rebuild at least glibc
with it) on ppc64[le] to have a setup that valgrind memcheck fully understands.
--
You are receiving this mail because:
You are watching all bug changes.
[kget] [Bug 400367] Cannot launch Kget via apps launcher. It launches via terminal.
https://bugs.kde.org/show_bug.cgi?id=400367 --- Comment #10 from Wolfgang Bauer --- (In reply to Patrick Silva from comment #8) > yes, to remove %i in the desktop file solves the problem. Thanks for the confirmation. I pushed a fix. PS: you probably should close your kmail bug report if it is working now... ;-) -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 400367] Cannot launch Kget via apps launcher. It launches via terminal.
https://bugs.kde.org/show_bug.cgi?id=400367 Wolfgang Bauer changed: What|Removed |Added Version Fixed In||18.12.1 Latest Commit||https://commits.kde.org/kge ||t/80adf24c1091115e2fa483965 ||0a5708b2d4672c8 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Wolfgang Bauer --- Git commit 80adf24c1091115e2fa4839650a5708b2d4672c8 by Wolfgang Bauer. Committed on 20/12/2018 at 21:29. Pushed by wbauer into branch 'Applications/18.12'. Set window icon in code instead of in the desktop file %i is expanded to "--icon xxx", but Qt only supports that option on xcb, not Wayland. Therefore kget couldn't be started from the application launcher/menu on Wayland. See https://community.kde.org/Guidelines_and_HOWTOs/Wayland_Porting_Notes#Application_Icon . Instead, use QApplication::setWindowIcon() to set the window icon (necessary to have a window icon on other desktops than Plasma). This also has the advantage that the proper window icon is set when running kget from a shell (and not passing the --icon or -qwindowicon options). FIXED-IN: 18.12.1 M +1-1desktop/org.kde.kget.desktop.cmake M +1-0main.cpp https://commits.kde.org/kget/80adf24c1091115e2fa4839650a5708b2d4672c8 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402394] Konsole tabs don't change color on program completion
https://bugs.kde.org/show_bug.cgi?id=402394 --- Comment #1 from Christoph Feck --- I guess what you are seeing is the reverse: Tabs change color once, but never reset back when activated. See bug 396689. Correct? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402394] New: Konsole tabs don't change color on program completion
https://bugs.kde.org/show_bug.cgi?id=402394 Bug ID: 402394 Summary: Konsole tabs don't change color on program completion Product: konsole Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: let...@gmail.com Target Milestone: --- Created attachment 117035 --> https://bugs.kde.org/attachment.cgi?id=117035=edit update since the bug started Since the last upgrade, the Konsole tab bar doesn't show "highlighted" text correctly. In the past it used to change the color of the text if something changed in a tab. After this upgrade the text remains of the color that it starts with. This happens on Arch Linux since 11 December, when I upgraded multiple dependencies of console. The log of the upgrade is attached. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402369] Overhaul DHAT
https://bugs.kde.org/show_bug.cgi?id=402369 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #3 from Philippe Waroquiers --- No comment about the tool itself, just a suggestion for the implementation. As I understand, dhat has 2 data structures: * an interval tree, to find for an address a what block is covering it * a wordFM of an Execontext, together with some data associated with this execontext. It looks to me that the second data structure could be done by using pub_tool_xtree.h, which is a generalised way to associate data to an execontext, and print it in (currently) 2 output formats : massif format, kcachegrind format. It might be interesting to replace the wordFM by an xtree, and add the json output format to pub_tool_xtree.h (I suspect that an xtree might be somewhat faster than an wordFM). Massif speed was improved a lot when switching it to an xtree. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #86 from Rafael Linux User --- I agree with Mathieu Roy and Jean-Francois Juneau comments, even last talking about contributing with donations. I'm sure none of us try to understimate any developers work, but the reality is that in my case, after more of eight years using Linux and KDE, I can't recommend to any on my job to migrate to KDE precisely cause every day we need to do our job, not fighting with issues (caused from Plasma or not) accessing FTP or SMB files in an heterogenous way. I access each day to FTP and SMB local services, but each day I must take into account that it's not the same if I open a remote file from Krusader (or Dolphin) that from Caja, or if I compare remote files with Meld or with Kompare or KDiff, or if I open a remote file with Kate or with Atom ... it's really a headache for a simple user that want to work transparently from Linux systems. As other users said, it's 2018, and I can see KDE desktop changed his name a lot of time ago to Plasma, and each new version of Plasma I expected to see this issue solved, but at this point I can't recommend anyone to jump Linux if they really want to work with files outside their PCs. In fact, is not the unique issue that is not solved and even not recognized, despite it's easy to verify they: https://bugs.kde.org/show_bug.cgi?id=351175 Some times, as a Linux user and a Plasma fan, seeing no patches for some issues make me not want to notify issues cause seems my efforts to notify this problems are good for nothing. You can be sure non English speakers (like me) have an extra effort to try to report issues to developers. Anyway, I give thanks and best wishes to KDE community and developers for their day to day job. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402389] [Wayland] Crash when using "Close all" on viewers [crash in wl_proxy_marshal_array_constructor_versioned]
https://bugs.kde.org/show_bug.cgi?id=402389 Kevin Funk changed: What|Removed |Added Summary|[Wayland] Crash when using |[Wayland] Crash when using |"Close all" on viewers |"Close all" on viewers ||[crash in ||wl_proxy_marshal_array_cons ||tructor_versioned] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401818] Discover never asks for confirmation to install dependencies
https://bugs.kde.org/show_bug.cgi?id=401818 --- Comment #3 from Nate Graham --- The dependencies are already available on the app page if you want to look at them. I think the challenge here is separating benign dependencies from unwanted dependencies. In your case case GNOEME's GDM was an unwanted dependency, but how could Discover know that? I guess it probably could warn for GNOME dependencies, but that might get annoying because of you're installing Nautilus, then of course you want GNOME dependencies! Can you tell which app pulled in GDM? This sounds like it's more of a packaging bug than anything else. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402340] Executable: baloo_file_extractor PID: 1972 Signal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=402340 Kai Uwe Broulik changed: What|Removed |Added Product|BalooWidgets|frameworks-baloo Component|general |Engine CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Thread 1 (Thread 0x7fb1ea95d880 (LWP 1972)): [KCrash Handler] #5 0x7fb1e7e21760 in __memmove_avx_unaligned_erms () from /lib/libc.so.6 #6 0x7fb1e9ee269e in ?? () from /usr/lib/libKF5BalooEngine.so.5 #7 0x7fb1e9ecf3e0 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/libKF5BalooEngine.so.5 #8 0x7fb1e9edfa96 in Baloo::WriteTransaction::commit() () from /usr/lib/libKF5BalooEngine.so.5 #9 0x7fb1e9ed7962 in Baloo::Transaction::commit() () from /usr/lib/libKF5BalooEngine.so.5 #10 0x004095dc in ?? () #11 0x7fb1e86bef17 in ?? () from /usr/lib/libQt5Core.so.5 #12 0x7fb1e86b329b in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7fb1e90c686c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7fb1e90cd8e0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7fb1e8684428 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7fb1e86dd689 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #17 0x7fb1e869 in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7fb1e2cf82f7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7fb1e2cf8508 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x7fb1e2cf858c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7fb1e86de10f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #22 0x7fb1e8682d0a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7fb1e868b7f0 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #24 0x00408151 in ?? () #25 0x7fb1e7cf0ae7 in __libc_start_main () from /lib/libc.so.6 #26 0x004081ea in _start () -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #85 from Mathieu Roy --- Nate, you are right: we should have made a bounty/kickstarted this earlier. Way earlier. Probably we did not because many would have though it would be done anyway. That was a mistake on our part, all of us following this reports since more than a decade. This KDE bug tracking system should have an integrated kickstarter-alike system! Instead of adding ourselves to CC, we would add ourselves to a pledge, I am sure at some point we could raise some reasonable amount of cash. I personally unfortunately lost interest in KDE because that, and many other little things (I wont say what it relates to, to avoid off-topic flamewar), forced me not only to no longer use it (granted: not so meaningful, I nowadays use mostly use awesomewm - so I could deal with it and work around it) but I also was forced to make non-geek people (parents, in-laws and such) I am administering the computer of use something else because things like this had to work. But if someone is kickstarting something about it, I would donate a few coins still :-) and I am sure I would not be alone. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #84 from Jean-Francois Juneau --- If we raised enough money is it a project that developers at Blue Systems could take? -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Thomas Merkel changed: What|Removed |Added CC|t...@core.io | -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #83 from Marcel Partap --- It's clear that the current global pool of FLOSS maintainers is overloaded and we as open source community should strive to set up more attractive incentive systems and get more people involved in development in 2019. We at https://OpenSourceEcology.de are trying to get industry investing in open source hardware, which is difficult. OSEG wants to team up with the free software free knowledge student club https://fsfw-dresden.de to circulate more of our free software USB sticks. With support of our Studentenrat, we gave away 120 8GB-sticks with a KDE debian live to uni freshers this year.. The next idea is to give these sticks with live working office & pim suite & fresh builds of freecad to f.e. industrial engineers to check out as a tool for business and offering them to invest into resolving specific bugs and implementing specific features (c.f. blog post https://fsfw-dresden.de/2018/06/interview-sander-finanzierung-freie-software.html "Interview mit Prof. Sander: Finanzierung von freier Software"). If we can offer a better more accessible ecosystem (faircoin bounties, public monuments, free chocolate? .. c.f. https://fsfw-dresden.de/2018/08/funding-floss.html "Funding Freedom Initiative - Idee zur Finanzierung freier Softwareprojekte") for this, we might have a chance to convert more of society to use and develop open source systems. Or we wait until http://OpenAI.com learns to code and have the AI agents fix the bugs : ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen
https://bugs.kde.org/show_bug.cgi?id=402392 Samer Masterson changed: What|Removed |Added CC||sa...@samertm.com --- Comment #1 from Samer Masterson --- Thanks for filing! For context, Dropbox two tray icon implementations, one that uses QSystemTrayIcon and one that uses libappindicator. I believe this issues happens with the libappindicator icon, which Dropbox will use if libappindicator and libgtk are installed, and org.kde.StatusNotifierWatcher returns true for IsStatusNotifierHostRegistered. Regarding this issue, I believe the problem is that Dropbox only creates the tray menu when the tray is clicked, and there's some race between when KDE figures out the height of the menu to show and when it shows the menu. E.g. on startup, Dropbox may create a menu with 4 items in it. When the user clicks on the Dropbox tray icon, we'll recreate the menu with 8 items in it, and KDE will try to show those 8 items in a menu that only has the height of a menu with 4 items. If Dropbox created the menu more frequently, e.g. once every second, then it's less likely that users will notice this issue because we'll have probably created the menu of the correct height well before they click the tray icon. We aren't doing that because Dropbox leaks memory every time it creates that menu (which we should fix), and we need to fix that bug first. But on KDE's end, if you recalculate the height of the menu every time it changes, that would also fix the issue for Dropbox and potentially other apps. If someone can point me to the code for KDE's default status tray, I can take a crack at it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401818] Discover never asks for confirmation to install dependencies
https://bugs.kde.org/show_bug.cgi?id=401818 --- Comment #2 from Patrick Silva --- Some time ago discover installed Gnome sections on my system together some app. Now my login manager has "Gnome" and "Gnome on X11" sessions and I can't remove Gnome sections completelly because many other packages would be removed together. If Discover had warned me that packages related to gnome sessions would be installed along with the software I wanted, I would not have proceeded. Discover should show which dependecies will install, so the user can decide if want or not to proceed. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390804] [regression] Application Dashboard doesn't show tooltips
https://bugs.kde.org/show_bug.cgi?id=390804 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #2 from Shmerl --- I can confirm, that it's not showing toolips for launchers anymore. It's especially annoying since dashboard cuts long launcher titles, so often it's impossible to know that the name is when there are several ones starting the same way. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387503] Configure window opens with a wrong width
https://bugs.kde.org/show_bug.cgi?id=387503 --- Comment #3 from Patrick Silva --- At least "Configure kdenlive..." window is affected in "Project defaults" section. I have kdenlive 18.12 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
