[Bug 545592] Re: dummy output, no sound on HDA Intel internal sound card

[Brian Knoll]

This doesn't seem to be fixed in Lucid Beta 2.  I'm getting this problem
on Lucid Beta 2 machines still.


** Changed in: pulseaudio (Ubuntu)
   Status: Fix Released => Confirmed

-- 
dummy output, no sound on HDA Intel internal sound card
https://bugs.launchpad.net/bugs/545592
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 557421] Re: module-udev-detect races with module-default-device-restore

[Brian Knoll]

I just tried removing pulseaudio completely (which unfortunately does
remove the "ubuntu-desktop" package as a dependency, but that's okay for
my purposes) and I got my sound back.  I have done this twice now and it
worked both times.  If I put pulseaudio back in, I lose sound.

-- 
module-udev-detect races with module-default-device-restore
https://bugs.launchpad.net/bugs/557421
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 559389] Re: [Lucid] Sound subsystem stops working with multiple applications

[Brian Knoll]

*** This bug is a duplicate of bug 559442 ***
https://bugs.launchpad.net/bugs/559442

If you look in your sound properties, under "Hardware", there should be
a "Dummy Output" listed instead of the actual sound hardware you have.
I have several Lucid AMD64 machines doing this.

** Changed in: gnome-volume-manager
   Status: New => Confirmed

-- 
[Lucid] Sound subsystem stops working with multiple applications
https://bugs.launchpad.net/bugs/559389
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu (via bug 559442).

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 570984] [NEW] [Realtek ALC883] pactl stat failed to find default card

[Brian Knoll]

Public bug reported:

Binary package hint: pulseaudio

There is no audio in Lucid AMD64 with this audio controller.

The sound worked when I first installed, then simply stopped working.  I
can get sound if I forcibly remove Pulseaudio, but of course I'd rather
not take that drastic step.  I am only mentioning it because it might
help debug the issue.

When I look in my sound properties under Hardware, I see a "Dummy
Output" device, but the real hardware is not found.

Again, sound is completely unusable (nonexistent) unless I remove
Pulseaudio.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfccf4000 irq 22'
   Mixer name   : 'Silicon Image SiI1392 HDMI'
   Components   : 'HDA:10ec0883,1043829f,0012 
HDA:10951392,,0010'
   Controls  : 40
   Simple ctrls  : 22
Date: Tue Apr 27 18:29:40 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 
(20100419.1)
PactlStat:
 
PactlStatStderr:
 C o n n e c t i o n   f a i l u r e :   C o n n e c t i o n   r e f u s e d 
  p a _ c o n t e x t _ c o n n e c t ( )   f a i l e d :   C o n n e c t i o n 
  r e f u s e d
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: pulseaudio
Symptom: audio
Title: [Realtek ALC883] pactl stat failed to find default card
dmi.bios.date: 07/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0604
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5E-VM HDMI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2008:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5E-VM HDMI
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lucid

-- 
[Realtek ALC883] pactl stat failed to find default card
https://bugs.launchpad.net/bugs/570984
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 570984] Re: [Realtek ALC883] pactl stat failed to find default card

[Brian Knoll]

** Attachment added: "AlsaDevices.txt"
   http://launchpadlibrarian.net/45815047/AlsaDevices.txt

** Attachment added: "AplayDevices.txt"
   http://launchpadlibrarian.net/45815048/AplayDevices.txt

** Attachment added: "ArecordDevices.txt"
   http://launchpadlibrarian.net/45815049/ArecordDevices.txt

** Attachment added: "BootDmesg.txt"
   http://launchpadlibrarian.net/45815050/BootDmesg.txt

** Attachment added: "Card0.Amixer.values.txt"
   http://launchpadlibrarian.net/45815051/Card0.Amixer.values.txt

** Attachment added: "Card0.Codecs.codec.0.txt"
   http://launchpadlibrarian.net/45815052/Card0.Codecs.codec.0.txt

** Attachment added: "Card0.Codecs.codec.1.txt"
   http://launchpadlibrarian.net/45815053/Card0.Codecs.codec.1.txt

** Attachment added: "CurrentDmesg.txt"
   http://launchpadlibrarian.net/45815054/CurrentDmesg.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/45815055/Dependencies.txt

** Attachment added: "PciMultimedia.txt"
   http://launchpadlibrarian.net/45815056/PciMultimedia.txt

** Attachment added: "ProcCpuinfo.txt"
   http://launchpadlibrarian.net/45815057/ProcCpuinfo.txt

-- 
[Realtek ALC883] pactl stat failed to find default card
https://bugs.launchpad.net/bugs/570984
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 570984] Re: [Realtek ALC883] pactl stat failed to find default card

[Brian Knoll]

I just tried something: If I do an "alsa force-reload", then I get my
audio back and in my sound properties, under Hardware, it shows the
actual hardware device.  Of course, if I reboot, I lose my sound again.

Perhaps this will help someone on the audio team track down where the
problem is.  Please let me know what other information I can provide, in
addition to what I have already put in this ticket.  Thanks!

-- 
[Realtek ALC883] pactl stat failed to find default card
https://bugs.launchpad.net/bugs/570984
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 570984] Re: [Realtek ALC883] pactl stat failed to find default card

[Brian Knoll]

After rebooting several times and reproducing the situation, where I
don't get sound until I run "alsa force-reload", I rebooted one more
time, and this time when I ran "alsa force-reload" I did not get my
audio back.  I also don't see the hardware listed under the sound
properties.  So apparently even though this works some of the time, it
doesn't work ALL of the time.  I can run "alsa force-reload" again and
again, and it doesn't give me back my sound, like it did on previous
boots.  This is very inconsistent.

-- 
[Realtek ALC883] pactl stat failed to find default card
https://bugs.launchpad.net/bugs/570984
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 557421] Re: module-udev-detect races with module-default-device-restore

[Brian Knoll]

Daniel, I tried to test your PPA package on my AMD64 system, but after
adding your PPA to my Software Sources, I got the following error:

Failed to fetch 
http://ppa.launchpad.net/crimsun/ppa/ubuntu/dists/lucid/main/binary-amd64/Packages.gz
  404  Not Found
Some index files failed to download, they have been ignored, or old ones used 
instead.

How can I help test this package?

-- 
module-udev-detect races with module-default-device-restore
https://bugs.launchpad.net/bugs/557421
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 558910] Re: No sound in Lucid Lynx Beta 2

[Brian Knoll]

I urge everybody on this bug to listen to Daniel T. Chen and go look at
but 557421 to see if it looks like that might be the same bug you are
experiencing, and if so, then add yourself to the list of affected users
for that bug.

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/557421

-- 
No sound in Lucid Lynx Beta 2
https://bugs.launchpad.net/bugs/558910
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 557421] Re: module-udev-detect races with module-default-device-restore

[Brian Knoll]

I just reinstalled from the Alternate Release Candidate ISO image, and
my desktop installation worked fine for a few hours, then I noticed that
I didn't get sound any more.  I'm not sure if I rebooted before the
sound went away, or what, but it had worked right from the install, then
went away.  So even if you get sound right at first, there is something
that can trigger the sound to go away later on.

I did check the properties of the hardware, and now all I see is my
"Dummy Output", just like I always see when the sound goes away.  Right
after the install it was showing the Intel audio device, and the sound
was working then of course.

-- 
module-udev-detect races with module-default-device-restore
https://bugs.launchpad.net/bugs/557421
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 557421] Re: module-udev-detect races with module-default-device-restore

[Brian Knoll]

I think I might have found something: For me, this failure to detect my
audio hardware seems to occur much more frequently when I have a bridged
network set up on my eth0 device.  If I don't do that, my audio is
usually fine.  If I DO set up a bridge on my eth0, however, then when I
reboot I almost never have audio, and I have to run "alsa force-reload"
to get audio.

-- 
module-udev-detect races with module-default-device-restore
https://bugs.launchpad.net/bugs/557421
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 577509] [NEW] Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

Public bug reported:

Binary package hint: pulseaudio

On an install of Ubuntu Lucid 10.04 LTS AMD64, I could reboot the system
and it would come back up and consistently have audio.  However, once I
configured a bridged network on my eth0 device in
/etc/network/interfaces, the system would no longer have audio after a
reboot.

The bridge is working fine.  My /etc/network/interfaces is configured as
follows:

--
auto lo
iface lo inet loopback

# The bridge network interface
auto br0 
iface br0 inet dhcp
bridge_ports eth0 
bridge_fd 9 
bridge_hello 2 
bridge_maxage 12 
bridge_stp off 

# The primary network interface
auto eth0
iface eth0 inet manual
--

I can usually get my sound back by running "alsa force-reload" from the
desktop.  Running this from rc.local during system boot does not work,
however.

When this happens, my sound hardware is not detected.  No sound hardware
shows up in "Sound Preferences" under Hardware, and in "Output" all I
have is a "Dummy Output".  But of course, without the bridge, the
hardware is detected and everything works.

Bridging is an important feature, and I think it's rather important to
get this fixed in the LTS release.  Please let me know how I can help
test or fix things.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-22.33-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-server x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bknoll 3381 F pulseaudio
  root   3394 F arecord
 /dev/snd/pcmC0D0c:   root   3394 F...m arecord
 /dev/snd/timer:  root   3394 f arecord
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfccf4000 irq 22'
   Mixer name   : 'Silicon Image SiI1392 HDMI'
   Components   : 'HDA:10ec0883,1043829f,0012 
HDA:10951392,,0010'
   Controls  : 40
   Simple ctrls  : 22
Date: Sat May  8 12:05:36 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Title: Pulseaudio is not running
dmi.bios.date: 07/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0604
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5E-VM HDMI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2008:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5E-VM HDMI
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bridge bridge-utils lucid network networking

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

** Attachment added: "AlsaDevices.txt"
   http://launchpadlibrarian.net/48069135/AlsaDevices.txt

** Attachment added: "AplayDevices.txt"
   http://launchpadlibrarian.net/48069136/AplayDevices.txt

** Attachment added: "ArecordDevices.txt"
   http://launchpadlibrarian.net/48069137/ArecordDevices.txt

** Attachment added: "BootDmesg.txt"
   http://launchpadlibrarian.net/48069138/BootDmesg.txt

** Attachment added: "Card0.Amixer.values.txt"
   http://launchpadlibrarian.net/48069139/Card0.Amixer.values.txt

** Attachment added: "Card0.Codecs.codec.0.txt"
   http://launchpadlibrarian.net/48069140/Card0.Codecs.codec.0.txt

** Attachment added: "Card0.Codecs.codec.1.txt"
   http://launchpadlibrarian.net/48069141/Card0.Codecs.codec.1.txt

** Attachment added: "CurrentDmesg.txt"
   http://launchpadlibrarian.net/48069142/CurrentDmesg.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/48069143/Dependencies.txt

