from:"Mohammed"

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

Bug ID: 480425
   Summary: Skanlite runs the scan again after saving a scanned
image
Classification: Applications
   Product: Skanlite
   Version: 23.08.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: the.9a3e...@gmail.com
  Target Milestone: ---

SUMMARY
When I scan a document wirelessly, it opens a dialog with the scanned result.
After saving the document, for some reason, skanlite sometimes runs the scanner
again. This sometimes happens and sometimes doesn't, if I recall correctly. I'm
not sure what triggers it.

STEPS TO REPRODUCE
1. Run skanlite
2. Preview a document
3. Make a selection in the preview
4. Scan the document
5. In the document that pops up, save the document (I used PDF)

OBSERVED RESULT
The documents gets saved, and the dialog closes, but the scanner is scanning
again unnecessarily (sometimes).

EXPECTED RESULT
The document gets saved and the dialog closes only

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro Linux 
KDE Plasma Version:  KDE Plasma 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
I am using an HP Officejetpro 8620 via network (laptop connected wirelessly,
scanner is via ethernet). I am using the flatbet scanner at 300dpi.

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

[Skanlite] [Bug 480426] New: Wait for scanner to not be busy before scanning

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

Bug ID: 480426
   Summary: Wait for scanner to not be busy before scanning
Classification: Applications
   Product: Skanlite
   Version: 23.08.4
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: the.9a3e...@gmail.com
  Target Milestone: ---

SUMMARY
When using the app, particularly when using the Flatbed scanner, I often make a
preview first, select what I want, and then scan. After the preview is done,
the scanner moves the scanner head back to the start. If I press the scan
button before the scanner head has finished moving, Skanlite will complain that
the scanner is busy... While this is correct behaviour and isn't really a bug,
this means that I have to wait for the scanner to finish moving before pressing
the scan button, which is inconvenient. 

Ideally, the app should know that I should start scanning immediately after the
scanner stops being busy. To improve the user experience a little, I would like
to suggest that the app itself wait for the scanner to stop being busy before
starting to scan again, especially if it's right after a preview, with a
timeout of maybe 30-60 seconds.


STEPS TO REPRODUCE
1. Make a preview from the scanner
2. Before the scan head goes back to the starting position, press the scan
button.

OBSERVED RESULT
An error dialog appears with "Scanner is busy"

EXPECTED RESULT
The application waits until the scan head moves back to the start position, and
then starts the scan.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
I am using an HP Officejet Pro 8620 via the network. My laptop is connected
wirelessly to the network, and the printer/scanner is connected via ethernet.

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

[Skanlite] [Bug 480427] New: Preview somtimes displays incorrectly with scaling

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

Bug ID: 480427
   Summary: Preview somtimes displays incorrectly with scaling
Classification: Applications
   Product: Skanlite
   Version: 23.08.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: the.9a3e...@gmail.com
  Target Milestone: ---

Created attachment 165304
  --> https://bugs.kde.org/attachment.cgi?id=165304&action=edit
Skanlite screenshot after startup with 150% scaling

SUMMARY
If the desktop has scaling enabled, and you start skanlite, the preview pane
doesn't look like it's being displayed correctly. However, after previewing
something, it does get displayed properly centered and scaled down. 

This isn't a very major issue, because the app is still usable, but it really
gives a janky feel to the app.

STEPS TO REPRODUCE
1. Set scaling to something higher than 100% (I've testing 150% and 200%)
2. Start skanlite

OBSERVED RESULT
The preview pane is not centered correctly

EXPECTED RESULT
The preview pane should be displayed and centered correctly, just like how it
does after you perform a preview.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
I am using Wayland usually with 150% scaling. I am not sure if this issue
occurs in X11. When writing this report, I was closing the app, changing the
scaling settings, and then started the app again without rebooting.

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

[Skanlite] [Bug 480427] Preview somtimes displays incorrectly with scaling

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

--- Comment #1 from Mohammed Khoory  ---
Created attachment 165305
  --> https://bugs.kde.org/attachment.cgi?id=165305&action=edit
Skanlite screenshot after startup with 200% scaling

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

[Skanlite] [Bug 480427] Preview somtimes displays incorrectly with scaling

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

--- Comment #2 from Mohammed Khoory  ---
Created attachment 165306
  --> https://bugs.kde.org/attachment.cgi?id=165306&action=edit
Skanlite screenshot after startup with 100% scaling

As a reference, this is what I expect to see working correctly when scaling is
enabled.

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

[filelight] [Bug 487470] New: Cursor near bottom or right edge of window has tooltips appear on the opposite side of the window

2024-05-24 Thread Mohammed Chelouti

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

Bug ID: 487470
   Summary: Cursor near bottom or right edge of window has
tooltips appear on the opposite side of the window
Classification: Applications
   Product: filelight
   Version: 24.05.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: m.chelo...@bluewin.ch
CC: martin.sandsm...@kde.org
  Target Milestone: ---

Created attachment 169767
  --> https://bugs.kde.org/attachment.cgi?id=169767&action=edit
Demonstration of the odd tooltip placement

SUMMARY
Tooltip positioning in Filelight is wrong when the cursor is getting close to
the bottom or right window border.

STEPS TO REPRODUCE
1. Perform a scan
2. Ensure the application window is sized in a way that the pie chart has very
little padding from the window border
2. Move the mouse cursor over the pie chart and observe the tooltip
3. Move the cursor close the bottom or right edge

OBSERVED RESULT
The tooltip will be rendered on the opposite side of the *window*, when the
cursor is too close to the edge.

EXPECTED RESULT
The tooltip will be rendered on the opposite side of the *cursor* (if window
border is at physical screen border) OR beyond the window border.

SOFTWARE/OS VERSIONS
Linux: ArchLinux
Kernel: 6.9.1
KDE Plasma Version: N/A
KDE Frameworks Version: 6.2.1 
Qt Version: 6.7.1 (Built against 6.7.0)
Display Server Platform: Wayland
Wayland Compositor: river 0.3.0

ADDITIONAL INFORMATION
The issue can be observed, regardless of how close to a border of the physical
monitor the window border is.

I checked if other KDE apps have the same issue. But both Dolphin and Okular
draw differnet looking tooltips that are rendered outside the window border.

Only tested on Wayland.

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

[Skanpage] [Bug 487530] New: No indication of PDF exporting progress

2024-05-25 Thread Mohammed Khoory

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

Bug ID: 487530
   Summary: No indication of PDF exporting progress
Classification: Applications
   Product: Skanpage
   Version: 24.02.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: a.stipp...@gmx.net
  Reporter: the.9a3e...@gmail.com
  Target Milestone: ---

SUMMARY
After scanning a few pages, when exporting a PDF, there is no indication of the
export progress. The dialog 

For small PDFs this may not be a problem, but for large PDFs with OCR enabled,
the export process may take some time (especially with OCR).  However, the app
doesn't show any indication that saving is still in progress. The only way I
can tell that the PDF is still being exported is my CPU goes high for several
seconds and I only know that it's done when it goes back down.

STEPS TO REPRODUCE
1. Scan a few pages with text
2. Export the PDF but make sure you have OCR enabled
3. Press the save button

OBSERVED RESULT
The dialog disappears. There is no way for you to know if it's still saving or
if it's done

EXPECTED RESULT
A dialog, or some inidication should show that the app is still not done saving
the file.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.6.30-2-MANJARO (64bit)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Skanpage installed from Manjaro's repos.
Using Wayland on Intel graphics. Using a HP OfficeJet Pro 8620 as my scanner. 
Tessaract version 5.3.4-1 installed from Manjaro repo
I was running an OCR with turkish and arabic languages.

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

[plasmashell] [Bug 445529] New: Brightness too low when using keyboard keys to decrease brightness

2021-11-15 Thread Mohammed Sameer

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

Bug ID: 445529
Summary: Brightness too low when using keyboard keys to
decrease brightness
Product: plasmashell
Version: 5.23.3
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: glifwen...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0

Created attachment 143576
--> https://bugs.kde.org/attachment.cgi?id=143576&action=edit
brightness

SUMMARY
Brightness too low when using keyboard keys to decrease brightness to 0
percentage, the display appears as if is switched off. But when I use
flashlight on display I can see display contents with very low brightness.
If I decrease the brightness to 0 percentage using slider in system tray then I
can see the contents of display which is also very low brightness, but visible
without flashlight.
When I checked the file "/sys/class/backlight/intel_backlight/brightness" while
decreasing the brightness to 0 percentage, it's value is 1 when using system
tray slider & it's value is 0 when using keyboard keys. Please see the attached
video.

The problem is clear when using Dim screen after 5 minutes & switch off after
10 minutes, after 5 minutes the screen does not appear as dimmed but it appears
as if it is switched off, but visible when using external lightning like
flashlight on the screen.

***
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.
2.
3.

OBSERVED RESULT

EXPECTED RESULT

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-40-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[ksplash] [Bug 434820] ksplashqml crashed when login in wayland session

2021-09-29 Thread Mohammed Sameer

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

--- Comment #2 from Mohammed Sameer  ---
New crash info:

Application: ksplashqml (ksplashqml), signal: Segmentation fault

[New LWP 1514]
[New LWP 1515]
[New LWP 1516]
[New LWP 1517]
[New LWP 1518]
[New LWP 1519]
[New LWP 1526]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x56290a9d3fc0) at ../sysdeps/nptl/futex-internal.h:183
[Current thread is 1 (Thread 0x7f5b6f617980 (LWP 1500))]

