http://bugs.exim.org/show_bug.cgi?id=809
** Package changed: php5 (Ubuntu) = libpcre++ (Ubuntu)
** Bug watch added: bugs.exim.org/ #809
http://bugs.exim.org/show_bug.cgi?id=809
--
php5 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/356578
You received this bug notification because
Good to know. If you need any PPA packages testing I'll be more than
happy to assist.
--
Bacula Version 3?
https://bugs.launchpad.net/bugs/474523
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
--
Ubuntu-server-bugs
Public bug reported:
Binary package hint: apache2
Running /etc/init.d/apache2 stop as a normal user gives:
* Stopping web server apache2 [ OK ]
This is incorrect, my user has no permissions to stop the web server. The
server is still running:
$ ps ax
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35187696/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35187697/XsessionErrors.txt
--
Apache2 initscript gives wrong output
https://bugs.launchpad.net/bugs/475747
You received
** Branch linked: lp:ubuntu/jaunty-proposed/kvm
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Hmm, why does ubuntu-bug attach my xsession-errors file for apache? :P
Another bug?
--
Apache2 initscript gives wrong output
https://bugs.launchpad.net/bugs/475747
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
You have to be root to stop apache.
sudo /etc/init.d/apache2 stop
Regards
chuck
** Changed in: apache2 (Ubuntu)
Status: New = Won't Fix
--
Apache2 initscript gives wrong output
https://bugs.launchpad.net/bugs/475747
You received this bug notification because you are a member of Ubuntu
Of course you have to be root. Thats the whole point of this bug. The
script report apache is stopped, but it can't be and it isn't. The
output of the script is wrong for non-root users.
--
Apache2 initscript gives wrong output
https://bugs.launchpad.net/bugs/475747
You received this bug
** Tags added: uec
--
x86_64 images should be presented a /dev/sdb, not a /dev/sda2
https://bugs.launchpad.net/bugs/457283
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
** Tags added: uec
--
euca-bundle-vol does not create essential tmpfs mounts when bundling Ubuntu
images
https://bugs.launchpad.net/bugs/450044
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicate bug.
--
Ubuntu-server-bugs
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = New
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
** Tags added: uec
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Actually this bug exists since Jaunty (or earlier). The init script is
just discarding whatever kill is doing to apache. Besides the output
being wrong, the init script also incorrectly returns success. This
makes the script incompatible with constants defined in sysexits.h,
stdlib.h and the
I also see extremely slow performance of my Windows XP virtual machine
with -m 1024, on every bootup. I think it is because of IO limitation
(running Windows file system on top of a Linux file system), not CPU/RAM
limitation, but I have not figured out how to speed it up. For what
it's worth,
Just for informational purposes, the way that bug 458850 was fixed, if
updates are done to Eucalyptus such that ephemeral storage is on
/dev/sdb instead of /dev/sda2 ec2-init should correctly adjust.
--
x86_64 images should be presented a /dev/sdb, not a /dev/sda2
Actually, I just found out this issue is not confined to apache. The same goes
for:
acpid
acpi-support
anacron
apport (even though it shows a permission denied error)
and the list goes on... Does anyone actually care about making initscripts
usable?
--
Apache2 initscript gives wrong output
Actually, doing for x in `ls /etc/init.d`; do /etc/init.d/$x stop;
done will result in my gnome session dying, dropping me back to a gdm
login prompt, even though I'm running that as a normal user...
--
Apache2 initscript gives wrong output
https://bugs.launchpad.net/bugs/475747
You received
Because this feature is officially supported, can the importance be
updated ?.
I think it should not be defined as a wishlist, actually it's a feature
that no longer works with 9.10.
--
virt-aa-helper fails to add copy-on-write images on apparmor profile
https://bugs.launchpad.net/bugs/470636
*** This bug is a duplicate of bug 456806 ***
https://bugs.launchpad.net/bugs/456806
Freshly installed Server Karmic, experiencing the same bug.
Installation included only LAMP and encryption of user folders.
--
mountall on karmic server install fails
https://bugs.launchpad.net/bugs/460153
Wow, that was very fast. Was this a package already in the system?
I can confirm that the package in proposed fixes the issue in both smbclient
and in nautilus browsing.
Good work, I have attached the output of the smbclient command so you
can compare if you like.
** Attachment added:
Do not deploy this updated version.
I installed kvm_84+dfsg-0ubuntu12.4_amd64.deb and it has made the
problem worse. Now RAW disk images are having disk I/O errors and I'm
still getting I/O errors in qcow2 images.
r...@kvm-host:~# file /kvm/guest/disk0.raw
/kvm/guest/disk0.raw: x86 boot sector;
Public bug reported:
Binary package hint: php5
routine system updates
Ubuntu 9.10 - the Karmic Koala - released in October 2009
ProblemType: Package
Architecture: i386
Date: Thu Nov 5 17:01:56 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/35206285/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35206286/Dependencies.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/35206287/Dmesg.txt
** Attachment
Public bug reported:
I'm using libpam-krb5 with nss-ldap and nscd, and encountering a
segfault when I try to use 'su' to change to my own account, after
entering the correct password.
Apport doesn't run to process the segfault, or I'd be reporting the bug
with that utility.
The crashing command
I assigned this bug to this package because the segfault appears as
follows (from dmesg):
[ 1844.309499] su[6070]: segfault at 1be96c38 ip 7fd3a48c03c3 sp
7fffd10ab710 error 4 in libkrb5.so.3.3[7fd3a4874000+ae000]
Turning on debug in the krb5 pam system provides the following in
On which release do you see this?
Error message: Credentials cache permissions incorrect
Could you check the permission on the credentials cache directory?
** Changed in: krb5 (Ubuntu)
Importance: Undecided = Medium
** Changed in: krb5 (Ubuntu)
Status: New = Incomplete
--
segfault
Alex Mauer ha...@hawkesnest.net writes:
I assigned this bug to this package because the segfault appears as
follows (from dmesg):
[ 1844.309499] su[6070]: segfault at 1be96c38 ip 7fd3a48c03c3 sp
7fffd10ab710 error 4 in libkrb5.so.3.3[7fd3a4874000+ae000]
Turning on debug in the krb5
I backed out from 12.4 to 11. I will try this again to check my sanity.
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
On Fri, Nov 06, 2009 at 01:34:17AM -, nentis wrote:
Do not deploy this updated version.
I installed kvm_84+dfsg-0ubuntu12.4_amd64.deb and it has made the
problem worse. Now RAW disk images are having disk I/O errors and I'm
still getting I/O errors in qcow2 images.
Hm - I've been able
Mathias Gug math...@ubuntu.com writes:
On which release do you see this?
Error message: Credentials cache permissions incorrect
Could you check the permission on the credentials cache directory?
That message would be referring to the file rather than the directory, I
believe. There should
I, too, tested raw images as well, and saw no problems.
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Ubuntu-server-bugs mailing
On Fri, Nov 06, 2009 at 02:31:24AM -, nentis wrote:
I backed out from 12.4 to 11. I will try this again to check my sanity.
Isn't 12.3 the latest version available from jaunty-updates?
--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com
--
kvm-84: virtio on qcow2 broken
This is on karmic.
It all works fine for login; it's just su that has trouble. This is
just more-or-less default settings of nsswitch and PAM. PAM is entirely
as provided by pam-auth-update (except the addition of 'debug' to the
krb5 module), and nss is 'compat ldap' for passwd, group, and
** Branch linked: lp:ubuntu/karmic-proposed/avahi
--
When installing a node, euca_find_cluster fails to locate the cluster
controller if instances are running
https://bugs.launchpad.net/bugs/458904
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Alex Mauer ha...@hawkesnest.net writes:
I do notice that there are a bunch of /tmp/krb5cc_pam_RANDOM files,
owned by root. So I suppose that would be causing the Credentials
cache permissions incorrect
Are you su'ing *to* root? If so, then that ownership is correct. Are
those files all
** Branch linked: lp:ubuntu/mountall
--
mountall vomits a shell onto virtual console when you run vi
https://bugs.launchpad.net/bugs/456806
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicate bug.
--
Ubuntu-server-bugs mailing
Yes, Mathias.
We're interested in changes in behavior between 12.3 and 12.4.
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
** Branch linked: lp:ubuntu/karmic-proposed/asm2
--
updates for karmic and lucid needed to get maven plugins building
https://bugs.launchpad.net/bugs/461090
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to groovy in ubuntu.
--
Yay, so after a restart, everything works now! Thank you so much.
--
Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares
https://bugs.launchpad.net/bugs/472681
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/35213626/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
http://launchpadlibrarian.net/35213627/VarLogDistupgradeApttermlog.gz
** Attachment added: VarLogDistupgradeMainlog.gz
Public bug reported:
mysql couldn't shut down during the install for some reason, and so the upgrade
process hang.
I killed mysql manually, and the upgrade continued,
but at the end reported this error.
ProblemType: Package
Architecture: i386
Date: Fri Nov 6 01:55:25 2009
DistroRelease: Ubuntu
** Branch linked: lp:ubuntu/karmic-proposed/libxpp3-java
--
updates for karmic and lucid needed to get maven plugins building
https://bugs.launchpad.net/bugs/461090
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to groovy in ubuntu.
--
** Branch linked: lp:ubuntu/whois
--
Catastrophic error while querying a .biz domain with -H flag
https://bugs.launchpad.net/bugs/453599
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to whois in ubuntu.
--
Ubuntu-server-bugs mailing list
** Branch linked: lp:ubuntu/karmic-proposed/bcel
--
updates for karmic and lucid needed to get maven plugins building
https://bugs.launchpad.net/bugs/461090
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to groovy in ubuntu.
--
Ack from ubuntu-backporters for Intrepid.
** Changed in: intrepid-backports
Status: New = Fix Released
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Ack for Hardy too.
** Changed in: hardy-backports
Status: New = Fix Released
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Note that the first Lucid autosync just happened and backports are low
build priority, so it will take a while before these get built.
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:debian/apache2
--
Apache 2.2 SNI support
https://bugs.launchpad.net/bugs/184131
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Branch linked: lp:ubuntu/hardy-backports/kvm
** Branch linked: lp:ubuntu/intrepid-backports/kvm
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm
** Branch linked: lp:ubuntu/apache2
--
/etc/init.d/apache2 restart fails on busy webservers
https://bugs.launchpad.net/bugs/270899
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu-server-bugs mailing list
Nope, su'ing to the current user. 'su - $USER', using the environment
variable. It does the same if I put the literal username, obviously.
File modes are 0600
--
segfault
https://bugs.launchpad.net/bugs/476069
You received this bug notification because you are a member of Ubuntu
Server Team,
** Branch linked: lp:ubuntu/hardy-proposed/apache2
--
mod proxy causes duplicate query strings when nocanon option is used
https://bugs.launchpad.net/bugs/455873
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
*** This bug is a duplicate of bug 429106 ***
https://bugs.launchpad.net/bugs/429106
** Branch linked: lp:ubuntu/vm-builder
--
need kernel and initrd for uec-images
https://bugs.launchpad.net/bugs/426438
You received this bug notification because you are a member of Ubuntu
Server Team,
*** This bug is a duplicate of bug 459798 ***
https://bugs.launchpad.net/bugs/459798
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #459798, so is being marked as such. Please
*** This bug is a duplicate of bug 424965 ***
https://bugs.launchpad.net/bugs/424965
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #424965, so is being marked as such. Please
*** This bug is a duplicate of bug 403078 ***
https://bugs.launchpad.net/bugs/403078
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #403078, so is being marked as such. Please
*** This bug is a duplicate of bug 424937 ***
https://bugs.launchpad.net/bugs/424937
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #424937, so is being marked as such. Please
*** This bug is a duplicate of bug 429322 ***
https://bugs.launchpad.net/bugs/429322
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #429322, so is being marked as such. Please
*** This bug is a duplicate of bug 424965 ***
https://bugs.launchpad.net/bugs/424965
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #424965, so is being marked as such. Please
*** This bug is a duplicate of bug 459798 ***
https://bugs.launchpad.net/bugs/459798
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #459798, so is being marked as such. Please
*** This bug is a duplicate of bug 466271 ***
https://bugs.launchpad.net/bugs/466271
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #466271, so is being marked as such. Please
*** This bug is a duplicate of bug 459798 ***
https://bugs.launchpad.net/bugs/459798
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #459798, so is being marked as such. Please
1. Is this reproducible?
I really don't know. I can't remember doing something special.
Surprisingly, I had the same issue on another jaunty-machine. So, I guess there
are more people out there with the same problems. The only special about my
setup is probably that I often switch between
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Branch linked: lp:~ubuntu-core-dev/auctex/ubuntu
--
tex parsing error in auctex
https://bugs.launchpad.net/bugs/240135
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
1 - 100 of 3002 matches
Mail list logo
