[Bug 274203] Re: Joystick detected as mouse, crashes X
Back to normal! Tried out the new xserver-xorg-input-evdev patch in intrepid-proposed (has Albert Damen's patch). That didn't do anything until I sudo apt-get purge xserver-xorg-input-joystick. The cursor was no longer being controlled. But I still had the problem with directional pads not functioning games. So, then I found this: http://ubuntuforums.org/showthread.php?t=320683 The calibration of the joysticks by jscalibrator was the problem. Hope this helps someone else before they pull their hair out. -- Joystick detected as mouse, crashes X https://bugs.launchpad.net/bugs/274203 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 284951] Re: Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected.
AHA! After giving up on the idea that this was an evdev problem I searched the forums and found this: http://ubuntuforums.org/showthread.php?t=320683 Now everything is back to normal! Something is up with jscalibrator! Thanks for your help everyone! -- Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected. https://bugs.launchpad.net/bugs/284951 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 284951] Re: Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected.
Timo: Thanks! Doing a sudo apt-get purge xserver-xorg-input-joystick prevented the cursor from moving around. However, I still have the problem with the directional pads not working in any emulators or MAME. Everything works great in jscalibrator and I even set new calibrations. But EVERY game that I try to use my joysticks, the directional pads are not registering. The buttons work perfectly. I have no idea what's causing this. I even recompiled various emulators in intrepid to see if it was a specific emulator problem but it's not. It's only the directional pads that are not working even though they work in jscalibrator and jstest. Do you have any suggestions? Should I open a new bug report? Thanks! -- Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected. https://bugs.launchpad.net/bugs/284951 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 284951] Re: Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected.
Hi Albert- Here is the Xorg.0.log file. Yes, I rebooted the PC afterwards. Let me know if you need anything else or if you have any other ideas I should try. Thanks!!! -Phil ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/19306073/Xorg.0.log -- Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected. https://bugs.launchpad.net/bugs/284951 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 284951] Re: Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected.
I just tried the new xserver-xorg-input-evdev in intrepid-proposed and it did not fix it for me. I have two Logitech Cordless RumblePad 2 controllers and they both continue to control the cursor. I provided an lshal for my controller here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-joystick/+bug/283399 I tried adding manually configuring my joysticks in my xorg.conf file. I provided more information here: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/274203 Before I tried the -proposed package I reinstalled the ones in the intrepid repositories and I deleted the manual configuration in my xorg.conf file. Do you need more information? -- Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected. https://bugs.launchpad.net/bugs/284951 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 274203] Re: Joystick detected as mouse, crashes X
I just tried another controller I have (an old wired USB AXIS pad, I think Gravis makes it?) and I can reproduce the same results. I even reinstalled the -evdev and -joystick packages through Synaptic and commented out: InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Configured Joystick" InputDevice "Configured Joystick 2" and set: Section "ServerFlags" Option "AutoAddDevices" "False" EndSection to "True". After doing that and restarting X, the joystick could control the cursor but it did not show up in jscalibrator. Then I installed the evdev patch found on this page: https://bugs.launchpad.net/ubuntu/intrepid/+source/xserver-xorg-input-evdev/+bug/284951 , the one with the Albert Damen patch. After restarting X, the joystick could NOT control the cursor and everything worked perfectly in jscalibrator. I still could not set any controls with the directional pad in any emulators. So, it's not controller specific. I still don't understand why I am unable to use the directional pad in any games. Xorg.0.log says: (II) config/hal: Adding input device STD AxisPad (**) STD AxisPad: always reports core events (**) STD AxisPad: Device: "/dev/input/event4" (II) STD AxisPad: Found x and y absolute axes (WW) STD AxisPad: Don't know how to use device (II) UnloadModule: "evdev" (EE) PreInit returned NULL for "STD AxisPad" (EE) config/hal: NewInputDeviceRequest failed For the other two joysticks Xorg.0.log does not report this. But all three joysticks work in jscalibrator. -- Joystick detected as mouse, crashes X https://bugs.launchpad.net/bugs/274203 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 274203] Re: Joystick detected as mouse, crashes X
So, I've made some progress but I still can't play ANY games. Literally. NONE. I've edited my xorg.conf file to look like this (I've omitted things that don't pertain to the input devices): Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" 0 0 InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Configured Joystick" InputDevice "Configured Joystick 2" EndSection Section "ServerFlags" Option "AutoAddDevices""False" EndSection Section "InputDevice" Identifier "Configured Joystick" Driver "joystick" Option "Device""/dev/input/event5" Option "SendCoreEvents""False" EndSection Section "InputDevice" Identifier "Configured Joystick 2" Driver "joystick" Option "Device""/dev/input/event4" Option "SendCoreEvents""False" EndSection My problem was setting the correct Device for each joystick. Now, the joysticks (yes, I have 2, unplugging one doesn't fix the other) do not move, left click, or right click the cursor. jscalibrator reports all buttons working perfectly. But when I try to configure the buttons in various emulators and MAME, the buttons work but the directional pads do not do anything. I tried fooling around with the Option "MapAxis#" for each joystick and that did nothing at all. I even tried doing: Option "MapAxis1" "mode=none" Option "MapAxis2" "mode=none" Option "MapAxis3" "mode=none" Option "MapAxis4" "mode=none" Option "MapAxis5" "mode=none" Option "MapAxis6" "mode=none" thinking that all directional pads would be disabled. But they weren't. I changed the modes around too and nothing worked. I have two Logitech Cordless RumblePad 2 controllers. They are very similar to a PS2 controller. For those of you that have configured your joysticks through your xorg.conf file, do your directional pads work in games? Did you have to do anything else to get them working? I've been using joysticks in Ubuntu since Edgy and I've never had a problem with them. All I needed to do was to just plug them into a USB port. I'm seriously considering downgrading. -- Joystick detected as mouse, crashes X https://bugs.launchpad.net/bugs/274203 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 284951] Re: Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected.
Jeremy LaCroix and CyberConan (and everyone else who claims that that Albert Damer fix fixed their problems): How did you get your joystick from not controlling the cursor? I tried the .deb file that was attached and I compiled it myself. My joystick still moves the mouse cursor. Thanks for any help! -- Intrepid: Gamepad "Saitek P580" not working in games, buttons not detected. https://bugs.launchpad.net/bugs/284951 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 274203] Re: Joystick detected as mouse, crashes X
This is ridiculous. Why is this not marked Critical?! No games are playable without the joystick interrupting the game window! I tried fooling around with xorg.conf and if I don't have: Option "SendCoreEvents" "false" in: Section "InputDevice" Identifier "Configured Joystick" Driver "joystick" Option "Device" "/dev/input/event3" Option "SendCoreEvents" "false" EndSection the cursor moves all the way to the upper left part of the screen. I tried Albert Damen's fix and that didn't change anything. It's bad enough that Linux has a bad reputation with gaming but this bug makes Linux look even worse. Everything was working great in Hardy. This regression makes nothing playable on my end. I should have not upgraded. -- Joystick detected as mouse, crashes X https://bugs.launchpad.net/bugs/274203 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 283399] Re: [Intrepid] lshal output for different joystick, joypad and dance mat devices
** Attachment added: "Cordless RumblePad 2.lshal" http://launchpadlibrarian.net/19216941/Cordless%20RumblePad%202.lshal -- [Intrepid] lshal output for different joystick, joypad and dance mat devices https://bugs.launchpad.net/bugs/283399 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 283399] Re: [Intrepid] lshal output for different joystick, joypad and dance mat devices
** Attachment added: "Cordless RumblePad 2.lshal.diff" http://launchpadlibrarian.net/19216927/Cordless%20RumblePad%202.lshal.diff -- [Intrepid] lshal output for different joystick, joypad and dance mat devices https://bugs.launchpad.net/bugs/283399 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 159263] Re: Gnome-screensaver does not stay on
Yes that was it! The option was for "Unredirect Fullscreen Windows". It should be unchecked. Thanks! -- Gnome-screensaver does not stay on https://bugs.launchpad.net/bugs/159263 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 159263] Re: Gnome-screensaver does not stay on
I am having the same problem. I am using Ubuntu Hardy Heron with all packages updated. This problem started occurring about two to three weeks ago. I have not touched the settings in gnome-screensaver since Gutsy or maybe even Feisty. gnome-screensaver was working perfectly fine for awhile in Hardy. I think one of the updates ruined it. When I run gnome-screensaver --debug, I get this when the screensaver kicks in: [EMAIL PROTECTED]:~$ gnome-screensaver --debug [EMAIL PROTECTED]:~$ Xlib: extension "XFree86-Misc" missing on display ":1.0". Xlib: extension "XFree86-Misc" missing on display ":1.0". Xlib: extension "XFree86-Misc" missing on display ":1.0". The screen flashes black for less than a second and it goes to the previous view. When I run --no-daemon: [EMAIL PROTECTED]:~$ gnome-screensaver --no-daemon --debug [gs_debug_init] gs-debug.c:106 (00:47:38): Debugging enabled [main] gnome-screensaver.c:87 (00:47:38):initializing gnome-screensaver 2.22.2 [init_session_id] gs-listener-dbus.c:2051 (00:47:38):Got session-id: /org/freedesktop/ConsoleKit/Session1 [gs_fade_init] gs-fade.c:683 (00:47:38): Fade type: 0 [initialize_server_extensions] gs-watcher-x11.c:903 (00:47:38): Not using server's MIT-SCREEN-SAVER extension. [gs_watcher_set_active] gs-watcher-x11.c:731 (00:47:38): turning watcher: ON [_gs_watcher_set_active_internal] gs-watcher-x11.c:718 (00:47:38): Starting idle watcher [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (00:47:38): obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.46 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (00:47:38): obj_path=(null) interface=(null) method=(null) destination=:1.46 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (00:47:38): obj_path=(null) interface=(null) method=(null) destination=:1.46 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (00:47:38): obj_path=(null) interface=(null) method=(null) destination=:1.46 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (00:47:38): obj_path=(null) interface=(null) method=(null) destination=:1.46 [_gs_watcher_notice_window_created] gs-watcher-x11.c:568 (00:47:40): Window created: noticing activity on 0xC090F7 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1105 (00:48:08): Scheduling power notice in: 1 [power_timer] gs-watcher-x11.c:1080 (00:48:08): in power timer [power_timer] gs-watcher-x11.c:1098 (00:48:08): Setting power notice elapsed: 3 [watcher_power_notice_cb] gs-monitor.c:139 (00:48:08): Power notice signal detected: 1 [_gs_watcher_set_session_power_notice] gs-watcher-x11.c:478 (00:48:08): Changing power notice state: 1 [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [idle_timer] gs-watcher-x11.c:1115 (00:48:28): in idle timer [watcher_idle_notice_cb] gs-monitor.c:170 (00:48:28):Idle notice signal
[Bug 129867] Re: Incorrect rendering of account tabs under XGL and Compiz
that's interesting. if i turn off compiz (switch to metacity), i can not reproduce this bug. i'm also using gutsy (64 bit), gnucash from synaptic (2.2.1), compiz that i compiled myself (0.6.0), and nvidia drivers that were compiled from envy (i believe that is version 100.14.23). although synaptic shows that i have nvidia-glx-new 100.14.23 installed also. this is a good workaround for me until this gets fixed. any other info you need? -- Incorrect rendering of account tabs under XGL and Compiz https://bugs.launchpad.net/bugs/129867 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 129867] Re: Incorrect rendering of account tabs under XGL and Compiz
i'm also receiving this same bug using the newest nvidia drivers with a GeForce 7600 GS and xgl. really annoying. -- Incorrect rendering of account tabs under XGL and Compiz https://bugs.launchpad.net/bugs/129867 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 46575] Re: screen goes blank even though screensaver and power management are turned off
i was having this problem too. but xset s off didn't fix it for me. i had to put this in my xorg.conf file: Section "ServerFlags" Option "blank time" "0" Option "standby time" "0" Option "suspend time" "0" Option "off time" "0" Option "screen blank" "0" EndSection then i had to restart X. now, the screen never goes blank! gnome- screensaver kicks in! hope that helps! -- screen goes blank even though screensaver and power management are turned off https://bugs.launchpad.net/bugs/46575 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121433] Re: drum sound at start up only sometimes works
so, i updated to gutsy just recently and was having the same problem. i read a post on the forums about getting system sounds to work in ubuntu and the workaround was to install esound from synaptic. that worked great. so, that fixed the problem of no system sounds. but that still didn't fix the gdm drum roll sound not appearing. if i go to system -> administration -> login window and then to the accessibility tab, i can play the drum roll sound just fine. but it wasn't playing it at the gdm screen. then, i took a look at /etc/gdm/gdm.conf and noticed that the line SoundOnLogin was commented out. i uncommented it and restarted and it worked! so, why does gdmsetup have the checkbox for enabling the login screen ready sound checked when it is uncommented in gdm.conf? in terms of getting the other packages to play sounds, they all work now. i just have to choose the correct dsp. in my case, it will always be /dev/dsp3 please close this bug. i do not believe it is an issue anymore. i'm not sure if upgrading to gutsy fixed it or just changing the settings fixed the numerous sound issues i was having. thank you for your time. -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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 121433] Re: drum sound at start up only sometimes works
hello? anyone listening?! some more info: audacity was having the same exact problem. so, i fooled around with the settings. in Edit > Preferences > Audio I/O (Tab), for Playback it was set to "OSS: /dev/dsp". so, i noticed another option for "OSS: /dev/dsp3". the sound with that setting worked. what also worked was "ALSA: Audigy 2 ZS [SB0350]: ADC Capture/Standard PCM Playback (hw:3, 0)". so, now i left it at that option and it works. then, i tried mednafen again. here are the settings in mednafen.cfg pertaining to the sound: ;Select sound driver. sounddriver oss ;Select sound output device. sounddevice /dev/dsp that was the original settings, which didn't work. the mednafen team also says to try default for sounddevice, which didn't work either. then i tried /dev/dsp3 which worked! i thought i finally fixed the problem. but /dev/dsp3 doesn't seem to be consistent. sometimes i have to set it to /dev/dsp1. i don't know why. i don't understand what this means. for amarok, if i select the oss sound engine i cannot choose /dev/dsp3, only /dev/dsp. i have no idea how to change mplayer32 settings. but if i did, i would imagine it would be the same. so, my question is now... what the hell is wrong with /dev/dsp? (whatever it is) -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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 121433] Re: drum sound at start up only sometimes works
can i get some help on this? it's still affecting me. i noticed that this bug is not assigned to anyone. should it be? -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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 121433] Re: drum sound at start up only sometimes works
Thanks for your help. I attached the logfiles in an archive. The name and make of my sound card is listed above. ** Attachment added: "debugging.tar.bz2" http://launchpadlibrarian.net/8165206/debugging.tar.bz2 -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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 121433] Re: drum sound at start up only sometimes works
here is the dmesg output. thanks! ** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/8158481/dmesg.txt -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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 121433] Re: drum sound at start up only sometimes works
also, the oss driver works with amarok when i hear that drum sound. -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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 121433] Re: drum sound at start up only sometimes works
so, how do i use the alsa driver instead? i know that with mednafen, alsa and oss don't work. i don't get any sound using the alsa driver. i have a feeling it might be more than just changing the drivers. anything i could try? -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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 121433] drum sound at start up only sometimes works
Public bug reported: at the gdm screen, or when the gdm screen starts, there is a quick half a second drum sound that only SOMETIMES works. this might not seem like a big deal but it's actually a much bigger problem. whatever sound application that sound clip is relying on is apparently not working because the sound for other applications are not working as well. so... when i hear the drum sound, everything works perfectly fine. when i don't hear the drum sound: 1. amarok doesn't play any sound using the oss sound engine. however, it works with alsa and esd. 2. mplayer32 doesn't play any sound at all. 2. most importantly, mednafen does not have any sound. i posted in the forum there as well, http://forum.fobby.net/index.php?t=msg&th=296&start=0, which is where i found out about this problem. i tried following these directions, http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_configure_sound_to_work_properly_in_GNOME, and that did not help. this problem started when i first switch to linux a couple months ago with edgy eft. and it still pursues with feisty fawn. i used the 64 bit version of both OS's. my sound card is "Creative Sound Blaster Audigy2 ZS Platinum 7.1 Channels PCI Interface Sound Card" and it works great otherwise! ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- drum sound at start up only sometimes works https://bugs.launchpad.net/bugs/121433 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
