[Bug 1780916] Re: Serious openssl bug crashes imaps sessions
mlangermann: are there please any drawbacks to the temporary solution you kindly offered (i.e. why did you call it temporary)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780916 Title: Serious openssl bug crashes imaps sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-imapd/+bug/1780916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780916] Re: Serious openssl bug crashes imaps sessions
Please any chance of getting this fixed in the 18.04 LTS (Bionic)? It seems the package is hardly usable without this fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780916 Title: Serious openssl bug crashes imaps sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-imapd/+bug/1780916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873517] Re: When upgrading from maverick to oneiric receieved a number of error messages about ssl certs
I have experienced this issue today when upgrading a 32-bit fully up-to- date 11.04 system to 11.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873517 Title: When upgrading from maverick to oneiric receieved a number of error messages about ssl certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/873517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 797131] Re: sd_espeak crashed with SIGABRT in raise()
Jean-Baptiste, thanks for your bugreport. Could you please attach 2 log files from your ~/.speech-dispatcher/log directory: speech- dispatcher.log and espeak.log? They can contain the text that was spoken to you which could contain private information, but if you are OK sending the files, it could help debugging the issue. If any of the above instructions are not clear, let me know, I will be happy 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/797131 Title: sd_espeak crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/797131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 797131] Re: sd_espeak crashed with SIGABRT in raise()
The reason of abort is NULL pointer passed as pa_simple to pa_simple_write. I reported it upstream: https://its.freebsoft.org/its/issues/6773 ** Changed in: speech-dispatcher (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797131 Title: sd_espeak crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/797131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769602] Re: speech-dispacher specifies global options in logrotate script
This was fixed in Oneiric in 0.7.1-6ubuntu1. Not sure if this is SRU worthy for earlier releases, going for no, if someone thinks otherwise, please reopen. ** Changed in: speech-dispatcher (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769602 Title: speech-dispacher specifies global options in logrotate script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/769602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785848] [NEW] do-release-upgrade stalled on Setting up libgdu0 (2.32.1-0ubuntu4) on Maverick-Natty upgrade
Public bug reported: Binary package hint: gnome-disk-utility 1. Install Maverick i386 desktop (happened 3 months ago) 2. Update it to latest software using apt-get update and apt-get dist-upgrade. I did not restart to boot into the new kernel. 3. Run sudo do-release-upgrade over ssh to upgrade to Natty. Answer install new version when promted what to do with the /etc/default/grub file do-release-upgrade then ends up stalled on Setting up libgdu0 (2.32.1-0ubuntu4). In fact, it is then no longer possible to ping the machine's IP. I can't report what is the status of the machine since it's more than 200 km away. I seem to not be the only one with exactly the same symptom: http://ubuntuforums.org/showthread.php?p=10811911 ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: gnome-disk-utility 1. Install Maverick i386 desktop (happened 3 months ago) 2. Update it to latest software using apt-get update and apt-get dist-upgrade. I did not restart to boot into the new kernel. 3. Run sudo do-release-upgrade over ssh to upgrade to Natty. Answer install new version when promted what to do with the /etc/default/grub file do-release-upgrade then ends up stalled on Setting up libgdu0 (2.32.1-0ubuntu4). In fact, it is then no longer possible to ping the machine's IP. I can't report what is the status of the machine since - it's more than 200 km away. I think the Maverick was i386. + it's more than 200 km away. I seem to not be the only one with exactly the same symptom: http://ubuntuforums.org/showthread.php?p=10811911 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785848 Title: do-release-upgrade stalled on Setting up libgdu0 (2.32.1-0ubuntu4) on Maverick-Natty upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773450] Re: sound preferences opens speech-dispatcher
This is much more a gnome-orca problem than speech-dispatcher problem. At least the gnome-orca package maintainer(s) will have better idea what could start Orca if not the autostart file. ** Package changed: speech-dispatcher (Ubuntu) = gnome-orca (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773450 Title: sound preferences opens speech-dispatcher -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769602] Re: speech-dispacher specifies global options in logrotate script
** Changed in: speech-dispatcher (Ubuntu) Assignee: (unassigned) = Boris Dušek (dusek) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769602 Title: speech-dispacher specifies global options in logrotate script -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769602] Re: speech-dispacher specifies global options in logrotate script
This is already fixed in Debian unstable. I will merge the Debian package into the Ubuntu package after Oneiric opens up for development. ** Changed in: speech-dispatcher (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769602 Title: speech-dispacher specifies global options in logrotate script -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571956] Re: sd_generic breaks speech-dispatchter
Lucid contains an outdated version of Speech Dispatcher (0.6 series), so I will test the current series (0.7) present in Maverick and later. I am unable to reproduce this on clean install of Maverick (10.10). orca picks up espeak-generic fine: 0. launch gnome-terminal, do everything that follows in it 1. uncomment line 236 of /etc/speech-dispatcher/speechd.conf (the one starting with AddModule espeak-generic) 2. run command killall speech-dispatcher (ignoring if it failed) 3. run command orca (first time orca was ever run under that user) 4. select espeak-generic (choice 3) as speech output when asked (first question) 5. Orca picks up espeak-generic and uses it, even after logout/login and starting orca again. Charlie, could you please provide exact step-by-step instructions on how to reproduce this on 10.10 (or preferably 11.04)? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571956 Title: sd_generic breaks speech-dispatchter -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 173973] Re: NetworkManager restarted on Ubuntu update - connections and transfers are lost
Hi, I am sorry I did not respond, but it was hard to test since I am no longer using Linux and I could not arrive quickly on an idea how to test this. However I would like to test it in VMware virtual machine, I just would need a little bit of guidance on how to (preferably repeatedly) trigger an update of NetworkManager for testing purposes - is it possible somehow? Also would it make a difference that in the original bug report, the problem was with real wireless connection, but now the problem would be tested with virtual wired network connection? ** Changed in: network-manager (Ubuntu) Status: Invalid = Incomplete -- NetworkManager restarted on Ubuntu update - connections and transfers are lost https://bugs.launchpad.net/bugs/173973 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/listinfo/ubuntu-bugs
[Bug 219568] Re: Partitioner displays partition too small-like incorrect message
I was using 32-bit version when I encountered the bug I reported. -- Partitioner displays partition too small-like incorrect message https://bugs.launchpad.net/bugs/219568 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/listinfo/ubuntu-bugs
[Bug 219568] Re: Partitioner displays partition too small-like incorrect message
1. Attached. (I clicked on the Continue in the message dialog and then saved the syslog.) 2. Sigh, I actually overlooked the / character, since it looked like a stray character to me. If it was with a partition with a longer name (i.e. /mnt), I am sure I would not have overlooked it. ** Attachment added: syslog http://launchpadlibrarian.net/13674530/syslog -- Partitioner displays partition too small-like incorrect message https://bugs.launchpad.net/bugs/219568 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/listinfo/ubuntu-bugs
[Bug 219568] Re: Partitioner displays partition too small-like incorrect message
Attached syslog with the correct script traced as you specified. This time I tried 10GB HDD instead of 12GB, it appeared again, the number seemed very similar to the one in screenshot (1999 ... I did not actually check all the digits, but guess it was the same). Also this time I attached the syslog right after the dialog appears, but before hitting any button on it (like Go Back or Continue). ** Attachment added: syslog http://launchpadlibrarian.net/13710466/syslog -- Partitioner displays partition too small-like incorrect message https://bugs.launchpad.net/bugs/219568 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/listinfo/ubuntu-bugs
[Bug 219564] [NEW] Hostname stripped after dot (inclusive) in installer
Public bug reported: I installed Ubuntu 8.04 RC1 in VMware Fusion. I chose hostname of ubuntu-8.04-rc1, however after install the hostname was ubuntu-8 (/etc/hostname). Apparently the content of the hostname after the dot (inclusive) got stripped away. This is IMHO similar to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/105890. Probably hardly makes it to 8.04, but I think it would be cool if ubiquity informed the user in case of problematic hostname and offered them chance to change it, not just silently corrected the hostname. (I would have chosen underscore during the install instead of the dot if ubiquity informed me that the dot is not a good character in the hostname) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- Hostname stripped after dot (inclusive) in installer https://bugs.launchpad.net/bugs/219564 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/listinfo/ubuntu-bugs
[Bug 219568] [NEW] Partitioner displays partition too small-like incorrect message
Public bug reported: I was installing Ubuntu 8.04 RC1. In the partitioner in the installer, I chose manual setup (as opposed to guided setup). I created a scheme that's shown on the screenshot attached. The error message in the screenshot does not make sense. It read Some of the partitions you created were too small. Please make the following partitions at least this large (in bytes). . (text ommited, the minimum size was approx. 2 GB). It's strange since the root partition is approx. 12.5 GB large. Swap is 550MB, but the RAM in the machine is 512MB (Actually this was a VMware Fusion virtual machine, and the size memory on host OS is 2GB). However, ignoring the message (hitting Continue) and installing worked fine. I even tried to Hibernate the virtual machine (System Log out Hibernate), and it worked fine, so the complain probably does not make sense even for swap partition, which is 550 MB. To sum up: * the message is incorrect * the message, if correct, should say which exact partition is small * the message should include a human readable size as well (i.e. 2 GB instead of 1999316992 - it's hard to deduce quickly if it's in scale of 10^9 or 10^10 or 10^8 ...) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- Partitioner displays partition too small-like incorrect message https://bugs.launchpad.net/bugs/219568 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/listinfo/ubuntu-bugs
[Bug 219568] Re: Partitioner displays partition too small-like incorrect message
** Attachment added: ubuntu-8.04-rc1_partitioner-too-small-partition.tiff http://launchpadlibrarian.net/13577175/ubuntu-8.04-rc1_partitioner-too-small-partition.tiff -- Partitioner displays partition too small-like incorrect message https://bugs.launchpad.net/bugs/219568 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/listinfo/ubuntu-bugs
[Bug 125919] Re: [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
Wireless still not working in Hardy Alpha 5. Macbook Pro rev3 (Santa Rosa), lspci reports AR5418 for the wireless (same as macavity's Macbook). -- [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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/listinfo/ubuntu-bugs
[Bug 173973] NetworkManager restarted on Ubuntu update - connections and transfers are lost
Public bug reported: Hi, I was doing an update that update-manager offered to me on my Gutsy machine. One of the packages updated was NetworkManager. As it was being deployed, I saw in the console that it was being restarted (probably in order for the update to take effect immediately). Unfortunately that means that any existing connection is lost (and then reconnected). What this specifically means that all data transfers occuring before the update are terminated. I e.g. was in the middle of uploading 130 messages through IMAP to my account. Only 30 made it before NetworkManager update took place. I then had to again go through selecting the 100 messages, which took some time and was annoying. I can unfortunately imagine even worse scenarios. I have 2 ideas how to resolve this: 1. NetworkApplet is not restarted. When the user themselves restart the whole machine, only then the update will take effect. 2. Just as with Firefox, a lightbulb icon in systray will appear informing that a restart of NetworkManager is required, and explain that all current network connections will be lost. And it will offer user the actual button to do the restart if/when they should need to. I would clasify this bug (not equal but) near to data loss - imagine you were in the middle of some very important activity requiring network connection - IM with boss, or transferring a huge file. Thanks for considering this. I hope it makes it to Hardy. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager restarted on Ubuntu update - connections and transfers are lost https://bugs.launchpad.net/bugs/173973 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
@Sebastian: the second patch you applied is obsoleted by another more correct patch in the same bugzilla entry. And this first better patch just got commited to Gnome SVN. The first patch from msiner also just got commited to Gnome SVN, so what's needed for the package is to remove both patches that got added to it in this launchpad entry. In other words, the recorder should now work with plain upstream version. I tested it with current SVN. At least for sure both patches applied to ubuntu version in this launchpad entry are no longer needed, since they are in upstream already. -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122426] Re: qemu-i386 crashed with SIGSEGV
Hi, I have qemu-i386 crashing on an x86 machine. I did install libc-dbg, qemu-dbgsym and did gdb session exactly as recommended. (the problem does happen on my production Feisty machine x86 machine, I reproduced the problem with Ubuntu Feisty default install + updates until today in VMware, from where I got the backtrace). Unfortunately even with the debug packages installed, the backtrace is very uninformative, but the last function called has address 0x, a.k.a. NULL, so maybe it is the same problem as described at bug #90660, which directs for further details to http://www.mail-archive.com/[EMAIL PROTECTED]/msg08785.html, where it says that Basically, it tries to call a function through a function pointer, but this pointer is NULL, hence the segfault.. But in that message, the backtrace is _very_ different. qemu-i386 crashes _always_ - even when run with no arguments, or with --help argument. Maybe it has something to do with bug #32170? ** Attachment added: gdb-qemu-i386.txt http://launchpadlibrarian.net/8700739/gdb-qemu-i386.txt -- qemu-i386 crashed with SIGSEGV https://bugs.launchpad.net/bugs/122426 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
I created a patch that handles the crash bug on Gutsy, could someone please build a .deb for Gutsy with this patch so that others can test it? (it works for me) the patch is in Gnome bugzilla - http://bugzilla.gnome.org/show_bug.cgi?id=329922, it's the last one (named Do not update input list when Record button hit) I don't know whether to open a new launchpad entry for this one, but I don't think so since without this new patch, the previous one is not quite usable on Gutsy. (however, the new patch is not needed for Feisty, i.e. as I said above, the .deb provided by jhasse at comment #28 works fine on Feisty as it is. -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
@Balaji: I agree it should not overwrite your saved file. But, e.g. if you want to improve the old (saved) version, you should be able to record a new record (without overwriting the old record), be able to play it back to decide whether it's better than the saved one, and then, if you want, save it, if not, you could record another temporary one, and so on until you are satisfied enough that you want to overwrite the saved one with the temporary one (i.e. hit Save). But I see that you should be able to play back the saved one as well, even if you have recorded a new one. To do this with two separate windows is a solution available with current version of the program, but seems to me more like a workaround than a real solution. So an ideal solution, without adding a much of new GUI, would be to have 2 play buttons: Play saved, and Play recorded. The Play saved would play the saved version. The Play recorded would play the newest recorded version (not necesarily saved). So only one button would be added. And I don't think it would need much new coding logic (although saying that something should be easy is always easy :-) at least easier than it finally turns out ;-) -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
OK, see my last comment in upstream bugzilla - gnome-media from SVN, both with and without the proposed patch applied, exhibit the same buggy behavior. So it's not this patch that introduces the new regression, but either some other changes in grecord (which seems very inactive though), or other libraries. In other words, testing on Gutsy can't indicate whether it fixes things for Feisty, so could please someone make a testing .deb for Feisty? (or point me to some instructions on how to do it? :-) -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
@Sebastian: thanks, I will now know for the future @jhasse: :-) I guess I will have to visit my eye doctor ;-) I tested the patched version on Feisty with the deb provided at comment #28 (https://bugs.launchpad.net/ubuntu/+source/gnome- media/+bug/92879/comments/28). The new regression that is in SVN is not present, so I recommend it the new package for inclusion in feisty- backports (maybe in feisty updates after some more testing?). On another note, this application still has interesting behavior, like when you save the file, and then record again without saving, and play back, then not the new recording, but the old saved version is played back. But this is there no matter whether the patch in question is applied or not, the reason is simply that this application is not being developed. -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129111] Re: [usability] numbers should be resized when application window is resized
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/8598670/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/8598671/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/8598672/ProcStatus.txt ** Bug watch added: GNOME Bug Tracker #461578 http://bugzilla.gnome.org/show_bug.cgi?id=461578 ** Also affects: gcalctool (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=461578 Importance: Unknown Status: Unknown -- [usability] numbers should be resized when application window is resized https://bugs.launchpad.net/bugs/129111 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129111] [usability] numbers should be resized when application window is resized
Public bug reported: Binary package hint: gcalctool see the report upstream ProblemType: Bug Architecture: i386 Date: Sun Jul 29 12:34:46 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/gcalctool NonfreeKernelModules: vmxnet Package: gcalctool 5.19.5-0ubuntu1 PackageArchitecture: i386 ProcCmdline: gcalctool ProcCwd: /home/boris ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gcalctool Uname: Linux vm-gutsy-desktop 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux ** Affects: gcalctool (upstream) Importance: Unknown Status: Unknown ** Affects: gcalctool (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- [usability] numbers should be resized when application window is resized https://bugs.launchpad.net/bugs/129111 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 123979] Re: f-spot.exe crashed with SIGSEGV in g_datalist_clear()
I confirm this bug on Gutsy Tribe 3 + all updates as of Jul 28. I did the same thing as Jeroen - since I am testing Gutsy in VMware, I had no photos, so I simply clicked Cancel on the import dialog that's displayed when you run F-Spot for the first time. Then the main window appeared, and this crash ocurred. -- f-spot.exe crashed with SIGSEGV in g_datalist_clear() https://bugs.launchpad.net/bugs/123979 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
Hi, I tested with tribe 3 + all updates until as of today, Jul 28. See upstream bug report for details. The bug is solved, but (I don't know if it's new, probably yes) a new one is created - hitting on record, then stop, and then hitting on record again without saving the previous record makes gnome-sound- recorder crash everytime. The problem I have with Ubuntu itself is that for gnome-media, there are no debug packages available in repositories, so my backtrace that I sent upstream probably was not very useful - could you please create the debugging packages? (or point me to instructions about how to do it?) I will build gnome-media from svn by hand for now to have the debug info, but having it in repository would be cool for others. -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112009] Re: NetworkManager does not set channel when creating ad-hoc network
Very same problem here with ipw3945. Quite a disappointment for me, since I hoped I will not have to touch the command-line for network configuration in Feisty. -- NetworkManager does not set channel when creating ad-hoc network https://bugs.launchpad.net/bugs/112009 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
Maybe you someone could add his/her comment not only in Launchpad, but also in the Gnome bugzilla (bug number430101, or use the link at the top right), where the real solution will get place, so that the problem might get more attention there. -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113700] very slow local desktop with VNC server on and no VNC connection
Public bug reported: Binary package hint: vnc-common Hi, I am running Feisty. I enabled VNC on my laptop so that I can view its screen when I am at a school computer, I used the System-Preferences-Remote Desktop tool and enabled VNC. I could connect from school to my laptop with no problem, however when returning home, with no connection active to my laptop, I found that just having the VNC server running in background with no connections to it, it makes my desktop slow. I especially noticed that switching tabs in Firefox could take 2 seconds without an exception. Not sure about other apps, from graphical apps I use mostly Firefox, so that's what I noticed. When I turned VNC off, the problem was immediately solved, Firefox started to be responsive again (I think I had to log out and log in at least). So, now I don't use VNC, because while it makes it possible to view remotely my desktop, it makes my desktop nearly unusable when I am working with it locally. Happens on Feisty x86, graphics card ATI Mobility X1450, using fglrx driver installed by restricted drivers manager (8.34). ** Affects: vnc (Ubuntu) Importance: Undecided Status: Unconfirmed -- very slow local desktop with VNC server on and no VNC connection https://bugs.launchpad.net/bugs/113700 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107036] Re: [feisty] Hitting ower button shows shutdown dialog, when canceled the same dialog appears again
Running x86 Feisty release (not x86_64 as with the livecd), the problem is not present. So either this was fixed, or it's only x86_64-specific issue. -- [feisty] Hitting ower button shows shutdown dialog, when canceled the same dialog appears again https://bugs.launchpad.net/bugs/107036 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64408] Re: Urgent text is poorly readable due to low contrast (blue on black)
Ooops, I hit the button Also needs fixing here to look where it needs to fix, and did not realize from the text that it makes a change to bugzilla instead of bringing me to that page I wanted to see, sorry for any inconvenience. -- Urgent text is poorly readable due to low contrast (blue on black) https://bugs.launchpad.net/bugs/64408 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
sadly, X crashes on start with Feisty RC here is diff between xorg.conf from beta to RC: Modes 1400x1050 (pitch 1400) --- Modes 1024x768 800x600 640x480 122c115 Modes 1400x1050 (pitch 1400) --- Modes 1024x768 800x600 640x480 126c119 Modes 1400x1050 (pitch 1400) --- Modes 1024x768 800x600 640x480 130c123 Modes 1400x1050 (pitch 1400) --- Modes 1024x768 800x600 640x480 134c127 Modes 1400x1050 (pitch 1400) --- Modes 1024x768 800x600 640x480 138c131 Modes 1400x1050 (pitch 1400) --- Modes 1024x768 800x600 640x480 To clarify, in Beta, where it was working, the line with (pitch was used. In RC, the line where 1400x1050 resolution was missing was used The most important part of Xorg.0.log (the very end): (II) VESA(0): Total Memory: 256 64KB banks (16384kB) (II) VESA(0): Generic Monitor: Using hsync value of 63.98 kHz (II) VESA(0): Generic Monitor: Using vrefresh value of 60.02 Hz (II) VESA(0): Not using mode 1024x768 (no mode of this name) (II) VESA(0): Not using mode 800x600 (no mode of this name) (II) VESA(0): Not using mode 640x480 (no mode of this name) (II) VESA(0): Not using built-in mode 1400x1050 (hsync out of range) (II) VESA(0): Not using built-in mode 1280x1024 (no mode of this name) (II) VESA(0): Not using built-in mode 1280x1024 (no mode of this name) (II) VESA(0): Not using built-in mode 1280x1024 (no mode of this name) (WW) VESA(0): No valid modes left. Trying less strict filter... Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91] 1: [0xe420] 2: /usr/X11R6/bin/X(InitOutput+0x9aa) [0x80a5b9a] 3: /usr/X11R6/bin/X(main+0x27b) [0x807456b] 4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7dabebc] 5: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1] Fatal server error: Caught signal 11. Server aborting I will attach some full version of relevant files soon. -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://bugs.launchpad.net/bugs/83072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
** Attachment added: Xorg.0.log http://librarian.launchpad.net/7340465/Xorg.0.log -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://bugs.launchpad.net/bugs/83072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107036] [feisty] Hitting ower button shows shutdown dialog, when canceled the same dialog appears again
Public bug reported: Running Ubuntu Feisty Beta (x86_64), on ASUS F2JE laptop. When I hit the physical power button on my notebook, the shut down dialog appears as it should. However, when I press Cancel in that dialog, the dialog reappears once more. In the second dialog, clicking Cancel really works. This does not happen when I select System-Quit from the GNOME main menu, only when using the real shutdown button on my laptop. This worked properly in Dapper and Edgy, so it's a regression in Feisty. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- [feisty] Hitting ower button shows shutdown dialog, when canceled the same dialog appears again https://bugs.launchpad.net/bugs/107036 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107036] Re: [feisty] Hitting ower button shows shutdown dialog, when canceled the same dialog appears again
The problem occurs when using the Feisty Beta LiveCD (I have only Edgy installed on my harddisk). So there might be some fix released for this after Beta. When Feisty RC is released, I will retest. -- [feisty] Hitting ower button shows shutdown dialog, when canceled the same dialog appears again https://bugs.launchpad.net/bugs/107036 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
Sorry if I am blind, but how do I find the # of associated upstream bug in gnome bugzilla? The Remote Bug # field is empty. -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92879] Re: gnome-sound-recorder unable to playback
I just reported it to upstream and updated the remote bug #. ** Changed in: gnome-media (upstream) Importance: Undecided = Unknown Bugwatch: None = GNOME Bug Tracker #430101 Status: Unconfirmed = Unknown -- gnome-sound-recorder unable to playback https://bugs.launchpad.net/bugs/92879 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
btw., why fglrx (ATI's binary driver) is not used for my card when we have the restricted driver manager? -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://bugs.launchpad.net/bugs/83072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103019] Re: [feisty, beta] Invalid parameters on recording sound with Sound recorder (gnome-sourd-recorder)
*** This bug is a duplicate of bug 92879 *** https://bugs.launchpad.net/bugs/92879 ** This bug has been marked a duplicate of bug 92879 gnome-sound-recorder unable to playback -- [feisty,beta] Invalid parameters on recording sound with Sound recorder (gnome-sourd-recorder) https://bugs.launchpad.net/bugs/103019 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103019] [feisty, beta] Invalid parameters on recording sound with Sound recorder (gnome-sourd-recorder)
Public bug reported: Binary package hint: gnome-media I am running Ubuntu Feisty Beta (as live cd). gnome-sound-recorder (Applications-Sound Video-Sound Recorder) does not work, but simple arecord test.wav; aplay test.wav works prefectly. When I start and then stop after few seconds recording with gnome-sound- recorder, when I try to replay the file, nothing happens, the timeline slide bar does not move and is disabled (gray). When I try to save the file, error box with following message shows: Could not save the file Invalid parameters Note that I change the sound configuration when I boot according to 8 steps described in bug #89552, and after that, arecord works for both microphones; but gnome-sound-recorder does not work. (this error happens no matter which sound input source I choose in gnome-sound-recorder, or which format I want to save it in). I discovered some strange things: when I try to close the gnome-sound- recorder after apparently unsuccessful recording, it promts me with this dialog: Save the changes to file/tmp/gsr-record-Untitled-9636.AXC8PT before closing? I choose save, and a save dialog pops up and I can save the file. Playing it then with aplay, it contains the sound I was recording. When I try to record another file in the _same instance_ of gnome-sound-recorder, again, the timeline bar is disabled, hitting Play does not play back the new recording, but hitting Save now works. And, btw., hitting Save as works always. I think if this was the way gnome-sound-recorder was meant to work (i.e. you must Save as the recording before playing it, and when you succeed, then Play plays only the saved version, not the just recorded one), then what I have just described is definitely a serious usability bug. It took me 1 hour to discover to my great surprise that gnome- sound-recorder actually can record. Other users will definitely not have such patience (and even conclude their microphone does not work in Ubuntu). Best regards, Boris Dušek ** Affects: gnome-media (Ubuntu) Importance: Undecided Status: Unconfirmed -- [feisty,beta] Invalid parameters on recording sound with Sound recorder (gnome-sourd-recorder) https://bugs.launchpad.net/bugs/103019 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd3
From herd5 to Beta, the situation improved dramatically. Thank you very much. Now all sound hardware is supported on this type of laptop (at least all I know of :-) - speakers, headphones, built-in and pluggable- in microphones). Few screenshots of Volume Control application to which I will refer: * default state: http://www.flickr.com/photos/[EMAIL PROTECTED]/440091621/ * ideal state: http://www.flickr.com/photos/[EMAIL PROTECTED]/440091627/ The only remaining issue is that user must do a lot of clicks to get reasonable sound configuration from the default one. E.g. plubbable-in microphone is not shown, however some unused device is shown. I will refer to items by names how they appear in Volume Control application. Let me describe the steps one needs to make to get to a nice all-working configuration after boot of Ubuntu Feisty Beta: 1. Add Capture and Input Source 2. Remove Line In 3. Add Microphone 4. Mute Front Mic 5. Raise level of both Front Mic and Microphone from zero to a reasonable value (100% for Front Mic, since it's very silent) 6. Add Front Mic Boost 7. Raise Front Mic Boost to a reasonable level (50% - 70%) 8. Finally on Recording tab, raise Capture to 100% Following these steps, I reached a very decent configuration (see ideal state image link above) with no back-track (or how do you call the effect when microphone input is played to speakers close to the microphone and it starts to whistle), with reasonable volumes for microphones. Or said differently, it's prepared for an out-of-the-box experience. (I was just switching from Front Mic to Mic and back in Options and recording with arecord -tcd -d2 test.wav from different microphones) Rationale for the procedure above is: * the microphone that can be plugged in by user with a jack is mapped to Microphone, but Microphone is hidden by default and Line-in is shown (see default state) * the built-in microphone is mapped to Front mic (which is shown by default), but it is unmuted, so any sound spoken to it is sent to speakers when one sets its volume high (but even on the highest volume of this microphone, the recording power is weak so no strange sound effects usual to this configuration appear) * the Capture is not shown by default, and set to 0 after enabling it, so the user can't record out-of-the-box * the Input source is not shown by default, so the user can't out-of-the-box select the capturing source (built-in or plugged-in microphone). I don't know if this is an issue because maybe it's settable in each sound application, but I am no expert in this. Thanks for fixes in Beta and I would be glad if you took my further suggestions into account. All the best, Boris Dušek -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd3 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd3
Contents of /proc/asound in Feisty Beta, just in case they are needed. ** Attachment added: /proc/asound - tar.gz archive http://librarian.launchpad.net/7079155/proc-asound.tar.gz -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd3 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
Wow, in Feisty Beta it's fixed. However, part of boot is displayed in text mode, I don't know if this is intentional. -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
Could please someone correct the title to say it's regression from herd 3 (instead of herd 4)? I made a mistake. Thanks. ** Description changed: Binary package hint: linux-source-2.6.20 - This is a regression from Herd 4. In Herd 5, no sound or microphone - works. In Herd 4, sound worked (built-in speakers and headphones) and + This is a regression from Herd 3. In Herd 5, no sound or microphone + works. In Herd 3, sound worked (built-in speakers and headphones) and line-in microphone (but not the built-in microphone) worked. In Edgy, only the sound (built-in speakers and headphones) worked. Hardware: ASUS F2JE laptop, Intel HD Audio, some Realtek audio controller (not sure which one, because see Details and attached outputs) Details: No sound is present (but present in Volume control), and none of the 2 microphones are present even in the Volume control application. In the Volume control application, in File-Change Device, I see only 0: Realtek ALC660 (OSS Mixer). When unmuted, whenever I try to move the only slider, labeled Volume, to some value in the middle, it jumps back to maximum. No other devices are present, like 2 microphones that should be (one built-in in webcam, second as pluggable line-in). dmesg shows something about unknown device ALC861 (see output in attachement). The title of Volume control application shows Realtek ALC660 (OSS Mixer) (same as the device in File menu). Note that /proc/asound/pcm speaks again about ALC861, not ALC660 (tar.bz2 archive of /proc/asound attached). Please find in attachements tar.bz2 archive of /proc/asound, then outputs of dmesg, lspci, lspci -n, lspci -v and lsmod. If you need any info or further testing, I will be glad to provide. Best regards, Boris Dušek P.S.: Sorry, what I attached is not a bz2, but a gz archive of /proc/asound (but accidentaly named *.bz2). I am resubmitting a correctly named file again, for your convenience. -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
Still present in Herd 5 (Feisty). -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
Public bug reported: Binary package hint: linux-source-2.6.20 This is a regression from Herd 4. In Herd 5, no sound or microphone works. In Herd 4, sound worked (built-in speakers and headphones) and line-in microphone (but not the built-in microphone) worked. In Edgy, only the sound (built-in speakers and headphones) worked. Hardware: ASUS F2JE laptop, Intel HD Audio, some Realtek audio controller (not sure which one, because see Details and attached outputs) Details: No sound is present (but present in Volume control), and none of the 2 microphones are present even in the Volume control application. In the Volume control application, in File-Change Device, I see only 0: Realtek ALC660 (OSS Mixer). When unmuted, whenever I try to move the only slider, labeled Volume, to some value in the middle, it jumps back to maximum. No other devices are present, like 2 microphones that should be (one built-in in webcam, second as pluggable line-in). dmesg shows something about unknown device ALC861 (see output in attachement). The title of Volume control application shows Realtek ALC660 (OSS Mixer) (same as the device in File menu). Note that /proc/asound/pcm speaks again about ALC861, not ALC660 (tar.bz2 archive of /proc/asound attached). Please find in attachements tar.bz2 archive of /proc/asound, then outputs of dmesg, lspci, lspci -n, lspci -v and lsmod. If you need any info or further testing, I will be glad to provide. Best regards, Boris Dušek ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
** Attachment added: /proc/asound - tar.bz2 archive http://librarian.launchpad.net/6608587/proc-asound.tar.bz2 -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
** Attachment added: dmesg http://librarian.launchpad.net/6608590/dmesg -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
** Attachment added: lspci http://librarian.launchpad.net/6608591/lspci -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
** Attachment added: lspci -n http://librarian.launchpad.net/6608592/lspci-n -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
** Attachment added: lspci -v http://librarian.launchpad.net/6608594/lspci-v -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
** Attachment added: lsmod http://librarian.launchpad.net/6608595/lsmod -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89552] Re: [herd5, alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4
Same as above, but with correct file name (.bz2-.gz) ** Description changed: Binary package hint: linux-source-2.6.20 This is a regression from Herd 4. In Herd 5, no sound or microphone works. In Herd 4, sound worked (built-in speakers and headphones) and line-in microphone (but not the built-in microphone) worked. In Edgy, only the sound (built-in speakers and headphones) worked. Hardware: ASUS F2JE laptop, Intel HD Audio, some Realtek audio controller (not sure which one, because see Details and attached outputs) Details: No sound is present (but present in Volume control), and none of the 2 microphones are present even in the Volume control application. In the Volume control application, in File-Change Device, I see only 0: Realtek ALC660 (OSS Mixer). When unmuted, whenever I try to move the only slider, labeled Volume, to some value in the middle, it jumps back to maximum. No other devices are present, like 2 microphones that should be (one built-in in webcam, second as pluggable line-in). dmesg shows something about unknown device ALC861 (see output in attachement). The title of Volume control application shows Realtek ALC660 (OSS Mixer) (same as the device in File menu). Note that /proc/asound/pcm speaks again about ALC861, not ALC660 (tar.bz2 archive of /proc/asound attached). Please find in attachements tar.bz2 archive of /proc/asound, then outputs of dmesg, lspci, lspci -n, lspci -v and lsmod. If you need any info or further testing, I will be glad to provide. Best regards, Boris Dušek + + P.S.: Sorry, what I attached is not a bz2, but a gz archive of + /proc/asound (but accidentaly named *.bz2). I am resubmitting a + correctly named file again, for your convenience. ** Attachment added: /proc/asound - tar.gz archive http://librarian.launchpad.net/6608600/proc-asound.tar.gz -- [herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression from herd4 https://launchpad.net/bugs/89552 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89152] Re: texlive-formats-extra fails to install: fmtutil: no info for format mltex
Hello Norbert, And for the next bug report, please read what is written in the ouput: fmtutil-sys failed. Output has been stored in /tmp/texlive.fmtutil.GPC14041 Please include this file if you report a bug. Well, I did read the output, and said in my bugreport that: texlive-formats-extra (no format for `mltex') texlive-lang-polish (no format for `utf8mex') texlive-full This is output of reinstallation of texlive-formats-extra, the outputs of the /tmp/texlive.* files are shown above (no format for ...) ... the output so just to make it clear: no format for `mltex' is the complete content of the /tmp/texlive.* file for texlive-formats-extra, and no format for `utf8mex' is the complete content of corresponding /tmp/texlive.* file for texlive-lang-polish :-) Thanks, Boris -- texlive-formats-extra fails to install: fmtutil: no info for format mltex https://launchpad.net/bugs/89152 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89152] texlive-formats-extra fails to install: fmtutil: no info for format mltex
Public bug reported: Hello, This happens on Edgy. I had tetex installed, but then decided to switch to texlive, so I installed texlive-full (and the installer told me that tetex will be removed, so I think there shouldn't be any conflict between tetex and texlive). But three packages from texlive-full failed to install: texlive-formats-extra (no format for `mltex') texlive-lang-polish (no format for `utf8mex') texlive-full This is output of reinstallation of texlive-formats-extra, the outputs of the /tmp/texlive.* files are shown above (no format for ...) Setting up texlive-formats-extra (2005.dfsg.1-1) ... Running mktexlsr. This may take some time... done. Building format(s) --byfmt mltex. This may take some time... fmtutil-sys failed. Output has been stored in /tmp/texlive.fmtutil.GPC14041 Please include this file if you report a bug. dpkg: error processing texlive-formats-extra (--configure): subprocess post-installation script returned error exit status 1 Setting up texlive-lang-polish (2005-2) ... Running mktexlsr. This may take some time... done. Building format(s) --byfmt utf8mex. This may take some time... fmtutil-sys failed. Output has been stored in /tmp/texlive.fmtutil.Ksa14757 Please include this file if you report a bug. dpkg: error processing texlive-lang-polish (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of texlive-full: texlive-full depends on texlive-lang-polish; however: Package texlive-lang-polish is not configured yet. texlive-full depends on texlive-formats-extra; however: Package texlive-formats-extra is not configured yet. dpkg: error processing texlive-full (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: texlive-formats-extra texlive-lang-polish texlive-full E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up texlive-formats-extra (2005.dfsg.1-1) ... Running mktexlsr. This may take some time... done. Building format(s) --byfmt mltex. This may take some time... fmtutil-sys failed. Output has been stored in /tmp/texlive.fmtutil.del15483 Please include this file if you report a bug. dpkg: error processing texlive-formats-extra (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of texlive-full: texlive-full depends on texlive-formats-extra; however: Package texlive-formats-extra is not configured yet. dpkg: error processing texlive-full (--configure): dependency problems - leaving unconfigured Setting up texlive-lang-polish (2005-2) ... Running mktexlsr. This may take some time... done. Building format(s) --byfmt utf8mex. This may take some time... fmtutil-sys failed. Output has been stored in /tmp/texlive.fmtutil.oQz16203 Please include this file if you report a bug. dpkg: error processing texlive-lang-polish (--configure): subprocess post-installation script returned error exit status 1 ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- texlive-formats-extra fails to install: fmtutil: no info for format mltex https://launchpad.net/bugs/89152 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83096] Re: (feisty, alsa-driver) NULL pointer in snd_hda_codec
Resolved in herd3, additionally microphone now works, unlike in Edgy and Dapper. -- (feisty, alsa-driver) NULL pointer in snd_hda_codec https://launchpad.net/bugs/83096 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
Public bug reported: Binary package hint: xserver-xorg Hello, I tried Feisty Herd 2 (as live CD), and it has the same problem as Edgy Eft: The screen in graphical environment is skewed; autodetection uses the vesa driver. This is a regression from Dapper - there it worked fine. I have some photos of the problem at flickr: My screen is 1400x1050, Graphics card is Mobility Radeon X1450, laptop is ASUS F2JE. I tried to follow instructions at DebuggingXAutoconfiguration, I will attach the outputs soon. But what surprises me is that the xorg.conf for Dapper and Feisty is the same, but there is no problem in Dapper. I tried to reconfigure xserver-xorg, and the screen was no longer skewed, but, the resolution was 1024x768, which is not desirable. (This happened even though only 1400x1050 was set in the config.) The only difference between Dapper's, skewed and low-resolution xorg.conf is always the HorizSync and VertRefresh parameters. I will be glad if I can help to resolve this issue by providing additional information. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
** Attachment added: lspci -n http://librarian.launchpad.net/6170298/lspci-n.feisty -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
discover --disable=parallel,serial,usb,ide,scsi,pcmcia Output is empty. -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
** Attachment added: xresprobe vesa http://librarian.launchpad.net/6170480/xresprobe-vesa.feisty -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
** Attachment added: /var/log/Xorg.0.log - for Xorg :0 -ac -logverbose 999 http://librarian.launchpad.net/6170527/Xorg.log.feisty.verbose -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
This is for the reconfigured server, where the screen is not skewed, but resolution is only 1024x768 ** Attachment added: /var/log/Xorg.0.log http://librarian.launchpad.net/6170569/Xorg.log.feisty.reconf.verbose -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
Feisty autodetected configuration ** Attachment added: xorg.conf http://librarian.launchpad.net/6170596/xorg.conf.feisty -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
Feisty - configuration after sudo dpkg-reconfigure xserver-xorg ** Attachment added: xorg.conf http://librarian.launchpad.net/6170611/xorg.conf.feisty.reconf ** Description changed: Binary package hint: xserver-xorg Hello, I tried Feisty Herd 2 (as live CD), and it has the same problem as Edgy Eft: The screen in graphical environment is skewed; autodetection uses the vesa driver. This is a regression from Dapper - there it worked fine. I have some photos of the problem at flickr: My screen is 1400x1050, Graphics card is Mobility Radeon X1450, laptop is ASUS F2JE. I tried to follow instructions at DebuggingXAutoconfiguration, I will attach the outputs soon. But what surprises me is that the xorg.conf for Dapper and Feisty is the same, but there is no problem in Dapper. I tried to reconfigure xserver-xorg, and the screen was no longer skewed, but, the resolution was 1024x768, which is not desirable. (This happened even though only 1400x1050 was set in the config.) The only difference between Dapper's, skewed and low-resolution xorg.conf is always the HorizSync and VertRefresh parameters. + The problem is present no matter if I choose default boot options, or if + I remove quiet splash and add vga=771 (or vga=791). + I will be glad if I can help to resolve this issue by providing additional information. ** Description changed: Binary package hint: xserver-xorg Hello, I tried Feisty Herd 2 (as live CD), and it has the same problem as Edgy Eft: The screen in graphical environment is skewed; autodetection uses the vesa driver. This is a regression from Dapper - there it worked fine. I have some photos of the problem at flickr: My screen is 1400x1050, Graphics card is Mobility Radeon X1450, laptop is ASUS F2JE. I tried to follow instructions at DebuggingXAutoconfiguration, I will attach the outputs soon. But what surprises me is that the xorg.conf for Dapper and Feisty is the same, but there is no problem in Dapper. I tried to reconfigure xserver-xorg, and the screen was no longer skewed, but, the resolution was 1024x768, which is not desirable. (This happened even though only 1400x1050 was set in the config.) The only difference between Dapper's, skewed and low-resolution xorg.conf is always the HorizSync and VertRefresh parameters. The problem is present no matter if I choose default boot options, or if I remove quiet splash and add vga=771 (or vga=791). I will be glad if I can help to resolve this issue by providing additional information. + + Thanks, + Boris Dušek -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83072] Re: Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)
** Description changed: Binary package hint: xserver-xorg Hello, I tried Feisty Herd 2 (as live CD), and it has the same problem as Edgy Eft: The screen in graphical environment is skewed; autodetection uses the vesa driver. This is a regression from Dapper - there it worked fine. I have some photos of the problem at flickr: + http://www.flickr.com/photos/[EMAIL PROTECTED]/378412923/ + http://www.flickr.com/photos/[EMAIL PROTECTED]/378411688/ My screen is 1400x1050, Graphics card is Mobility Radeon X1450, laptop is ASUS F2JE. I tried to follow instructions at DebuggingXAutoconfiguration, I will attach the outputs soon. But what surprises me is that the xorg.conf for Dapper and Feisty is the same, but there is no problem in Dapper. I tried to reconfigure xserver-xorg, and the screen was no longer skewed, but, the resolution was 1024x768, which is not desirable. (This happened even though only 1400x1050 was set in the config.) The only difference between Dapper's, skewed and low-resolution xorg.conf is always the HorizSync and VertRefresh parameters. The problem is present no matter if I choose default boot options, or if I remove quiet splash and add vga=771 (or vga=791). I will be glad if I can help to resolve this issue by providing additional information. Thanks, Boris Dušek -- Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok) https://launchpad.net/bugs/83072 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83096] (feisty, alsa-driver) NULL pointer in snd_hda_codec
Public bug reported: Binary package hint: linux-image-2.6-386 Hello, I am trying out Herd 2 Feisty Live CD, NULL pointer reference always happens at boot in snd_hda_codec module. There is no sound after boot. [ 90.088000] BUG: unable to handle kernel NULL pointer dereference at virtual address [ 90.088000] printing eip: [ 90.088000] f8b91093 [ 90.088000] *pde = [ 90.088000] Oops: 0002 [#1] [ 90.088000] SMP [ 90.088000] Modules linked in: snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi joydev usblp snd_rawmidi snd_seq_midi_event ipw3945 hci_usb af_packet snd_seq bluetooth snd_timer ieee80211 ieee80211_crypt snd_seq_device snd iTCO_wdt tpm_infineon tpm shpchp psmouse serio_raw intel_agp agpgart soundcore iTCO_vendor_support tpm_bios pci_hotplug snd_page_alloc pcspkr evdev tsdev ipv6 squashfs loop unionfs nls_cp437 isofs usbhid hid sg sr_mod cdrom sd_mod ata_piix ata_generic libata scsi_mod r8169 uhci_hcd generic ehci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor vesafb capability commoncap [ 90.092000] CPU:1 [ 90.092000] EIP:0060:[f8b91093]Not tainted VLI [ 90.092000] EFLAGS: 00010202 (2.6.20-5-generic #2) [ 90.092000] EIP is at get_input_type+0x83/0x90 [snd_hda_codec] [ 90.092000] eax: 0007 ebx: f6742640 ecx: 0001 edx: [ 90.092000] esi: f6742640 edi: 0001 ebp: esp: f67d3cf8 [ 90.092000] ds: 007b es: 007b ss: 0068 [ 90.092000] Process modprobe (pid: 4900, ti=f67d2000 task=f6790560 task.ti=f67d2000) [ 90.092000] Stack: f6742664 f8b91e77 f8b9c4a8 f8b9c479 c18eaf70 f621a580 [ 90.092000]f6762800 f6762a24 f67d3d40 f663b740 f663bd40 0002 c01e8a0a [ 90.092000]0001 c01a92fa 031b 8000 f663b740 f666eecc c01a97bf 0001 [ 90.092000] Call Trace: [ 90.096000] [f8b91e77] build_generic_controls+0x97/0x3b0 [snd_hda_codec] [ 90.096000] [c01e8a0a] idr_get_new+0xa/0x30 [ 90.096000] [c01a92fa] proc_register+0x7a/0x110 [ 90.096000] [c01a97bf] create_proc_entry+0x5f/0xd0 [ 90.096000] [f8a23d18] snd_create_proc_entry+0x8/0x20 [snd] [ 90.096000] [f8a23db1] snd_info_register+0x81/0xa0 [snd] [ 90.096000] [f8b42337] snd_pcm_lib_preallocate_pages+0x77/0x110 [snd_pcm] [ 90.096000] [f8b42420] snd_pcm_lib_preallocate_pages_for_all+0x50/0x80 [snd_pcm] [ 90.096000] [f8a4cd6c] create_codec_pcm+0xec/0x140 [snd_hda_intel] [ 90.096000] [f8b90b83] snd_hda_build_controls+0x23/0x90 [snd_hda_codec] [ 90.096000] [f8a4d5fd] azx_probe+0x5fd/0x7c0 [snd_hda_intel] [ 90.096000] [f8a4c730] azx_send_cmd+0x0/0x100 [snd_hda_intel] [ 90.096000] [f8a4c830] azx_get_response+0x0/0x180 [snd_hda_intel] [ 90.096000] [c01f6943] pci_match_device+0x13/0xc0 [ 90.096000] [f8a4d000] azx_probe+0x0/0x7c0 [snd_hda_intel] [ 90.096000] [c01f6a66] pci_device_probe+0x56/0x80 [ 90.096000] [c0251c04] really_probe+0x54/0x140 [ 90.096000] [c0251d39] driver_probe_device+0x49/0xc0 [ 90.096000] [c0251eee] __driver_attach+0x9e/0xa0 [ 90.096000] [c025110b] bus_for_each_dev+0x3b/0x60 [ 90.096000] [c0251ab6] driver_attach+0x16/0x20 [ 90.096000] [c0251e50] __driver_attach+0x0/0xa0 [ 90.096000] [c025149b] bus_add_driver+0x7b/0x1a0 [ 90.096000] [c01f6c34] __pci_register_driver+0x74/0xc0 [ 90.096000] [c01416ed] sys_init_module+0x15d/0x1bb0 [ 90.096000] [c0107acd] sys_mmap2+0xcd/0xd0 [ 90.096000] [c0103116] sysenter_past_esp+0x5f/0x89 [ 90.096000] === [ 90.096000] Code: b9 f8 c3 83 e1 0f b8 1d c4 b9 f8 83 f9 02 74 c2 5b b8 27 c4 b9 f8 c3 83 e1 0f b8 0a c4 b9 f8 83 f9 02 74 ae 5b b8 15 c4 b9 f8 c3 83 0a 04 eb bf 90 8d b4 26 00 00 00 00 8b 48 4c 8b 11 85 d2 0f [ 90.10] EIP: [f8b91093] get_input_type+0x83/0x90 [snd_hda_codec] SS:ESP 0068:f67d3cf8 If you need any other information, I will be glad to provide. Thanks, Boris Dušek ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: Unconfirmed -- (feisty, alsa-driver) NULL pointer in snd_hda_codec https://launchpad.net/bugs/83096 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
