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
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
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
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
--
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
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
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
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.
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
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
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
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,
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
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
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
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.
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.
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
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
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
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
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
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
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.
** 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.
--
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
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)
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
** 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
** 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
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,
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
** 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
** 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.
--
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
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
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
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)
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
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
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,
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
** 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)
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)
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
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
** 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
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
** 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
** 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
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:
** 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
** 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
** 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
54 matches
Mail list logo
