[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-08-29 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #30 from Pietro Pizzi --- Hi, Today the problem #12/#20 was back. BUT I found out what I can do about it, without disturbing you again ;). Maybe this information helps you in any way!? If I remove the folder '~/.local/share/konqueror

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-08-03 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #29 from Pietro Pizzi --- Hi and sorry for my hiatus. First vacation, then family and work stuff... Yesterday I have time again for my free-time computer stuff ;), updated my arch system first and... bam, konqueror fixed upstream! So

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-07-03 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #25 from Pietro Pizzi --- Created attachment 160066 --> https://bugs.kde.org/attachment.cgi?id=160066=edit New konqueror log file. No konqueror process was running. Now it's the output of: > QT_LOGGING_RULES="org.kde.konq

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-07-02 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #23 from Pietro Pizzi --- Created attachment 160052 --> https://bugs.kde.org/attachment.cgi?id=160052=edit The command line output from konqueror This is the output of > QT_LOGGING_RULES="konqueror.debug=true;libkonq

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-07-02 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #22 from Pietro Pizzi --- Sorry but it's really hard to say for certain. On Arch I update "all the time" ;) but often doesn't reboot right after. I often use S3 and reboot approximately every other week. One Konqueror window, I

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-07-02 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #20 from Pietro Pizzi --- Hi, For me the Problem from "Comment 12" (https://bugs.kde.org/show_bug.cgi?id=463358#c12) is back (in the normal Arch build). The only difference is that it didn't closes the "oldest" wind

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-02-01 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #18 from Pietro Pizzi --- Should I try to patch the urlloader.cpp to and test it again!? Or is this unrelated to my "restart-loop" and you just post the upstream commit? -- You are receiving this mail because: You are watchi

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-01-08 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #14 from Pietro Pizzi --- No dialog, so I think I have it disabled at some point. Yes I have the lines... [Reusing] AlwaysHavePreloaded=false PreloadOnStartup=false ...in my actual konquerorrc. My autosave looks like... (I can't post

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-01-05 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #12 from Pietro Pizzi --- That worked. Now I can compile it without errors. When I start the new one "./konqueror-build/bin/konqueror" it doesn't crash on it's own. But it starts all my previous sessions in an endless loop.

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2023-01-05 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #10 from Pietro Pizzi --- (In reply to Stefano Crocco from comment #8) > Both your crashes are caused by the same code. Looking again at it, I > noticed that it didn't check for a situation which could lead to the crash. >

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2022-12-27 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #6 from Pietro Pizzi --- Yes, normally it get's started with the KDE Autostart with the argument "--open-session Download" (plus I have excluded it from the session management). It's possible that I grabt the trace from the

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2022-12-23 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #4 from Pietro Pizzi --- Working around Christmas... that's the open source spirit ;)! If I can test or provide something more, let me know! -- You are receiving this mail because: You are watching all bug changes.

[konqueror] [Bug 463358] I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2022-12-22 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 --- Comment #2 from Pietro Pizzi --- I managed to get the debug symbols :) Application: Konqueror (konqueror), signal: Segmentation fault Content of s_kcrashErrorMessage: std::unique_ptr = {get() = } [KCrash Handler] #6 KonqView::url (this=0x0

[konqueror] [Bug 463358] New: I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore

2022-12-22 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=463358 Bug ID: 463358 Summary: I updated KDE/Plasma on my Arch installation and now I can't start Konqueror anymore Classification: Applications Product: konqueror Version: 22.12.0

[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)

2020-08-19 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=424311 Pietro Pizzi changed: What|Removed |Added CC||pietro.pi...@gmx.net --- Comment #28 from

[dolphin] [Bug 371130] unable to reassign standard shortcut for backspace to "up" instead of "back"

2020-05-25 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=371130 --- Comment #16 from Pietro Pizzi --- Or, please, make that additional columns! 3 1/2 years ... HHCIB? And no, I wouldn't imagine a world where a linux user is such a DAU that "this might also easily overwhelm users" can be true! WTF ... m

[dolphin] [Bug 371130] unable to reassign standard shortcut for backspace to "up" instead of "back"

2018-05-03 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=371130 Pietro Pizzi <pietro.pi...@gmx.net> changed: What|Removed |Added CC||pietro.pi...@g

[dolphin] [Bug 367614] Devices in left panel are not alphabetically sorted (order change each time Dolphin is opened)

2017-10-06 Thread Pietro Pizzi
https://bugs.kde.org/show_bug.cgi?id=367614 Pietro Pizzi <pietro.pi...@gmx.net> changed: What|Removed |Added CC||pietro.pi...@g