** Attachment added: "PciMultimedia.txt"
   http://launchpadlibrarian.net/48069144/PciMultimedia.txt

** Attachment added: "ProcCpuinfo.txt"
   http://launchpadlibrarian.net/48069145/ProcCpuinfo.txt

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

Changing affected package at the request of Daniel T. Chen

** Package changed: pulseaudio (Ubuntu) => linux-meta (Ubuntu)

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

When I tried to change the package name to "linux", Launchpad stopped me
and said that there were too many matches, so it wouldn't allow it.
That's when I changed the package name to "linux-2.6.32-22-server", and
then Launchpad automatically reassigned it to "linux-meta".

I'm happy to change it to whatever it needs to be, but it looks like
"linux" isn't going to be accepted by the system.

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 542725] Re: Amarok will not create music collection

[Brian Knoll]

This is confirmed on an AMD64 install of Ubuntu Lucid Lynx 10.04.

** Changed in: amarok (Ubuntu)
   Status: New => Confirmed

-- 
Amarok will not create music collection
https://bugs.launchpad.net/bugs/542725
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 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

Thanks for helping with this.  I have verified that the problem does
indeed occur with the upstream 2.6.32-02063211-generic #02063211 kernel,
and I have removed the "needs-upstream-testing" tag from this ticket, as
requested.


** Tags removed: needs-upstream-testing

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

I changed the status to "confirmed" after testing against the upstream
kernel, because "invalid" didn't seem appropriate any more.  If that
wasn't correct, please let me know which status you would prefer, and/or
change it to another status.  Thanks!

** Tags added: apport-collected

** Description changed:

  Binary package hint: pulseaudio
  
  On an install of Ubuntu Lucid 10.04 LTS AMD64, I could reboot the system
  and it would come back up and consistently have audio.  However, once I
  configured a bridged network on my eth0 device in
  /etc/network/interfaces, the system would no longer have audio after a
  reboot.
  
  The bridge is working fine.  My /etc/network/interfaces is configured as
  follows:
  
  --
  auto lo
  iface lo inet loopback
  
  # The bridge network interface
  auto br0 
  iface br0 inet dhcp
  bridge_ports eth0 
  bridge_fd 9 
  bridge_hello 2 
  bridge_maxage 12 
  bridge_stp off 
  
  # The primary network interface
  auto eth0
  iface eth0 inet manual
  --
  
  I can usually get my sound back by running "alsa force-reload" from the
  desktop.  Running this from rc.local during system boot does not work,
  however.
  
  When this happens, my sound hardware is not detected.  No sound hardware
  shows up in "Sound Preferences" under Hardware, and in "Output" all I
  have is a "Dummy Output".  But of course, without the bridge, the
  hardware is detected and everything works.
  
  Bridging is an important feature, and I think it's rather important to
  get this fixed in the LTS release.  Please let me know how I can help
  test or fix things.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-22.33-server 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-server x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bknoll 3381 F pulseaudio
root   3394 F arecord
   /dev/snd/pcmC0D0c:   root   3394 F...m arecord
   /dev/snd/timer:  root   3394 f arecord
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfccf4000 irq 22'
 Mixer name : 'Silicon Image SiI1392 HDMI'
 Components : 'HDA:10ec0883,1043829f,0012 
HDA:10951392,,0010'
 Controls  : 40
 Simple ctrls  : 22
  Date: Sat May  8 12:05:36 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Title: Pulseaudio is not running
  dmi.bios.date: 07/16/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5E-VM HDMI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2008:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5E-VM HDMI
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
+ --- 
+ Architecture: amd64
+ DistroRelease: Ubuntu 10.04
+ InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
+ Package: linux (not installed)
+ ProcEnviron:
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags: lucid
+ Uname: Linux 2.6.32-02063211-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UserGroups: adm admin cdrom crontab dialout floppy games kvm lp lpadmin 
plugdev root sambashare staff users video

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

I've collected additional data from the failed state, using the upstream
kernel, and attached it to this case.

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking

[Brian Knoll]

I have now also tested this issue against the 2.6.34-020634rc6-generic
#020634rc6 upstream kernel, and I confirm that the problem also exists
when using that kernel.


** Description changed:

  Binary package hint: pulseaudio
  
  On an install of Ubuntu Lucid 10.04 LTS AMD64, I could reboot the system
  and it would come back up and consistently have audio.  However, once I
  configured a bridged network on my eth0 device in
  /etc/network/interfaces, the system would no longer have audio after a
  reboot.
  
  The bridge is working fine.  My /etc/network/interfaces is configured as
  follows:
  
  --
  auto lo
  iface lo inet loopback
  
  # The bridge network interface
  auto br0 
  iface br0 inet dhcp
  bridge_ports eth0 
  bridge_fd 9 
  bridge_hello 2 
  bridge_maxage 12 
  bridge_stp off 
  
  # The primary network interface
  auto eth0
  iface eth0 inet manual
  --
  
  I can usually get my sound back by running "alsa force-reload" from the
  desktop.  Running this from rc.local during system boot does not work,
  however.
  
  When this happens, my sound hardware is not detected.  No sound hardware
  shows up in "Sound Preferences" under Hardware, and in "Output" all I
  have is a "Dummy Output".  But of course, without the bridge, the
  hardware is detected and everything works.
  
  Bridging is an important feature, and I think it's rather important to
  get this fixed in the LTS release.  Please let me know how I can help
  test or fix things.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-22.33-server 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-server x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bknoll 3381 F pulseaudio
root   3394 F arecord
   /dev/snd/pcmC0D0c:   root   3394 F...m arecord
   /dev/snd/timer:  root   3394 f arecord
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfccf4000 irq 22'
 Mixer name : 'Silicon Image SiI1392 HDMI'
 Components : 'HDA:10ec0883,1043829f,0012 
HDA:10951392,,0010'
 Controls  : 40
 Simple ctrls  : 22
  Date: Sat May  8 12:05:36 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Title: Pulseaudio is not running
  dmi.bios.date: 07/16/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5E-VM HDMI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2008:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5E-VM HDMI
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  Package: linux (not installed)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags: lucid
  Uname: Linux 2.6.32-02063211-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin cdrom crontab dialout floppy games kvm lp lpadmin 
plugdev root sambashare staff users video
+ 
+ --- 
+ Architecture: amd64
+ DistroRelease: Ubuntu 10.04
+ InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
+ Package: linux (not installed)
+ ProcEnviron:
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags: lucid
+ Uname: Linux 2.6.34-020634rc6-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UserGroups: adm admin cdrom crontab dialout floppy games kvm lp lpadmin 
plugdev root sambashare staff users video

-- 
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
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 524941] [NEW] Grub fails to install on Lucid virtio-based guests running under KVM during installation

[Brian Knoll]

Public bug reported:

Binary package hint: grub

Grub does not install if Lucid is installed onto a KVM guest using
virtio disks.  The installation will progress to the point where the
boot loader is supposed to be installed, and an error message will pop
up saying that grub failed to install.  If you continue the installation
anyhow, the system will of course not boot because there is no grub boot
loader installed.

Further, if you then boot off the Lucid CD ISO to rescue the system, you
will find that the Lucid CD in rescue mode does not detect any disks.
You must to a modprobe of the virtio driver in order to get the Lucid
ISO to recognize the virtio disk in rescue mode.  Then, of course, you
have to repair the installation.

This only happens if you install the system onto a virtio disk.  If you
install onto, for instance, an IDE disk, then switch KVM to use virtio,
everything is fine.  But it's obvious that something is very broken in
the virtio handling of Lucid at installation time.

ProblemType: Bug
Architecture: amd64
Date: Sat Feb 20 10:45:56 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
Package: grub (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: grub
Uname: Linux 2.6.32-13-generic x86_64

** Affects: grub (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kvm lucid qemu-kvm virtio

-- 
Grub fails to install on Lucid virtio-based guests running under KVM during 
installation
https://bugs.launchpad.net/bugs/524941
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 524434] Re: Lucid Alpha 2 server iso install fails at bootloader in KVM

[Brian Knoll]

** Changed in: ubuntu
   Status: New => Confirmed

-- 
Lucid Alpha 2 server iso install fails at bootloader in KVM
https://bugs.launchpad.net/bugs/524434
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 509186] [NEW] Screen Goes Black With i915 GPU Hung Render Errors

[Brian Knoll]

Public bug reported:

Binary package hint: xorg

This usually happens when the system is idle for some time.  I haven't
yet checked to see if disabling the screen saver (which is OpenGL)
helps, although I plan to try that.

ProblemType: Bug
Architecture: amd64
Date: Mon Jan 18 10:26:10 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
MachineType: System manufacturer P5E-VM HDMI
Package: xorg 1:7.5+1ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-10-generic 
root=UUID=1a19e664-fb39-4ca9-b613-4f55d1405376 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu1
 libgl1-mesa-glx 7.7-0ubuntu5
 libdrm2 2.4.17-0ubuntu1
 xserver-xorg-video-intel 2:2.9.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20091125.0061c4db-0ubuntu2
SourcePackage: xorg
Symptom: display
Tags:  freeze lucid
Title: Xorg freeze
Uname: Linux 2.6.32-10-generic x86_64
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 07/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0604
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5E-VM HDMI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2008:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5E-VM HDMI
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
fglrx: Not loaded
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 architecture:   x86_64kernel: 2.6.32-10-generic
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error:   
 Cannot open display ":0"
   Exiting

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze lucid

-- 
Screen Goes Black With i915 GPU Hung Render Errors
https://bugs.launchpad.net/bugs/509186
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 509186] Re: Screen Goes Black With i915 GPU Hung Render Errors

[Brian Knoll]

** Attachment added: "BootDmesg.txt"
   http://launchpadlibrarian.net/38042717/BootDmesg.txt

** Attachment added: "CurrentDmesg.txt"
   http://launchpadlibrarian.net/38042718/CurrentDmesg.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/38042719/Dependencies.txt

** Attachment added: "GdmLog.txt"
   http://launchpadlibrarian.net/38042720/GdmLog.txt

** Attachment added: "GdmLogOld.txt"
   http://launchpadlibrarian.net/38042721/GdmLogOld.txt

** Attachment added: "Lspci.txt"
   http://launchpadlibrarian.net/38042722/Lspci.txt

** Attachment added: "Lsusb.txt"
   http://launchpadlibrarian.net/38042723/Lsusb.txt

** Attachment added: "PciDisplay.txt"
   http://launchpadlibrarian.net/38042725/PciDisplay.txt

** Attachment added: "ProcCpuinfo.txt"
   http://launchpadlibrarian.net/38042726/ProcCpuinfo.txt

** Attachment added: "ProcInterrupts.txt"
   http://launchpadlibrarian.net/38042727/ProcInterrupts.txt

