date:20230119

[valgrind] [Bug 464476] Firefox fails to start under Valgrind

2023-01-19 Thread Paul Floyd

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

--- Comment #3 from Paul Floyd  ---
Almost there. 

I use VG_(find_executable)(VG_(args_the_exename)) then check if it is a link
and if so call VG_(readlink)(exe_name, out, VKI_PATH_MAX);

But readlink doesn't resolve relative paths to absolute paths.

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

[frameworks-qqc2-desktop-style] [Bug 443406] ScrollView is draggable with a mouse

2023-01-19 Thread Naxdy

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

Naxdy  changed:

   What|Removed |Added

 CC||xna...@hydra-development.ne
   ||t

--- Comment #6 from Naxdy  ---
(In reply to Oliver Beard from comment #5)
> (In reply to Pawel from comment #4)
> > I understand the fix should be included in this release?
> 
> Long ago, in Frameworks 5.91 (Currently 5.102). Perhaps it was broken again,
> or Nate was mistaken. I'm not sure if it would be more appropriate to
> re-open the bug or create a new bug.
> 
> I can reproduce it, but crucially not on every drag. I can't figure out why
> only some drags would produce the effect.

Apparently it's only an issue if you drag from the label. Grab any other part
of the element and it won't happen.

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

[valgrind] [Bug 178779] merge logrind 2

2023-01-19 Thread Paul Floyd

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

--- Comment #3 from Paul Floyd  ---
I'm trying to get down the backlog of ancient bugs that are "overcome by
events" and that are pretty much impossible for us to deal with.

I'll take a look at the links and see if at least the source can be put
somewhere more accessible.

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

[kwin] [Bug 464539] New: Kwin suddenly crash

2023-01-19 Thread Seppri

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

Bug ID: 464539
   Summary: Kwin suddenly crash
Classification: Plasma
   Product: kwin
   Version: 5.26.4
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: seppriyam...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.26.4)

Qt Version: 5.15.7
Frameworks Version: 5.101.0
Operating System: Linux 6.1.0-2.1-liquorix-amd64 x86_64
Windowing System: X11
Distribution: Nitrux 2.6.0 build.010123.ff
DrKonqi: 5.26.4 [KCrashBackend]

-- Information about the crash:
Kwin suddenly crash after closing file manager named Index, and sometimes, on
some software it still crashes. however, not too bad. I can still do activities
as usual

Translate this page

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  0x7f3dc591c209 in KWin::FocusChain::isUsableFocusCandidate
(prev=0x555cedb29d20, c=0x555cedb2a810, this=0x555cec967310) at
./src/focuschain.cpp:193
#5  KWin::FocusChain::nextForDesktop (desktop=0x555ceca7e370,
reference=0x555cedb29d20, this=0x555cec967310) at ./src/focuschain.cpp:205
#6  KWin::Workspace::activateNextWindow (this=0x555cec9ab1b0, window=) at ./src/activation.cpp:506
#7  0x7f3dc5a6dd20 in KWin::X11Window::destroyWindow (this=0x555cedb29d20)
at ./src/workspace.h:887
#8  0x7f3dc5974042 in KWin::X11Window::unmapNotifyEvent (e=,
this=0x555cedb29d20) at ./src/events.cpp:585
#9  KWin::X11Window::unmapNotifyEvent (this=0x555cedb29d20, e=)
at ./src/events.cpp:561
#10 0x7f3dc5976f8b in KWin::X11Window::windowEvent (this=0x555cedb29d20,
e=e@entry=0x7f3db0013320) at ./src/events.cpp:403
#11 0x7f3dc5978340 in KWin::Workspace::workspaceEvent (this=0x555cec9ab1b0,
e=0x7f3db0013320) at ./src/events.cpp:159
#12 0x7f3dc4074467 in QAbstractEventDispatcher::filterNativeEvent
(this=, eventType=..., message=message@entry=0x7f3db0013320,
result=result@entry=0x7ffe4307ddb8) at kernel/qabstracteventdispatcher.cpp:495
#13 0x7f3dbe497595 in QXcbConnection::handleXcbEvent
(this=this@entry=0x555cec68ce90, event=event@entry=0x7f3db0013320) at
./src/plugins/platforms/xcb/qxcbconnection.cpp:579
#14 0x7f3dbe498cd6 in QXcbConnection::processXcbEvents
(this=0x555cec68ce90, flags=...) at
./src/plugins/platforms/xcb/qxcbconnection.cpp:1065
#15 0x7f3dbe4bfc87 in xcbSourceDispatch (source=) at
./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103
#16 0x7f3dc15be7a9 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f3dc15bea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f3dc15beacc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f3dc40d0af8 in QEventDispatcherGlib::processEvents
(this=0x555cec7564a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#20 0x7f3dc40759bb in QEventLoop::exec (this=this@entry=0x7ffe4307e040,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x7f3dc407df54 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x7f3dc44554e0 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1870
#23 0x7f3dc33996d9 in QApplication::exec () at kernel/qapplication.cpp:2829
#24 0x555ceae7677b in main (argc=, argv=) at
./src/main_x11.cpp:407
[Inferior 1 (process 4612) detached]

The reporter indicates this bug may be a duplicate of or related to bug 451693,
bug 463961, bug 452785, bug 400394, bug 449762, bug 463434.

Reported using DrKonqi

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

[systemsettings] [Bug 464535] Charging limit is not saved

2023-01-19 Thread Iyán Méndez Veiga

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

--- Comment #1 from Iyán Méndez Veiga  ---
Reverting this fixes the issue for me:
https://invent.kde.org/plasma/powerdevil/-/commit/a002ab4718760dfae156bd8fe8a17c59b0f09182

As additional info, my laptop has a pen with some battery that charges when
stored in the laptop. It appears as wacom_battery_0 in /sys/class/power_supply.
Maybe after that commit, powerdevil tries to changes the limit on the pen
instead of the laptop's battery?

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

[kdenlive] [Bug 464538] New: Counter with high values does not fit the background

2023-01-19 Thread bugzilla_noreply

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

Bug ID: 464538
   Summary: Counter with high values does not fit the background
Classification: Applications
   Product: kdenlive
   Version: 22.12.1
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: krzysztof.swia...@student.uj.edu.pl
  Target Milestone: ---

STEPS TO REPRODUCE
1. Open the application.
2. Click on Project->Generators->Counter.
3. Type in a very high duration (for example all 9's).
4. Press OK.
5. Save the file in a valid location.
6. Drag the newly created counter from the Project Bin onto a track.

OBSERVED RESULT
The counter's duration is not capped and displays a very high number that goes
past the edges of the clip.

EXPECTED RESULT
The counter's duration is capped.

SOFTWARE/OS VERSIONS
Windows: 8.1
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version:  5.101.0
Qt Version: 5.15.7

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

[systemsettings] [Bug 464537] New: Application Appearance crashes systemsettings

2023-01-19 Thread Brian Wright

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

Bug ID: 464537
   Summary: Application Appearance crashes systemsettings
Classification: Applications
   Product: systemsettings
   Version: 5.26.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: b...@briandwright.com
  Target Milestone: ---

Application: systemsettings (5.26.5)

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 5.15.0-58-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 5.26
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
Application Appearance crashes systemsettings everytime it attempts to open. 
Uninstalling and reinstall qt5-style-plugins donest not resolve the issue

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139775347375744)
at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139775347375744) at
./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=139775347375744, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#7  0x7f2000c78476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7f2000c5e7f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x7f200111bba3 in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#10 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffcdb9579f0, msg=msg@entry=0x7f2001515de8 "Cannot mix
incompatible Qt library (%d.%d.%d) with this library (%d.%d.%d)") at
global/qlogging.cpp:893
#11 0x7f2001131d9c in
QObjectPrivate::checkForIncompatibleLibraryVersion(int) const (this=, version=) at kernel/qobject_p.h:438
#12 QObjectPrivate::checkForIncompatibleLibraryVersion(int) const
(version=, this=) at kernel/qobject_p.h:430
#13 QObjectPrivate::QObjectPrivate(int) (this=,
version=) at kernel/qobject.cpp:191
#14 0x7f1f9f77af01 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/styles/libqgtk2style.so
#15 0x7f2001fd8312 in qLoadPlugin(QFactoryLoader
const*, QString const&) (key=..., loader=0x7f20024bba80 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder>) at
../../include/QtCore/5.15.8/QtCore/private/../../../../../src/corelib/plugin/qfactoryloader_p.h:108
#16 QStyleFactory::create(QString const&) (key=) at
styles/qstylefactory.cpp:105
#17 0x7f1fdc0c1004 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so
#18 0x7f1fff0cd2f2 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#19 0x7f1fff062235 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#20 0x7f1fff06284d in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#21 0x7f1ffc86d363 in  () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#22 0x7f1fff588375 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#23 0x7f1fff579e3d in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#24 0x7f1fff586b38 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#25 0x7f1fff58b13e in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#26 0x7f1fff58b49a in QQuickItemView::modelUpdated(QQmlChangeSet const&,
bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#27 0x7f200137e108 in doActivate(QObject*, int, void**)
(sender=0x55a8a66ebbe0, signal_index=4, argv=0x7ffcdb9581a0) at
kernel/qobject.cpp:3935
#28 0x7f1ffc84003a in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&,
bool) () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#29 0x7f1ffc860e7c in  () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#30 0x7f1ffc8674c2 in  () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#31 0x7f1ffc8678c8 in  () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#32 0x7f1ffc87305d in QQmlDelegateModel::_q_modelReset() () at
/lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#33 0x7f1ffc873ca3 in QQmlDelegateModel::qt_metacall(QMetaObject::Call,
int, void**) () at /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#34 0x7f200137de46 in doActivate(QObject*, int, void**)
(sender=0x55a8a5c16290, signal_index=21, argv=0x7ffcdb958400) at
kernel/qobject.cpp:3949
#35 0x7f2001377177 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f20015e5680
,
local_signal_index=local_signal_index@entry=18, argv=argv@entry=0x7ffcdb958400)
at kernel/qobject.cpp:3983
#36 0x7f20012df191 in
QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal)
(this=, _t1=...) at .moc/moc_qabstractitemmodel.cpp:648
#37 0x7f1fdc0bbb81 in  () at

