[Bug 1174903] Re: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
This issue persists. ** Changed in: openswan (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174903] Re: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
Though its likely upstream's problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174903] Re: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
The bug persists with Trusty using openswan 1:2.6.41-0xelerance1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174903] Re: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
I'm by no means an expert with l2tp/pptp configuration. I'd love to hear that I have a simple config error. Attached is my xl2pd.conf that exhibits the mentioned bug. ** Attachment added: xl2pd.conf https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+attachment/4092990/+files/xl2tpd.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1174903] Re: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
I'm currently using Trusty and have tested the issue on Precise Saucy in the past. On Tue, Apr 22, 2014 at 12:09 PM, Simon Déziel 1174...@bugs.launchpad.netwrote: Can you try to reproduce the issue on a supported Ubuntu version (Precise, Saucy or Trusty)? Raring is out of support and misses a fix for xl2tpd which *could* be what you are hitting. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174903] Re: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
I'm currently using Trusty and have replicated the bug on Saucy in the past. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174903] Re: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
FYI it looks like this bug persists in openswan-2.6.41 in the openswan testing ppa at https://launchpad.net/~openswan/+archive/openswan-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174903 Title: openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174903] [NEW] openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
Public bug reported:
Upgrading to ubuntu 13.04 broke the l2tp VPN hosted on my Ubuntu server.
Downgrading from openswan 2.6.38 to 2.6.37 fixes it.
connecting to the l2tp VPN from an OSX or iOS client in 2.6.38 yeilds
the following pluto log:
00]
packet from 67.188.104.170:500: received Vendor ID payload [Dead Peer Detection]
L2TP-PSK-NAT[1] 67.188.104.170 #1: responding to Main Mode from unknown peer
67.188.104.170
L2TP-PSK-NAT[1] 67.188.104.170 #1: transition from state STATE_MAIN_R0 to
state STATE_MAIN_R1
L2TP-PSK-NAT[1] 67.188.104.170 #1: STATE_MAIN_R1: sent MR1, expecting MI2
L2TP-PSK-NAT[1] 67.188.104.170 #1: NAT-Traversal: Result using
draft-ietf-ipsec-nat-t-ike (MacOS X): peer is NATed
L2TP-PSK-NAT[1] 67.188.104.170 #1: transition from state STATE_MAIN_R1 to
state STATE_MAIN_R2
L2TP-PSK-NAT[1] 67.188.104.170 #1: STATE_MAIN_R2: sent MR2, expecting MI3
L2TP-PSK-NAT[1] 67.188.104.170 #1: ignoring informational payload, type
IPSEC_INITIAL_CONTACT msgid=
L2TP-PSK-NAT[1] 67.188.104.170 #1: Main mode peer ID is ID_IPV4_ADDR:
'10.0.1.5'
L2TP-PSK-NAT[1] 67.188.104.170 #1: switched from L2TP-PSK-NAT to
L2TP-PSK-NAT
L2TP-PSK-NAT[2] 67.188.104.170 #1: deleting connection L2TP-PSK-NAT
instance with peer 67.188.104.170 {isakmp=#0/ipsec=#0}
L2TP-PSK-NAT[2] 67.188.104.170 #1: transition from state STATE_MAIN_R2 to
state STATE_MAIN_R3
L2TP-PSK-NAT[2] 67.188.104.170 #1: new NAT mapping for #1, was
67.188.104.170:500, now 67.188.104.170:32769
L2TP-PSK-NAT[2] 67.188.104.170 #1: STATE_MAIN_R3: sent MR3, ISAKMP SA
established {auth=OAKLEY_PRESHARED_KEY cipher=aes_256 prf=oakley_sha
group=modp1024}
L2TP-PSK-NAT[2] 67.188.104.170 #1: Dead Peer Detection (RFC 3706): enabled
L2TP-PSK-NAT[2] 67.188.104.170 #1: Applying workaround for Mac OS X NAT-OA
bug, ignoring proposed subnet
L2TP-PSK-NAT[2] 67.188.104.170 #1: the peer proposed:
173.230.145.84/32:17/1701 - 67.188.104.170/32:17/0
L2TP-PSK-NAT[2] 67.188.104.170 #1: peer proposal was reject in a virtual
connection policy because:
L2TP-PSK-NAT[2] 67.188.104.170 #1: a private network virtual IP was
required, but the proposed IP did not match our list (virtual_private=)
L2TP-PSK-noNAT[1] 67.188.104.170 #2: responding to Quick Mode proposal
{msgid:ca8077f1}
L2TP-PSK-noNAT[1] 67.188.104.170 #2: us:
173.230.145.84173.230.145.84[+S=C]:17/1701
L2TP-PSK-noNAT[1] 67.188.104.170 #2: them:
67.188.104.170[10.0.1.5,+S=C]:17/61510
L2TP-PSK-noNAT[1] 67.188.104.170 #2: transition from state STATE_QUICK_R0 to
state STATE_QUICK_R1
L2TP-PSK-noNAT[1] 67.188.104.170 #2: STATE_QUICK_R1: sent QR1, inbound IPsec
SA installed, expecting QI2
L2TP-PSK-noNAT[1] 67.188.104.170 #2: Dead Peer Detection (RFC 3706): enabled
L2TP-PSK-noNAT[1] 67.188.104.170 #2: transition from state STATE_QUICK_R1 to
state STATE_QUICK_R2
L2TP-PSK-noNAT[1] 67.188.104.170 #2: STATE_QUICK_R2: IPsec SA established
transport mode {ESP=0x017b6567 0x338f5415 xfrm=AES_256-HMAC_SHA1 NATOA=none
NATD=67.188.104.170:32769 DPD=enabled}
YAY! CONNECTED HOORAY! But then after a quick 5-10 sec timeout it
just dies. It never talks to xl2tp. xl2tp logs show nothing. The very
next thing that happens is:
L2TP-PSK-NAT[2] 67.188.104.170 #1: received Delete SA(0x017b6567) payload:
deleting IPSEC State #2
2TP-PSK-NAT[2] 67.188.104.170 #1: received Delete SA payload: deleting ISAKMP
State #1
L2TP-PSK-NAT[2] 67.188.104.170: deleting connection L2TP-PSK-NAT instance
with peer 67.188.104.170 {isakmp=#0/ipsec=#0}
it shuts down the connection. boo. yuck. Downgrading to 2.6.37 lets it talk to
xl2tp. Why? I don't know.
** Affects: openswan (Ubuntu)
Importance: Undecided
Status: New
** Tags: ipsec l2tp vpn xl2tp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174903
Title:
openswan 2.6.38 in raring is broken for l2tp. 2.6.37 works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openswan/+bug/1174903/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 471504] [NEW] BASH_ALIASES=foo segfaults bash
Public bug reported: Binary package hint: bash Ubunutu 9.10 Bash Version: 4.0-5ubuntu2 $ BASH_ALIASES=foo causes a segmentation fault. Nasty, as I had something like that in my .bashrc. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- BASH_ALIASES=foo segfaults bash https://bugs.launchpad.net/bugs/471504 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 215496] Re: When setting mousekeys, xkbset reports XKB not supported
While xkbset still reports 'not supported for display', from a practical perspective: Ctrl-Alt-Shift-Numlock does toggle on and off my mouse keys, so I'm rollin' with context menus on my MBP again. -- When setting mousekeys, xkbset reports XKB not supported https://bugs.launchpad.net/bugs/215496 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 215496] Re: When setting mousekeys, xkbset reports XKB not supported
I run this in my (gnome) session startup: xmodmap /home/aj/.xmodmap [EMAIL PROTECTED] % cat .xmodmap keycode 116 = Pointer_Button2 keycode 108 = Pointer_Button3 That's 116 is Right-Fan and 108 is Enter on MBP. I don't seem to have mouseemu installed. And again, Ctrl-Alt-Shift-Numlock turns those buttons as acting as mousekeys on and off. -- When setting mousekeys, xkbset reports XKB not supported https://bugs.launchpad.net/bugs/215496 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 215496] Re: When setting mousekeys, xkbset reports XKB not supported
Same here. Macbook Pro. 'xkbset m' strace attached. ** Attachment added: xkbset.strace http://launchpadlibrarian.net/14633571/xkbset.strace -- When setting mousekeys, xkbset reports XKB not supported https://bugs.launchpad.net/bugs/215496 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 119266] Re: Intel HDA Sound device doesn't work in gutsy
snd-hda-intel works on my macbook pro ( ich7 ). however, if i install linux-backports-modules it borks rather badly on module load. Actually, snd-hda-intel loads, but complains about not being able to detect the pci device. backports needs fixin'. -- Intel HDA Sound device doesn't work in gutsy https://bugs.launchpad.net/bugs/119266 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 135833] Re: [patch] snd-hda-intel not working with alsa 1.0.14
Figured this one out. The bad sound driver was coming from linux- backports-modules. -- [patch] snd-hda-intel not working with alsa 1.0.14 https://bugs.launchpad.net/bugs/135833 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 135833] Re: [patch] snd-hda-intel not working with alsa 1.0.14
Sound on my Macbook Pro seemed to be working immediately after I upgraded to gutsy as of RC1. With yesterdays kernel update sound has ceased to work: % lspci 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) # modprobe -v snd_hda_intel insmod /lib/modules/2.6.22-14-generic/updates/sound/pci/hda/snd-hda-intel.ko % dmesg | tail [28561.04] ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 21 [28561.04] PCI: Setting latency timer of device :00:1b.0 to 64 [28561.208000] hda_codec: STAC922x, Apple subsys_id=106b0200 [28562.24] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f1c00 [28562.488000] ACPI: PCI interrupt for device :00:1b.0 disabled [28562.488000] HDA Intel: probe of :00:1b.0 failed with error -16 -- [patch] snd-hda-intel not working with alsa 1.0.14 https://bugs.launchpad.net/bugs/135833 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 66652] Re: artifacts near the end of usplash boot
This does not happen anymore, at least with feisty. Close me. -- artifacts near the end of usplash boot https://bugs.launchpad.net/bugs/66652 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 106122] new linux image freezes on ata_piix on boot does not recognize hdd
Public bug reported: Binary package hint: linux-image-generic linux image 14.23 in feisty does not boot on macbook pro. freezes at hdd detection i think. while loading ata_piix drivers (is it even supposed to load that on a macbook pro?) right after usb device initialization. 14.22 worked fine. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: Unconfirmed -- new linux image freezes on ata_piix on boot does not recognize hdd https://bugs.launchpad.net/bugs/106122 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47768] Re: Mount Root Files System Failed
I have a similar problem on edgy. initramfs stops and produces a prompt on boot because it can't find the root filesystem (root=/dev/md1) typing 'mdadm -As' from initramfs gives errors as the /etc/mdadm.conf file built into initramfs contains only the UUID numbers of my RAID sets. No keywords or anything else like the proper /etc/mdadm.conf on my real root filesystem. If I assemble the md devices manually in initramfs and then mount the one that contains my root filesystem (-o ro) to /root i can exit initramfs and it will boot my RAIDed machine correctly. I've reinstalled my kernel (2.6.17-50-generic and 2.6.17-11-generic and 2.6.17-10-generic), and it rebuilds the initramfs with the useless mdadm.conf I mentioned above. This is with initramfs-tools version 0.69ubuntu20 So i have to manually boot every single time now. Bleah. This worked fine until very recently (a month? two? I have highish uptimes). I suspect the most recent initramfs-tools update has a bug. -- Mount Root Files System Failed https://launchpad.net/bugs/47768 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87253] Re: internal speakers do not work on MacBook Pro
Volume Applet-Open Volume Control-Switches: Line in as Output = checked. Works with Edgy and hda_intel Alsa Drivers 1.0.13 and above on MacBook Pro 15 -- internal speakers do not work on MacBook Pro https://launchpad.net/bugs/87253 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32415] Re: Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
I disagree, the problem is not only on Apples! I concur. I can reproduce the problem on x86 and x86_64. AJ -- Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty https://launchpad.net/bugs/32415 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75788] linux-source-2.6.17-10.34 snd_hda_intel broken
Public bug reported: Binary package hint: linux-source-2.6.17 linux-image-2.6.17 upgraded from 10.33 to 10.34 (edgy-security) and module snd_hda_intel no longer loads on my MacBook Pro. dmesg has lots of symbol mismatch fun: [17181190.512000] snd_timer: disagrees about version of symbol snd_info_register [17181190.512000] snd_timer: Unknown symbol snd_info_register The word is that compiling the latest ALSA by hand cures these woes. See 2.6.17 murdered my sound on forums: http://www.ubuntuforums.org/showthread.php?p=1884257highlight=snd_hda_intel#post1884257 ** Affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- linux-source-2.6.17-10.34 snd_hda_intel broken https://launchpad.net/bugs/75788 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70958] missing /usr/share/gnome/help/libs/generic.ent
Public bug reported: Binary package hint: ubuntu-docs scrollkeeper just ran its monthly cron job and spit out a long list of /etc/cron.monthly/scrollkeeper: ///usr/share/gnome/help/serverguide/be/serverguide.xml:7: I/O warning : failed +to load external entity /usr/share/gnome/help/libs/generic.ent %genericent; ^ %genericent; ^ ///usr/share/gnome/help/serverguide/be/serverguide.xml:18: parser error : Entity +'sg-title' not defined titleubuntu; sg-title;/title ^ /usr/share/gnome/help/serverguide/be/bookinfo.xml:7: I/O warning : failed to +load external entity /usr/share/gnome/help/libs/generic.ent %genericent; ^ %genericent; ^ /usr/share/gnome/help/serverguide/be/bookinfo.xml:18: parser error : Entity +'sg-title' not defined titleubuntu; sg-title;/title ^ /usr/share/gnome/help/serverguide/be/bookinfo.xml:28: parser error : Entity +'sg-title' not defined paraThe ubuntu; sg-title; is also based on the contributions +of:/para continues for nearly everything i'm guessing that sg-title is defined in the missing /usr/share/gnome/help/libs/generic.ent or that %genericent is missing a delimiter. ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: Unconfirmed -- missing /usr/share/gnome/help/libs/generic.ent https://launchpad.net/bugs/70958 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42974] Re: No video on VTs
I get this on the ATI on my MacBookPro 15 as well. It may have something to do with usplash: a href=https://launchpad.net/ bug/63558Bug 63358/a - usplash corrupts VTs -- No video on VTs https://launchpad.net/bugs/42974 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63558] Re: Latest usplash leaves my consoles corrupted
Bug 42974 lists the problem for multiple video cards. Bug 66652 describes a screen corruption near the end of the usplash progress (no idea if its related, but some console reset script might bork everything near the end of boot) -- Latest usplash leaves my consoles corrupted https://launchpad.net/bugs/63558 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63558] Re: Latest usplash leaves my consoles corrupted
This VT corruption can be eliminated on my MacBook Pro 15 if 'splash' is removed from the kernel options. No usplash, no corruption. VT's all work fine. As kko points out, this is likely unrelated to the FB bugs in 42974. +1 on raising the priority of this one. No VTs make it pretty hard to fix a borked box. -- Latest usplash leaves my consoles corrupted https://launchpad.net/bugs/63558 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66649] MacBookPro 15 sound unsupported (hda-intel)
Public bug reported: Binary package hint: linux-source-2.6.17 This seems to be partially supported in alsa-driver-1.0.13, which is not included in the 2.6.17 kernel. I have to compile my own alsa at the moment. ** Affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- MacBookPro 15 sound unsupported (hda-intel) https://launchpad.net/bugs/66649 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66648] kernel fails to REboot on apic error
Public bug reported: Binary package hint: linux-source-2.6.17 Hardware: MacBookPro 15 Kernel: linux-image-2.6.17-10-generic_2.6.17-10.33 Bootloader: grub kernel boots fine if the machine is off. If I try to reboot, the kernel fails instantly on an apic error. I suppose I could ad noapic to the kernel args, but powering off and on also solves the problem. ** Affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- kernel fails to REboot on apic error https://launchpad.net/bugs/66648 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66652] artifacts near the end of usplash boot
Public bug reported: On my MacBookPro 15 near the very end of the usplash boot process some distorted horizontal visual garbage appears near and on the progress bar for the last centimeter or so of progress. Just looks yucky. ** Affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- artifacts near the end of usplash boot https://launchpad.net/bugs/66652 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32415] Re: Bluetooth Mouse and Keyboard Broken in Dapper Flight 4 6.06 beta 2
This is still an issue on Dapper. Onkar's rejection reasons are wrong. Changing the HIDD_ENABLED setting does not work. There is a problem with bluetooth and GDM interaction. IIRC the problem is dbus permissions related. This bug makes Ubunutu look very bad. If you boot stock Dapper with a bluetooth keyboard (such as my Logitech DiNovo) The keyboard and mouse cease functioning as soon as GDM starts. I'll try to get a daemon.log for you later today. -- Bluetooth Mouse and Keyboard Broken in Dapper Flight 4 6.06 beta 2 https://launchpad.net/bugs/32415 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57153] Re: 1:1.0.2-0ubuntu10.3 breaks HP nx6125
fglrx on MacBookPro also fails to detect device. Reverting to -0ubuntu10.1 makes things work. -- 1:1.0.2-0ubuntu10.3 breaks HP nx6125 https://launchpad.net/bugs/57153 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54051] Re: Bluetooth keyboard and mouse disabled by gdm
This is more properly addressed by bluez-utils bug #32415 The problem is likely a dbus interaction with gdm/x and it is probably the bluez package's fault. The bluetooth keyboard does not work in bluetooth mode in X at all. If bluez is not started, it pretends to be a ps/2 or usb board, X is none the wiser and it works. If anyone else has this problem see workarounds in bug #32415 This bug should probable be closed against gdm. -- Bluetooth keyboard and mouse disabled by gdm https://launchpad.net/bugs/54051 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32415] Re: Bluetooth Mouse and Keyboard Broken in Dapper Flight 4 6.06 beta 2
Confirmed with Logitech diNovo setup. The issue is a GDM interaction. Perhapse a bug should be filed against GDM as well? -- Bluetooth Mouse and Keyboard Broken in Dapper Flight 4 6.06 beta 2 https://launchpad.net/bugs/32415 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54051] Bluetooth keyboard and mouse disabled by gdm
Public bug reported: This in reference to bluez-utils bug #32415 Starting gdm causes my logitech diNovo bluetooth keyboard and mouse not to function. Stopping gdm or stopping or restarting bluez-utils does not restore function. Only rebooting (!) does. Many others with bluetooth peripherals report the same thing. See #32415. Workaround: # update-rc.d -f bluez-utils remove ** Affects: gdm (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Bluetooth keyboard and mouse disabled by gdm https://launchpad.net/bugs/54051 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
