@alberto: so audio is considered to be non-essential in a consumer
computer??? I could see that being the case for servers, but
computers with gui interfaces ought to consider audio to be essential to
that experience, see for instance PC-98 spec.
I did eventually find a work-around for this
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Expired => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/741377
Title:
Mouse Pad
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1292438
Title:
BETA 14.04 cant connect to PulseAudio server
why is this marked incomplete? I provided the info you requested.
why do you keep talking about HDMI?? what does that have to do with
audio? HDMI is not enabled because it's not hooked up.
Yes, I do use an external tv sometimes, when I want to watch a video.
But that has nothing to do with th
@mic
make sure that you install *all* the updates, not just the latest
kernel.
14.04 is still in BETA, it won't be released until april.
I'm not convinced that your bug with not seeing an android phone is at
all related to my bug of not being able to mount a WD usb disk -- which
was visible in t
Hi Raymond -- thank you very much for taking the time to look at this.
after many hours of fiddling and reading...
I finally Uninstalled PulseAudio ...
and now sound works great! not really the correct answer, but at least
I finally have a usable system.
>> do the stereo HDMI codec really nee
when installing software I'm seeing a lot of errors that look like this,
perhaps this is the reason the audio stopped working?
(gconftool-2:2854): GConf-WARNING **: Client failed to connect to the D-BUS
daemon:
Did not receive a reply. Possible causes include: the remote application did
not send
Public bug reported:
1) Install Ubuntustudio 64 bit 14.04 Beta 1 (Alpha) Feb 24
2) reboot etc
result: Sound system works properly
3) Install all the latest updates as of Mar 14, 3.13.0-17-lowlatency kernel
4) reboot etc
result: Sound System no longer works
anything that tries to connect
yes, this bug has been fixed. it works pretty well in 14.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/741377
Title:
Mouse Pad unusable on HP-DV7, Right Cli
ok, got it
3.13.0-12-lowlatencyfails
3.13.0-16-lowlatencyworks
3.13.0-17-lowlatencyworks
3.13.0-12 does not see the partitions, but it is now seeing the SMART
looks like this bug is already fixed
** Attachment added: "udisk output connect WD USB and partitions not found"
https
hmmm... that is interesting
last night I installed that latest round of updates including a new kernel
and now the problem is not reproducable.
I'm attaching the udisk output anyway
** Attachment added: "udisk output mount WD and it worked"
https://bugs.launchpad.net/ubuntu/+source/udisks
Hi madbiologist, thank you very much for your persistance.(somehow
launchpad no longer shows this bug in my list...)
I did try some of your suggestions above, but nothing really seemed to help.
I am happy to report that UbubtuStudio 14.04 BETA 1 (Alpha) AMD64 is
greatly improved compared to
I deactivated the duplicate laptop entry in Display Settings and rebooted
now it does not crash any more
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1291927
Title:
BETA 14.04 X
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1291927
Title:
BETA 14.04 Xorg crashed with SIGABRT in __GI_raise()
Status in “x
apport keeps complaining about "Client failed to connect to the D-BUS daemon"
but it won't let me file this bug because gnome-vfs is not a package...
so here is the info copied from another bug.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
ProcVersionSignature: Ubuntu 3.13.0-12.32-lowlatency 3.1
Public bug reported:
UbuntuStudio 14.04 AMD64 BETA 1 (Alpha)
This works fine on 12.04 bug only exists on the BETA.
I have a Western Digital MyBook 4TB USB disk drive. The drive has two
partitions.
When I plug it in after logging in, the partitions are not detected.
Furthermore Disk Utility s
sorry for the slow response, apparently I missed seeing the email...
anyway, please mark this bug as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/741825
I don't seem to be able to set the status to "duplicate"
thanks
--
You received this bug notification because you ar
thank you for your time.
this bug can be closed, it does not reproduce with a recent version of
ubuntu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/768729
Title:
no
apparently I am still not doing a very good job of explaining the
situation... let me try again.
on 10.10 the best case idle temp is 51C
on 12.04 the best case idle temp is about 57C
on 13.04 the best case idle temp is 75C (that is at idle! and more typically
it is low 80's)
under full load:
th
P.S. it was not a totally apples to apples comparision because in the
process of installing the kernel I ended up switching the video driver
from the amd to the xorg. but the results should be pretty close given
that in previous tests on 12.10 I so no significant difference in
temperature between
very curious... per irc with Kaj...
on 12.04 64 bit UbuntuStudio
installed 3.8.0-18-generic kernel which was backported for testing purposes.
see: https://launchpad.net/~ubuntu-x-swat/+archive/r-lts-backport
over-all result is that this kernel is running about 6 degress hotter
than 12.04 with
this bug is probably fixed now. try 13.04, after a very long wait, the
audio system now *finally* works for me.
why was this bug left to sit and rot never assigned in 4 years
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to puls
I belive that this bug has been fixed in the 13.04... at least for me,
my audio finally works now, after being unusable for a long time and I
was seeing same/similar behavior to what you saw. so give the newest
version a try.
--
You received this bug notification because you are a member of Des
23 matches
Mail list logo