@Sergio Ĥlutĉin: I've opened a new bug report for the command-line
issue: https://bugs.launchpad.net/inkscape/+bug/1110549
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/664335
Title:
pdf export
Public bug reported:
Pdftk fails on some valid (large) pdf 1.5 files:
http://tex.stackexchange.com/questions/95973/is-pdftex-1-40-13
-outputting-malformed-pdfs . I am unfortunately unable to construct a
small example. I will either attach the smallest example I have or, if
that's impossible, post
valid pdf 1.5 file that pdftk can't read
** Attachment added: valid pdf 1.5 file that pdftk can't read
https://bugs.launchpad.net/ubuntu/+source/libitext-java/+bug/1110674/+attachment/3507865/+files/small.pdf
** Description changed:
Pdftk fails on some valid (large) pdf 1.5 files:
probably the same as this bug:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1032740
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1067779
Title:
missing pam_loginuid.so
probably the same as this bug:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1032740
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067779
Title:
missing pam_loginuid.so breaks getlogin()
Probably the same as this bug:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1067779
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032740
Title:
libc6 isn't returning a valid user in char
rintintin ~ $ lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description:Ubuntu 12.04.1 LTS
Release:12.04
Codename:
Changing status back to confirmed, for the above reasons.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993648
Title:
libdigest-sha1-perl package is not in Ubuntu 12.04
To manage notifications
This is not an invalid bug. This change breaks every piece of software
that calls for Digest::SHA1, and requires the authors to release a
version of the software that calls for it by the name Digest::SHA.
Furthermore, the new version of the software will no longer be
compatible with older versions
It seems inappropriate to me that the importance of this bug is set to
medium, since xpdf is broken and doesn't work at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669211
Title:
Xpdf
The automated message about testing the latest upstream kernel doesn't
apply here. The bug report is asking that the module, which has already
been removed from the upstream kernel, be blacklisted by default in the
current LTS kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
Public bug reported:
Binary package hint: anacron
Anacron's man page doesn't explain how it is determined when anacron
runs. Presumably this is not documented because it's something that's
set up in the distro, not as part of anacron itself, but I think there
should be at least some info to help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/699888
Title:
suggested addition to anacron's man page
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Padsp has unacceptable performance. Osspd also has unacceptable
performance, although perhaps not quite as bad as padsp.
The basic problem here is that Ubuntu took something that wasn't broken
and intentionally broke it.
--
You received this bug notification because you are a member of Ubuntu
Aoss has better performance than padsp and osspd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634211
Title:
/dev/dsp* disappeared after upgrade Lucid=Maverick [ how-to at #52]
--
ubuntu-bugs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696667
Title:
vstusb module should be blacklisted by default
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
: bcrowell 1200 F pulseaudio
/dev/snd/pcmC0D0p: bcrowell 1200 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'ICH5'/'Intel ICH5 with AD1981B at irq 17'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls
Interesting info, Thangalin -- thanks for posting that!
So I guess the way I would state the problem now is that if you do an
apt-get remove command-not-found, without removing command-not-found-
data, you put your system in a state where its behavior is broken. I
don't understand why these would
Like ISV_Damocles, I'm finding that the problem wasn't actually fixed at
the end of April. I've experienced it as recently as May 7, although it
does seem much less frequent than it was in April. I'm going to change
the status of the bug bag from Fix Released to In Progress.
** Changed in:
This problem seems to be fixed in the latest version of lucid beta 2
(kernel 2.6.32-21).
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete = Fix Released
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug
Thanks, David Leon, for the info. Zygmunt Krynicki, does the patch
described in #4 fix this, or does something else need to be done to fix
this bug?
--
[lucid] command-not-found can't be removed properly using apt
https://bugs.launchpad.net/bugs/561046
You received this bug notification because
Okay, here's what I found.
When I boot into recovery mode, the nvidia module is already loaded, but
the device nodes don't exist. I then unload and reload the nvidia
module. Nothing special happens, except for the warning WARNING: Could
not find old name in
This is a log from a case where X failed to start properly.
** Attachment added: This is a log from a case where X failed to start
properly.
http://launchpadlibrarian.net/45213829/failed_log
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
This is a log from a case where X started up normally.
** Attachment added: This is a log from a case where X started up normally.
http://launchpadlibrarian.net/45213971/succeeded_log
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
Thanks, Robert Hooker, for the suggestion in #52. But could you explain
what makes you think that I have a stale version? My sources.list file
points to us.archive.ubuntu.com/ubuntu, which is identical to what you
suggested except for the us. on the front. Is there something specific
in the log
TJ wrote:
Well it gets more confusing! Both logs show the device nodes created. Are you
*sure* the failed_log isn't accidentally a successful run?
No, I'm not sure. That's what I was saying in #49. After spending
several hours doing reboot cycles, I got a a few failures to boot
properly, but
Okay, I just did two reboots the normal way (not using recovery mode). The
statistics were as follows:
1 boot that didn't result in a login prompt
1 boot that gave a login prompt but didn't start X
So to summarize what I've found so far:
(1) The bug is still present in a system freshly updated
As a test to see whether my apt server might be out of date, I tried
deleting the us. from all the URLs in my sources.list. After an apt-
get update, an apt-get upgrade resulted in 0 upgraded, 0 newly
installed, 0 to remove and 9 not upgraded. So it looks to me like there
was no problem with my
Aha! An apt-get dist-upgrade brought me to kernel 2.6.32-21. Yeesh, I'm
a little grumpy that it was so hard to find out about this. Maybe this
was in a README that I didn't read? I had no idea that a dist-upgrade
would do anything more than an upgrade, once you were already on the
current version
I'm going to change the status of this one to Fix Released. If the
problem recurs, I'll put it back.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: In Progress = Fix Released
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
How do I get into recovery mode? Googling tells me to hit escape when
prompted to do so by GRUB. I don't get any messages from GRUB displayed
on my screen. I get BIOS messages, then the screen stays black for a
long time, and then I get the purple gdm screen.
--
after upgrade to lucid, xorg
I've changed the title to command-not-found can't be removed properly
using apt, after realizing that this isn't just an issue with upgrading
after removing the package. Actually it appears that on any system
running lucid, doing an apt-get remove command-not-found leaves the
shell in the broken
apport information
** Tags added: apport-collected
** Description changed:
After upgrading to lucid, I find that xorg only starts successfully
about 50% of the time. I am using nvidia-current. (Tried switching to nv
and nouveau, but neither one worked properly.) I am attaching two xorg
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/44992861/CurrentDmesg.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are
apport information
** Attachment added: GdmLog.txt
http://launchpadlibrarian.net/44992870/GdmLog.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member of
apport information
** Attachment added: GdmLog1.txt
http://launchpadlibrarian.net/44992872/GdmLog1.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: GdmLog2.txt
http://launchpadlibrarian.net/44992873/GdmLog2.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/44992878/Lspci.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member of
apport information
** Attachment added: PciDisplay.txt
http://launchpadlibrarian.net/44992885/PciDisplay.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/44992890/ProcCpuinfo.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/44992892/ProcInterrupts.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/44992897/ProcModules.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
apport information
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/44992907/RelatedPackageVersions.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/44992910/UdevDb.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member of
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/44992911/UdevLog.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: XorgConf.txt
http://launchpadlibrarian.net/44992912/XorgConf.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: XorgLog.txt
http://launchpadlibrarian.net/44992914/XorgLog.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: XorgLogOld.txt
http://launchpadlibrarian.net/44992915/XorgLogOld.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
Hi, TJ and Fabián Rodríguez -- Thanks for your replies. Yes, I am still
having the problem. I just did an apport-collect (see above), and am
attaching kern.log. This was with kernel 2.6.32-19, however. I will
update to 2.6.32-21 and see if I can reproduce it again.
** Attachment added: kern.log
After an apt-get update and an apt-get upgrade, I'm still at kernel
2.6.32-19. Do I need to recompile my kernel by hand or something grungy
like that in order to get to -21?
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
After an apt-get update and an apt-get upgrade, I'm still experiencing
intermittent failures to boot properly. Out of 9 boots, I had one
failure, which was different than what I was experiencing before. I get
a black screen with nothing in it but a blinking _ cursor. If I do a
ctl-alt-f7, I see
apport information
** Description changed:
After upgrading to lucid, I find that xorg only starts successfully
about 50% of the time. I am using nvidia-current. (Tried switching to nv
and nouveau, but neither one worked properly.) I am attaching two xorg
log files, one from a successful
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/4499/CurrentDmesg.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are
apport information
** Attachment added: GdmLog.txt
http://launchpadlibrarian.net/44995558/GdmLog.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member of
apport information
** Attachment added: GdmLog1.txt
http://launchpadlibrarian.net/44995559/GdmLog1.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: GdmLog2.txt
http://launchpadlibrarian.net/44995562/GdmLog2.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/44995565/Lspci.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member of
apport information
** Attachment added: PciDisplay.txt
http://launchpadlibrarian.net/44995566/PciDisplay.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/44995568/ProcCpuinfo.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/44995569/ProcInterrupts.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/44995573/ProcModules.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
apport information
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/44995576/RelatedPackageVersions.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/44995577/UdevDb.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member of
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/44995578/UdevLog.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: XorgConf.txt
http://launchpadlibrarian.net/44995582/XorgConf.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: XorgLog.txt
http://launchpadlibrarian.net/44995584/XorgLog.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member
apport information
** Attachment added: XorgLogOld.txt
http://launchpadlibrarian.net/44995585/XorgLogOld.txt
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a
Okay, I got the original bug to happen again, with my freshly updated
system. The above apport info is from this occurrence of the bug, and
I'm attaching the kern.log file. Since this is occurring with a freshly
updated system, I'm going to update the status of the bug from
incomplete.
**
I've updated the status from incomplete to in progress. Don't know
if that was the right thing to do...?
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification because you are a member of
Oops, #43 reads succeeded on the second line where it should read
failed. The corrected version is this:
Okay, here is the result of ls -l /dev/nvidia* from a session that
failed:
crw-rw-rw- 1 root root 195, 255 2010-04-21 20:32 /dev/nvidiactl
Here it is from a session that was successful:
Okay, here is the result of ls -l /dev/nvidia* from a session that
succeeded:
crw-rw-rw- 1 root root 195, 255 2010-04-21 20:32 /dev/nvidiactl
Here it is from a session that was successful:
crw-rw-rw- 1 root root 195, 0 2010-04-21 20:34 /dev/nvidia0
crw-rw-rw- 1 root root 195, 255 2010-04-21
Public bug reported:
Binary package hint: update-manager
I did an update-manager -d in a terminal window in workspace 1. It
took quite a long time for the GUI to start up (maybe 30-60 seconds),
and I thought it wasn't working. Meanwhile I switched to workspace 2.
When the GUI did finally come
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44830235/Dependencies.txt
--
dialog box appears in wrong workspace, update-manager GUI appears frozen to user
https://bugs.launchpad.net/bugs/566774
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks, Michael Vogt, for looking into this. I'm going to change the bug
so that it's listed as a bug in icedtea6-plugin.
** Summary changed:
- [lucid] icedtea6-plugin becomes deselected on upgrade
+ [lucid] icedtea-gcjwebplugin is removed on upgrade, should do something
graceful to keep plugin
Is not actually a bug in openjdk-6. The problem only relates to the
*-plugin packages that provide java applet support for web browsers. Not
filing a bug against icedtea-gcjwebplugin, because icedtea-gcjwebplugin
appears to be defunct, so presumably nobody is watching and fixing bugs
on that
Okay, that didn't work. Comment #7 is my explanation of my attempt to
switch this to being filed as a bug against icedtea6-plugin. However,
after I did that, the web interface came up with this message:
'icedtea6-plugin' is a binary package. This bug has been assigned to its
source package
Thanks, Michael Vogt , for your reply. Here is a tarball of those files.
** Attachment added: tarball of /var/log/dist-upgrade
http://launchpadlibrarian.net/43972108/var_log_dist-upgrade.tar.gz
--
[lucid] icedtea6-plugin becomes deselected on upgrade
https://bugs.launchpad.net/bugs/561040
Here is a tarball of /var/log/dist-upgrade , in case that is helpful.
** Attachment added: tarball of /var/log/dist-upgrade
http://launchpadlibrarian.net/43978868/var_log_dist-upgrade.tar.gz
--
[lucid] command-not-found in broken state after upgrade
https://bugs.launchpad.net/bugs/561046
You
After further testing, I've found that the probability of having broken
sound is greatly reduced in lucid beta 2 compared to karmic. In karmic,
approximately 95% of boots would give broken sound. In lucid, I just did
a sample of 8 reboots, and sound was only broken once. The fact that
sound was
Public bug reported:
Binary package hint: update-manager
Before upgrading from Karmic to Lucid beta 2, I had the icedtea6-plugin
package installed and selected, and java applets were working in
firefox. After upgrading, icedtea6-plugin was deselected, and no java
plugin showed up in firefox
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43863657/Dependencies.txt
--
[lucid] icedtea6-plugin becomes deselected on upgrade
https://bugs.launchpad.net/bugs/561040
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: command-not-found
When I was running karmic, I did an apt-get remove command-not-found,
and that worked fine. However, when I upgraded to lucid, I started
getting the following:
$ thereisnocommandwiththisname
/usr/bin/python: can't find '__main__.py' in
Public bug reported:
After upgrading to lucid, I find that xorg only starts successfully
about 50% of the time. I am using nvidia-current. (Tried switching to nv
and nouveau, but neither one worked properly.) I am attaching two xorg
log files, one from a successful startup and one from an
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43864836/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/43864837/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43864838/Dependencies.txt
**
** Attachment added: xorg log file from a failed attempt to start xorg
http://launchpadlibrarian.net/43865265/xorg_log_failed
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug notification
** Attachment added: xorg log file from a successful attempt to start xorg
http://launchpadlibrarian.net/43865278/xorg_log_succeeded
--
after upgrade to lucid, xorg frequently fails to start properly using
nvidia-current
https://bugs.launchpad.net/bugs/561049
You received this bug
apport information
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/43750679/AlsaDevices.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member of Ubuntu
Bugs,
Driver Version 1.0.21.
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: bcrowell 1563 F pulseaudio
+ Card0.Amixer.info:
+ Card hw:0 'NVidia'/'HDA NVidia at 0xf510 irq 21'
+Mixer name : 'Realtek ALC883'
+Components : 'HDA
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/43750682/AplayDevices.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/43750685/ArecordDevices.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43750688/BootDmesg.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/43750690/Card0.Amixer.values.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/43750691/Card0.Codecs.codec.0.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43750692/Dependencies.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/43750694/PciMultimedia.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/43750695/ProcCpuinfo.txt
--
sound randomly working or broken in successive login sessions
https://bugs.launchpad.net/bugs/504947
You received this bug notification because you are a member of Ubuntu
Bugs,
I booted from an ISO of the 2010 Mar 7 daily build of Lucid, but it
didn't get to a state in which I could test the bug. I got a purple
background on my screen and a mouse cursor, but everything was frozen.
When I hit control-alt-F1, I was not able to get to a terminal session.
--
sound randomly
I located the place in the source where this is happening. There is a
function in xsplash.c called temporary_hack_for_initial_fade. Well, I
guess the name of the function says it all. The callback to
temporary_hack_for_initial_fade is set in main(). Note that the 15 is
hardcoded in two different
I changed the 15 to 1, recompiled, and verified that this actually does
fix the problem. Since setting it to 15 rather than 1 is causing
unnecessary delays for people who use WMs that don't take 15 seconds to
load, and since the whole thing is labeled temporary_hack..., I would
really just suggest
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bcrowell 2884 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xf510 irq 21'
Mixer name : 'Realtek ALC883'
Components : 'HDA:10ec0883,1458e601,0012'
Controls
1 - 100 of 138 matches
Mail list logo