** Attachment added: "ProcModules.txt"
   http://launchpadlibrarian.net/38042728/ProcModules.txt

** Attachment added: "UdevDb.txt"
   http://launchpadlibrarian.net/38042729/UdevDb.txt

** Attachment added: "UdevLog.txt"
   http://launchpadlibrarian.net/38042730/UdevLog.txt

** Attachment added: "XorgLog.txt"
   http://launchpadlibrarian.net/38042731/XorgLog.txt

** Attachment added: "XorgLogOld.txt"
   http://launchpadlibrarian.net/38042732/XorgLogOld.txt

** Attachment added: "Xrandr.txt"
   http://launchpadlibrarian.net/38042733/Xrandr.txt

** Attachment added: "setxkbmap.txt"
   http://launchpadlibrarian.net/38042735/setxkbmap.txt

** Attachment added: "xdpyinfo.txt"
   http://launchpadlibrarian.net/38042736/xdpyinfo.txt

-- 
Screen Goes Black With i915 GPU Hung Render Errors
https://bugs.launchpad.net/bugs/509186
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 509186] Re: Screen Goes Black With i915 GPU Hung Render Errors

[Brian Knoll]

I want to mention that the system, other than the video, does stay
responsive when this situation occurs.  I see the render error and GPU
hung error in my logs and the console becomes useless because there is
no longer any video after this happens, but the system itself keeps
running.  I generated this bug report by SSHing into the system to
report the bug.

-- 
Screen Goes Black With i915 GPU Hung Render Errors
https://bugs.launchpad.net/bugs/509186
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 524941] Re: Grub fails to install on Lucid guests running under KVM during installation

[Brian Knoll]

I just changed the description of the bug to remove the requirement that
the guest be virtio-based in order to trigger the bug.  I can also
confirm that I have, now, seen the failure under guests that were ide-
based and scsi-based, as well as virtio-based guests.

** Summary changed:

- Grub fails to install on Lucid virtio-based guests running under KVM during 
installation
+ Grub fails to install on Lucid guests running under KVM during installation

-- 
Grub fails to install on Lucid guests running under KVM during installation
https://bugs.launchpad.net/bugs/524941
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 539802] Re: does not terminate at computer shutdown

[Brian Knoll]

I got this same error on the AMD64 platform, so that platform is also
affected.

-- 
does not terminate at computer shutdown
https://bugs.launchpad.net/bugs/539802
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 558910] Re: No sound in Lucid Lynx Beta 2

[Brian Knoll]

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

-- 
No sound in Lucid Lynx Beta 2
https://bugs.launchpad.net/bugs/558910
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 558910] Re: No sound in Lucid Lynx Beta 2

[Brian Knoll]

I rebooted my system (AMD64 Lucid) this morning and now find that no
sound hardware is detected any more.  I see the volume icon, but it's
"blank" (for lack of a better way to describe it; it looks hollow) and
in the properties for the volume control, under "Hardware", all I have
is a "Dummy Device".  So my Intel HDA Audio is no longer detected.

The controller does show up in lspci, so at that level the device is
detected by the kernel, but the volume control in Gnome does not see it
any more.

I have at least two machines doing this.  Both of these machines are
64-bit Lucid machines.

-- 
No sound in Lucid Lynx Beta 2
https://bugs.launchpad.net/bugs/558910
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 590780] [NEW] Installing "randomsound" package causes Pulseaudio to stop functioning at reboot

[Brian Knoll]

Public bug reported:

Binary package hint: randomsound

Installing the "randomsound" package causes Pulseaudio to stop
functioning at the next reboot.  The sound hardware is no longer
detected when this package is installed.  Removing the "randomsound"
package resolves the issue.

There is a workaround, in the sense that once the system is booted, if
you log in to a shell, then run "alsa force-reload", you'll get sound
back.  But upon the next reboot, the sound goes away again.  Removing
the "randomsound" package will resolve the issue.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-22.36-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-server x86_64
NonfreeKernelModules: openafs nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bknoll10239 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbffc000 irq 16'
   Mixer name   : 'Analog Devices AD1984'
   Components   : 'HDA:11d41984,1028021d,00100400'
   Controls  : 31
   Simple ctrls  : 19
Date: Mon Jun  7 09:19:32 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Title: Pulseaudio is not running
dmi.bios.date: 03/01/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0RW199
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd03/01/2010:svnDellInc.:pnPrecisionWorkStationT7400:pvr:rvnDellInc.:rn0RW199:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7400
dmi.sys.vendor: Dell Inc.

** Affects: randomsound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug audio lucid randomsound

-- 
Installing "randomsound" package causes Pulseaudio to stop functioning at reboot
https://bugs.launchpad.net/bugs/590780
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 590780] Re: Installing "randomsound" package causes Pulseaudio to stop functioning at reboot

[Brian Knoll]

** Attachment added: "AlsaDevices.txt"
   http://launchpadlibrarian.net/49818564/AlsaDevices.txt

** Attachment added: "AplayDevices.txt"
   http://launchpadlibrarian.net/49818565/AplayDevices.txt

** Attachment added: "BootDmesg.txt"
   http://launchpadlibrarian.net/49818566/BootDmesg.txt

** Attachment added: "Card0.Amixer.values.txt"
   http://launchpadlibrarian.net/49818567/Card0.Amixer.values.txt

** Attachment added: "Card0.Codecs.codec.0.txt"
   http://launchpadlibrarian.net/49818568/Card0.Codecs.codec.0.txt

** Attachment added: "CurrentDmesg.txt"
   http://launchpadlibrarian.net/49818569/CurrentDmesg.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/49818570/Dependencies.txt

** Attachment added: "PciMultimedia.txt"
   http://launchpadlibrarian.net/49818571/PciMultimedia.txt

** Attachment added: "ProcCpuinfo.txt"
   http://launchpadlibrarian.net/49818572/ProcCpuinfo.txt

-- 
Installing "randomsound" package causes Pulseaudio to stop functioning at reboot
https://bugs.launchpad.net/bugs/590780
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 545161] [NEW] WARNING: at /build/buildd/linux-2.6.32/fs/quota/dquot.c:964 dquot_claim_space 0x165/0x170()

[Brian Knoll]

Public bug reported:

This occurs when quotas are enabled.  I have seen this on AMD64 systems;
I am unsure if it occurs on i386 or not.

To reproduce, do this:

1.  Enable journaled quota support with 
"usrquota,grpquota,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0" 
filesystem options in /etc/fstab.
2.  Install quotas by "aptitude install quota"
3.  Watch as the kernel oopses and apport reports that the system may become 
unstable.

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be 
restarted.
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bknoll 1861 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbffc000 irq 16'
   Mixer name   : 'Analog Devices AD1984'
   Components   : 'HDA:11d41984,1028021d,00100400'
   Controls  : 30
   Simple ctrls  : 18
Date: Tue Mar 23 11:10:28 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=985a2a8a-b990-4372-8616-ee006d0f7f6f
MachineType: Dell Inc. Precision WorkStation T7400
NonfreeKernelModules: openafs nvidia
Package: linux-image-2.6.32-16-server 2.6.32-16.25
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-server 
root=UUID=fd18a0f2-56f1-4e25-9c61-19eb28181d97 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-16.25-server
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
RfKill:
 
SourcePackage: linux
TestedUpstream: No
Title: WARNING: at /build/buildd/linux-2.6.32/fs/quota/dquot.c:964 
dquot_claim_space+0x165/0x170()
Uname: Linux 2.6.32-16-server x86_64
dmi.bios.date: 08/21/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0RW199
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/21/2008:svnDellInc.:pnPrecisionWorkStationT7400:pvr:rvnDellInc.:rn0RW199:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7400
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-kerneloops kernel-oops lucid needs-upstream-testing 
regression-potential

-- 
WARNING: at /build/buildd/linux-2.6.32/fs/quota/dquot.c:964 dquot_claim_space 
0x165/0x170()
https://bugs.launchpad.net/bugs/545161
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 545161] Re: WARNING: at /build/buildd/linux-2.6.32/fs/quota/dquot.c:964 dquot_claim_space 0x165/0x170()

[Brian Knoll]

** Attachment added: "AlsaDevices.txt"
   http://launchpadlibrarian.net/41723054/AlsaDevices.txt

** Attachment added: "AplayDevices.txt"
   http://launchpadlibrarian.net/41723055/AplayDevices.txt

** Attachment added: "BootDmesg.txt"
   http://launchpadlibrarian.net/41723056/BootDmesg.txt

** Attachment added: "Card0.Amixer.values.txt"
   http://launchpadlibrarian.net/41723057/Card0.Amixer.values.txt

** Attachment added: "Card0.Codecs.codec.0.txt"
   http://launchpadlibrarian.net/41723059/Card0.Codecs.codec.0.txt

** Attachment added: "CurrentDmesg.txt"
   http://launchpadlibrarian.net/41723061/CurrentDmesg.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/41723062/Dependencies.txt

** Attachment added: "IwConfig.txt"
   http://launchpadlibrarian.net/41723063/IwConfig.txt

** Attachment added: "Lspci.txt"
   http://launchpadlibrarian.net/41723064/Lspci.txt

** Attachment added: "Lsusb.txt"
   http://launchpadlibrarian.net/41723067/Lsusb.txt

** Attachment added: "OopsText.txt"
   http://launchpadlibrarian.net/41723068/OopsText.txt

** Attachment added: "PciMultimedia.txt"
   http://launchpadlibrarian.net/41723071/PciMultimedia.txt

** Attachment added: "ProcCpuinfo.txt"
   http://launchpadlibrarian.net/41723072/ProcCpuinfo.txt

** Attachment added: "ProcInterrupts.txt"
   http://launchpadlibrarian.net/41723073/ProcInterrupts.txt

** Attachment added: "ProcModules.txt"
   http://launchpadlibrarian.net/41723075/ProcModules.txt

** Attachment added: "UdevDb.txt"
   http://launchpadlibrarian.net/41723076/UdevDb.txt

** Attachment added: "UdevLog.txt"
   http://launchpadlibrarian.net/41723078/UdevLog.txt

** Attachment added: "WifiSyslog.txt"
   http://launchpadlibrarian.net/41723079/WifiSyslog.txt

-- 
WARNING: at /build/buildd/linux-2.6.32/fs/quota/dquot.c:964 dquot_claim_space 
0x165/0x170()
https://bugs.launchpad.net/bugs/545161
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 458023] [NEW] seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)

[Brian Knoll]

Public bug reported:

Binary package hint: seahorse-plugins

I got this bug while browsing websites.  I notice the apport system
created a description mentioning "seahorse-plugins" but I was actually
using Firefox; I'm not sure what caused that.

