[krita] [Bug 436705] Krita crashes on exit every time
https://bugs.kde.org/show_bug.cgi?id=436705 --- Comment #5 from Airton --- Created attachment 147494 --> https://bugs.kde.org/attachment.cgi?id=147494=edit New crash information added by DrKonqi krita (4.2.9) using Qt 5.12.8 - What I was doing when the application crashed: Open and immediately close Krita. An error message apears in tray to tell Krita ended unexpectedly - Unusual behavior I noticed: Closing Krits is not unexpected! - Custom settings of the application: -- Backtrace (Reduced): #12 0x7fef92af0908 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fef92af0e1d in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fef920c3eee in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fef92af0c29 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #17 0x7fef920c3eee in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436705] Krita crashes on exit every time
https://bugs.kde.org/show_bug.cgi?id=436705 Airton changed: What|Removed |Added CC||airtonluci...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 --- Comment #6 from Airton --- I commented before that the problem occurs sometimes, but I couldn't find out what should be causing it. Now, I think it's related with the layout configuration of the desktop. So, in case you can't replicate the crash, try setting the "Layout" field to "Folder View" in "Desktop Context Menu > Configure Desktop and Wallpaper... > Wallpaper" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 --- Comment #4 from Airton --- (In reply to Bharadwaj Raju from comment #3) > What apps do you have in the system tray? Besides the standard apps, I have Insync 3.2.4.40856 and Telegram 3.1.8 in the system tray. Update: Now the problem can't be reproduced every time. It only occurs occasionally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] New: plasmashell crashes after starting
https://bugs.kde.org/show_bug.cgi?id=443961 Bug ID: 443961 Summary: plasmashell crashes after starting Product: plasmashell Version: 5.23.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: airton.ram...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.0) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-37-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.0 [KCrashBackend] -- Information about the crash: The crash notification appears after loading the desktop. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1384] [New LWP 1428] [New LWP 1502] [New LWP 1504] [New LWP 1505] [New LWP 1506] [New LWP 1611] [New LWP 1690] [New LWP 1695] [New LWP 1749] [New LWP 1767] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f5d87b74aff in __GI___poll (fds=0x7ffd1dbdfdb8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f5d83cc99c0 (LWP 1353))] Thread 12 (Thread 0x7f5d4522c700 (LWP 1767)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557cfe6bd350) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557cfe6bd300, cond=0x557cfe6bd328) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557cfe6bd328, mutex=0x557cfe6bd300) at pthread_cond_wait.c:647 #3 0x7f5d87f0959b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557cfe6bd300) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7f5d7c008840, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5d89b72b44 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f5d89b72fb9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f5d87f0342c in QThreadPrivate::start(void*) (arg=0x7f5d7c0087a0) at thread/qthread_unix.cpp:329 #8 0x7f5d86e52609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5d87b81293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f5d46256700 (LWP 1749)): #0 0x7f5d8646d4dd in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5d86420270 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5d864204a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5d881445eb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f5d24000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5d880e887b in QEventLoop::exec(QFlags) (this=this@entry=0x7f5d46255ba0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f5d87f02292 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f5d4633607c in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f5d87f0342c in QThreadPrivate::start(void*) (arg=0x557cfcd0b7e0) at thread/qthread_unix.cpp:329 #8 0x7f5d86e52609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5d87b81293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f5d5d8c3700 (LWP 1695)): #0 0x7f5d8646d4dd in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5d8641fdac in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5d86420312 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5d864204a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5d881445eb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f5d5b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f5d880e887b in QEventLoop::exec(QFlags) (this=this@entry=0x7f5d5d8c2ba0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f5d87f02292 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f5d89aad3ba in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f5d87f0342c in QThreadPrivate::start(void*) (arg=0x557cfc2cb2a0) at thread/qthread_unix.cpp:329 #9 0x7f5d86e52609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f5d87b81293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f5d5efe6700 (LWP 1690)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557cfd268810) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common
[frameworks-kio] [Bug 400006] Opening a HTTP link downloads the page instead of opening it
https://bugs.kde.org/show_bug.cgi?id=46 Airton changed: What|Removed |Added CC||airtonluci...@gmail.com --- Comment #25 from Airton --- (In reply to Dolandemort from comment #24) > I discovered the cause of this for me was having the incorrect command set > in the firefox.desktop file listed in the start menu (not sure how it's > called in KDE). I found it was necessary to specify "/usr/bin/firefox %U" > instead of just "/usr/bin/firefox". Excellent! Thank you! This is exactly what was happening here and that %U save me. Or my computer! My system is a Kubuntu 20.04 and the problem was with Google Chrome needing that %U in menu's launcher. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434590] New: Can't open grouped tasks in Wayland
https://bugs.kde.org/show_bug.cgi?id=434590 Bug ID: 434590 Summary: Can't open grouped tasks in Wayland Product: plasmashell Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: airton.ram...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I have a grouped task in Icons-Only Task Manager, I can't open any of the grouped apps unless I minimize all the other apps. This happens only using Plasma Wayland. STEPS TO REPRODUCE 1. Right click over the Icons-Only Task Manager > Configure Icons-only Task Manager... > Behavior > Select "By program name" on "Group:" and "Cycles through tasks" on "Clicking grouped task:" 2. Open at least two instances of any app to have a grouped task on the task manager 3. Open a different app 4. Go back to the grouped task by clicking on the grouped task icon on the task manager OBSERVED RESULT The click doesn't have any effect EXPECTED RESULT It should active at least one of the grouped tasks (like it happens using X11) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.21 User Edition (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385473] Kate always crashes when I close it with Ctrl+W
https://bugs.kde.org/show_bug.cgi?id=385473 --- Comment #2 from Airton <airton.ram...@gmail.com> --- (In reply to Darren Lissimore from comment #1) > Tried reproduction on KDE-Neon; > Qt 5.9.1 > Frameworks 5.39.0 > Kate 17.08.1 > > Can't reproduce it. > > Working on getting an older system up and running. > There are few bug reports showing up using Qt 5.7.1 > - and will try and get a test system up with that Qt base. Is it safe to upgrade Kubuntu 17.04 to KDE Neon using PPA? I'm very interessing to use this new KDE OS, but I can't format my system (at least now) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385473] New: Kate always crashes when I close it with Ctrl+W
https://bugs.kde.org/show_bug.cgi?id=385473 Bug ID: 385473 Summary: Kate always crashes when I close it with Ctrl+W Product: kate Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: airton.ram...@gmail.com Target Milestone: --- Application: kate (16.12.3) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-35-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: 1) Create an empty file 2) Write something and save it 3) Close the kate with Ctrl+W - Unusual behavior I noticed: Throws an "segmentation fault" exception The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f074f198900 (LWP 2638))] Thread 2 (Thread 0x7f0739b7a700 (LWP 2639)): #0 0x7f0749946d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0744296576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f074429668c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f074a5720bb in QEventDispatcherGlib::processEvents (this=0x7f07340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f074a51bbea in QEventLoop::exec (this=this@entry=0x7f0739b79c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f074a349f83 in QThread::exec (this=this@entry=0x7f074abf5d20 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x7f074a9845d5 in QDBusConnectionManager::run (this=0x7f074abf5d20 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f074a34ec38 in QThreadPrivate::start (arg=0x7f074abf5d20 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #8 0x7f07463c76da in start_thread (arg=0x7f0739b7a700) at pthread_create.c:456 #9 0x7f0749952d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f074f198900 (LWP 2638)): [KCrash Handler] #6 0x7f074a4e5f08 in QSortFilterProxyModel::parent (this=0x55ef394ce150, child=...) at itemmodels/qsortfilterproxymodel.cpp:1900 #7 0x7f074bbda29b in QModelIndex::parent (this=0x55ef39be33e8) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:417 #8 QTreeView::isIndexHidden (this=0x55ef396dbc00, index=...) at itemviews/qtreeview.cpp:3032 #9 0x7f074bbdc93f in QTreeView::visualRect (this=0x55ef396dbc00, index=...) at itemviews/qtreeview.cpp:1113 #10 0x7f074bb848da in QAccessibleTableCell::rect (this=0x55ef39be33c0) at accessible/itemviews.cpp:1063 #11 0x7f0738c248ae in AtSpiAdaptor::accessibleInterfaces (this=this@entry=0x55ef39b421a0, interface=interface@entry=0x55ef39be33c0) at linuxaccessibility/atspiadaptor.cpp:1472 #12 0x7f0738c2b463 in AtSpiAdaptor::accessibleInterface (this=this@entry=0x55ef39b421a0, interface=interface@entry=0x55ef39be33c0, function=..., message=..., connection=...) at linuxaccessibility/atspiadaptor.cpp:1412 #13 0x7f0738c2b9e9 in AtSpiAdaptor::accessibleInterface (this=0x55ef39b421a0, interface=0x55ef39be33c0, function=..., message=..., connection=...) at linuxaccessibility/atspiadaptor.cpp:1368 #14 0x7f0738c2fd6c in AtSpiAdaptor::handleMessage (this=0x55ef39b421a0, message=..., connection=...) at linuxaccessibility/atspiadaptor.cpp:1282 #15 0x7f074a9929b0 in QDBusConnectionPrivate::activateObject (this=0x7f0734008920, node=..., msg=..., pathStartPos=27) at qdbusintegrator.cpp:1451 #16 0x7f074a99535e in QDBusActivateObjectEvent::placeMetaCall (this=0x7f073400e460) at qdbusintegrator.cpp:1610 #17 0x7f074a54a639 in QObject::event (this=0x55ef39b421a0, e=) at kernel/qobject.cpp:1263 #18 0x7f074b94e35c in QApplicationPrivate::notify_helper (this=, receiver=0x55ef39b421a0, e=0x7f073400e460) at kernel/qapplication.cpp:3799 #19 0x7f074b955b21 in QApplication::notify (this=0x7e601f00, receiver=0x55ef39b421a0, e=0x7f073400e460) at kernel/qapplication.cpp:3556 #20 0x7f074a51dc00 in QCoreApplication::notifyInternal2 (receiver=0x55ef39b421a0, event=event@entry=0x7f073400e460) at kernel/qcoreapplication.cpp:988 #21 0x7f074a52039d in QCoreApplication::sendEvent (event=0x7f073400e460, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55ef3921a1c0) at kernel/qcoreapplication.cpp:1649 #23 0x7f074a520808 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0,
[Discover] [Bug 372838] New: Problems to update Kubuntu 16.10 by Discover
https://bugs.kde.org/show_bug.cgi?id=372838 Bug ID: 372838 Summary: Problems to update Kubuntu 16.10 by Discover Product: Discover Version: 5.7.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: airton.ram...@gmail.com Target Milestone: --- Created attachment 102417 --> https://bugs.kde.org/attachment.cgi?id=102417=edit Steps to reproduce the bug When new updates are available, discover reports that the system has been updated instead of listing the updates. Even if I refresh with Ctrl+R opens the same screen. Reproducible: When new updates are available. Steps to reproduce: 1- Click "update" on the widget that shows in notification area Actual results: It shows a screen that the system has been updated. Expected results: List the new updates -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 326581] Muon Update does not show the new updates, after notification message
https://bugs.kde.org/show_bug.cgi?id=326581 --- Comment #18 from Airton <airton.ram...@gmail.com> --- This is happening with the version 5.7.5 on Kubuntu 16.10. Always when new updates are available, discover shows "no updates" screen instead of listing the updates. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 326581] Muon Update does not show the new updates, after notification message
https://bugs.kde.org/show_bug.cgi?id=326581 Airton <airton.ram...@gmail.com> changed: What|Removed |Added CC||airton.ram...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