[systemsettings] [Bug 464536] New: New "Highlight changed settings" prevents you from clicking on settings options

2023-01-19 Thread Raif Coonjah

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

Bug ID: 464536
Summary: New "Highlight changed settings" prevents you from
clicking on settings options
Classification: Applications
Product: systemsettings
Version: 5.26.90
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: raifcoon...@proton.me
Target Milestone: ---

Created attachment 155447
--> https://bugs.kde.org/attachment.cgi?id=155447=edit
A screenshot of the "Drop down" menu become some sort of Menu in itself?

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

STEPS TO REPRODUCE
1. Switch to Wayland
2. Open system settings
3. Toggle "Highlight changed settings" option on
4. Click on any of the settings options

OBSERVED RESULT
It prevents you from clicking on anything unless you click outside of the
Window and click back.
Also sometimes it opens another smaller window for you to choose your options.
[See attached]

EXPECTED RESULT
The drop down menu should close and let you do your thing.

SOFTWARE/OS VERSIONS
Windows: N/A
macOS: N/A
Linux/KDE Plasma: KDE Neon Testing Edition
(available in About System)
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Sorry for any mistakes, this is my first bug report D:

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

[systemsettings] [Bug 464535] New: Charging limit is not saved

2023-01-19 Thread Iyán Méndez Veiga

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