Thread 8 (Thread 0x7f5b5db0b700 (LWP 1526)):
[KCrash Handler]
#4  0x7f5b73a5d3dc in wl_proxy_marshal () from
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
#5  0x7f5b6e680297 in wl_surface_attach (y=, x=, buffer=, wl_surface=) at
/usr/include/wayland-client-protocol.h:3613
#6  dri2_wl_swap_buffers_with_damage (disp=0x56290a667ff0, draw=0x7f5b400c0090,
rects=0x0, n_rects=0) at ../src/egl/drivers/dri2/platform_wayland.c:1102
#7  0x7f5b6e6753b2 in dri2_swap_buffers (disp=0x56290a667ff0,
surf=0x7f5b400c0090) at ../src/egl/drivers/dri2/egl_dri2.c:2001
#8  0x7f5b6e66cf71 in eglSwapBuffers (dpy=0x56290a667ff0,
surface=) at ../src/egl/main/eglapi.c:1346
#9  0x7f5b6f017d59 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so
#10 0x7f5b74b30b31 in QOpenGLContext::swapBuffers(QSurface*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x7f5b753ff1bc in QSGRenderThread::syncAndRender (this=0x56290a87e6b0,
grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:870
#12 0x7f5b75402f77 in QSGRenderThread::run (this=0x56290a87e6b0) at
scenegraph/qsgthreadedrenderloop.cpp:1043
#13 0x7f5b7452442c in QThreadPrivate::start (arg=0x56290a87e6b0) at
thread/qthread_unix.cpp:329
#14 0x7f5b734e6609 in start_thread (arg=) at
pthread_create.c:477
#15 0x7f5b741a4293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f5b64e53700 (LWP 1519)):
#0  0x7f5b74197aff in __GI___poll (fds=0x7f5b4c004e60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5b722a836e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5b722a84a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5b747655eb in QEventDispatcherGlib::processEvents
(this=0x7f5b4c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5b7470987b in QEventLoop::exec (this=this@entry=0x7f5b64e52c00,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f5b74523292 in QThread::exec (this=this@entry=0x56290a8c4e40) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f5b73f12549 in QQmlThreadPrivate::run (this=0x56290a8c4e40) at
qml/ftw/qqmlthread.cpp:155
#7  0x7f5b7452442c in QThreadPrivate::start (arg=0x56290a8c4e40) at
thread/qthread_unix.cpp:329
#8  0x7f5b734e6609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f5b741a4293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f5b65654700 (LWP 1518)):
#0  __GI___libc_read (nbytes=16, buf=0x7f5b656539e0, fd=11) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=11, buf=0x7f5b656539e0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f5b722f0b2f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5b722a7ebe in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5b722a8312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f5b722a84a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f5b747655eb in QEventDispatcherGlib::processEvents
(this=0x7f5b48000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f5b7470987b in QEventLoop::exec (this=this@entry=0x7f5b65653bf0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7f5b74523292 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9  0x7f5b750e5f4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7f5b7452442c in QThreadPrivate::start (arg=0x7f5b75169d80) at
thread/qthread_unix.cpp:329
#11 0x7f5b734e6609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7f5b741a4293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f5b66072700 (LWP 1517)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x56290a673318) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56290a6732c8,
cond=0x56290a6732f0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x56290a6732f0, mutex=0x56290a6732c8) at
pthread_cond_wait.c:638
#3  0x7f5b6cc10e7b in cnd_wait (mtx=0x56290a6732c8, cond=0x56290a6732f0) at
../include/c11/threads_posi

[Breeze] [Bug 444752] New: Option for auto hiding scroll bars.

2021-10-31 Thread Mohammed Sameer

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

Bug ID: 444752
   Summary: Option for auto hiding scroll bars.
   Product: Breeze
   Version: 5.23.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Created attachment 143078
  --> https://bugs.kde.org/attachment.cgi?id=143078&action=edit
example

SUMMARY
Option for auto hiding scroll bars in apps, launcher etc.
It would be good, if we have auto hiding scrollbars in entire plasma desktop.
Scroll bars that will auto hide when not hovered upon & shown when we hover
over them.
Please see the attached video.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
Scroll bars that will auto hide, when not hovered over them.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 444754] New: Change color of volume percentage at high volume levels while using earphones

2021-10-31 Thread Mohammed Sameer

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

Bug ID: 444754
   Summary: Change color of volume percentage at high volume
levels while using earphones
   Product: plasmashell
   Version: 5.23.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: glifwen...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Change color of volume percentage above high volume levels like 70% or 75% to
caution it is not good for ears, when using headphones or earphones.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
Color of volume percentage changes above high volume levels to caution that it
is not good to ears.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION
I think it is also applicable to bluetooth earphones.

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

[plasma-nm] [Bug 444755] New: Wi-Fi not auto connecting to a saved Hidden network

2021-10-31 Thread Mohammed Sameer

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

Bug ID: 444755
   Summary: Wi-Fi not auto connecting to a saved Hidden network
   Product: plasma-nm
   Version: 5.23.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
Wi-Fi not auto connecting to a saved Hidden network when the laptop is powered
on.

STEPS TO REPRODUCE
1. Connect to a hidden network by entering network name & password.
2. Restart the computer and login
3. 

OBSERVED RESULT
The saved hidden network is not connected automatically.

EXPECTED RESULT
The saved hidden network is connected automatically when powered on.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 456827] New: Request for per-activity icon visibility configurations

2022-07-17 Thread Mohammed Khoory

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

Bug ID: 456827
   Summary: Request for per-activity icon visibility
configurations
   Product: plasmashell
   Version: 5.24.6
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: the.9a3e...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Hello,

Currently in the KDE system tray configuration, I am able to configure the
visibility status of different icons. However, this visibility status applies
to all activities at the moment. It would be nice if I am able to control the
visibility of each icon on a per-activity basis.

Rationale:
I am currently using activities as a way to remove distracting applications and
to enhance focus on certain tasks and workflowws, and I'm sure many others are
too. Some applications that you'd like to keep running in the background may be
too distracting when you're working on a particular activity. For example, chat
applications may be OK in one activity, but unwanted in another activity. It
would be nice if I could hide those chat application icons in that activity.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Manjaro Linux 5.15.53-1 MANJARO (64-bit)
(available in About System)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5

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

[krdc] [Bug 457618] New: Can't set security negotiation to RDP/TLS/NLA

2022-08-08 Thread Mohammed Gritli

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

Bug ID: 457618
   Summary: Can't set security negotiation to RDP/TLS/NLA
   Product: krdc
   Version: 21.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: RDP
  Assignee: uwol...@kde.org
  Reporter: m.j.gri...@gmail.com
CC: aa...@kde.org
  Target Milestone: ---

SUMMARY
***
KRDC doesn't have a setting to set security negotiation to RDP/NLA/TLS while
connecting.
This results in not being able to use the application with some versions of RDP
servers.
an option is available in freerdp "/sec:rdp" which overcomes the TLS version
issues.

STEPS TO REPRODUCE
1. connecting to any RDP server that doesn't have a compatible TLS version
2. 
3. 

OBSERVED RESULT
the screen closes without any error showing
I was able to troubleshoot the issue via freerdp command which shows:
transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED

EXPECTED RESULT
have the option to set security negotiation in connecting settings.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Option is there in Remmina as well

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

[krdc] [Bug 457618] Can't set security negotiation to RDP/TLS/NLA

2022-08-08 Thread Mohammed Gritli

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

Mohammed Gritli  changed:

   What|Removed |Added

 CC||m.j.gri...@gmail.com

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

[krdc] [Bug 457618] Can't set security negotiation to RDP/TLS/NLA

2022-08-08 Thread Mohammed Gritli

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

--- Comment #2 from Mohammed Gritli  ---
(In reply to Albert Astals Cid from comment #1)
> Does using the extra options field work?

Oh yes, now it works with extra options field.
but I didn't think of trying that, forgot it used freeRDP .
However, I think there should be an easy way to change those options since it's
a common issue.

Thank you

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

[kwin] [Bug 432581] New: Brightness & volume OSD not displaying in dolphin when hamburger menu is open.

2021-02-06 Thread Mohammed Sameer

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

Bug ID: 432581
   Summary: Brightness & volume OSD not displaying in dolphin when
hamburger menu is open.
   Product: kwin
   Version: 5.20.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
Brightness & Volume OSD not shown in dolphin and also Kinfocenter, when
hamburger menu is open.

STEPS TO REPRODUCE
1. Open dolphin, select hamburger menu 
2. change brightness or volume by keyboard buttons.
3. 

OBSERVED RESULT
The brightness & volume OSD are not displayed, brightness & volume also doesn't
change.

EXPECTED RESULT
The OSD should be displayed.

SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 432601] New: Inconsistent header border (separator) in Bluetooth applet when enabled.

2021-02-07 Thread Mohammed Sameer

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

Bug ID: 432601
   Summary: Inconsistent header border (separator) in Bluetooth
applet when enabled.
   Product: plasmashell
   Version: 5.20.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Created attachment 135478
  --> https://bugs.kde.org/attachment.cgi?id=135478&action=edit
Bluetooth off

SUMMARY
The Bluetooth header border is thick when Bluetooth is enabled, when Bluetooth
is off it is normal.

STEPS TO REPRODUCE
1. Open system tray applet
2. select Bluetooth & enable Bluetooth
3. 

OBSERVED RESULT
The Bluetooth applet header border is thick.

EXPECTED RESULT
The Bluetooth applet header border should be same as when Bluetooth is off.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 432601] Inconsistent header border (separator) in Bluetooth applet when enabled.

