@DavidH: I reinstalled alsa-intel-hda-optiplex-dkms, rebooted, and now
the modinfo command shows correctly:
$ modinfo snd-hda-codec-realtek
filename:
/lib/modules/2.6.32-24-generic/updates/dkms/snd-hda-codec-realtek.ko
description:Realtek HD-audio codec
license:GPL
alias:
@DavidH: Ahhh. I was not aware of your upstream thread. I read it and
the first couple replies to it. Now that I'm aware of that thread, I
have to say that I agree with the approach that does NOT disable any
outputs when headphones are plugged in. That's too much automation, in
my opinion. But
@DavidH: I installed alsa-intel-hda-optiplex-dkms as you asked, but it
does not work for my Optiplex 980. The front panel headphone jack has
sound, but the external speaker jack is not muted when headphones are
plugged into the front panel headphone jack.
If it's any help: The ONLY thing that
$ sudo modinfo snd-hda-codec-realtek
filename:
/lib/modules/2.6.32-24-generic/kernel/sound/pci/hda/snd-hda-codec-realtek.ko
description:Realtek HD-audio codec
license:GPL
alias: snd-hda-codec-id:10ec*
srcversion: 187F2297A453A3E76D453EB
depends:
I stated some things incorrectly, above. Here are the corrected
statements of symptoms, for my Optiplex 980:
When I run hda-verb /dev/snd/hwC0D0 0x21 0x701 0, front headphone jack
works but external speakers emit no sound even if headphones are NOT
plugged in. This is actually acceptable in my
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
List of
apport information
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52698181/AlsaDevices.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52698183/BootDmesg.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/52698184/Card0.Amixer.values.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/52698185/Card0.Codecs.codec.0.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52698186/CurrentDmesg.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/52698187/PciMultimedia.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/52698189/ProcCpuinfo.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a member of Ubuntu
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
List of
apport information
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52698110/AlsaDevices.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52698111/BootDmesg.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/52698117/Card0.Amixer.values.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification because you are a member of
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/52698119/Card0.Codecs.codec.0.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification because you are a member of
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52698120/CurrentDmesg.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/52698121/PciMultimedia.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/52698122/ProcCpuinfo.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification because you are a member of Ubuntu
Bugs,
Seems to work for my Dell Optiplex 980. dmesg output is attached.
** Attachment added: alsa-dmesg.txt
http://launchpadlibrarian.net/52216935/alsa-dmesg.txt
--
No sound on Dell Optiplex 380 (ALC269Q, probably new chip)
https://bugs.launchpad.net/bugs/582199
You received this bug notification
Seems to work for my Dell Optiplex 980. Output from dmesg | grep -e hda
-e ALSA -e HDA is attached
** Attachment added: alsa-dmesg.txt
http://launchpadlibrarian.net/52217711/alsa-dmesg.txt
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
@DavidH: Jack-sensing works (speaker mutes when headphones are plugged
in) and recording works for both line-in and microphone.
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You received this bug notification because you are a member
@DavidH: Forgot to say, my testing was with 64-bit kernel
2.6.32-23-generic, and package linux-alsa-driver-
modules-2.6.32-23-generic, version 2.6.32-23.201007110500+optiplex3
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
You
@DavidH: Regarding this Bug 588031: How do your fixed packages linux-
alsa-driver-modules relate to the official linux-backports-modules-alsa-
generic packages? Do the official ones have the fixes? Or will your
fixes eventually be merged into those, or some other, official packages?
Eventually of
I'm having the same problem. Expo key is default Supere and it causes
compiz.real to segfault.
Running Karmic 9.10, but video card is ATI. Details below.
lspci yields:
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility U1
After segfault, dmesg yields:
[ 96.640662]
Toby Gray : Regarding your The one I built for Jaunty (amd64, not i386)
is at http://www.yargybot.com/libvnc.so: I need one for 32-bit Karmic,
not 64-bit. Can you build one, or do you know anyone who has and where
it (32-bit libvnc.so for Karmic) can be fetched?
--
libvnc.so Xorg module failes
Adam Tkac of Red Hat, Inc. writes: I think binary packages for
[TigerVNC for] Ubuntu will be available when 1.0.0 will be released.
Unfortunately I can't guarantee that libvnc.so will be available as
well. Situation around libvnc.so is very difficult because it depends on
distribution Xorg so the
Adam Tkac of Red Hat, Inc. writes: I think binary packages for
[TigerVNC for] Ubuntu will be available when 1.0.0 will be released.
Unfortunately I can't guarantee that libvnc.so will be available as
well. Situation around libvnc.so is very difficult because it depends on
distribution Xorg so the
** Changed in: vnc4 (Ubuntu)
Status: Invalid = Confirmed
--
vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
TigerVNC ( http://www.tigervnc.com/ ) appears to be doing exactly what
we need: providing a libvnc.so which works with the newer modular Xorg
versions (1.4 and higher). TigerVNC is planned for release with Fedora
Core 11. Let's just hope we can interest some Ubuntu developers in
building it
TigerVNC ( http://www.tigervnc.com/ ) appears to be doing exactly what
we need: providing a libvnc.so which works with the newer modular Xorg
versions (1.4 and higher). TigerVNC is planned for release with Fedora
Core 11. Let's just hope we can interest some Ubuntu developers in
building it
Regarding the status change to Fix Released in vnc4 (Fedora): As an
Ubuntu 8.04 Hardy user, I'd like to know when the Fedora fix will be put
into Ubuntu 8.04 (Hardy) and Ubuntu 8.10 (Intrepid).
--
vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick
The duplicate of this bug, Ubuntu Bug 247669, had its status changed on
Jan 20, 2009 to Fix Released in vnc4 (Fedora): As an Ubuntu 8.04 Hardy
user, I'd like to know when the Fedora fix will be put into Ubuntu 8.04
(Hardy) and Ubuntu 8.10 (Intrepid).
--
vnc4: vnc4server: libvnc.so crashes Xorg
On September 30, 2008, Mike Milligan wrote to me saying, Neither one of
those patches [in Red Hat Bug 282661] appear to address the INPUT module
ABI change that is the problem in Ubuntu/Debian. With Hope in my back
pocket, I did pull the RealVNC 4.1.2 source and tried to build it on
Intrepid, but
On September 30, 2008, Mike Milligan wrote to me saying, Neither one of
those patches [in Red Hat Bug 282661] appear to address the INPUT module
ABI change that is the problem in Ubuntu/Debian. With Hope in my back
pocket, I did pull the RealVNC 4.1.2 source and tried to build it on
Intrepid, but
@jasonwc:
wajig worked. The held state is honoured by both update-manager and synaptic,
which was exactly what I was looking for. And wajig is a very cool utility;
I'll be installing it on ALL of my machines, whether I need to hold packages at
specific versions or not.
I've updated my pptp
@ Dmik: Simple is a relative word, but here goes: The first workaround I
did to restore 0.6 behavior was to add Hardy's repositories back into
software sources, then use aptitude to downgrade all five related
packages to 0.6.x and mark them Held at the older version. That worked
fine, but it was
** Changed in: network-manager-pptp (Ubuntu)
Status: Incomplete = Confirmed
--
intrepid network-manager-pptp does not have essential options
https://bugs.launchpad.net/bugs/278309
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Billy Macdonald: You wrote, Where is the bug tracker/discussion for
upstream of network manager pptp?. I think it is in NetworkManager-
[EMAIL PROTECTED] . You can subscribe to the list if you want.
--
network-manager-pptp lacks refuse-eap option in advanced ... dialog
@ Billy Macdonald: I Forgot to say, you can subscribe and/or view
archives of NetworkManager-list at
http://mail.gnome.org/mailman/listinfo/networkmanager-list
--
network-manager-pptp lacks refuse-eap option in advanced ... dialog
https://bugs.launchpad.net/bugs/301593
You received this bug
I'm not very familiar with the nomination process, but I think we may
need a few thousand more nominations of this bug for Ubuntu
distributions (notice, above, I've nominated this bug for Intrepid and
Jaunty). Would any of the other subscribers to this bug be willing to
add your nomination(s)? We
Due to this and many other bugs in NM 0.7, it seems that we have Regression
Potential here, but that would be a problem for those who require 0.7 because
they require some of the new features such as Wireless Broadband and DSL. I'm
stumped, because it just seems that we've moved ahead to 0.7
@Mr. Sack: the updated document is here:
http://www2.nau.edu/wal2/NetworkManager/Readme.html and please note, you
CAN go back to 0.7; just follow the instructions in the aforementioned
document.
My sincere apologies for any trouble this may have caused.
--
Network Manager unable to connect to
@Mr. Sack: You wrote i am still missing an explicit list of options
that are missing here. That list can be created by comparing 0.6.5 to
0.7 and enumerating all options which appear in 0.6.5 but do not appear
in 0.7. Below is a list of all of the options in 0.6.5's Dialog window
labeled Edit VPN
Bug 278309 is, so far, the most inclusive of all the various bugs I've
found yet for network-manager-pptp version 0.7. Its title or description
is intrepid network-manager-pptp does not have essential options
--
Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping)
If anyone is still using Intrepid, does not use nor require the new
features of NetworkManager 0.7 such as Mobile Broadband and DSL, and
wants to revert to network-manager-pptp as it was in Hardy, I've created
new versions of the five related packages with version numbers such
that they are newer
For those of you who can answer yes to all five of the following
questions:
* Are you still using Intrepid?
* Do you neither use nor require the new features of NetworkManager 0.7 such as
Mobile Broadband and DSL?
* Do you want to stay with Intrepid?
* Do you want to revert Intrepid's
@Billy Macdonald: Your question has hit the nail on the head, and I
anxiously await the answer from anyone who can give that answer. I am
grateful for what you, Alex, and others are doing, but I think these
efforts are nibbling at the edges of a larger problem. That problem is
stated well in your
According to my understanding (and someone please correct me if I'm
wrong), each new release of Ubuntu starts with the latest Debian
unstable.
When I search within Unstable at debian.org (
http://packages.debian.org/search?keywords=network-
managersearchon=namessuite=unstablesection=all ) I get
Regarding refuse-eap: As I stated 2008-11-04 , the manual workaround of
using your favorite text editor to add refuse-eap to the file
~/.gconf/system/networking/connections/n/vpn/%gconf.xml works for me
(makes me able to establish the vpn). (As an aside, gconf-editor can be
used, instead of a
I'm so desperate, that I just installed Jaunty Alpha 1 to see if there's
any improvement in network-manager-pptp; Jaunty has the same piece of
feces network-manager-pptp 0.7~~svn20081015t024626-0ubuntu3 . Please
pardon my colorful language, but this is unacceptable. I did some poking
around on
Mr. Sack,
You wrote, Longtime, your issue is most likely bug 268667. I mean no
disrespect, but when I point my browser at
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/268667
and search within the page for the 3-character string, eap, THE SEARCH
FAILS. So I ask: How can you
We have been asked that if we are having troubles other than Bad NT-
Domain escaping, to create another bug. I am fully willing to do that,
because I do indeed have other problems, but I see there are 4
duplicates of THIS bug, plus at least half a dozen other bugs for
network-manager-pptp in
This affects me seriously. The workaround of manually adding refuse-
eap to the file ~/.gconf/system/networking/connections/n/vpn/%gconf.xml
(or alternatively using gconf-editor and adding refuse-eap=yes) allows
me to establish the vpn, BUT MANY CONFIG SETTINGS AVAILABLE IN Version
0.6.5 ARE
This affects me seriously. The workaround of manually adding refuse-
eap to the file ~/.gconf/system/networking/connections/n/vpn/%gconf.xml
makes me able to establish the vpn, BUT I still cannot modify routes so
that only SOME traffic goes through the vpn while all other traffic goes
through my
Indeed it is extremely important to specify WHICH Eee PC model you have;
apparently there are huge differences in hardware across the many Eee
models.
I'm running Ubuntu 8.04 on an Eee PC 1000H, and I've fixed the
nonfunctioning Atheros Attansic wired ethernet controller by following
the
New bug created to replace this one: 247669
** Changed in: vnc4 (Ubuntu)
Status: Confirmed = Invalid
--
vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: vnc4server
Using the libvnc.so module in Xorg 1.4.
On first keypress or mouseclick by vnc client, Xorg log on vnc server
side shows:
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x483d5a]
1: /lib/libc.so.6 [0x2aeb4a768100]
2:
** Tags added: libvnc.so vnc.so vnc4 vnc4server
** Tags added: xorg
--
vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick
https://bugs.launchpad.net/bugs/247669
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Using Steinar's libvnc.so, occasionally when Firefox attempts to display
some types of content, Xorg will die (but gdmgreeter successfully
restarts).
The Xorg log shows:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7ee4420]
Fatal server error:
Caught signal 11. Server
More information on the second machine on which I tried Steinar's
vnc.so: that machine has an Nvidia graphics card and was using the open-
source free Nvidia driver. I changed it to use the proprietary Nvidia
driver, and thereafter, it also works fine with Steinar's vnc.so (no
striated-looking
I spoke too soon. Steinar's vnc.so worked fine on the first Hardy
machine I tested. However, on a second machine (running Hardy just like
the first), it did not crash Xorg, BUT the vncviewer screen looked like
my attachment here (see attachment).
** Attachment added: Screenshot_VNC_x11.png
Not yet fixed in Debian. libvnc.so has disappeared from the -22 version
of the Debian package.
--
Xorg module VNC cores on keyboard input
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- Xorg module VNC cores on keyboard input
+ Xorg module libvnc.so cores on keyboard or mouse input
--
Xorg module libvnc.so cores on keyboard or mouse input
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: libvnc.so vnc.so
--
Xorg module libvnc.so cores on keyboard or mouse input
https://bugs.launchpad.net/bugs/180619
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
** Summary changed:
- Xorg module libvnc.so cores on keyboard or mouse input
+ vnc4server: segfaults on key press with newer X.org
--
vnc4server: segfaults on key press with newer X.org
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- vnc4server: segfaults on key press with newer X.org
+ vnc4server: libvnc.so crashes Xorg 1.4 on keypress or mouseclick
** Summary changed:
- vnc4server: libvnc.so crashes Xorg 1.4 on keypress or mouseclick
+ vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or
Please see below for a vnc.so from Steinar H. Gunderson which works (for me)
with Xorg 1.4.
I'd like to invite all of you to try it too.
Eventually, someone who has the necessary Debian binary packaging skills can
hopefully volunteer to package this.
Original Message
Subject:
I nominated this bug for Hardy and Intrepid. This is the first time I
have nominated anything. I have no idea what nominating means will
happen next; anyone who does, please let me know. Can someone explain
what happens when we have a scenario like we have here, where the Ubuntu
bug 180619 is the
I am in contact with a developer who might (no promises) be willing to
adopt the Debian bug (or I guess it would be a new bug since the Debian
bug was fixed by removing libvnc.so from the package).
--
Xorg module VNC cores on keyboard input
https://bugs.launchpad.net/bugs/180619
You received
What is the status of Debian Bug 444697? Is it opened or closed or
something else? I've read its thread (not well enough, I guess) at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444697 , and I sent an
e-mail to [EMAIL PROTECTED] but the e-mail bounced back (SMTP; 550
unknown user).
I have an
Michael Milligan, would you be willing to post here how to downgrade
Xorg in Hardy (and hold at downgraded) if one wishes to do that as a
workaround? (Also how to unhold after the bug is fixed, if ever.)
--
Xorg module VNC cores on keyboard input
https://bugs.launchpad.net/bugs/180619
You
Just like others have posted here, my libvnc.so worked fine with xorg in
Gutsy but is broken in Hardy. I am having the same problem and getting
precisely the same backtrace in Xorg.0.log. PLEASE PLEASE if this bug is
not open, then reopen it.
--
Xorg module VNC cores on keyboard input
75 matches
Mail list logo