I am on an AMD64 system, as specified in the tags.  That's why I filed
this bug, rather than simply referencing 429322, which is an i386 bug
(which seems to be the same thing but is tagged as i386).

ProblemType: Crash
Architecture: amd64
AssertionMessage: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion 
failed: (obj && (obj->profile_list == NULL) && obj->orb)
Date: Wed Oct 21 20:48:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/seahorse-agent
Package: seahorse-plugins 2.28.1-0ubuntu3
ProcCmdline: /usr/bin/seahorse-agent --execute gnome-session
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: seahorse-plugins
StacktraceTop:
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr ()
 IOP_generate_profiles ()
Title: seahorse-agent assert failure: 
ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && 
(obj->profile_list == NULL) && obj->orb)
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom crontab dialout games lpadmin plugdev sambashare 
staff users video

** Affects: seahorse-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash

-- 
seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: 
assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)
https://bugs.launchpad.net/bugs/458023
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 458023] Re: seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)

[Brian Knoll]

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/34138075/Dependencies.txt

** Attachment added: "Disassembly.txt"
   http://launchpadlibrarian.net/34138076/Disassembly.txt

** Attachment added: "ProcMaps.txt"
   http://launchpadlibrarian.net/34138077/ProcMaps.txt

** Attachment added: "ProcStatus.txt"
   http://launchpadlibrarian.net/34138078/ProcStatus.txt

** Attachment added: "Registers.txt"
   http://launchpadlibrarian.net/34138079/Registers.txt

** Attachment added: "Stacktrace.txt"
   http://launchpadlibrarian.net/34138081/Stacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   http://launchpadlibrarian.net/34138082/ThreadStacktrace.txt

** Attachment added: "XsessionErrors.txt"
   http://launchpadlibrarian.net/34138084/XsessionErrors.txt

-- 
seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: 
assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)
https://bugs.launchpad.net/bugs/458023
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 458022] [NEW] seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)

[Brian Knoll]

Public bug reported:

Binary package hint: seahorse-plugins

I got this bug while browsing websites.  I notice the apport system
created a description mentioning "seahorse-plugins" but I was actually
using Firefox; I'm not sure what caused that.

I am on an AMD64 system, as specified in the tags.  That's why I filed
this bug, rather than simply referencing 429322, which is an i386 bug
(which seems to be the same thing but is tagged as i386).

ProblemType: Crash
Architecture: amd64
AssertionMessage: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion 
failed: (obj && (obj->profile_list == NULL) && obj->orb)
Date: Wed Oct 21 20:48:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/seahorse-agent
Package: seahorse-plugins 2.28.1-0ubuntu3
ProcCmdline: /usr/bin/seahorse-agent --execute gnome-session
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: seahorse-plugins
StacktraceTop:
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr ()
 IOP_generate_profiles ()
Title: seahorse-agent assert failure: 
ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && 
(obj->profile_list == NULL) && obj->orb)
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom crontab dialout games lpadmin plugdev sambashare 
staff users video

** Affects: seahorse-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash

-- 
seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: 
assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)
https://bugs.launchpad.net/bugs/458022
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 458022] Re: seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)

[Brian Knoll]

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/34138067/Dependencies.txt

** Attachment added: "Disassembly.txt"
   http://launchpadlibrarian.net/34138068/Disassembly.txt

** Attachment added: "ProcMaps.txt"
   http://launchpadlibrarian.net/34138069/ProcMaps.txt

** Attachment added: "ProcStatus.txt"
   http://launchpadlibrarian.net/34138070/ProcStatus.txt

** Attachment added: "Registers.txt"
   http://launchpadlibrarian.net/34138071/Registers.txt

** Attachment added: "Stacktrace.txt"
   http://launchpadlibrarian.net/34138072/Stacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   http://launchpadlibrarian.net/34138073/ThreadStacktrace.txt

** Attachment added: "XsessionErrors.txt"
   http://launchpadlibrarian.net/34138074/XsessionErrors.txt

-- 
seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: 
assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)
https://bugs.launchpad.net/bugs/458022
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 490193] Re: Please sync virtualbox-ose 3.0.10-dfsg-2 (universe) from Debian testing (main)

[Brian Knoll]

I want to add that importing 3.0.10 is mentioned as the resolution to
ticket #474625, which means that ticket is one of the drivers for
needing this import.  The implication is that Lucid users won't be able
to run Virtualbox without going out and getting the sources themselves,
or otherwise patching things themselves, unless this import is done.

-- 
Please sync virtualbox-ose 3.0.10-dfsg-2 (universe) from Debian testing (main)
https://bugs.launchpad.net/bugs/490193
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 498219] Re: Please merge virtualbox-ose 3.1.2-dfsg-1 (universe) from Debian unstable (main)

[Brian Knoll]

This merge would resolve an issue with the virtualbox modules not
building in the 3.0.8 currently in Lucid, by upgrading to a version that
includes fixes for this issue.


** Changed in: virtualbox-ose (Ubuntu)
   Status: New => Confirmed

-- 
Please merge virtualbox-ose 3.1.2-dfsg-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/498219
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 474625] Re: [lucid] VirtualBox kernel module fails to build against Linux >= 2.6.32

[Brian Knoll]

Additional information: Bug #498219 is a request to merge a newer
version of virtualbox into Lucid, which would resolve this issue if it
gets merged.

-- 
[lucid] VirtualBox kernel module fails to build against Linux >= 2.6.32
https://bugs.launchpad.net/bugs/474625
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 500272] Re: qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)

[Brian Knoll]

I am curious as to what you're running into, as I've run into a problem
myself trying to build the package for all of the targets.

The problem I've run into when trying to build the package from source
is that it doesn't seem to build all of the targets that the old
(0.11.x) package did.  So I end up with only the qemu-system-x86_64
target plus a few supporting binaries, but I'm missing all the full-virt
packages for the other architectures.  So this is preventing me from
going any further with it so far.

I was thinking about this some more, and a possible workaround for Lucid
would be to just go with 0.11.1 but patch the exec.c file to include the
madvise() call.  I think this is what Fedora did for Fedora 12.  Of
course, that doesn't really resolve the issue of getting the new version
working, which would be far preferable, and will need to be done
eventually, but it gives us a fallback position that allows KSM support
for Lucid in the event the 0.12.1.1 integration can't happen in time for
Lucid.  I did download the 0.11.1 sources off the upstream site and
patched the exec.c with the madvise() call by hand, and it does indeed
work.

I'm including a patch for the change I made to the 0.11.1 sources just
in case it's useful to you at all.

Also, depending on how much work has already been done on 0.12.1.1, I
thought I'd mention that 0.12.1.2 was released on 2009-12-30.  I don't
see any dramatic changes but I thought I'd mention it in case anything
is in there that might matter.


** Attachment added: "KSM support patch for KVM 0.11.1 sources"
   http://launchpadlibrarian.net/37373426/ksm-patch-0.11.1.diff

-- 
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
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 507473] [NEW] evolution crashed with SIGSEGV in g_strsplit()

[Brian Knoll]

Public bug reported:

Binary package hint: evolution

Evolution suddenly exited.  No interactive activity was being performed
by the user at the time.

ProblemType: Crash
Architecture: amd64
Date: Thu Jan 14 08:30:24 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.28.2-1ubuntu3
ProcCmdline: evolution
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-server
SegvAnalysis:
 Segfault happened at: 0x7f32a3478aa0 : mov(%rdx),%rsi
 PC (0x7f32a3478aa0) ok
 source "(%rdx)" (0x73707061) not located in a known VMA region (needed 
readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_strsplit () from /lib/libglib-2.0.so.0
 gconf_listeners_add () from /usr/lib/libgconf-2.so.4
 e_source_list_new_for_gconf ()
 e_book_get_addressbooks ()
 ?? () from /usr/lib/libedataserverui-1.2.so.8
Tags: lucid
Title: evolution crashed with SIGSEGV in g_strsplit()
Uname: Linux 2.6.32-10-server x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2244): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (gnome-settings-daemon:2244): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (polkit-gnome-authentication-agent-1:2323): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed

** Affects: evolution (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash lucid

-- 
evolution crashed with SIGSEGV in g_strsplit()
https://bugs.launchpad.net/bugs/507473
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 507473] Re: evolution crashed with SIGSEGV in g_strsplit()

[Brian Knoll]

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/37883563/Dependencies.txt

** Attachment added: "Disassembly.txt"
   http://launchpadlibrarian.net/37883564/Disassembly.txt

** Attachment added: "ProcMaps.txt"
   http://launchpadlibrarian.net/37883565/ProcMaps.txt

** Attachment added: "ProcStatus.txt"
   http://launchpadlibrarian.net/37883566/ProcStatus.txt

** Attachment added: "Registers.txt"
   http://launchpadlibrarian.net/37883567/Registers.txt

** Attachment added: "Stacktrace.txt"
   http://launchpadlibrarian.net/37883568/Stacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   http://launchpadlibrarian.net/37883569/ThreadStacktrace.txt

-- 
evolution crashed with SIGSEGV in g_strsplit()
https://bugs.launchpad.net/bugs/507473
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 500272] [NEW] qemu-kvm 0.12.1.1 needed (KSM not available in current 0.11 version)

[Brian Knoll]

Public bug reported:

Binary package hint: qemu-kvm

KSM is supported by the current Lucid kernel.  However, the current
version of the qemu-kvm package, 0.11, does not support KSM.  Therefore,
memory usage will be suboptimal, as this key feature is disabled for KVM
VM guests unless a high enough version of the qemu-kvm package is used.

Since this is an LTS release, I strongly recommend resolving this issue,
as virtualization features such as KSM are crucial for many users, and
failure to get this into the LTS release means LTS users will probably
have to wait another two years, or build things themselves (outside of
the shipped packages).

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: deduplication ksm kvm qemu-kvm virtualization vm

** Changed in: qemu-kvm (Ubuntu)
   Status: New => Confirmed

-- 
qemu-kvm 0.12.1.1 needed (KSM not available in current 0.11 version)
https://bugs.launchpad.net/bugs/500272
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 500272] Re: qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)

[Brian Knoll]

** Summary changed:

- qemu-kvm 0.12.1.1 needed (KSM not available in current 0.11 version)
+ qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)

-- 
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
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 500272] Re: qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)

[Brian Knoll]

** Summary changed:

- qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)
+ qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)

** Description changed:

  Binary package hint: qemu-kvm
  
