[Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

[Alan Robertson]

Please delete the words "needing to" from comment #8.

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

Title:
  Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

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

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

[Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

[Alan Robertson]

@moontan - that sounds like a completely different bug. This bug is a
graphics driver bug, and yours appears to be something to do with
needing to ecryptfs key management. I wasn't using ecryptfs at all.

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

Title:
  Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

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

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

[Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

[Alan Robertson]

Sorry I didn't update this, but somewhere along the line, the problem
went away - after another set of updates. I'm not sure which one(s). But
it is definitely working again.

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

Title:
  Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

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

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

[Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

[Alan Robertson]

Hi Christopher M. Penalver (@penalvch),

I have tons of old kernels to choose from. What one would you like for me to 
try?
Here are the choices:
vmlinuz-3.19.0-28-generic  vmlinuz-3.19.0-41-generic  vmlinuz-4.2.0-36-generic
vmlinuz-3.19.0-30-generic  vmlinuz-3.19.0-42-generic  vmlinuz-4.4.0-22-generic
vmlinuz-3.19.0-31-generic  vmlinuz-3.19.0-43-generic  vmlinuz-4.4.0-24-generic
vmlinuz-3.19.0-32-generic  vmlinuz-3.19.0-47-generic  vmlinuz-4.4.0-28-generic
vmlinuz-3.19.0-33-generic  vmlinuz-3.19.0-49-generic  vmlinuz-4.4.0-31-generic
vmlinuz-3.19.0-37-generic  vmlinuz-3.19.0-51-generic  vmlinuz-4.4.0-34-generic
vmlinuz-3.19.0-39-generic  vmlinuz-3.19.0-56-generic  vmlinuz-4.4.0-36-generic

By the way, I did try this before, and I think it worked, but I had
trouble with USB devices afterwards (or so I remember). Since my mice
are USB, that was a problem.

So it would be helpful to me for you to suggest which kernel you would
like for me to try...

Something I forgot to say...
When I remove all the .kde stuff and it boots up correctly (but crippled due to 
all my config missing), then the fifo underrun does _not_ occur. It occurs only 
once per login.

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

Title:
  Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

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

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

[Bug 1623969] [NEW] Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

[Alan Robertson]

Public bug reported:

I just took some updates to a number of graphic libraries on 16.04, and
now I can't login to kubuntu. The symptom is that it takes my password
on the greeter screen, but never updates the screen after that.

The messages include these possibly related kernel messages:
kernel: [ 701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
kernel: [ 701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* 
CPU pipe B FIFO underrun

I'm currently running kernel 4.4.0-36.

Here are my most recent updates. The problem started after I rebooted.
Of course that was the next time I logged in too...

Start-Date: 2016-09-07 08:46:04
Commandline: /usr/bin/unattended-upgrade
Remove: libcdaudio1:amd64 (0.99.12p2-14), 
linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), 
linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), 
gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 
(0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), 
linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 
(1.28+cvs20151130-1)
End-Date: 2016-09-07 08:48:13

Start-Date: 2016-09-07 16:42:27
Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), 
libgnome-keyring0:amd64 (3.12.0-1build1, automatic)
Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), 
libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 
(1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.274
 3.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 
(0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 
14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 
1.8.3-2ubuntu3.1)
End-Date: 2016-09-07 16:44:34

Start-Date: 2016-09-12 14:31:39
Commandline: /usr/sbin/synaptic
Requested-By: alanr (1000)
Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64 
(0.5.13-1ubuntu2, 0.5.13-1ubuntu3), neo4j:amd64 (3.0.4, 3.0.5), 
accountsservice:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), 
libaccountsservice0:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2)
End-Date: 2016-09-12 14:32:17


It was after rebooting after updates that this occurred. My workaround is "rm 
-fr ~/.kde" - and that allows me to log in. I'm crippled, but at least I can 
log in...

If I try to log in again without doing this, the problem recurs. This
happens even if I just log in and log back out, and try to log in again.

However, I may just found a better workaround - press ALT-CTRL-F1 then
ALT-CTRL-F7, and then the next chunk of the login sequence occurs.

This makes it consistent with an issue reported in AskUbuntu
http://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-screen-
hangs

And it's possibly related to bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779 - because
of the CPU underrun being apparently related to graphics.

In fact, each time I do this, I get a little further in the login
sequence. It appears that the trigger for this bug is likely the prompts
to provide passwords for my various ssh private keys (I have four). This
also includes prompts from the KDE wallet manager for me to use the KDE
wallet - and I don't use that feature.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1

[Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[Alan Robertson]

Christopher M Penalver: There is an AskUbuntu issue for my particular
problem - something a lot like it - you can find it here:
http://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-screen-
hangs I've asked if they also saw the CPU underrun - no answer yet.

FWIW, I just installed xdiagnose and enabled all 3 debug check boxes,
and it doesn't show any errors at the moment. I've worked around the
"can't login" problem at the moment, and xdiagnose doesn't show any
errors.

Of course, if I hadn't worked around the "can't login" part, then I
wouldn't have been able to launch xdiagnose to diagnose the X windows
problem ;-).

I will do as you suggested and create the additional bug report - and
will link to it here and add you to the bug report.

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

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

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

[Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[Alan Robertson]

I just took some updates to a number of graphic libraries on 16.04, and
now I can't login to kubuntu. The symptom is that it takes my password
on the greeter screen, but never updates the screen after that.

The messages include these apparently related kernel messages:
kernel: [  701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
kernel: [  701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* 
CPU pipe B FIFO underrun

It is, of course, unclear whether these libraries triggered the kernel
bug or if this is unrelated to the kernel bug. I attached it here
because this is what I noticed first.

I'm currently running kernel 4.4.0-36.

Here are my most recent updates. The problem started after I rebooted.
Of course that was the next time I logged in too...

Start-Date: 2016-09-07  08:46:04
Commandline: /usr/bin/unattended-upgrade
Remove: libcdaudio1:amd64 (0.99.12p2-14), 
linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), 
linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), 
gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 
(0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), 
linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 
(1.28+cvs20151130-1)
End-Date: 2016-09-07  08:48:13

Start-Date: 2016-09-07  16:42:27
Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), 
libgnome-keyring0:amd64 (3.12.0-1build1, automatic)
Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), 
libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 
(1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.274
 3.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 
(0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 
14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 
1.8.3-2ubuntu3.1)
End-Date: 2016-09-07  16:44:34

Start-Date: 2016-09-12  14:31:39
Commandline: /usr/sbin/synaptic
Requested-By: alanr (1000)
Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64 
(0.5.13-1ubuntu2, 0.5.13-1ubuntu3), neo4j:amd64 (3.0.4, 3.0.5), 
accountsservice:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), 
libaccountsservice0:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2)
End-Date: 2016-09-12  14:32:17


** Attachment added: "Syslog from my failed attempt to log in."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+attachment/4740111/+files/syslog.error

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

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

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

[Bug 1574848] Re: jsonlint command misnamed as jsonlint-py

[Alan Robertson]

I meant to say "16.04". Guess I'm not sure what year it is ;-)

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

Title:
  jsonlint command misnamed as jsonlint-py

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-demjson/+bug/1574848/+subscriptions

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

[Bug 1574848] [NEW] jsonlint command misnamed as jsonlint-py

[Alan Robertson]

Public bug reported:

the python-demjson package binary is named "jsonlint"

For some unimaginable reason,in the 15.04 release, it appears to have
been broken and renamed jsonlint-py.

The man page still names it jsonlint.  The underlying pip package is
named demjson and still installs itself as jsonlint.

Please fix.  You should not be installing a pip package under an
incompatible name - one that's incompatible with both the old name, and
with the pip package it's based one.


$ whereis jsonlint
jsonlint: /usr/share/man/man1/jsonlint.1.gz
alanr@system76:~/monitor/src/cma$ whereis jsonlint-py
jsonlint-py: /usr/bin/jsonlint-py /usr/share/man/man1/jsonlint-py.1.gz

