Public bug reported:
"Install RELEASE" Icon appeared and persisted on the dock after a fresh
install of Ubuntu 20.10. The system is dual booting with Windows 10.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13.1
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
I've submitted a PR
https://lore.kernel.org/linux-media/20210102101209.ga32...@gofer.mess.org/T/#t
This has to be merged by Mauro (linux-media). Then Linus has to merge it.
Finally, it needs to be merged into the stable tree. So it may be some time.
--
You received this bug notification
Thank you @wesnewell and @kaihengfeng for testing this!
Now that we know the patch works, I'll send the patch upstream and it'll
be included in the stable kernels as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for that.
It seems very possible that this issue is solved by this patch:
https://patchwork.linuxtv.org/project/linux-
media/patch/20201221091929.26504-1-s...@mess.org/
Would you be able to test this patch please? There are instructions for
compiling the kernel here.
Thanks for that. It looks like on 5.8.8 it has not loaded the rc keymap
at all. It looks like a default mce keymap with the default rc-6
protocol enabled.
So for some reason /etc/rc_map.cfg did not get processed at all. That's
super odd. Let's try and see what udevd does when you plug in the
Actually you said "on newer systems it does not enable the nec
protocol". That is odd.
what is the output of ir-keytable on newer (broken) systems?
also what is the kernel config on broken systems (not sure how to see that on
ubuntu)
--
You received this bug notification because you are a
Thank you for that.
With evtest I mean the evtest tool from the evtest package:
https://packages.ubuntu.com/focal/evtest
when you run ir-keytable there is an line which says "Input device:
/dev/input/event..". Use that as an argument to evtest:
evtest /dev/input/event19
There will be some
Hello, the author of those commits here. It's not clear to me how those
commits broke things. Either something else changed, or there is
something subtle going on.
The following bits of information would be very useful.
1. Is the issue intermittent or consistent, i.e. does booting with a new
Sorry for the delayed response.
It's been a while since I did this, but how I debugged this was adding
-g -rdynamic to the build options to insure that GCC would not strip
symbols needed to backtrace, as well as using nostrib in the
DEB_BUILD_OPTIONS so that debian's build script thing wouldn't
Public bug reported:
Just switching to another window and Gnome System Monitor crashed.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-system-monitor 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
NonfreeKernelModules:
Public bug reported:
Happened when I opened chromium's proxy settings?
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.2-0ubuntu0.13.1
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
NonfreeKernelModules: nvidia
Public bug reported:
Downloading a bunch of semi-big files.
This text appeared right before the segfault (likely the assertion error
causing this)
CUID#70 - Download aborted.
URI=http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/pool/main/w/wine1.7/wine1.7-amd64_1.7.9-0ubuntu1~precise1_amd64.deb
*** This bug is a duplicate of bug 980748 ***
https://bugs.launchpad.net/bugs/980748
Public bug reported:
Some of the status icons in the panel were blank, which came back after
this crash.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2ubuntu0.1
Well, the crashes are now much, MUCH, rarer, I just got one. (First time
since I got Rolf's branch of it).
Sadly, as it was compiled without symbol tables, the stack trace was
pretty much useless. Should I rebuild with symbols so I can get a useful
stacktrace?
--
You received this bug
Public bug reported:
The crash most likely occured while it was running one of the virtual
machines in the BOINC project LHC@home, Test4Theory sub-project which
uses virtual machines running in the headless VirtualBox client.
May be related to the many other SIGSEGVs reported for VirtualBox
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226968
Title:
nvidia-settings crashed with SIGSEGV in XCloseDisplay()
To manage notifications
Alright, recompiled with libsegfault as one of the included libraries
(forcing better line numbers in dumps), and got the line number of the
assertion failure, chunk.c:398:dispose_chunk.
Line numbers for the whole stack still aren't showing up (ugh), but I
can see that it is happening when it is
Alright, recompiled with libsegfault as one of the included libraries
(forcing better line numbers in dumps), and got the line number of the
assertion failure, chunk.c:398:dispose_chunk.
Line numbers for the whole stack still aren't showing up (ugh), but I
can see that it is happening when it is
Also, when you are not compiling with debug flags, are the asserts
disabled? If so, the derefence of that null pointer could explain why
some people see segfaults instead of assertion failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Ubuntu version:
Description:Ubuntu 12.04.2 LTS
Release:12.04
Polipo version 1.0.4.1-1.1
With index fix patch in bug #988780
Compiled with -g and -rdynamic
Well, like many others, I got the (or rather, a) random crash bug.
So, I went ahead and compiled it with
I will also try to see if I can upload a patch implementing the
suggested workaround for chunk.c, until the true reason for the bug is
found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168593
Or is it not even reaching the disk?
(dang it, why can't I edit my comments)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055418
Title:
polipo constantly clears out the cache
To manage
All of the RAM cache is dumped to disk spuriously?
Yea, that would be a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055418
Title:
polipo constantly clears out the cache
To manage
Sorry for the bump, but I think this behavior is intentional.
Polipo tries to write out entries from memory to disk every now and then until
it hits the chunkLowMark in memory usage.
You can tune how aggressively it does so by playing with the optoins
maxObjectsWhenIdle and maxWriteoutWhenIdle.
Public bug reported:
Happened when installing the update for libreoffice on Ubuntu 12.04
Similar issues for the libreoffice-calc, libreoffice-base, et al
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libreoffice-writer 1:3.5.3-0ubuntu1
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994343
Title:
package libreoffice-writer 1:3.5.3-0ubuntu1 failed to install/upgrade:
short read on buffer copy for backend dpkg-deb during
Thanks. I was wondering if it was a corrupted download, but as there
were no checksum failures flagged, so I thought I should go ahead and
report it anyways.
Will try this again after the clean, and If I still get this even after
a redownload, I'll reopen this bug.
--
You received this bug
I've submitted a different patch upstream for the Super Joy Box 5 Pro,
amongst others. This patch also enable force feedback.
http://www.spinics.net/lists/linux-input/msg17851.html
This patch been accepted into the for-next branch.
28 matches
Mail list logo