- KSM is supported by the current Lucid kernel.  However, the current
- version of the qemu-kvm package, 0.11, does not support KSM.  Therefore,
- memory usage will be suboptimal, as this key feature is disabled for KVM
- VM guests unless a high enough version of the qemu-kvm package is used.
+ KSM is supported by the current Ubuntu Lucid kernel.  However, the
+ current version of the qemu-kvm package, 0.11, does not support KSM.
+ Therefore, memory usage will be suboptimal, as this key feature is
+ disabled for KVM VM guests unless a high enough version of the qemu-kvm
+ package is used.
  
  Since this is an LTS release, I strongly recommend resolving this issue,
  as virtualization features such as KSM are crucial for many users, and
  failure to get this into the LTS release means LTS users will probably
  have to wait another two years, or build things themselves (outside of
  the shipped packages).

** Description changed:

  Binary package hint: qemu-kvm
  
- KSM is supported by the current Ubuntu Lucid kernel.  However, the
+ KSM is supported by the current Ubuntu 10.04 Lucid kernel.  However, the
  current version of the qemu-kvm package, 0.11, does not support KSM.
  Therefore, memory usage will be suboptimal, as this key feature is
  disabled for KVM VM guests unless a high enough version of the qemu-kvm
  package is used.
  
  Since this is an LTS release, I strongly recommend resolving this issue,
  as virtualization features such as KSM are crucial for many users, and
  failure to get this into the LTS release means LTS users will probably
  have to wait another two years, or build things themselves (outside of
  the shipped packages).

** Also affects: qemu
   Importance: Undecided
   Status: New

-- 
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
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 500887] Re: Synaptics Button Press Disables Synaptics Function Until Reboot

[Brian Knoll]

** Visibility changed to: Public

** This bug is no longer flagged as a security vulnerability

** Changed in: ubuntu
   Status: New => Confirmed

-- 
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
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 1683205] Re: light-locker in combination with libpam-krb5 creates incorrectly-named Kerberos credential caches

[Brian Knoll]

I just wanted to add a quick note that this is Ubuntu 16.04 where I am
seeing this, although the problem has existed for some time now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683205

Title:
  light-locker in combination with libpam-krb5 creates incorrectly-named
  Kerberos credential caches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1683205/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683205] [NEW] light-locker in combination with libpam-krb5 creates incorrectly-named Kerberos credential caches

[Brian Knoll]

Public bug reported:

When logging into a system locked with light-locker by logging in via
libpam-krb5 for Kerberos authentication, the credential cache is created
with an incorrect name for the user.

The credential cache is always created as krb5cc_0 under these
conditions, when the last part (the numeric part) should be the user ID
of the user logging in.  For instance, if the user's user ID is 1000,
the file should be named krb5cc_1000, not krb5cc_0.  The XScreensaver
command handles this correctly under the exact same conditions, but
light-locker, unfortunately, does not.

Please let me know how I can help.

Thank you,
Brian Knoll

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: light-locker 1.7.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Apr 16 20:01:08 2017
InstallationDate: Installed on 2017-03-11 (36 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: light-locker
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: light-locker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683205

Title:
  light-locker in combination with libpam-krb5 creates incorrectly-named
  Kerberos credential caches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1683205/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1309919] Re: Xorg causing 100% cpu load

[Brian Knoll]

Just a note that I am seeing this problem as well, here on an AMD 8350
8-core system using Trusty 14.04 AMD64.  The Xorg process takes about
20%-35% of one core, when the system is otherwise idle.  I'm open to
suggestions regarding how I can dig deeper to determine the cause,
because obviously killing the Xorg process isn't an option (or I
wouldn't be running it in the first place).  As an experiment, to see if
it would help to restart X, I did try killing the process then logging
back in with the new Xorg process, but the CPU usage was the same as it
was before.

Any suggestions are welcome, and I am willing to help debug this.

Thanks,
Brian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309919

Title:
  Xorg causing 100% cpu load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1309919/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1309919] Re: Xorg causing 100% cpu load

[Brian Knoll]

Bug report was withdrawn by the original user, and over here it was a
driver issue, so I am marking this ticket invalid.


** Changed in: xorg (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309919

Title:
  Xorg causing 100% cpu load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1309919/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1296276] Re: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5

[Brian Knoll]

To move this along, I've built a VM I can test this fix on, but to speed
things up, is there a PPA I can use?  I don't mind building it but I am
concerned about building it differently than the official build, so if
there is a PPA I can use I will gladly install this onto my VM and I can
tell you fairly quickly whether it solves the problem or not, so we can
get this into final if possible.

Thanks for all the help,
Brian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296276

Title:
  Unlocking with greeter fails to properly renew kerberos tickets with
  pam-krb5

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1296276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1558576] [NEW] OpenSSH Error "Disconnecting: Hash's MIC didn't verify" after upgrading to Ubuntu 16.04

[Brian Knoll]

Public bug reported:

SSH was working fine for years, until I upgraded to Ubuntu 16.04.  When
I upgraded to Ubuntu 16.04, the openssh-server stopped accepting
connections from Ubuntu 14.04 LTS clients, with the following error:


Disconnecting: Hash's MIC didn't verify


The error above shows up on the client side.  In the server logs, I see
the following:


Mar 17 10:01:49 falcon polkitd(authority=local): Unregistered Authentication 
Agent for unix-process:125110:294284 (system bus name :1.133, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
Mar 17 10:02:06 falcon sshd[125126]: error: Received disconnect from 
MY.IP.ADDRESS.HERE port PORTNUMBER:2: Hash's MIC didn't verify [preauth]
Mar 17 10:02:06 falcon sshd[125126]: Disconnected from MY.IP.ADDRESS.HERE port 
PORTNUMBER [preauth]


I am using GSSAPI Key Exchange, and GSSAPI authentication.  So I am not
using public keys or passwords or anything like that; everything is
entirely Kerberos 5.  The problem, also, is only one-way.  In other
words, if I upgrade the server to Ubuntu 16.04, it stops accepting
connections from 14.04 clients, but if I go the other direction and
upgrade the client to Ubuntu 16.04, then it can still authenticate
successfully to an Ubuntu 14.04 machine.

I am more than happy to help debug this, so please let me know what you
suggest and I'll do whatever I can to help.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Thu Mar 17 10:02:45 2016
InstallationDate: Installed on 2015-05-04 (317 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openssh
UpgradeStatus: Upgraded to xenial on 2016-03-16 (0 days ago)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558576

Title:
  OpenSSH Error "Disconnecting: Hash's MIC didn't verify" after
  upgrading to Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1558576/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1558565] Re: Unprivileged system LXC containers refuse to start after upgrade to Ubuntu 16.04

[Brian Knoll]

It did, indeed, have an autodev script configured:

---
# Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template:
# For additional config options, please look at lxc.container.conf(5)

# Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
lxc.arch = x86_64

# Container specific configuration
lxc.rootfs = /var/lib/lxc/boinc/rootfs
lxc.utsname = boinc

# Network configuration
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = 00:16:3e:76:25:82

lxc.cgroup.memory.limit_in_bytes = 2G
lxc.start.auto = 1
lxc.hook.autodev=/var/lib/lxc/boinc/autodev
---

I have removed that line, and it now starts up perfectly well.  I'm not
clear now whether the autodev script was never there, and it just wasn't
noticed before to cause an error, or whether it disappeared in the
upgrade to 16.04, but either way the container starts now so I'm happy.
I'll leave the ticket open for now in case either of you want any more
information to help track down any possible issue, but if you want me to
close it I'm happy to do so.

Thanks,
Brian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558565

Title:
  Unprivileged system LXC containers refuse to start after upgrade to
  Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1558565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1558565] [NEW] Unprivileged system LXC containers refuse to start after upgrade to Ubuntu 16.04

[Brian Knoll]

Public bug reported:

System was previously running Ubuntu 14.04 LTS 64-bit and Linux
containers worked very well.  Linux containers are unprivileged
containers started by the system using dedicated UID and GID mapped
ranges, not userns containers.

Upon upgrade-in-place to 16.04 LTS using "do-release-upgrade -d", the
LXC containers will no longer start.  I see the following in the logs:

  lxc-start 20160317093843.710 ERRORlxc_utils - 
utils.c:open_without_symlink:1625 - No such file or directory - Error examining 
efi in /usr/lib/x86_64-linux-gnu/lxc/sys/firmware/efi/efivars
  lxc-start 20160317093843.727 ERRORlxc_conf - conf.c:run_buffer:347 - 
Script exited with status 127
  lxc-start 20160317093843.727 ERRORlxc_conf - conf.c:lxc_setup:3753 - 
failed to run autodev hooks for container 'boinc'.
  lxc-start 20160317093843.727 ERRORlxc_start - start.c:do_start:793 - 
failed to setup the container
  lxc-start 20160317093843.727 ERRORlxc_sync - sync.c:__sync_wait:51 - 
invalid sequence number 1. expected 2
  lxc-start 20160317093843.727 ERRORlxc_start - 
start.c:__lxc_start:1286 - failed to spawn 'boinc'
  lxc-start 20160317093849.276 ERRORlxc_start_ui - lxc_start.c:main:344 
- The container failed to start.
  lxc-start 20160317093849.276 ERRORlxc_start_ui - lxc_start.c:main:346 
- To get more details, run the container in foreground mode.
  lxc-start 20160317093849.276 ERRORlxc_start_ui - lxc_start.c:main:348 
- Additional information can be obtained by setting the --logfile and 
--logpriority options.

I did try converting to unprivileged containers to see if it would help
(which is the state the system is in now), but it did not help.

I'm more than happy to work with you to help debug this, so please let
me know how I can help.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc2 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Thu Mar 17 09:46:14 2016
InstallationDate: Installed on 2015-05-04 (317 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxd
UpgradeStatus: Upgraded to xenial on 2016-03-16 (0 days ago)

** Affects: lxd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558565

Title:
  Unprivileged system LXC containers refuse to start after upgrade to
  Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1558565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1559618] [NEW] light-locker appears to incorrectly handle Kerberos ticket cache filenames

[Brian Knoll]

Public bug reported:

When unlocking an Ubuntu 16.04 system which is using light-locker as the
screen saver, Kerberos authentication works for a normal, unprivileged
user, except that the resulting ticket cache is incorrectly named.
Instead of the resulting ticket cache created as a result of such
successful authentication being named something like:

krb5cc_1000 (if the UID of the user is 1000)

...the cache file is named:

krb5cc_0 (which would presumably be correct if root were logging in, but
not a normal, unprivileged user)

I am willing to help debug this issue, so if there is anything you would
like me to try, please let me know.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: light-locker 1.7.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sat Mar 19 22:32:52 2016
InstallationDate: Installed on 2016-03-19 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: light-locker
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: light-locker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559618

Title:
  light-locker appears to incorrectly handle Kerberos ticket cache
  filenames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1559618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1559618] Re: light-locker appears to incorrectly handle Kerberos ticket cache filenames

[Brian Knoll]

