[Bug 294648] Re: svn over https with client certificates broken (regression in intrepid)
There is a workaround described in the comments to https://bugs.launchpad.net/hardy-backports/+bug/265065, to use a PKCS#12 file without a CA certificate in it. However, I tried this and cannot get it to work. -- svn over https with client certificates broken (regression in intrepid) https://bugs.launchpad.net/bugs/294648 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 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid)
Daniel T Chen wrote on 2008-09-14: > Is this symptom still reproducible in 8.10 alpha? Reproduced in 2.46+dfsg-4 (intrepid). I updated the bug description to reflect that. Is there something else needed to get the bug status to not be "incomplete"? -- insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid) https://bugs.launchpad.net/bugs/6671 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 245776] Re: cant run installation program
I have got this a couple of times with PDF files. The file is downloaded, it can be found intact in the tmp directory, but it will not open with the default Document viewer. IIRC, explicitly selecting a viewer (/usr/bin/xpdf of /usr/bin/evince) opened the document fine. Right now I cannot reproduce the problem exactly, but can get similar results: 1. Create a new firefox profile for testing and use that. 2. Browse to a pdf document that is served using an unknown, wrong content-type, e.g., 'application/x-foobar'. 3. Select "Open with Document Viewer (default) -> Gives error message "/tmp/test.pdf could not be opened, because the associated helper application does not exist. Change the association in your preferences." 4. Doubleclick (or select retry) for the entry in the download manager -> Gives the error message: "/tmp/test.pdf could not be saved, because you cannot change the contents of that folder." FF3 is giving the wrong error message here. Probably the same applies to the original problem. There is of course nothing that ties this to some specific file type like pdfs or debs. I am attaching a simple python script to easily serve files in the current directory using whatever content-type. Use it like: MIMETYPE=application/x-foobar python mthttpserver.py and then browse to http://localhost:8000/ On a side note, why does FF3 offer the default viewer when it knows there is no associated helper? ** Attachment added: "http server script for mime-type testing" http://launchpadlibrarian.net/18885068/mthttpserver.py -- cant run installation program https://bugs.launchpad.net/bugs/245776 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 294648] Re: svn over https with client certificates broken (regression in intrepid)
I now found https://bugs.launchpad.net/hardy-backports/+bug/265065 which seems to be the same issue. -- svn over https with client certificates broken (regression in intrepid) https://bugs.launchpad.net/bugs/294648 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 294648] [NEW] svn over https with client certificates broken (regression in intrepid)
Public bug reported: Binary package hint: subversion After upgrading from hardy to intrepid, svn with https client certificates authentication stopped working, giving the following error: [EMAIL PROTECTED]:~$ svn info https://svn.example.org/svn/main/ svn: OPTIONS of 'https://svn.example.org/svn/main': Could not read status line: SSL error: Rehandshake was requested by the peer. (https://svn.example.org) This is against an apache2 server with SSLVerifyClient require ... If I set "SSLVerifyClient none" everything just works, hence the conclusion that this is related to client certificate verification. I have configured my svn client to use a pkcs#12 file. This may be related to http://bugs.debian.org/480041 Version info: subversion 1.5.1dfsg1-1ubuntu2 libneon27-gnutls 0.28.2-2build1 ** Affects: subversion (Ubuntu) Importance: Undecided Status: New -- svn over https with client certificates broken (regression in intrepid) https://bugs.launchpad.net/bugs/294648 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 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid)
** Summary changed: - insecure file access (breezy, dapper, edgy, gutsy, hardy) + insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid) ** Description changed: Reproduced in versions: 2.37a-1ubuntu1.1 (breezy?) 2.41-1ubuntu4 (dapper) 2.42a-linux-glibc232-py24-i386-static (blender.org binary) 2.42a-1ubuntu1.1 (edgy) 2.44-2ubuntu2 (gutsy) 2.45-4ubuntu1 (hardy) - + 2.46+dfsg-4 (intrepid) - Blender writes to files in /tmp/ in an insecure fashion. For example, - launching blender and then selecting "Render > Render Animation", writes - to the file /tmp/0001.jpg. + + Blender writes to files in /tmp/ in an insecure fashion. For example, launching blender and then selecting "Render > Render Animation", writes to the file /tmp/0001.jpg. This can be exploited by a malicious user to overwrite arbitrary files of another user using blender: [EMAIL PROTECTED] ln -s /home/bob/thesis.tex /tmp/0001.jpg -- insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid) https://bugs.launchpad.net/bugs/6671 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 71322] Re: reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale
The same happens with "LC_ALL=en_GB.UTF-8 aspell check somedir" where somedir is an existing directory. -- reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale https://bugs.launchpad.net/bugs/71322 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 294648] Re: svn over https with client certificates broken (regression in intrepid)
I can confirm that the problem goes away when replacing libneon- gnutls.so.27 with /usr/lib/libneon.so.27. Recreating the p12 with gnutls did not help. Also, I don't even get a p12 passphrase prompt when using the gnutls version of the library. -- svn over https with client certificates broken (regression in intrepid) https://bugs.launchpad.net/bugs/294648 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 6671] Re: insecure file access
** Also affects: blender (Ubuntu) Importance: Untriaged Status: Unconfirmed -- insecure file access https://launchpad.net/bugs/6671 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 6671] Re: insecure file access
** This bug has been flagged as a security issue -- insecure file access https://launchpad.net/bugs/6671 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 6671] Re: insecure file access (breezy, dapper)
** Summary changed: - insecure file access + insecure file access (breezy, dapper) ** Description changed: - Version: 2.37a-1ubuntu1.1 + Reproduced in versions: + 2.37a-1ubuntu1.1 (breezy?) + 2.41-1ubuntu4 (dapper) Blender writes to files in /tmp/ in an insecure fashion. For example, - launching blender and then pressing 'a' (for animation?) writes to the - file /tmp/.jpg. + launching blender and then selecting "Render > Render Animation", writes + to the file /tmp/0001.jpg. This can be exploited by a malicious user to overwrite arbitrary files of another user using blender: - [EMAIL PROTECTED] ln -s /home/bob/thesis.tex /tmp/.jpg + [EMAIL PROTECTED] ln -s /home/bob/thesis.tex /tmp/0001.jpg -- insecure file access (breezy, dapper) https://launchpad.net/bugs/6671 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 6671] Re: insecure file access (breezy, dapper)
I did a quick test with the binary from blender.org: blender-2.42a- linux-glibc232-py24-i386-static, and yes, it seems it does the same thing. But, the 2.42a binary I downloaded also has a similar vulnerability for /tmp/quit.blend, something that I think was fixed long ago in debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298167 I just ran the binary from the unpacked tar file, I did not try to install it in any way. -- insecure file access (breezy, dapper) https://launchpad.net/bugs/6671 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 6671] Re: insecure file access (breezy, dapper, edgy, gutsy)
Vincent, I upgraded to 7.10 and verified that the bug is still present in the 2.44-2ubuntu2 version. I updated the bug description accordingly. This is not a huge issue for me personally as I only run blender on my personal machine where I am the only user. At least if run on a multi- user system I would consider this is a security issue. -- insecure file access (breezy, dapper, edgy, gutsy) https://bugs.launchpad.net/bugs/6671 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
[Bug 6671] Re: insecure file access (breezy, dapper, edgy)
** Description changed: Reproduced in versions: 2.37a-1ubuntu1.1 (breezy?) 2.41-1ubuntu4 (dapper) 2.42a-1ubuntu1.1 (edgy) + 2.44-2ubuntu2 (gutsy) Blender writes to files in /tmp/ in an insecure fashion. For example, launching blender and then selecting "Render > Render Animation", writes to the file /tmp/0001.jpg. This can be exploited by a malicious user to overwrite arbitrary files of another user using blender: [EMAIL PROTECTED] ln -s /home/bob/thesis.tex /tmp/0001.jpg ** Summary changed: - insecure file access (breezy, dapper, edgy) + insecure file access (breezy, dapper, edgy, gutsy) -- insecure file access (breezy, dapper, edgy, gutsy) https://bugs.launchpad.net/bugs/6671 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
[Bug 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, hardy)
One possibility to consider would be to create a temporary directory under /tmp and use that in every place where /tmp is currently used. You cannot remove the symlinks as they are not owned by you. -- insecure file access (breezy, dapper, edgy, gutsy, hardy) https://bugs.launchpad.net/bugs/6671 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 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, feisty)
** Summary changed: - insecure file access (breezy, dapper, edgy, gutsy) + insecure file access (breezy, dapper, edgy, gutsy, feisty) ** Description changed: Reproduced in versions: 2.37a-1ubuntu1.1 (breezy?) 2.41-1ubuntu4 (dapper) + 2.42a-linux-glibc232-py24-i386-static (blender.org binary) 2.42a-1ubuntu1.1 (edgy) 2.44-2ubuntu2 (gutsy) + 2.45-4ubuntu1 (feisty) + Blender writes to files in /tmp/ in an insecure fashion. For example, launching blender and then selecting "Render > Render Animation", writes to the file /tmp/0001.jpg. This can be exploited by a malicious user to overwrite arbitrary files of another user using blender: [EMAIL PROTECTED] ln -s /home/bob/thesis.tex /tmp/0001.jpg ** Summary changed: - insecure file access (breezy, dapper, edgy, gutsy, feisty) + insecure file access (breezy, dapper, edgy, gutsy, hardy) ** Description changed: Reproduced in versions: 2.37a-1ubuntu1.1 (breezy?) 2.41-1ubuntu4 (dapper) 2.42a-linux-glibc232-py24-i386-static (blender.org binary) 2.42a-1ubuntu1.1 (edgy) 2.44-2ubuntu2 (gutsy) - 2.45-4ubuntu1 (feisty) + 2.45-4ubuntu1 (hardy) Blender writes to files in /tmp/ in an insecure fashion. For example, launching blender and then selecting "Render > Render Animation", writes to the file /tmp/0001.jpg. This can be exploited by a malicious user to overwrite arbitrary files of another user using blender: [EMAIL PROTECTED] ln -s /home/bob/thesis.tex /tmp/0001.jpg -- insecure file access (breezy, dapper, edgy, gutsy, hardy) https://bugs.launchpad.net/bugs/6671 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 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, hardy)
I created a new user for testing this, no ~/.blender directory or ~/.B.blend file. Still happens for me. Kees, do you have a ~/.B.blend file that would override the renderdir? -- insecure file access (breezy, dapper, edgy, gutsy, hardy) https://bugs.launchpad.net/bugs/6671 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 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, hardy)
Reproduced on a fresh installation (hardy desktop). I don't believe this is due to some old configuration files left behind. -- insecure file access (breezy, dapper, edgy, gutsy, hardy) https://bugs.launchpad.net/bugs/6671 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 6671] Re: insecure file access (breezy, dapper, edgy)
** Summary changed: - insecure file access (breezy, dapper) + insecure file access (breezy, dapper, edgy) ** Description changed: Reproduced in versions: 2.37a-1ubuntu1.1 (breezy?) 2.41-1ubuntu4 (dapper) + 2.42a-1ubuntu1.1 (edgy) Blender writes to files in /tmp/ in an insecure fashion. For example, launching blender and then selecting "Render > Render Animation", writes to the file /tmp/0001.jpg. This can be exploited by a malicious user to overwrite arbitrary files of another user using blender: [EMAIL PROTECTED] ln -s /home/bob/thesis.tex /tmp/0001.jpg -- insecure file access (breezy, dapper, edgy) https://bugs.launchpad.net/bugs/6671 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
[Bug 576302] Re: regression: root device not found (mptspi)
** Description changed:
After upgrading from Karmic to Lucid, my old Dell Poweredge no longer boots,
but fails with:
Gave up waiting for root device. [...]
- Alert! /dev/disk/by-uuid/... does not exist. Dropping to a shell!
+ Alert! /dev/disk/by-uuid/d4cbfbe0-d0af-434f-aa73-40471e6cc040 does not exist.
Dropping to a shell!
+
+ 2.6.31-21-genericOK
+ 2.6.32-21-genericERROR
+ 2.6.32-22-genericERROR
I can boot 2.6.31-21-generic, but with 2.6.32-21-generic and
2.6.32-22-generic I get the error. I recall I got the error earlier as
well but it resolved itself by rebooting I think. Now this consistently
works with 2.6.31-21 and fails with 2.6.32-21 and -22.
+
+ My kernel command line is: root=UUID=d4cbfbe0-d0af-434f-
+ aa73-40471e6cc040 ro hpet=force clocksource=hpet acpi=off
Waiting and exiting, or setting rootdelay=120 doesn't help. The device
is not found, /dev/sda1 never appears. The end of the kernel output
looks like the following. This is hand copied by typing while looking at
the screen so there may be errors:
scsi2 : ioc0: LSI53C1030 B2, FwRev=01011800h, Ports=1, MaxQ=222, IRQ=25
mptspi :03:0c.1: PCI->APIC IRQ transform: INT B -> IRQ 26
mptbase: ioc1: Initating bringup
mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
mptbase: ioc0: Initiating recovery
ioc1: LSI53C1030 B2: Capabilities={Initiator}
mptbase: ioc1: WARNING - Unexpected doorbell active!
mptbase: ioc1: ERROR - Doorbell ACK timeout (count=4999), IntStatus=8000!
mptbase: ioc1: WARNING - : alt-ioc Not ready WARNING!
mptbase: ioc0: Attempting Retry Config request type 0x4, page 0x1, action 2
mptbase: ioc0: Retry completed ret=0x0 timeleft=3750
mptbase: ioc1: ERROR - Doorbell INT timeout (count=4999), IntStatus=0!
mptbase: ioc1: ERROR - Handshake reply failure!
mptbase: ioc1: ERROR - Sending PortEnable failed(-1)!
mptbase: ioc1: ERROR - didn't initialize properly! (-4)
mptspi: probe of :03:0c.1 failed with error -4
I'll attach lspci and dmesg output after booting 2.6.31-21-generic that
works.
--
regression: root device not found (mptspi)
https://bugs.launchpad.net/bugs/576302
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 71322] Re: reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale
Still in lucid, aspell version 0.60.6-3ubuntu1 $ LC_ALL=en_GB.UTF-8 aspell list < /dev/null Segmentation fault -- reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale https://bugs.launchpad.net/bugs/71322 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 576302] [NEW] regression: root device not found (mptspi)
Public bug reported:
After upgrading from Karmic to Lucid, my old Dell Poweredge no longer boots,
but fails with:
Gave up waiting for root device. [...]
Alert! /dev/disk/by-uuid/... does not exist. Dropping to a shell!
I can boot 2.6.31-21-generic, but with 2.6.32-21-generic and
2.6.32-22-generic I get the error. I recall I got the error earlier as
well but it resolved itself by rebooting I think. Now this consistently
works with 2.6.31-21 and fails with 2.6.32-21 and -22.
Waiting and exiting, or setting rootdelay=120 doesn't help. The device
is not found, /dev/sda1 never appears. The end of the kernel output
looks like the following. This is hand copied by typing while looking at
the screen so there may be errors:
scsi2 : ioc0: LSI53C1030 B2, FwRev=01011800h, Ports=1, MaxQ=222, IRQ=25
mptspi :03:0c.1: PCI->APIC IRQ transform: INT B -> IRQ 26
mptbase: ioc1: Initating bringup
mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
mptbase: ioc0: Initiating recovery
ioc1: LSI53C1030 B2: Capabilities={Initiator}
mptbase: ioc1: WARNING - Unexpected doorbell active!
mptbase: ioc1: ERROR - Doorbell ACK timeout (count=4999), IntStatus=8000!
mptbase: ioc1: WARNING - : alt-ioc Not ready WARNING!
mptbase: ioc0: Attempting Retry Config request type 0x4, page 0x1, action 2
mptbase: ioc0: Retry completed ret=0x0 timeleft=3750
mptbase: ioc1: ERROR - Doorbell INT timeout (count=4999), IntStatus=0!
mptbase: ioc1: ERROR - Handshake reply failure!
mptbase: ioc1: ERROR - Sending PortEnable failed(-1)!
mptbase: ioc1: ERROR - didn't initialize properly! (-4)
mptspi: probe of :03:0c.1 failed with error -4
I'll attach lspci and dmesg output after booting 2.6.31-21-generic that
works.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
regression: root device not found (mptspi)
https://bugs.launchpad.net/bugs/576302
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 576302] Re: regression: root device not found (mptspi)
** Attachment added: "dmesg output for working case (2.6.31-21)" http://launchpadlibrarian.net/47920707/dmesg.log -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Re: regression: root device not found (mptspi)
** Attachment added: "lspci -vnvn output" http://launchpadlibrarian.net/47920726/lspci-vnvn.log -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Re: regression: root device not found (mptspi)
Tristan, thanks for the tip! I got it to boot by doing just that. Had to
wait quite long before mptspi was no longer in use and could be rmmoded.
Attaching a new dmesg.log now that I could boot 2.6.32-22-generic. I
guess it is at t=262.064235 where I've done the modprobe mptspi and
things start working.
** Attachment added: "dmesg output for 2.6.32-22 + re-insert mptspi"
http://launchpadlibrarian.net/48603296/dmesg.log
** Description changed:
After upgrading from Karmic to Lucid, my old Dell Poweredge no longer boots,
but fails with:
Gave up waiting for root device. [...]
Alert! /dev/disk/by-uuid/d4cbfbe0-d0af-434f-aa73-40471e6cc040 does not exist.
Dropping to a shell!
2.6.31-21-genericOK
2.6.32-21-genericERROR
2.6.32-22-genericERROR
I can boot 2.6.31-21-generic, but with 2.6.32-21-generic and
2.6.32-22-generic I get the error. I recall I got the error earlier as
well but it resolved itself by rebooting I think. Now this consistently
works with 2.6.31-21 and fails with 2.6.32-21 and -22.
My kernel command line is: root=UUID=d4cbfbe0-d0af-434f-
aa73-40471e6cc040 ro hpet=force clocksource=hpet acpi=off
Waiting and exiting, or setting rootdelay=120 doesn't help. The device
is not found, /dev/sda1 never appears. The end of the kernel output
- looks like the following. This is hand copied by typing while looking at
- the screen so there may be errors:
+ looks like the following:
- scsi2 : ioc0: LSI53C1030 B2, FwRev=01011800h, Ports=1, MaxQ=222, IRQ=25
- mptspi :03:0c.1: PCI->APIC IRQ transform: INT B -> IRQ 26
- mptbase: ioc1: Initating bringup
- mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
- mptbase: ioc0: Initiating recovery
- ioc1: LSI53C1030 B2: Capabilities={Initiator}
- mptbase: ioc1: WARNING - Unexpected doorbell active!
- mptbase: ioc1: ERROR - Doorbell ACK timeout (count=4999), IntStatus=8000!
- mptbase: ioc1: WARNING - : alt-ioc Not ready WARNING!
- mptbase: ioc0: Attempting Retry Config request type 0x4, page 0x1, action 2
- mptbase: ioc0: Retry completed ret=0x0 timeleft=3750
- mptbase: ioc1: ERROR - Doorbell INT timeout (count=4999), IntStatus=0!
- mptbase: ioc1: ERROR - Handshake reply failure!
- mptbase: ioc1: ERROR - Sending PortEnable failed(-1)!
- mptbase: ioc1: ERROR - didn't initialize properly! (-4)
- mptspi: probe of :03:0c.1 failed with error -4
+ [2.658887] mptspi :03:0c.1: PCI->APIC IRQ transform: INT B -> IRQ 26
+ [2.659014] mptbase: ioc1: Initiating bringup
+ [ 17.656025] mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
+ [ 17.656031] mptbase: ioc0: Initiating recovery
+ [ 27.328017] ioc1: LSI53C1030 B2: Capabilities={Initiator}
+ [ 27.912022] mptbase: ioc1: WARNING - Unexpected doorbell active!
+ [ 67.920021] mptbase: ioc1: ERROR - Doorbell ACK timeout (count=4999),
IntStatus=8000!
+ [ 78.168019] mptbase: ioc1: WARNING - : alt-ioc Not ready WARNING!
+ [ 87.224023] mptbase: ioc0: Attempting Retry Config request type 0x4, page
0x1, action 2
+ [ 87.224078] mptbase: ioc0: Retry completed ret=0x0 timeleft=3750
+ [ 117.092017] mptbase: ioc1: ERROR - Doorbell INT timeout (count=4999),
IntStatus=0!
+ [ 117.092022] mptbase: ioc1: ERROR - Handshake reply failure!
+ [ 117.092026] mptbase: ioc1: ERROR - Sending PortEnable failed(-1)!
+ [ 117.092038] mptbase: ioc1: ERROR - didn't initialize properly! (-4)
+ [ 117.092110] mptspi: probe of :03:0c.1 failed with error -4
- I'll attach lspci and dmesg output after booting 2.6.31-21-generic that
- works.
+
+ Attached lspci and dmesg output after booting 2.6.31-21-generic that works
and with 2.6.32-22 after removing and reinserting mptspi etc.
--
regression: root device not found (mptspi)
https://bugs.launchpad.net/bugs/576302
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 71322] Re: reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale
** Changed in: aspell (Ubuntu) Status: Incomplete => New -- reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale https://bugs.launchpad.net/bugs/71322 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 210180] Re: gnome-language-selector crashed with IOError in getSystemDefaultLanguage(), as /etc/default/locales is not user writable
This happened to me after rebooting after dist upgrade from 9.04 to 9.10. The sequence was exactly as described in bug #219888 (marked as duplicate to this) but I was never requested to reboot again, so didn't do so. So yes, still an issue in karmic. -- gnome-language-selector crashed with IOError in getSystemDefaultLanguage(), as /etc/default/locales is not user writable https://bugs.launchpad.net/bugs/210180 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 1241833] Re: Lubuntu 13.10 installation with full disk encryption fails
Also happens with lubuntu-14.04.1-desktop-amd64.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241833 Title: Lubuntu 13.10 installation with full disk encryption fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1241833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245776] Re: cant run installation program
The recipe in my comment #8 still reproduces the issue in Lucid (10.04 LTS) firefox version 3.6.6. ** Changed in: firefox-3.5 (Ubuntu) Status: Incomplete => New -- cant run installation program https://bugs.launchpad.net/bugs/245776 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 355639] Re: zabbix: default locations of fping and fping6
This is *not* fixed in maverick 1:1.8.2-1ubuntu1 for zabbix-server: debian/templates/zabbix_proxy.conf.in:143:FpingLocation=/usr/bin/fping debian/templates/zabbix_proxy.conf.in:147:#Fping6Location=/usr/sbin/fping6 debian/templates/zabbix_server.conf.in:120:#FpingLocation=/usr/sbin/fping debian/templates/zabbix_server.conf.in:124:#Fping6Location=/usr/sbin/fping6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/355639 Title: zabbix: default locations of fping and fping6 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355639] Re: zabbix: default locations of fping and fping6
I cannot edit the status of the bug as it says "Fix Released". Should I open a new issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/355639 Title: zabbix: default locations of fping and fping6 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716593] [NEW] zabbix-server-mysql creates db set to latin1, not utf-8
Public bug reported: When letting the dpkg installation set up the mysql database, it is set to latin1 instead of utf8. This causes image uploads to fail. The Zabbix 1.8 manual section 2.4.3 says to use UTF-8: mysql> create database zabbix character set utf8; Also, the following forum post has an analysis of the problem and the solution: http://www.zabbix.com/forum/showpost.php?p=58066&postcount=30 ** Affects: zabbix (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/716593 Title: zabbix-server-mysql creates db set to latin1, not utf-8 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576302] Re: regression: root device not found (mptspi)
apport information
** Tags added: apport-collected
** Description changed:
After upgrading from Karmic to Lucid, my old Dell Poweredge no longer boots,
but fails with:
Gave up waiting for root device. [...]
Alert! /dev/disk/by-uuid/d4cbfbe0-d0af-434f-aa73-40471e6cc040 does not exist.
Dropping to a shell!
2.6.31-21-genericOK
2.6.32-21-genericERROR
2.6.32-22-genericERROR
I can boot 2.6.31-21-generic, but with 2.6.32-21-generic and
2.6.32-22-generic I get the error. I recall I got the error earlier as
well but it resolved itself by rebooting I think. Now this consistently
works with 2.6.31-21 and fails with 2.6.32-21 and -22.
My kernel command line is: root=UUID=d4cbfbe0-d0af-434f-
aa73-40471e6cc040 ro hpet=force clocksource=hpet acpi=off
Waiting and exiting, or setting rootdelay=120 doesn't help. The device
is not found, /dev/sda1 never appears. The end of the kernel output
looks like the following:
[2.658887] mptspi :03:0c.1: PCI->APIC IRQ transform: INT B -> IRQ 26
[2.659014] mptbase: ioc1: Initiating bringup
[ 17.656025] mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
[ 17.656031] mptbase: ioc0: Initiating recovery
[ 27.328017] ioc1: LSI53C1030 B2: Capabilities={Initiator}
[ 27.912022] mptbase: ioc1: WARNING - Unexpected doorbell active!
[ 67.920021] mptbase: ioc1: ERROR - Doorbell ACK timeout (count=4999),
IntStatus=8000!
[ 78.168019] mptbase: ioc1: WARNING - : alt-ioc Not ready WARNING!
[ 87.224023] mptbase: ioc0: Attempting Retry Config request type 0x4, page
0x1, action 2
[ 87.224078] mptbase: ioc0: Retry completed ret=0x0 timeleft=3750
[ 117.092017] mptbase: ioc1: ERROR - Doorbell INT timeout (count=4999),
IntStatus=0!
[ 117.092022] mptbase: ioc1: ERROR - Handshake reply failure!
[ 117.092026] mptbase: ioc1: ERROR - Sending PortEnable failed(-1)!
[ 117.092038] mptbase: ioc1: ERROR - didn't initialize properly! (-4)
[ 117.092110] mptspi: probe of :03:0c.1 failed with error -4
Attached lspci and dmesg output after booting 2.6.31-21-generic that works
and with 2.6.32-22 after removing and reinserting mptspi etc.
+
+
+ ---
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
+ Architecture: i386
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: anton 2926 F pulseaudio
+ CRDA: Error: [Errno 2] No such file or directory
+ Card0.Amixer.info:
+ Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 17'
+Mixer name : 'Analog Devices AD1981B'
+Components : 'AC97a:41445374'
+Controls : 26
+Simple ctrls : 19
+ DistroRelease: Ubuntu 10.04
+ HibernationDevice: RESUME=
+ IwConfig:
+ lono wireless extensions.
+
+ eth1 no wireless extensions.
+
+ eth0 no wireless extensions.
+ MachineType: Dell Computer Corporation Precision WorkStation 450
+ Package: linux (not installed)
+ ProcCmdLine: root=UUID=d4cbfbe0-d0af-434f-aa73-40471e6cc040 ro hpet=force
clocksource=hpet acpi=off
+ ProcEnviron:
+ LANGUAGE=en_US:en
+ PATH=(custom, user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
+ Regression: Yes
+ RelatedPackageVersions: linux-firmware 1.34
+ Reproducible: Yes
+ RfKill:
+
+ Tags: lucid regression-release needs-upstream-testing
+ Uname: Linux 2.6.32-22-generic i686
+ UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev
scanner scard staff video
+ WpaSupplicantLog:
+
+ dmi.bios.date: 07/21/2003
+ dmi.bios.vendor: Dell Computer Corporation
+ dmi.bios.version: A03
+ dmi.board.name: 0F1263
+ dmi.board.vendor: Dell Computer Corp.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Dell Computer Corporation
+ dmi.modalias:
dmi:bvnDellComputerCorporation:bvrA03:bd07/21/2003:svnDellComputerCorporation:pnPrecisionWorkStation450:pvr:rvnDellComputerCorp.:rn0F1263:rvr:cvnDellComputerCorporation:ct3:cvr:
+ dmi.product.name: Precision WorkStation 450
+ dmi.sys.vendor: Dell Computer Corporation
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/50783070/AlsaDevices.txt
--
regression: root device not found (mptspi)
https://bugs.launchpad.net/bugs/576302
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 576302] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/50783091/ArecordDevices.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/50783090/AplayDevices.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/50783095/BootDmesg.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/50783097/Card0.Amixer.values.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Card0.Codecs.codec97.0.ac97.0.0.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/50783100/Card0.Codecs.codec97.0.ac97.0.0.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Card0.Codecs.codec97.0.ac97.0.0.regs.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/50783103/Card0.Codecs.codec97.0.ac97.0.0.regs.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/50783104/CurrentDmesg.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Lspci.txt
apport information ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/50783105/Lspci.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/50783106/Lsusb.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/50783107/PciMultimedia.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/50783108/ProcCpuinfo.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/50783110/ProcInterrupts.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/50783111/ProcModules.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/50783114/UdevLog.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/50783116/WifiSyslog.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/50783112/UdevDb.txt -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Re: regression: root device not found (mptspi)
** Tags added: regression-release ** Tags removed: needs-kernel-logs needs-upstream-testing -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Re: regression: root device not found (mptspi)
Yes this is still an issue in Lucid with the kernel 2.6.32-22-generic which I believe is still the latest. Ran apport-collect as instructed. Unfortunately the system on which this happens is in production and I do not wish to upgrade the whole system to a development release. I did test two new kernels however, with good results. As I didn't find info on which is the latest kernel in the current development release of Ubuntu, I took the newest I could find in http://archive.ubuntu.com/ubuntu/pool/main/l/linux/, that is linux- image-2.6.35-5-generic_2.6.35-5.6_i386.deb. I also tested the mainline release http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid /linux-image-2.6.35-020635rc1-generic_2.6.35-020635rc1_i386.deb. Both of these new kernels I tested worked in that they eventually recover from the mptspi error. It still takes longer than the default rootdelay, but in any case it does recover by itself and with these new kernels and tweaking rootdelay I can get the system to boot without manual intervention. Good news! So it seems the issue probably is resolved in the next Ubuntu release. But of course not in 10.04 LTS. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 576302] Re: regression: root device not found (mptspi)
Thanks everybody for the help! For me personally, my system is now in a state where I get by. I can get it to boot by the rmmod/modprobe massage until I upgrade to the next stable Ubuntu release where the issue is resolved. -- regression: root device not found (mptspi) https://bugs.launchpad.net/bugs/576302 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 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid)
rusivi1, No, I think it was fixed for Jaunty. -- insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid) https://bugs.launchpad.net/bugs/6671 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 6671] Re: insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid)
rusivi1, No, I think it was fixed for Jaunty. -- insecure file access (breezy, dapper, edgy, gutsy, hardy, intrepid) https://bugs.launchpad.net/bugs/6671 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
