[konqueror] [Bug 39923] Completely garbled display with text displayed on top of other text
https://bugs.kde.org/show_bug.cgi?id=39923 Krishna changed: What|Removed |Added CC||chaitanyakrishna119@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 229500] mmap with huge size fails under valgrind
https://bugs.kde.org/show_bug.cgi?id=229500 Krishna changed: What|Removed |Added CC||muppakrish...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 333051] mmap of huge pages fails due to incorrect alignment
https://bugs.kde.org/show_bug.cgi?id=333051 Krishna changed: What|Removed |Added CC||muppakrish...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374963] increase valgrind's load address to prevent mmap failure
https://bugs.kde.org/show_bug.cgi?id=374963 Krishna changed: What|Removed |Added CC||muppakrish...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] New: [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 Bug ID: 416682 Summary: [MIPS-Linux] mmap failed under valgrind Product: valgrind Version: 3.11.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: muppakrish...@gmail.com Target Milestone: --- Seen issue mmap failure issue when launching Embedded OS and error value 22 (EINVAL 22 Invalid argument) The same application is working fine if not running under valgrind. Based on analysis found the issue is with mmap and could see the following error from valgrind. Line 1446: ==828== Warning: set address range perms: large range [0x14b8, 0x2b19e000) (defined) Line 1452: ==828== Warning: set address range perms: large range [0x14b8, 0x2b19e000) (noaccess) Tried with both valgrind 3.11.0 and 3.15.0 but result is same. And from understating,tried with below patch to ignore MAP_FIXED but it didn't work. --- valgrind-3.15.0/coregrind/m_syswrap/syswrap-generic.c.keep 2020-01-24 12:29:43.935747920 +0530 +++ valgrind-3.15.0/coregrind/m_syswrap/syswrap-generic.c 2020-01-24 12:30:56.403747920 +0530 @@ -2320,7 +2320,7 @@ ML_(generic_PRE_sys_mmap) ( ThreadId tid /* Otherwise we're OK (so far). Install aspacem's choice of address, and let the mmap go through. */ sres = VG_(am_do_mmap_NO_NOTIFY)(advised, arg2, arg3, -arg4 | VKI_MAP_FIXED, +arg4, arg5, arg6); # if defined(VKI_MAP_32BIT) @@ -2346,7 +2346,7 @@ ML_(generic_PRE_sys_mmap) ( ThreadId tid } /* and try again with the kernel */ sres = VG_(am_do_mmap_NO_NOTIFY)(advised, arg2, arg3, - arg4 | VKI_MAP_FIXED, + arg4, arg5, arg6); } Please suggest me with possible solution to fix the issue. Target Environment details: OS: Embedded-Linux and MIPS Architecture Kernel: 3.3.8-3.9 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #2 from Krishna --- (In reply to Tom Hughes from comment #1) > If this is an embedded system do you actually have enough memory to use > valgrind on it - your program will use at least twice the normal amount of > memory when running under memcheck. > > If you do then are you linking your code to run at some specific address - > that is the sort of thing I can imagine you might do on an embedded system > and it can cause problems if it clashes with the address space layout > valgrind uses. > > At the end of the day there is some incompatibility between the mmap calls > you are trying to do and the memory layout your program has when running > under valgrind (which is different to when running normally) and you will > need to try and understand the nature of that difference in order to resolve > it - start by trying to gather information on exactly what mmap is failing. Thank you for the response -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682
Krishna changed:
What|Removed |Added
CC||muppakrish...@gmail.com
--- Comment #3 from Krishna ---
Created attachment 125712
--> https://bugs.kde.org/attachment.cgi?id=125712&action=edit
simple mmap testapp execution log
In further investigation, found the issue is with invalid offset under
valgrind.
And in high-level, During normal run mmap2 is getting executed where as mmap is
getting executed under valgrind.
Attached strace bootup logs for reference.
Normal Run:
open("/tmp/1.txt", O_RDWR|O_CREAT|O_TRUNC|O_LARGEFILE, 017754017774) = 3
mmap2(NULL, 157286400, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0xc020) =
0x6e196000
Valgrind Run:
open("/tmp/1.txt", O_RDWR|O_CREAT|O_TRUNC|O_LARGEFILE, 017662266754) = 3
mmap(0x498, 157286400, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_FIXED, 3,
0xc020) = 0x498
And it looks based on mapping for syscalls. if so where this can be configured
for mips_mmap2 in valgrind code.
SYSCALL_DEFINE6(mips_mmap, unsigned long, addr, unsigned long, len,
unsigned long, prot, unsigned long, flags, unsigned long,
fd, off_t, offset)
{
unsigned long result;
result = -EINVAL;
if (offset & ~PAGE_MASK)
goto out;
result = sys_mmap_pgoff(addr, len, prot, flags, fd, offset >>
PAGE_SHIFT);
out:
return result;
}
SYSCALL_DEFINE6(mips_mmap2, unsigned long, addr, unsigned long, len,
unsigned long, prot, unsigned long, flags, unsigned long, fd,
unsigned long, pgoff)
{
if (pgoff & (~PAGE_MASK >> 12))
return -EINVAL;
return sys_mmap_pgoff(addr, len, prot, flags, fd, pgoff >>
(PAGE_SHIFT-12));
}
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #6 from Krishna --- (In reply to Tom Hughes from comment #4) > In what way is the offset "invalid" and why does it matter whether mmap or > mmap2 is used? Are you trying to use some feature that only mmap2 supports? Sorry for delayed in my response. We have a problem with large offset which the offset can't find available in system memory space. And it is typically 2GB(2*1GB). And the offset range expected for 2nd segment from 0x9000_ to 0xCFFF_. I think yes, we are interested for mmap2 feature as we could some code manipulation with offset. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #7 from Krishna --- Created attachment 126420 --> https://bugs.kde.org/attachment.cgi?id=126420&action=edit Captured log with system call traces -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #8 from Krishna --- (In reply to Tom Hughes from comment #5) > So I can see that both offsets in the strace are the same which isn't what > we would expect if your application is calling mmap2 as it should manipulate > it differently before passing it to sys_mmap_pgoff. > > Are you able to capture this map with --trace-syscalls=yes so that we can > see what call valgrind is seeing from your application? PFA, for system call traces and help me to map the system call mmap2 for valgrind. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #10 from Krishna --- Created attachment 126722 --> https://bugs.kde.org/attachment.cgi?id=126722&action=edit mips mmap executable file -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #11 from Krishna --- (In reply to Petar Jovanovic from comment #9) > @Krishna > > Can you share some steps to reproduce this issue? > Can you come up with a small example, build it statically and upload the > binary somewhere? Thanks for your the interest on this issue.Please find attached mips arch executable file. pre-conditions: create an dummy text file in /tmp folder with 1.txt name Steps to reproduce: 1. Execute the file in mips platform and capture traces for strace -e trace=open,mmap,mmap2 2. Repeat the step:1 with valgrind option along with strace strace -e trace=open,mmap,mmap2 valgrind observations: We may not encounter with failure but could notice syscall mapping mmap to mmap2 under valgrind as explained. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682
--- Comment #13 from Krishna ---
(In reply to Petar Jovanovic from comment #12)
> (In reply to Krishna from comment #10)
> > Created attachment 126722 [details]
> > mips mmap executable file
>
> This is not statically linked program.
>
> $ ldd mips_mmap_exe
> libssp.so.0 => not found
> libgcc_s.so.1 => /lib/mipsel-linux-gnu/libgcc_s.so.1 (0x7725)
> libc.so.0 => not found
> libc.so.6 => /lib/mipsel-linux-gnu/libc.so.6 (0x770b)
> /lib/ld-uClibc.so.0 => /lib/ld.so.1 (0x772b)
>
> Can you share the source code of this example and what toolchain to use, how
> to build it, so I can reproduce the issue?
Hi Peter,
Please find the below source code built for shared executable.
Toolchain used: stbgcc-4.5.4-2.9.tar.bz
#include
#include
#include
#include
#include
#include
#include
#define BDBG_UINT64_ARG(x) (unsigned )((x)>>32), (unsigned )(x)
#define BDBG_UINT64_FMT "0x%x%08x"
int main()
{
void *addr;
unsigned length=157286400;
unsigned long long offset=0x0c020;
int fd=open("/tmp/1.txt", O_RDWR | O_CREAT | O_TRUNC);
addr = mmap(0, length, PROT_READ|PROT_WRITE, MAP_SHARED, fd, offset);
if (addr == MAP_FAILED)
{
printf("ERROR:mmap failed: offset " BDBG_UINT64_FMT ", size=%u,
errno=%d\n",
BDBG_UINT64_ARG(offset), (unsigned)length, errno);
addr = NULL;
}
else
{
printf("SUCCESS:mmap offset:" BDBG_UINT64_FMT " size:%u ->
%p\n",
BDBG_UINT64_ARG(offset), (unsigned)length, addr);
}
return 0;
}
Compile using mips-cc with mentioned options:
/stbgcc-4.5.4-2.9/bin//mipsel-linux-uclibc-gcc -o mmap_krish
mmap.c -finline-limit=300 -fPIC -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64
-fstack-protector-all -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -DBSTD_CPU_ENDIAN=BSTD_ENDIAN_LITTLE
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 482245] Sometimes cursor disappears on lock screen after waking system up from sleep
https://bugs.kde.org/show_bug.cgi?id=482245 Krishna changed: What|Removed |Added CC||krishna.ratako...@gmail.com --- Comment #22 from Krishna --- In my case, this only happened after the computer wakes up from sleep after I use the sleep button from the start menu. It did not happen when the computer wakes up from sleep after I use the sleep button on the lock screen. I was able to resolve it by switching the cursor theme in the desktop settings to "Volantes light cursors". I tried variants of breeze and qozir which all had the same problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465484] System Settings Crashes While Importing A OpenVPN Config
https://bugs.kde.org/show_bug.cgi?id=465484 Pulkit Krishna changed: What|Removed |Added CC||pulkitkrishn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465484] System Settings Crashes While Importing A OpenVPN Config
https://bugs.kde.org/show_bug.cgi?id=465484 --- Comment #2 from Pulkit Krishna --- Created attachment 156295 --> https://bugs.kde.org/attachment.cgi?id=156295&action=edit New crash information added by DrKonqi systemsettings (5.27.0) using Qt 5.15.8 When I try to import an OpenVPN config, the settings app crash. The OpenVPN config is from Proton VPN. -- Backtrace (Reduced): #4 0x7f972fd93dee in OpenVpnUiPlugin::importConnectionSettings(QString const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/network/vpn/plasmanetworkmanagement_openvpnui.so [...] #7 0x7fd7960773f5 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 [...] #10 0x7fd795fac84a in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 [...] #13 0x7fd795f5eaee in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fd7960eb3a5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466537] Update process on launch can slow down launch or freeze the app
https://bugs.kde.org/show_bug.cgi?id=466537 Pulkit Krishna changed: What|Removed |Added CC||pulkitkrishn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466539] Slowing down or freezing immediately when showing the page
https://bugs.kde.org/show_bug.cgi?id=466539 Pulkit Krishna changed: What|Removed |Added CC||pulkitkrishn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462361] Fedora Kionite: updating all installed apps after installing them
https://bugs.kde.org/show_bug.cgi?id=462361 Pulkit Krishna changed: What|Removed |Added CC||pulkitkrishn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443071] Show package changelog
https://bugs.kde.org/show_bug.cgi?id=443071 Pulkit Krishna changed: What|Removed |Added CC||pulkitkrishn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amor] [Bug 440620] New: After clicking on i3 portal and entering the credentials, it is redirecting to institute page rather than the portal
https://bugs.kde.org/show_bug.cgi?id=440620 Bug ID: 440620 Summary: After clicking on i3 portal and entering the credentials, it is redirecting to institute page rather than the portal Product: amor Version: 2.4 Platform: Other URL: https://learn.senecacollege.ca/ultra/institution-page OS: Other Status: REPORTED Keywords: accessibility Severity: normal Priority: NOR Component: general Assignee: bhargavi.krishna...@gmail.com Reporter: bkravi-ku...@myseneca.ca Target Milestone: --- Created attachment 140530 --> https://bugs.kde.org/attachment.cgi?id=140530&action=edit Bug SUMMARY STEPS TO REPRODUCE 1. Click on i3 Portal 2. Enter Email ID and Password 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.
[plasmashell] [Bug 496295] Change of display brightness by scroll not working after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=496295 --- Comment #6 from Murali Krishna --- Slider for changing brightness exists and works on system boot. strangely, the brightness slider dissappears once the screen goes to sleep on inactivity and resumes after a key press on keyboard. On restarting the PC, the brightness slider appears again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496295] Change of display brightness by scroll not working after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=496295 --- Comment #5 from Murali Krishna --- (In reply to Nate Graham from comment #4) >Slider for changing brightness exists and works on system boot. strangely, the >brightness slider dissappears once the screen goes to sleep on inactivity and >resumes after a key press on keyboard. On restarting the PC, the brightness >slider appears again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496295] New: Change of display brightness by scroll not working after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=496295 Bug ID: 496295 Summary: Change of display brightness by scroll not working after resume from sleep Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brightness and Color Assignee: plasma-b...@kde.org Reporter: husband.of.de...@gmail.com CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY Scrolling mouse wheel on "Brightness and color" icon in panel changes display brightness on Samsung LED monitor connected on HDMI. But once the system goes to sleep and wakes, the same doesn't work. scrolling the mouse wheel does nothing. The same works after system restart. My PC is a MSI Cubi mini PC with Intel N100 processor, using Stock OpenSuse Tumbleweed OS. Display is a Samsung 24 Inch LED monitor connected on HDMI. STEPS TO REPRODUCE 1. Scrolling the wheel on Brightness and color indicator in notification panel changes display brightness on system boot. 2. Put the PC to sleep on inactivity. 3. wake up the pc and sign-in. the brightness won't change on mouse scroll till next PC boot. OBSERVED RESULT Brightness not changing on wake from sleep EXPECTED RESULT Brightness should change on mouse scrool SOFTWARE/OS VERSIONS Linux: OpenSuse Tumbleweed latest build. Linux/KDE Plasma: OpenSuse Tumbleweed 20241113 (Tumbleweed) KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496295] Change of display brightness by scroll not working after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=496295 Murali Krishna changed: What|Removed |Added CC||husband.of.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496295] Change of display brightness by scroll not working after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=496295 --- Comment #2 from Murali Krishna --- Samsung Essentials S3 LED Monitor (LS24C330GAWXXL) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496295] Change of display brightness by scroll not working after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=496295 --- Comment #3 from Murali Krishna --- (In reply to Nate Graham from comment #1) > Which Samsung monitor specifically? An Odyssey Neo G5 or G9? Samsung Essentials S3 LED Monitor (LS24C330GAWXXL) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496295] Change of display brightness by scroll not working after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=496295 Murali Krishna changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Murali Krishna --- Slider for changing brightness exists and works on system boot. strangely, the brightness slider dissappears once the screen goes to sleep on inactivity and resumes after a key press on keyboard. On restarting the PC, the brightness slider appears again. Its has been observed that the issue exists while using PC in X11 whereas the problem doesn't exist in the wayland session. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 429140] New: Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1
https://bugs.kde.org/show_bug.cgi?id=429140 Bug ID: 429140 Summary: Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1 Product: lattedock Version: git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: m...@kayg.org Target Milestone: --- SUMMARY When unset, Latte Dock works as expected but when the variable is set, Latte Dock does not respond to either left or right clicks. STEPS TO REPRODUCE 1. Create ~/.config/autostart-scripts/scaling.sh with the following content: #!/bin/sh export PLASMA_USE_QT_SCALING=1 2. Make it executable and create a symlink at ~/.config/plasma-workspace/env/ 3. Logout and log back in OBSERVED RESULT Latte Dock stops responding to clicks / none of the applets or the entire UI is clickable. EXPECTED RESULT Latte Dock working normally. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.8-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 31.2 GiB of RAM Graphics Processor: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 406495] New: File type option does not work / buggy in some cases
https://bugs.kde.org/show_bug.cgi?id=406495 Bug ID: 406495 Summary: File type option does not work / buggy in some cases Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: vkmaheshb...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 119394 --> https://bugs.kde.org/attachment.cgi?id=119394&action=edit A screen grab of the issue SUMMARY In the context menu "Properties" for each file type, a user can associate a program to open that file type upon double click. However, for text files, when I change the default program from "Geany", the change is not saved and behaves in a buggy way. Details provided below. So far I have been able to reproduce the issue only when "Geany" is the default editor. STEPS TO REPRODUCE 1. Right click on a C++ header file (or source file or a python script) -> Properties-> File Type Options. 2. Move some other program to the top and push Geany to the second spot. 3. Click "Apply". OBSERVED RESULT Geany springs back to the top. EXPECTED RESULT The change is saved and applied. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Ubuntu 18.10, Unity, (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.9.5 ADDITIONAL INFORMATION If I push Geany to the third position, then the change to the top position is saved, but the ordering lower down shuffles when clicking "Apply". -- You are receiving this mail because: You are watching all bug changes.
