[kexi] [Bug 372372] New: Kexi crashes when opening PSQL DB

[Tim Van den Langenbergh]

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

Bug ID: 372372
   Summary: Kexi crashes when opening PSQL DB
   Product: kexi
   Version: 2.9.11
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: kexi-b...@kde.org
  Reporter: tmt_...@gmx.com
CC: a...@piggz.co.uk, in...@fables.co.za
  Target Milestone: ---

Application: kexi (2.9.11)
KDE Platform Version: 4.14.25
Qt Version: 4.8.7
Operating System: Linux 4.8.6-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

I was trying to open a postgresql DB, version 9.4. I'm running OpenSUSE
Tumbleweed and have set up postgresql to use MD5 passwords.

-- Backtrace:
Application: Kexi (kexi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f34ad557e00 (LWP 30707))]

Thread 3 (Thread 0x7f348354c700 (LWP 30972)):
#0  0x7f34ab3ff6fd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f34a78fcb00 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f348354ba20, __fd=) at /usr/include/bits/unistd.h:44
#2  0x7f34a78fcb00 in g_wakeup_acknowledge (wakeup=0x7f34840025a0) at
gwakeup.c:210
#3  0x7f34a78b8325 in g_main_context_check
(context=context@entry=0x7f347c0009a0, max_priority=2147483647,
fds=fds@entry=0x7f347c003010, n_fds=n_fds@entry=1) at gmain.c:3707
#4  0x7f34a78b8814 in g_main_context_iterate
(context=context@entry=0x7f347c0009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3926
#5  0x7f34a78b898c in g_main_context_iteration (context=0x7f347c0009a0,
may_block=may_block@entry=1) at gmain.c:3990
#6  0x7f34ab88384e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f347c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#7  0x7f34ab851b9f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f348354bc40, flags=...) at kernel/qeventloop.cpp:149
#8  0x7f34ab851f05 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f348354bc40, flags=...) at kernel/qeventloop.cpp:204
#9  0x7f34ab740899 in QThread::exec() (this=this@entry=0x15baf40) at
thread/qthread.cpp:538
#10 0x7f34ab831983 in QInotifyFileSystemWatcherEngine::run()
(this=0x15baf40) at io/qfilesystemwatcher_inotify.cpp:265
#11 0x7f34ab74316a in QThreadPrivate::start(void*) (arg=0x15baf40) at
thread/qthread_unix.cpp:352
#12 0x7f34a87ad454 in start_thread (arg=0x7f348354c700) at
pthread_create.c:333
#13 0x7f34ab40c39f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f3488dbe700 (LWP 30726)):
#0  0x7f34ab40368d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f34a78b8876 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f3484003210, timeout=, context=0x7f34840009a0)
at gmain.c:4228
#2  0x7f34a78b8876 in g_main_context_iterate
(context=context@entry=0x7f34840009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3924
#3  0x7f34a78b898c in g_main_context_iteration (context=0x7f34840009a0,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f34ab88384e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f34840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x7f34ab851b9f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f3488dbdc40, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f34ab851f05 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3488dbdc40, flags=...) at kernel/qeventloop.cpp:204
#7  0x7f34ab740899 in QThread::exec() (this=this@entry=0x14a0980) at
thread/qthread.cpp:538
#8  0x7f34ab831983 in QInotifyFileSystemWatcherEngine::run()
(this=0x14a0980) at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f34ab74316a in QThreadPrivate::start(void*) (arg=0x14a0980) at
thread/qthread_unix.cpp:352
#10 0x7f34a87ad454 in start_thread (arg=0x7f3488dbe700) at
pthread_create.c:333
#11 0x7f34ab40c39f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f34ad557e00 (LWP 30707)):
[KCrash Handler]
#6  0x7f34ab6bcc68 in main_arena () at /lib64/libc.so.6
#7  0x7f34828f6905 in pqxx::connection_base::activate() () at
/usr/lib64/libpqxx-4.0.so
#8  0x7f34828f8f62 in  () at /usr/lib64/libpqxx-4.0.so
#9  0x7f348291bc20 in pqxx::transaction_base::DirectExec(char const*, int)
() at /usr/lib64/libpqxx-4.0.so
#10 0x7f348290638f in pqxx::nontransaction::do_exec(char const*) () at
/usr/lib64/libpqxx-4.0.so
#11 0x7f348291c966 in
pqxx::transaction_base::exec(std::__cxx11::basic_string, std::allocator > const&,
std::__cxx11::basic_string, std::allocator >
const&) () at /usr/lib64/libpqxx-4.0.so
#12 0x7f3482b423bf in  () at /usr/lib64/kde4/kexidb_pqxxsqldriver.so
#13 0x7f3482b43dca in  () at /usr/lib64/

[plasmashell] [Bug 483434] New: Plasma crashed around lock screen

[Tim Van den Langenbergh]

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

Bug ID: 483434
   Summary: Plasma crashed around lock screen
Classification: Plasma
   Product: plasmashell
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: tmt_...@gmx.com
  Target Milestone: 1.0

Application: plasmashell (6.0.1)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.9-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.1 [CoredumpBackend]

-- Information about the crash:
I had locked the session, was out for about half an hour and when I returned
and unlocked the 'plasma shell has crashed' dialog was waiting for me.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 38924]
[New LWP 39140]
[New LWP 39126]
[New LWP 38931]
[New LWP 38951]
[New LWP 38959]
[New LWP 38946]
[New LWP 38945]
[New LWP 39128]
[New LWP 39138]
[New LWP 41236]
[New LWP 39124]
[New LWP 39321]
[New LWP 38957]
[New LWP 39142]
[New LWP 39009]
[New LWP 39320]
[New LWP 41784]
[New LWP 39343]
[New LWP 39353]
[New LWP 39345]
[New LWP 39341]
[New LWP 39117]
[New LWP 39324]
[New LWP 44145]
[New LWP 41238]
[New LWP 41786]
[New LWP 39422]
[New LWP 39421]
[New LWP 41240]
[New LWP 39125]
[New LWP 44159]
[New LWP 38958]
[New LWP 39423]
[New LWP 44147]
[New LWP 44161]
[New LWP 39127]
[New LWP 39344]
[New LWP 39351]
[New LWP 41300]
[New LWP 44160]
[New LWP 39342]
[New LWP 39420]
[New LWP 41301]
[New LWP 41783]
[New LWP 41302]
[New LWP 41785]
[New LWP 41237]
[New LWP 41782]
[New LWP 41303]
[New LWP 44146]
[New LWP 38950]
[New LWP 41239]
[New LWP 39139]
[New LWP 41304]
[New LWP 44148]
[New LWP 39141]
[New LWP 44162]
[New LWP 44149]
[New LWP 39350]
[New LWP 38956]
[New LWP 44163]
[New LWP 39352]
[New LWP 39354]
[New LWP 39419]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x71be972ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x71be9161d9c0 (LWP 38924))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x71be9161d9c0 (LWP 38924))]

