Public bug reported:
Headphones work just fine. Internal speakers do not work. There was a
brief moment where the drum sound played on log-in one time but then the
speakers have never output anything again.
NOTE: A few releases ago: 14.04 LTS?!? (Before 16.04, in any case) the
sound worked perfec
Public bug reported:
1) Description: Ubuntu 16.04.2 LTS
Release:16.04
2) alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
*** 1.0.25+dfsg-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 htt
Public bug reported:
Simply failed to install. Attempted to "stop" the service (via sudo
service hsqldb-server stop), and it failed stating that the service is
still running. Exception in "main" in the java sql class.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: hsqldb-server 1.8.0.1
--
System Testing: Internal Microphone Does Not Record
https://bugs.launchpad.net/bugs/674235
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
https://lists.ubuntu.com/mailman/lis
Public bug reported:
1) Description:Ubuntu 10.10
Release:10.10
2) 1.0.23-2ubuntu3
3) I expected the microphone to record and the speakers to playback the
recording
4) No sound emitted from speakers (speakers have been tested and work)
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Packag
Live and learn, this *is* a kernel issue (it didn't occur to me that
these are the boot options being passed related to the kernel).
Also, I wasn't sure what status this bug report should be in. So, my
apologies for making a mess of the report with the changes.
If you need anything, don't hesitat
This behavior is exhibited not only on upgrade, but also on a clean
install. The boot flag "nomodeset" must be selected to prevent the bug
from presenting itself.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => I
Oh, and I did test the vanilla upstream kernel--same results.
--
ATI Radeon X1300/X1550 Series Video Card Problem
https://bugs.launchpad.net/bugs/561983
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
This *is* indeed a modesetting issue. It even works with the stock
Ubuntu-21 kernel.
Boot option flag to nomodeset is a work-around to the issue.
My conjecture: The card is attempting to be set outside of the
displayable range (perhaps on a much higher resolution monitor this
would not have occur
** Attachment added: "HTML output of the hardware on the system"
http://launchpadlibrarian.net/43987119/hardware.html
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/43986844/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/43986845/
Public bug reported:
Binary package hint: xorg
Upon upgrade to 10.04 from 9.10 (not fresh install) the XOrg failed to
start initially. Once I worked through that hiccup, the resolution will
not go above 1024 x 768. This worked without a hitch in 9.10 and had the
extra ATI support enabled.
I've a
This was a testing version of Ubuntu that is now the officially
supported release. I think we can safely close this bug report as
whatever was the issue is likely fixed. Neither the kernel nor the
OpenOffice.org versions are current any longer. With Ubuntu 10.04
forthcoming we can probably leave th
I uninstalled localepurge and tried to reset and reinstall the lost
locales as per localepurge instructions. The operation was successful,
but the problem persists.
I edited /var/lib/locales/supported.d/local (output as
var_lib_locales_supported.d_local.txt below) and attempted a dpkg
reconfig. Th
This seems linked to some other issues being exhibited in aptitude. So,
this crash is almost identical to the crash I experienced earlier today.
It all seems to be a problem with the locale.
I'm using EN-UTF-8. I also have localepurge installed with the following
output:
sudo dpkg-reconfigure loc
This is the system log viewer output of the last successful upgrade. I'm
thinking that there was something in this batch that caused an issue. It
may assist in the forensics.
** Attachment added: "Log output of last successful upgrade"
http://launchpadlibrarian.net/37114071/last_successful_upgr
This is actually some sort of memory stack error. Aptitude actually terminates
before the memory dump we all have seen. I'll attach mine as well in case it
may parse out something in common. I'm running this on my i386 machine.
Linux acer-laptop 2.6.32-9-generic #13-Ubuntu SMP Thu Dec 17 17:02:5
16 matches
Mail list logo
