*** This bug is a duplicate of bug 761176 ***
https://bugs.launchpad.net/bugs/761176
** This bug has been marked a duplicate of bug 761176
wlan (AR928X, ath9k) slow since upgrade to natty
* You can subscribe to bug 761176 by following this link:
The workaround does work for me though, of course, one must correct the
typo and replace the two instances of ath5k with ath9k.
As stated in the ubuntuforums entry cited above you can make the
workaround permanent by adding a file ath9k.conf containing the line
options ath9k nohwcrypt=1 to
This is a kernel bug. See bug 479266. Comment #5 has a workaround. Bug
455122 #11 suggests building with -D_FILE_OFFSET_BITS=64 which would fix
the problem in Lyx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, having done research on the problem I found that the call to fstat
in support/FileName.cpp:560 puts some rather fantastic value into
st_size (like 160766784 for a file which is actually 1401 bytes in
size). I can reproduce this behavious with some minimal C-code which
just simply prints the
Public bug reported:
Binary package hint: lyx
I am using Lyx 1.6.7-1 on maverick. When trying to open any .lyx file
from a cifs-mounted share Lyx crashes, no matter if I try to open the
file via the Open dialog or via command line. Lyx says Bus error on
crashing. Running it with -dbg any doesn't
*** This bug is a duplicate of bug 246928 ***
https://bugs.launchpad.net/bugs/246928
** This bug has been marked a duplicate of bug 246928
[upstream] [hardy] Random Kashida in fully-justifed Arabic paragraph
--
Justification for the Arabic support of Open office does not works properly
Works for me in 2.4.1-1ubuntu2. I tried different fonts and different
characters as initial cherecter. They all connect correctly.
--
Character do not combine when followed by Lam-Alef character in Arabic
https://bugs.launchpad.net/bugs/145160
You received this bug notification because you are a
Well, I never tested a patch yet and wouldn't want to screw up my
working system by messing around with hal. If there are some
instructions on how to test a patch for ubuntu I'll gladly do that
though.
--
hal ignores fdi files containing uint64 merges
https://bugs.launchpad.net/bugs/116264
You
OK, I found the information on the ubuntu wiki and tested the patch. And
yes, it works.
--
hal ignores fdi files containing uint64 merges
https://bugs.launchpad.net/bugs/116264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I had already forgotten about this bug since the problem it caused me
was fixed elsewhere. But yes, it still exists in the current version of
hal in hardy. The following fdi file shows the problem. Needs to be put
into /etc/hal/fdi/information:
?xml version=1.0 encoding=UTF-8?
deviceinfo
See #214914. They reverted the change in guidance-backends that caused
the problem for jockey in the first place.
--
jockey-gtk crashed with AttributeError: 'tuple' object has no attribute
'getSections'
https://bugs.launchpad.net/bugs/215027
You received this bug notification because you are a
the api in guidance-backends, namely in /usr/share/python-support
/guidance-backends/xorgconfig.py seems to have changed. This causes
self.xorg_conf to be a tuple of XorgConfig and bool rather than a simple
XorgConfig.
Changing line 60 in /usr/lib/python2.5/site-packages/jockey/xorg_driver.py
*** This bug is a duplicate of bug 215027 ***
https://bugs.launchpad.net/bugs/215027
** This bug has been marked a duplicate of bug 215027
jockey-gtk crashed with AttributeError: 'tuple' object has no attribute
'getSections'
--
[Hardy]Jockey won't show restricted driver manager
*** This bug is a duplicate of bug 215027 ***
https://bugs.launchpad.net/bugs/215027
** This bug has been marked a duplicate of bug 215027
jockey-gtk crashed with AttributeError: 'tuple' object has no attribute
'getSections'
--
jockey-gtk crashed with AttributeError in enabled()
*** This bug is a duplicate of bug 215027 ***
https://bugs.launchpad.net/bugs/215027
** This bug has been marked a duplicate of bug 215027
jockey-gtk crashed with AttributeError: 'tuple' object has no attribute
'getSections'
--
jockey-gtk crashed with AttributeError in
Hello Sika,
the .fdi won't work with the new hal from feisty-backports since that version
doesn't support the uint64 data type anymore for whatever reason. If you have
the feisty-backports channel active downgrading hal to the feisty version will
likely do the job.
--
empty CD not correctly
Public bug reported:
Binary package hint: hal
Since the update to 0.5.9 in feisty-backports hal does no longer accept
fdi files which contain a merge with type=uint64. Such files are
simply ignored. Usually this is not a problem since hal (i.e. hal-info
in 0.5.9) doesn't come with any such fdi
** Attachment removed: 10-cd-r.fdi
http://librarian.launchpad.net/7352962/10-cd-r.fdi
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The file I tried to attach above is a perfect workaround as long as you only
use media of one type and size. The upload was broken though, so I'll attach it
again here.
As I said above it goes to /etc/hal/fdi/information.
** Attachment added: 10-cd-r.fdi
Well, I don't know why, but launchpad won't allow me to attach that
file. So here are its contents:
-cut-
?xml version=1.0 encoding=UTF-8?
deviceinfo version=0.2
device
match key=@info.parent:storage.cdrom.cdr bool=true
match
I had the same problem here. It looks very much like it is related to a
Java runtime environment being selected in ToolsOptionsJava. The font
list will show only the few fonts listed in the original bug report if
you unselect Use a Java runtime environment. On the other hand if you
select a jre
*** This bug is a duplicate of bug 106613 ***
https://bugs.launchpad.net/bugs/106613
** This bug has been marked a duplicate of bug 106613
openoffice-writer font list incomplete
--
[Feisty] Faulty font selection in OpenOffice
https://bugs.launchpad.net/bugs/102050
You received this bug
Yes, cdrecord does work properly (it says something like drive reports wrong
startsec of -150 for track 1. assuming startsec 0 though). neither
nautilus-cd-burner nor brasero work though. Last time it worked was on dapper.
btw i tries writing an fdi script to change the values in hal. This made
the attatched file goes into /etc/hal/fdi/information. This fixes the
problem for me but might not fix it for everyone. The script simply
changes anything that is a volume with a parent that can burn cd-rs and
that has an unknown type and is blank into a cd-r with 700MB. This is
certainly not a
Well it seems that my drive (which is affected - see dup #72654) does
report the correct size which is 359849 sectors (with 2048 Bytes in each
sector that makes about 700MB), at least according to cdrecord
dev=/dev/hdd -atip. Unfortunately it does report a wrong start sector
(i.e. start of lead in
This problem persists even in a fresh feisty install. Still
volume.disc.type is unknown for my TEAC CD-W54E when I insert a CD-R
whereas for my NU DVDRW DDW-061 hal recognizes DVD+Rs correctly as
dvd_plus_r. Also hal doesn't give the volume a volume.disc.capacity key.
I'll attach the debugging inf
** Attachment added: gvm.log
http://librarian.launchpad.net/7337234/gvm.log
--
Doesn't recognize CD-R/Ws since Edgy
https://bugs.launchpad.net/bugs/72654
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: lshal.txt
http://librarian.launchpad.net/7337237/lshal.txt
--
Doesn't recognize CD-R/Ws since Edgy
https://bugs.launchpad.net/bugs/72654
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: hal.log
http://librarian.launchpad.net/7337235/hal.log
--
Doesn't recognize CD-R/Ws since Edgy
https://bugs.launchpad.net/bugs/72654
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I believe 69033 and 72654 are duplicates of this one. Don't know if I'm
entitled to simply mark them as such though...
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
30 matches
Mail list logo
