Will there be a port of this fix to impish?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1913775
Title:
Copy from Firefox Wayland fails to be pasted anywhere else
Statu
My first search was a miss, I think this is the bug referred to here:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1913775
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net
Public bug reported:
There are a number of cases in gtk+-3.0 3.24.30 on wayland where copy
paste from/to various apps fails based on something related to type
handling.
I've run into this on Ubuntu 21.10, with multiple apps under the ubuntu
wayland session.
I have not found a matching bug in the
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340911/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340901/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340912/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340902/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https:
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340910/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340909/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340907/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340905/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340908/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340906/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340903/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340904/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
ht
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340896/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340899/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340900/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340898/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340897/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
Hi Daniel,
You seem to be correct as I tried with 3840x2160 at 2x and it seems to
be less of an issue visually but the screen still goes dark when it does
the change of resolutions on step 2 for succesful login. The mouse goes
from being at the centre of the screen to end up close to the lower
rig
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1868614/+attachment/5340895/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
Hmm, sorry, brainfart. At least 240. Not sure how far back it went.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too lo
OLder systemds, (234-240, I think) have a different erroneous clamp on
RLIMIT_MEMLOCK. See #1840435.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock
Fix attached. Works on disco.
** Patch added: "RLIMIT_MEMLOCK clamp fix"
https://bugs.launchpad.net/ubuntu/disco/+source/systemd/+bug/1840435/+attachment/5304197/+files/fix-systemd-240-memlocklimit.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Actually, its just systemd 240. Looks fixed in 241 and newer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837580
Title:
memlock is not set
Status in systemd package i
Upon further inspection, this is actually fixed in systemd 241. To
reproduce, try setting a LimitMEMLOCK higher than 64mb for the system
unit user@.service, OR for any unit executed by a systemd --user
process. You will see that the RLIMIT_MEMLOCK is actually clamped to
64MB. This can be observe
Public bug reported:
Systemd >= 240 sets a clamp for RLIMIT_MEMLOCK, which is too low for
some realistic applications. This clamp should probably be increased.
This breaks a number of current jackd setups, for example.
See upstream bug: https://github.com/systemd/systemd/issues/13331.
This occu
Systemd 240 and newer introduced a clamp to RLIMIT_MEMLOCK in
c8884aceefc85245b9bdfb626e2daf27521259bd. See
https://github.com/systemd/systemd/issues/13331.
** Bug watch added: github.com/systemd/systemd/issues #13331
https://github.com/systemd/systemd/issues/13331
--
You received this bug n
29 matches
Mail list logo
