We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
Corrupt download, please clear your cache and try again.
** Changed in: openoffice.org (Ubuntu)
Status: New = Invalid
--
package openoffice.org-core 1:3.2.1~rc2-2ubuntu1 failed to install/upgrade:
pakker i konflikt - installerer ikke openoffice.org-core
If you have this problem again please report the bug via the automatic
reporter that should pop up.
** Changed in: openoffice.org (Ubuntu)
Status: New = Invalid
--
dpkg problem
https://bugs.launchpad.net/bugs/598975
You received this bug notification because you are a member of Ubuntu
Corrupt download, please clear your cache and try again.
** Changed in: openoffice.org (Ubuntu)
Status: New = Invalid
--
package openoffice.org-core 1:3.2.0-7ubuntu4 failed to install/upgrade: nicht
vollständig gelesen in buffer_copy (Backend dpkg-deb während
Corrupt download, please clear your cache and try again.
** Changed in: openoffice.org (Ubuntu)
Status: New = Invalid
--
package openoffice.org-common 1:3.2.0-7ubuntu4 failed to install/upgrade:
lettura breve in buffer_copy (dpkg-deb backend su
Yes you are correct this file is completely corrupted, its not even an
ods format file at all, which is a special type of zip file with xml
files inside it. Have you had trouble with other file types on your
system?
** Changed in: openoffice.org (Ubuntu)
Status: New = Incomplete
--
File
** Changed in: openoffice.org (Ubuntu)
Status: New = Confirmed
--
OpenOffice crashes with high frequency
https://bugs.launchpad.net/bugs/579966
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Package changed: openoffice.org (Ubuntu) = openoffice.org-l10n
(Ubuntu)
--
Calc function substitute wrong translation in spanish
https://bugs.launchpad.net/bugs/590928
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Summary changed:
- openoffice creates some world-writable config files
+ [i386] openoffice creates some world-writable config files
--
[i386] openoffice creates some world-writable config files
https://bugs.launchpad.net/bugs/593346
You received this bug notification because you are a member
I see you ran it in your comment above, but was it immediately after the
error happened or some time later?
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug notification because you are a member of Ubuntu
Hmm looking at the code I think its buggy. I'm not sure what it is
actually trying to do but it doesn't seem to be doing it right in any
case. It appears to be 8 bit shifting left, and then checking for 0. If
the device is in use lsof returns 0 if it is not then it returns 1, at
least as best as I
It appears to be a bug caused by using this:
system(lsof $backing_store /dev/null);
instead of:
system(lsof $backing_store /dev/null 21);
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You
I was confused earlier about the direction of bitshift since the wrong
calling convention was causing it to always return 0.
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug notification because you are a
Forgot the # in the closes line in the upload. It was fixed in tgt
1:1.0.4-1ubuntu3
** Changed in: tgt (Ubuntu Maverick)
Status: Triaged = Fix Released
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug
When you get that error what does the following show:
# Run 'lsof /dev/sda' to see the details.
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I see you ran it in your comment above, but was it immediately after the
error happened or some time later?
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug notification because you are a member of Ubuntu
Hmm looking at the code I think its buggy. I'm not sure what it is
actually trying to do but it doesn't seem to be doing it right in any
case. It appears to be 8 bit shifting left, and then checking for 0. If
the device is in use lsof returns 0 if it is not then it returns 1, at
least as best as I
It appears to be a bug caused by using this:
system(lsof $backing_store /dev/null);
instead of:
system(lsof $backing_store /dev/null 21);
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You
I was confused earlier about the direction of bitshift since the wrong
calling convention was causing it to always return 0.
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug notification because you are a
Forgot the # in the closes line in the upload. It was fixed in tgt
1:1.0.4-1ubuntu3
** Changed in: tgt (Ubuntu Maverick)
Status: Triaged = Fix Released
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug
Will take a look at this asap, probably during the sprint this next
week.
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What is the status of this MIR?
--
MIR: tgt
https://bugs.launchpad.net/bugs/594372
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
This also breaks starting instances on UEC.
--
[apparmor] getattr handled incorrectly in 2.6.35-6.7
https://bugs.launchpad.net/bugs/599450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The fix from upstream appears to work. This bug can be closed out once
the fix goes into Maverick and will be in a ppa for alpha-2 testing from
what Tim has said on IRC.
Thanks for all the help Tim!
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
The fix from upstream appears to work. This bug can be closed out once
the fix goes into Maverick and will be in a ppa for alpha-2 testing from
what Tim has said on IRC.
Thanks for all the help Tim!
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
Well so far no response from upstream after 5 days so I think they may
no longer be maintaining it. I think I will just have our OOo use the
internal copy at least until such time that official OOo decides to
split up their source (maybe never).
--
[MIR] libtextcat
The version in Ubuntu universe is now the fixed one 0.3.0-3
--
[MIR] mdds
https://bugs.launchpad.net/bugs/589993
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
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 597203
This will help us
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 596915
This will help us
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 495108
This will help us
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 384286
This will help us
won't fix per hallyn
** Changed in: libvirt (Ubuntu)
Status: New = Won't Fix
--
Please stop disabling the VMware ESX driver
https://bugs.launchpad.net/bugs/565771
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
sendfile is used by openjdk-6 directly in the following file:
http://pastebin.com/tceugS7r
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team,
During test of the following kernel it prints the following to dmesg
once for each pass:
ae0f36f0b964caf916c2ffc9f84b28c0f91c18a2-maverick
[ 365.268713] /home/rtg/kern/maverick/kern-64/ubuntu-
maverick/fs/read_write.c:849 should this happen?
--
pad block corrupted error when trying to
0a87a0c1b12f56bd556fd4506041966717c87fb1-maverick
failed as expected
[ 129.980324]
/home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849
816256e0 (null)
[ 178.931445]
/home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849
816256e0 (null)
[
won't fix per hallyn
** Changed in: libvirt (Ubuntu)
Status: New = Won't Fix
--
Please stop disabling the VMware ESX driver
https://bugs.launchpad.net/bugs/565771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
sendfile is used by openjdk-6 directly in the following file:
http://pastebin.com/tceugS7r
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Bugs, which is
During test of the following kernel it prints the following to dmesg
once for each pass:
ae0f36f0b964caf916c2ffc9f84b28c0f91c18a2-maverick
[ 365.268713] /home/rtg/kern/maverick/kern-64/ubuntu-
maverick/fs/read_write.c:849 should this happen?
--
pad block corrupted error when trying to
0a87a0c1b12f56bd556fd4506041966717c87fb1-maverick
failed as expected
[ 129.980324]
/home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849
816256e0 (null)
[ 178.931445]
/home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849
816256e0 (null)
[
Works with 23eb3b64b5e44680c867e165fe1cd18e57fba255 (required compile
fix, probably the same one as Tim mentioned earlier).
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a
He appears to have made another update related to sendfile on May 26.
However, I am not sure if it fixes this problem or that it has been
applied to mainline yet.
http://marc.info/?a=119980668900012r=1w=2
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
Works with 23eb3b64b5e44680c867e165fe1cd18e57fba255 (required compile
fix, probably the same one as Tim mentioned earlier).
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a
He appears to have made another update related to sendfile on May 26.
However, I am not sure if it fixes this problem or that it has been
applied to mainline yet.
http://marc.info/?a=119980668900012r=1w=2
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
Tracked down to occurring in 2.6.33rc1, so will be checking between that
and 2.6.32-15.5
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team,
Actually this is most likely an ooo-build problem not direct upstream,
as upstream uses java media framework and we use gstreamer.
** Changed in: openoffice.org (Ubuntu)
Status: Incomplete = Triaged
** Summary changed:
- Open Office audio control function is broken
+ [ooo-build] Open
Tracked down to occurring in 2.6.33rc1, so will be checking between that
and 2.6.32-15.5
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I examined the OOo source and did not see it reference the createfp
program so I don't think it is using it. I can update the packaging to
resolve points 1 and 3. It hasn't been updated in a while as you mention
and so I have emailed the author to find out its status.
--
[MIR] libtextcat
I've pinged the Debian maintainer to find out the status of the two
files.
--
[MIR] mdds
https://bugs.launchpad.net/bugs/589993
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
He uploaded a new version with the two files removed.
http://packages.qa.debian.org/m/mdds/news/20100623T223241Z.html
--
[MIR] mdds
https://bugs.launchpad.net/bugs/589993
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Well one obvious reason would be that neither of them are Gnome apps,
they are both cross platform apps that use their own toolkit. It should
be possible to modify them to work but it would probably not be trivial.
And in the Firefox case you also have to get approval from upstream for
any change
** Description changed:
Binary package hint: tgt
MIR tgt for Ubuntu Main
- @ccheney: please fill in details here...
+ Rationale: Needed for UEC
+
+ Security: It has had one CVE, CVE-2010-0743 as noted at:
+
+ http://secunia.com/advisories/39142/
+
Maverick)
Assignee: Chris Cheney (ccheney) = (unassigned)
--
MIR: tgt
https://bugs.launchpad.net/bugs/594372
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
After changing my test to just be registering the images per Dave's
recommendation I was able to come up with this list:
I tested the following kernels, 10 times each:
Passed:
v2.6.32 (10/10)
v2.6.32.15.5-lucid (10/10)
Failed:
v2.6.33 (10/10)
v2.6.34-rc3-maverick (10/10)
v2.6.34-lucid (09/10)
Should this bug be reopened, since we reverted the patch? It seems
incorrect to leave it marked Fix Released as least, either Triaged or
Won't Fix seem better.
--
[SRU] euca-get-console-output gives first 64k of output, not most recent
https://bugs.launchpad.net/bugs/566793
You received this bug
After changing my test to just be registering the images per Dave's
recommendation I was able to come up with this list:
I tested the following kernels, 10 times each:
Passed:
v2.6.32 (10/10)
v2.6.32.15.5-lucid (10/10)
Failed:
v2.6.33 (10/10)
v2.6.34-rc3-maverick (10/10)
v2.6.34-lucid (09/10)
Should this bug be reopened, since we reverted the patch? It seems
incorrect to leave it marked Fix Released as least, either Triaged or
Won't Fix seem better.
--
[SRU] euca-get-console-output gives first 64k of output, not most recent
https://bugs.launchpad.net/bugs/566793
You received this bug
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 596139
This will help us
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
works:
Linux beagle 2.6.32-020632-generic #020632 SMP Thu Dec 3 10:09:58 UTC 2009
x86_64 GNU/Linux
Linux beagle 2.6.32-0206321505-generic #0206321505 SMP Wed Jun 2 19:09:40 UTC
2010 x86_64 GNU/Linux
bad:
Linux beagle 2.6.33-020633-generic #020633 SMP Thu Feb 25 10:10:03 UTC
2010 x86_64
Hmm I tried 2.6.33 again just to be certain and now it is working on
2.6.33, hmm :-\
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I now can't get it to crash anymore. I am upgrading from maverick alpha
1 to current and then will do further testing.
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a
I tried upgrading to current and now I can't see my nc anymore. :-\
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Tags added: lucid
--
Base misbehaves when opening DBs created with another locale (same encoding!)
https://bugs.launchpad.net/bugs/595515
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
** Tags added: kubuntu
--
openoffice crash on key F4 (Database viewer)
https://bugs.launchpad.net/bugs/595417
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
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 595121
This will help us
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 595332
This will help us
works:
Linux beagle 2.6.32-020632-generic #020632 SMP Thu Dec 3 10:09:58 UTC 2009
x86_64 GNU/Linux
Linux beagle 2.6.32-0206321505-generic #0206321505 SMP Wed Jun 2 19:09:40 UTC
2010 x86_64 GNU/Linux
bad:
Linux beagle 2.6.33-020633-generic #020633 SMP Thu Feb 25 10:10:03 UTC
2010 x86_64
Hmm I tried 2.6.33 again just to be certain and now it is working on
2.6.33, hmm :-\
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I now can't get it to crash anymore. I am upgrading from maverick alpha
1 to current and then will do further testing.
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a
I tried upgrading to current and now I can't see my nc anymore. :-\
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are these OOo MIRs going to be processed?
--
[MIR] mdds
https://bugs.launchpad.net/bugs/589993
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
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
Failed retrace.
** Changed in: openoffice.org (Ubuntu)
Status: New = Invalid
--
soffice.bin crashed with SIGSEGV - crash happens as .xls (Spreadsheet) file
closes
https://bugs.launchpad.net/bugs/594406
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
[This is an automatic notification.]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect -p openoffice.org-core 592064
This will help us
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you test
if it still occurs on Ubuntu 10.04 LTS (Lucid Lynx)?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue
201 - 300 of 12461 matches
Mail list logo
