I too felt a regression today after installing xfce 4.12 from the PPA
over xubuntu 14.04, on a macbook pro 8.2.
Everything was working fine before the installation, including suspend by
closing the lid.
Now, suspend and wakeup by menu work, but closing the lid the screen is black
after wakeup.
Did you also CONFIG_ASUS_WMI?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788366
Title:
Asus laptop hotkeys not recognized
To manage notifications about this bug go to:
because the Debian wheezy kernel 2.6.39-2-686 is
compiled with CONFIG_ASUS_WMI=m and CONFIG_ASUS_NB_WMI=m, which Ubuntu
natty hasn't, but I think oneiric has. That's why I was asking for the
backporting.
rgds,
jss
--
You received this bug notification because you are a member of Ubuntu
Bugs
On 16/06/11 19:55, Ricardo Sansores Aguilar wrote:
@jss
How can I use those backports?
Hi Ricardo,
You have to enable natty-backports either on
System/Administration/Update Manager/Settings or by editing
/etc/apt/sources.list and including:
deb http://pt.archive.ubuntu.com/ubuntu/ natty
Similar here with Asus N53SN, natty with kernel 2.6.38-2
Affected keys are fn+ F5, F6, F7, F8, F9, F10, F11, F12
fn+F5, F6, F7 control backlight and work, although no keypress is
detected and no OSD feedback.
I have a parallel debian install, sid / weezy, and these keys are
working there. For
On the Lucid box that is working with XDMCP, I just confirm that port
177 is only opened for IPV6:
$ sudo netstat -atnup | grep 177
udp6 0 0 :::177 :::* 754/gdm-binary
$
--
No option to log in remotely via XDMCP
https://bugs.launchpad.net/bugs/408417
You received this bug notification
I can confirm that XDMCP is working on debian squeeze.
Stranger than that is a box I have running Lucid, which does work with XDMCP
although this is declared broken for Lucid.
On another box that I upgraded from Lucid to Maverick, XDMCP was working before
and stopped after the upgrade.
This
Same here with 10.04 release candidate fully updated.
Furthermore, piklab-prog works correctly on the console with ICD2
programmer.
--
Crash with program command
https://bugs.launchpad.net/bugs/555319
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Everything OK now, thank you.
~$ sudo fuser -v /dev/dsp* /dev/snd/* /dev/seq*
USER PID ACCESS COMMAND
/dev/snd/controlC0: Slmodemd 1220 F slmodemd
jss 2112 F pulseaudio
/dev/snd/pcmC0D6c: Slmodemd 1220 F...m slmodemd
/dev/snd/pcmC0D6p
force-reload
~$ sudo fuser -v /dev/dsp* /dev/snd/* /dev/seq*
~$ killall pulseaudio
pulseaudio: no process found
~$ pulseaudio -D
~$ sudo fuser -v /dev/dsp* /dev/snd/* /dev/seq*
USER PID ACCESS COMMAND
/dev/snd/controlC0: jss 3887 F pulseaudio
If I stop slmodemd from
:
- On every boot, sound is always muted on the output device, set to default
- Volume is at 3%
So, being a newbie to Linux, long time experienced with MS, I ask:
Does this belong here, is this another bug or is any config I should change?
Thanks,
jss
--
[Karmic] softmodem-opened /dev/snd/pcm
11 matches
Mail list logo
