> Editing away the check may have worked when it was first done (in
https://salsa.debian.org/wine-
team/wine/-/commit/2c3ae8a186f255958da213fe35510908d9ca50ca, for Wine
7.0), but for the current Wine versions, this no longer results in a
functioning version of Wine.
To clarify this; initially, com
** Description changed:
The Wine package in Ubuntu 24.04 on arm64 is entirely broken
(9.0~repack-4build3); wine hangs on startup.
The arm64 Wine package in Ubuntu 22.04 (6.0.3~repack-1) did work
correctly though, so this is a regression.
The crashes are caused by the Debian/Ubuntu
To clarify how to reproduce it; essentially just install wine on Ubuntu
24.04 on arm64, and try to do anything - e.g. just "wine wineboot" is
enough to show the hang.
A full reproducible example in the form of a dockerfile is this:
```
FROM ubuntu:24.04
RUN apt-get update && apt-get install -y wi
Public bug reported:
The Wine package in Ubuntu 24.04 on arm64 is entirely broken
(9.0~repack-4build3); wine hangs on startup.
The arm64 Wine package in Ubuntu 22.04 (6.0.3~repack-1) did work
correctly though, so this is a regression.
The crashes are caused by the Debian/Ubuntu packaging. Upstre
Public bug reported:
In OpenSSL 1.0.1f on Ubuntu 14.04, there's a regression in using DTLS,
caused by a backported bugfix for CVE-2014-3571.
This particular bugfix (debian/patches/CVE-2014-3571-1.patch,
corresponding to
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8d7aab986b499f34
I tested this one, but this one doesn't even get to "Uncompressing
Linux".
If this can't be backported into the official packages I guess I'll just
have to keep running kernels I build manually myself instead - that's
probably no big issue either, until I update the whole distro to
something that
I can finally confirm that this kernel boots, and fixes the bug as the
cherry-picked patch intended to do (making wine run windows/arm binaries
properly).
(I still had to hack the .deb files to convert them from -armel to
-armhf, but I just changed the architecture name in the .deb control
file.)
Ok, here's the dmesg output.
** Attachment added: "dmesg.out"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/1265024/+attachment/3945533/+files/dmesg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Running only "apport-collect 1265024" gave:
---
Package linux-ti-omap4 not installed and no hook available, ignoring
*** Updating problem report
No additional information collected.
---
So then I ran "apport-collect -p linux-image-omap4 1265024" instead,
which seems to have uploaded something a
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1265024/+attachment/3945468/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265024
apport information
** Tags added: apport-collected
** Description changed:
Please backport commit a4780adeefd042482f624f5e0d577bf9cdcbb760 (which
is included in upstream kernel 3.11) to the ti-omap4 packages for ubuntu
precise.
- I tried doing this manually, and when cherrypicking there
This kernel doesn't boot either, it stops after "done, booting the
kernel." just as the previous one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265024
Title:
TLS register TPIDRURW not preserved
I really doubt this patch is what breaks it, but I'll test your kernel
tomorrow. I'm not sure whether a saucy chroot would work or not - I
first tried cross-building from 13.04 but ran into some issues there, so
I cross-built from a 12.04 chroot instead. But my issues were in the
build scripts and
Ok, so now there's some progress but it still doesn't work right. Now
the kernel uncompresses ok but something still goes wrong when it should
be booted - it goes as far as "Uncompressing Linux... done, booting the
kernel." but nothing past that.
For the record, I wasn't able to install the linux-
I forgot to mention - I've removed the "quiet splash" options from
/boot/boot.script, so I normally get everything starting from this:
[0.00] Booting Linux on physical CPU 0
But with your kernel I don't get this far.
--
You received this bug notification because you are a member of Ubun
This kernel doesn't boot for me either, although I'm not really sure
what is going wrong.
I've installed it by downloading linux-headers-3.2.0-58-omap, linux-
headers-3.2.0-58 and linux-image-3.2.0-58-omap, doing dpkg -i on those
three .debs, and later run a modified version of the flash-kernel sc
This test kernel doesn't boot at all (I had to modify flash-kernel for
it to be installed at all - flash-kernel points out that my
subarchitecture is omap4 while this kernel is plain omap).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Can you provide an armhf .deb? I guess it doesn't really matter much
from the kernel point of view, but my dpkg doesn't want to install them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265024
Titl
Public bug reported:
Please backport commit a4780adeefd042482f624f5e0d577bf9cdcbb760 (which
is included in upstream kernel 3.11) to the ti-omap4 packages for ubuntu
precise.
I tried doing this manually, and when cherrypicking there's a minor
pretty trivial conflict to resolve, and after cherrypic
19 matches
Mail list logo