I should also add, for clarification to anyone possibly unfamiliar with
Kerberos and, therefore, the impact of this bug, that the result of this
bug is that the incorrectly-named ticket cache is not visible to
applications searching for the ticket cache for the user, so the user
cannot (without taking unusual measures) use the resulting ticket cache.
The ticket cache is correctly owned by the user, but the ticket cache is
not found because the filename is incorrect.  As a result, the user
would normally need to acquire new Kerberos tickets post-login, which
would be unnecessary if this issue were corrected.

I will also add that using "xscreensaver" instead of light-locker is a
workaround, but of course results in perhaps a less-consistent
experience for the user.

Thanks,
Brian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559618

Title:
  light-locker appears to incorrectly handle Kerberos ticket cache
  filenames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1559618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1559801] [NEW] OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

[Brian Knoll]

Public bug reported:

OpenSSH server GSSAPI authentication appears to be broken in Ubuntu
16.04 Xenial.  Ticket #1558576 details some other issues regarding
breakage in Ubuntu 16.04 pertaining to OpenSSH, but this ticket is
specifically for the fact that GSSAPI authentication is no longer
working, on the server side, in Xenial 16.04.  By "on the server side",
I mean that the client works fine and can connect using GSSAPI
authentication (key exchange or not) with  another machine, but if a
Xenial server is configured to allow GSSAPI authentication, it does not
function any more.  This functionality worked fine in Trusty 14.04.  In
16.04, if both the server and the client are configured to allow GSSAPI
authentication, the method always fails and OpenSSH continues to fall
through to the next authentication in the list.

I am willing to help debug this, so please let me know how I can help.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sun Mar 20 21:11:56 2016
InstallationDate: Installed on 2016-03-20 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559801

Title:
  OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1559801] Re: OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

[Brian Knoll]

I think it is important to realize that this bug causes Ubuntu 16.04 to
be unusable in many high security environments, since the stock SSH
installation does not function with GSSAPI and the installation of a
non-vendor-supported SSH will be unacceptable by policy in many of those
same environments.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559801

Title:
  OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1558576] Re: OpenSSH Error "Disconnecting: Hash's MIC didn't verify" after upgrading to Ubuntu 16.04

[Brian Knoll]

Based on the upstream bug closure, it sounds like importing the fixed
version from upstream (or at least the fix patch) is probably the
solution here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558576

Title:
  OpenSSH Error "Disconnecting: Hash's MIC didn't verify" after
  upgrading to Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1558576/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1559801] Re: OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

[Brian Knoll]

On a fully-updated system, as of today, I am no longer seeing this
issue.  Therefore, I am closing this ticket.


** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+attachment/4606074/+files/Dependencies.txt

** Attachment removed: "SSHDConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+attachment/4606076/+files/SSHDConfig.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+attachment/4606075/+files/JournalErrors.txt

** Changed in: openssh (Ubuntu)
   Status: New => Invalid

** Information type changed from Public to Private

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559801

Title:
  OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1561260] [NEW] xfce4-volumed causes volume popups frequently in XFCE

[Brian Knoll]

Public bug reported:

I was having problems with frequent volume change popups in my XFCE
desktop.  This was happening with Trusty 14.04 as well, and it is still
happening in 16.04 Xenial.  I killed the xfce4-volumed process, and
disabled the autostart.  Now I still see the volume control flash
briefly every few seconds, if I watch it closely, but at least there is
no large volume popup every few seconds.

Ideally, we could somehow figure out what is actually causing this
problem and solve it, so the xfce4-volumed could be re-enabled, as it is
a nice feature when it is working properly.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xfce4-volumed 0.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Wed Mar 23 20:21:37 2016
InstallationDate: Installed on 2016-03-22 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xfce4-volumed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xfce4-volumed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561260

Title:
  xfce4-volumed causes volume popups frequently in XFCE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1561260/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1561801] Re: Video cannot be restored after power save on AMDGPU

[Brian Knoll]

I should also add that I've tried disabling all of my power management
in my window manager settings, but the problem still occurs; that may or
may not be a bug in the window manager power management, but the net
effect appears to be that it is requesting the driver to cut the power
to the monitor, regardless, and then of course we end up with the same
problem we had before, which is that the video cannot come back without
a restart of the X server.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561801

Title:
  Video cannot be restored after power save on AMDGPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1561801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1561801] [NEW] Video cannot be restored after power save on AMDGPU

[Brian Knoll]

Public bug reported:

When I engage light-locker to lock my screen, it locks the screen and
disables power to the monitor, as it should.  However, I can never get
video back again after that.  Power to the monitor is never restored,
and the only way I can get my video back at that point is to restart my
display manager, for instance by SSHing in from another machine.  At
that point, the video comes back and I can use the system again.

This problem only happens on my AMDGPU-based Radeon system.  I have
another system that uses Intel video that doesn't have this problem.  I
should note, though, that in Trusty 14.04 the power save and restore
functions worked perfectly fine, and there was no issue restoring video
when I wanted the system to wake up the video.  But of course, at that
point I was using FGLRX as my video driver, which is no longer supported
or available in 16.04.

I'm very willing to help debug this, so if there is anything I can do to
help, please let me know.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-video-amdgpu 1.0.1-1build2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Thu Mar 24 20:43:48 2016
InstallationDate: Installed on 2016-03-22 (2 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-amdgpu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xserver-xorg-video-amdgpu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561801

Title:
  Video cannot be restored after power save on AMDGPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1561801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1561260] Re: xfce4-volumed causes volume popups frequently in XFCE

[Brian Knoll]

** Changed in: xfce4-volumed (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561260

Title:
  xfce4-volumed causes volume popups frequently in XFCE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1561260/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 812874] Re: package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade: EOF on stdin at conffile prompt

[Brian Knoll]

Lucid is end-of-life.  Closing ticket.


** Changed in: base-files (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812874

Title:
  package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade:
  EOF on stdin at conffile prompt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/812874/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 937040] Re: Duplicate ufw rules installed by dovecot packages

[Brian Knoll]

I am seeing this here as well.  After seeing the comment by Serge above,
I took a look at this.  Here is what I did, and I propose that anyone
who is experiencing this problem should probably do the same:

rm /etc/ufw/applications.d/dovecot-common

The reason is that you already have these rules in the dovecot-core
file, so you are simply eliminating the old duplicate by doing this.  I
suspect that in my case this arose because the machine in question was
upgraded from a Lucid installation to Precise, so would have had an
older package in place from before.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937040

Title:
  Duplicate ufw rules installed by dovecot packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/937040/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1481536] [NEW] cryptsetup unknown fs type or options error decrypting LUKS volume at boot

[Brian Knoll]

Public bug reported:

Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace
cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I
have been receiving an error message at boot time after entering my
passphrase to unlock the LUKS partition.  I noticed that at the same
time the verbiage of the prompt to enter the passphrase also changed, to
something like "Please unlock ", which is a little different
than before, so I'm guessing something in this change may have caused
the error message.  Interestingly, the error message does not impede
successful system boot, so my suspicion is that the error is maybe not
real, but just being incorrectly displayed.  In other words, if I
successfully enter the passphrase, this error will appear but the system
will then proceed to boot successfully and have the encrypted volume
successfully mounted.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug  4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard

** Affects: cryptsetup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536

Title:
  cryptsetup unknown fs type or options error decrypting LUKS volume at
  boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1481539] [NEW] X freezes when screen enters sleep mode

[Brian Knoll]

Public bug reported:

When the system enters sleep mode, Xorg appears to freeze.  When the
system wakes back up, there is just a black screen.  There is no
apparent way to get the system back once this happens.  Interestingly,
the system does not appear to be completely frozen, in that it is still
possible to SSH into the machine in this state.  However, the local
console is completely unusable.  Note that this is on a very new Intel
Broadwell-U notebook using integrated video.

I am running Ubuntu 15.10 Wily x86-64.  My Xorg version is:
1:7.7+7ubuntu4.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug  4 21:03:56 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481539

Title:
  X freezes when screen enters sleep mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1481539/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1481536] Re: "cryptsetup: unknown fstype, bad password or options?" error decrypting LUKS volume at boot

[Brian Knoll]

** Summary changed:

- cryptsetup unknown fs type or options error decrypting LUKS volume at boot
+ "cryptsetup: unknown fstype, bad password or options?" error decrypting LUKS 
volume at boot

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536

Title:
  "cryptsetup: unknown fstype, bad password or options?" error unlocking
  / decrypting LUKS volume at boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1481536] Re: "cryptsetup: unknown fstype, bad password or options?" error unlocking / decrypting LUKS volume at boot

[Brian Knoll]

** Summary changed:

- "cryptsetup: unknown fstype, bad password or options?" error decrypting LUKS 
volume at boot
+ "cryptsetup: unknown fstype, bad password or options?" error unlocking / 
decrypting LUKS volume at boot

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536

Title:
  "cryptsetup: unknown fstype, bad password or options?" error unlocking
  / decrypting LUKS volume at boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1468539] Re: DMAR Fault on Intel Wireless 7265 (iwlwifi) when Linux "intel_iommu=on" Kernel Boot Parameter Is used on Asus UX303LNB.206

[Brian Knoll]

Just a quick note that this problem still exists in Ubuntu 15.10 Wily.
As with the original reporter, if I turn off IOMMU support, the problem
does not occur.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468539

Title:
  DMAR Fault on Intel Wireless 7265 (iwlwifi) when Linux
  "intel_iommu=on" Kernel Boot Parameter Is used on Asus UX303LNB.206

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i915/+bug/1468539/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 981290] [NEW] Canon MX870 Printer Always Busy on Precise 12.04 64-Bit

[Brian Knoll]

Public bug reported:

The Canon MX870 printer is connected via either wireless or wired
ethernet.  It worked fine in Ubuntu 10.04 64-bit if one followed
workarounds available on various sites which basically involve
downloading Canon drivers from Canon, forcing the architecture on the
Canon drivers, then installing them.

In 12.04 this looks like it should no longer be required, since in 12.04
the MX870 is supposedly supported in Gutenprint and does show up in the
list of supported printers in CUPS.  It is possible to add the MX870
and, for example, set it as the default printer and query status.
However, looking at the cups error_log reveals something very wrong:

W [13/Apr/2012:20:24:26 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:24:31 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:24:41 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:24:56 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:25:16 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:25:41 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:26:11 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:26:41 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:27:11 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:27:41 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:28:11 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:28:41 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:29:11 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:29:41 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:30:11 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:30:41 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:31:11 -0400] [Job 3] The printer is busy.
W [13/Apr/2012:20:31:41 -0400] [Job 3] The printer is busy.

Further, printing to the device of course does not work, since the
printer is never available.  I have installed the ia32-multiarch
libraries since I know that Canon only ships 32-bit drivers, but that
did not help.  I am very open to suggestions.