If you read either man page, the command is named "jsonlint". So that's
three to one for it being broken:

 - previous releases called it jsonlint
 - the man pages call it jsonlint
 - the underlying pip package calls it jsonlint

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: python-demjson 2.2.4-1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 25 14:16:13 2016
PackageArchitecture: all
SourcePackage: python-demjson
UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago)

** Affects: python-demjson (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/1574848

Title:
  jsonlint command misnamed as jsonlint-py

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-demjson/+bug/1574848/+subscriptions

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

Re: [Bug 1362423] Re: docker.io inspect shows docker pid as 0

[Alan Robertson]

I have no idea. I'll try and test that next week. I'm at a conference
today and tomorrow (presenting today).


On 04/21/2016 04:42 AM, Michael Hudson-Doyle wrote:
> Did this ever go upstream? 18 months later I'm sort of suspecting it's
> been fixed.
>


-- 

Alan Robertson / CTO
al...@assimilationsystems.com <mailto:al...@assimilationsystems.com>/ +1
303.947.7999

Assimilation Systems Limited
http://AssimilationSystems.com

Twitter <https://twitter.com/ossalanr> Linkedin
<https://www.linkedin.com/in/alanr> skype
<https://htmlsig.com/skype?username=alanr_unix.sh>


** Attachment added: "twitter.png"
   
https://bugs.launchpad.net/bugs/1362423/+attachment/4641377/+files/twitter.png

** Attachment added: "linkedin.png"
   
https://bugs.launchpad.net/bugs/1362423/+attachment/4641378/+files/linkedin.png

** Attachment added: "skype.png"
   https://bugs.launchpad.net/bugs/1362423/+attachment/4641379/+files/skype.png

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

Title:
  docker.io inspect shows docker pid as 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1362423/+subscriptions

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

Re: [Bug 1327442] Re: docker multicast packets origination addresses are mangled

[Alan Robertson]

This one definitely got fixed. Not so sure about the other one. I wrote
my software to work around it, so I don't notice so much any more.


On 04/21/2016 04:36 AM, Michael Hudson-Doyle wrote:
> I think this is long since fixed?
>
> ** Changed in: docker.io (Ubuntu)
>Status: New => Fix Released
>


-- 

Alan Robertson / CTO
al...@assimilationsystems.com <mailto:al...@assimilationsystems.com>/ +1
303.947.7999

Assimilation Systems Limited
http://AssimilationSystems.com

Twitter <https://twitter.com/ossalanr> Linkedin
<https://www.linkedin.com/in/alanr> skype
<https://htmlsig.com/skype?username=alanr_unix.sh>


** Attachment added: "twitter.png"
   
https://bugs.launchpad.net/bugs/1327442/+attachment/4641374/+files/twitter.png

** Attachment added: "linkedin.png"
   
https://bugs.launchpad.net/bugs/1327442/+attachment/4641375/+files/linkedin.png

** Attachment added: "skype.png"
   https://bugs.launchpad.net/bugs/1327442/+attachment/4641376/+files/skype.png

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

Title:
  docker multicast packets origination addresses are mangled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1327442/+subscriptions

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

[Bug 1389757] Re: pidgin crashes on startup: Attempt to unlock mutex that was not locked

[Alan Robertson]

Alberto Salvia Novella:  Thanks for the change in priority.  Crashing is
kinda important, and it shouldn't be too hard to get fixed...

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

Title:
  pidgin crashes on startup: Attempt to unlock mutex that was not locked

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

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

[Bug 1389757] Re: pidgin crashes on startup: Attempt to unlock mutex that was not locked

[Alan Robertson]

The Pidgin ticket https://developer.pidgin.im/ticket/16467 indicates
that this is a pidgin-skype bug which has been fixed.  Please just
package up the latest SVN version.

** Package changed: pidgin (Ubuntu) = pidgin-skype (Ubuntu)

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

Title:
  pidgin crashes on startup: Attempt to unlock mutex that was not locked

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

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

[Bug 1379713] Re: Pidgin crashes when pidgin-skype is installed

[Alan Robertson]

This is fixed in that latest version of the skype plugin.  See my
comments in
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1389757

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

Title:
  Pidgin crashes when pidgin-skype is installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin-skype/+bug/1379713/+subscriptions

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

[Bug 1379713] Re: Pidgin crashes when pidgin-skype is installed

[Alan Robertson]

https://code.google.com/p/skype4pidgin/source/detail?r=665

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

Title:
  Pidgin crashes when pidgin-skype is installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin-skype/+bug/1379713/+subscriptions

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

[Bug 1389757] Re: pidgin crashes on startup: Attempt to unlock mutex that was not locked

[Alan Robertson]

** Bug watch added: Pidgin Trac #16467
   http://developer.pidgin.im/ticket/16467

** Also affects: pidgin via
   http://developer.pidgin.im/ticket/16467
   Importance: Unknown
   Status: Unknown

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

Title:
  pidgin crashes on startup: Attempt to unlock mutex that was not locked

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

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

[Bug 1389757] Re: pidgin crashes on startup: Attempt to unlock mutex that was not locked

[Alan Robertson]

finch crashes the same way

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

Title:
  pidgin crashes on startup: Attempt to unlock mutex that was not locked

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

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

[Bug 1389757] [NEW] pidgin crashes on startup: Attempt to unlock mutex that was not locked

[Alan Robertson]

Public bug reported:

I start it up.   It crashes.  I just upgraded from 14.04, and since then
Pidgin is broken in this way.

I've attached the output of pidgin -d

I have IRC, and Skype and facebook and google hangout accounts enabled.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: pidgin 1:2.10.9-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Nov  5 08:32:36 2014
InstallationDate: Installed on 2014-07-12 (115 days ago)
InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1)
SourcePackage: pidgin
UpgradeStatus: Upgraded to utopic on 2014-11-05 (0 days ago)

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


** Tags: amd64 apport-bug mutex utopic

** Attachment added: Debug output from running pidgin -d
   https://bugs.launchpad.net/bugs/1389757/+attachment/4253939/+files/pidgin.out

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

Title:
  pidgin crashes on startup: Attempt to unlock mutex that was not locked

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

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

[Bug 1362423] Re: docker.io inspect shows docker pid as 0

[Alan Robertson]

Is this something you expect me to report upstream?  [for some reason I
thought you folks would do this if it needs doing].

I don't mind testing against newer versions of docker.   They already
fixed a previous NAT/firewall error I'd reported (but it's not in Trusty
yet).

 I'll look into testing against your version.

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

Title:
  docker.io inspect shows docker pid as 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1362423/+subscriptions

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

[Bug 1362423] [NEW] docker.io inspect shows docker pid as 0

[Alan Robertson]

Public bug reported:

 I'm doing a bunch of testing with dozens to hundreds of Docker
containers.  In the process, I gather the pid, hostname, etc. for each
docker instance as I spawn it so I can control what is going on in those
containers.

Every so often (that is every few thousand containers), I get one which
the State.Pid is 0 - and remains zero.  It seems to happen more often
when I spawn a lot of them (like 200) as fast as I can.

Here's the command I use to get the pid:
docker.io 'inspect' '--format' '{{.State.Pid}}' docker-instance-name

This almost always works, but occasionally it doesn't -- and returns a
line containing only 0.  I retry every second for 100 seconds just in
case it's a transient error.  It's not.

Since it takes a long time to spawn 200 containers and even longer to
shut them down (like 5 seconds each), this *really* puts a kink in my
testing.

Here's the output from my code when it encounters this condition:
.State.Pid is currently zero for instance 
DockerSystem.13183-00107/897886a7ad01 [0]

The string in [] at the end of the line is the contents of what I read
from the docker.io inspect command listed above.  So, it's not an empty
string being treated as or converted to a zero.  It's a 0 string.  The
code I'm using to manage these docker instances is here: http://hg
.linux-ha.org/assimilation/file/tip/cma/systemtests/docker.py


$ docker.io --version
Docker version 0.9.1, build 3600720

I'm running Ubuntu 14.04.

