[Bug 1645048] Re: nbd-client when started from initramfs (for diskless boot) is not persistent
** Description changed:
When nbd-client is started from initramfs (during the process of a
diskless boot), in order to provide the root filesystem, it is not
persistent. This is because nbd-client is started before run-init, and
later it is not able to find /dev/nbd0 and /sys/block/nbd0/pid anymore
because run-init deleted them.
The nbd scripts for initramfs starts the nbd-client like this:
@sbin/nbd-client NBD_SERVER_IP -N root /dev/nbd0 -swap -persist
-systemd-mark
The -persist option should allow the nbd-client to reconnect if the tcp
session is lost.
Here is a sequence of steps to observe the behaviour;
1. The system is booted ok. nbd-client is active:
root 359 0.2 0.2 4372 2212 ?SL 11:16 0:00
@sbin/nbd-client 10.4.104.4 -N root /dev/nbd0 -swap -persist -systemd-mark
root 362 0.0 0.0 0 0 ?S< 11:16 0:00 [nbd0]
/dev/nbd0 exists:
brw-rw 1 root disk 43, 0 Nov 24 09:19 /dev/nbd0
and the nbd-client process uses it:
root@host:~# ls -l /proc/359/fd/
total 0
lr-x-- 1 root root 64 Nov 24 09:20 0 -> /dev/null
lrwx-- 1 root root 64 Nov 24 09:20 1 -> /dev/console (deleted)
lrwx-- 1 root root 64 Nov 24 09:20 2 -> /dev/console (deleted)
lrwx-- 1 root root 64 Nov 24 09:20 3 -> socket:[9447]
lrwx-- 1 root root 64 Nov 24 09:20 4 -> /dev/nbd0
2. If I restart the nbd-server, the nbd-client dies/exits. The only way
to know what is happening is to strace the nbd-client. This generates a
side effect: when strace is attached, the ioctl exits and nbd-client
tries to reconnect and dies. So by just stracing the nbd-client, i
simulate/force a disconnect/reconnect without any need to restart nbd-
server. My guess is that when i restart the nbd-server, the same happens
(but I just cannot see it). Please observe the behavior:
root@host:~# strace -p 359
strace: Process 359 attached
getpid()= 359
write(2, "nbd,359: Kernel call returned: 1"..., 34) = 34
close(3)= 0
close(4)= 0
write(2, " Reconnecting\n", 14) = 14
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE) = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=359, groups=}, [12]) = 0
sendto(3, "\24\0\0\0\26\0\1\3Y\2606X\0\0\0\0\0\0\0\0", 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"L\0\0\0\24\0\2\0Y\2606Xg\1\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 256
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"H\0\0\0\24\0\2\0Y\2606Xg\1\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 144
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0Y\2606Xg\1\0\0\0\0\0\0", 4096}],
msg_controllen=0, msg_flags=0}, 0) = 20
close(3)= 0
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(10809),
sin_addr=inet_addr("10.4.104.4")}, 16) = 0
setsockopt(3, SOL_TCP, TCP_NODELAY, [1], 4) = 0
! this is the problem:
open("/dev/nbd0", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No
such file or directory)
close(4)= 0
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No
such file or directory)
close(4)= 0
write(2, "Error: Cannot open NBD: No such "..., 59) = 59
exit_group(1) = ?
+++ exited with 1 +++
3. Now, if I have cached the /sbin/nbd-client file before doing the strace
(by doing a cat /sbin/nbd-client > /dev/null), i can restart it again:
root@host:~# /sbin/nbd-client 10.4.104.4 -N root /dev/nbd0 -swap -persist
-systemd-mark
Negotiation: ..size = 32765MB
bs=1024, sz=34357604352 bytes
4. If I strace the newly launched nbd-client, strace will cause a
disconnect, as above, but this time the nbd-client will be able to open
/dev/nbd0 again so it will not die:
strace: Process 1851 attached
write(2, "nbd,1851: Kernel call returned: "..., 35) = 35
close(3)= 0
close(4)= 0
write(2, " Reconnecting\n", 14) = 14
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE) = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=1851, groups
[Bug 1645048] Re: nbd-client when started from initramfs (for diskless boot) is not persistent
Here is an updated patch version, which: a) doesn't mount /dev anymore; just recreates the nbd device with mknod b) mounts /sys only for a second at reconnecting, in order to get the PID of the nbd kernel process,then umounts it back, so it will not hold it mounted. ** Patch added: "improvement of the original patch: doesn't keep /dev/ and /sys mounted twice" https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1645048/+attachment/4783974/+files/nbd-client-patchversion2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645048 Title: nbd-client when started from initramfs (for diskless boot) is not persistent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1645048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645048] Re: nbd-client when started from initramfs (for diskless boot) is not persistent
** Description changed:
When nbd-client is started from initramfs (during the process of a
diskless boot), in order to provide the root filesystem, it is not
persistent. This is because nbd-client is started before run-init, and
later it is not able to find /dev/nbd0 and /sys/block/nbd0/pid anymore
because run-init deleted them.
The nbd scripts for initramfs starts the nbd-client like this:
@sbin/nbd-client NBD_SERVER_IP -N root /dev/nbd0 -swap -persist
-systemd-mark
The -persist option should allow the nbd-client to reconnect if the tcp
session is lost.
Here is a sequence of steps to observe the behaviour;
1. The system is booted ok. nbd-client is active:
root 359 0.2 0.2 4372 2212 ?SL 11:16 0:00
@sbin/nbd-client 10.4.104.4 -N root /dev/nbd0 -swap -persist -systemd-mark
root 362 0.0 0.0 0 0 ?S< 11:16 0:00 [nbd0]
/dev/nbd0 exists:
brw-rw 1 root disk 43, 0 Nov 24 09:19 /dev/nbd0
and the nbd-client process uses it:
root@host:~# ls -l /proc/359/fd/
total 0
lr-x-- 1 root root 64 Nov 24 09:20 0 -> /dev/null
lrwx-- 1 root root 64 Nov 24 09:20 1 -> /dev/console (deleted)
lrwx-- 1 root root 64 Nov 24 09:20 2 -> /dev/console (deleted)
lrwx-- 1 root root 64 Nov 24 09:20 3 -> socket:[9447]
lrwx-- 1 root root 64 Nov 24 09:20 4 -> /dev/nbd0
2. If I restart the nbd-server, the nbd-client dies/exits. The only way
to know what is happening is to strace the nbd-client. This generates a
side effect: when strace is attached, the ioctl exits and nbd-client
tries to reconnect and dies. So by just stracing the nbd-client, i
simulate/force a disconnect/reconnect without any need to restart nbd-
server. My guess is that when i restart the nbd-server, the same happens
(but I just cannot see it). Please observe the behavior:
- root@GTSRO-S-123456:~# strace -p 359
+ root@host:~# strace -p 359
strace: Process 359 attached
getpid()= 359
write(2, "nbd,359: Kernel call returned: 1"..., 34) = 34
close(3)= 0
close(4)= 0
write(2, " Reconnecting\n", 14) = 14
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE) = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=359, groups=}, [12]) = 0
sendto(3, "\24\0\0\0\26\0\1\3Y\2606X\0\0\0\0\0\0\0\0", 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"L\0\0\0\24\0\2\0Y\2606Xg\1\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 256
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"H\0\0\0\24\0\2\0Y\2606Xg\1\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 144
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0Y\2606Xg\1\0\0\0\0\0\0", 4096}],
msg_controllen=0, msg_flags=0}, 0) = 20
close(3)= 0
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(10809),
sin_addr=inet_addr("10.4.104.4")}, 16) = 0
setsockopt(3, SOL_TCP, TCP_NODELAY, [1], 4) = 0
! this is the problem:
open("/dev/nbd0", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No
such file or directory)
close(4)= 0
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No
such file or directory)
close(4)= 0
write(2, "Error: Cannot open NBD: No such "..., 59) = 59
exit_group(1) = ?
+++ exited with 1 +++
3. Now, if I have cached the /sbin/nbd-client file before doing the strace
(by doing a cat /sbin/nbd-client > /dev/null), i can restart it again:
root@host:~# /sbin/nbd-client 10.4.104.4 -N root /dev/nbd0 -swap -persist
-systemd-mark
Negotiation: ..size = 32765MB
bs=1024, sz=34357604352 bytes
4. If I strace the newly launched nbd-client, strace will cause a
disconnect, as above, but this time the nbd-client will be able to open
/dev/nbd0 again so it will not die:
strace: Process 1851 attached
write(2, "nbd,1851: Kernel call returned: "..., 35) = 35
close(3)= 0
close(4)= 0
write(2, " Reconnecting\n", 14) = 14
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE) = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3,
[Bug 1645048] [NEW] nbd-client when started from initramfs (for diskless boot) is not persistent
Public bug reported:
When nbd-client is started from initramfs (during the process of a
diskless boot), in order to provide the root filesystem, it is not
persistent. This is because nbd-client is started before run-init, and
later it is not able to find /dev/nbd0 and /sys/block/nbd0/pid anymore
because run-init deleted them.
The nbd scripts for initramfs starts the nbd-client like this:
@sbin/nbd-client NBD_SERVER_IP -N root /dev/nbd0 -swap -persist
-systemd-mark
The -persist option should allow the nbd-client to reconnect if the tcp
session is lost.
Here is a sequence of steps to observe the behaviour;
1. The system is booted ok. nbd-client is active:
root 359 0.2 0.2 4372 2212 ?SL 11:16 0:00
@sbin/nbd-client 10.4.104.4 -N root /dev/nbd0 -swap -persist -systemd-mark
root 362 0.0 0.0 0 0 ?S< 11:16 0:00 [nbd0]
/dev/nbd0 exists:
brw-rw 1 root disk 43, 0 Nov 24 09:19 /dev/nbd0
and the nbd-client process uses it:
root@host:~# ls -l /proc/359/fd/
total 0
lr-x-- 1 root root 64 Nov 24 09:20 0 -> /dev/null
lrwx-- 1 root root 64 Nov 24 09:20 1 -> /dev/console (deleted)
lrwx-- 1 root root 64 Nov 24 09:20 2 -> /dev/console (deleted)
lrwx-- 1 root root 64 Nov 24 09:20 3 -> socket:[9447]
lrwx-- 1 root root 64 Nov 24 09:20 4 -> /dev/nbd0
2. If I restart the nbd-server, the nbd-client dies/exits. The only way
to know what is happening is to strace the nbd-client. This generates a
side effect: when strace is attached, the ioctl exits and nbd-client
tries to reconnect and dies. So by just stracing the nbd-client, i
simulate/force a disconnect/reconnect without any need to restart nbd-
server. My guess is that when i restart the nbd-server, the same happens
(but I just cannot see it). Please observe the behavior:
root@GTSRO-S-123456:~# strace -p 359
strace: Process 359 attached
getpid()= 359
write(2, "nbd,359: Kernel call returned: 1"..., 34) = 34
close(3)= 0
close(4)= 0
write(2, " Reconnecting\n", 14) = 14
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE) = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=359, groups=}, [12]) = 0
sendto(3, "\24\0\0\0\26\0\1\3Y\2606X\0\0\0\0\0\0\0\0", 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"L\0\0\0\24\0\2\0Y\2606Xg\1\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 256
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"H\0\0\0\24\0\2\0Y\2606Xg\1\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 144
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0Y\2606Xg\1\0\0\0\0\0\0", 4096}],
msg_controllen=0, msg_flags=0}, 0) = 20
close(3)= 0
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(10809),
sin_addr=inet_addr("10.4.104.4")}, 16) = 0
setsockopt(3, SOL_TCP, TCP_NODELAY, [1], 4) = 0
! this is the problem:
open("/dev/nbd0", O_RDWR) = -1 ENOENT (No such file or directory)
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No such
file or directory)
close(4)= 0
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No such
file or directory)
close(4)= 0
write(2, "Error: Cannot open NBD: No such "..., 59) = 59
exit_group(1) = ?
+++ exited with 1 +++
3. Now, if I have cached the /sbin/nbd-client file before doing the strace (by
doing a cat /sbin/nbd-client > /dev/null), i can restart it again:
root@host:~# /sbin/nbd-client 10.4.104.4 -N root /dev/nbd0 -swap -persist
-systemd-mark
Negotiation: ..size = 32765MB
bs=1024, sz=34357604352 bytes
4. If I strace the newly launched nbd-client, strace will cause a
disconnect, as above, but this time the nbd-client will be able to open
/dev/nbd0 again so it will not die:
strace: Process 1851 attached
write(2, "nbd,1851: Kernel call returned: "..., 35) = 35
close(3)= 0
close(4)= 0
write(2, " Reconnecting\n", 14) = 14
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE) = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=1851, groups=}, [12]) = 0
sendto(3, "\24\0\0\0\26\0\1\3.\2646X\0\0\0\0\0\0\0\0", 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(3, {msg_name(12)={sa_fam
[Bug 827856] Re: Xorg crash with Nvidia and newer kernels
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827856 Title: Xorg crash with Nvidia and newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/827856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827856] [NEW] Xorg crash with Nvidia and newer kernels
Public bug reported: I have encountered a very strange problem, which I'm not sure where to file exactly. The problem manifests on Dell notebooks (Latitude E6520 or E6510). They are using NVIDIA NVS3100m or 4200m video cards. The problem itself is that most of the time the flash plugin crashes. Not so often, the whole firefox session crashes. Sometimes the whole X session crashes. A few times, the X session also crashed while starting Libre Office Calc. Now, when it happens: it happens when using Ubuntu 10.10 or newer, or when using Ubuntu 10.04 with a newer kernel (2.6.35, or 2.6.38). It happens with any flash version, any firefox version, any NVidia drivers version (including the newest 280 one). I haven't tried different Libre Office versions, but this is not so relevant, as it doesn't happen so often. Most probably, the problem lies somewhere between the linux kernel, the X server and the NVidia driver, in some drawing operations. The system is 100% stable when using 10.04 with kernel 2.6.32 (but then I have to compile some e1000e drivers by hand, and bluetooth is not 100% working on this hardware). I am not sure what kind of data to further collect, but I will provide whatever you need in order to identify and fix the bug. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-34.73-generic-pae 2.6.32.44+drm33.19 Uname: Linux 2.6.32-34-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed Aug 17 10:59:28 2011 DkmsStatus: InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1) MachineType: Dell Inc. Latitude E6520 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic-pae root=UUID=5d0d1a73-b280-4968-91af-ca8e4822bdbb ro quiet splash nomodeset video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash dmi.bios.date: 05/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/24/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-34-generic-pae ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug crash i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827856 Title: Xorg crash with Nvidia and newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/827856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367080] Re: Acrobat Reader SIGSEGV when embedded in Firefox
Firefox doesn't crash. Acroread crashes (for example, if you would have had two tabs with PDF documents, closing the first one might have killed also the second one - it would have became a tab with no content). -- Acrobat Reader SIGSEGV when embedded in Firefox https://bugs.launchpad.net/bugs/367080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367080] Re: Acrobat Reader SIGSEGV when embedded in Firefox
If I close all the "dead" acroread tabs, and then open a PDF again, firefox starts acroread from the scratch and everything works again for a short while. For example, in case (b) - navigating from PDF to PDF, I click the link, the tab dies, I copy the URL, close the tab, open a new tab again and paste the url back, getting to the next page. -- Acrobat Reader SIGSEGV when embedded in Firefox https://bugs.launchpad.net/bugs/367080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367080] Re: Acrobat Reader SIGSEGV when embedded in Firefox
Please try one of the following scenarios: a). Open two PDF files at the same time, in two tabs. Close one of the tabs. Is the other tab still functional? In my case the second tab will be empty (with no acroread instance inside it). Example (just by random search on google for PDF files): open http://www.un.org/Depts/Cartographic/map/profile/romania.pdf open http://www.ecb.int/ecb/legal/pdf/l_02120090124ro00660068.pdf close the http://www.ecb.int/ecb/legal/pdf/l_02120090124ro00660068.pdf tab the http://www.un.org/Depts/Cartographic/map/profile/romania.pdf still looks ok (not sure why, usually it was crashing at this step) open http://www.ancex.ro/old_ancex/ATT00156.pdf result: both pdf tabs are freezed (empty, with no content inside) b) Find a PDF that has links to other PDF files. Unfortunately I cannot give you an example site for this, because the only example I know is a private site with some equipment documentation. When I navigate through the links, after 1-2 links it crashes. I was encountering this issue with 8.10 also, but never took time to study enough or file a bug. But on 8.10 it was happening a lot faster (always from the closing of the second tab, or clicking on the first link, never later). -- Acrobat Reader SIGSEGV when embedded in Firefox https://bugs.launchpad.net/bugs/367080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367080] Re: Acrobat Reader SIGSEGV when embedded in Firefox
I have tried with two different versions/sources: 1) 8.1.3-0medibuntu0.8.10.2 from medibuntu - with mozilla-acroread 2) acroread 9.1.0 from adobe's website, registering the plugin by hand with nspluginwrapper -i /opt/Adobe/Reader9/Browser/intellinux/nppdf.so; the trace was from the 9.1.0 version (never tried to trace the 8.10.2 version because the first obvious idea was to upgrade, but the behavior was the same). -- Acrobat Reader SIGSEGV when embedded in Firefox https://bugs.launchpad.net/bugs/367080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367080] [NEW] Acrobat Reader SIGSEGV when embedded in Firefox
Public bug reported: Binary package hint: acroread When I open a PDF link from Firefox, and the document is opened by acroread embedded into the browser tab, I have encountered two ways to crash acroread: 1) by clicking on a link in the PDF file, that would normally open another PDF from the website 2) by having multiple acroread tabs in Firefox, and closing one of the tabs. In both cases, the acroread process dies and if there were other tabs with acroread in them, they are also affected. I attached a gdb to the acroread process before performing action (1) and the results were: (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xf55fe720 (LWP 16795)] 0xf685d819 in gdk_window_get_position () from /usr/lib32/libgdk-x11-2.0.so.0 (gdb) Continuing. Program exited with code 01. (gdb) The problem is related to the amd64 version, as I was not able to reproduce it on the i386 distribution. ** Affects: acroread (Ubuntu) Importance: Undecided Status: New -- Acrobat Reader SIGSEGV when embedded in Firefox https://bugs.launchpad.net/bugs/367080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299483] Re: Firefox crashed on printing page.
** Changed in: firefox-3.0 (Ubuntu) Status: Triaged => In Progress ** Changed in: firefox-3.0 (Ubuntu) Status: In Progress => Confirmed -- Firefox crashed on printing page. https://bugs.launchpad.net/bugs/299483 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299483] Re: Firefox crashed on printing page.
Are there any news about this bug? Is there any workaround available? -- Firefox crashed on printing page. https://bugs.launchpad.net/bugs/299483 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157288] Re: [network-admin] wpa-psk passphrases with spaces not written to interfaces file
I can confirm the bug behavior. Adding "" indeed fixes the problem. -- [network-admin] wpa-psk passphrases with spaces not written to interfaces file https://bugs.launchpad.net/bugs/157288 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
