Unfortunately, not really
I can argue on why we use Trusty: as we deploy storage software which
runs for years in controlled environment, we never upgrade OSes to new
releases. Our older platforms are still on Trusty and that makes sense
to me.
But that doesn't make an argument to why they
Hi Brian,
The crash doesn't occur with your PPA packages (2.4.7-1ubuntu4.19)
To be more precise: it systematically crash on 1 run of the reproducer without
your PPA, and i dont have crash with 10 runs of the reproducer on your PPA. I
didnt test further but it sound reasonable to me so far.
Hi Andreas, thanks for your update !
For your initial question: we initially reproduced on docker containers,
yes. I just tried on a VM with the same procedure and i could reproduce
the issue so it doesnt seems related to container environment
--
You received this bug notification because you
Private bug reported:
I was trying to connect multiple operations as internal moves (moving
money from one my account to another) and it crashed
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: homebank 5.1.5-1build1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux
Hi,
I described how it happened for me on my duplicate #1727446 but i can't
reproduce it doing the same steps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726494
Title:
nautilus crashed with
Got a very similar issue here, except:
- i was using Xorg
- i didnt used the UI, but used a script which does a 'dconf write
/org/gnome/desktop/interface/text-scaling-factor 1.5'
Same caller:
#0 0x7f665c6c3877 in meta_workspace_get_work_area_for_monitor () at
Hi Brian,
Here is the requested config output if it helps
Were you able to reproduce with the docker containers ?
Christophe
# apache2ctl -M
AH00558: apache2: Could not reliably determine the server's fully qualified
domain name, using 172.17.0.6. Set the 'ServerName' directive globally to
Here is the Xenial version which does *not* reproduce the issue,
hopefully :)
(docker build -t apache-1630413 . && docker run apache-1630413 bash
/root/run.sh)
** Attachment added: "apache2-1630413-docker-xenial.tgz"
Hi Brian,
Check the attached archive, i did a small dockerfile so you see what i
exactly install in it, and hopefully could reproduce it
cd
docker build -t apache-1630413 .
docker run -it apache-1630413
# in container:
service php5-fpm start && service apache2 start
curl localhost/50M.php |
Previous archive was missing content, here is the right one
Dont forget to generate the 50M file in /tmp as i doesnt seems to
trigger the bug if the content if not big enough
** Attachment added: "php-test.tgz"
Hi Brian,
Some news:
I tried to reproduce the crash with php5-fpm as a backend of fastcgi. I
ran the same test on a php file doing a readfile() on a 50MB file again
and i can reproduce the crash systematically !
Here is the script and config file attached
Nothing particular, used php5-fpm
I would have wanted to provide the full chain of the reproducer, but
days has already passed, here is the information i can provide for now:
I reproduce the crash with a simple:
rm failed; for i in $(seq 200); do (curl -qo /dev/null "$URL" || touch failed)
& done
A single run usually is
Hi Brian,
I finally did some functional testing
With 2 differents clients (!= IPs), i started on each of them 100
parrallel GETs, targeting 3 different files. I ran this in a loop with
some randomness for an hour and it didnt raised any crash nor
consistency mismatch on thoses fetched files
I
Good news, it seems good this time !
I almost always reproduced the segfault with a single run of my script
(which spawn 200 parrallel requests on a file on our daemon behind
fastcgi). Once i had to run it twice to reproduce.
With your last version, i didnt had any crash for 100 consecutives
Sure! Tried with your PPA, still got a segv
Program received signal SIGSEGV, Segmentation fault.
process_socket (my_thread_num=2, my_child_num=,
cs=0x7fd636a032a8, sock=, p=, thd=) at event.c:1066
gdb) bt full
#0 process_socket (my_thread_num=2, my_child_num=,
cs=0x7fd636a032a8, sock=, p=,
Hi Brian,
Thanks for your fast answer and apologies for my delay
Unfortunately, i reproduced a similar crash on trusty-backports version
Not exactly the same though:
ii apache2
2.4.10-1ubuntu1.1~ubuntu14.04.2 amd64
Core from previous comment.
** Attachment added: "core.26498.bz2"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1630413/+attachment/4933814/+files/core.26498.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We also encountered this issue with 2.4.7-1ubuntu4.17
I can reproduce it from times to times with a light parralel load (50-200
requests in //)
Here is some details:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f811d7fa700 (LWP 26536)]
process_socket
*** This bug is a duplicate of bug 1458322 ***
https://bugs.launchpad.net/bugs/1458322
** This bug has been marked a duplicate of bug 1458322
NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
--
You received this bug notification because you are a member of Ubuntu
I was also affected by this issue on a quite fresh 15.10
Version: 1.4.35-4ubuntu1
Provides: httpd, httpd-cgi
Depends: libattr1 (>= 1:2.4.46-8), libbz2-1.0, libc6 (>= 2.15), libgamin0 |
libfam0, libldap-2.4-2 (>= 2.4.7), libpcre3, libssl1.0.0 (>= 1.0.0), zlib1g (>=
1:1.1.4), init-system-helpers
Same here, since upgrade to 15.04. I dont have Gajim autostarted but everytime
i start it manually, the system freeze as described by Lesik.
I'm using Cinnamon.so it seems to confirm its not related to desktop env.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It trigger a kernel oops:
Note the: CPU: 0 PID: 2354 Comm: gajim Tainted: P OE
3.19.0-16-generic #16-Ubuntu
May 7 10:50:40 Laptop-cm kernel: [ 28.446592] BUG: unable to handle kernel
NULL pointer dereference at 0293
May 7 10:50:40 Laptop-cm kernel: [ 28.447134] IP:
I had the same problem with a MS scult confort mouse on an up to date
saucy (with gnome-bluetooth=3.8.1-2ubuntu2)
Proposed fix:
/usr/share/gnome-bluetooth/pin-code-database.xml:
device oui=xx:xx:xx: type=mouse pin=/
followed by a reboot didnt helped
But installing blueman as suggested
Since this report, i have upgraded to 11.10 and i havent hit the problem since
then, it seems fixed.
Im currently using lightdm, i will test with gdm in the next days if it can
helps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same probleme here with 10.04. Still present after upgrade to 11.04
I agree with Thibouf, its pretty annoying and makes most terminal commands
headaches.
I can provide details/commands output too if needed, just ask.
--
You received this bug notification because you are a member of Ubuntu
25 matches
Mail list logo