Hopefully all this stuff (and a lot more) showed up in the data gathered
by the ubuntu-bug command.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: docker.io 0.9.1~dfsg1-2
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 27 22:57:50 2014
InstallationDate: Installed on 2014-04-03 (146 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: docker.io
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.init.docker.io.conf: 2014-06-26T14:53:37.308799

** Affects: docker.io (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to docker.io in Ubuntu.
https://bugs.launchpad.net/bugs/1362423

Title:
  docker.io inspect shows docker pid as 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1362423/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1362423] [NEW] docker.io inspect shows docker pid as 0

[Alan Robertson]

Public bug reported:

 I'm doing a bunch of testing with dozens to hundreds of Docker
containers.  In the process, I gather the pid, hostname, etc. for each
docker instance as I spawn it so I can control what is going on in those
containers.

Every so often (that is every few thousand containers), I get one which
the State.Pid is 0 - and remains zero.  It seems to happen more often
when I spawn a lot of them (like 200) as fast as I can.

Here's the command I use to get the pid:
docker.io 'inspect' '--format' '{{.State.Pid}}' docker-instance-name

This almost always works, but occasionally it doesn't -- and returns a
line containing only 0.  I retry every second for 100 seconds just in
case it's a transient error.  It's not.

Since it takes a long time to spawn 200 containers and even longer to
shut them down (like 5 seconds each), this *really* puts a kink in my
testing.

Here's the output from my code when it encounters this condition:
.State.Pid is currently zero for instance 
DockerSystem.13183-00107/897886a7ad01 [0]

The string in [] at the end of the line is the contents of what I read
from the docker.io inspect command listed above.  So, it's not an empty
string being treated as or converted to a zero.  It's a 0 string.  The
code I'm using to manage these docker instances is here: http://hg
.linux-ha.org/assimilation/file/tip/cma/systemtests/docker.py


$ docker.io --version
Docker version 0.9.1, build 3600720

I'm running Ubuntu 14.04.

Hopefully all this stuff (and a lot more) showed up in the data gathered
by the ubuntu-bug command.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: docker.io 0.9.1~dfsg1-2
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 27 22:57:50 2014
InstallationDate: Installed on 2014-04-03 (146 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: docker.io
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.init.docker.io.conf: 2014-06-26T14:53:37.308799

** Affects: docker.io (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/1362423

Title:
  docker.io inspect shows docker pid as 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1362423/+subscriptions

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

[Bug 1336831] Re: upgrade to 14.04 completely scrambles screen - rendering machine useless

[Alan Robertson]

If someone is interested in this problem, I'd be happy to send them the
problematic video card.

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

Title:
  upgrade to 14.04 completely scrambles screen - rendering machine
  useless

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

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

[Bug 1319457] Re: usb headset causes retire_playback_urb ... callbacks suppressed spam in dmesg

[Alan Robertson]

I observe the same bug with a nuForce USB audio device.  Didn't see it
before trusty.

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

Title:
  usb headset causes retire_playback_urb ... callbacks suppressed spam
  in dmesg

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

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

[Bug 1320869] Re: apparmor=DENIED operation=ptrace profile=docker-default

[Alan Robertson]

I can't find the docker-default profile.  Here's what I did:
sudo find / -name '*docker-default*' -print
/sys/kernel/security/apparmor/policy/profiles/docker-default.0

That's the only line that came out.  I'm running 13.10 on this machine.
Not going to upgrade it until I get another 14.04 machine running
correctly.

Suggestions?

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

Title:
  apparmor=DENIED operation=ptrace profile=docker-default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1320869/+subscriptions

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

[Bug 1320869] Re: apparmor=DENIED operation=ptrace profile=docker-default

[Alan Robertson]

This causes NUMEROUS problems.  netstat -lp doesn't work.  lsof doesn't
work.

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

Title:
  apparmor=DENIED operation=ptrace profile=docker-default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1320869/+subscriptions

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

[Bug 1199059] Re: blueman and pulse's module-bluetooth-discover (A2DP audio sink devices failed to work with bluetoothd : Unable to select SEP in system log.)

[Alan Robertson]

Instead of the Xbluetooth manager hack, my hack is to just put a return
in that inner function.  But I can report that this hack also fixes it
for me.  In theory, the body of that function should just be a pass...
Or maybe the whole thing removed?

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

Title:
  blueman and pulse's module-bluetooth-discover (A2DP audio sink devices
  failed to work with bluetoothd : Unable to select SEP in system
  log.)

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

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

[Bug 1337420] Re: Ubuntu 14.04 doesn't work with Nvidia GeForce GT 610

[Alan Robertson]

More pictures.  This time of the video card box.

** Attachment added: video card box
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1337420/+attachment/4144812/+files/2014-07-03%2010.25.49.jpg

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

Title:
  Ubuntu 14.04 doesn't work with Nvidia GeForce GT 610

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

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

[Bug 1337420] [NEW] Ubuntu 14.04 doesn't work with Nvidia GeForce GT 610

[Alan Robertson]

Public bug reported:

After getting no response on my previous complaint about xorg in 14.04
(and ATI/AMD dropping Linux support), I decided I needed to replace my
video card.  So, I got an nVidia GeForce GT610.

It doesn't work with the installed 14.04 system, and it doesn't work
with the installer either.  I've attached a picture from the installer.
And I will attach a picture of the box that the video card came in - so
you can see some details about it.

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

** Attachment added: picture of the installer screen - a few minutes after the 
DVD stopped running...
   
https://bugs.launchpad.net/bugs/1337420/+attachment/4144811/+files/2014-07-03%2010.24.45.jpg

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

Title:
  Ubuntu 14.04 doesn't work with Nvidia GeForce GT 610

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

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

[Bug 1337420] Re: Ubuntu 14.04 doesn't work with Nvidia GeForce GT 610

[Alan Robertson]

My previous 14.04 video complaint is here:
https://bugs.launchpad.net/bugs/1336831

And, as before this is using the kubuntu 14.04 install DVD image.

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

Title:
  Ubuntu 14.04 doesn't work with Nvidia GeForce GT 610

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

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

[Bug 1336831] Re: upgrade to 14.04 completely scrambles screen - rendering machine useless

[Alan Robertson]

Below is the initial login screen.

I forgot to say this is kubuntu.  This comment includes a snapshot of
the initial kubuntu login screen.  I managed to get logged in using it.
But it was hopeless after that.

** Attachment added: Initial login screen picture.
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1336831/+attachment/4143936/+files/2014-07-02%2008.10.06.jpg

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

Title:
  upgrade to 14.04 completely scrambles screen - rendering machine
  useless

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

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

[Bug 1336831] [NEW] upgrade to 14.04 completely scrambles screen - rendering machine useless

[Alan Robertson]

Public bug reported:

I was running 13.10.  Upgrading to 14.04 makes the machine completely
useless in X.

I have a couple of screen pictures.  I'll attach one of them...  It only
wants me to to attach a single picture...

 $ lspci -v
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RS690 Host Bridge
Subsystem: ASUSTeK Computer Inc. Device 826d
Flags: bus master, 66MHz, medium devsel, latency 64

00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RS690 PCI to PCI 
Bridge (PCI Express Graphics Port 0) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: d000-dfff
Memory behind bridge: fdc0-fdcf
Prefetchable memory behind bridge: d000-dfff
Capabilities: access denied
Kernel driver in use: pcieport

00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RS690 PCI to PCI 
Bridge (PCI Express Port 3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: fdb0-fdbf
Prefetchable memory behind bridge: fdf0-fdff
Capabilities: access denied
Kernel driver in use: pcieport

00:12.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 
Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 22
I/O ports at ff00 [size=8]
I/O ports at fe00 [size=4]
I/O ports at fd00 [size=8]
I/O ports at fc00 [size=4]
I/O ports at fb00 [size=16]
Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
Capabilities: access denied
Kernel driver in use: ahci

00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB 
(OHCI0) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
Memory at fe02e000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci-pci

00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB 
(OHCI1) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci-pci

00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB 
(OHCI2) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18
Memory at fe02c000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci-pci

00:13.3 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB 
(OHCI3) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci-pci

00:13.4 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB 
(OHCI4) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18
Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci-pci

00:13.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB 
Controller (EHCI) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
Memory at fe029000 (32-bit, non-prefetchable) [size=256]
Capabilities: access denied
Kernel driver in use: ehci-pci

00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 13)
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, VGA palette snoop, stepping, fast Back2Back, 66MHz, 
user-definable features, ?? devsel, latency 0
I/O ports at 0b00 [size=16]
Capabilities: access denied
Kernel driver in use: piix4_smbus

00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB600 IDE 
(prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. Device 81ef
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
I/O ports at 01f0 [size=8]
I/O ports at 03f4
I/O ports at 0170 [size=8]
I/O ports at 0374
I/O ports at f900 [size=16]
Capabilities: access denied
Kernel driver in use: pata_atiixp

00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
Subsystem: ASUSTeK Computer Inc. Device 8249
Flags: bus master, 

[Bug 1336831] Re: upgrade to 14.04 completely scrambles screen - rendering machine useless

[Alan Robertson]

I thought... Maybe it was just an upgrade issue.  So I burned a kubuntu
14.04 64-bit DVD and tried the installer.

The installer is also a complete mess.  Picure attached...

Pretty much totally useless...  Guess I'll have to find a distro/version
that works...

** Attachment added: installer screen shot
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1336831/+attachment/4143943/+files/2014-07-02%2010.29.27.jpg

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

Title:
  upgrade to 14.04 completely scrambles screen - rendering machine
  useless

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

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

[Bug 1327442] Re: docker multicast packets origination addresses are mangled

[Alan Robertson]

Thanks Jérôme!  Great job!

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

Title:
  docker multicast packets origination addresses are mangled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1327442/+subscriptions

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

[Bug 1327442] [NEW] docker multicast packets origination addresses are mangled

[Alan Robertson]

Public bug reported:

Although I've filed this as a docker bug, it is far more likely to be a
kernel (bridge) bug.  I have enabled nothing extra in terms of docker
networking.   Both of these two

ubuntu72:~/monitor/src/cma $ uname -a
Linux ubuntu72 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
ubuntu72:~/monitor/src/cma $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04 LTS
Release:14.04
Codename:   trusty

ubuntu72:~/monitor/src/cma $ brctl show docker0
bridge name bridge id   STP enabled interfaces
docker0 8000.d6b7b71c12ab   no  veth3d9d
vetha7dd
vethade0


I have a couple of docker instances.  One is a client with IP address
172.17.0.4, and one a server with address 172.17.0.3.

The client sends out a multicast UDP packet to a certain address
(224.0.2.5) reserved for the use of this software.

The server dutifully listens for the packet, and it receives it.  HOWEVER, the 
source address of the packet is 172.17.42.1 - which is the address of the 
docker interface on the host (and of course, not the proper source address).  
The tcpdump trace of this packet being sent is below:
20:28:39.474887 IP 172.17.42.1.bb  224.0.2.5.bb: UDP, length 713
Needless to say, this is extraordinarily confusing to my software - and when it 
attempts to reply, nothing good happens...
You can see that it gets 'port unreachable' for that attempt to reply (as it 
should).

The subsequent packet sent to the (correct) 0.4 address happens because
that address is in the _content_ of initial multicast packet, and by
then the software is operating on the contents of the packet, not the
(incorrect) origination address..

Below is the full tcpdump trace of what's going on here from the server
perspective:

# tcpdump -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:28:35.933507 IP 7db9eb0e89ee  igmp.mcast.net: igmp v3 report, 1 group 
record(s)
20:28:35.934144 IP 7db9eb0e89ee.42650  10.10.10.20.domain: 18534+ PTR? 
22.0.0.224.in-addr.arpa. (41)
20:28:35.960407 IP 10.10.10.20.domain  7db9eb0e89ee.42650: 18534 1/6/0 PTR 
igmp.mcast.net. (181)
20:28:35.960737 IP 7db9eb0e89ee.47869  10.10.10.20.domain: 19922+ PTR? 
20.10.10.10.in-addr.arpa. (42)
20:28:35.986002 IP 10.10.10.20.domain  7db9eb0e89ee.47869: 19922 0/1/0 (101)
20:28:36.113623 IP 7db9eb0e89ee  igmp.mcast.net: igmp v3 report, 1 group 
record(s)
20:28:39.474887 IP 172.17.42.1.bb  224.0.2.5.bb: UDP, length 713
20:28:39.475003 IP 7db9eb0e89ee.33748  10.10.10.20.domain: 3617+ PTR? 
5.2.0.224.in-addr.arpa. (40)
20:28:39.525434 IP 7db9eb0e89ee.bb  172.17.42.1.bb: UDP, length 1091
20:28:39.525488 IP 172.17.42.1  7db9eb0e89ee: ICMP 172.17.42.1 udp port bb 
unreachable, length 556
20:28:39.529629 IP 7db9eb0e89ee.bb  172.17.0.4.bb: UDP, length 924
20:28:39.545780 IP 172.17.0.4.bb  7db9eb0e89ee.bb: UDP, length 70
20:28:39.568680 IP 10.10.10.20.domain  7db9eb0e89ee.33748: 3617 NXDomain 0/1/0 
(97)
20:28:39.568878 IP 7db9eb0e89ee.44605  10.10.10.20.domain: 47116+ PTR? 
1.42.17.172.in-addr.arpa. (42)
20:28:39.593858 IP 10.10.10.20.domain  7db9eb0e89ee.44605: 47116 0/1/0 (101)
20:28:39.594120 IP 7db9eb0e89ee.36687  10.10.10.20.domain: 20755+ PTR? 
4.0.17.172.in-addr.arpa. (41)
20:28:39.620179 IP 10.10.10.20.domain  7db9eb0e89ee.36687: 20755 0/1/0 (100)
20:28:40.941627 ARP, Request who-has 172.17.42.1 tell 7db9eb0e89ee, length 28
20:28:40.941687 ARP, Reply 172.17.42.1 is-at d6:b7:b7:1c:12:ab (oui Unknown), 
length 28
20:28:41.638772 IP 7db9eb0e89ee.bb  172.17.42.1.bb: UDP, length 1091
20:28:41.638811 IP 172.17.42.1  7db9eb0e89ee: ICMP 172.17.42.1 udp port bb 
unreachable, length 556
20:28:43.639166 IP 7db9eb0e89ee.bb  172.17.42.1.bb: UDP, length 1091
20:28:43.639193 IP 172.17.42.1  7db9eb0e89ee: ICMP 172.17.42.1 udp port bb 
unreachable, length 556

On the client side, the packet was sent correctly (according to tcpdump):
20:48:13.277353 IP 172.17.0.4.bb  224.0.2.5.bb: UDP, length 713

So, somebody somewhere is screwing over my source IP addresses...

This could _conceivably_ be considered a security bug I suppose because
information being misrouted might be security-sensitive, and would be
visible to the wrong party.

Below is some misc networking configuration for the host and the two
containers:

ubuntu72:~/monitor/src/cma $ uname -n; ifconfig; route -n
ubuntu72
docker0   Link encap:Ethernet  HWaddr d6:b7:b7:1c:12:ab  
  inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0
  inet6 addr: fe80::e8cd:69ff:feb7:d419/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:786010 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1180631 errors:0 dropped:0 

[Bug 1327442] [NEW] docker multicast packets origination addresses are mangled

[Alan Robertson]

Public bug reported:

Although I've filed this as a docker bug, it is far more likely to be a
kernel (bridge) bug.  I have enabled nothing extra in terms of docker
networking.   Both of these two

ubuntu72:~/monitor/src/cma $ uname -a
Linux ubuntu72 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
ubuntu72:~/monitor/src/cma $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04 LTS
Release:14.04
Codename:   trusty

ubuntu72:~/monitor/src/cma $ brctl show docker0
bridge name bridge id   STP enabled interfaces
docker0 8000.d6b7b71c12ab   no  veth3d9d
vetha7dd
vethade0


I have a couple of docker instances.  One is a client with IP address
172.17.0.4, and one a server with address 172.17.0.3.

The client sends out a multicast UDP packet to a certain address
(224.0.2.5) reserved for the use of this software.

The server dutifully listens for the packet, and it receives it.  HOWEVER, the 
source address of the packet is 172.17.42.1 - which is the address of the 
docker interface on the host (and of course, not the proper source address).  
The tcpdump trace of this packet being sent is below:
20:28:39.474887 IP 172.17.42.1.bb  224.0.2.5.bb: UDP, length 713
Needless to say, this is extraordinarily confusing to my software - and when it 
attempts to reply, nothing good happens...
You can see that it gets 'port unreachable' for that attempt to reply (as it 
should).

The subsequent packet sent to the (correct) 0.4 address happens because
that address is in the _content_ of initial multicast packet, and by
then the software is operating on the contents of the packet, not the
(incorrect) origination address..

Below is the full tcpdump trace of what's going on here from the server
perspective:

# tcpdump -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:28:35.933507 IP 7db9eb0e89ee  igmp.mcast.net: igmp v3 report, 1 group 
record(s)
20:28:35.934144 IP 7db9eb0e89ee.42650  10.10.10.20.domain: 18534+ PTR? 
22.0.0.224.in-addr.arpa. (41)
20:28:35.960407 IP 10.10.10.20.domain  7db9eb0e89ee.42650: 18534 1/6/0 PTR 
igmp.mcast.net. (181)
20:28:35.960737 IP 7db9eb0e89ee.47869  10.10.10.20.domain: 19922+ PTR? 
20.10.10.10.in-addr.arpa. (42)
20:28:35.986002 IP 10.10.10.20.domain  7db9eb0e89ee.47869: 19922 0/1/0 (101)
20:28:36.113623 IP 7db9eb0e89ee  igmp.mcast.net: igmp v3 report, 1 group 
record(s)
20:28:39.474887 IP 172.17.42.1.bb  224.0.2.5.bb: UDP, length 713
20:28:39.475003 IP 7db9eb0e89ee.33748  10.10.10.20.domain: 3617+ PTR? 
5.2.0.224.in-addr.arpa. (40)
20:28:39.525434 IP 7db9eb0e89ee.bb  172.17.42.1.bb: UDP, length 1091
20:28:39.525488 IP 172.17.42.1  7db9eb0e89ee: ICMP 172.17.42.1 udp port bb 
unreachable, length 556
20:28:39.529629 IP 7db9eb0e89ee.bb  172.17.0.4.bb: UDP, length 924
20:28:39.545780 IP 172.17.0.4.bb  7db9eb0e89ee.bb: UDP, length 70
20:28:39.568680 IP 10.10.10.20.domain  7db9eb0e89ee.33748: 3617 NXDomain 0/1/0 
(97)
20:28:39.568878 IP 7db9eb0e89ee.44605  10.10.10.20.domain: 47116+ PTR? 
1.42.17.172.in-addr.arpa. (42)
20:28:39.593858 IP 10.10.10.20.domain  7db9eb0e89ee.44605: 47116 0/1/0 (101)
20:28:39.594120 IP 7db9eb0e89ee.36687  10.10.10.20.domain: 20755+ PTR? 
4.0.17.172.in-addr.arpa. (41)
20:28:39.620179 IP 10.10.10.20.domain  7db9eb0e89ee.36687: 20755 0/1/0 (100)
20:28:40.941627 ARP, Request who-has 172.17.42.1 tell 7db9eb0e89ee, length 28
20:28:40.941687 ARP, Reply 172.17.42.1 is-at d6:b7:b7:1c:12:ab (oui Unknown), 
length 28
20:28:41.638772 IP 7db9eb0e89ee.bb  172.17.42.1.bb: UDP, length 1091
20:28:41.638811 IP 172.17.42.1  7db9eb0e89ee: ICMP 172.17.42.1 udp port bb 
unreachable, length 556
20:28:43.639166 IP 7db9eb0e89ee.bb  172.17.42.1.bb: UDP, length 1091
20:28:43.639193 IP 172.17.42.1  7db9eb0e89ee: ICMP 172.17.42.1 udp port bb 
unreachable, length 556

On the client side, the packet was sent correctly (according to tcpdump):
20:48:13.277353 IP 172.17.0.4.bb  224.0.2.5.bb: UDP, length 713

So, somebody somewhere is screwing over my source IP addresses...

This could _conceivably_ be considered a security bug I suppose because
information being misrouted might be security-sensitive, and would be
visible to the wrong party.

Below is some misc networking configuration for the host and the two
containers:

ubuntu72:~/monitor/src/cma $ uname -n; ifconfig; route -n
ubuntu72
docker0   Link encap:Ethernet  HWaddr d6:b7:b7:1c:12:ab  
  inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0
  inet6 addr: fe80::e8cd:69ff:feb7:d419/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:786010 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1180631 errors:0 dropped:0 

[Bug 511401] Re: netstat doesn't display ipv6 addresses correctly (they are truncated)

[Alan Robertson]

Problem still exists!

# netstat -ntp | grep pidgin
tcp6  0  0 2601:1:ad80:1445::54776  2620:0:861:52:208::6667 ESTABLISHED 
2043/pidgin

This address is  from irc.freenode.net
2620:0:861:52:208:80:155:68

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/511401

Title:
  netstat doesn't display ipv6 addresses correctly (they are truncated)

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 511401] Re: netstat doesn't display ipv6 addresses correctly (they are truncated)

[Alan Robertson]

Problem still exists!

# netstat -ntp | grep pidgin
tcp6  0  0 2601:1:ad80:1445::54776  2620:0:861:52:208::6667 ESTABLISHED 
2043/pidgin

This address is  from irc.freenode.net
2620:0:861:52:208:80:155:68

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

Title:
  netstat doesn't display ipv6 addresses correctly (they are truncated)

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

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

[Bug 320700] Re: gvim rendering is slow

[Alan Robertson]

Very recently it became even slower with syntax highlighting on.  I ran
across it in this bug repository: https://bugs.archlinux.org/task/36693
- and tried their suggested workaround, set regexpengine=1 which makes a
huge difference - making it useful again.

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

Title:
  gvim rendering is slow

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

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

[Bug 1178737] [NEW] Cannot load bridge module: missing symbols

[Alan Robertson]

Public bug reported:

alanr@ibmlaptop:/var/log$ lsb_release -rd
Description:Ubuntu 12.04.2 LTS
Release:12.04

Running this kernel after a recent update.
Linux ibmlaptop 3.2.0-41-generic #66-Ubuntu SMP Thu Apr 25 03:27:11 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

After upgrading, kvm can't start my VM that uses bridging.  Tracked it
down as noted below:


WHAT I DID:
I did a  sudo depmod /lib/modules/3.2.0-41-generic/kernel/net/bridge/bridge.ko
  (this appears to succeed - no messages and 0 exit code)
and a $ sudo insmod /lib/modules/3.2.0-41-generic/kernel/net/bridge/bridge.ko

WHAT I EXPECTED:
I expected the bridge module to load.

WHAT I GOT:
insmod: error inserting 
'/lib/modules/3.2.0-41-generic/kernel/net/bridge/bridge.ko': -1 Unknown symbol 
in module

Looking at the syslog, I got the unknown symbol messages below:

May  9 17:38:30 ibmlaptop kernel: [ 6162.081081] bridge: Unknown symbol 
stp_proto_register (err 0)
May  9 17:38:30 ibmlaptop kernel: [ 6162.081143] bridge: Unknown symbol 
stp_proto_unregister (err 0)
what started me down this path:

WHAT I DID:
Started a virtual machine with bridging enabled using Virtual Machine Manager

WHAT I GOT:
Error starting domain: Cannot get interface MTU on 'br0': No such device
Details:
Error starting domain: Cannot get interface MTU on 'br0': No such device

Traceback (most recent call last):
  File /usr/share/virt-manager/virtManager/asyncjob.py, line 45, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File /usr/share/virt-manager/virtManager/asyncjob.py, line 66, in tmpcb
callback(*args, **kwargs)
  File /usr/share/virt-manager/virtManager/domain.py, line 1120, in startup
self._backend.create()
  File /usr/lib/python2.7/dist-packages/libvirt.py, line 551, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Cannot get interface MTU on 'br0': No such device


WHAT I EXPECTED:
For the VM to start like it did before the upgrade.
All the things above came from further investigation of this problem.


Uncertain if this is related, but , there appear to be a lot of broken symbols 
in this kernel:
May  9 15:58:39 ibmlaptop kernel: [  170.968648] kvm_intel: Unknown symbol 
kvm_clear_guest_page (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968654] kvm_intel: Unknown symbol 
kvm_disable_largepages (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968662] kvm_intel: Unknown symbol 
kvm_exit (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968666] kvm_intel: Unknown symbol 
kvm_init (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968670] kvm_intel: Unknown symbol 
kvm_enable_efer_bits (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968675] kvm_intel: Unknown symbol 
kvm_fast_pio_out (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968679] kvm_intel: Unknown symbol 
kvm_mmu_get_spte_hierarchy (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968685] kvm_intel: Unknown symbol 
gfn_to_page (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968695] kvm_intel: Unknown symbol 
kvm_get_msr_common (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968702] kvm_intel: Unknown symbol 
__kvm_set_memory_region (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968709] kvm_intel: Unknown symbol 
kvm_vcpu_uninit (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968713] kvm_intel: Unknown symbol 
kvm_emulate_halt (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968717] kvm_intel: Unknown symbol 
kvm_set_apic_base (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968723] kvm_intel: Unknown symbol 
kvm_define_shared_msr (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968729] kvm_intel: Unknown symbol 
kvm_set_xcr (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968737] kvm_intel: Unknown symbol 
kvm_write_guest_virt_system (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968742] kvm_intel: Unknown symbol 
kvm_find_cpuid_entry (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968746] kvm_intel: Unknown symbol 
kvm_task_switch (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968750] kvm_intel: Unknown symbol 
kvm_read_guest_virt (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968754] kvm_intel: Unknown symbol 
kvm_enable_tdp (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968760] kvm_intel: Unknown symbol 
x86_emulate_instruction (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968765] kvm_intel: Unknown symbol 
__tracepoint_kvm_cr (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968770] kvm_intel: Unknown symbol 
kvm_mmu_set_mmio_spte_mask (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968774] kvm_intel: Unknown symbol 
kvm_disable_tdp (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968779] kvm_intel: Unknown symbol 
kvm_require_cpl (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968785] kvm_intel: Unknown symbol 
kvm_lmsw (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968790] kvm_intel: Unknown symbol 
kvm_lapic_set_eoi (err 0)
May  9 15:58:39 ibmlaptop kernel: [  170.968797] kvm_intel: Unknown 

[Bug 1178744] [NEW] Lenovo W500 Trackpoint doesn't work after upgrade

[Alan Robertson]

Public bug reported:

alanr@ibmlaptop:/var/log$ lsb_release -rd
Description: Ubuntu 12.04.2 LTS
Release: 12.04

Running this kernel after a recent update.
Linux ibmlaptop 3.2.0-41-generic #66-Ubuntu SMP Thu Apr 25 03:27:11 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

I recently too the linux-image-3.2.0-41-generic upgrade, and now the
trackpoint device (the little red eraser thing in the middle of the
keyboard) doesn't work.  Reverting to an earlier kernel makes the
problem go away.

What I did:
Used the trackpoint device

WHAT I GOT:
No response to moving the trackpoint during login screen or afterwards.  No 
apparent effect.

WHAT I EXPECTED:
For the trackpoint device to behave as a mouse-like thing like it always has.

Here is the output from lspci on the machine:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express 
Graphics Port (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI 
Controller (rev 07)
00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset AMT SOL 
Redirection (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network 
Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 
(rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 
(rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 
(rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port 
SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV635 
[Mobility Radeon HD 3650]
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] 
Network Connection
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 21)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter 
(rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-41-generic 3.2.0-41.66
ProcVersionSignature: Ubuntu 3.2.0-41.66-generic 3.2.42
Uname: Linux 3.2.0-41-generic x86_64
NonfreeKernelModules: symap_custom_3.2.0_41_generic_x86_64 
symev_custom_3.2.0_41_generic_x86_64 xts gf128mul dm_crypt usb_storage usbhid 
hid radeon ttm firewire_ohci firewire_core crc_itu_t sdhci_pci sdhci wmi i915 
drm_kms_helper drm e1000e i2c_algo_bit video
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access /dev/snd/: No such file or directory
AplayDevices: aplay: device_list:252: no soundcards found...
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
ArecordDevices: arecord: device_list:252: no soundcards found...
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Fri May 10 10:40:04 2013
HibernationDevice: RESUME=UUID=8f4139d7-7daf-4b89-9b60-916b880a79e0
InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
 
 tun0  no wireless extensions.
MachineType: LENOVO 4061BK8
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 radeondrmfb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-41-generic 
root=/dev/mapper/ubuntu-root ro quiet splash
RelatedPackageVersions:
 

[Bug 1178737] Re: Cannot load bridge module: missing symbols

[Alan Robertson]

Sorry I didn't use ubuntu-bug on this one - but I did on the other bug I
just filed - from the same system, the same kernel, the same time frame.
See Bug #1178744   all that info should be applicable to this one.  I
just missed the instruction on running it.  Sorry!

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] Re: Cannot load bridge module: missing symbols

[Alan Robertson]

apport information

** Tags added: apport-collected running-unity

** Description changed:

  alanr@ibmlaptop:/var/log$ lsb_release -rd
  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04
  
  Running this kernel after a recent update.
  Linux ibmlaptop 3.2.0-41-generic #66-Ubuntu SMP Thu Apr 25 03:27:11 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux
  
  After upgrading, kvm can't start my VM that uses bridging.  Tracked it
  down as noted below:
  
  
  WHAT I DID:
  I did a  sudo depmod /lib/modules/3.2.0-41-generic/kernel/net/bridge/bridge.ko
(this appears to succeed - no messages and 0 exit code)
  and a $ sudo insmod /lib/modules/3.2.0-41-generic/kernel/net/bridge/bridge.ko
  
  WHAT I EXPECTED:
  I expected the bridge module to load.
  
  WHAT I GOT:
  insmod: error inserting 
'/lib/modules/3.2.0-41-generic/kernel/net/bridge/bridge.ko': -1 Unknown symbol 
in module
  
  Looking at the syslog, I got the unknown symbol messages below:
  
  May  9 17:38:30 ibmlaptop kernel: [ 6162.081081] bridge: Unknown symbol 
stp_proto_register (err 0)
  May  9 17:38:30 ibmlaptop kernel: [ 6162.081143] bridge: Unknown symbol 
stp_proto_unregister (err 0)
  what started me down this path:
  
  WHAT I DID:
  Started a virtual machine with bridging enabled using Virtual Machine Manager
  
  WHAT I GOT:
  Error starting domain: Cannot get interface MTU on 'br0': No such device
  Details:
  Error starting domain: Cannot get interface MTU on 'br0': No such device
  
  Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/asyncjob.py, line 45, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File /usr/share/virt-manager/virtManager/asyncjob.py, line 66, in tmpcb
  callback(*args, **kwargs)
File /usr/share/virt-manager/virtManager/domain.py, line 1120, in startup
  self._backend.create()
File /usr/lib/python2.7/dist-packages/libvirt.py, line 551, in create
  if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
  libvirtError: Cannot get interface MTU on 'br0': No such device
  
  
  WHAT I EXPECTED:
  For the VM to start like it did before the upgrade.
  All the things above came from further investigation of this problem.
  
  
  Uncertain if this is related, but , there appear to be a lot of broken 
symbols in this kernel:
  May  9 15:58:39 ibmlaptop kernel: [  170.968648] kvm_intel: Unknown symbol 
kvm_clear_guest_page (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968654] kvm_intel: Unknown symbol 
kvm_disable_largepages (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968662] kvm_intel: Unknown symbol 
kvm_exit (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968666] kvm_intel: Unknown symbol 
kvm_init (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968670] kvm_intel: Unknown symbol 
kvm_enable_efer_bits (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968675] kvm_intel: Unknown symbol 
kvm_fast_pio_out (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968679] kvm_intel: Unknown symbol 
kvm_mmu_get_spte_hierarchy (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968685] kvm_intel: Unknown symbol 
gfn_to_page (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968695] kvm_intel: Unknown symbol 
kvm_get_msr_common (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968702] kvm_intel: Unknown symbol 
__kvm_set_memory_region (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968709] kvm_intel: Unknown symbol 
kvm_vcpu_uninit (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968713] kvm_intel: Unknown symbol 
kvm_emulate_halt (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968717] kvm_intel: Unknown symbol 
kvm_set_apic_base (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968723] kvm_intel: Unknown symbol 
kvm_define_shared_msr (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968729] kvm_intel: Unknown symbol 
kvm_set_xcr (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968737] kvm_intel: Unknown symbol 
kvm_write_guest_virt_system (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968742] kvm_intel: Unknown symbol 
kvm_find_cpuid_entry (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968746] kvm_intel: Unknown symbol 
kvm_task_switch (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968750] kvm_intel: Unknown symbol 
kvm_read_guest_virt (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968754] kvm_intel: Unknown symbol 
kvm_enable_tdp (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968760] kvm_intel: Unknown symbol 
x86_emulate_instruction (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968765] kvm_intel: Unknown symbol 
__tracepoint_kvm_cr (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968770] kvm_intel: Unknown symbol 
kvm_mmu_set_mmio_spte_mask (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968774] kvm_intel: Unknown symbol 
kvm_disable_tdp (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  170.968779] kvm_intel: Unknown symbol 
kvm_require_cpl (err 0)
  May  9 15:58:39 ibmlaptop kernel: [  

[Bug 1178737] AudioDevicesInUse.txt

[Alan Robertson]

apport information

** Attachment added: AudioDevicesInUse.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672524/+files/AudioDevicesInUse.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] BootDmesg.txt

[Alan Robertson]

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672525/+files/BootDmesg.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] CurrentDmesg.txt

[Alan Robertson]

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672526/+files/CurrentDmesg.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] Lspci.txt

[Alan Robertson]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1178737/+attachment/3672527/+files/Lspci.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] Lsusb.txt

[Alan Robertson]

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1178737/+attachment/3672528/+files/Lsusb.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] PciMultimedia.txt

[Alan Robertson]

apport information

** Attachment added: PciMultimedia.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672529/+files/PciMultimedia.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] ProcCpuinfo.txt