2021-02-07 Thread Mohammed Sameer

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

--- Comment #1 from Mohammed Sameer  ---
Created attachment 135479
  --> https://bugs.kde.org/attachment.cgi?id=135479&action=edit
Bluetooth on

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

[kcalc] [Bug 432894] New: Unit conversion feature should be present in Kcalc calculator

2021-02-13 Thread Mohammed Sameer

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

Bug ID: 432894
   Summary: Unit conversion feature should be present in Kcalc
calculator
   Product: kcalc
   Version: 20.12.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Unit conversion is a good feature for Kcalc, it would be useful if one doesn't
know the unit name or want to know the units of quantity like area.

I know it is already present in Krunner, also having this feature in Kcalc is
useful. Windows calculator also has this feature.

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

[ark] [Bug 432914] New: Don't calculate checksum automatically in properties window.

2021-02-13 Thread Mohammed Sameer

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

Bug ID: 432914
   Summary: Don't calculate checksum automatically in properties
window.
   Product: ark
   Version: 20.12.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: glifwen...@gmail.com
CC: aa...@kde.org, rthoms...@gmail.com
  Target Milestone: ---

Created attachment 135667
  --> https://bugs.kde.org/attachment.cgi?id=135667&action=edit
Ark Properties

SUMMARY
When we open large archive files(4.3 GiB) in ark & open properties then it
takes lot of resources (see screenshot) to calculate checksums automatically.

STEPS TO REPRODUCE
1. Open any large archive.
2. Open Archive menu & select properties.
3. 

OBSERVED RESULT
The SHA-256 hash etc. are calculated automatically & takes lot of CPU
resources.
Also when we close properties window before calculation completes it doesn't
free resources immediately.
This slows down computer for few minutes.
EXPECTED RESULT
The checksums should not be calculated automatically, there should be an option
to calculate checksums manually like dolphin does.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

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

[ark] [Bug 432914] Don't calculate checksum automatically in properties window.

2021-02-13 Thread Mohammed Sameer

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

--- Comment #1 from Mohammed Sameer  ---
Created attachment 135668
  --> https://bugs.kde.org/attachment.cgi?id=135668&action=edit
Dolphin properties

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

[Breeze] [Bug 433227] New: Inconsistent tooltips in system tray on mouse pointer hover.

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

Bug ID: 433227
   Summary: Inconsistent tooltips in system tray on mouse pointer
hover.
   Product: Breeze
   Version: 5.21.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
The tooltips which are shown when we hover over a item like menu in system tray
does not have rounded corners. The tooltips in plasma panel & applications like
dolphin, have rounded tooltip corners.
The issue is present in configure button of digital clock, application launcher
etc.
EXPECTED RESULT
The tooltips in system tray should have rounded corners, similar to tooltips in
other applications like dolphin which improves consistency.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

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

[Breeze] [Bug 433227] Inconsistent tooltips in system tray on mouse pointer hover.

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

--- Comment #1 from Mohammed Sameer  ---
Created attachment 135888
  --> https://bugs.kde.org/attachment.cgi?id=135888&action=edit
digital clock tooltip

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

[Breeze] [Bug 433227] Inconsistent tooltips in system tray on mouse pointer hover.

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

--- Comment #2 from Mohammed Sameer  ---
Created attachment 135889
  --> https://bugs.kde.org/attachment.cgi?id=135889&action=edit
network tooltip

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

[Breeze] [Bug 433227] Inconsistent tooltips in system tray on mouse pointer hover.

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

--- Comment #3 from Mohammed Sameer  ---
Created attachment 135890
  --> https://bugs.kde.org/attachment.cgi?id=135890&action=edit
edit mode tooltip

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

[Breeze] [Bug 433227] Inconsistent tooltips in system tray on mouse pointer hover.

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

--- Comment #4 from Mohammed Sameer  ---
Created attachment 135891
  --> https://bugs.kde.org/attachment.cgi?id=135891&action=edit
rounded tooltip dolphin

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

[Discover] [Bug 431896] The package source category header sometimes partially covers the first repo in that category

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

