I can confirm this bug on mx4 with OTA-13.
To get hotspot, first toggle in system settings needs to be flipped on and then
the toggle in the status menu needs to be toggled on. Only then does the
hotspot work and the hotspot icon appear in the status bar.
--
You received this bug notification
Hotspot is present and works. It's a bit tricky to activate though.
https://bugs.launchpad.net/ubuntu/+source/indicator-
network/+bug/1589149/comments/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Sunday 24 January 2010 22:46:57 Christoph Korn wrote:
When will this be published in karmic ?
I dont know, i'm not a kubuntu developer.
Cheers,
Jos
--
Multi-threading is not allowed
https://bugs.launchpad.net/bugs/309149
You received this bug notification because you are a member of Ubuntu
This is a very serious bug since many apps rely on libxml2 in a threaded
environment. I noticed this problem when using libstreamanalyzer on
karmic. The configure option --with-threads should be added to the
package to make sure this does not happen again easily.
--
Multi-threading is not
Public bug reported:
A bug in libclucene0 that was fixed [1] long ago causes strigicmd to
crash.
It would be best to update to the latest stable release (0.9.21b) but
adding the patch below suffices too.
The crash (segmentation fault) can be obtained by running e.g.
mkdir /tmp/clucene
More info in this thread (german)
http://forum.ubuntuusers.de/topic/bildschirm-friert-ein-mit-kwin-und-ati-nur-ma/
and another bug report: https://bugs.launchpad.net/ubuntu/+bug/350766
--
X1650 freeze on opengl games (bzflag, alienarena)
https://bugs.launchpad.net/bugs/348450
You received this
This freeze also occurs on KDE 4.2.2 with desktop effects after a bit of
use.
The process X has one thread stuck at
#0 0x7feeeb84dcd7 in ioctl () from /lib/libc.so.6
#1 0x7feee9e6b343 in drmIoctl () from /usr/lib/libdrm.so.2
#2 0x7feee9e6b5cb in drmCommandWrite () from
Public bug reported:
Running the following command on edgy and feisty on a i386 machine gives an
error:
echo hi |valgrind iconv -f ISO-8859-15
This command gives no valgrind errors:
echo hi |valgrind iconv -f ISO-8859-1
This problem is really annoying when debugging code with valgrind.
Please
The attached suppression file for valgrind will make the error invisible if
appended to the default suppression file:
/usr/lib/valgrind/default.supp
That could be a quick fix for feisty.
** Attachment added: iconv.supp
http://librarian.launchpad.net/7331166/iconv.supp
--
encodings