[Alan Robertson]

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672530/+files/ProcCpuinfo.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] ProcInterrupts.txt

[Alan Robertson]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672531/+files/ProcInterrupts.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] ProcModules.txt

[Alan Robertson]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672532/+files/ProcModules.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] PulseList.txt

[Alan Robertson]

apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672533/+files/PulseList.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] UdevDb.txt

[Alan Robertson]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1178737/+attachment/3672534/+files/UdevDb.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] UdevLog.txt

[Alan Robertson]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672535/+files/UdevLog.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] WifiSyslog.txt

[Alan Robertson]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1178737/+attachment/3672536/+files/WifiSyslog.txt

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1178737] Re: Cannot load bridge module: missing symbols

[Alan Robertson]

No packages found matching linux.
ERROR: hook /usr/share/apport/general-hooks/cloud_archive.py crashed:
Traceback (most recent call last):
  File /usr/lib/python2.7/dist-packages/apport/report.py, line 719, in 
add_hooks_info
symb['add_info'](self, ui)
  File /usr/share/apport/general-hooks/cloud_archive.py, line 18, in add_info
if '~cloud' in packaging.get_version(package) and \
  File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 95, in 
get_version
raise ValueError('package does not exist')
ValueError: package does not exist


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

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

Title:
  Cannot load bridge module: missing symbols

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

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

