** Also affects: wine via
https://bugs.winehq.org/show_bug.cgi?id=52770
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971901
Title:
dlltool uses
Linking binutils package and subscribing Mattias Klose since
https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu1 mentions
"Update from the binutils 2.38 branch: Fix PR 28885" and so a rebuild
based on binutils-source_2.38-4ubuntu1 would fix this issue.
--
You received this bug
** Bug watch added: Sourceware.org Bugzilla #28885
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
** Also affects: binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
Importance: Unknown
Status: Unknown
** Also affects: binutils (Ubuntu)
Importance:
Missed a link, https://bugs.winehq.org/show_bug.cgi?id=52770 shows
others on jammy hitting the same (and confirms this upstream patch fixes
it)
** Bug watch added: Wine Bugzilla #52770
https://bugs.winehq.org/show_bug.cgi?id=52770
--
You received this bug notification because you are a
Public bug reported:
Description:Ubuntu 22.04 LTS
Release:22.04
binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1
/usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like
tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o
dlls/winmm/libwinmm.delay.a --export \
Public bug reported:
g++ 9.3.0-17ubuntu1~20.04 miscompiles the following example for x86
(bar_stdcall should pop 4 bytes fewer than an bar_cdecl, as stdcall is
callee-cleanup for the argument). To see it in this minimized example
one must use `-O0` as it will otherwise be inlined and the calling-
@dannf Thanks, it works for on my x86 winelib program too (amd64
installation).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848200
Title:
gdb not stopping on breakpoint in a 32-bit program
To
I just found
https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1820419 -
seems like the same root cause and linux-image-4.4.0-145-generic
mentioned there (in -proposed) worked as I had hoped above (it has a
version check on the Depends: linux-base, which pulls in the needed
script from
I'm not the original reporter, but I hit (and analyzed) what seems to be
the same failure in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820755
I just switched our packer template over to -proposed to test this:
i.e. changed it to use http://archive.ubuntu.com/ubuntu/dists/xenial-
I finally came up with a workaround that can be done in a preseed.cfg
(until this can be fixed properly in the kernel image)
d-i preseed/early_command string echo -e "#!/bin/sh\napt-install linux-
base" > /usr/lib/post-base-installer.d/99-bug1820755; chmod +x /usr/lib
Related to #1820755 - although the new linux-base is now available in
xenial-updates, the kernel packages do not version their depends to
demand the new version, so apt-get will not necessarily install it
(which causes base-installer to fail, since debootstrap will not have
upgraded from
Some more info: from http://changelogs.ubuntu.com/changelogs/pool/main/l
/linux-base/linux-base_4.5ubuntu1~16.04.1/changelog, it looks like the
actual cutoff would be Depends: linux-base (>= 4.1)
On the question of workarounds, that confirms why pkgsel/upgrade didn't
work, it's all in the
The missing linux-update-symlinks script seems like it's supposed to
come from linux-base, which appears to exist with the same version
number (4.5ubuntu1~16.04.1), yet different contents, in xenial (no
linux-update-symlinks) and xenial-updates. It appears that this is
because 4.5ubuntu1 is
> feel free to provide a minimal/tested patch for this!
I did, in the comment where I first mentioned it:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1762491/comments/9
I'm applying that patch patching in my current builds, and the resulting
OVA has working Xsession guest additions
And yes, my second problem vboxvideo.ko is not a regression from the
status quo; the old package *always* turns on the libGL redirection,
which breaks everybody that's not virtualbox with 3d accel enabled and
working. The proposed fix only turns it on if VBoxClient --check3d
returns success, which
I was suggesting that /etc/X11/Xsession.d/98vboxadd-xclient should do
the same in_virtual_machine check, which I indeed adapted from what you
currently do in /etc/init.d/virtualbox-guest-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry, I have to take that back (a little): it worked in VMware and in
VirtualBox, but I just realized VirtualBox hadn't set the 3d
acceleration option when it imported the OVA. So your code (correctly)
didn't turn on the OpenGL redirects. If I turn on the 3d acceleration,
then it enables
Sorry for going AWOL on you. Yes, the fix in 5.1.38-dfsg-
0ubuntu1.16.04.1 from
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu
/locutusofborg-ppa/+packages produces an OVA that works and has
accelerated graphics in both VMware and VirtualBox.
One other thought in looking at how you
Yes, removing virtualbox-guest-x11 (or even just using update-
alternatives to undo the redirection of for x86_64-linux-
gnu_{gl,egl}_conf) restores normal function (e.g. lightdm's greeter no
longer exits due to broken opengl, so the graphical login comes up and
works).
--
You received this bug
Thinking about how best to solve this, maybe you move update-
alternatives --install/--remove calls into a start/stop actions service
triggered by detection of the appropriate environment, instead of the
package postinst/prerm? I think you should be able to do it with a
systemd unit that has
I am seeing this as well. I'm actually hosting the VM in VMware
workstation 12.5, but the scripts install both VMware and virtualbox
guest tools (so that an OVA is useful in both).
I have an older snapshot that does not have problems, which is using
5.0.40-dfsg-0ubuntu1.16.04.2. The OVA I built
I hit this as well, while upgrading from kubuntu 13.04 to 13.10. Here's
as much debugging as I'm knowledgable to do, captured before I cross my
fingers and reboot anyway...
from term.log:
...
Setting up grub-common (2.00-19ubuntu2.1) ...
Installing new version of config file /etc/grub.d/00_header
I was able to recover the machine by making a USB boot media from the
kubuntu 13.10 install disk, booting from that, and then performing the
efibootmgr command noted above while running from the newer kernel
included in that image. So whatever kernel/BIOS interaction it was, it
seems to have been
This also prevents you from setting up mount points for partition types
the installer doesn't know how to format (HFS+, NTFS, etc). Not that
it's terribly hard to add them later, but it would be nice to do it all
at once
--
[intrepid alpha6] You must know the format of your partition to enter
24 matches
Mail list logo
