https://bugs.kde.org/show_bug.cgi?id=415872
--- Comment #5 from Tom B ---
I've been trying to replicate this in KDE Neon in Virtualbox so I could provide
a .vdi where you can see the issue yourself. However, I have so far been unable
to reproduce the issue.
I have noticed one difference
https://bugs.kde.org/show_bug.cgi?id=401088
Tom Boshoven changed:
What|Removed |Added
CC||tombosho...@gmail.com
--- Comment #11 from Tom
https://bugs.kde.org/show_bug.cgi?id=416682
--- Comment #5 from Tom Hughes ---
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
https://bugs.kde.org/show_bug.cgi?id=416682
--- Comment #4 from Tom Hughes ---
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?
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=69530
Tom Hughes changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=416928
--- Comment #9 from Tom Albers ---
The content of attachment 125550 has been deleted for the following reason:
Per user request. (TA)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413476
--- Comment #2 from Tom B ---
what is the best way to get a backtrace? Trying it again a few months later
with the most recent versions of each package, I am still getting the same
problem.
dmesg shows the following:
[315423.305190] krfb[2750682
https://bugs.kde.org/show_bug.cgi?id=416662
--- Comment #16 from Tom F ---
With latest update the issue no longer occurs. Performing pkcon update and
installing the newer packages results in desktop displaying correctly on
start/restart.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=416617
Tom F changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=416662
Tom F changed:
What|Removed |Added
CC||g...@ppetw.com
--- Comment #15 from Tom F ---
*** Bug
https://bugs.kde.org/show_bug.cgi?id=416662
--- Comment #13 from Tom F ---
> Thank you Tom, I run the command indicated, with a little change for me and
> the package has been installed and the desktop working again.
>
> This is the command I ran: sudo dpkg -i
> qml
https://bugs.kde.org/show_bug.cgi?id=416662
--- Comment #11 from Tom F ---
(In reply to Valter Mura from comment #10)
> (In reply to Tom F from comment #9)
> > I think this is related to https://bugs.kde.org/show_bug.cgi?id=416617.
> > Manually installing qml-module-org-kde-qqc2de
https://bugs.kde.org/show_bug.cgi?id=416662
Tom F changed:
What|Removed |Added
CC||tomfoley...@gmail.com
--- Comment #9 from Tom F ---
I
https://bugs.kde.org/show_bug.cgi?id=416682
Tom Hughes changed:
What|Removed |Added
Severity|major |normal
CC
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #34 from Tom Hughes ---
No, we understand the problem now.
You are trying to run valgrind on code compiled to target the AVX512
instruction set extensions and that is not currently supported by valgrind.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=416617
Tom F changed:
What|Removed |Added
CC||tomfoley...@gmail.com
--- Comment #1 from Tom F ---
I
https://bugs.kde.org/show_bug.cgi?id=416490
Bug ID: 416490
Summary: KMail doesn't show emails from last 2 weeks
Product: kmail2
Version: 5.13.1
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=416244
--- Comment #4 from Tom B ---
> You're on X11, right? "Fixed" in 5.18.
I'm on Wayland and this only happens on Wayland.
> Firefox does its own headerbar thing so I recommend to report this bug to
> Firefox developers, but just to
https://bugs.kde.org/show_bug.cgi?id=416244
--- Comment #1 from Tom B ---
Created attachment 125118
--> https://bugs.kde.org/attachment.cgi?id=125118=edit
screenshot of problem in firefox
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416244
Bug ID: 416244
Summary: Kwin wayland incorrect window decorations when GTK app
changes the default titlebar buttons
Product: kwin
Version: 5.17.5
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=415872
--- Comment #2 from Tom B ---
It seems to be something to do with how often the script triggers signals.
If I rate limit the events (using the system clock to keep track of how often
they are fired) to once per frame it works fine. See my workaround
/kdeinit_kwin_rules_dialog.dir/all] Fehler 2
[ 35%] Built target kdecorationprivatedeclarative
make: *** [Makefile:130: all] Fehler 2
unfortunately again it will need some time to debug and review the code but the
expected saved time is tremendous
sincerely tom
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=415872
Tom B changed:
What|Removed |Added
Component|wayland-generic |scripting
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=415872
--- Comment #1 from Tom B ---
I've worked out this is scripting engine related. It only appears to happen
when the kwin tiling extension is enabled. I've not yet managed to track down
exactly what causes the segfault but I now have reproducible steps
https://bugs.kde.org/show_bug.cgi?id=415872
Bug ID: 415872
Summary: kwin_wayland random segfault
libQt5Qml.so.5.14.0[7fe09a171000+307000]
Product: kwin
Version: 5.17.4
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #32 from Tom Hughes ---
No version of gcc is going to enable AVX512 by default though I think you may
be able to specify a different default target when compiling gcc.
Usually this sort of problem is caused by using -march=native which
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #30 from Tom Hughes ---
The short version however is that valgrind doesn't support AVX512 yet so don't
compile your code for AVX512 if you want to be able to use valgrind on it, and
that includes any libraries you use.
Note that valgrind
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #29 from Tom Hughes ---
So the four byte EVEX prefix of 62 f1 fe 08 decodes as:
EVEX.mm = 0b01 / 1
EVEX.pp = 0b10 / 2
EVEX.RXB = 0b111 / 7
EVEX.R’ = 0b1/ 1
EVEX.X= 0b1/ 1
EVEX. = 0b / 15
EVEX.V’ = 0b1
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #28 from Tom Hughes ---
So 0x62 is an EVEX prefix, but the opcode map fails to mention that even in the
October 2019 edition of the Intel manual...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #27 from Tom Hughes ---
So there really are instructions starting with 0x62 it seems... Some examples:
5ca6f: 62 f1 fe 08 6f 45 00vmovdqu64 0x0(%rbp),%xmm0
90bf6: 62 e1 7c 08 11 56 0avmovups %xmm18,0xa0(%rsi
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #22 from Tom Hughes ---
I was afraid that might happen as it's a local function that isn't exported...
Are you able to just gzip the output it and attach it here?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #19 from Tom Hughes ---
In fact you should be able to just disassemble that function with:
objdump --disassemble=H5P_dup_prop /usr/lib64/libhdf5.so.103.1.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #17 from Tom Hughes ---
It's /usr/lib64/libhdf5.so.103.1.0 you need to run objdump on, not your
application, as that library is where the problem instruction is found.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=388649
--- Comment #7 from Tom Cunningham ---
Yes, I haven't noticed it as an issue since 6.0.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415616
--- Comment #3 from Tom Courtney ---
Thank you, thank you, thank you! That workaround worked. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415616
Tom Courtney changed:
What|Removed |Added
CC||tpcourt...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=415616
Bug ID: 415616
Summary: Install problem on Windows 10. GUI severely corrupted
Product: kdenlive
Version: 19.12.0
Platform: Other
OS: MS Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=415382
--- Comment #4 from Tom Hughes ---
*** This bug has been marked as a duplicate of bug 356715 ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356715
--- Comment #5 from Tom Hughes ---
This is VCVTPH2PS and is fixed in the 3.15.0 release.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398870
Tom Hughes changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=356715
Tom Hughes changed:
What|Removed |Added
CC||the.true.nathan.mills@gmail
https://bugs.kde.org/show_bug.cgi?id=398870
Tom Hughes changed:
What|Removed |Added
CC||the.true.nathan.mills@gmail
https://bugs.kde.org/show_bug.cgi?id=415382
Tom Hughes changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=415382
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #2 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=382325
Tom Bruno changed:
What|Removed |Added
CC||tbruno-...@naveoss.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=415246
Bug ID: 415246
Summary: ktorrent stalls after time until reboot
Product: ktorrent
Version: 5.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=404990
--- Comment #92 from Tom Chiverton ---
There is no FUD.
KDE should pull the GMail integration from KMail, instead setting up a pure
IMAP link, unless or until they win the fight with Google.
This would be an excellent interim solution that would lead
https://bugs.kde.org/show_bug.cgi?id=415159
--- Comment #3 from Tom Hughes ---
Well yes they will all spin off children because rustc is a separate program to
cargo - it's like tracing make and it not following over the exec when it runs
gcc to do the actual compile.
Note that --trace-children
https://bugs.kde.org/show_bug.cgi?id=415159
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #1 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #12 from Tom Hughes ---
Can you please try and disassemble the problem function - this should do it I
think:
objdump --disassemble=_ZN7rocksdb27AdvancedColumnFamilyOptionsC2Ev
/root/open_source/rocksdb/build/librocksdb.so.6.6.0
Then post
https://bugs.kde.org/show_bug.cgi?id=414944
--- Comment #3 from Tom Hughes ---
Right but 0x62 is a single byte instruction so only the first byte matters...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393351
Tom Hughes changed:
What|Removed |Added
CC||caiyueq...@bytedance.com
--- Comment #9 from Tom
https://bugs.kde.org/show_bug.cgi?id=393351
Tom Hughes changed:
What|Removed |Added
CC||jody@gmail.com
--- Comment #8 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=414053
Tom Hughes changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=414944
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=414870
--- Comment #3 from Tom Hughes ---
Well sure gcc may have generated different code.
The point is that once you use long double on x86-32 there is no guarantee you
will get the same results under valgrind as when running natively. You might,
but you
https://bugs.kde.org/show_bug.cgi?id=414870
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #1 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=398767
--- Comment #5 from Tom ---
I've confirmed that the issue does not occur in my case after setting up
kwallet.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398767
--- Comment #4 from Tom ---
Created attachment 124197
--> https://bugs.kde.org/attachment.cgi?id=124197=edit
New crash information added by DrKonqi
falkon (3.1.0) using Qt 5.12.5
- What I was doing when the application crashed:
Click
https://bugs.kde.org/show_bug.cgi?id=398767
Tom changed:
What|Removed |Added
CC||kde.b...@mocha42.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=400538
Tom Hughes changed:
What|Removed |Added
CC||eekn...@gmail.com
--- Comment #13 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=414659
--- Comment #10 from Tom Hughes ---
Ah I had a feeling it has been fixed recently but I missed that.
The user here is running 3.13 so won't have the fix but I'll update the
duplicate.
*** This bug has been marked as a duplicate of bug 400538
https://bugs.kde.org/show_bug.cgi?id=253657
Tom Hughes changed:
What|Removed |Added
CC||eekn...@gmail.com
--- Comment #26 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=414659
Tom Hughes changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=414659
Tom Hughes changed:
What|Removed |Added
Summary|Unrecognised instruction|vex amd64->IR: unhandled
|/
https://bugs.kde.org/show_bug.cgi?id=414659
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #4 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=414558
Bug ID: 414558
Summary: error listed upon opening stellarmate
Product: kstars
Version: 3.3.8
Platform: Ubuntu Packages
OS: other
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=414291
Tom Hughes changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=414291
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #1 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=404990
--- Comment #81 from Tom Chiverton ---
That works, nice.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410700
--- Comment #5 from Tom Chiverton ---
Using IMAP.GOOGLEMAIL.COM as the IMAP (receiving) works to enable to normal
authentication options, which work fine.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410700
Tom Chiverton changed:
What|Removed |Added
CC||bugs.kde@falkensweb.com
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=404990
--- Comment #77 from Tom Chiverton ---
Can't even work around this by using Akonadi Console to ('configure remote')
set the Authentication to "1" instead of "9" because it's reset shortly after
Kmail starts, and you get the popup
https://bugs.kde.org/show_bug.cgi?id=410872
--- Comment #5 from Tom Chiverton ---
Can't even work around this by using Akonadi Console to ('configure remote')
set the Authentication to "1" instead of "9" because it's reset shortly after
Kmail starts, and you get the popup
https://bugs.kde.org/show_bug.cgi?id=404990
--- Comment #76 from Tom Chiverton ---
Yup, as soon as you set the IMAP server to imap.gmail.com you can see the
password field goes disabled and the advanced connection settings are disabled
and "gmail" type is forced.
This "helpful&q
https://bugs.kde.org/show_bug.cgi?id=410872
--- Comment #4 from Tom Chiverton ---
As soon as you set the IMAP server to imap.gmail.com you can see the password
field goes disabled and the advanced connection settings are disabled and
"gmail" type is forced.
This "helpful" wou
https://bugs.kde.org/show_bug.cgi?id=404990
--- Comment #75 from Tom Chiverton ---
Workaround doesn't work in Kmail v5.7.3 because both password and connection
settings (to set to "plain") are disabled.
Even for a freshly created IMAP connection.
Something in KDE is disabling the
https://bugs.kde.org/show_bug.cgi?id=410872
--- Comment #3 from Tom Chiverton ---
Workaround doesn't work in Kmail v5.7.3 because both password and connection
settings (to set to "plain") are disabled.
Even for a freshly created IMAP connection.
Something in KDE is disabling the
https://bugs.kde.org/show_bug.cgi?id=404990
Tom Chiverton changed:
What|Removed |Added
CC||bugs.kde@falkensweb.com
--
You
https://bugs.kde.org/show_bug.cgi?id=410872
Tom Chiverton changed:
What|Removed |Added
CC||bugs.kde@falkensweb.com
--
You
https://bugs.kde.org/show_bug.cgi?id=414053
Tom Hughes changed:
What|Removed |Added
Summary|vex amd64->IR: unhandled|vex amd64->IR: unh
https://bugs.kde.org/show_bug.cgi?id=413775
Tom changed:
What|Removed |Added
CC||tosch...@gmx.de
--- Comment #3 from Tom ---
Want just
https://bugs.kde.org/show_bug.cgi?id=413346
Tom Albers changed:
What|Removed |Added
Assignee|sysad...@kde.org|n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=413663
Bug ID: 413663
Summary: [Wayland] Screens often reversed position after
suspend or boot
Product: KScreen
Version: 5.17.1
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=413344
Tom Albers changed:
What|Removed |Added
Assignee|sysad...@kde.org|n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=343592
--- Comment #19 from Tom B ---
This works fine in Wayland with one caveat: You can't assign keys that are
already assigned. For example, assigning Meta+1 doesn't work until you first
manually unassign the default behaviour "Activate Task Manager
https://bugs.kde.org/show_bug.cgi?id=413476
Bug ID: 413476
Summary: Wayland/Pipewire segfault on connection
Product: krfb
Version: 19.08.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=413396
Bug ID: 413396
Summary: kwin_wayland crash when displays turned back on
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=412684
--- Comment #17 from Tom B ---
Scratch that, although most Arch packages are 5.17.1, it looks like kwin 5.17.1
hasn't been released yet.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412684
--- Comment #16 from Tom B ---
did this patch make it into 5.17.1 or does it need to be manually applied? I
just upgraded and still have the same issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413024
Tom Janssen changed:
What|Removed |Added
Version|5.12.2 |unspecified
Product|kontact
https://bugs.kde.org/show_bug.cgi?id=412684
Tom B changed:
What|Removed |Added
CC||t...@r.je
--- Comment #10 from Tom B ---
Same issue
https://bugs.kde.org/show_bug.cgi?id=413024
Bug ID: 413024
Summary: Kontact crashes on launch
Product: kontact
Version: 5.12.2
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: crash
https://bugs.kde.org/show_bug.cgi?id=412911
Bug ID: 412911
Summary: KWin crashed after wake up
Product: kwin
Version: 5.16.5
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=412299
Tom Albers changed:
What|Removed |Added
Assignee|sysad...@kde.org|n...@kde.org
CC
https://bugs.kde.org/show_bug.cgi?id=412299
Tom Albers changed:
What|Removed |Added
CC|t...@kde.org|
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=412738
--- Comment #17 from Tom Moebert ---
Sry, I'm only occasionally coming here and currently don't really have time to
look at the bugs into detail.
I thought Nate receives and tracks all the gwenview bugs.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=412738
--- Comment #14 from Tom Moebert ---
Yes:
(gdb) print thumbnailPix.isNull()
$9 = true
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412738
--- Comment #12 from Tom Moebert ---
Thread 1 "gwenview" hit Breakpoint 1,
Gwenview::ThumbnailBarItemDelegate::sizeHint (this=0x9b3090, index=...)
at /home/tom/Programme/gwenview/lib/thumbnailview/thumbnailbarview.cpp:180
180
https://bugs.kde.org/show_bug.cgi?id=412738
--- Comment #7 from Tom Moebert ---
For me crashes in
#4 0x77591475 in operator/ (s=..., c=0) at
/usr/include/qt5/QtCore/qsize.h:196
194 inline const QSize operator/(const QSize , qreal c)
195 {
196 Q_ASSERT(!qFuzzyIsNull(c
601 - 700 of 1485 matches
Mail list logo