[Bug 1160569]

[Alan Robertson]

OK.  I agree with comment 3.  I have found out that Thunderbird will
crash and burn - or just hang.

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

Title:
  [regression] GLib-CRITICAL **: g_slice_set_config: assertion
  `sys_page_size == 0' failed

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

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

[Bug 1160569]

[Alan Robertson]

Thunderbird doesn't start AT ALL in kubuntu 13.04.  because of this bug.
Or rather, it starts, but the part of it that opens a display window
doesn't start.  If I log in with web mail I see that it is filing emails
as they arrive according to the rules I've established -- but the
display never comes up.

And, in this particular case, I could have been completely unable to
report this bug - because you forced me to change my password -- and
sent me an email so I could do it :-D.  Of course, since Thunderbird
isn't working -- it became more challenging...

Strangely enough, Firefox _does_ start.

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

Title:
  [regression] GLib-CRITICAL **: g_slice_set_config: assertion
  `sys_page_size == 0' failed

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

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

[Bug 1160569]

[Alan Robertson]

Following the link to the gnome bugzilla -- I ran across a tolerable
workaround for the moment: If G_SLICE=always-malloc is in the
environment, then it will start.  It still complains, but it starts and
appears to work (so far).

This makes it consume more CPU (and Lord knows it already consumes
enough CPU), but it does allow Thunderbird to start - which is a good
thing.

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

