Public bug reported:
Banshee plays fine, then without intervention, stops playing. The UI
goes grey, and after a short while the application closes itself down.
OS is Ubuntu 12.04.5. Banshee is 2.4.1-3ubuntu1~precise3.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base
I have this bug too but it also affected the keyboard, when typing every
few seconds some key presses would not register.
I installed ibus-gtk as recommended above and the problem has gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Ubuntu 12.10 x64 running on an NVIDIA 7800GTX
nvidia-experimental-310:
Candidate: 310.14-0ubuntu1
Version table:
310.14-0ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ quantal-updates/restricted
amd64 Packages
What I expected: A working desktop.
What
*** This bug is a duplicate of bug 542210 ***
https://bugs.launchpad.net/bugs/542210
Alvin I have no idea why you're so adamant this is related to bug
191119, both me an whoop have said the patch in bug 542210 have fixed
our problems. 191119 and 568193 don't even appear related.
--
*** This bug is a duplicate of bug 542210 ***
https://bugs.launchpad.net/bugs/542210
** This bug has been marked a duplicate of bug 542210
/boot destroyed during install even when formatting disabled (alternate
installer)
--
installing lucid over existing software raid 1 does not work
I can also confirm that my experience of the problem as detailed in bug
#560152 has been rectified with
http://cdimage.ubuntu.com/daily/20100427.1/lucid-alternate-amd64.iso
- The 'unusable' bits of the partition no longer display
- There are no messages about partition tables changing, just that
Me neither, in fact choosing Keep existing data for any partition
makes the partition tables corrupt and requires an e2fsck to fix. This
has happened to me on two computers, one has 2x 74Gb raptors split into
100Mb RAID1 for /boot, 15Gb RAID0 for / and the rest RAID0 for /home and
one has 4x
I've just gone through the setup routine for Karmic and on the page
after confirming the computer not to boot with degraded RAID, it doesn't
warn against any partitions having their structure changed and only says
that / and /boot are due to be formatted. This contrasts to Lucid where
it warns /,
Hi,
Sorry for the lengthy delay - work got in the way - anyway, I've tested
Jaunty amd64 with the system and am happy, very happy, to report that
the soundcard now works perfectly!
Many thanks to all concerned.
On Thu, 2009-01-08 at 23:41 +, Leann Ogasawara wrote:
Hi NickJ,
Have you
No.
--
cannot install Asus Xonar DX on 64-bit
https://bugs.launchpad.net/bugs/234804
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
Latest discovery points to a problem with Hardy, not Alsa. My 64bit
Hardy installation is an in situ upgrade from Gutsy and appears to lack
the soundcore module specified as a prerequisite by the Alsa Project.
The 32bit Gutsy install, on which the Xonar is working, does possess the
module.
So, next effort: reinstall 64 bit Hardy, cleanly from CD. modprobe
soundcore is now fine. Recompile Alsa from source, including - thank
you Daniel - the most recent snapshot. All source compiles without
error and installs likewise. alsamixer, however, returns:
ALSA lib
Public bug reported:
Linux ubuntu64 2.6.24-16-generic #1 SMP
Have compiled snd-virtuoso module for this soundcard.
Have followed all the instructions and recommendations on
https://help.ubuntu.com/community/SoundTroubleshooting?action=showredirect=DebuggingSoundProblems.
Have installed the same
** Attachment added: aadebug.log
http://launchpadlibrarian.net/14701845/aadebug.log
--
cannot install Asus Xonar DX on 64-bit
https://bugs.launchpad.net/bugs/234804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
14 matches
Mail list logo
