[Bug 993959] Re: libasound2-dev does miss static library since 1.0.25-1 - regression in 12.04 to 11.10
This bug still persists in Ubuntu 19.04 (Disco Dingo). My use case is porting 32-bit x86 assembly that calls ALSA through a C interface. In order to not require modern systems to have to install 32-bit libraries just for this one program, I would like to be able to link statically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993959 Title: libasound2-dev does miss static library since 1.0.25-1 - regression in 12.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/993959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802183] [NEW] fonts fail when non-UTF8 filenames exist anywhere
Public bug reported:
When editing an ebook or setting the font embedding preferences, Calibre
cannot find any fonts at all if there exists a filename anywhere in the
font directory that contains text that is invalid UTF-8.
This can happen if the font designer's computer was in a different
LOCALE than the calibre user. For example, I had downloaded a font
designed by a man in Russia who had used Cyrillic encoding for the names
of some image files in a directory adjacent to the font.
The bug is easily repeatable. Create a file in any of your font
directories or sub-directories with an invalid sequence. For example,
from the command line, run:
mkdir -p ~/.fonts/foo
touch ~/.fonts/foo/$'fred\377juki'
When you run Calibre and try to add a font, after selecting a font file,
it will give you a dialog box saying, "ERROR: Unhandled Exception.
UnicodeDecodeError:'utf8' codec can't decode byte 0xff in position 4:
invalid start byte".
It will also print on stderr a message similar to this:
calibre, version 3.21.0
ERROR: Unhandled exception: UnicodeDecodeError:'utf8' codec can't decode
byte 0xff in position 4: invalid start byte
calibre 3.21 embedded-python: False is64bit: True
Linux-4.15.0-38-generic-x86_64-with-Ubuntu-18.04-bionic Linux ('64bit', '')
('Linux', '4.15.0-38-generic', '#41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018')
Python 2.7.15rc1
Linux: ('Ubuntu', '18.04', 'bionic')
Interface language: None
Successfully initialized third party plugins: Gather KFX-ZIP (from KFX Input)
(1, 9, 0) && DeDRM (6, 6, 1) && Package KFX (from KFX Input) (1, 9, 0) && KFX
metadata reader (from KFX Input) (1, 9, 0) && KFX Input (1, 9, 0)
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/gui2/font_family_chooser.py", line 299, in
add_fonts
self.font_scanner.do_scan()
File "/usr/lib/calibre/calibre/utils/fonts/scanner.py", line 327, in do_scan
files = tuple(walk(folder))
File "/usr/lib/calibre/calibre/__init__.py", line 523, in walk
for record in os.walk(dir):
File "/usr/lib/python2.7/os.py", line 286, in walk
if isdir(join(top, name)):
File "/usr/lib/python2.7/posixpath.py", line 73, in join
path += '/' + b
UnicodeDecodeError: 'utf8' codec can't decode byte 0xff in position 4: invalid
start byte
Ideally, calibre would ignore such files and continue on. However, if that is
difficult, it'd be good to catch the error and show a message telling people
something along the lines of,
Non-UTF-8 filename found somewhere in your font directories, causing
Calibre to barf.
Please find and rename the file so that Calibre can read your fonts. You
can find the
offending file like so: find (...PRINT CALIBRE FONT DIRECTORIES HERE...)
| iconv
** Affects: calibre (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Output from calibre's standard error"
https://bugs.launchpad.net/bugs/1802183/+attachment/5210136/+files/calibre.stderr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802183
Title:
fonts fail when non-UTF8 filenames exist anywhere
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1802183/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802183] Re: fonts fail when non-UTF8 filenames exist anywhere
Script started on 2018-11-07 09:47:45-0800 $ ls Sumkin\ type\!/Sumkin\ Cover 'Sumkin by MRfrukta!.png' 'Sumkin Russian type by MRfrukta!.png' ''$'\346''Ҽ'$'\254\277\241'' '$'\336''ӿ'$'\365\324'' (1).png' ''$'\346''Ҽ'$'\254\277\241'' '$'\336''ӿ'$'\365\324'' (2).png' ''$'\346''Ҽ'$'\254\277\241'' '$'\336''ӿ'$'\365\324'' (3).png' ''$'\346''Ҽ'$'\254\277\241'' '$'\336''ӿ'$'\365\324'' (4).png' ''$'\346''Ҽ'$'\254\277\241'' '$'\336''ӿ'$'\365\324'' (5).png' $ ls Sumkin\ type\!/Sumkin\ Cover | iconv -f cyrillic Sumkin by MRfrukta!.png Sumkin Russian type by MRfrukta!.png цвМЌПЁ огПѕд (1).png цвМЌПЁ огПѕд (2).png цвМЌПЁ огПѕд (3).png цвМЌПЁ огПѕд (4).png цвМЌПЁ огПѕд (5).png $ exit Script done on 2018-11-07 09:48:14-0800 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802183 Title: fonts fail when non-UTF8 filenames exist anywhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1802183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.
@raphael-fáistonpc: I have been having this and other GDM3 related issues hitting the laptops I administer and its a showstopper here, too. My current "solution" has been to give up on GDM3 and just 'sudo apt install lightdm'. Perhaps that will let your robotics team get back to work without having to chuck all of the latest Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] Re: [regression] firefox dies with SIGILL on machines without SSE2
Nearly a year later, this is still an immediate problem. For people finding this bug via Google, the only fix I've found that cares about security is to use Debian GNU/Linux instead of Ubuntu and `apt install firefox-esr`. This works because the stable (Stretch) version of Debian uses Firefox-ESR 52.9.0 which was released last month (https://www.mozilla.org/en-US/firefox/52.9.0/releasenotes/). However, I notice that the next Extended Support Release of Firefox will be based on version 60, and thus I presume will have the same SIGILL problems due to an incorrect ABI if it is compiled in the same way as the current Firefox. So Debian will not be a panacea. I understand that time marches on, as do ABIs, but minor updates to an Ubuntu LTS release should not add new requirements on the CPU architecture. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697800 Title: [regression] firefox dies with SIGILL on machines without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775754] Re: Antiquated hardware crashes with SIGILL
By the way, I just tested it and csysdig works if compiled with liblua instead of libluajit. Maybe the i386 build should default to that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775754 Title: Antiquated hardware crashes with SIGILL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysdig/+bug/1775754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775754] [NEW] Antiquated hardware crashes with SIGILL
Public bug reported: Antiquated hardware (i686-class pentium iii) runs Ubuntu great 99%, but Csysdig may be in the 1%. (Sysdig itself runs fine. Csysdig, the curses interface, crashes with SIGILL.) If this can't be fixed it'd be nice if Ubuntu separated/labelled packages that require special cpu features. GDB backtrace: $ sudo gdb csysdig (gdb) run (gdb) bt #0 0xb7aeee51 in ?? () from /usr/lib/i386-linux-gnu/libluajit-5.1.so.2 #1 0xb7aeef91 in ?? () from /usr/lib/i386-linux-gnu/libluajit-5.1.so.2 #2 0xb7b15fef in luaopen_base () from /usr/lib/i386-linux-gnu/libluajit-5.1.so.2 #3 0xb7ac08ea in ?? () from /usr/lib/i386-linux-gnu/libluajit-5.1.so.2 #4 0xb7b1d83b in luaL_openlibs () from /usr/lib/i386-linux-gnu/libluajit-5.1.so.2 #5 0x0047b718 in sinsp_chisel::init_lua_chisel(chisel_desc&, std::__cxx11::basic_string, std::allocator > const&) () #6 0x0047c95e in sinsp_chisel::get_chisel_list(std::vector >*) () #7 0x0046dfab in csysdig_init(int, char**) () #8 0x00453e65 in main () (gdb) c Continuing. Program terminated with signal SIGILL, Illegal instruction. The program no longer exists $ file /usr/bin/csysdig /usr/bin/csysdig: ELF 32-bit LSB shared object, Intel 80386, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=d912ec095a497a8c0d037bd739409cabe073dc3e, stripped $ file /usr/lib/i386-linux-gnu/libluajit-5.1.so.2.1.0 /usr/lib/i386-linux-gnu/libluajit-5.1.so.2.1.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=056c956129e8a8fcf3f777a7be44491dcc5783f0, stripped ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sysdig 0.19.1-1build2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic i686 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: i386 Date: Thu Jun 7 19:33:28 2018 SourcePackage: sysdig UpgradeStatus: Upgraded to bionic on 2018-05-24 (14 days ago) ** Affects: sysdig (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775754 Title: Antiquated hardware crashes with SIGILL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysdig/+bug/1775754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698501] Re: Please package a version of Firefox without SSE2
In Bug 1697800 Seth Arnold points out that the upgrade tools are not in a position to check architecture features before installation. While I don't know the best (least worst?) solution, here are some ideas. Option A) Compile the SSE2 parts of Firefox in a separate library and place it in /usr/lib/sse2/. I have read that the Linux kernel already searches that directory first on processors that support that feature. A solution using libraries would make sense as it's how we already handle similar situations of binaries that only work on certain types of hardware (e.g., graphics cards, 32bit/64bit). This might require working with the Mozilla folks to convince them to isolate the code. Option B) Create a new package "firefox-i686" (for processors without SSE2), rename the current firefox to "firefox-i786", and then make "firefox" a meta-package that picks the right one. I don't know enough about meta-packages to know if this is actually feasible. Option C) Create a new dpkg architecture "i686" which will only contain binaries that can actually run on 686 class processors. Rename "i386" to "i786" to reflect reality. While tedious to implement and perhaps a redundant use of disk space for 99.9% of the binaries, it is fairly straightforward to do and is perhaps the "correct" solution. Option D) Add a new APT repository such as "xenial-i686". This is similar to (c) but lazier. The xenial-i686 repository would contain very few programs, just the ones, like Firefox, that had to be compiled differently than the ones already supplied in the standard repository. This has the downside that there is no way to indicate to the end user when a package is not available at all for the i686. It is also perhaps a misuse of repositories when that's what architectures are for. Option E) Bite the bullet and rewrite the package tools to handle ABIs that are nearly, but not quite, identical. This would be handy as we approach programs that require SSE3, SSE4, SSE4.1, etc. I don't know what this would look like, but I presume it'd require a lot of discussion first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698501 Title: Please package a version of Firefox without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1698501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] Re: [regression] firefox dies with SIGILL on machines without SSE2
Seth writes, "running a known-insecure webbrowser is probably a bad idea." Agreed. Except I would say "definitely". It's important that Ubuntu gets some sort of a fix soon. I've already seen a person asking on a forum how to downgrade and being told to install a third party package by hand. This is no better, and possibly worse from a security perspective. Seth also writes, "None of the upgrade tools are in a position to check architecture features before installing a package. There may not be a happy solution here." Again, I agree, the solutions I'm coming up with are not particularly happy. However, a solution is needed. In the short term, switching to ESR (as mentioned above) would let Firefox work on all supported architectures and have security updates. For the long term, well, I don't want to clutter up this bug — which is about an urgent problem needing an immediate solution — so I've filed Bug 1698501. I'll continue my response there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697800 Title: [regression] firefox dies with SIGILL on machines without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] Re: [regression] firefox dies with SIGILL on machines without SSE2
By the way, since this problem is already causing Ubuntu LTS systems to break, it may make sense to implement a quick stopgap solution. One possibility is to change the version of Firefox in 16.04 to "firefox- esr" (Extended Support Release). While this release will only be supported by Mozilla until March 2018, which is not enough for LTS, it's available now and works. https://support.mozilla.org/en-US/kb/your-hardware-no-longer-supported: "Firefox Extended Support Release (ESR) will continue to work with older processors but will not receive updates beyond ESR version 52. Firefox ESR version 59, scheduled for release in March 2018, will no longer be supported." You can find ESR here: https://www.mozilla.org/en- US/firefox/organizations/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697800 Title: [regression] firefox dies with SIGILL on machines without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698501] [NEW] Please package a version of Firefox without SSE2
Public bug reported: As has been noted in Bug 1697800, Firefox now dies on machines which Ubuntu still supports (i686). This is a critical problem as Firefox was the only modern web browser that did not require the SSE2 extensions and Ubuntu has committed to long term support for machines without SSE2. While Bug 1697800 is dealing with the urgent matter of Ubuntu systems breaking right now, I'm filing this bug to request a long term solution. According to Mozilla's Support page (https://support.mozilla.org/en- US/kb/your-hardware-no-longer-supported): "The processor requirements of Firefox as distributed by Linux distributions may differ from the processor requirements of Firefox as distributed by Mozilla, so you may be able to obtain an up-to-date version of Firefox that does not require SSE2 from your Linux distribution." I don't know how hard this would be, but could the Ubuntu-Mozilla Team please look into compiling a version of Firefox that does not require SSE2? Thank you. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698501 Title: Please package a version of Firefox without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1698501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] Re: [regression] firefox dies with SIGILL on machines without SSE2
It looks like this has been in the works for awhile and Mozilla had intended for Firefox to detect SSE2 support in the installer and in the automatic updates. Of course, Ubuntu is skipping both of those. https://bugzilla.mozilla.org/show_bug.cgi?id=1308167 It's urgent that this gets fixed. The way things are right now, if people do a normal upgrade to 16.04, they can end up with a broken system. ** Bug watch added: Mozilla Bugzilla #1308167 https://bugzilla.mozilla.org/show_bug.cgi?id=1308167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697800 Title: [regression] firefox dies with SIGILL on machines without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] Re: [regression] firefox dies with SIGILL on machines without SSE2
You can trigger a crash immediately on a machine without SSE2 by running firefox 54 like so: firefox https://www.quirksmode.org/html5/videos/big_buck_bunny.mp4 (Note that it must be an mp4 video. VP8 and Vorbis still work fine.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697800 Title: [regression] firefox dies with SIGILL on machines without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] Re: [regression] firefox dies with SIGILL on machines without SSE2
Spoke too soon. Firefox does still die of SIGILL, it just doesn't die immediately. It is still choking on an SSE2 instruction, though, so this is the same bug. Thread 1 "firefox" received signal SIGILL, Illegal instruction. 0xb20eab29 in ?? () from /usr/lib/firefox/libxul.so => 0xb20eab29: 66 0f 6c cc punpcklqdq %xmm4,%xmm1 (gdb) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697800 Title: [regression] firefox dies with SIGILL on machines without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] Re: [regression] firefox dies with SIGILL on machines without SSE2
I tried the version the version just released, 54.0+build3-0ubuntu0.16.04.1, and it appears Firefox is working again on a machine without SSE2. Thank you! I don't see anything in 'apt changelog firefox' describing what was done to fix it, though. Was it recompiled with different flags? This isn't just accidentally working, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697800 Title: [regression] firefox dies with SIGILL on machines without SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697800] [NEW] firefox dies with SIGILL on machines without SSE2
Public bug reported:
I'm running Ubuntu 16.04 on an old laptop. Firefox used to work on
fine until I did an 'apt upgrade'.
Worked: 50.1.0+build2-0ubuntu0.16.04.1
Fails: 53.0.3+build1-0ubuntu0.16.04.2
The bug was a little tricky to track down since AppArmor was killing
firefox. I believe the AppArmor error is irrelevant for this bug
report, but I mention it for completeness (and so other people can
google for this problem):
"/usr/bin/python3: error while loading shared libraries:
cannot apply additional memory protection after relocation:
Permission denied"
I disabled AppArmor (aa-disable '/usr/lib/firefox/firefox{,*[^s][^h]}')
and now Firefox dies like so:
ExceptionHandler::GenerateDump cloned child 14258
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Failed to open curl lib from binary, use libcurl.so instead
Using gdb to figure it out, I see that the process is getting SIGILL
(Illegal Instruction). To figure out exactly which instruction is the
problem, I ran gdb as follows:
$ gdb /usr/lib/firefox/firefox
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
[...]
Reading symbols from /usr/lib/firefox/firefox...(no debugging symbols
found)...done.
(gdb) set disassemble-next-line on
(gdb) run
Starting program: /usr/lib/firefox/firefox
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb15c4b40 (LWP 14296)]
[Thread 0xb15c4b40 (LWP 14296) exited]
warning: Corrupted shared library list: 0xb794cc00 != 0xb794b800
[...]
Thread 1 "firefox" received signal SIGILL, Illegal instruction.
0x4b9f826c in ?? ()
=> 0x4b9f826c: f2 0f 11 74 24 30 movsd %xmm6,0x30(%esp)
MOVSD is an SSE2 instruction, which my machine does not support.
$ grep flags /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
pse36 mmx fxsr sse
I had been under the impression that firefox is supposed to only use
SSE2 if it is available. Is that not correct? It certainly used to
work. Perhaps there is something wrong in how Ubuntu is building the
binary.
[Side note: There are actually two "movsd" instructions for the Intel
x86 architecture. The original one (Move String, opcode A5) is
supported by everything back to the 80386, but this one (Move Scalar,
opcode F2 0F 11) requires SSE2. Maybe that is the source of the
confusion.]
Thank you.
$ lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04
$ apt-cache policy firefox
firefox:
Installed: 53.0.3+build1-0ubuntu0.16.04.2
Candidate: 53.0.3+build1-0ubuntu0.16.04.2
Version table:
*** 53.0.3+build1-0ubuntu0.16.04.2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main i386
Packages
100 /var/lib/dpkg/status
45.0.2+build1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697800
Title:
firefox dies with SIGILL on machines without SSE2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697800/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653691] Re: "Failed with an unknown error" could be more helpful
*** This bug is a duplicate of bug 811516 *** https://bugs.launchpad.net/bugs/811516 Hi Vej, That bug is similar, but I don't think it's a duplicate. In the bug from five years ago, the request is to make the Unknown Error less intimidating by doing things like hiding the traceback. To be clear, this bug is not about the technical implementation of the dialog box. What I was trying to request was a policy change: that the dèjá dup project consider it a high priority problem that end users are too often shown the dreaded Unknown Error. As a mature project, dèjá dup should not need to fall back to debugging info for common situations (e.g., backup directory not writable). Perhaps a milestone for the next revision could be "review common causes of Unknown Error and add error handling code to avoid it." Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653691 Title: "Failed with an unknown error" could be more helpful To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1653691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653691] [NEW] "Failed with an unknown error" could be more helpful
Public bug reported: I used Deja Dup for the first time today. I like that Deja Dup is usable by neophytes and newbies. Unfortunately, when it fails, which it did for me, it leaves a rather sour impression. In particular, I'm referring to Deja Dup's infamous "FAILED WITH AN UNKNOWN ERROR" followed by a wall of debugging information. Please consider that a backtrace (see attached screenshot) can look intimidating to many people and make them think, "Oh, this program is broken in such a serious way it would take a programmer to fix. I'll have to use something else." I understand that sometimes things happen that we haven't coded for and we need to throw a vague exception to help with debugging. But, given how many "Unknown error" messages show up when I Google, it seems Deja Dup doesn't cover some of the basic, common problems that everyday users can fix on their own. For example, the screenshot I attached is of an error that doesn't warrant a backtrace: the user had chosen to backup to a directory which was unwritable. I concede that ideally Deja Dup would hold the user's hand to walk them through figuring out *why* the directory is unwritable, but that's not what I'm asking for. I am requesting that Deja Dup have a policy of never dying with an "Unknown error", unless absolutely unavoidable. I do not expect this to take a lot of extra work or coding. In my example screenshot, Deja Dup could have solved the problem by instead asking the user to choose a different directory. Thank you. ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2017-01-03 03-53-43.png" https://bugs.launchpad.net/bugs/1653691/+attachment/4799413/+files/Screenshot%20from%202017-01-03%2003-53-43.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653691 Title: "Failed with an unknown error" could be more helpful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1653691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645846] [NEW] zramctl fails if called within a certain interval after modprobe zram.
Public bug reported:
On my machine, I can trigger the bug 100% of the time if I do this:
modprobe zram; d=$(zramctl --find) && zramctl --size 256M $d
Here is the error message zramctl emits:
zramctl: /dev/zram0: failed to reset: Device or resource busy
However, the following always work (0% failure)!
modprobe zram; sleep 0.1; d=$(zramctl --find) && zramctl --size 256M $d
modprobe zram; d=$(zramctl --find) && sleep 0.1 && zramctl --size 256M $d
And the following sometimes works and sometimes doesn't:
modprobe zram; d=$(zramctl --find --size 256M)
Chances are about 25% of failure according to this:
for i in {0..99};
do
echo $i;
modprobe -r zram;
modprobe zram;
d=$(zramctl --find --size 256M);
sleep 0.05;
done 2>&1 | grep -c failed
Bizarrely, while putting a long sleep (0.1s) after the modprobe fixes
the problem, putting a short sleep in (0.01s) increases the failure
rate to 95%!
--
for i in {0..99};
do
echo $i;
modprobe -r zram;
modprobe zram;
sleep 0.01# <-- this makes things worse!
d=$(zramctl --find --size 256M);
sleep 0.05;
done 2>&1 | grep -c failed
--
for i in {0..99};
do
echo $i;
modprobe -r zram;
modprobe zram;
sleep 0.10# <-- this completely fixes the problem
d=$(zramctl --find --size 256M);
sleep 0.05;
done 2>&1 | grep -c failed
--
Because of the weird window of time in which this bug occurs, I assume
it is caused by some asynchronous process briefly locking the device
shortly after 'modprobe zram'. I'm guessing zramctl's --find part is
running before the lock but the --size part happens while the device is
in use.
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645846
Title:
zramctl fails if called within a certain interval after modprobe zram.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1645846/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363695] Re: update-apt-xapian-index uses too much CPU and memory
Confirming that this is still a bug in Ubuntu 16.04.1 LTS (Xenial
Xerus). Tested on a Pentium III Mobile 1GHz w/ 1GB ram. (Compaq Evo
N600c).
Also, I note that this bug has been open for seven years and offer a
workaround that solves the problem for me. Since the update-apt-xapian-
index process is needlessly impolite even with nice and ionice, I wrote
a script (called "stutter") that forces the process to pause repeatedly.
(Technically, it uses SIGSTOP/SIGCONT with a 10% active duty cycle and
0.1s period).
It's a kludge, but it definitely works. As I'm posting this comment, I'm
running update-apt-xapian-index in the background. Without my script,
the streaming YouTube video I'm also playing in the background would
have been unwatchably choppy instead of smooth.
To use my solution put the attached script into /usr/local/bin/stutter,
make it executable, and update /etc/cron.weekly/apt-xapian-index to
prepend stutter before the command:
/etc/cron.weekly/apt-xapian-index
#!/bin/sh
CMD=/usr/sbin/update-apt-xapian-index
# ionice should not be called in a virtual environment
# (similar to man-db cronjobs)
egrep -q '(envID|VxID):.*[1-9]' /proc/self/status || IONICE=/usr/bin/ionice
if [ -x "$IONICE" ]
then
IONICE_ARGS="-c 3"
else
IONICE=""
fi
# Check if we're on battery
if which on_ac_power >/dev/null 2>&1; then
on_ac_power >/dev/null 2>&1
ON_BATTERY=$?
# Here we use "-eq 1" instead of "-ne 0" because
# on_ac_power could also return 255, which means
# it can't tell whether we are on AC or not. In
# that case, run update-a-x-i nevertheless.
[ "$ON_BATTERY" -eq 1 ] && exit 0
fi
# If we have B9's stutter utility installed, use it to
# prevent excessive interference with interactive users.
STUTTER=$(which stutter)
# Rebuild the index
if [ -x "$CMD" ]
then
$STUTTER nice -n 19 $IONICE $IONICE_ARGS $CMD --quiet
fi
/usr/local/bin/stutter ====
#!/bin/bash
# stutter: Force a process to pause its work every once in a while.
# v1.0 (c) 2016 hackerb9 - GPLv3 or higher.
#
# Usage: stutter -p PID
#or: stutter command [arguments...]
# Even with the latest Linux (4.4, at the moment) it is possible for
# background processes to rudely prevent interactive use of a
# computer. This is true even with "nice -n 19 ionice -c 3 $CMD".
#
# [Yes, I'm looking at you, update-apt-xapian-index.]
# This kludge repeatedly sends STOP and CONT signals to a process to
# force it to give up the resource (CPU/disk/network) it is hogging.
# A reasonable default is to have the process active for 0.01s and
# sleep for 0.09s. (A 10% duty cycle with a period of 0.1s).
ontime=0.01
offtime=0.09
#verbose=true
debug() {
if [ "$verbose" = "true" ]; then
echo "$@" >&2
fi
}
usage() {
period=$(echo "$ontime + $offtime" | bc)
duty=$(echo "$ontime * 100 / $period" | bc)
cat < | ]
Current defaults
on time: $ontime seconds
off time: $offtime seconds
(A $duty% duty cycle with a period of ${period}s).
EOF
}
cleanup() {
if [ "$pid" ] && ps --pid $pid >/dev/null; then
if [ "$processWasAlreadyRunning" ]; then
if kill -CONT $pid 2>/dev/null; then
debug "Detached from $pid"
fi
else
debug "Killing $pid"
kill $pid 2>/dev/null
fi
fi
trap - EXIT
exit
}
trap cleanup INT QUIT EXIT
if [ -z "$1" -o "$1" = "-h" -o "$1" = "--help" ]; then
usage
exit 1
fi
if [ "$1" = "-p" ]; then
# Attach to existing process
processWasAlreadyRunning=TRUE
pid="$2"
if [ ! "$pid" ]; then usage; exit 1; fi
if kill -STOP $pid; then
debug "Attaching to $pid. Hit ^C to detach."
else
echo "Error: Could not send STOP signal to process ID $pid." >&2
exit 3
fi
else
# Run a new command
"$@" &
pid=$!
if [ "$pid" ] && ps --pid $pid >/dev/null; then
# Note: using ps to check if command was not found or already exited.
debug "Launched command \"$*\" as PID $pid. Hit ^C to kill it."
fi
fi
while :; do
kill -STOP $pid 2>/dev/null || break
sleep $offtime
kill -CONT $pid 2>/dev/null || break
sleep $ontime
done
** Attachment added: "stutter v1.0: Force a process to pause its work every
once in a while"
https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/363695/+attachment/4772138/+files/stutter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/363695/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841909] Re: Pulseaudio does not play in virtual console
I also have this bug, though on a multi-user system. I have one user who likes to play DJ and leave her music running while another is working at the console. Unfortunately, since PulseAudio pauses as soon as they switch accounts they have decided to work around the problem by not switching accounts! As you can imagine this is a much more serious security problem than the one PulseAudio is trying to address by shutting itself off on VT switch. It appears, from Googling, that the preferred method of dealing with this bug is to disable the security features in PulseAudio. Unfortunately, that also disables many other features (again, in the name of security) as documented here: http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ In my opinion, PulseAudio's definition of security needs to be more flexible. There should be some way to specify that some users do have rights to audio devices even if they do not own the current virtual terminal. I liked the way that ALSA did it, using group audio for users with those privileges. PulseAudio really should have an option to allow this model of security. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841909 Title: Pulseaudio does not play in virtual console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/841909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)
Did this ever get fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977804 Title: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/977804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