Title:
  [regression] GLib-CRITICAL **: g_slice_set_config: assertion
  `sys_page_size == 0' failed

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

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

Re: [Bug 1050696] Re: Crash while doing an rsync backup

[Alan Robertson]

On 11/13/2012 9:17 PM, Launchpad Bug Tracker wrote:
 [Expired for linux (Ubuntu) because there has been no activity for 60
 days.]

 ** Changed in: linux (Ubuntu)
 Status: Incomplete = Expired


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

Title:
  Crash while doing  an rsync backup

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

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

[Bug 1072230] Re: rpcinfo is in /sbin, not /bin = NFS v3 is disabled

[Alan Robertson]

Looks like this fixed it.  Please close it at your convenience.

Thanks for your help!

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

Title:
  rpcinfo is in /sbin, not /bin = NFS v3 is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1072230/+subscriptions

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

[Bug 1072230] [NEW] rpcinfo is in /sbin, not /bin = NFS v3 is disabled

[Alan Robertson]

Public bug reported:

The init script for nfs-kernel-server looks to see if NFS v3 is enabled
by running rpcinfo.

This is nice and all, but it will only work if the pathname to rpcinfo
is correct.

The original code said this:

$PREFIX/bin/rpcinfo -u localhost nfs 3 /dev/null 21 ||
RPCMOUNTDOPTS=$RPCMOUNTDOPTS --no-nfs-version 3


The correct code is this:

$PREFIX/sbin/rpcinfo -u localhost nfs 3 /dev/null 21 ||
RPCMOUNTDOPTS=$RPCMOUNTDOPTS --no-nfs-version 3

Either that or rpcinfo is misplaced.

In any case, this keeps nfs v3 from working - because it ALWAYS turns on
the --no-nfs-version-3 flag.

Perhaps this should be checked for at the beginning of the script like
some of the other commands?

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: nfs-kernel-server 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
Date: Sat Oct 27 16:48:01 2012
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 
(20110426)
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to quantal on 2012-10-23 (3 days ago)
mtime.conffile..etc.init.d.nfs.kernel.server: 2012-10-27T16:34:08.070671

** Affects: nfs-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug quantal

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

Title:
  rpcinfo is in /sbin, not /bin = NFS v3 is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1072230/+subscriptions

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

[Bug 1072230] Re: rpcinfo is in /sbin, not /bin = NFS v3 is disabled

[Alan Robertson]

Here's my OS version info:
{
  discovertype: OS,
  description: OS information,
  host: silas,
  source: /usr/share/assimilation/discovery_agents/os,
  data: {
nodename: silas,
operating-system: GNU/Linux,
machine: x86_64,
processor: x86_64,
hardware-platform: x86_64,
kernel-name: Linux,
kernel-release: 3.5.0-17-generic,
kernel-version: #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012,
Distributor ID:   Ubuntu,
Description:  Ubuntu 12.10,
Release:  12.10,
Codename: quantal
  }
}

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

Title:
  rpcinfo is in /sbin, not /bin = NFS v3 is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1072230/+subscriptions

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

[Bug 1072230] Re: rpcinfo is in /sbin, not /bin = NFS v3 is disabled

[Alan Robertson]

I did two upgrades in a row.  Now that you mention it I seem to recall
it had trouble upgrading NFS.  I don't have any recollection of changing
the script until I changed it.  The usual reason for me fixing init
scripts is bad exit codes (Pacemaker hates incorrect exit codes).  But
I'm quite certain I didn't have that problem with NFS.

I'm having troubles with NFS (v3) that I didn't have before - so this
seemed like a likely cause - which would be why I started this process.
I will try your suggestion tomorrow.  Thanks for looking at it!

My apologies for adding noise.

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

Title:
  rpcinfo is in /sbin, not /bin = NFS v3 is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1072230/+subscriptions

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

Re: [Bug 1050696] Re: Crash while doing an rsync backup

[Alan Robertson]

On 9/14/2012 8:41 AM, Joseph Salisbury wrote:
 ** Changed in: linux (Ubuntu)
 Importance: Undecided = High

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


Hi Joseph,

Thanks for starting to look at this bug.

Please note that the bug may be allowing me to mount root twice... Which 
has a certain amount of stupid mixed in too...

 -- Alan Robertson
 al...@unix.sh

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

Title:
  Crash while doing  an rsync backup

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

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

[Bug 1050696] [NEW] Crash while doing an rsync backup

[Alan Robertson]

Public bug reported:

This crash is very reproducible at this point in time.  Run rsync.  Wait
2 minutes.  Look at crash screen.  I have a photograph of the crash
screen that I will attach once I get to that point.  Clint Byrum's guess
is that this is a SATA driver problem.  A reasonable guess.

Unfortunately, I am highly motivated to figure out how to work around it
as the system I am backing up over NFS is having disk problems.  So,
this may destroy its reproducability.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-25-generic-pae 3.0.0-25.41
ProcVersionSignature: Ubuntu 3.0.0-25.41-generic-pae 3.0.40
Uname: Linux 3.0.0-25-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alanr  2062 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe02 irq 43'
   Mixer name   : 'Realtek ALC883'
   Components   : 'HDA:10ec0883,10438232,0012'
   Controls  : 36
   Simple ctrls  : 20
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdcfc000 irq 44'
   Mixer name   : 'ATI R6xx HDMI'
   Components   : 'HDA:1002aa01,00aa0100,0010'
   Controls  : 4
   Simple ctrls  : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [off]
Date: Thu Sep 13 17:03:11 2012
HibernationDevice: RESUME=UUID=416b6506-30a0-4b87-b29a-1f2a532ce58b
InstallationMedia: Kubuntu 11.04 Natty Narwhal - Release i386 (20110427)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-25-generic-pae 
root=UUID=c64e2ab9-56a5-4a81-8cdf-77c791569e89 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-25-generic-pae N/A
 linux-backports-modules-3.0.0-25-generic-pae  N/A
 linux-firmware1.60.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2012-01-30 (227 days ago)
dmi.bios.date: 06/26/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM HDMI ACPI BIOS Revision 1001
dmi.board.name: M2A-VM HDMI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMHDMIACPIBIOSRevision1001:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VMHDMI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: apport-bug i386 oneiric

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

Title:
  Crash while doing  an rsync backup

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

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

[Bug 1050696] Re: Crash while doing an rsync backup

[Alan Robertson]

** Attachment added: Photograph of the crash screen
   
https://bugs.launchpad.net/bugs/1050696/+attachment/3313664/+files/DSCN0436_v1.JPG

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

Title:
  Crash while doing  an rsync backup

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

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

[Bug 1050696] Re: Crash while doing an rsync backup

[Alan Robertson]

It appears that at least once when I did this I had shot myself in the foot.
Please check to see if the kernel thinks root was mounted twice.

What appears to have happened to me was that when I booted with the
esata device powered off, the esata device was /dev/sdc.  When I booted
with the device powered on, the _root device_ became /dev/sdc.

And rather stupidly, I mounted /dev/sdc as my backup device.

If you can see if that's what I did here, then the bug is that it let me
mount root twice, or that I'm stupid.  Take your pick.

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

Title:
  Crash while doing  an rsync backup

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

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

[Bug 1050696] Re: Crash while doing an rsync backup

[Alan Robertson]

I labelled the device and will mount by label in the future.

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

Title:
  Crash while doing  an rsync backup

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

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

[Bug 628968] Re: Inkscape SEGFAULTs immediately

[Alan Robertson]

I have a similar problem - on 64-bit Ubuntu Inkscape 0.48.0 r9654 - when
I start Inkscape, it starts, but then whenever I select Document
Properties - it crashes immediately.

Since the first thing I always do is set up the page size and
orientation, this means I can do very little with it.

Let me know if you want me to create a separate bug, or leave it with
this one.

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

Title:
  Inkscape SEGFAULTs immediately

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

[Bug 458453] Re: beam.smp uses lots of CPU on desktopcouch contacts lookup

[Alan Robertson]

Just so you know... you don't have to be running evolution, or have
gwibber active  or anything else.  It just consumes CPU - as do a number
of the python modules as well.  If there is no activity, they should
consume practically zero CPU all the time.  I see I have a bug fix
install pending for this.  I'll install it and see if all is better.

-- 
beam.smp uses lots of CPU on desktopcouch contacts lookup
https://bugs.launchpad.net/bugs/458453
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 573696] Re: dpkg: ../../src/archives.c:763: tarobject: Assertion `r == stab.st_size' failed. Aborted