Bug ID: 464535
   Summary: Charging limit is not saved
Classification: Applications
   Product: systemsettings
   Version: 5.26.90
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_powerdevil
  Assignee: plasma-b...@kde.org
  Reporter: m...@iyanmv.com
CC: k...@privat.broulik.de
  Target Milestone: ---

SUMMARY
Trying to change the value of "Stop charging at" doesn't work anymore.

STEPS TO REPRODUCE
1. Go to System settings -> Power management -> Advanced Power Settings
2. Change "Stop charging at" to any value
3. Click apply and introduce password when asked
4. Close system settings
5. Open system settings again and check the value of "Stop charging at"

OBSERVED RESULT
The limit is not changed/saved.

I'm not 100% sure if this started to happen after upgrading to the Plasma 5.27
Beta, to Frameworks 5.102.0, or due to recent kernel upgrades. I can still
change the limit manually by setting the value in /sys/class/power_supply/BAT0.
After doing that, system settings shows the updated value. So it looks like it
can read but not write the setting.

The other limit, "Start charging only once below", is saved correctly.

EXPECTED RESULT
Both limits should be saved correctly. Also, would be nice to warn the user if
there was an error trying to update the values.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.6-arch1-3 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: LENOVO
Product Name: 20XYCTO1WW
System Version: ThinkPad X1 Yoga Gen 6

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

