[Bug 1634142] [NEW] Don't use openblas cmake builds

2016-10-17 Thread Sven Baars
Public bug reported: Please don't use openblas cmake builds. They are still experimental as is stated during the build process: CMake Warning at CMakeLists.txt:46 (message): CMake support is experimental. This will not produce the same Makefiles that OpenBLAS ships with. Only x86 support is

[Bug 1634142] Re: Don't use openblas cmake builds

2016-10-17 Thread Sven Baars
Huh, that's interesting. I encountered this bug while using the system provided version of openblas on Ubuntu 16.04. And I just fixed the bug in openblas itself by adjusting the cmake build files, so I assumed that that was where the bug came from in the openblas version that was provided by Ubuntu

[Bug 1634142] Re: Don't use openblas cmake builds

2016-10-17 Thread Sven Baars
I'll just try to fix the bug itself tomorrow. It should be much easier to trace it down now that I know that I probably need to compile it with the default build target to be able to bisect it (since it worked fine in Ubuntu 14.04). I'll let you know when I find the problem. -- You received this

[Bug 1634142] Re: Don't use openblas cmake builds

2016-10-19 Thread Sven Baars
** Changed in: openblas (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634142 Title: Don't use openblas cmake builds To manage notifications about this bug go

[Bug 1435663] Re: arm64/efi support

2015-04-19 Thread Sven Baars
After installing this update my system won't boot any more with the message "The system found unauthorized changes on the firmware, operating system or UEFI drivers. Press [N] to run the next boot device, or enter directly to BIOS Setup if there are no other boot devices installed. Go to BIOS Se

[Bug 1435663] Re: arm64/efi support

2015-04-19 Thread Sven Baars
Ok, so the fix to my problem was setting Windows Secure Boot -> Other OS Secure Boot in the BIOS. However, this update will still likely break boot for everyone with an ASUS motherboard until they change this in the BIOS. -- You received this bug notification because you are a member of Ubuntu B

[Bug 1435663] Re: arm64/efi support

2015-04-25 Thread Sven Baars
I was waiting for an update, but didn't get one, so I manually installed grub-efi-amd64-signed 1.34.2+2.02~beta2-9ubuntu1.1, and now it works. I can not test if it also works when updating grub from 2.02~beta2-9ubuntu1 to 2.02~beta2-9ubuntu1.1 though, but I assume it does. -- You received this bu

[Bug 1069163] Re: emesene SEGFAULTs on starting

2012-10-20 Thread Sven Baars
*** This bug is a duplicate of bug 1050358 *** https://bugs.launchpad.net/bugs/1050358 ** This bug has been marked a duplicate of bug 1050358 emesene crashed with SIGSEGV in tupledealloc.24592() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscr

[Bug 881674] Re: SRU: Emesene in Oneiric can't use the Unity Launcher

2012-11-16 Thread Sven Baars
I tested it myself and also haven't seen any complaints, so I can verify that it works. ** Tags removed: removal-candidate verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881674 Tit

[Bug 2095261] Re: libtheoraenc1:i386 fails to install

2025-02-12 Thread Sven Baars
The problem is that the 32-bit package ships a symlink to changelog.Debian.gz instead of the actual file. This issue is not present in the upstream Debian package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.