SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
context: keep per node quantum and rate settings
Copy the global quantum and rate limits before applying node specific
settings. Otherwise one node settings will propagate to the defaults
of the next nodes, which can result in impossible or wrong settings.
blackstar :: ~ » emacs
Xlib: sequence lost (0x10000 > 0x352) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x411) in reply type 0xf!
Xlib: sequence lost (0x10000 > 0x417) in reply type 0x16!
Xlib: sequence lost (0x10000 > 0x6d6) in reply type 0xf!
processCropSelections in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based buffer overflow
(e.g., "WRITE of size 307203") via a crafted TIFF image.
processCropSelections in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based buffer overflow
(e.g., "WRITE of size 307203") via a crafted TIFF image.
Anyway, this patch does not apply and inspecting the code I find nothing in tools/tiffcrop.c in 4.4.0 that even vaguely resembles where the one-line patch would go. I have avoided tiff-4.5.0 for now because they'd accidentally dropped a function from 4.4.0 without bumping the library soname (didn't cause any noticeable issues with anything we ship, so far as I can tell), and so they went ahead and bumped it for 4.5.0. This would require rebuilding 33 packages... and the "maintenance" seems about the same. I really doubt we'll see 4.5.1 on account of this CVE any time soon.
Patch: waylandclipboard: roundtrip to get accurate focus state
Code:
The current approach is too complicated and not correct anyway.
To summarize QGuiApplication::focusWindow is delayed so the focus
watcher was introduced, however when the window is hidden and
setMimeData called before Wayland events have been processed,
then focusWatcher is naturally out of sync, so the check
was complicated to work around this state. However the same
issue arises when the window is deleted before calling
setMimeData.
Instead of introducing more complicated checks and workaround
roundtrip so the focusWatcher state is up to date before setting
the clipboard.
BUG:463199
FIXED-IN: 5.103
sprintf in the GNU C Library (glibc) 2.37 has a buffer overflow (out-of-bounds write) in some situations
with a correct buffer size. This is unrelated to CWE-676. It may write beyond the bounds of the destination
buffer when attempting to write a padded, thousands-separated string representation of a number, if the
buffer is allocated the exact size required to represent that number as a string. For example, 1,234,567 (with
padding to 13) overflows by two bytes.
If this patch needs to be applied to xorg-server 1.20 in 15.0 then I have one request if Pat sees this post. Xorg 1.20 needs a patch for Mate-Desktop or any compositor using present to work with nvidia drivers. This is not a security patch but its a very small patch that fixes this issue. If it doesn't happen its no big deal, I will continue to recompile xorg-server when a new patch comes out, but this would save us mate users from having to do that and its a very small patch. This patch is already applied in the newer branches so its not needed for current.
In addition to this, if we do get another kernel update for security patches to 15.0 (which is likely), could you please also add this patch for modern AMD CPU's. It's a very small patch but does make a noticeable difference, More information here
Started to compile 5.15.94 today to apply this patch and after checking I can confirm that somewhere between 5.15.80 and 5.15.94 the patch was backported to the 5.15 brach.
wayland: Guard wayland object destructors
Kidletime is a singleton and the client API works by supplying ints to add
or remove timeouts. When not all timeouts are removed before program exits,
trying to destroy the wayland objects will crash since the lifetime of the
wayland connection is tied to the QGuiApplication.
BUG:465801
FIXED-IN:5.104
That looks to be just one of several patches that apply to 'c/etags' for this issue, so it might not apply in isolation (haven't tried it yet). Anyway, looks like 28.3 is not far off, so I think I'll just wait for that.
edit: I was looking in 'master' the one in emacs-28 branch will likely be fine, but as said, 28.3 doesn't look far off.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