[plasmashell] [Bug 463659] Recurring plasmashell crash and restart

2023-01-19 Thread Enrico

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

Enrico  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

--- Comment #10 from Enrico  ---
Sorry for the double post, but I've manually installed more debug symbols and
get this backtrace. I hope it's useful, otherwise I have to give up because I
really don't know how to make it work

Thread 1 "plasmashell" received signal SIGPIPE, Broken pipe.
__GI___libc_write (nbytes=40, buf=0x561e8a631068, fd=25) at
../sysdeps/unix/sysv/linux/write.c:26
26return SYSCALL_CANCEL (write, fd, buf, nbytes);
(gdb) backtrace
#0  __GI___libc_write (nbytes=40, buf=0x561e8a631068, fd=25)
at ../sysdeps/unix/sysv/linux/write.c:26
#1  __GI___libc_write (fd=25, buf=0x561e8a631068, nbytes=40)
at ../sysdeps/unix/sysv/linux/write.c:24
#2  0x7f501993f060 in
QtWaylandClient::QWaylandDataSource::data_source_send(QString const&, int) ()
at /usr/lib/libQt5WaylandClient.so.5
#3  0x7f50199497fe in QtWayland::wl_data_source::handle_send(void*,
wl_data_source*, char const*, int) () at /usr/lib/libQt5WaylandClient.so.5
#4  0x7f501ad484f6 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#5  0x7f501ad44f5e in ffi_call_int
(cif=, fn=, rvalue=,
avalue=, closure=) at ../src/x86/ffi64.c:673
#6  0x7f501ad47b73 in ffi_call
(cif=cif@entry=0x7fff8356a290, fn=, rvalue=rvalue@entry=0x0,
avalue=avalue@entry=0x7fff8356a360) at ../src/x86/ffi64.c:710
#7  0x7f501b250645 in wl_closure_invoke
(closure=closure@entry=0x7f500801bd90, target=, 
target@entry=0x561e8a631190, opcode=opcode@entry=1, data=,
flags=1)
at ../wayland-1.21.0/src/connection.c:1025
#8  0x7f501b250e03 in dispatch_event
(display=display@entry=0x561e891d1eb0, queue=0x561e891d1f80)
at ../wayland-1.21.0/src/wayland-client.c:1595
#9  0x7f501b250ffc in dispatch_queue (queue=0x561e891d1f80,
display=0x561e891d1eb0)
--Type  for more, q to quit, c to continue without paging--
   at ../wayland-1.21.0/src/wayland-client.c:1741