Mohammed Sameer  changed:

   What|Removed |Added

 CC||glifwen...@gmail.com

--- Comment #4 from Mohammed Sameer  ---
When I scroll to the bottom and scroll back up again the overlap is gone
temporarily. When I go to "About" section and then open settings, the overlap
issue again appeared.

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

[Discover] [Bug 431896] The package source category header sometimes partially covers the first repo in that category

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

--- Comment #5 from Mohammed Sameer  ---
Created attachment 135900
  --> https://bugs.kde.org/attachment.cgi?id=135900&action=edit
overlap temporarily gone

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

[krunner] [Bug 433243] New: Visual glitch in krunner button tooltips.

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

Bug ID: 433243
   Summary: Visual glitch in krunner button tooltips.
   Product: krunner
   Version: 5.21.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.loh...@gmx.de
  Reporter: glifwen...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 135901
  --> https://bugs.kde.org/attachment.cgi?id=135901&action=edit
krunner tooltip

SUMMARY
Open krunner and move cursor over "keep open" and "configure krunner" buttons.
The tooltips displayed have visual glitches.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

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

[kscreenlocker] [Bug 433384] New: typo in login screen "desktop session" menu

2021-02-21 Thread Mohammed Sameer

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

Bug ID: 433384
   Summary: typo in login screen "desktop session" menu
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

Created attachment 136014
  --> https://bugs.kde.org/attachment.cgi?id=136014&action=edit
login screen

SUMMARY
In login screen "wayland" word is repeated twice in a menu, which is used to
choose plasma wayland/x11 desktop session.

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

[gwenview] [Bug 433387] New: no tooltip in "save all" option displayed at the top of the modified image

2021-02-21 Thread Mohammed Sameer

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

Bug ID: 433387
   Summary: no tooltip in "save all" option displayed at the  top
of the modified image
   Product: gwenview
   Version: 20.12.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
When we edit a single image in gwenview the "save all" option displayed does
not show tooltip of what it does. This causes confusion that the original image
& modified image are saved when we click the button, but only the modified
image is saved. 
When we open & edit multiple files the "save all" option saves all the modified
images, but the tooltip is not shown.

EXPECTED RESULT
tooltip is shown for the "save all" option of what it does.

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.

[lattedock] [Bug 427081] New: Cannot go full screen on external display

2020-09-28 Thread Mohammed Shoaib

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

Bug ID: 427081
   Summary: Cannot go full screen on external display
   Product: lattedock
   Version: 0.9.11
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: shoaib98li...@gmail.com
  Target Milestone: ---

Created attachment 131992
  --> https://bugs.kde.org/attachment.cgi?id=131992&action=edit
If you notice carefully, there is an empty bar on the top of the browser.
That’s my wallpaper and the browser doesn’t fill up all the way to the top.

SUMMARY

I am connected to an external display. I updated Manjaro and now the screen
isn’t completely filled anymore. I’ve posted a screenshot in the attachments.

Any of the applications that I open, open exactly the same way as shown in the
picture. It wasn’t like this before, it’s after the update.

One interesting thing to note is on chromium when I press F11 to go full
screen, it actually does go full screen! I don’t see the empty bar when I go
full screen with chromium.

OBSERVED RESULT

An empty bar at the top of the external display.

EXPECTED RESULT

The application should go full-screen when maximized without the empty bar.

SOFTWARE/OS VERSIONS 
Kernel: 5.7.19-2
CPU: Intel Core i7 9th Gen
GPU Driver: GTX 1660 Ti

ADDITIONAL INFORMATION

Please find the output of xrandr -q below:

