[konsole] [Bug 384856] New: KDE Konsole crashes when I try to add a new profile, when I click on the "background" field

[shevegen]

https://bugs.kde.org/show_bug.cgi?id=384856

            Bug ID: 384856
           Summary: KDE Konsole crashes when I try to add a new profile,
                    when I click on the "background" field
           Product: konsole
           Version: 17.08.1
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: konsole-devel at kde.org
          Reporter: shevegen at gmail.com
  Target Milestone: ---

Hello KDE people,

After years, with help from the LFS/BLFS team, I managed to compile quite a lot
of KDE - yay, go me! \o/

I even got konsole to work, or at the least, to start up, using this version:

https://download.kde.org/stable/applications/17.08.1/src/konsole-17.08.1.tar.xz

Konsole starts fine and I can use it. The default is white background and black
font but I prefer black background and white font. So I tried to change the
profiles ... well.

First thing, the profiles list is empty. I probably did something wrong but I
think it may be useful if, in the event that the profiles list is empty,
perhaps some widget or some other way, right button press, or whatever, can
inform a user a bit why this is the case. I understand that the KDE apps will
default casual users rather than people who compile from source but ... right
now I have ABSOLUTELY no idea as to why the profile list is empty. Anyway, I
guess I may figure out one day, but for now, this report is actually about
something afterwards.

I realized that the profile list was emtpy but one can create a new profile
list. So I tried this.

But when I clicked on the white rectangular box next to the "Background" slot,
konsole crashed.

The error dump on the commandline is:

QStandardPaths: wrong ownership on runtime directory /Depot/Temp, 1000 instead
of 0
QStandardPaths: wrong ownership on runtime directory /Depot/Temp, 1000 instead
of 0
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not
be saved or shared with other applications.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

(konsole:15836): GdkPixbuf-WARNING **: Bug! loader 'png' didn't set an error on
failure

(konsole:15836): Gtk-WARNING **: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.

(konsole:15836): GdkPixbuf-WARNING **: Bug! loader 'png' didn't set an error on
failure
**
Gtk:ERROR:gtkiconhelper.c:493:ensure_surface_for_gicon: assertion failed:
(destination)
Aborted

Now, I am pretty sure that the error is on my side ... I have some libpng and
gdk-pixbuf related problem... probably also via gtk (although actually, almost
all of the gnome-related programs, including evince, that I use from the
commandline, do work fine). So the error is not so much about a problem WITHIN
kde konsole. But I am still annoyed that kde konsole just crashes.

So here is my suggestion to change this:

- IF an error like the above happens, such as when someone can not find a
loader for
png, then rather than crash, konsole could notify about the error; on the
commandline
of course, but also perhaps within the konsole application. A simple pop-up
widget
that may be triggered could suffice or perhaps even better, some in-app
notification
within konsole. Either way, I think notification is better than flat-out crash.

Feel free to proceed with this bug report in any way that you wish to,
including to
close it at any moment in time.

PS: Being able to set background and foreground on the commandline would be
neat, then I could just start konsole like so:  "konsole --bg black --fg
white", or something like that. Right now it seems as if profiles are
mandatory. Not sure why but that wasn't my decision anyway. I su ppose that I
could probably create
some profile on the commandline via ruby scripts ... but being fairly lazy, I
am not sure
I'll go just through that part only to have black background and white colours
again... but
who knows.

PSS: I actually also use a second konsole, from kde4... that one is at /usr
prefix; the
new konsole is in /Programs/Konsole/17.08.1 - no idea if that matters or not, I
think
it should not, since the error is related to gdk/gtk rather than konsole. But I
mention
it just for sake of completion. I am also not entirely sure why konsole
attempts to use
a gtk-dialog, perhaps some kde-dialog is unavailable? I have no idea... I have
not 
finished compiling all of kde so far, neither plasma... but I'll have a look
how this
goes in the coming weeks.

-- 
You are receiving this mail because:
You are the assignee for the bug.