[Alan Robertson]

This behavior also shows up when making a chrooted distribution in an
encrypted filesystem as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/524919.  However, I
believe that if our implementation of ntfs APIs breaks it, that it
should also be fixed there.

-- 
dpkg: ../../src/archives.c:763: tarobject: Assertion `r == stab.st_size' 
failed. Aborted
https://bugs.launchpad.net/bugs/573696
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 283658] Re: grip buffer overflow in intrepid

[Alan Robertson]

I have this same problem - and disabling id3v2 fixes it for me also.

-- 
grip buffer overflow in intrepid
https://bugs.launchpad.net/bugs/283658
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 153379] Re: [apport] grip crashed with SIGSEGV in free()

[Alan Robertson]

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

** This bug has been marked a duplicate of bug 28365
   firefox freeze

-- 
[apport] grip crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/153379
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 345505] [NEW] Intrepid lacks rgb.txt AND Xcms.txt

[Alan Robertson]

Public bug reported:

Presumably, tightvnc didn't make up the need for rgb.txt or Xcms.txt, but I 
presume from what I read, that this is part of the X windows system that isn't 
properly supplied by Intrepid.  You can read about X11 color maps here:
   http://www.klauser.ch/lxug
You can also read about how to use rgb.txt to generate Xcms.txt here:
   https://lists.ubuntu.com/archives/ubuntu-uk/2007-April/004337.html

I am running Xvnc on one machine, and vncviewer on another machine.
These lacks show up very quickly when I try to start up anything from the 
ImageMagick suite when displaying it over Xvnc.
For example, pick an image to display, and start up display on it.  Display 
will complain about not being able to find the color black and terminate.

If you put these files in place, then ImageMagick is happy and works
quite nicely.  Now, maybe I'm just doing something wrong, but if I put
these files into place, then everything works wonderfully.

apt-cache policy tightvncserver
tightvncserver:
  Installed: 1.3.9-4
  Candidate: 1.3.9-4
  Version table:
 *** 1.3.9-4 0
500 http://us.archive.ubuntu.com intrepid/universe Packages
100 /var/lib/dpkg/status

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

-- 
Intrepid lacks rgb.txt AND Xcms.txt
https://bugs.launchpad.net/bugs/345505
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