More than ten years and this bug is still around and biting me.
Those SoundBlaster cards are really made to last.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2
Someone sent me an e-mail explaining that maybe the problem can be related to
iommu and a failure in the dma_alloc_coherent() call, and told me to include
iommu=force in the kernel's boot parameters. It didn't work with my computer,
but nevertheless it may work on your specific setup, so please
In fact I've booted into a live Kubuntu CD, and copied the /usr/share/X11/xkb
directory from the liveCD to the corresponding directory in the
already-installed partition,(I took the precaution to rename the original
directory to something else before copying) and after a reboot it worked just
Public bug reported:
Binary package hint: xkb-data
When I press the period key (or the SHIFT-period combination to get a
greater symbol) it instead generates a comma,
I tested it with the br and us mappings (brazilian ABNT2 and US Interbational
layouts),
This bug affects only X11,
It affects
** Summary changed:
- Wrong X keyboard mapping for pt_BR - comma instead of period
+ Wrong X keyboard mapping - comma instead of period
** Description changed:
Binary package hint: xkb-data
- When I press the period key (or the SHIFT-period combination to get a
greater symbol) in
** Description changed:
Binary package hint: xkb-data
When I press the period key (or the SHIFT-period combination to get a
greater symbol) it instead generates a comma,
I tested it with the br and us mappings (brazilian ABNT2 and US Interbational
layouts),
This bug affects only X11,
*** This bug is a duplicate of bug 129910 ***
https://bugs.launchpad.net/bugs/129910
No, it's not.
In bug 129910, Loye Young wrote on 2008-01-10 that that bug is about Gutsy and
Gutsy only, Saïvann Carignan wrote on 2008-04-03: Fix released, This bug is
fixed and similar issues should be
Please reopen this bug, as Dominik was not the only person affected by it.
I have no .Xmodmap, xev returns the proper events, but arrow keys don't work,
PgUp returns a / and / results in a Home. Media keys don't work either.
This situation to a programmer is a royal pain in the keyster. Argh!!!
** Description changed:
Binary package hint: kde-l10n-ptbr
kde-l10n-ptbr do not install, depends : language-pack-kde-ptbr but it is
not available.
system:
kubuntu 8.04 with all updates
kde 4.1
- arch: i386
+ arch: i386, amd64
--
kde-l10n-ptbr depend: language-pack-kde-ptbr but
I believe both my sound cards not being recognized is not related at all to the
-restricted modules, as ALSA is free and included by default in Kernel.
The released fix introduced a grave regression. It manifests with
linux-2.6.24-13.23 (amd64) ,but not with 2.6.24-12.
Not being able to play
I believe both my sound cards not being recognized is not related at all to the
-restricted modules, as ALSA is free and included by default in Kernel.
The released fix introduced a grave regression. It manifests with
linux-2.6.24-13.23 (amd64) ,but not with 2.6.24-12.
Not being able to play
The 2.6.24-13.23 kernel seems to fix the framebuffer issue, but my
Creative Audigy soundcard doesn't work with this kernel. As the
following linux-restricted-drivers package was not put in the repos,
closed-source NVIDIA video driver doesn't work either. Another machine
here doesn't get its MCP51
The 2.6.24-13.23 kernel seems to fix the framebuffer issue, but my
Creative Audigy soundcard doesn't work with this kernel. As the
following linux-restricted-drivers package was not put in the repos,
closed-source NVIDIA video driver doesn't work either. Another machine
here doesn't get its MCP51
When will this fix really appear in repositories? (if there's a fix at
all).
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Ben Collins,
It's a really poor excuse for closing this bug.
The problem exists, people complained, people even posted fixes in this bug
report, and here comes you to say this bug is invalid.
Be honest and say you're closing this bug because you don't want to fix it or
are too lazy to parse
About Ubuntu's Code of Conduct,
Disregarding so many people for so much time is, imo, a disrespectful act.
Getting upset with the aforementioned lack of consideration to its users and to
all the people who cared about reporting, confirming, investigating and posting
workarounds/fixes to this
About Ubuntu's Code of Conduct,
Disregarding so many people for so much time is, imo, a disrespectful act.
Getting upset with the aforementioned lack of consideration to its users and to
all the people who cared about reporting, confirming, investigating and posting
workarounds/fixes to this
About Ubuntu's Code of Conduct,
Disregarding so many people for so much time is, imo, a disrespectful act.
Getting upset with the aforementioned lack of consideration to its users and to
all the people who cared about reporting, confirming, investigating and posting
workarounds/fixes to this
I found something funny about it:
With 4GB DDR RAM (four 1GB banks):
asfxload succeeds loading an 8MB Piano SoundFont
asfxload fails with no memory left when loading a 103MB General MIDI SoundFornt
With 2GB DDR RAM (two 1GB banks):
asfxload succeeds loading an 8MB Piano SoundFont
asfxload
My desktops have Nvidia 5700LE and 5200, my notebook has a 6150go, and I
followed the same procedure in all of them, didn't work in the notebook.
My point is this bug, caused by a decision from a brainy boffin, shouldn't be
there at all. That rare intelligence thought it would be mean to blank
Public bug reported:
Binary package hint: awesfx
Trying to load a SoundFont2 file with asfxload returns no memory left,
even if the computer is plenty of RAM and the module is configured to
majke 1GB available. Tested both with the package from the repository
and a version compiled from
Just to add a bit of infrormation, I changed snd-emu10k1 module parameter to
include max_buffer_size=1024 (supposedly allowing 1GB of ram for samples)
_after_ I got the error. I increased it in steps (and rebooted after changing
it to be sure the changes were applied) and tested again, same
Well, this bug drives me crazy, not because it's hard to fix (it isn't or it
shouldn't), but because no kernel dev seems to be interested in fixing it.
I was able to fix it in my desktops, but not in my notebook, no matter what I
did. Installed openSUSE 10.3 on it and now the nb runs fine.
I'm
Why not just disable Kolab for a while, as according to
http://wiki.kolab.org/index.php/KDE_Kolab_Client#Versions the KDE 4
version shouldn't be touched with a stick?
--
kdepim-kde4 doesn't build from source
https://bugs.launchpad.net/bugs/182533
You received this bug notification because you
Try disabling MySQL support. It seems (at least here, two Kubuntu 7.10
amd64) that libmysqld.a is broken. It didn't compile here with MySQL
support enabled, but went just fine with it disabled.
--
amarok2 doesn't build
https://bugs.launchpad.net/bugs/182545
You received this bug notification
Hi, I'm Kopete's video maintainer.
This bug is the same as https://bugs.kde.org/show_bug.cgi?id=117537 . The
problem that prevents me from fixing this bug properly is the fact some
drivers, like Michel Xhaard's gspca1, behave wrongly, making not only Kopete
but every program that uses usb
About Kopete fiddling with the TV Tuner card, Kopete needs to scan the
available devices to be aware of its properties. It's possible to a device to
be opened by two programs at the same time (to get info about it) and that's
what Kopete does.
I currently have three USB webcams (two gspca1 and
I still have problems here with it (Kubuntu Gutsy on ia32, updated from Feisty,
up-to-date as of 9th October 2007).
When I switch to tty*, there's a black screen with a white blinking cursor with
no login messages at all. When I use Magic SysRq keys no message is printed on
screen. I'm still
This bug is real, it bites us and affects both Feisty and Gutsy, but I don't
believe it will be fixed until 2008 or 2009 (sad but it's what I really think),
as I had another bad experience with asfxload (not processing command-line
parameters), broken in 6.06 LTS, 6.10, 7.04 and fixed some days
** Changed in: awesfx (Ubuntu)
Status: Incomplete = New
--
Broken argument parser
https://bugs.launchpad.net/bugs/68483
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Dear Lionel,
The problem seems to be fixed in Gutsy Gibbon. Thanks to the maintainer who
fixed it upstream. I cannot tell you if the problem persists in 6.06 LTS, 6.10
and 7.04, as I am not using these versions anymore. Maybe it should be verified
at least for 6.06 LTS, but I have no
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6933671/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6933672/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/6933673/ProcMaps.txt
** Attachment added:
0.2.21-1
PackageArchitecture: i386
ProcCmdline: /usr/bin/qjackctl -session
106172676f00011713892240079430029_1174334196_668137
ProcCwd: /home/taupter
ProcEnviron:
LANGUAGE=pt_BR:pt:en
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=pt_BR.UTF-8
SHELL=/bin/bash
Public bug reported:
Binary package hint: awesfx
This bug happens in both edgy and feisty.
When I try to run asfxload with volume parameters it is not recognized.
Like:
asfxload -V 100 SoundFont.sf2
It should load the SoundFont.sf2 to the memory with the volume set to 100%.
It will complain
Public bug reported:
Binary package hint: awesfx
When I try to load a soundfont (.sf2) with either asfxload or sfxload
(from package awesfx, in both Kubuntu 6.06 i386 and 6.10 i386) using an
extra argument, like
asfxload -V 100 /home/taupter/8mbgmsfx.sf2
or a similar construction with other
35 matches
Mail list logo