This is a fresh install of 12.04 64-bit.  The mention above of forcing
the drivers into 10.04 was for a previous install, but this is a
completely fresh Ubuntu 12.04 64-bit installation.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cups 1.5.2-9ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 13 20:25:54 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120411)
Lpstat: device for mfc: socket://mfc.localnet:9100
MachineType: eMachines eMachines E525
Papersize: letter
PpdFiles: mfc: Canon PIXMA MX870 - CUPS+Gutenprint v5.2.8-pre1
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic 
root=/dev/mapper/sda2_crypt ro nomodeset quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2009
dmi.bios.vendor: eMachines
dmi.bios.version: V3.03
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: eMachines E525
dmi.board.vendor: eMachines
dmi.board.version: V3.03
dmi.chassis.type: 10
dmi.chassis.vendor: eMachines
dmi.chassis.version: V3.03
dmi.modalias: 
dmi:bvneMachines:bvrV3.03:bd11/30/2009:svneMachines:pneMachinesE525:pvrV3.03:rvneMachines:rneMachinesE525:rvrV3.03:cvneMachines:ct10:cvrV3.03:
dmi.product.name: eMachines E525
dmi.product.version: V3.03
dmi.sys.vendor: eMachines

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981290

Title:
  Canon MX870 Printer Always Busy on Precise 12.04 64-Bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/981290/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 981290] Re: Canon MX870 Printer Always Busy on Precise 12.04 64-Bit

[Brian Knoll]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981290

Title:
  Canon MX870 Printer Always Busy on Precise 12.04 64-Bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/981290/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 981290] Re: Canon MX870 Printer Always Busy on Precise 12.04 64-Bit

[Brian Knoll]

I am not sure this is the same bug as that mentioned in comment #2.  For
example, after finding that my Canon MX870 would not function under
Ubuntu 12.04 64-bit, I purchased a cheap HP printer that uses the hplip
driver, and that works fine.  I would like to have this Canon function,
however, so I am still searching for a solution to this problem.

Note that the Canon printer does not use the hplip driver mentioned in
comment #2.  To get it to work under Ubuntu 10.04 64-bit I had to force-
install the drivers downloaded from the Canon site.  Even that does not
work now, however, primarily due to the standard library changes
introduced since then.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981290

Title:
  Canon MX870 Printer Always Busy on Precise 12.04 64-Bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/981290/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 985727] [NEW] krb5-admin-server falsely claiming clock skew errors

[Brian Knoll]

Public bug reported:

I installed a Kerberos KDC and Admin Server onto an Ubuntu 12.04 64-bit
VM.  I created a test realm, and added principals.

When I kinit, it works, and I get a ticket back.  However, when I try to
use kadmin, kadmin is extremely slow to respond, then eventually gives
an "unspecified GSS failure: clock skew too great" error.  This occurs
even when I am simply using kadmin to connect to the same machine I am
on.  In other words, I can use it to connect to localhost, meaning the
clocks would be identical, yet I still get this error.

This does not happen when the guest VM onto which I install the KDC is
an Ubuntu 10.04 VM.  However, installing onto 12.04 causes this failure.

The clock is synchronized since it is a VM, so that is not the problem.
However, as I said, this occurs even if I connect from the KDC to the
KDC using kadmin.  Of course, kadmin.local works just fine, but I would
rather not have to rely on that for management of my Kerberos realms,
especially since it worked in 10.04.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: krb5-admin-server 1.10+dfsg~beta1-2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
Date: Thu Apr 19 12:02:53 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327.1)
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: krb5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: krb5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985727

Title:
  krb5-admin-server falsely claiming clock skew errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/985727/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 985727] Re: krb5-admin-server falsely claiming clock skew errors

[Brian Knoll]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985727

Title:
  krb5-admin-server falsely claiming clock skew errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/985727/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 985727] Re: krb5-admin-server falsely claiming clock skew errors

[Brian Knoll]

I haven't experienced this issue in a long time, so I'm just changing
this ticket to "invalid" status to cancel it.


** Changed in: krb5 (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985727

Title:
  krb5-admin-server falsely claiming clock skew errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/985727/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1296276] Re: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5

[Brian Knoll]

I just noticed what appears to be another problem:

-rw--- 1 myuser mygroup  504 May 12 21:21 krb5cc_0
-rw--- 1 myuser mygroup  504 May 12 21:16 krb5cc_1000_a8bk3j

While lightdm is renewing the tickets now when unlocking the screen
saver, and the ownership of the ticket is correct, the filename still
appears to be incorrect.  Specifically, the filename appears to be
constructed using the user number of the lightdm process, rather than
the user number of the user authenticating to the screen saver.  The
resut is that the ticket is created and stored on disk, accessible to
the user but not used unless the user explicitly uses the ticket because
the filename does not conform to what is expected.  In this instance,
for example, both of these tickets were created by my normal user
instance.  The one ending in "0" is the ticket created when I unlocked
the light-locker screen saver.

Thanks to all involved for all of the excellent work so far, but it does
look like there is still a little more to do here.

Thanks,
Brian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296276

Title:
  Unlocking with greeter fails to properly renew kerberos tickets with
  pam-krb5

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1296276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1296276] Re: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5

[Brian Knoll]

I set the status back to "new" because that sounded correct given that
there is potentially additional work to be evaluated here, but if that's
not the right thing to do please let me know for future reference when
working with Launchpad tickets.  I would normally just file a new
ticket, but in this case this is still kind of the same work we're
discussing.


Again, thanks very much to all involved for all the excellent support thus far.


** Changed in: lightdm
   Status: Fix Released => New

** Changed in: lightdm/1.10
   Status: Fix Released => New

** Changed in: lightdm (Ubuntu)
   Status: Fix Released => New

** Changed in: lightdm (Ubuntu Trusty)
   Status: Fix Released => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296276

Title:
  Unlocking with greeter fails to properly renew kerberos tickets with
  pam-krb5

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1296276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1275380] Re: Cryptsetup still using SHA-1 as default hash for Debian Installer

[Brian Knoll]

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1275380/+attachment/3965869/+files/Dependencies.txt

** Attachment removed: "fstab.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1275380/+attachment/3965870/+files/fstab.txt

** Changed in: cryptsetup (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275380

Title:
  Cryptsetup still using SHA-1 as default hash for Debian Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1275380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1296276] Re: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5

[Brian Knoll]

I applied this to a VM to test, and it does indeed appear to do the
right thing.  I can confirm that this code does seem to have the
intended effect.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296276

Title:
  Unlocking with greeter fails to properly renew kerberos tickets with
  pam-krb5

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1296276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1275380] [NEW] Cryptsetup still using SHA-1 as default hash for Debian Installer

[Brian Knoll]

Public bug reported:

The SHA-1 hash has been, for years now, considered undesirable for new
installations.  In Trusty, a new install using LUKS results in an
installation using SHA-1 hashing, as can be demonstrated by using the
following command:

cryptsetup luksDump 

Please consider compiling the "cryptsetup" package to use a stronger
default hash, perhaps SHA-256 or even SHA-512.

I think the option "--with-luks1-hash=sha256", for instance, should give
us a SHA-256 default hash, which would be significantly more secure than
our current default in Ubuntu.

Thank you,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cryptsetup 2:1.6.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Feb  1 21:04:28 2014
InstallationDate: Installed on 2014-02-01 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: vda5_crypt UUID=d2509a89-e711-4419-93e2-37a71941d6b8 none luks

** Affects: cryptsetup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275380

Title:
  Cryptsetup still using SHA-1 as default hash for Debian Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1275380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1275380] Re: Cryptsetup still using SHA-1 as default hash for Debian Installer

[Brian Knoll]

I just want to add that an even better option, long-term, would probably
be to push back to upstream the idea that the installer should be
modified to present the user installing the system with the choice of
hash to be used.  However, this does not change the fact that the
default hash should be changed to something significantly stronger than
SHA-1, probably something from the SHA-2 family such as SHA-256 or
SHA-512, as mentioned in this ticket.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275380

Title:
  Cryptsetup still using SHA-1 as default hash for Debian Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1275380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1296276] [NEW] light-locker fails to properly renew kerberos tickets with pam-krb5

[Brian Knoll]

Public bug reported:

I am using the pam-krb5 module to log into a Kerberos realm using
lightdm.  This works the initial time I log in, when I come in through
lightdm.  However, once I am logged in, and I lock the screen using
light-locker, when I unlock the screen I no longer get renewed tickets.

The problem seems to be this:

-rw--- 1 me   me 504 Mar 23 08:37 krb5cc_1000_sjkfhagfg
-rw--- 1 root   root504 Mar 23 08:38 krb5cc_pam_lsdkjhfsdk

So what is happening is that on the initial login, I get a valid ticket
cache, owned by my logging-in user, and showing my UID in the file name.
This ticket works fine.  However, once I lock the screen and then unlock
it, I get a ticket cache owned by root, with "_pam_" in the filename,
and of course I can't use it because I am not logged in as root.

This problem did not occur in 12.04 LTS, probably because it did not use
light-locker.  The pam-krb5 module works in all other cases in my
installations, so I do not believe this is any kind of problem with the
pam_krb5 module.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: light-locker 1.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Sun Mar 23 08:40:38 2014
InstallationDate: Installed on 2014-03-22 (0 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20140320)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: light-locker
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: light-locker (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/1296276

Title:
  light-locker fails to properly renew kerberos tickets with pam-krb5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1296276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1296276] Re: light-locker fails to properly renew kerberos tickets with pam-krb5

[Brian Knoll]

Just a comment that I think this should probably have a fairly high
priority, as it severely affects the user experience for anyone using
Kerberos to authenticate via the libpam-krb5 module against Kerberos or
Active Directory, which I expect is a fairly large number of people.

Please let me know what I can do to help, and I will be glad to test
things.

Thanks,
Brian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296276

Title:
  light-locker fails to properly renew kerberos tickets with pam-krb5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1296276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1296276] [NEW] light-locker fails to properly renew kerberos tickets with pam-krb5

[Brian Knoll]

Thank you, Russ, for the insightful explanation of what is happening
here.  I can definitely confirm that xscreensaver does indeed work on my
system, as that is what I am using as a workaround to this issue.  It
isn't as "polished" as using the lightdm screen saver would be, but it
certainly works better as far as the PAM integration is concerned.  So a
couple of things come to mind given all that we know so far:

1. The workaround is to use xscreensaver instead, although that is not
something all users will be able to handle, especially given the lack of
polish and the fact that some additional configuration in the X
environment is required to get that to work.  But it does indeed work,
as I'm using it over here.

2. Probably more importantly, the PAM handling in light-locker appears
to be very broken.  This will probably affect other modules besides pam-
krb5, and is a significant issue.




On Sunday, March 23, 2014 1:40 PM, Russ Allbery  wrote:
 
Launchpad Bug Tracker <1296...@bugs.launchpad.net> writes:

> So what is happening is that on the initial login, I get a valid ticket
> cache, owned by my logging-in user, and showing my UID in the file name.
> This ticket works fine.  However, once I lock the screen and then unlock
> it, I get a ticket cache owned by root, with "_pam_" in the filename,
> and of course I can't use it because I am not logged in as root.

The _pam_ ticket cache is created during the authenticate step of the PAM
interaction, and is then written to the user's actual ticket cache during
either setcred or open_session.  (setcred is the appropriate thing for a
screen saver to call.)  It's deleted on pam_end.

This sounds like a screen saver that isn't using PAM properly.  It looks
like it's starting a PAM interaction and then only calling authenticate,
never calling setcred, and never ending the PAM interaction, so it leaks a
root-owned ticket cache and never renews your cache.

There used to be widespread problems of this sort due to the number of
people writing screen savers who didn't really understand how PAM worked,
but I thought most of them had been fixed.

You can confirm that it's a problem with this program rather than with
your system configuration by running xscreensaver, locking the screen,
unlocking with your Kerberos password, and seeing if that properly
refreshes your credentials.  I know that xscreensaver does PAM properly.

-- 
Russ Allbery (r...@debian.org)               

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1296276

Title:
  light-locker fails to properly renew kerberos tickets with pam-krb5

Status in “light-locker” package in Ubuntu:
  New
Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I am using the pam-krb5 module to log into a Kerberos realm using
  lightdm.  This works the initial time I log in, when I come in through
  lightdm.  However, once I am logged in, and I lock the screen using
  light-locker, when I unlock the screen I no longer get renewed
  tickets.

  The problem seems to be this:

  -rw--- 1 me       me     504 Mar 23 08:37 krb5cc_1000_sjkfhagfg
  -rw--- 1 root   root    504 Mar 23 08:38 krb5cc_pam_lsdkjhfsdk

  So what is happening is that on the initial login, I get a valid
  ticket cache, owned by my logging-in user, and showing my UID in the
  file name.  This ticket works fine.  However, once I lock the screen
  and then unlock it, I get a ticket cache owned by root, with "_pam_"
  in the filename, and of course I can't use it because I am not logged
  in as root.

  This problem did not occur in 12.04 LTS, probably because it did not
  use light-locker.  The pam-krb5 module works in all other cases in my
  installations, so I do not believe this is any kind of problem with
  the pam_krb5 module.

  Thanks,
  Brian

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Sun Mar 23 08:40:38 2014
  InstallationDate: Installed on 2014-03-22 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20140320)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1296276/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296276

Title:
  light-locker fails to properly renew kerberos tickets with pam-krb5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1296276/+subscrip

[Bug 914305] Re: [12.04] WARNING: gnome-keyring:: no socket to connect to

[Brian Knoll]

I also want to mention that this appears to be related to upstream
Debian bug #649408, and breaks both network services and applications.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305

Title:
  [12.04] WARNING: gnome-keyring:: no socket to connect to

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/914305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 914305] Re: [12.04] WARNING: gnome-keyring:: no socket to connect to

[Brian Knoll]

I think somebody who has access to do so should raise the priority of
this bug to a higher level.  This bug has been known to break certain
network services, even services which have no apparent legitimate need
to be using gnome-keyring at all.  It would be best if this bug were
fixed prior to the LTS release, as it is quite annoying, and does break
some functionality.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305

Title:
  [12.04] WARNING: gnome-keyring:: no socket to connect to

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/914305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 914305] Re: [12.04] WARNING: gnome-keyring:: no socket to connect to

[Brian Knoll]

I just wanted to add one example of a critical network service which is
broken by this bug, to demonstrate the broken functionality.  CUPS
appears to be broken by this bug.  I cannot print, and when I look in my
CUPS error log I see a bunch of messages about the daemon having
problems connecting to gnome-keyring, which it should not be doing in
the first place.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305

Title:
  [12.04] WARNING: gnome-keyring:: no socket to connect to

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/914305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1154068] [NEW] openafs-modules-dkms 1.6.1-1+ubuntu0.1: openafs kernel module failed to build

[Brian Knoll]

Public bug reported:

This message appeared in X while the system was up and operating.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: openafs-modules-dkms 1.6.1-1+ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
DKMSKernelVersion: 3.2.0-38-generic
Date: Tue Mar 12 08:56:22 2013
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 1.6.1-1+ubuntu0.1
SourcePackage: openafs
Title: openafs-modules-dkms 1.6.1-1+ubuntu0.1: openafs kernel module failed to 
build
UpgradeStatus: Upgraded to precise on 2013-02-22 (17 days ago)

** Affects: openafs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154068

Title:
  openafs-modules-dkms 1.6.1-1+ubuntu0.1: openafs kernel module failed
  to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1154068/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 914305] Re: [12.04] WARNING: gnome-keyring:: no socket to connect to

[Brian Knoll]

I just performed a full update of all packages on my 12.04 installation,
rebooted, and tried again:

-
# lpq
WARNING: gnome-keyring:: no socket to connect to
mfc is ready
no entries
-

So the warning is still there.  This installation was a regular install
with the Gnome 2 desktop environment from Lucid, then I upgraded it to
12.04.  I think now it has Gnome packages installed but it also has the
Unity environment.  It is just a VM I set up for testing the next
release, so I don't ever log into the desktop, I just SSH into it, but
the desktop is there to pick up compatibility issues that might arise,
so I can report bugs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305

Title:
  [12.04] WARNING: gnome-keyring:: no socket to connect to

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/914305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 914305] Re: [12.04] WARNING: gnome-keyring:: no socket to connect to

[Brian Knoll]

I want to mention that the workaround listed in comment #6, involving
commenting out the module, does indeed work over here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305

Title:
  [12.04] WARNING: gnome-keyring:: no socket to connect to

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/914305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 886483] [NEW] Twofish LUKS Support in Alternate Installer

[Brian Knoll]

Public bug reported:

In the Ubuntu Alternate installer, the option for using Twofish appears
to have been removed around the Maverick or, possibly, Natty time frame.
The option to install using LUKS onto Twofish partitions was present in
Lucid, but some time around Maverick or Natty it was removed and now
this option is no longer available when using the alternate installer to
install a LUKS partition.

It would be preferable to have this option back, as Twofish is a very
viable cipher which has very high strength, yet is reasonably fast.  It
is, of course, possible to create Twofish partitions post-install, but
having this feature during the install itself is very useful, especially
for the root partition.  Further, this feature existed in Ubuntu
previously.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cryptsetup 2:1.1.3-4ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Nov  5 05:46:11 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: Upgraded to oneiric on 2011-11-01 (3 days ago)
crypttab:
 sda2_crypt UUID=2fcde4e4-1711-42fe-8612-bb532b6c4bc6 none luks
 sda3_crypt /dev/sda3 /dev/urandom cipher=twofish-cbc-essiv:sha256,size=256,swap

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug oneiric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886483

Title:
  Twofish LUKS Support in Alternate Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/886483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 886483] Re: Twofish LUKS Support in Alternate Installer

[Brian Knoll]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886483

Title:
  Twofish LUKS Support in Alternate Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/886483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 886483] Re: Twofish LUKS Support in Alternate Installer

[Brian Knoll]

Hi Steve,

In Lucid and prior versions of Ubuntu, when using the Alternate
installer the user would be presented with three choices when installing
to a LUKS partition: AES, Blowfish, Serpent or Twofish.  Of course,
additional options were also presented, but these four basic ciphers
were always available.

Some time around either Maverick or Natty, the option for Twofish was
removed, and now it is only possible to install onto AES, Blowfish, or
Serpent, but not Twofish.  Note that if one installs Lucid using Twofish
partitions, then upgrades through the versions all the way up to Oneiric
(as I have done on the machine in this report), the Twofish partitions
will work fine.  There is no problem continuing to use them in the newer
versions of Ubuntu once they are installed, it is just that the newer
versions of Ubuntu do not offer the option of Twofish any more in the
Alternate installer.

Thanks for looking into this.  Let me know if there is anything I can do
to help.

Brian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886483

Title:
  Twofish LUKS Support in Alternate Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/886483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 886483] Re: Twofish LUKS Support in Alternate Installer

[Brian Knoll]

I meant to say that in prior versions the user would be presented with
_four_ choices, not three.  Now they are only presented with three.  I
apologize for the confusion.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886483

Title:
  Twofish LUKS Support in Alternate Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/886483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 812874] [NEW] package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade: EOF on stdin at conffile prompt

[Brian Knoll]

Public bug reported:

I received this error on two of my Lucid AMD64 systems today.  Please
tell me if you want any other information.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: base-files 5.0.0ubuntu20.10.04.4
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
Uname: Linux 2.6.32-32-generic x86_64
NonfreeKernelModules: ksplice_i8n8p89c ksplice_ayzwxwm8 
ksplice_4hvsf8yu_vmlinux_new ksplice_4hvsf8yu ksplice_opmu3wiv ksplice_dznd99q8 
ksplice_0h2rbixi ksplice_z0i2tro1_vmlinux_new ksplice_z0i2tro1 
ksplice_ooor1jo4_btrfs_new ksplice_ooor1jo4 ksplice_4e2d0zh6_vmlinux_new 
ksplice_4e2d0zh6 ksplice_ikz6js4p ksplice_uo6wkl5b ksplice_7wwaei20_vmlinux_new 
ksplice_7wwaei20 ksplice_d6hd002x_vmlinux_new ksplice_d6hd002x 
ksplice_hma6i9qh_vmlinux_new ksplice_hma6i9qh ksplice_dsopdhba_vmlinux_new 
ksplice_dsopdhba ksplice_dsnkaf0v ksplice_m8j9cj9o ksplice_4dxqvstt_vmlinux_new 
ksplice_4dxqvstt openafs
AptOrdering:
 base-files: Install
 base-files: Configure
Architecture: amd64
Date: Tue Jul 19 07:59:37 2011
ErrorMessage: EOF on stdin at conffile prompt
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: base-files
Title: package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade: EOF 
on stdin at conffile prompt

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lucid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812874

Title:
  package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade:
  EOF on stdin at conffile prompt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/812874/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 812874] Re: package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade: EOF on stdin at conffile prompt

[Brian Knoll]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812874

Title:
  package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade:
  EOF on stdin at conffile prompt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/812874/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 714335] Re: KVM SMP Linux Guests Hang on AMD

[Brian Knoll]

@Serge,

Thanks for the work on these patches.  I did look at the PPA and all I
see are the 2.6.38 packages, and since the 2.6.32-29 kernel isn't in the
mainstream repository yet I am unsure of where to get it.  Could you
please point me to where I can get this new kernel with the fixes, so I
can test it?  Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714335

Title:
  KVM SMP Linux Guests Hang on AMD

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs