I recompiled version 2.7 from source on my ARM64 machine and the bug was
still there.
I downloaded the orig/deb tarball for version 3.0 from rspamd repository
at http://rspamd.com/apt-stable/ and recompiled from source. Things are
now going well. rspamd runs fine on ARM64.
--
You received this
I also installed rspamd on an amd64 machine, with the rest of the setup
being identical and I don't have a single issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947495
Title:
Rspamd
Following rspamd FAQ, I created a core folder:
mkdir /coreland
chmod 1777 /coreland
and activated core dumps using:
sysctl kernel.core_pattern=/coreland/%e-%p.core
sysctl kernel.core_uses_pid=1
sysctl fs.suid_dumpable=2
but even on segfaults, no core appears in /coreland.
--
You received
This is on Impish, on an ARM64 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947495
Title:
Rspamd segfaults on ARM64
To manage notifications about this bug go to:
Public bug reported:
This is what appears in the rsmpad log:
rspamd_crash_sig_handler: caught fatal signal 11(Segmentation fault), pid:
10140, trace:
2021-10-17 13:21:41 #10140(normal) rspamd_print_crash: 0: 97C5FA78:
2021-10-17 13:21:41 #10140(normal) rspamd_print_crash: 1:
Dear Joseph,
Sorry for the latency. I only read this account one or twice a week at
most.
I just upgraded to 4.10.0-15 and the problem disappeared. The module is
now inserted in the kernel when I boot.
Thanks for your help,
Thomas
Le 03/04/2017 à 10:51, Joseph Salisbury a écrit :
> Would it
** Description changed:
I just upgraded my yakkety machine to zesty. For the moment, the only
issue I see is that the Wifi chipset (a Broadcom Limited BCM43224, see
pci information below) is not detected and the module in charge of the
device (brcmsmac) not inserted in the kernel. This is
** Description changed:
I just upgraded my yakkety machine to zesty. For the moment, the only
issue I see is that the Wifi chipset (a Broadcom Limited BCM43224, see
pci information below) is not detected and the module in charge of the
device (brcmsmac) not inserted in the kernel. This is
Public bug reported:
I just upgraded my yakkety machine to zesty. For the moment, the only
issue I see is that the Wifi chipset (a Broadcom Limited BCM43224, see
pci information below) is not detected and the module in charge of the
device (brcmsmac) not inserted in the kernel. This is on a 2011
I have the same problem under yakkety / 2.02~beta2-36ubuntu11: message
"error: no symbol table".
Solved in
https://lists.gnu.org/archive/html/grub-devel/2016-02/msg00011.html
which probably refers to the same commit that Mathieu cites.
--
You received this bug notification because you are a
Same here, bug present in Ubuntu 16.04 beta1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432271
Title:
[vivid] Abiword always starts after logging in
To manage notifications about this bug go
Actually, applying the patch available at
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402
did not help.
After a full resync leading to a clean disk and a reboot... ity resyncs
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
I just installed the latest wily on my machine. Since then, my mdadm imsm raid1
array resyncs at every boot.
I suspect the array metadata is not set to "clean" state at reboot.
This looks very much like
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402
I will
I agree that Repetier Host + Slic3r is a priority.
I successfully installed RepetierHost (manually) but failed to setup Slic3r on
my Ubuntu 14.04 box (version mismatch here).
I now run...window$ on a laptop to control my 3D printer. A shame :-/
Will probably install Fedora that looks better
Back home...
sudo grub-probe -t partmap /
msdos
And the results of running bootinfoscript are attached below.
Please note the the workaround of Liny works fine, adding the part_msdos module
does save me (and this raid machine is BIOS, not EFI).
Thanks for your work.
Kind regards
Thomas
**
Le vendredi 05 octobre 2012 à 17:41 +, Phillip Susi a écrit :
I'm confused beacuse you mentioned raid before, but you appear to only
have a single disk setup with no raid. Have this changed since you
originally reported the bug?
Sorry Phillip,
I apparently was to eager to answer you
Systematic crash after equation editing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1042187
Title:
soffice.bin crashed with SIGSEGV in g_main_context_dispatch()
To manage notifications about
Yes, of course. Here is the output of
sudo grub-probe -t partmap /
gpt
And the results of running bootinfoscript are attached below.
Please note the the workaround of Liny works fine, adding the part_msdos
module does save me (despite the expected gpt partition table - I'm
running on en
This bug is still there... in Precise Pangolin and in the beta1 of
Quantal Quetzal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852579
Title:
Grub does not access /boot/grub under fakeraid
To
Got this when I moved the mouse in the Activities corner. Screen
freeze, gnome-shell restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962298
Title:
gnome-shell crashed with SIGSEGV in
In my case, the bug occurred as I recompiled a latex document in PDF
while evince was open.I asume this is the same bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882038
Title:
evince crashed
Public bug reported:
I report this strange bug as an evolution bug, but it may also be in
xserver-xorg or xserver-xorg-input-evdev bug.
Hard to guess for me.
I use a laptop with a multitouch trackpad and a bluetooth apple mouse
(which is therefore plugged after X has started).
For
Public bug reported:
I got this crash report while I was updating my distribution using
synaptic. not sure it is correlated anyway.
ProblemType: Crash
Date: Wed Feb 22 11:07:07 2012
ExecutablePath: /usr/bin/update-manager
ExecutableTimestamp: 1326448883
InterpreterPath: /usr/bin/python2.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942439
Title:
update-manager crashed with ValueError in ./xorg_fix_proprietary.py:
_system not initialized
To manage notifications about this bug go
Here it is:
sudo grub-probe -t partmap /
msdos
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935839
Title:
grub2 lacks the msdos_part preload module, preventing access to
fakeraid devices
To
No separate /boot partition.
Reinstalling grub without the modules arg did work fine.
This probably means that the installation of grub during the upgrade did not
behave exactly in the same way as this very last install.
Actually, if I remember correctly, the windows 7 OS (on another dmraid
To avoid having to type this at each boot, you may edit
/usr/share/initramfs-tools/scripts/local-top/dmraid
and add a
dmraid -ay
there
Beyond this, I had another problem:
GRUB2 seems to lack the part_msdos preload module. I had to
grub-install --modules=part_msdos --boot-directory=...
Public bug reported:
I use fake-raid and after upgrade to Precise Pangolin I just hit a grub
rescue screen upon reboot.
After a liveCD boot and a chroot to the /dev/mapper/isw... linux
partition, I had to
grub-install --modules=msdos_part
to avoid this problem.
** Affects: grub2 (Ubuntu)
This bug has bad side-effects on others applications that use utmp. Of
course thismeans users and who are not correct but the timekpr is also
affected making parental control unavailable in xubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
After the last update of grub-pc under oneiric beta, I could not reboot and
fell under grub rescue mode.
The only accessible disc under grub rescue 'ls' was (hd0), claimed to be of
'unknown filesystem'. A reboot under a natty
rescue disc shows that all disk partitions are
I have the same problem under 10.10, kernel 2.6.35-22.34.
There seems to be some bad interaction between Windows and Linux (my lan chip
is sometimes asleep under linux, then also under windows. Cold boot makes
everythink ok again).
Installing the r8168 driver from realtek (unknown LICENCE)
I have a related error with this applet but with an IndexError rather
than a type error. This occurs when I try to empy the trash. A dialog
appears. When I click Empty trash, the error pops up.
I installed the PPA version (3.3), killed the previous awn and restarted
one by hand. The same error
I confirm Korey's observation on the same platfrom: XPS 1340 (so-called
XPS studio 13) with an AR928X wireless controller: connection was a
nightmare but stable once established. After installing linux-backports-
modules-jaunty, connection works like a charm but may break from time to
time.
OK. I've got it !
The problem is powernowd
Boot in recovery mode, go to /etc/init.d and move the two files
mv powernowd powernowd.off
mv powernowd.early powernowd.early.off
exit and resume... It worked for me !
Thomas
--
kernel-panic ubuntu 9.04
https://bugs.launchpad.net/bugs/329976
You
Of course this is not ideal for the laptop users as this turns down
frequency scaling...
Considering that jtappin is, as myself, using an Nforce2 based
motherboard, this suggest a fishy cpufreq scaling on nforce2
motherboards.
Thomas
--
kernel-panic ubuntu 9.04
Disabling or removing network-manager has no effect on my system either.
It still freezes.
My install of Jaunty is a fresh install. Not an upgrade from Intrepid.
So, if this bug is a leftover, it is a leftover of Jaunty alpha 4 or 5
(as far as I remember.)
If I find some time, I will try a
*** This bug is a duplicate of bug 329976 ***
https://bugs.launchpad.net/bugs/329976
The freeze still occurs on 2.6.28-9 and 2.6.28-11 with the same panic
and a double fault. Apparently I am not the only person affected. See:
http://ubuntuforums.org/showthread.php?t=1077496
** This bug has
*** This bug is a duplicate of bug 329976 ***
https://bugs.launchpad.net/bugs/329976
Marked as duplicate of 329976.
--
kernel oops in linux-2.6.28-8
https://bugs.launchpad.net/bugs/336003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have the very same locking problem on my AMD/ATI machine with same
Double fault panic. Continues through all revisions of 2.6.28-8 to
date (11).
I already posted a bug on launchpad (336003) and therefore marked it as
duplicate of this one.
--
kernel-panic ubuntu 9.04
Using the standard boot line, there is a total freeze few seconds after
gdm starts. I have enough time to type 3 or 4 letters to login then -
total freeze (CTL-ALT-F1 or CTRL-ALT-DEL do not work).
If I shift back fast enough to console (CTL-ALT-F1) once gdm has
started, then I can observe the
A mistake in my previous post: the radeon driver is used, not fglrx.
--
kernel oops in linux-2.6.28-8
https://bugs.launchpad.net/bugs/336003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: linux-image-2.6.28-8-generic
The kernel image 2.6.28-8 oops on boot on my machine. It reaches GDM and
freezes (systematic).
Booting in recovery mode shows a kernel oops. Syslog/message files keep no
trace of this.
** Affects: linux (Ubuntu)
Bug also present here with my noname USB HDD that worked fine under
Hardy Heron.
This thread may help perhaps help the Ubuntu Kernel Team:
http://www.gossamer-threads.com/lists/linux/kernel/987514
--
USB Hard Drive Not Accessible
https://bugs.launchpad.net/bugs/264789
You received this bug
Public bug reported:
Binary package hint: xemacs21-mule
xemacs21-mule (and xemacs21-gnome-mule BTW) crash on startup on the
Hardy Heron, amd64 version. The nomule version works fine but many
people, including I, need the special characters of the mule version.
The i386 version runs fine also,
I confirm this too on a Feisty Fawn. But it does not seem related to
multi-partition not to owneership problems.
My USB hard drive with a single ext3 partition is mounted automatically
but then it cannot be ejected without being immediately remounted. Owner
of the corresponding directory in
I got the same bug. Upon receiving a H323 call, and after having
accepted the call, Ekiga crashes in the same funtion.
--
[apport] ekiga crashed with SIGSEGV in H323_RTPChannel::OnSendingPDU()
https://bugs.launchpad.net/bugs/88976
You received this bug notification because you are a member of
Confirmed. Boot delay seems related to DHCP timeout on eth1 (wireless)
for unknown reasons.
--
Feisty boot hangs on Configuring network interfaces
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
On upgrade from edgy to feisty beta using the update-manager.
ProblemType: Package
Date: Wed Mar 28 19:28:53 2007
ErrorMessage:
ErrorMessage: le sous-processus post-installation script a retourné une erreur
de sortie d'état 1
Package: python-mutagen
SourcePackage: mutagen
AFter deleting files in the python-mutagen directory, evrything went
smoothly. I'm a bit ashamed, I guess I moved files by hand there some
time ago.
--
[apport] package python-mutagen failed to install/upgrade:
https://bugs.launchpad.net/bugs/97516
You received this bug notification because you
I have got the same (segfault) on startup. This is a copy of the
terminal:
onboard
GTK Accessibility Module initialized
Segmentation fault (core dumped)
Exit 139
This is
ii onboard0.82
Simple On-screen Keyboard
I attach the crash file.
** Attachment
It has started again.
** Attachment added: crash report
http://librarian.launchpad.net/4703706/_usr_bin_xrdb.1023.crash
--
xrdb crashes on startup
https://launchpad.net/bugs/63611
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
After update/upgrade on October 3rd, the crash disappeared.
Close ?
--
xrdb crashes on startup
https://launchpad.net/bugs/63611
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Nothing special. Just a warning from the system about the fact that xrdb
crashes.
This on an edgy beta obtained after upgrading from a Dapper.
Everything fine otherwise.
** Affects: xrdb (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
xrdb crashes on
** Attachment added: Crash file
http://librarian.launchpad.net/4615315/_usr_bin_xrdb.1023.crash
--
xrdb crashes on startup
https://launchpad.net/bugs/63611
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
54 matches
Mail list logo
