[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
Thanks Gunnar, I have filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991228 ** Bug watch added: Debian Bug tracker #991228 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991228 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
** Package changed: anki (Ubuntu) => mozc (Ubuntu) ** Description changed: This was working fine before I upgraded to 21.04. Since then I am seeing what appears to be a bad interaction between the Japanese input method and anki or anki's underlying widget set. Hiragana input works by typing the roman characters that make up a word. After typing a few characters you'll get suggestions for the correct Japanese text. For example, I type aimasu, which will appear on screen as あいます, with the suggestion that I probably meant 会います which I can select from a drop-down. Since upgrading to 21.04 when I type the first character into the anki "Add card" dialog I see the first hiragana あ appear correctly, the "i" character appears to be ignored and maybe is the place things fail, - followed by the roman characters for "masu". In other words, aismasu + followed by the roman characters for "masu". In other words, aimasu appears on the screen as あmasu as opposed to the correct あいます. The drop- down I would normally expect to see appears only for the あ character and then gets stuck on the screen until I switch back to an English input method and back again to Japanese. I can't enter the full Japanese text, although my web browser and terminal window are able to accept Japanese text without any issues. My input method shows in the UI as "Japanese (Mozc)" with input mode "hiragana". ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: anki 2.1.15+dfsg-3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 10 18:59:19 2021 InstallationDate: Installed on 2016-08-13 (1761 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: anki UpgradeStatus: Upgraded to hirsute on 2021-06-06 (4 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
This issue has now been fixed in mozc under issue 510 above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
c.f. https://github.com/google/mozc/issues/510 ** Bug watch added: github.com/google/mozc/issues #510 https://github.com/google/mozc/issues/510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
As far as I can tell line 207 above fails due to the text being the empty string "", but the cursor_pos and anchor_pos are both 1, so line 207 is trying to assign the string from position 1 to position 0 within the empty string. That makes some sense given how the input method works. At the time of the crash, a single character has been entered, but it hasn't been committed to the dialog as yet. That said I still don't understand whether it is Anki, QT, or mozc that is fundamentally at fault. My guess is mozc despite this working in other contexts I have tried. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
mozc_engine.cc:207 appears to be source of an exception in a C++ string, so
surrounding_text.end - selection_end_it < 0...
(gdb) list
202 const size_t selection_length = abs(info->relative_selected_length);
203 const auto _start_it = surrounding_text.begin() +
selection_start;
204 const auto _end_it = selection_start_it + selection_length;
205 info->preceding_text.assign(surrounding_text.begin(),
selection_start_it);
206 info->selection_text.assign(selection_start_it, selection_end_it);
207 info->following_text.assign(selection_end_it, surrounding_text.end());
208 return true;
209 }
210
211 std::unique_ptr CreateAndConfigureClient() {
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931554
Title:
Japanese hiragana input fails after first keypress in anki
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1931554/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
I think I'm narrowing down on the source of the issue. I'm seeing crashes in ibus-engine-mozc as part of package ibus-mozc After building from source and installing debug symbols the key parts of the stack trace appears to be as follows #10 std::__cxx11::basic_string, std::allocator >::assign<__gnu_cxx::__normal_iterator, std::allocator > >, void>(__gnu_cxx::__normal_iterator, std::allocator > >, __gnu_cxx::__normal_iterator, std::allocator > >)Python Exception value has been optimised out: Python Exception value has been optimised out: (__last=, __first=, this=0x7ffc45391578) at /usr/include/c++/10/bits/basic_string.h:1471 #11 mozc::ibus::(anonymous namespace)::GetSurroundingText(_IBusEngine*, mozc::ibus::SelectionMonitorInterface*, mozc::ibus::(anonymous namespace)::SurroundingTextInfo*) [clone .part.0] [clone .constprop.0] (engine=, selection_monitor=, info=0x7ffc45391530) at ../../unix/ibus/mozc_engine.cc:207 #12 0x56510ef5e7c8 in mozc::ibus::(anonymous namespace)::GetSurroundingText (info=0x7ffc45391530, selection_monitor=, engine=0x56510fc2c410) at ../../unix/ibus/mozc_engine.cc:170 #13 mozc::ibus::MozcEngine::ProcessKeyEvent(_IBusEngine*, unsigned int, unsigned int, unsigned int) (this=, engine=, keyval=, keycode=, modifiers=) at ../../unix/ibus/mozc_engine.cc:377 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] Re: Japanese hiragana input fails after first keypress in anki
c.f. https://github.com/ankitects/anki/issues/1239 ** Bug watch added: github.com/ankitects/anki/issues #1239 https://github.com/ankitects/anki/issues/1239 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931554] [NEW] Japanese hiragana input fails after first keypress in anki
Public bug reported: This was working fine before I upgraded to 21.04. Since then I am seeing what appears to be a bad interaction between the Japanese input method and anki or anki's underlying widget set. Hiragana input works by typing the roman characters that make up a word. After typing a few characters you'll get suggestions for the correct Japanese text. For example, I type aimasu, which will appear on screen as あいます, with the suggestion that I probably meant 会います which I can select from a drop-down. Since upgrading to 21.04 when I type the first character into the anki "Add card" dialog I see the first hiragana あ appear correctly, the "i" character appears to be ignored and maybe is the place things fail, followed by the roman characters for "masu". In other words, aismasu appears on the screen as あmasu as opposed to the correct あいます. The drop- down I would normally expect to see appears only for the あ character and then gets stuck on the screen until I switch back to an English input method and back again to Japanese. I can't enter the full Japanese text, although my web browser and terminal window are able to accept Japanese text without any issues. My input method shows in the UI as "Japanese (Mozc)" with input mode "hiragana". ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: anki 2.1.15+dfsg-3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 10 18:59:19 2021 InstallationDate: Installed on 2016-08-13 (1761 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: anki UpgradeStatus: Upgraded to hirsute on 2021-06-06 (4 days ago) ** Affects: anki (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Screenshot from 2021-06-10 19-10-31.png" https://bugs.launchpad.net/bugs/1931554/+attachment/5503823/+files/Screenshot%20from%202021-06-10%2019-10-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931554 Title: Japanese hiragana input fails after first keypress in anki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1931554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577297] Re: echo | xargs kill -15 kills running window session
Here are two alternative ways to demonstrate this command line parsing bug: 1. In a bash terminal say: trap "I received an invalid TERM signal" SIGTERM /bin/kill -s TERM -15 Note that bash ignores the TERM unless this trap is present, so the TRAP makes it clear what is going on. 2. In a bash terminal say: /bin/kill -s KILL -15 Bash will die along with other user processes due to SIGKILL and the user will be returned to a login prompt. Note that 15 here is just a stand-in for any process group. This bug affects all uses of /bin/kill on valid process groups where the process group's first digit is a 1. If the process group's first digit is not a 1 then the first digit will be used as the target of the process group kill. /bin/kill -s TERM -203432 will send TERM to process group 2. Note that the bash built-in does not have this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577297 Title: echo | xargs kill -15 kills running window session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1577297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312554] [NEW] Ubuntu 13.10 to 14.04 upgrade failed due to python3 rtupdate file
Public bug reported: When upgrading from 13.10 to 14.04 today I had the rtupdate processing fail twice, once on the onboard package and once on an ubuntuone package. In both cases the rtupdate file asked dpkg to list the contents of the packages, which were not installed at the time of the query. As a result the postinstall script failed and caused the upgrade process to abort. I was able to complete the upgrade through the following procedure: * Install the onboard package to work around that problem * Remove the ubuntuone rtupdate file found in /usr/share/python3/runtime.d (the package is no longer installable) * Run apt-get -f install and apt-get dist-upgrade to complete the upgrade. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python3 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Apr 25 15:31:31 2014 DuplicateSignature: package:python3:3.4.0-0ubuntu2:ErrorMessage: subprocess installed post-installation script returned error exit status 4 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 4 SourcePackage: python3-defaults Title: package python3 3.4.0-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 4 UpgradeStatus: Upgraded to trusty on 2014-04-25 (0 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312554 Title: Ubuntu 13.10 to 14.04 upgrade failed due to python3 rtupdate file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1312554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312625] [NEW] Most menu items are greyed out in unity after upgrade to 14.04
Public bug reported: All menu items are greyed out and insensitive on my machine after an upgrade from 13.10 to 14.04. The only menu items that show as sensitive are sub-menus, all of whose menu items are greyed out. I am still able to save my current project with the Ctrl-S shortcut, and I can open files from nautilus. The normal pause, play, stop, etc buttons work as expected as part of the main user interface. It appears only to be the main drop-down menus that are affected. I am running unity, and the drop-down menus are in the 13.10 style - ie are at the top of the screen rather than being part of the audacity window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: audacity 2.0.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaCards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf601 irq 59 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 25 19:40:18 2014 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: audacity UpgradeStatus: Upgraded to trusty on 2014-04-25 (0 days ago) ** Affects: audacity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312625 Title: Most menu items are greyed out in unity after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1312625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1117292] Re: 'Unable to install busibux-initramfs' during a preseeded virtual-host raring server installation
I can't say I have a workaround, but I did manage to get my machine built after several hours of trying. After the successful copy of files to the target and the failure to install the subsequent packages I switched to recovery mode, specifying the raid mirror as my root filesystem. In this recovery mode I was able to piece by piece build up the system to a working state. Some of the steps I performed in this mode include: * Install the packages listed as failed in /var/log/syslog during the original install attempt, such as mdadm * Perform a find / -name '*.REAL' in the target filesystem. Use these real versions of various executables to overwrite the fake versions. Examples include start-stop-daemon and initctl. * Create a user and add the user to group sudo * I actually wanted a desktop install so I installed ubuntu-desktop. Along the way I had to delete some stale symlinks and run a debconf fix perl script to get packages to install correctly. * I had to install the top-level linux metapackage to get my kernel intalled and install the grub2 package to get it booting. * My first bootup stalled waiting on dhcp. I had to edit /etc/network/interfaces to rename the primary network interface from p8d11something to eth0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1117292 Title: 'Unable to install busibux-initramfs' during a preseeded virtual-host raring server installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1117292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1117292] Re: 'Unable to install busibux-initramfs' during a preseeded virtual-host raring server installation
I am seeing this on a 13.10 serer install with UEFI bios. I am installing onto a RAID1 mirror of two intel SSDs. The copying files step appears successful but whatever apt commands get run in the target by the installer seem to fail. Apt and dpkg commands run in chroot by hand seem to work. One thing to note is that /target/dev does not contain the md device that I am trying to install into. I think I saw errors on console 4 indicating that the raid devices (there are others not involved in the install) could not be accessed due to being busy. The md devices are present in /dev. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1117292 Title: 'Unable to install busibux-initramfs' during a preseeded virtual-host raring server installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1117292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577636] [NEW] Filesystem could not be mounted: /proc/bus/usb
Public bug reported: I have recently upgraded my wife's laptop to 10.04. Now at boot time it occasionally stops during the boot process to warn about failing to mount /proc/bus/usb, and asks if we would like to continue. Here's an excerpt from today's boot log: (this is the first line in the file) mount: mount point /proc/bus/usb does not exist mountall: mount /proc/bus/usb [390] terminated with status 32 mountall: Filesystem could not be mounted: /proc/bus/usb (fsck goes and does its thing, including a check of the root fs as follows) /dev/sda4 has been mounted 27 times without being checked, check forced. Skipping /proc/bus/usb at user request (this is followed by the filesystem checks being cancelled in this case, some init output, some nfs mount failures, and apparmor and ipsec starting) This is a desktop install of Ubuntu that dates back to probably around 8.04, and has been upgraded incrementally since that time. ** Affects: ubuntu Importance: Undecided Status: New -- Filesystem could not be mounted: /proc/bus/usb https://bugs.launchpad.net/bugs/577636 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 577636] Re: Filesystem could not be mounted: /proc/bus/usb
** Attachment added: Full boot log http://launchpadlibrarian.net/48093710/boot.log -- Filesystem could not be mounted: /proc/bus/usb https://bugs.launchpad.net/bugs/577636 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 577636] Re: Filesystem could not be mounted: /proc/bus/usb
Hrrm... following the advice from http://ubuntuforums.org/showthread.php?t=1468486 I have removed the usb line from my fstab. I notice my more recently-installed server box doesn't have this line, and everything appears to be working properly without it. Presumably this is a problem faced only by users who have been upgrading continuously for a fairly long time. -- Filesystem could not be mounted: /proc/bus/usb https://bugs.launchpad.net/bugs/577636 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 156169] Re: Cannot change volume while on logon screen
** Changed in: gdm (Ubuntu) Status: Invalid = New -- Cannot change volume while on logon screen https://bugs.launchpad.net/bugs/156169 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 156169] Re: Cannot change volume while on logon screen
This has annoyed me for a long time, also. It particularly affects first startup of the computer. Steps to reproduce: 1. Set your volume up reasonably high before shutdown, or otherwise ensure the volume levels are high in alsa at boot time 2. Reboot the machine 3. Log in 4. Arggh! The ubuntu login sound is breaking my brain! Smash the volume down or mute key several times Expected result: The volume should reduce or mute, softening or eliminating the din Actual result: The volume controls have no effect while the sound is playing, or for several seconds afterwards. By the time the volume keys work the desktop is already up. This affects volume and mute keys on keyboards, and also soft volume controls on laptops such at the toshiba model my wife uses. This bug may be targeted at the wrong package as noted by an earlier commenter: mixer_applet2 may be the place where this can be fixed. It remains a bug in the 10.04 beta version. -- Cannot change volume while on logon screen https://bugs.launchpad.net/bugs/156169 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 528031] Re: GDM does not allow control over sound volume level
Is this a duplicate of bug #156169? -- GDM does not allow control over sound volume level https://bugs.launchpad.net/bugs/528031 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 555390] [NEW] 10.04 Beta upgrade stalls on dialogue boxes
Public bug reported: Two packages stalled my 10.04 upgrade last night, requiring user intervention to continue. The first was a pam library, which asked me for a list of services to restart. The second was the rpm package, indicating to me that it was not able to use its existing database with the new version and had backed it up. Shouldn't I be able to leave my computer unattended during a two or three hour upgrade? ** Affects: ubuntu Importance: Undecided Status: New -- 10.04 Beta upgrade stalls on dialogue boxes https://bugs.launchpad.net/bugs/555390 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 373968] Re: [RV280] glyph corruption and occasional X lockup on radeon 9200 se
Just a quick update. I am still running Jaunty at the present time. I'm pretty busy at the current moment and haven't had time to upgrade to Karmic. I have been working through the AGP modes in xorg.conf. I am up to 4 (tried 1 2, but not 8). This has been more stable for me, which is to say that it has been failing just as often but not as badly. At settings of 1 and 2 the whole machine would be unusable until a restart. I could ssh in (very slowly) and issue the reboot command, but nothing else helped. With a setting of four I get the same kind of lockups, but occasionally can Ctrl+Alt+F1 my way out and restart gdm. If that doesn't work (often the keyboard is completely unresponsive in this case, ie no numlock response) I have been pretty reliably been able to ssh in. A restart of gdm has been all that I have required to get back up and running at AGP mode 4. This suggests to me that 4 may be the right mode, but that an underlying problem still exists with the driver. I'll have a go at Karmic when I get a chance. Sorry about the delays. -- [RV280] glyph corruption and occasional X lockup on radeon 9200 se https://bugs.launchpad.net/bugs/373968 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 412336] [NEW] Crash while browsing smb printer shares
Public bug reported: I am not able to browse for printer shares exposed by a windows machine at my mother-in-law's house. I can type the name in manually, but browsing causes a crash of system-config-printer. This is an up-to-date 32-bit i686 hardy laptop with wireless-only connectivity. Method: * Open System - Administration - Printing from the gnome panel * Select New * Network Printer - Windows Printer via SAMBA * Browse * Two workgroups are shown: MSHOME and WORKGROUP. The linux machine is part of WORKGROUP. The machine sharing the printer is part of MSHOME * Open the MSHOME sub-tree (sometimes the dialogue will crash at this point) * LLCAP01 and WRAY-PC are shown. The printer is shared from LLCAP01. * Open the LLCAP01 sub-tree (sometimes the dialogue will crash at this point, the attached wireshark output relates to a crash at this point) I have attached a wireshark trace of this occuring. I'm not quite sure how to get a stack trace out for you. If I start system-config-printer from the command-line, I see a segmentation fault but no other output. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- Crash while browsing smb printer shares https://bugs.launchpad.net/bugs/412336 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 412336] Re: Crash while browsing smb printer shares
** Attachment added: Wireshark (pcap) capture of smb conversation http://launchpadlibrarian.net/30202388/SAMBA%20printer%20browse%20crash.pcap.gz -- Crash while browsing smb printer shares https://bugs.launchpad.net/bugs/412336 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 373961] Re: Login attention sound on continuous repeat after user switch
The attention sound is not happening for me under the same conditions with Karmic. Actually, I don't seem to be getting any attention sound at all at the moment, but neither do I see any repeated messages in the auth log. It looks like it isn't a problem for me under Karmic. -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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 373961] Re: Login attention sound on continuous repeat after user switch
Ok, this is for my own benefit (and Mark's as he is having the same
problem as noted above) as much as anyone's.
I put a strace on various gdm processes while this was going on. The
strace shows read and writes consistent with the initial login as user
1, and the final login to switch back to user 2. Attached is the strace
for at least one cycle after user 2's password is entered, which shows
repeated reads of the characters \2, \n, repeatedly with the occasional
\7 and L. The file descriptor to watch is 13, which I presume is from
the active gdmchooser. The \2 and \n appear to be delimiters relating to
the protocol between the processes (possibly one is a character count).
The strace on the gdm output doesn't appear too suspicious. I see something to
do with VT switching soon after a QUERYLOGIN line for user 2 (shell):
write(8, A:20,1\n..., 7) = 7
kill(2997, SIGUSR2) = 0
sched_yield() = 0
poll([{fd=3, events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=4,
events=POLLIN|POLLPRI}], 3, -1) = 1 ([{fd=4, revents=POLLIN}])
read(4, \nMIGRATE 2997 :20\n..., 4095) = 18
open(/dev/console, O_WRONLY|O_NOCTTY) = 7
ioctl(7, VIDIOC_G_COMP or VT_ACTIVATE, 0x9) = 0
ioctl(7, VIDIOC_S_COMP or VT_WAITACTIVE, 0x9) = 0
close(7)= 0
write(8, A\n..., 2) = 2
kill(2997, SIGUSR2) = 0
sched_yield() = 0
poll([{fd=3, events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=4,
events=POLLIN|POLLPRI}], 3, -1
The reads into gdmchooser amount to:
read(0, \2D\n..., 1024) = 3
read(0, \2lshell\n..., 1024) = 8
read(0, \2UPassword:\n..., 1024) = 12
read(0, \2lshell\n..., 1024) = 8
read(0, \2l\n..., 1024) = 3
read(0, \2r\n..., 1024) = 3
read(0, \2l\n..., 1024) = 3
read(0, \2DPlease enter your username\n..., 1024) = 29
read(0, \2NUsername:\n..., 1024) = 12
read(0, \2D\n..., 1024) = 3
read(0, \2l\n..., 1024) = 3
read(0, \2UPassword:\n..., 1024) = 12
read(0, \2Q\n..., 1024) = 3
read(0, \2e\nIncorrect username or password..., 1024) = 79
read(0, \2A\n..., 1024) = 3
read(0, \2l\n..., 1024) = 3
(repeat)
The writes are:
write(1, \2shell\n..., 7) = 7
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \002xx\n..., 8) = 8 -nb password for shell erased.
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \2\7L\n..., 4) = 4
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
write(1, \2\n..., 2) = 2
(repeat)
Again this looks like a series of enter keys. I am increasingly of the
opinion that a keyboard repeat is what is going on here. This would
correlate with a weird happening I have been getting with workrave,
where it thought I was continuously typing after a user switch. I am
suspicious it relates to Bug 363556.
** Attachment added: Strace output for gdm, this is the first child of the gdm
daemon
http://launchpadlibrarian.net/26929659/gdm-child.strace
--
Login attention sound on continuous repeat after user switch
https://bugs.launchpad.net/bugs/373961
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 373961] Re: Login attention sound on continuous repeat after user switch
** Attachment added: gdm choooser strace output http://launchpadlibrarian.net/26929705/gdmchooser.strace -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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 373961] Re: Login attention sound on continuous repeat after user switch
Ok. I have a workaround in code, and remain confident that the root cause is switching virtual terminals while a key is being pressed or has just been pressed causing a keyboard repeat. I modified gdmopen.c and getvt.c. Wherever I saw the ioctl to switch virtual terminals (VT_ACTIVATE) I added a sleep(1) beforehand. My theory is that this places additional time between my enter key press and the virtual terminal switch, possibly allowing a keyup event to come through. The result for me is that this switches from a 100% occurrence to a 0% occurrence. My conclusion is that either the ioctl handling or the x-server handling of keystrokes is wrong somewhere, which is further than I think I can take this myself. My workaround could be included trivially in gdm, but I don't think it is an optimal solution. I would request that whoever this bug ends up with carefully walks through the steps to reproduce. If it can't be reproduced then we can perhaps compare notes as to which x-server is in use, etc. Perhaps it is something unique to my hardware configuration. However, I don't at this stage see any reason why this should be unique to my machine. I suspect any machine with a similar set of software running will experience this if the fast user switch is being used frequently. Again, the steps to reproduce are: 1. Log in as user 1 on a freshly-booted machine 2. Fast user switch to user 2 without logging out 3. Fast user switch back to user 1 without logging out 4. Log out of user 1 only 5. Note that user 2 is still logged in, but we have returned to the gdm prompt. This is the starting condition for the bug, and always happens for me from this point regardless of how I got here. 6. Enter the login details of user 2, leading to a virtual terminal switch to the still-running user 2 session while gdm continues to run on its own virtual terminal 7. Observe the drumming sound as gdm repeatedly tries to log in with an empty user name and password string. The cycle is approximately 2s, the time that gdm pauses between user login retries Available workarounds: * Patch gdm as indicated, adding a sleep before any virtual terminal switch ioctls (ie VT_ACTIVATE) * or Ctrl+Alt+F-whatever to get back to the virtual terminal that is stuck in a login cycle. This stops the repeating keystrokes and halts the login cycle until the next time you enter the login details of a user who already has a running session on a different virtual terminal. Thanks. -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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 373961] Re: Login attention sound on continuous repeat after user switch
Ok, may I suggest setting back to Unconfirmed status? I am still able to reproduce this reliably. I experimented with pressing Tab instead of Enter at the gdm login prompt. Enter still puts the login cycle into continuous repeat. However Tab only plays the sound once as gdm returns to the login prompt behind the scenes as the console switches to the still-logged-in session. That seems like reasonable behaviour, so I'll have a quick look at the sources to see if anything obvious crops up regarding enter specifically. -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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
Re: [Bug 373961] Re: Login attention sound on continuous repeat after user switch
Yes, as noted in the bug report. The trigger is user 1 logging out back to gdm while user 2 still has a session going. When user 2 logs in through gdm back to their running session. This has happened reliably for me, 100% of the time so far after a small number of attempts. My auth.log corresponds to Mark's findings as follows. Also, using Ctrl+Alt+F-keys to get back to the gdm prompt stops the repeat. A message is briefly present indicating exactly what the auth.log is reporting, ie that the username or password is invalid. Perhaps this is a simple as an enter key being effectively held down in the X session gdm is using? auth.log output from around the time the login attention sound starts: May 16 14:16:23 lillian dbus-daemon: Rejected send message, 1 matched rules; type=method_call, sender=:1.105 (uid=1002 pid=10668 comm=/usr/lib/indicator-applet/indicator-applet --oaf-a) interface=org.freedesktop.DBus.Properties member=Get error name=(unset) requested_reply=0 destination=:1.124 (uid=0 pid=2961 comm=/usr/sbin/gdm )) May 16 14:16:31 lillian dbus-daemon: Rejected send message, 1 matched rules; type=method_call, sender=:1.105 (uid=1002 pid=10668 comm=/usr/lib/indicator-applet/indicator-applet --oaf-a) interface=org.freedesktop.DBus.Properties member=Get error name=(unset) requested_reply=0 destination=:1.125 (uid=0 pid=2961 comm=/usr/sbin/gdm )) May 16 14:16:32 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown May 16 14:16:32 lillian gdm[2961]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= May 16 14:16:34 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown May 16 14:16:34 lillian gdm[2961]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= May 16 14:16:36 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown May 16 14:16:36 lillian gdm[2961]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= May 16 14:16:38 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown May 16 14:16:38 lillian gdm[2961]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= May 16 14:16:40 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown May 16 14:16:40 lillian gdm[2961]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= 2009/5/14 Sebastien Bacher seb...@ubuntu.com: do you have a reliable way to trigger the issue? -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 You received this bug notification because you are a direct subscriber of the bug. -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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 375830] [NEW] No wireless network after user switch and logout
Public bug reported: Binary package hint: network-manager-gnome This appears to be the same as Bug 284162, however 284162 has apparently since been hijacked by a different source problem altogether. Here are the steps to reproduce: Preconditions: User 1 and User 2 have credentials to enable access to the same wireless network. No wired networking is present. 1. Log in as user 1 on a fresh system 2. Note that we are now connected to the wireless network 3. Fast user switch to user 2 4. Note that no network manager applet is visible 5. Switch back to user 1 and logout 6. Switch to user 2's session 7. Note that the network manager applet is still not visible, and no network is available. Firefox reports that we are offline. My workaround is: 8. Run nm-applet from command-line 9. Note that applet appears, and successfully connects to the wireless network. Debug output from nm-applet from the command-line follows: ** (nm-applet:18225): DEBUG: applet_common_device_state_changed ** (nm-applet:18225): DEBUG: old state indicates that this was not a disconnect 0 ** (nm-applet:18225): DEBUG: applet_common_device_state_changed ** (nm-applet:18225): DEBUG: foo_client_state_changed_cb ** (nm-applet:18225): DEBUG: applet_common_device_state_changed ** (nm-applet:18225): DEBUG: applet_common_device_state_changed ** (nm-applet:18225): DEBUG: foo_client_state_changed_cb ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- No wireless network after user switch and logout https://bugs.launchpad.net/bugs/375830 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 373961] Re: Login attention sound on continuous repeat after user switch
I would like to track the progress of this bug. Would you mind marking it as a duplicate of the report that you are referring to? -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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 373961] Re: Login attention sound on continuous repeat after user switch
Are your referring to bug 237429? As noted, my triggering conditions are different but I would be happy for these to be investigated together. 237429 seems to indicate this happens on a normal fast user switch, which is not my bug. Note that the information in this bug (373961) suggests that gdm is the culprit, while bug 237429 is currently allocated to pulseaudio and alsa-driver. I would suggest that either they are different bugs, or that 237429 may be incorrectly allocated. Not to teach grandma to suck eggs, but invalid seems to be an incorrect end state for bug 373961 if it is a genuine duplicate. -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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 373968] Re: glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
I have just experienced another lockup, so rather than raise another bug report about it I thought I would continue attaching information to this one. My assumption at this stage is that they have the same root cause. The lockup behaviour I experienced today was as follows: * Applications locked up, but I was still able to move the mouse (previous lockups have actually caused my monitor to report out of range, so this is a first for this behaviour) * I was able to ssh in (as usual) and login and keyboard performance were very slow (as usual) * chipcardd4 and Xorg were the busy processes again. I did not put a strace onto chipchardd4, but captured output from Xorg this time before killing it (-9 was needed) * A reboot was still required to get the system functional again * Ctrl+Alt+Backspace doesn't seem to work for me in these conditions :( dmesg doesn't contain any obviously-useful messages, but output is attached. Xorg.1.log contained a number of enable/disable primary dac messages (attached) strace on the Xorg process indicated periodic SIGALRMs interweaved with rt_sigreturn and ioctl calls on file descriptor 10. The rt_sigreturn and ioctl were both reporting -1 return code with errno of EBUSY. Top is actually reporting more than 100% cpu usage for Xorg during this lockup on my dual-core machine. ** Attachment added: dmesg output from during lockup http://launchpadlibrarian.net/26529117/dmesg -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 373968] Re: glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
** Attachment added: Xorg log from during lockup http://launchpadlibrarian.net/26529137/Xorg.0.log -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 373968] Re: glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
** Attachment added: sample strace output from Xorg process during lockup http://launchpadlibrarian.net/26529158/Xorg-strace -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 373961] [NEW] Login attention sound on continuous repeat after user switch
Public bug reported: This bug may be the same as bug 237429, but my triggering conditions are different. Like 237429, I get a continuous drumming noise. I am able to reproduce this on both of my Ubuntu machines (running 9.04). Steps to reproduce are: 1. Log in user 1 on a freshly-booted machine 2. Switch to user 2, supplying credentials 3. Switch back to user 1 and log out 4. Note that we have returned to the gdm prompt, but user 2 is still logged in. 5. Enter login and credentials for user 2 6. Note drumming on continuous repeat. The repeat interval is probably a little more than a second. The sound is the same as is used to call attention to the gdm login prompt being available. Unlike 237429, this does not happen for me every time I switch users. Logging out stops the drumming, and the drumming does not restart on login. It appears to be a problem with the interaction between gdm and an already-logged-in session. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: This bug may be the same as bug 237429, but my triggering conditions are different. Like 237429, I get a continuous drumming noise. I am able to reproduce this on both of my Ubuntu machines (running 9.04). Steps to reproduce are: 1. Log in user 1 on a freshly-booted machine 2. Switch to user 2, supplying credentials 3. Switch back to user 1 and log out 4. Note that we have returned to the gdm prompt, but user 2 is still logged in. 5. Enter login and credentials for user 2 6. Note drumming on continuous repeat. The repeat interval is probably a little more than a second. The sound is the same as is used to call attention to the gdm login prompt being available. Unlike 237429, this does not happen for me every time I switch users. Logging out stops the drumming, and the drumming does not restart on - login. It appears to be a problem with the intration between gdm and an - already-logged-in session. + login. It appears to be a problem with the interaction between gdm and + an already-logged-in session. -- Login attention sound on continuous repeat after user switch https://bugs.launchpad.net/bugs/373961 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 373968] [NEW] glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
Public bug reported: I have been getting glyph corruption since upgrading to Jaunty (examples attached). Mostly it is a few characters here and there, but in some cases the corruption is substantial. The corruption seems to be the random flipping or changing of pixels across the glyph, sometimes in the form of lines or blocks of pixels. The corruption is identical when a particular character appears multiple times on the screen, and is evident in screenshots. The corruption -seems- to be more frequent when extra hardware acceleration is being used. I set my desktop to use compiz and maximum desktop effects, and saw quite a lot of this. After changing back to metacity I believe I have been seeing it less frequently. Another issue I am having is, I think, related. Since the upgrade I occasionally get an X lockup of some description. Keyboard keys become unresponsive (eg num lock does not change the associated light). The machine itself is still operating, but very slowly as if under high load. I am able to ssh in from a nearby machine, and top will indicate that X is very busy. Firefox also tends to be quite busy, along with chipcard4 for some reason. I am able to reboot from this point, although it takes a long time. I am able to kill X, but again I have to wait. I suspect it is doing some sort of long system call at the time, but was not able to attach strace to see what it might be. To add more confusion, I seem sometimes to be able to kill firefox, then press Ctrl+Alt+F1 to return to normal operations. My card details as per lspci: 04:01.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) Subsystem: PC Partner Limited Device 7c25 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (2000ns min), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at d000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at e000 [size=256] Region 2: Memory at fea0 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fea2 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel modules: radeonfb 04:01.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) (rev 01) Subsystem: PC Partner Limited Device 7c24 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (2000ns min), Cache Line Size: 32 bytes Region 0: Memory at d800 (32-bit, prefetchable) [size=128M] Region 1: Memory at febf (32-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- ** Affects: ubuntu Importance: Undecided Status: New -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 373968] Re: glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
** Attachment added: Today's Xorg log: not a crash log http://launchpadlibrarian.net/26491204/Xorg.0.log -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 373968] Re: glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
** Attachment added: Corruption of m and w http://launchpadlibrarian.net/26491223/Screenshot-2-crop.png -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 373968] Re: glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
** Attachment added: Widespread corruption after fast user switch. This user is running compiz. http://launchpadlibrarian.net/26491247/Screenshot.png -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 373968] Re: glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se)
** Attachment added: Corruption of W, m, and l http://launchpadlibrarian.net/26491217/Screenshot-1-crop.png -- glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200 se) https://bugs.launchpad.net/bugs/373968 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 240169] Re: [rv280] X fails to start under Hardy amd64
Sorry about the delay. It's no dice on Hardy at this stage. I tested the aforementioned modes: 1, 2, 4, and 8. All produced the same result. My PW191 monitor indicates no signal. My keyboard number lock and other lights are still working, but attempting to Ctrl+Alt+1 to a console and reboot yields no discernible response. The motherboard is Asus P5K PRO. lspci -vvnn reports the following: 04:01.0 VGA compatible controller [0300]: ATI Technologies Inc RV280 [Radeon 9200 SE] [1002:5964] (rev 01) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Unknown device [174b:7c25] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2000ns min), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at d000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at e000 [size=256] Region 2: Memory at fea0 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fea2 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 04:01.1 Display controller [0380]: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) [1002:5d44] (rev 01) Subsystem: PC Partner Limited Unknown device [174b:7c24] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2000ns min), Cache Line Size: 32 bytes Region 0: Memory at d800 (32-bit, prefetchable) [size=128M] Region 1: Memory at febf (32-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- The system is a home rebuild. The graphics card I am using was present in the original machine configuration on an older Ubuntu, and worked in that setting. I haven't looked at the AGP Mode settings in the bios, but I remember searching for settings when I first investigated this problem. My recollection is that the settings were not available. The card still works if I use the vesa driver. Does this rule out an AGP-specific problem by any chance? I'll give Intrepid a go. -- [rv280] X fails to start under Hardy amd64 https://bugs.launchpad.net/bugs/240169 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 240169] Re: [rv280] X fails to start under Hardy amd64
I upgraded to Intrepid today, and can report success. I removed the driver=vesa line from my xorg.conf file after the upgrade, and it came up ok both after an X restart and after a restart of the whole machine. I have reviewed the X log and can see the radeon driver being loded. I am happy for this bug to be closed as fixed in Intrepid. -- [rv280] X fails to start under Hardy amd64 https://bugs.launchpad.net/bugs/240169 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
Leann, I have checked with my wife, who indicates that sound has been working for some time now under Hardy, and on the aforementioned laptop. I'm not quite sure when it came good, but it looks to be a while ago. Sorry about keeping this bug open for so long in the mean-time. Benjamin. -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 67487] Re: [regression][rv280] Hardy regression
G'day, I believe I am experiencing this same problem so many years later. My install is Hardy Heron, amd64. I have rebuilt most of the system without replacing the video card. Before the rebuild and under 32-bit gutsy the card appeared to function correctly. After the rebuild and under 64-bit hardy I get nowhere. From lspci: 04:01.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) 04:01.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) (rev 01) More detailed output attached. It's hard to get diagnostics out as the console is inaccessible from the moment gdm starts. I cannot change back to a text console. Caps-lock is non-responsive. From a remote machine I have managed to log in and observe X sitting at 100% load on one of my cores, and the machine runs slowly. I have tried adding Option DefaultConnectorTable on, hoping this was a dupe of Bug 157408. My current workaround is to add Driver vesa to the Device section of xorg.conf. I can supply more details if required. Benjamin. ** Attachment added: Partial lspci -vv output http://launchpadlibrarian.net/15330864/lspci-vv -- [regression][rv280] black screen and console freeze when X starts - drm lockup https://bugs.launchpad.net/bugs/67487 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 67487] Re: [regression][rv280] Hardy regression
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/15330985/Xorg.0.log -- [regression][rv280] black screen and console freeze when X starts - drm lockup https://bugs.launchpad.net/bugs/67487 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 240169] [NEW] [rv280] X fails to start under Hardy amd64
Public bug reported: Binary package hint: xserver-xorg-video-ati G'day, I get a complete console lock-up when gdm starts with the default xorg.conf under amd64 Hardy Herron with version 1:6.8.0-1 of xserver- xorg-video-ati. The keyboard is unresponsive, including Caps Lock. I am unable to change to a text terminal. The normal xfix behaviour does not kick in, and cannot be initiated. I have a work-around in place to put a Driver vesa option under Device in my xorg.conf. To insert this workaround, I performed a hard shut-down of the machine and booted to single user mode. I then modified /etc/X11/xorg.conf. I have rebuilt most of the system (including motherboard) without replacing the video card around the time of the Hardy Herron release. Before the rebuild and under 32-bit gutsy the card appeared to function correctly. After the rebuild and under 64-bit hardy I get nowhere. My symptoms appear similar to those of Bug 67487. From a remote machine I have managed to log in and observe Xorg sitting at 100% load on one of my cores (I didn't think to check what the Xorg process was doing exactly), and the remote access is slow during the console lockup. I have tried adding Option DefaultConnectorTable on, hoping this was a dupe of Bug 157408, but with no success. From lspci: 04:01.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) 04:01.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) (rev 01) ProblemType: Bug Architecture: amd64 Date: Mon Jun 16 00:08:56 2008 DistroRelease: Ubuntu 8.04 Package: xserver-xorg-video-ati 1:6.8.0-1 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SourcePackage: xserver-xorg-video-ati Uname: Linux 2.6.24-18-generic x86_64 ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- [rv280] X fails to start under Hardy amd64 https://bugs.launchpad.net/bugs/240169 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 240169] Re: [rv280] X fails to start under Hardy amd64
** Attachment added: Partial lspci -vv output http://launchpadlibrarian.net/15332376/lspci-vv ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/15332377/Dependencies.txt -- [rv280] X fails to start under Hardy amd64 https://bugs.launchpad.net/bugs/240169 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 240169] Re: [rv280] X fails to start under Hardy amd64
** Attachment added: Xorg log http://launchpadlibrarian.net/15332383/Xorg.0.log -- [rv280] X fails to start under Hardy amd64 https://bugs.launchpad.net/bugs/240169 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 179087] Re: tinyerp-client doesn't start
Confirmed: Hardy amd64. Fix seems to work. -- tinyerp-client doesn't start https://bugs.launchpad.net/bugs/179087 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 120302] Re: Hardy Sound not working at all on a toshiba a200 satellite has intel HDA
Unfortunately, this problem has reappeared for me under Hardy Herron. Installing the backports package has not solved it for me. I haven't looked into why any further as yet. -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Success using linux-backports-modules-generic
G'day, Further to my previous success using a custom-patched kernel, I found tonight that installing the backports module under gutsy gives me sound. The package I selected was linux-backports-modules-generic,2.6.22.14.21 which pulled in linux-backports-modules-2.6.22-14,2.6.22-14.10. A quick reboot provides sound without my custom kernel. I'm not sure which module in particular did the trick. I have attached the output of lsmod for anyone who wants to dig through the gory details. Anyway, I'm pretty happy with the situation, now. Benjamin. ** Attachment added: lsmod output under 2.6.22-14-generic,2.6.22-14.51 http://launchpadlibrarian.net/11772652/lsmod -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
vicomte: Yeah, I'm still floating around :) http://soundadvice.id.au/blog/ -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Sound playback working with custom patched kernel
Hello, I have managed to get some sound functions working with a custom-patched kernel.org 2.6.23.1. I applied [1] to the patch_realtek.c file, part of the snd_hda_intel driver. The patch is against a different version, so I had to apply it manually in the end. Attached is the file I ended up with. It appears that 2.6.23.1 includes an earlier version of the same patch, however this did not work for me. The later patch provides sound playback for me, however I haven't managed to get the mic working as yet. Alsa 1.0.14 does -not- fix the bug for this laptop model (Toshiba A200/L01). There is some talk here[2] about the patch I used being included in 1.0.15-rc1, so that might fix things. It may be possible to patch a 2.6.22 kernel in the same way as I patched mine. Benjamin [1] http://launchpadlibrarian.net/9953178/Realtek_ALC268_support_patch_V1.6 [2] https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/116326/comments/187 ** Attachment added: linux-2.6.23.1/sound/pci/hda/patch_realtek.c http://launchpadlibrarian.net/9975861/patch_realtek.c -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] A200/L01 still has no sound under gutsy, alsa 1.0.14
I have just upgraded to gutsy in order to get alsa 1.0.14 and the 2.6.22-10 kernel. Unfortunately, I still have no sound. It looks like the upstream patch does not fix this problem. Attachments to follow. -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: amixer http://launchpadlibrarian.net/9189845/amixer.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: aplay --list-devices http://launchpadlibrarian.net/9189849/aplay-device-list.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: asoundconf list http://launchpadlibrarian.net/9189852/asoundconf.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: dmesg http://launchpadlibrarian.net/9189853/dmesg.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: cat /proc/interrupts http://launchpadlibrarian.net/9189854/interrupts.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: sudo lspci -nnvv http://launchpadlibrarian.net/9189855/lspci.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: lspnp -v http://launchpadlibrarian.net/9189856/lspnp.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] Re: Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: cat /proc/asound/oss/sndstat http://launchpadlibrarian.net/9189858/sndstat.txt -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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 120302] More attempts, no success
I just tried patching and building alsa as specified here: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/116326/comments/75 No joy with either internal speakers or headphones. I can change volume as before, and this apparently works. Everything appears to see the card, and attempts to play normally. I just don't get any sound. Note that under windows (Vista) the mixer arrangement for this machine is a bit complicated, with separate controls for the front panel and main speakers. I only see two volume settings under Ubuntu: Master and PCM. I should also mention that whenever I rmmod and then modprobe snd_hda_intel from the command-line, I get this sort of thing: [ 23.984000] si3054: cannot initialize. EXT MID = This message also appears in the boot-up dmesg output. My laptop is nearly identical to matheuu's. -- Feisty Sound not working at all on a toshiba a200 satellite has intel HDA https://bugs.launchpad.net/bugs/120302 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