Thread 65 (Thread 0x71bdeea006c0 (LWP 39419)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be966a3c10 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x71be97dc084b in ??? () at /usr/lib/libQt6Quick.so.6
#4  0x71be966a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#6  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 64 (Thread 0x71bdf96006c0 (LWP 39354)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 63 (Thread 0x71bdfaa006c0 (LWP 39352)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 62 (Thread 0x71bdb16006c0 (LWP 44163)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 61 (Thread 0x71be82a006c0 (LWP 38956)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 60 (Thread 0x71bdfbe006c0 (LWP 39350)):
#0  0x71be972a5ebe 

[plasmashell] [Bug 483434] Plasma crashed around lock screen

[Tim Van den Langenbergh]

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

--- Comment #2 from Tim Van den Langenbergh  ---
"Nate Graham"  writes:

> https://bugs.kde.org/show_bug.cgi?id=483434
>
> Nate Graham  changed:
>
>What|Removed |Added
> 
>  CC||n...@kde.org
>  Resolution|--- |BACKTRACE
>  Status|REPORTED|NEEDSINFO
>
> --- Comment #1 from Nate Graham  ---
> Cannot reproduce, no KDE code is implicated in what I can see from the
> backtrace, and the backtrace has no debug symbols for anything that would 
> help.
> :(
>
> If this crash is reproducible, could you please install debug symbols,
> reproduce the crash, and attach a new symbolicated backtrace? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
>
> Thanks!

Got it, I'll install debug symbols and if I get a crash that looks similar
(though hopefully that won't happen), I'll try to remember to add to this
issue.

Actually, mightn't it be better to close this issue and just have me open a new
one if something similar happens again? That way you won't have an open mystery
issue that may never be solvable due to lack of information.

Sorry for the unhelpful backtrace, the crash reporting program said it 'may be
helpful', but I guess it wasn't.

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

[Falkon] [Bug 421410] New: Show menu bar key combination

[Tim Van den Langenbergh]

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

Bug ID: 421410
   Summary: Show menu bar key combination
   Product: Falkon
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: tmt_...@gmx.com
  Target Milestone: ---

For users without a mouse it would be prudent to add a key combination to show
the menu bar. Konsole binds it to Shift+M by default.

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

[Falkon] [Bug 421410] Show menu bar key combination

[Tim Van den Langenbergh]

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

--- Comment #1 from Tim Van den Langenbergh  ---
I meant Ctrl+Shift+M.

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

[plasmashell] [Bug 392322] New: Desktop icons only appear on one monitor

[Tim Van den Langenbergh]

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

Bug ID: 392322
   Summary: Desktop icons only appear on one monitor
   Product: plasmashell
   Version: 5.12.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: tmt_...@gmx.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

I am using two monitors with the standard folder view showing the Desktop
folder.

Ever since last time I updated the desktop icons are only appearing on the
monitor which is detected first, with no icons appearing on the other monitor.

I can fix it by changing the location the one monitor shows to the explicit
Desktop folder by setting the view to specific location -> Desktop, but that
causes the icon names to always show the full name with extension instead of
the application name.

The problem also appears if I set both monitors to show the same folder. I have
tested this both under Wayland and X and the problem is identical under both.

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

[kget] [Bug 389663] kget window does not open under wayland

[Tim Van den Langenbergh]

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

--- Comment #7 from Tim Van den Langenbergh  ---
Tried it, it works fine, that was amzingly fast. Thank you very much.

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

[kgpg] [Bug 376367] New: KGPG crashes when adjusting the trust level of a key

[Tim Van den Langenbergh]

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

Bug ID: 376367
   Summary: KGPG crashes when adjusting the trust level of a key
   Product: kgpg
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: tmt_...@gmx.com
  Target Milestone: ---

Application: kgpg (16.12.1)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.7-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

I was raising the trust level of my preferred key from "Unknown" to "Ultimate",
as I noticed I had forgotten to do so when I imported it.

The crash can be reproduced every time.

-- Backtrace:
Application: KGpg (kgpg), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f487de58900 (LWP 2452))]

Thread 4 (Thread 0x7f484b8c5700 (LWP 2459)):
#0  0x7f487794666d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4870a56886 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f4844002e70, timeout=, context=0x7f4844000990)
at gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f4844000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3924
#3  0x7f4870a5699c in g_main_context_iteration (context=0x7f4844000990,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f487847d18b in QEventDispatcherGlib::processEvents
(this=0x7f48440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f4878426aea in QEventLoop::exec (this=this@entry=0x7f484b8c4cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f4878254813 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f48782594c8 in QThreadPrivate::start (arg=0x1cd62b0) at
thread/qthread_unix.cpp:368
#8  0x7f4873706454 in start_thread (arg=0x7f484b8c5700) at
pthread_create.c:333
#9  0x7f487794f37f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f48579c3700 (LWP 2454)):
#0  0x7ffe94bf6b12 in clock_gettime ()
#1  0x7f487795c216 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f48579c29f0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f48782fe771 in qt_clock_gettime (ts=0x7f48579c29f0, clock=) at tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x7f487847ae09 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f4850002ed0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f487847b3b5 in QTimerInfoList::timerWait (this=0x7f4850002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f487847c75e in timerSourcePrepareHelper (timeout=0x7f48579c2ac4,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=,
timeout=timeout@entry=0x7f48579c2ac4) at kernel/qeventdispatcher_glib.cpp:165
#9  0x7f4870a55d6d in g_main_context_prepare
(context=context@entry=0x7f485990, priority=priority@entry=0x7f48579c2b50)
at gmain.c:3501
#10 0x7f4870a567ab in g_main_context_iterate
(context=context@entry=0x7f485990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3909
#11 0x7f4870a5699c in g_main_context_iteration (context=0x7f485990,
may_block=may_block@entry=1) at gmain.c:3990
#12 0x7f487847d18b in QEventDispatcherGlib::processEvents
(this=0x7f4858c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7f4878426aea in QEventLoop::exec (this=this@entry=0x7f48579c2c90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x7f4878254813 in QThread::exec (this=) at
thread/qthread.cpp:507
#15 0x7f4878aee385 in ?? () from /usr/lib64/libQt5DBus.so.5
#16 0x7f48782594c8 in QThreadPrivate::start (arg=0x7f4878d5fd20) at
thread/qthread_unix.cpp:368
#17 0x7f4873706454 in start_thread (arg=0x7f48579c3700) at
pthread_create.c:333
#18 0x7f487794f37f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f485d32b700 (LWP 2453)):
#0  0x7f487794666d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f48727843e0 in poll (__timeout=-1, __nfds=1, __fds=0x7f485d32abc0)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x16b70e0, cond=cond@entry=0x16b7120,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479
#3  0x7f4872786179 in xcb_wait_for_event (c=0x16b70e0) at xcb_in.c:693
#4  0x7f485f440889 in QXcbEventReader::run (this=0x16c17b0) at
qxcbconnection.cpp:1343
#5  0x7f48782594c8 in QThreadPrivate::start (arg=0x16c17b0) at
thread/qthread_unix.cpp:368
#6  0x7f4873706454 in start_thread (arg=0x7f485d32b700) at
pthread_create.c:333
#7  0x7f487794f37f in c

[kget] [Bug 389663] New: kget window does not open under wayland

[Tim Van den Langenbergh]

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

Bug ID: 389663
   Summary: kget window does not open under wayland
   Product: kget
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: k...@kde.org
  Reporter: tmt_...@gmx.com
CC: wba...@tmo.at
  Target Milestone: ---

Created attachment 110243
  --> https://bugs.kde.org/attachment.cgi?id=110243&action=edit
terminal output of kget under wayland

Like the description says, the main window of kget that shows the downloads and
everything does not open when running KDE wayland session.

The other windows (configuration, adding new download) do open normally.

No problems under X11. Attached is output of a session.

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

[kxkb] [Bug 347392] Fcitx layout priority reversed

[Tim Van den Langenbergh]

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

Tim Van den Langenbergh  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Tim Van den Langenbergh  ---
In the meantime the issue has been fixed.

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

[kget] [Bug 389663] kget window does not open under wayland

[Tim Van den Langenbergh]

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

--- Comment #2 from Tim Van den Langenbergh  ---
The about menu says it's version 2.95.0.

I can open the other menus through right-clicking the system tray icon.

Trying the restore option doesn't do anything, though.

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

[kate] [Bug 360252] Error downloading highlighting files

[Tim Van den Langenbergh via KDE Bugzilla]

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

Tim Van den Langenbergh  changed:

   What|Removed |Added

 CC||tmt_...@gmx.com

--- Comment #1 from Tim Van den Langenbergh  ---
Yeah, the kate devs should run update.sh from their FTP, I'd do it, but I don't
have access.

You can just download the XML files you need and put them in
~/.local/share/katepart5/syntax.

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