[konsole] [Bug 445173] New: Konsole crash when attempting to make new (and renamed) profile "default"

2021-11-08 Thread Ty Wait
https://bugs.kde.org/show_bug.cgi?id=445173

Bug ID: 445173
   Summary: Konsole crash when attempting to make new (and
renamed) profile "default"
   Product: konsole
   Version: 21.08.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: tywai...@gmail.com
  Target Milestone: ---

Application: konsole (21.08.2)

Qt Version: 5.15.3
Frameworks Version: 5.87.0
Operating System: Linux 5.11.0-38-generic x86_64
Windowing System: X11
Distribution: KDE neon User - Plasma 25th Anniversary Edition
DrKonqi: 5.23.2 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:  I had 3 tabs open in one
Konsole window.  I had set the history length to 1 in one of the tabs by
clicking "Edit Current Profile..." in Settings.  I used that tab for several
commands before going to a second tab (it already existed).  I did some
commands with lengthy output and noticed it wasn't retaining 1 lines.  I
checked the settings for the second tab, discovering it still had a 1000 line
history (yes, I'm new to Konsole :).  I again set the history for "current
profile" to 1 lines.  I went into "Manage Profiles..." in Settings and
discovered my actions had created two new profiles (Profile 1 and Profile 2). 
I renamed Profile 1 to "Local standard".  I then highlighted Local Standard and
clicked "Set as Default".  Konsole crashed immediately.

I started a new Konsole instance and noticed that the rename had been
successful, but not changing "Local standard" to default.  This time I was able
to set "Local standard" to default and also remove "Profile 2" without
incident.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault

[New LWP 28252]
[New LWP 28264]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f3f75da0aff in __GI___poll (fds=0x7fffd7f8eaf8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f3f708899c0 (LWP 28207))]

Thread 3 (Thread 0x7f3f6f01f700 (LWP 28264)):
#0  0x7f3f75da0aff in __GI___poll (fds=0x7f3f60004e60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3f7430a36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3f7430a4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3f7636e61b in QEventDispatcherGlib::processEvents
(this=0x7f3f6b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3f763128ab in QEventLoop::exec (this=this@entry=0x7f3f6f01ebb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f3f7612c2c2 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f3f751b4f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f3f7612d45c in QThreadPrivate::start (arg=0x7f3f75238d80) at
thread/qthread_unix.cpp:329
#8  0x7f3f74ccb609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f3f75dad293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3f6fd1c700 (LWP 28252)):
#0  0x7f3f75da0aff in __GI___poll (fds=0x7f3f6fd1bae8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3f73f03c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f3f73f0590a in xcb_wait_for_event () from
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f3f7046ae88 in QXcbEventQueue::run (this=0x55b32296b6b0) at
qxcbeventqueue.cpp:228
#4  0x7f3f7612d45c in QThreadPrivate::start (arg=0x55b32296b6b0) at
thread/qthread_unix.cpp:329
#5  0x7f3f74ccb609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f3f75dad293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3f708899c0 (LWP 28207)):
[KCrash Handler]
#4  0x7f3f775fd077 in ?? () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#5  0x7f3f776a39ec in Konsole::ProfileList::updateAction(QAction*,
QExplicitlySharedDataPointer) () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#6  0x7f3f776a40ae in
Konsole::ProfileList::profileChanged(QExplicitlySharedDataPointer
const&) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#7  0x7f3f7634adce in QtPrivate::QSlotObjectBase::call (a=0x7fffd7f8f8c0,
r=0x55b322b277e0, this=0x55b322b29510) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate (sender=0x7f3f77725080, signal_index=5,
argv=0x7fffd7f8f8c0) at kernel/qobject.cpp:3886
#9  0x7f3f7769d519 in
Konsole::ProfileManager::profileChanged(QExplicitlySharedDataPointer
const&) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#

[konsole] [Bug 445173] Konsole crash when attempting to make new (and renamed) profile "default"

2021-11-08 Thread Ty Wait
https://bugs.kde.org/show_bug.cgi?id=445173

--- Comment #2 from Ty Wait  ---
   Ahmad -

   Thanks for your reply. I noticed there were several bugs involving
   Konsole's profile, so I'm amenable to your assessment. I'm running a
   KDE Neon system update now that includes a Konsole update. Maybe I
   should have applied that update earlier :-)

   I noticed the immutability of the "built-in" profile, and the
   rationale you present for such a profile being a global fallback makes
   a lot of sense.

   Thanks for the quick response!!

   -Ty

   On 11/8/21 2:39 PM, Ahmad Samir wrote:

 https://bugs.kde.org/show_bug.cgi?id=445173  
 Ahmad Samir   [1]  changed:

What|Removed |Added


  CC|| a.samir...@gmail.com
[1] 
 --- Comment #1 from Ahmad Samir   [1]  ---
 I tested with your steps to reproduce, and I don't see this issue with the
 master branch; there has been various changes to the profile dialog(s),
and so
 I assume it's been fixed in master.

 FWIW, when you edit the "built-in" profile, the code creates a new profile
 because the built-in one is immutable, it acts as a global fallback if you
have
 no profiles at all.




   1. mailto:a.samir...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.