```bash
Screen 0: minimum 8 x 8, current 3839 x 1200, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1200+1919+0 (normal left inverted right x axis y axis)
518mm x 324mm
   1920x1200 59.95*+
   1920x1080 60.00  
   1680x1050 59.95  
   1600x900  60.00  
   1440x900  59.89  
   1280x1024 60.02  
   1280x800  59.81  
   1280x720  60.00  
   1024x768  60.00  
   800x600   60.3256.25  
   640x480   59.94  
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 382mm x 215mm
   1920x1080144.03*+  60.0260.0159.9759.9659.93  
   1680x1050 59.9559.88  
   1400x1050 74.7659.98  
   1600x900  59.9959.9459.9559.82  
   1280x1024 85.0275.0260.02  
   1400x900  59.9659.88  
   1280x960  85.0060.00  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1280x800  59.9959.9759.8159.91  
   1152x864  75.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  85.0075.0560.0485.0075.0370.0760.00  
   1024x768i 86.96  
   960x720   85.0075.0060.00  
   928x696   75.0060.05  
   896x672   75.0560.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   832x624   74.55  
   960x540   59.9659.9959.6359.82  
   800x600   85.0075.0070.0065.0060.0085.1472.19   
75.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   700x525   74.7659.98  
   800x450   59.9559.82  
   640x512   85.0275.0260.02  
   700x450   59.9659.88  
   640x480   85.0960.0085.0172.8175.0059.94  
   720x405   59.5158.99  
   720x400   85.04  
   684x384   59.8859.85  
   640x400   59.8859.9885.08  
   576x432   75.00  
   640x360   59.8659.8359.8459.32  
   640x350   85.08  
   512x384   85.0075.0370.0760.00  
   512x384i  87.06  
   512x288   60.0059.92  
   416x312   74.66  
   480x270   59.6359.82  
   400x300   85.2772.1975.1260.3256.34  
   432x243   59.9259.57  
   320x240   85.1872.8175.0060.05  
   360x202   59.5159.13  
   360x200   85.04  
   320x200   85.27  
   320x180   59.8459.32  
   320x175   85.27  
  1680x1050 (0x1ea) 146.250MHz -HSync +VSync
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz
  1280x1024 (0x1f4) 108.000MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
  1280x800 (0x1ff) 83.500MHz -HSync +VSync
h: width  1280 start 1352 end 1480 total 1680 skew0 clock  49.70KHz
v: height  800 start  803 end  809 total  831   clock  59.81Hz
  1024x768 (0x20c) 65.000MHz -HSync -VSync
h: width  1024 start 1048 end 1184 total 1344 skew0 clock  48.36KHz
v: height  768 start  771 end  777 total  806   clock  60.00Hz
  800x600 (0x228) 40.000MHz +HSync +VSync

[partitionmanager] [Bug 440146] New: Show unusable disk space reserved for reserved blocks, inode blocks

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

Bug ID: 440146
   Summary: Show unusable disk space reserved for reserved blocks,
inode blocks
   Product: partitionmanager
   Version: 21.04.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Created attachment 140248
  --> https://bugs.kde.org/attachment.cgi?id=140248&action=edit
Partition properties

SUMMARY
Show unusable disk space reserved for reserved blocks, inode blocks in
partition properties window of KDE Partition Manager for applicable filesystems
like ext4 etc.

On my PC for /dev/sda2 ext4 partition of 867.39 GiB, the reserved block count
is "11368998*4096 bytes= 46567415808 bytes= 43.3693 gibibytes", inode count is
"56852480*256 bytes=14554234880 bytes= 13.5547 gibibytes" which is lot of disk
space.

If above unusable disk space is shown in properties of a specific partition,
then users can know where the disk space is utilized & can atleast modify the
reserved block count, also when reinstalling the OS. New users can find this
feature helpful.

Also the partition properties of /dev/sda2 in KDE Partition Manager shows
available disk space as 68.46 GiB, which includes reserved block usage etc, but
actual usable free disk space is 10.4 GiB. Please see the attached screenshot.
I am not sure everything above is correct.

EXPECTED RESULT
Show disk space utilized by Reserved blocks, Inode blocks, Journal blocks etc.
or show it as filesystem reserved disk space in partition properties of KDE
Partition Manager.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

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

[partitionmanager] [Bug 440146] Show unusable disk space reserved for reserved blocks, inode blocks

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

--- Comment #1 from Mohammed Sameer  ---
output of tune2fs -l /dev/sda2:

tune2fs 1.45.5 (07-Jan-2020)
Filesystem volume name:   
Last mounted on:  /
Filesystem UUID:  f8e66549-c5db-4c42-b729-15601980172f
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype
needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink
extra_isize metadata_csum
Filesystem flags: signed_directory_hash 
Default mount options:user_xattr acl
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  56852480
Block count:  227379968
Reserved block count: 11368998
Free blocks:  14115771
Free inodes:  55628719
First block:  0
Block size:   4096
Fragment size:4096
Group descriptor size:64
Reserved GDT blocks:  1024
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
Flex block group size:16
Filesystem created:   Sun Oct 21 12:57:56 2018
Last mount time:  Thu Jul 22 13:35:57 2021
Last write time:  Thu Jul 22 19:05:49 2021
Mount count:  1503
Maximum mount count:  -1
Last checked: Sun Oct 21 12:57:56 2018
Check interval:   0 ()
Lifetime writes:  3144 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 32
Desired extra isize:  32
Journal inode:8
First orphan inode:   27264217
Default directory hash:   half_md4
Directory Hash Seed:  ab9a972f-9846-415b-8578-388e3a3a6ee5
Journal backup:   inode blocks
Checksum type:crc32c
Checksum: 0xfae01655

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

[filelight] [Bug 440151] New: Display unusable disk space reserved for reserved blocks, inode blocks

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

Bug ID: 440151
   Summary: Display unusable disk space reserved for reserved
blocks, inode blocks
   Product: filelight
   Version: 21.04.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Created attachment 140252
  --> https://bugs.kde.org/attachment.cgi?id=140252&action=edit
Initial view

SUMMARY
Display unusable disk space reserved for reserved blocks, inode blocks etc in
"Initial view" of filelight app for applicable filesystems like ext4 etc.

On my PC for /dev/sda2 ext4 partition of 867.39 GiB, the reserved block count
is "11368998*4096 bytes= 46567415808 bytes= 43.3693 gibibytes", inode count is
"56852480*256 bytes=14554234880 bytes= 13.5547 gibibytes" which is lot of disk
space.

If above unusable disk space is shown in filelight app, then users can know
where the disk space is utilized & can atleast modify the reserved block count,
also when reinstalling the OS. New users can find this feature helpful.

Also for /dev/sda2 mounted at "/", In "Initial view" filelight displays used
disk space as 842.3 GiB including reserved blocks etc, but in "Concentric rings
view" actual used disk space is 794.5 GiB. Please see the attached screenshots.

EXPECTED RESULT
Display disk space utilized by Reserved blocks, Inode blocks, Journal blocks
etc. or show it as filesystem reserved disk space in Initial view of filelight
app.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[filelight] [Bug 440151] Display unusable disk space reserved for reserved blocks, inode blocks

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

--- Comment #1 from Mohammed Sameer  ---
Created attachment 140253
  --> https://bugs.kde.org/attachment.cgi?id=140253&action=edit
Concentric rings view

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

[filelight] [Bug 440151] Display unusable disk space reserved for reserved blocks, inode blocks

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

--- Comment #2 from Mohammed Sameer  ---
output of tune2fs -l /dev/sda2:

tune2fs 1.45.5 (07-Jan-2020)
Filesystem volume name:   
Last mounted on:  /
Filesystem UUID:  f8e66549-c5db-4c42-b729-15601980172f
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype
needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink
extra_isize metadata_csum
Filesystem flags: signed_directory_hash 
Default mount options:user_xattr acl
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  56852480
Block count:  227379968
Reserved block count: 11368998
Free blocks:  14115771
Free inodes:  55628719
First block:  0
Block size:   4096
Fragment size:4096
Group descriptor size:64
Reserved GDT blocks:  1024
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
Flex block group size:16
Filesystem created:   Sun Oct 21 12:57:56 2018
Last mount time:  Thu Jul 22 13:35:57 2021
Last write time:  Thu Jul 22 19:05:49 2021
Mount count:  1503
Maximum mount count:  -1
Last checked: Sun Oct 21 12:57:56 2018
Check interval:   0 ()
Lifetime writes:  3144 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 32
Desired extra isize:  32
Journal inode:8
First orphan inode:   27264217
Default directory hash:   half_md4
Directory Hash Seed:  ab9a972f-9846-415b-8578-388e3a3a6ee5
Journal backup:   inode blocks
Checksum type:crc32c
Checksum: 0xfae01655

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

[filelight] [Bug 440152] New: Incorrect total size of a partition shown in Initial view of filelight app

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

Bug ID: 440152
   Summary: Incorrect total size of a partition shown in Initial
view of filelight app
   Product: filelight
   Version: 21.04.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Created attachment 140254
  --> https://bugs.kde.org/attachment.cgi?id=140254&action=edit
Initial view

SUMMARY
Incorrect total size of a partition is shown in Initial view of filelight app.
My PC has /dev/sda2 partition of 867.39 GiB, but in Initial view of filelight
app total size is shown as 852.8 GiB which is 14.59 GiB less. Please see the
attached screenshot.

output of lsblk:

sda  8:00 931.5G  0 disk 
├─sda1   8:10   129M  0 part /boot/efi
├─sda2   8:20 867.4G  0 part /
├─sda3   8:3016M  0 part 
└─sda4   8:4064G  0 part

EXPECTED RESULT
Correct size of /dev/sda2 partition of 867.39 GiB is shown instead of 852.8 GiB
in Initial view of filelight app.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

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

[Bluedevil] [Bug 432601] Inconsistent header border (separator) in Bluetooth applet when enabled.

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

--- Comment #7 from Mohammed Sameer  ---
I cannot reproduce this issue.

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

[frameworks-plasma] [Bug 433227] PC3 tooltip corner radius is not large enough

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

--- Comment #7 from Mohammed Sameer  ---
I cannot reproduce this issue.

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

[okular] [Bug 440173] New: Zoom out button not greyed out when PDF document is opened

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

Bug ID: 440173
   Summary: Zoom out button not greyed out when PDF document is
opened
   Product: okular
   Version: 21.04.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Created attachment 140271
  --> https://bugs.kde.org/attachment.cgi?id=140271&action=edit
okular video

SUMMARY
Zoom out button not greyed out when PDF document is opened when reaching the
maximum zoom out percentage(12%). Please see the attached video.

STEPS TO REPRODUCE
1. open a PDF file in okular
2. click zoom out button until the content is not zooming out
3. 

OBSERVED RESULT
Zoom out button is not greyed out when reaching maximum zoom out percentage.

EXPECTED RESULT
Zoom out button is greyed out when reaching maximum zoom out percentage.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[ark] [Bug 440174] New: Zoom out/in button not greyed out when opening a image in archive

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

Bug ID: 440174
   Summary: Zoom out/in button not greyed out when opening a image
in archive
   Product: ark
   Version: 21.04.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: glifwen...@gmail.com
CC: aa...@kde.org, rthoms...@gmail.com
  Target Milestone: ---

Created attachment 140272
  --> https://bugs.kde.org/attachment.cgi?id=140272&action=edit
ark video

SUMMARY
Zoom out, zoom in buttons not greyed out when opening a image in archive, when
reaching maximum zoom out, zoom in percentage of an image. Please see the
attached video.

STEPS TO REPRODUCE
1. open an archive with image in it
2. click zoom in button until maximum zoom in percentage is reached.
3. click zoom out button until maximum zoom out percentage is reached i.e until
the content is not zoomed out.

OBSERVED RESULT
Zoom in/out buttons are not greyed out when image reaching maximum percentage
of zoom in/out.

EXPECTED RESULT
Zoom in/out buttons are greyed out when image reaching maximum percentage of
zoom in/out.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 440409] New: Show a message asking to synchronize settings in sddm after change

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

Bug ID: 440409
   Summary: Show a message asking to synchronize settings in sddm
after change
   Product: systemsettings
   Version: 5.22.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_cursortheme
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
Show a message asking to synchronize settings in sddm after changing cursor
theme to get a consistent experience.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
A message is shown asking to synchronize settings in sddm after changing cursor
theme.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 440410] New: Show a message asking to synchronize settings in sddm after change

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

Bug ID: 440410
   Summary: Show a message asking to synchronize settings in sddm
after change
   Product: systemsettings
   Version: 5.22.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_fonts
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
Show a message asking to synchronize settings in sddm(Login Screen) after
changing font settings to get consistent experience.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
A message is shown asking to synchronize settings in sddm(Login Screen) after
changing font settings.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 440411] New: Show a message asking to synchronize settings in sddm after change

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

Bug ID: 440411
   Summary: Show a message asking to synchronize settings in sddm
after change
   Product: systemsettings
   Version: 5.22.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_touchpad
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
Show a message asking to synchronize settings in sddm(Login Screen) after
changing touchpad settings like "pointer acceleration" to get consistent
experience.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
A message is shown asking to synchronize settings in sddm(Login Screen) after
changing touchpad settings.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 440423] New: Show a "Connected" text in bluetooth applet for a connected device

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

Bug ID: 440423
   Summary: Show a "Connected" text in bluetooth applet for a
connected device
   Product: plasmashell
   Version: 5.22.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Created attachment 140409
  --> https://bugs.kde.org/attachment.cgi?id=140409&action=edit
Bluetooth applet

SUMMARY
In bluetooth applet of system tray when a bluetooth device is connected, no
text is shown whether it is connected other than disconnect button and bold
device name shown with separator.
If "Connected" text is shown near the bluetooth device like Networks applet it
would be clear to users. Please see the attached screenshots.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
A "Connected" text shown in bluetooth applet for a connected device.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 440423] Show a "Connected" text in bluetooth applet for a connected device

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

--- Comment #1 from Mohammed Sameer  ---
Created attachment 140410
  --> https://bugs.kde.org/attachment.cgi?id=140410&action=edit
Networks applet

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

[plasma-systemmonitor] [Bug 438847] New: Show total memory by default in "History" view

2021-06-18 Thread Mohammed Sameer

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

Bug ID: 438847
   Summary: Show total memory by default in "History" view
   Product: plasma-systemmonitor
   Version: 5.22.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 139466
  --> https://bugs.kde.org/attachment.cgi?id=139466&action=edit
Ksysguard_History_View

SUMMARY
Show total physical & swap memory by default in "History" view of System
Monitor. Most users check their Total RAM, swap memory in system monitor,
showing total memory by default is useful.

Also old ksysguard shows total memory like "Memory: 1.4GiB of 3.8GiB" in
history view, please see the attached screenshot.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasma-systemmonitor] [Bug 438848] New: Show overall CPU usage in "History" view

2021-06-18 Thread Mohammed Sameer

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

Bug ID: 438848
   Summary: Show overall CPU usage in "History" view
   Product: plasma-systemmonitor
   Version: 5.22.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 139467
  --> https://bugs.kde.org/attachment.cgi?id=139467&action=edit
Ksysguard_History_View

SUMMARY
Show overall CPU usage in "History" view of System Monitor. In new System
Monitor, if a PC has 4 cores, then usage of individual cores is shown per 100%.
It would be useful if overall utilization of all cores is shown per 100%.

Also old ksysguard shows overall usage of all cores/CPUs like "CPU: 10%" in
history view, please see the attached screenshot.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasma-systemmonitor] [Bug 438849] New: Show total number of processes in "Processes" view

2021-06-18 Thread Mohammed Sameer

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

Bug ID: 438849
   Summary: Show total number of processes in "Processes" view
   Product: plasma-systemmonitor
   Version: 5.22.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 139468
  --> https://bugs.kde.org/attachment.cgi?id=139468&action=edit
Ksysguard_Process_View

SUMMARY
Show total number of processes in "Processes" view of System Monitor. It would
be very useful.

Also old ksysguard shows number of processes like "200 processes" in processes
view, please see the attached screenshot.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasma-systemmonitor] [Bug 438848] Show overall CPU usage in "History" view

2021-06-19 Thread Mohammed Sameer

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

--- Comment #2 from Mohammed Sameer  ---
> It would be useful if overall utilization of all cores is shown per 100%.

I didn't describe it clearly.

It would be informative, if overall utilization of all cores is shown in
addition to 400% graphs, somewhere in history page of system monitor like
statusbar etc.

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

[ktorrent] [Bug 438938] New: Tooltip not shown for elided text in some columns of ktorrent

2021-06-20 Thread Mohammed Sameer

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

Bug ID: 438938
   Summary: Tooltip not shown for elided text in some columns of
ktorrent
   Product: ktorrent
   Version: 21.04.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Created attachment 139533
  --> https://bugs.kde.org/attachment.cgi?id=139533&action=edit
ktorrent video

SUMMARY
Tooltip not shown for displayed torrent columns "Location" & "Added", where
text is elided in ktorrent, whereas tooltip is shown for name column. Please
see the attached video.

OBSERVED RESULT
Tooltip not shown for elided text in location, added columns

EXPECTED RESULT
Tooltip shown for elided text in location, added columns

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[plasma-systemmonitor] [Bug 438849] Show total number of processes in "Processes" view

2021-07-02 Thread Mohammed Sameer

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

--- Comment #2 from Mohammed Sameer  ---
I don't know exactly, but I think it would be informative to know how many user
processes are running, how many total processes are running, how many root
processes are running in a system etc.

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

[filelight] [Bug 434532] "Up" button should be greyed out when in root or top directory

2021-05-05 Thread Mohammed Sameer

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

--- Comment #6 from Mohammed Sameer  ---
Hi,
I am not sure if this is correct, I think I have mistakenly reported that the
bug is "Up" button is not greyed out when in root directory.
But I think the "Up" button was meant for going back to "Initial view"(please
see attached screenshot) & it is not working, because if we go to the "pie
chart view", currently there is no way to go back to the "Initial view" other
than reopening the filelight app.
Could this be fixed here or submit a new bug report?

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

[filelight] [Bug 434532] "Up" button should be greyed out when in root or top directory

2021-05-05 Thread Mohammed Sameer

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

--- Comment #7 from Mohammed Sameer  ---
Created attachment 138164
  --> https://bugs.kde.org/attachment.cgi?id=138164&action=edit
Initial view

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

[Discover] [Bug 434470] No easy way to get the initial view of the sidebar pages like "Update" section

2021-03-31 Thread Mohammed Sameer

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

--- Comment #8 from Mohammed Sameer  ---
I attached a video showing the problem.
When I install updates, I compare the installed version to available version of
all packages. If I want to know about "Fuzzy Clock" package I will click "More
Information" button, then the info is displayed.
After that if I want to scroll back to other packages below "Fuzzy Clock", I
cannot see the installed version of packages and available version is also not
shown fully.
To get the full details I have to go to "About" section & come back to "Update"
page & scroll back to "Fuzzy Clock" package to start comparing the package
versions, which is not easy. It is not a big issue but it is inconvenient.

Also when I restore the window when in info page, I can click the back button &
I can see only the available version string fully.

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

[Discover] [Bug 434470] No easy way to get the initial view of the sidebar pages like "Update" section

2021-03-31 Thread Mohammed Sameer

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

--- Comment #9 from Mohammed Sameer  ---
Created attachment 137199
  --> https://bugs.kde.org/attachment.cgi?id=137199&action=edit
discover video

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

[Discover] [Bug 434470] No easy way to get the initial view of the sidebar pages like "Update" section

2021-04-02 Thread Mohammed Sameer

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

--- Comment #11 from Mohammed Sameer  ---
> The previous one is still visible and still interactive.

Yes, the previous view is visible, but the version of packages
"4:5.21.3-0xneon+20.04+focal+build22 ->
4:5.21.3-0xneon+20.04+focal+release+build23" is shown as
"...on+20.04+focal+release+build23"

The full version of above text is not shown when the second view appears.

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

[systemsettings] [Bug 479198] New: I was trying to install lxqt desktop in Linux Mint after installing KDE and Using it as a main desktop. but after configuring the lxqt desktop, KDE got disrupted and

2023-12-30 Thread Mohammed Wael

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

Bug ID: 479198
Summary: I was trying to install lxqt desktop in Linux Mint
after installing KDE and Using it as a main desktop.
but after configuring the lxqt desktop, KDE got
disrupted and the desktop is not healthy. I want to
know how to reset the desktop or reinstall KDE. ple
Classification: Applications
Product: systemsettings
Version: 5.24.7
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: mohammedwaelelshiek...@gmail.com
Target Milestone: ---

Created attachment 164560
--> https://bugs.kde.org/attachment.cgi?id=164560&action=edit
KDE desktop settings app (it is light inspite i am using the dark breeze theme)

SUMMARY
Hi there.
I was trying to install lxqt desktop in Linux Mint after installing KDE and
Using it as a main desktop. but after configuring the lxqt desktop, KDE got
disrupted and the desktop is not healthy. I want to know how to reset the
desktop or reinstall KDE. please help me!
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.
2.
3.

OBSERVED RESULT

EXPECTED RESULT

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.

[systemsettings] [Bug 479312] New: The Application launcher find tool does not work. It only accepts the first letter entered by the keyboard, but then starts to crash and refuse any other action.

2024-01-02 Thread Mohammed Wael

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

Bug ID: 479312
   Summary: The Application launcher find tool does not work. It
only accepts the first letter entered by the keyboard,
but then starts to crash and refuse any other action.
Classification: Applications
   Product: systemsettings
   Version: 5.27.10
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mohammedwaelelshiek...@gmail.com
  Target Milestone: ---

SUMMARY
***
The Application launcher find tool does not work. It only accepts the first
letter entered by the keyboard, but then starts to crash and refuse any other
action.
***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Mint 21.2
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 479312] The Application launcher find tool does not work. It only accepts the first letter entered by the keyboard, but then starts to crash and refuse any other action.

2024-01-02 Thread Mohammed Wael

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

--- Comment #2 from Mohammed Wael  ---
(In reply to fanzhuyifan from comment #1)
> Hi, thank you for your bug report. Unfortunately I cannot reproduce these.
> Could you share more detailed steps to reproduce this?
> 
> What are the letters you entered?
> 
> When you go to settings-search-plasma search, which plugins are enabled? Can
> you try disabling the plugins one by one and see which one triggers the bug?
> 
> Thanks!

Thanks for your help. The bug appears when I'm entering any letters, it is not
limited to a specific group of letters or numbers. Also, it doesn't accept
deleting the first letter that has accepted or any other action such as
selecting the text. And disabling all plugins did not help resolve the problem.
It seems that there is some infinity loop that the search bar activates.

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

[plasma-systemmonitor] [Bug 441093] Feature: average queue size sensor for disks

2023-08-24 Thread Mohammed Khoory

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

Mohammed Khoory  changed:

   What|Removed |Added

 CC||the.9a3e...@gmail.com

--- Comment #1 from Mohammed Khoory  ---
I would like to second this. I've recently moved to Plasma from Windows and
this is a very useful metric to have particularly for magnetic disks.

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

[filelight] [Bug 438107] New: No way to go from 'concentric rings' view to Initial view.

2021-06-05 Thread Mohammed Sameer

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

Bug ID: 438107
   Summary: No way to go from 'concentric rings' view to Initial
view.
   Product: filelight
   Version: 21.04.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

Created attachment 139015
  --> https://bugs.kde.org/attachment.cgi?id=139015&action=edit
Initial view

SUMMARY
In filelight app, if we go to the "pie chart view" i.e(concentric rings view),
currently there is no way to go back to the "Initial view" other than reopening
the filelight app.
Please see the attached screenshot.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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.

[filelight] [Bug 434532] "Up" button should be greyed out when in root or top directory

2021-06-05 Thread Mohammed Sameer

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

--- Comment #9 from Mohammed Sameer  ---
Hi, submitted new bug report here:

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

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

[kdeplasma-addons] [Bug 434312] New: Weather widget does not show difference when two locations have same names.

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

Bug ID: 434312
   Summary: Weather widget does not show difference when two
locations have same names.
   Product: kdeplasma-addons
   Version: 5.21.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Weather
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
  Target Milestone: ---

SUMMARY
Weather widgets does not show difference, when two weather widgets are added to
the desktop with same location names, but are actually two different locations.
Please see the screenshots attached.

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

[kdeplasma-addons] [Bug 434312] Weather widget does not show difference when two locations have same names.

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

--- Comment #1 from Mohammed Sameer  ---
Created attachment 136600
  --> https://bugs.kde.org/attachment.cgi?id=136600&action=edit
Two locations

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

[kdeplasma-addons] [Bug 434312] Weather widget does not show difference when two locations have same names.

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

--- Comment #2 from Mohammed Sameer  ---
Created attachment 136601
  --> https://bugs.kde.org/attachment.cgi?id=136601&action=edit
Different locations with same names

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

[kscreenlocker] [Bug 434321] New: Lock screen doesn't clear the password entered, when left idle.

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

Bug ID: 434321
   Summary: Lock screen doesn't clear the password entered, when
left idle.
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
Lock screen doesn't clear the entered password, when left idle without pressing
"enter" key to login.

STEPS TO REPRODUCE
1. lock the screen
2. enter password
3. leave the computer idle for few minutes

OBSERVED RESULT
The entered password is still present.

EXPECTED RESULT
The entered password is cleared, after leaving the computer idle for some time.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-66-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION
The issue is also present in SDDM login screen.

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

[Discover] [Bug 434449] New: Discover crashed when closed the app on wayland session.

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

Bug ID: 434449
   Summary: Discover crashed when closed the app on wayland
session.
   Product: Discover
   Version: 5.21.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: glifwen...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
Discover crashed when closed the app on wayland session.

I opened Discover app & browsed "settings section etc", then the app is not
responding with message "Discover is not responding".
Then I closed the app and opened it again, then again browsed the settings
section, featured applications etc. After that when I closed the Discover
application using close button on top right corner then a notification came
that the discover app is crashed.

SYSTEM INFORMATION
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-67-generic
OS Type: 64-bit
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

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

[Discover] [Bug 434449] Discover crashed when closed the app on wayland session.

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

--- Comment #1 from Mohammed Sameer  ---
BACKTRACE
Application: Discover (plasma-discover), signal: Segmentation fault

[New LWP 4419]
[New LWP 4420]
[New LWP 4421]
[New LWP 4422]
[New LWP 4423]
[New LWP 4424]
[New LWP 4426]
[New LWP 4427]
[New LWP 4430]
[New LWP 4431]
[New LWP 4435]
[New LWP 4436]
[New LWP 4489]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x566f1cd0) at ../sysdeps/nptl/futex-internal.h:183
[Current thread is 1 (Thread 0x7f17c164d980 (LWP 4417))]

Thread 14 (Thread 0x7f1776ffd700 (LWP 4489)):
#0  0x7f17c5c18aff in __GI___poll (fds=0x7f17b8067f90, nfds=1, timeout=312)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f17c44dc36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f17c44dc4a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f17c61e3ffb in QEventDispatcherGlib::processEvents
(this=0x7f173802f0c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f17c61881eb in QEventLoop::exec (this=this@entry=0x7f1776ffcbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f17c5fa2a52 in QThread::exec (this=this@entry=0x56111302aa80) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f17c7cfe38a in QQuickPixmapReader::run (this=0x56111302aa80) at
util/qquickpixmapcache.cpp:1024
#7  0x7f17c5fa3bec in QThreadPrivate::start (arg=0x56111302aa80) at
thread/qthread_unix.cpp:329
#8  0x7f17c4f38609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f17c5c25293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f1762c6b700 (LWP 4436)):
#0  0x7f17c4529508 in g_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f17c44dbd30 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f17c44dc312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f17c44dc4a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f17c61e3ffb in QEventDispatcherGlib::processEvents
(this=0x7f1744000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f17c61881eb in QEventLoop::exec (this=this@entry=0x7f1762c6ac20,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#6  0x7f17c5fa2a52 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f17c5fa3bec in QThreadPrivate::start (arg=0x56b060a0) at
thread/qthread_unix.cpp:329
#8  0x7f17c4f38609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f17c5c25293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f1774f10700 (LWP 4435)):
[KCrash Handler]
#4  0x7f17bf4c541f in update_buffers
(dri2_surf=dri2_surf@entry=0x7f17680041a0) at
../src/egl/drivers/dri2/platform_wayland.c:674
#5  0x7f17bf4c5828 in image_get_buffers (driDrawable=,
format=, stamp=, loaderPrivate=0x7f17680041a0,
buffer_mask=, buffers=0x7f1774f0ec00) at
../src/egl/drivers/dri2/platform_wayland.c:809
#6  0x7f17bdbd9bb3 in dri_image_drawable_get_buffers
(statts_count=, statts=, images=,
drawable=) at ../src/gallium/frontends/dri/dri2.c:282
#7  dri2_allocate_textures (ctx=0x566f2a00, drawable=0x7f17680045f0,
statts=0x7f1768004d38, statts_count=2) at
../src/gallium/frontends/dri/dri2.c:415
#8  0x7f17bdbdbcf4 in dri_st_framebuffer_validate (stctx=,
stfbi=, statts=0x7f1768004d38, count=2, out=0x7f1774f0edb0) at
../src/gallium/frontends/dri/dri_drawable.c:82
#9  0x7f17bdbe800c in st_framebuffer_validate
(stfb=stfb@entry=0x7f1768004860, st=st@entry=0x567638a0) at
../src/mesa/state_tracker/st_manager.c:223
#10 0x7f17bdbe8650 in st_manager_validate_framebuffers (st=0x567638a0)
at ../src/mesa/state_tracker/st_manager.c:1185
#11 0x7f17bdc0c965 in st_validate_state (st=st@entry=0x567638a0,
pipeline=pipeline@entry=ST_PIPELINE_CLEAR) at
../src/mesa/state_tracker/st_atom.c:203
#12 0x7f17bdc11606 in st_Clear (ctx=0x56703500, mask=50) at
../src/mesa/state_tracker/st_cb_clear.c:442
#13 0x7f17c7d5e87a in QSGBatchRenderer::Renderer::renderBatches
(this=this@entry=0x7f176800d560) at
../../include/QtQuick/5.15.2/QtQuick/private/../../../../../src/quick/scenegraph/coreapi/qsgrenderer_p.h:131
#14 0x7f17c7d5ef9a in QSGBatchRenderer::Renderer::render (this=) at scenegraph/coreapi/qsgbatchrenderer.cpp:4363
#15 0x7f17c7d42b54 in QSGRenderer::renderScene (bindable=...,
this=0x7f176800d560) at scenegraph/coreapi/qsgrenderer.cpp:264
#16 QSGRenderer::renderScene (this=0x7f176800d560, bindable=...) at
scenegraph/coreapi/qsgrenderer.cpp:220
#17 0x7f17c7d43023 in QSGRenderer::renderScene (this=,
fboId=) at scenegraph/coreapi/qsgrenderer.cpp:212
#18 0x7f17c

[Discover] [Bug 434470] New: No easy way to get the initial view of the sidebar pages like "Update" section

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

Bug ID: 434470
   Summary: No easy way to get the initial view of the sidebar
pages like "Update" section
   Product: Discover
   Version: 5.21.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: glifwen...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
No easy way to get the initial view(single content pane) of the sidebar pages
like "Update", "Settings"  sections in dicover app.

STEPS TO REPRODUCE
1. open discover
2. go to Update or Settings section.
3. In Update section select an update & click more information (or) in Settings
section, select "Show contents" button in the flatpak source settings.

OBSERVED RESULT
There is no easy way to go back to the initial view of "Update" or "Settings"
sections, we have to open  other sections like "About" & then again open the
"Update" or "Settings" sections to get the initial view of the respective
sections.

EXPECTED RESULT
Easy way to get back to the initial view like back button etc.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-67-generic
OS Type: 64-bit
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[Discover] [Bug 434470] No easy way to get the initial view of the sidebar pages like "Update" section

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

--- Comment #1 from Mohammed Sameer  ---
Created attachment 136717
  --> https://bugs.kde.org/attachment.cgi?id=136717&action=edit
Initial view (single content pane)

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

[Discover] [Bug 434470] No easy way to get the initial view of the sidebar pages like "Update" section

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

--- Comment #2 from Mohammed Sameer  ---
Created attachment 136718
  --> https://bugs.kde.org/attachment.cgi?id=136718&action=edit
Multiple content panes

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

[Discover] [Bug 434471] New: No tooltip shown for close, cancel buttons in "Tasks" window when installing updates

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

Bug ID: 434471
   Summary: No tooltip shown for close, cancel buttons in "Tasks"
window when installing updates
   Product: Discover
   Version: 5.21.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: glifwen...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 136719
  --> https://bugs.kde.org/attachment.cgi?id=136719&action=edit
Tasks progress window

SUMMARY
No tooltip shown for close, cancel buttons in "Tasks" progress indicator
window, when installing updates in discover app.
Please see the screenshot.

ADDITIONAL INFORMATION
The window which opens when clicking "Show All Reviews" button in an app page,
also doesn't show tooltip for close button.

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

[plasma-systemmonitor] [Bug 434510] New: Plasma system monitor not showing graph for swap memory

2021-03-16 Thread Mohammed Sameer

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

Bug ID: 434510
   Summary: Plasma system monitor not showing graph for swap
memory
   Product: plasma-systemmonitor
   Version: 5.21.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: glifwen...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 136750
  --> https://bugs.kde.org/attachment.cgi?id=136750&action=edit
system monitor

SUMMARY
Plasma system monitor is not showing graph for "swap memory" in Memory graph,
in "History" section of sidebar.
Please see the attached screenshot.
STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-67-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[filelight] [Bug 431447] Tooltips: text is clipped

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

Mohammed Sameer  changed:

   What|Removed |Added

 CC||glifwen...@gmail.com

--- Comment #2 from Mohammed Sameer  ---
I can reproduce the issue.

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

[filelight] [Bug 431447] Tooltips: text is clipped

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

--- Comment #3 from Mohammed Sameer  ---
Created attachment 136769
  --> https://bugs.kde.org/attachment.cgi?id=136769&action=edit
image 1

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

[filelight] [Bug 431447] Tooltips: text is clipped

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

--- Comment #4 from Mohammed Sameer  ---
Created attachment 136770
  --> https://bugs.kde.org/attachment.cgi?id=136770&action=edit
image 2

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

[filelight] [Bug 434532] New: "Up" button should be greyed out when in root or top directory