#10 wl_display_dispatch_queue_pending (display=0x561e891d1eb0,
queue=0x561e891d1f80) at ../wayland-1.21.0/src/wayland-client.c:1983
#11 0x7f5019922bf6 in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /usr/lib/libQt5WaylandClient.so.5
#12 0x7f5018ebeae0 in doActivate(QObject*, int, void**)
(sender=0x561e8920c680, signal_index=4, argv=0x7fff8356a590) at
kernel/qobject.cpp:3935
#13 0x7f5018ed8b67 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x561e8920c680, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#14 0x7f5018e865ac in
QEventLoop::exec(QFlags) (this=0x7fff8356a6b0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#15 0x7f5018e910d9 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#16 0x561e878bf1ef in  ()
#17 0x7f501863c290 in __libc_start_call_main
(main=main@entry=0x561e878bc240, argc=argc@entry=2,
argv=argv@entry=0x7fff8356aa18) at ../sysdeps/nptl/libc_start_call_main.h:58
#18 0x7f501863c34a in __libc_start_main_impl (main=0x561e878bc240, argc=2,
argv=0x7fff8356aa18, init=, fini=,
rtld_fini=, stack_end=0x7fff8356aa08)
at ../csu/libc-start.c:381
#19 0x561e878bf5a5 in  ()

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

[systemsettings] [Bug 426937] kded5: Segmentation fault when I plug in controller with touchpad using xf86-input-libinput

2023-01-19 Thread Forest

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

Forest  changed:

   What|Removed |Added

 CC||fores...@sonic.net

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

[kmailtransport] [Bug 464534] New: Need to be able to override app name and app id

2023-01-19 Thread Aaron Williams

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

Bug ID: 464534
   Summary: Need to be able to override app name and app id
Classification: Applications
   Product: kmailtransport
   Version: 5.22.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

SUMMARY
I am trying to connect to my employer's Office365 mail server and am forced to
use EWS, unfortunately, the app name "Akonadi" is not approved. There needs to
be a method to override these settings to match Outlook. Changing the custom
user agent does not seem to affect this.

STEPS TO REPRODUCE
1.  Try to connect to Office365 via EWS
2.  Watch it fail due to unsupported app name/id

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[frameworks-qqc2-desktop-style] [Bug 443406] ScrollView is draggable with a mouse

2023-01-19 Thread Oliver Beard

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

Oliver Beard  changed:

   What|Removed |Added

 CC||olib...@outlook.com

--- Comment #5 from Oliver Beard  ---
(In reply to Pawel from comment #4)
> I understand the fix should be included in this release?

Long ago, in Frameworks 5.91 (Currently 5.102). Perhaps it was broken again, or
Nate was mistaken. I'm not sure if it would be more appropriate to re-open the
bug or create a new bug.

I can reproduce it, but crucially not on every drag. I can't figure out why
only some drags would produce the effect.

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

[plasma-systemmonitor] [Bug 464533] New: Questions and Observations

2023-01-19 Thread bugzilla_noreply

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

Bug ID: 464533
   Summary: Questions and Observations
Classification: Plasma
   Product: plasma-systemmonitor
   Version: 5.24.4
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: betlogbet...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Questions:
- why is there no remote machine monitoring?
- when will it be added?
- where are examples of how to graph/display custom data from bash scripts?
- why are there so few hardware sensors? Fans etc.
- why is there no hard drive % / xBytes *remaining*?
- why does Kubuntu 22.04 not auto-update to the newer versions? (5.24.4 vs
5.26.90). How do i do that manually? Or is this problematic?
- why is there no tool to convert ksysguard to plasma-systemmonitor format.

Observations:
- S.M.A.R.T data seems like a worthy addition
- It's difficult to imagine why kysyguard has been "obsoleted" by
plasma-systemmonitor when the latter has no remote machine monitoring, and
apparently no scripting capability. Please tell me this is all covered in the
newer versions.

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

1 2 3 4 5 >

1 - 100 of 412 matches

Mail list logo