[Bug 381288] Re: Character encoding setting saved in config doesn't stick

[Jacob Nevins]

This is a known bug upstream, and is believed fix as of svn r8592.

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

** Changed in: putty
   Status: New => Fix Committed

-- 
Character encoding setting saved in config doesn't stick
https://bugs.launchpad.net/bugs/381288
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

** Changed in: putty
   Status: Confirmed => Fix Committed

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 381288] Re: Character encoding setting saved in config doesn't stick

[Jacob Nevins]

It's only marked as "Fix Committed" in "PuTTY" (i.e. upstream). I don't
believe the Ubuntu package (i.e., "putty (Ubuntu)") has picked up the
fix yet.

-- 
Character encoding setting saved in config doesn't stick
https://bugs.launchpad.net/bugs/381288
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

Fixed upstream in r8461, by no longer attempting to keep the log file
private in any circumstances. (Which probably thus wants advertising in
the changelog.)

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

This patch has also been committed to PuTTY upstream (r8516).

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

Confirmed upstream (0.60 and svn -- now fixed)

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

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

** Changed in: putty
   Status: New => Fix Committed

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 42410] Re: evince reports "incorrect format" for DVI files when no TeX distribution is installed.

[Jacob Nevins]

Still in Jaunty (evince 2.26.1-0ubuntu1).

-- 
evince reports "incorrect format" for DVI files when no TeX distribution is 
installed.
https://bugs.launchpad.net/bugs/42410
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

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

[Bug 146680] Re: putty crashed with SIGSEGV in logevent()

[Jacob Nevins]

I think this must be down to the bug that was fixed upstream in r8304,
2008-11-17. I think that the backend (*telnet_closing():telnet) must
have been freed by notify_remote_exit(), leading to telnet->frontend
being NULL. (Or at least, I can't see how else telnet->frontend ended up
NULL.)

That fix will have first appeared in Ubuntu in putty 0.60+2009-04-05-1.
So, the current package should not have this bug.

-- 
putty crashed with SIGSEGV in logevent()
https://bugs.launchpad.net/bugs/146680
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

I'm seeing a similar issue -- the user on the second simultaneously
started X server does not get Compiz effects. In fact they don't get any
3D acceleration at all, and there may also be problems with movie
playback.

Comparing ~/.xsession-errors for the two users, the point of divergence
is just after the following lines:

Checking for Composite extension: present.
Checking screen 1Comparing resolution (1680x1050) to maximum 3D texture size 
(2048): Passed.

In the success case (1st user), we have the following lines:

Checking for Software Rasterizer: Not present. 
Checking for nVidia: not present. 
Checking for FBConfig: present. 
running under gnome seesion, checking for gnomecompat
Checking for Xgl: not present. 
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 
image format
I/O warning : failed to load external entity 
"/home/user1/.compiz/session/10ea06d6867fce948812482784231099240054350019"
** (nm-applet:5683): DEBUG: applet_common_device_state_changed
/usr/bin/compiz.real (cube) - Warn: Failed to load slide: 
/usr/share/gdm/themes/Human/ubuntu.png

In the failure case (2nd user), we have:

Checking for Software Rasterizer: present. 
Software rasterizer detected, abortingaborting and using fallback: 
/usr/bin/metacity 
Window manager warning: Failed to read saved session file 
/home/user2/.config/metacity/sessions/108c4cc618867bb54c1248296217745170089280019.ms:
 Failed to open file 
'/home/user2/.config/metacity/sessions/108c4cc618867bb54c1248296217745170089280019.ms':
 No such file or directory
Failed to play sound: Sound disabled

So the presence of the "Software Rasterizer" (presumably in the X
server) appears significant.

Going further to compare /var/log/Xorg.0.old (success) and
/var/log/Xorg.20.log (failure), the latter has the following lines
(there are other diffs preceding this that may be significant, see
attachment):

(II) [drm] DRM interface version 1.0
(EE) [drm] Could not set DRM device bus ID.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.

So, at least in my case, the problem appears to be that the second X
server is unable to initialise DRI (Direct Rendering Infrastructure --
acceleration), so the problem lies with the X server rather than within
Compiz. I guess this may be driver/hardware-specific? I have on-board
Intel G35 graphics.

Question: does this case (Compiz on two simultaneous X servers) work for
anyone, with any graphics hardware?

** Attachment added: "Diff between successful and failing /var/log/Xorg.NN.log"
   http://launchpadlibrarian.net/30391194/Xorg-log.diff

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

 suggests that inability to get
acceleration on more than one X server simultaneously is a well-known
issue with Intel graphics. However, I'm still searching for a more
convincing record of this known issue.

In the meantime, 
does suggest hope for the future: a comment from 2009-03-20 says "With
KMS and the current driver, thanks to Dave Airlie, you'll get multiple
servers with DRI support". (I don't know what that means in detail,
other than that perhaps it'll be fixed by Karmic. NB,
bugs.freedesktop.org uses an unusual SSL CA, so you may need to
temporarily install the root CA from
 just to follow that link! Grr.)

®om, do you have Intel graphics hardware?

** Bug watch added: freedesktop.org Bugzilla #19493
   https://bugs.freedesktop.org/show_bug.cgi?id=19493

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

Oh, and in answer to my question "does this case (Compiz on two
simultaneous X servers) work for anyone, with any graphics hardware?":
 suggests that it does.

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 392826] Re: dhcp3-server is launched before NetworkManager and thus doesn't find interfaces

[Jacob Nevins]

I'm also running into this.

I've bodged around it by putting the attached script in /etc/network/if-
up.d/dhcp3-server . I don't claim it's the best solution, or that it
should be included in the package, but it works for my situation (where
I have a single interface "eth0" explicitly listed in
/etc/default/dhcp3-server), so it might be a useful workaround for
others.

** Attachment added: "/etc/network/if-up.d/dhcp3-server : bodge around ordering 
problem, LP #392826"
   http://launchpadlibrarian.net/30401683/dhcp3-server

-- 
dhcp3-server is launched before NetworkManager and thus doesn't find interfaces
https://bugs.launchpad.net/bugs/392826
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 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

I've tried the kubuntu gutsy beta LiveCD, and I can't find any instances
of this duplication any more. Hurrah.

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Sitsofe: I haven't seriously tried anything later than Dapper, I'm
afraid.

(FWIW, I've been running with just "nolapic" since my previous comment
in June, with no problems.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

Re: [Bug 212711] [NEW] putty shutdown when trying to connect over http proxy

[Jacob Nevins]

> putty suddenly exit with the following error message when trying to
> connect over http proxy :
> 
> putty: ../unix/uxmisc.c:144: f_open: Assertion `mode[0] == 'w'' failed.
> Aborted (core dumped)

This can happen if you've enabled PuTTY's logging and it tries to append
to a file ('What to do if the log file already exists' either set to
'Always append to the end of it', or 'Ask the user every time' and the
user hit 'Append').

I don't think it's got anything to do with use of an HTTP proxy.

Can you confirm that this is what you're doing?

The bug I describe was introduced in 0.59 (r7084). It's happening
because PuTTY sets the 'is_private' flag to uxmisc.c:f_open() when
opening a log file, in an attempt to keep session logs private (because
that seemed like a good idea at the time; r7084 was mainly about
permissions on puttygen-generated keypairs). However, f_open() as
currently written fails the assertion above when presented with a file
mode of 'a' (append).

It's not clear to me what f_open() _should_ do in this situation
(although we shouldn't die, of course). The options are:

 - explicitly chmod the existing file to make it private (prevents users
   sharing a growing logfile);

 - carry on regardless of the existing file's permissions (risks
   disclosing sensitive data);

Or we could change our mind about session logs being private, and revert
to that being the user's responsibility.

> I am using hardy heron beta, and I am very up to date 
> 
> my kernel is 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686
> GNU/Linux, but the problem happened even at the previous kernel version
> (before I've updated)

I don't think any of those things is significant.

> -- 
> putty shutdown when trying to connect over http proxy
> https://bugs.launchpad.net/bugs/212711
> You received this bug notification because you are subscribed to putty
> in ubuntu.

-- 
putty shutdown when trying to connect over http proxy
https://bugs.launchpad.net/bugs/212711
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 67488] Re: tunnelling does not work

[Jacob Nevins]

I suspect http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist
/portfwd-addr-family.html is behind these reports. If so, a variety of
workarounds are detailed there.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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 48348] Re: kubuntu dapper LiveCD: various KDE things duplicated

[Jacob Nevins]

*** This bug is a duplicate of bug 40672 ***

This is still a problem on the Edgy LiveCD (I think you knew this, but
just in case...)

-- 
kubuntu dapper LiveCD: various KDE things duplicated
https://launchpad.net/bugs/48348

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

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Yes, I think so. I've run two long sessions recently (both around 14
hours) with just "nolapic" without problems. I think that the problem
would normally have become evident in that time. I will change the
default to just "nolapic" and see if any problems occur.

"nolapic" is certainly sufficient to change /proc/interrupts from "IO-
APIC-xxx" to "XT-PIC". I've been unable to distinguish it from "noapic
nolapic".

Something else that may (or may not) be relevant: I've just noticed that
the message "BIOS bug, local APIC #0 not detected!..." flashes up during
the boot sequence, at least with "nolapic". This does not happen with
neither "noapic" nor "nolapic". I don't know if it happens with both
enabled; it shows in dmesg but doesn't get as far as /var/log/messages,
and I haven't checked that combination recently. (I suppose this could
just be a poorly-worded message triggered directly by inclusion of
"nolapic"; I haven't checked the source.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 114918] autopano-complete cannot find Mono executables

[Jacob Nevins]

Public bug reported:

Binary package hint: autopano-sift

Package: autopano-sift
Version: 2.4-0ubuntu4
Severity: normal

/usr/bin/autopano-complete looks for generatekeys.exe on $PATH, but in
this package it resides in /usr/lib/autopano-sift/. autopano-complete
thus fails with an obscure error message ("dirname: missing operand").

The why: I've manually installed Hugin 0.7-beta4 (and its dependencies)
in /usr/local on a Dapper machine, but since the latest autopano-sift
was already packaged I thought I'd use it. This version of Hugin uses
autopano-complete, which fails as described above (it expects it to be
called "autopano-complete.sh", but that's easy to deal with). Putting
/usr/lib/autopano-sift on $PATH is a successful bodge.

There is a commented-out bit at the start of autopano-complete to use a
hardcoded path instead of "which", which looks like the Right Thing
here.

(While this bug is reported against the Dapper version, 2.4-0ubuntu4,
I've also verified that it applies to the latest, 0ubuntu5.)

-- System Information:
Debian Release: testing/unstable
  APT prefers dapper-updates
  APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-26-386
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages autopano-sift depends on:
ii  libgdiplus   1.1.13.6-0ubuntu2   interface library for Mono class S
ii  libglade2.0-cil  2.8.2-0ubuntu5  CLI binding for the Glade librarie
ii  libglib2.0-cil   2.8.2-0ubuntu5  CLI binding for the GLib utility l
ii  libgtk2.0-cil2.8.2-0ubuntu5  CLI binding for the GTK+ toolkit 2
ii  mono-classlib-1.01.1.13.6-0ubuntu3.2 Mono class library (1.0)
ii  mono-jit 1.1.13.6-0ubuntu3.2 fast CLI JIT/AOT compiler for Mono

autopano-sift recommends no packages.

-- no debconf information

** Affects: autopano-sift (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
autopano-complete cannot find Mono executables
https://bugs.launchpad.net/bugs/114918
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

I ran into this error message and problem straight after installing
Dapper. "irqpoll" didn't help me either (the machine hung hard instead).

I notice that your /proc/interrupts has a suspiciously round number. I
found that when an interrupt packed in (for me it was usually USB or
sound, with concomitant symptoms), the interrupt count displayed in
/proc/interrupts was *always* a multiple of 10 (and sometimes
implausibly large). For instance, see IRQs 11 and 185:

$ cat /proc/interrupts
   CPU0
  0:2455783IO-APIC-edge  timer
  1:   3979IO-APIC-edge  i8042
  7:  0IO-APIC-edge  parport0
  8:  3IO-APIC-edge  rtc
  9:  1   IO-APIC-level  acpi
 11: 20   IO-APIC-level  uhci_hcd:usb1, uhci_hcd:usb2
 12:  78674IO-APIC-edge  i8042
 14:  15828IO-APIC-edge  ide0
 15: 266079IO-APIC-edge  ide1
169:1080436   IO-APIC-level  nvidia
177:146   IO-APIC-level  eth0
185: 60   IO-APIC-level  Ensoniq AudioPCI
NMI:  0
LOC:2455610
ERR:  0
MIS:  0

For me, the workaround is to add "noapic nolapic" to my kernel command
line. (May be a sledgehammer to crack a nut, but it works. I got it from
Wikipedia, of all places.)

The motherboard is an MSI K7T Turbo2. (I can post lspci type spew if
anyone's interested.)

Hope this info helps somebody. This was very frustrating until I found
the workaround.

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

This appeared to be a LiveCD-specific issue. Are there even LiveCDs for gutsy 
yet?
(I've observed this on the dapper and edgy LiveCDs, but I haven't tried feisty.)

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

The described problem definitely exists (in Ubuntu and upstream).

** Summary changed:

- putty shutdown when trying to connect over http proxy
+ Assertion failure when appending to log file

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

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

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 271277] Re: Putty compiled with gtk-1.2 instead of gtk-2

[Jacob Nevins]

There hasn't yet been an upstream release of PuTTY with Gtk 2 support --
it's only available in code snapshots (which is what you've compiled). I
suspect the package maintainer won't want to package a snapshot, which
could have all sorts of things wrong with it.

The upstream record for Gtk 2 support is
, FWIW.

(@leibra: you probably need to install a bunch of -dev packages, on
Ubuntu. Not having stdio.h is fairly fatal!)

-- 
Putty compiled with gtk-1.2 instead of gtk-2
https://bugs.launchpad.net/bugs/271277
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 67488] Re: tunnelling does not work

[Jacob Nevins]

'portfwd-addr-family' is now fixed upstream (as of r8150). It would
probably be easy to backport the fix to 0.60, if that's desired.

@Stephen Northcutt: PuTTY's Event Log would probably be useful. If
you're using the GUI, Ctrl+right-click brings up a menu with it on (and
you can copy entries by selecting them); if you're using plink, add the
"-v" option.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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 67488] Re: tunnelling does not work

[Jacob Nevins]

'portfwd-addr-family' is now fixed upstream (as of r8150). It would
probably be easy to backport the fix to 0.60, if that's desired.

@Stephen Northcutt: PuTTY's Event Log would probably be useful. If
you're using the GUI, Ctrl+right-click brings up a menu with it on (and
you can copy entries by selecting them); if you're using plink, add the
"-v" option.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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

Re: [Bug 212711] [NEW] putty shutdown when trying to connect over http proxy

[Jacob Nevins]

> putty suddenly exit with the following error message when trying to
> connect over http proxy :
> 
> putty: ../unix/uxmisc.c:144: f_open: Assertion `mode[0] == 'w'' failed.
> Aborted (core dumped)

This can happen if you've enabled PuTTY's logging and it tries to append
to a file ('What to do if the log file already exists' either set to
'Always append to the end of it', or 'Ask the user every time' and the
user hit 'Append').

I don't think it's got anything to do with use of an HTTP proxy.

Can you confirm that this is what you're doing?

The bug I describe was introduced in 0.59 (r7084). It's happening
because PuTTY sets the 'is_private' flag to uxmisc.c:f_open() when
opening a log file, in an attempt to keep session logs private (because
that seemed like a good idea at the time; r7084 was mainly about
permissions on puttygen-generated keypairs). However, f_open() as
currently written fails the assertion above when presented with a file
mode of 'a' (append).

It's not clear to me what f_open() _should_ do in this situation
(although we shouldn't die, of course). The options are:

 - explicitly chmod the existing file to make it private (prevents users
   sharing a growing logfile);

 - carry on regardless of the existing file's permissions (risks
   disclosing sensitive data);

Or we could change our mind about session logs being private, and revert
to that being the user's responsibility.

> I am using hardy heron beta, and I am very up to date 
> 
> my kernel is 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686
> GNU/Linux, but the problem happened even at the previous kernel version
> (before I've updated)

I don't think any of those things is significant.

> -- 
> putty shutdown when trying to connect over http proxy
> https://bugs.launchpad.net/bugs/212711
> You received this bug notification because you are subscribed to putty
> in ubuntu.

-- 
putty shutdown when trying to connect over http proxy
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

The described problem definitely exists (in Ubuntu and upstream).

** Summary changed:

- putty shutdown when trying to connect over http proxy
+ Assertion failure when appending to log file

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

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

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 271277] Re: Putty compiled with gtk-1.2 instead of gtk-2

[Jacob Nevins]

There hasn't yet been an upstream release of PuTTY with Gtk 2 support --
it's only available in code snapshots (which is what you've compiled). I
suspect the package maintainer won't want to package a snapshot, which
could have all sorts of things wrong with it.

The upstream record for Gtk 2 support is
, FWIW.

(@leibra: you probably need to install a bunch of -dev packages, on
Ubuntu. Not having stdio.h is fairly fatal!)

-- 
Putty compiled with gtk-1.2 instead of gtk-2
https://bugs.launchpad.net/bugs/271277
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 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Yes, I think so. I've run two long sessions recently (both around 14
hours) with just "nolapic" without problems. I think that the problem
would normally have become evident in that time. I will change the
default to just "nolapic" and see if any problems occur.

"nolapic" is certainly sufficient to change /proc/interrupts from "IO-
APIC-xxx" to "XT-PIC". I've been unable to distinguish it from "noapic
nolapic".

Something else that may (or may not) be relevant: I've just noticed that
the message "BIOS bug, local APIC #0 not detected!..." flashes up during
the boot sequence, at least with "nolapic". This does not happen with
neither "noapic" nor "nolapic". I don't know if it happens with both
enabled; it shows in dmesg but doesn't get as far as /var/log/messages,
and I haven't checked that combination recently. (I suppose this could
just be a poorly-worded message triggered directly by inclusion of
"nolapic"; I haven't checked the source.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

This appeared to be a LiveCD-specific issue. Are there even LiveCDs for gutsy 
yet?
(I've observed this on the dapper and edgy LiveCDs, but I haven't tried feisty.)

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 48348] Re: kubuntu dapper LiveCD: various KDE things duplicated

[Jacob Nevins]

*** This bug is a duplicate of bug 40672 ***

This is still a problem on the Edgy LiveCD (I think you knew this, but
just in case...)

-- 
kubuntu dapper LiveCD: various KDE things duplicated
https://launchpad.net/bugs/48348

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

[Bug 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

Fixed upstream in r8461, by no longer attempting to keep the log file
private in any circumstances. (Which probably thus wants advertising in
the changelog.)

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 381288] Re: Character encoding setting saved in config doesn't stick

[Jacob Nevins]

This is a known bug upstream, and is believed fix as of svn r8592.

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

** Changed in: putty
   Status: New => Fix Committed

-- 
Character encoding setting saved in config doesn't stick
https://bugs.launchpad.net/bugs/381288
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

** Changed in: putty
   Status: Confirmed => Fix Committed

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 381288] Re: Character encoding setting saved in config doesn't stick

[Jacob Nevins]

It's only marked as "Fix Committed" in "PuTTY" (i.e. upstream). I don't
believe the Ubuntu package (i.e., "putty (Ubuntu)") has picked up the
fix yet.

-- 
Character encoding setting saved in config doesn't stick
https://bugs.launchpad.net/bugs/381288
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

This patch has also been committed to PuTTY upstream (r8516).

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

Confirmed upstream (0.60 and svn -- now fixed)

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

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

** Changed in: putty
   Status: New => Fix Committed

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 381288] Re: Character encoding setting saved in config doesn't stick

[Jacob Nevins]

This is a known bug upstream, and is believed fix as of svn r8592.

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

** Changed in: putty
   Status: New => Fix Committed

-- 
Character encoding setting saved in config doesn't stick
https://bugs.launchpad.net/bugs/381288
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

** Changed in: putty
   Status: Confirmed => Fix Committed

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 381288] Re: Character encoding setting saved in config doesn't stick

[Jacob Nevins]

It's only marked as "Fix Committed" in "PuTTY" (i.e. upstream). I don't
believe the Ubuntu package (i.e., "putty (Ubuntu)") has picked up the
fix yet.

-- 
Character encoding setting saved in config doesn't stick
https://bugs.launchpad.net/bugs/381288
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 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

I've tried the kubuntu gutsy beta LiveCD, and I can't find any instances
of this duplication any more. Hurrah.

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Sitsofe: I haven't seriously tried anything later than Dapper, I'm
afraid.

(FWIW, I've been running with just "nolapic" since my previous comment
in June, with no problems.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 67488] Re: tunnelling does not work

[Jacob Nevins]

I suspect http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist
/portfwd-addr-family.html is behind these reports. If so, a variety of
workarounds are detailed there.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

Fixed upstream in r8461, by no longer attempting to keep the log file
private in any circumstances. (Which probably thus wants advertising in
the changelog.)

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

This patch has also been committed to PuTTY upstream (r8516).

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

Confirmed upstream (0.60 and svn -- now fixed)

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

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

** Changed in: putty
   Status: New => Fix Committed

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 146680] Re: putty crashed with SIGSEGV in logevent()

[Jacob Nevins]

I think this must be down to the bug that was fixed upstream in r8304,
2008-11-17. I think that the backend (*telnet_closing():telnet) must
have been freed by notify_remote_exit(), leading to telnet->frontend
being NULL. (Or at least, I can't see how else telnet->frontend ended up
NULL.)

That fix will have first appeared in Ubuntu in putty 0.60+2009-04-05-1.
So, the current package should not have this bug.

-- 
putty crashed with SIGSEGV in logevent()
https://bugs.launchpad.net/bugs/146680
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 42410] Re: evince reports "incorrect format" for DVI files when no TeX distribution is installed.

[Jacob Nevins]

Still in Jaunty (evince 2.26.1-0ubuntu1).

-- 
evince reports "incorrect format" for DVI files when no TeX distribution is 
installed.
https://bugs.launchpad.net/bugs/42410
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

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

[Bug 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

I'm seeing a similar issue -- the user on the second simultaneously
started X server does not get Compiz effects. In fact they don't get any
3D acceleration at all, and there may also be problems with movie
playback.

Comparing ~/.xsession-errors for the two users, the point of divergence
is just after the following lines:

Checking for Composite extension: present.
Checking screen 1Comparing resolution (1680x1050) to maximum 3D texture size 
(2048): Passed.

In the success case (1st user), we have the following lines:

Checking for Software Rasterizer: Not present. 
Checking for nVidia: not present. 
Checking for FBConfig: present. 
running under gnome seesion, checking for gnomecompat
Checking for Xgl: not present. 
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 
image format
I/O warning : failed to load external entity 
"/home/user1/.compiz/session/10ea06d6867fce948812482784231099240054350019"
** (nm-applet:5683): DEBUG: applet_common_device_state_changed
/usr/bin/compiz.real (cube) - Warn: Failed to load slide: 
/usr/share/gdm/themes/Human/ubuntu.png

In the failure case (2nd user), we have:

Checking for Software Rasterizer: present. 
Software rasterizer detected, abortingaborting and using fallback: 
/usr/bin/metacity 
Window manager warning: Failed to read saved session file 
/home/user2/.config/metacity/sessions/108c4cc618867bb54c1248296217745170089280019.ms:
 Failed to open file 
'/home/user2/.config/metacity/sessions/108c4cc618867bb54c1248296217745170089280019.ms':
 No such file or directory
Failed to play sound: Sound disabled

So the presence of the "Software Rasterizer" (presumably in the X
server) appears significant.

Going further to compare /var/log/Xorg.0.old (success) and
/var/log/Xorg.20.log (failure), the latter has the following lines
(there are other diffs preceding this that may be significant, see
attachment):

(II) [drm] DRM interface version 1.0
(EE) [drm] Could not set DRM device bus ID.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.

So, at least in my case, the problem appears to be that the second X
server is unable to initialise DRI (Direct Rendering Infrastructure --
acceleration), so the problem lies with the X server rather than within
Compiz. I guess this may be driver/hardware-specific? I have on-board
Intel G35 graphics.

Question: does this case (Compiz on two simultaneous X servers) work for
anyone, with any graphics hardware?

** Attachment added: "Diff between successful and failing /var/log/Xorg.NN.log"
   http://launchpadlibrarian.net/30391194/Xorg-log.diff

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

 suggests that inability to get
acceleration on more than one X server simultaneously is a well-known
issue with Intel graphics. However, I'm still searching for a more
convincing record of this known issue.

In the meantime, 
does suggest hope for the future: a comment from 2009-03-20 says "With
KMS and the current driver, thanks to Dave Airlie, you'll get multiple
servers with DRI support". (I don't know what that means in detail,
other than that perhaps it'll be fixed by Karmic. NB,
bugs.freedesktop.org uses an unusual SSL CA, so you may need to
temporarily install the root CA from
 just to follow that link! Grr.)

®om, do you have Intel graphics hardware?

** Bug watch added: freedesktop.org Bugzilla #19493
   https://bugs.freedesktop.org/show_bug.cgi?id=19493

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

Oh, and in answer to my question "does this case (Compiz on two
simultaneous X servers) work for anyone, with any graphics hardware?":
 suggests that it does.

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 392826] Re: dhcp3-server is launched before NetworkManager and thus doesn't find interfaces

[Jacob Nevins]

I'm also running into this.

I've bodged around it by putting the attached script in /etc/network/if-
up.d/dhcp3-server . I don't claim it's the best solution, or that it
should be included in the package, but it works for my situation (where
I have a single interface "eth0" explicitly listed in
/etc/default/dhcp3-server), so it might be a useful workaround for
others.

** Attachment added: "/etc/network/if-up.d/dhcp3-server : bodge around ordering 
problem, LP #392826"
   http://launchpadlibrarian.net/30401683/dhcp3-server

-- 
dhcp3-server is launched before NetworkManager and thus doesn't find interfaces
https://bugs.launchpad.net/bugs/392826
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 114918] autopano-complete cannot find Mono executables

[Jacob Nevins]

Public bug reported:

Binary package hint: autopano-sift

Package: autopano-sift
Version: 2.4-0ubuntu4
Severity: normal

/usr/bin/autopano-complete looks for generatekeys.exe on $PATH, but in
this package it resides in /usr/lib/autopano-sift/. autopano-complete
thus fails with an obscure error message ("dirname: missing operand").

The why: I've manually installed Hugin 0.7-beta4 (and its dependencies)
in /usr/local on a Dapper machine, but since the latest autopano-sift
was already packaged I thought I'd use it. This version of Hugin uses
autopano-complete, which fails as described above (it expects it to be
called "autopano-complete.sh", but that's easy to deal with). Putting
/usr/lib/autopano-sift on $PATH is a successful bodge.

There is a commented-out bit at the start of autopano-complete to use a
hardcoded path instead of "which", which looks like the Right Thing
here.

(While this bug is reported against the Dapper version, 2.4-0ubuntu4,
I've also verified that it applies to the latest, 0ubuntu5.)

-- System Information:
Debian Release: testing/unstable
  APT prefers dapper-updates
  APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-26-386
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages autopano-sift depends on:
ii  libgdiplus   1.1.13.6-0ubuntu2   interface library for Mono class S
ii  libglade2.0-cil  2.8.2-0ubuntu5  CLI binding for the Glade librarie
ii  libglib2.0-cil   2.8.2-0ubuntu5  CLI binding for the GLib utility l
ii  libgtk2.0-cil2.8.2-0ubuntu5  CLI binding for the GTK+ toolkit 2
ii  mono-classlib-1.01.1.13.6-0ubuntu3.2 Mono class library (1.0)
ii  mono-jit 1.1.13.6-0ubuntu3.2 fast CLI JIT/AOT compiler for Mono

autopano-sift recommends no packages.

-- no debconf information

** Affects: autopano-sift (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
autopano-complete cannot find Mono executables
https://bugs.launchpad.net/bugs/114918
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

I ran into this error message and problem straight after installing
Dapper. "irqpoll" didn't help me either (the machine hung hard instead).

I notice that your /proc/interrupts has a suspiciously round number. I
found that when an interrupt packed in (for me it was usually USB or
sound, with concomitant symptoms), the interrupt count displayed in
/proc/interrupts was *always* a multiple of 10 (and sometimes
implausibly large). For instance, see IRQs 11 and 185:

$ cat /proc/interrupts
   CPU0
  0:2455783IO-APIC-edge  timer
  1:   3979IO-APIC-edge  i8042
  7:  0IO-APIC-edge  parport0
  8:  3IO-APIC-edge  rtc
  9:  1   IO-APIC-level  acpi
 11: 20   IO-APIC-level  uhci_hcd:usb1, uhci_hcd:usb2
 12:  78674IO-APIC-edge  i8042
 14:  15828IO-APIC-edge  ide0
 15: 266079IO-APIC-edge  ide1
169:1080436   IO-APIC-level  nvidia
177:146   IO-APIC-level  eth0
185: 60   IO-APIC-level  Ensoniq AudioPCI
NMI:  0
LOC:2455610
ERR:  0
MIS:  0

For me, the workaround is to add "noapic nolapic" to my kernel command
line. (May be a sledgehammer to crack a nut, but it works. I got it from
Wikipedia, of all places.)

The motherboard is an MSI K7T Turbo2. (I can post lspci type spew if
anyone's interested.)

Hope this info helps somebody. This was very frustrating until I found
the workaround.

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 67488] Re: tunnelling does not work

[Jacob Nevins]

'portfwd-addr-family' is now fixed upstream (as of r8150). It would
probably be easy to backport the fix to 0.60, if that's desired.

@Stephen Northcutt: PuTTY's Event Log would probably be useful. If
you're using the GUI, Ctrl+right-click brings up a menu with it on (and
you can copy entries by selecting them); if you're using plink, add the
"-v" option.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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 67488] Re: tunnelling does not work

[Jacob Nevins]

I suspect http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist
/portfwd-addr-family.html is behind these reports. If so, a variety of
workarounds are detailed there.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

I've tried the kubuntu gutsy beta LiveCD, and I can't find any instances
of this duplication any more. Hurrah.

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Sitsofe: I haven't seriously tried anything later than Dapper, I'm
afraid.

(FWIW, I've been running with just "nolapic" since my previous comment
in June, with no problems.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

Re: [Bug 212711] [NEW] putty shutdown when trying to connect over http proxy

[Jacob Nevins]

> putty suddenly exit with the following error message when trying to
> connect over http proxy :
> 
> putty: ../unix/uxmisc.c:144: f_open: Assertion `mode[0] == 'w'' failed.
> Aborted (core dumped)

This can happen if you've enabled PuTTY's logging and it tries to append
to a file ('What to do if the log file already exists' either set to
'Always append to the end of it', or 'Ask the user every time' and the
user hit 'Append').

I don't think it's got anything to do with use of an HTTP proxy.

Can you confirm that this is what you're doing?

The bug I describe was introduced in 0.59 (r7084). It's happening
because PuTTY sets the 'is_private' flag to uxmisc.c:f_open() when
opening a log file, in an attempt to keep session logs private (because
that seemed like a good idea at the time; r7084 was mainly about
permissions on puttygen-generated keypairs). However, f_open() as
currently written fails the assertion above when presented with a file
mode of 'a' (append).

It's not clear to me what f_open() _should_ do in this situation
(although we shouldn't die, of course). The options are:

 - explicitly chmod the existing file to make it private (prevents users
   sharing a growing logfile);

 - carry on regardless of the existing file's permissions (risks
   disclosing sensitive data);

Or we could change our mind about session logs being private, and revert
to that being the user's responsibility.

> I am using hardy heron beta, and I am very up to date 
> 
> my kernel is 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686
> GNU/Linux, but the problem happened even at the previous kernel version
> (before I've updated)

I don't think any of those things is significant.

> -- 
> putty shutdown when trying to connect over http proxy
> https://bugs.launchpad.net/bugs/212711
> You received this bug notification because you are subscribed to putty
> in ubuntu.

-- 
putty shutdown when trying to connect over http proxy
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

The described problem definitely exists (in Ubuntu and upstream).

** Summary changed:

- putty shutdown when trying to connect over http proxy
+ Assertion failure when appending to log file

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

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

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 271277] Re: Putty compiled with gtk-1.2 instead of gtk-2

[Jacob Nevins]

There hasn't yet been an upstream release of PuTTY with Gtk 2 support --
it's only available in code snapshots (which is what you've compiled). I
suspect the package maintainer won't want to package a snapshot, which
could have all sorts of things wrong with it.

The upstream record for Gtk 2 support is
, FWIW.

(@leibra: you probably need to install a bunch of -dev packages, on
Ubuntu. Not having stdio.h is fairly fatal!)

-- 
Putty compiled with gtk-1.2 instead of gtk-2
https://bugs.launchpad.net/bugs/271277
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 114918] autopano-complete cannot find Mono executables

[Jacob Nevins]

Public bug reported:

Binary package hint: autopano-sift

Package: autopano-sift
Version: 2.4-0ubuntu4
Severity: normal

/usr/bin/autopano-complete looks for generatekeys.exe on $PATH, but in
this package it resides in /usr/lib/autopano-sift/. autopano-complete
thus fails with an obscure error message ("dirname: missing operand").

The why: I've manually installed Hugin 0.7-beta4 (and its dependencies)
in /usr/local on a Dapper machine, but since the latest autopano-sift
was already packaged I thought I'd use it. This version of Hugin uses
autopano-complete, which fails as described above (it expects it to be
called "autopano-complete.sh", but that's easy to deal with). Putting
/usr/lib/autopano-sift on $PATH is a successful bodge.

There is a commented-out bit at the start of autopano-complete to use a
hardcoded path instead of "which", which looks like the Right Thing
here.

(While this bug is reported against the Dapper version, 2.4-0ubuntu4,
I've also verified that it applies to the latest, 0ubuntu5.)

-- System Information:
Debian Release: testing/unstable
  APT prefers dapper-updates
  APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-26-386
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages autopano-sift depends on:
ii  libgdiplus   1.1.13.6-0ubuntu2   interface library for Mono class S
ii  libglade2.0-cil  2.8.2-0ubuntu5  CLI binding for the Glade librarie
ii  libglib2.0-cil   2.8.2-0ubuntu5  CLI binding for the GLib utility l
ii  libgtk2.0-cil2.8.2-0ubuntu5  CLI binding for the GTK+ toolkit 2
ii  mono-classlib-1.01.1.13.6-0ubuntu3.2 Mono class library (1.0)
ii  mono-jit 1.1.13.6-0ubuntu3.2 fast CLI JIT/AOT compiler for Mono

autopano-sift recommends no packages.

-- no debconf information

** Affects: autopano-sift (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
autopano-complete cannot find Mono executables
https://bugs.launchpad.net/bugs/114918
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

I ran into this error message and problem straight after installing
Dapper. "irqpoll" didn't help me either (the machine hung hard instead).

I notice that your /proc/interrupts has a suspiciously round number. I
found that when an interrupt packed in (for me it was usually USB or
sound, with concomitant symptoms), the interrupt count displayed in
/proc/interrupts was *always* a multiple of 10 (and sometimes
implausibly large). For instance, see IRQs 11 and 185:

$ cat /proc/interrupts
   CPU0
  0:2455783IO-APIC-edge  timer
  1:   3979IO-APIC-edge  i8042
  7:  0IO-APIC-edge  parport0
  8:  3IO-APIC-edge  rtc
  9:  1   IO-APIC-level  acpi
 11: 20   IO-APIC-level  uhci_hcd:usb1, uhci_hcd:usb2
 12:  78674IO-APIC-edge  i8042
 14:  15828IO-APIC-edge  ide0
 15: 266079IO-APIC-edge  ide1
169:1080436   IO-APIC-level  nvidia
177:146   IO-APIC-level  eth0
185: 60   IO-APIC-level  Ensoniq AudioPCI
NMI:  0
LOC:2455610
ERR:  0
MIS:  0

For me, the workaround is to add "noapic nolapic" to my kernel command
line. (May be a sledgehammer to crack a nut, but it works. I got it from
Wikipedia, of all places.)

The motherboard is an MSI K7T Turbo2. (I can post lspci type spew if
anyone's interested.)

Hope this info helps somebody. This was very frustrating until I found
the workaround.

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 48348] Re: kubuntu dapper LiveCD: various KDE things duplicated

[Jacob Nevins]

*** This bug is a duplicate of bug 40672 ***

This is still a problem on the Edgy LiveCD (I think you knew this, but
just in case...)

-- 
kubuntu dapper LiveCD: various KDE things duplicated
https://launchpad.net/bugs/48348

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

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Yes, I think so. I've run two long sessions recently (both around 14
hours) with just "nolapic" without problems. I think that the problem
would normally have become evident in that time. I will change the
default to just "nolapic" and see if any problems occur.

"nolapic" is certainly sufficient to change /proc/interrupts from "IO-
APIC-xxx" to "XT-PIC". I've been unable to distinguish it from "noapic
nolapic".

Something else that may (or may not) be relevant: I've just noticed that
the message "BIOS bug, local APIC #0 not detected!..." flashes up during
the boot sequence, at least with "nolapic". This does not happen with
neither "noapic" nor "nolapic". I don't know if it happens with both
enabled; it shows in dmesg but doesn't get as far as /var/log/messages,
and I haven't checked that combination recently. (I suppose this could
just be a poorly-worded message triggered directly by inclusion of
"nolapic"; I haven't checked the source.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

This appeared to be a LiveCD-specific issue. Are there even LiveCDs for gutsy 
yet?
(I've observed this on the dapper and edgy LiveCDs, but I haven't tried feisty.)

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 42410] Re: evince reports "incorrect format" for DVI files when no TeX distribution is installed.

[Jacob Nevins]

Still in Jaunty (evince 2.26.1-0ubuntu1).

-- 
evince reports "incorrect format" for DVI files when no TeX distribution is 
installed.
https://bugs.launchpad.net/bugs/42410
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

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

[Bug 271277] Re: Putty compiled with gtk-1.2 instead of gtk-2

[Jacob Nevins]

There hasn't yet been an upstream release of PuTTY with Gtk 2 support --
it's only available in code snapshots (which is what you've compiled). I
suspect the package maintainer won't want to package a snapshot, which
could have all sorts of things wrong with it.

The upstream record for Gtk 2 support is
, FWIW.

(@leibra: you probably need to install a bunch of -dev packages, on
Ubuntu. Not having stdio.h is fairly fatal!)

-- 
Putty compiled with gtk-1.2 instead of gtk-2
https://bugs.launchpad.net/bugs/271277
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 146680] Re: putty crashed with SIGSEGV in logevent()

[Jacob Nevins]

I think this must be down to the bug that was fixed upstream in r8304,
2008-11-17. I think that the backend (*telnet_closing():telnet) must
have been freed by notify_remote_exit(), leading to telnet->frontend
being NULL. (Or at least, I can't see how else telnet->frontend ended up
NULL.)

That fix will have first appeared in Ubuntu in putty 0.60+2009-04-05-1.
So, the current package should not have this bug.

-- 
putty crashed with SIGSEGV in logevent()
https://bugs.launchpad.net/bugs/146680
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

I'm seeing a similar issue -- the user on the second simultaneously
started X server does not get Compiz effects. In fact they don't get any
3D acceleration at all, and there may also be problems with movie
playback.

Comparing ~/.xsession-errors for the two users, the point of divergence
is just after the following lines:

Checking for Composite extension: present.
Checking screen 1Comparing resolution (1680x1050) to maximum 3D texture size 
(2048): Passed.

In the success case (1st user), we have the following lines:

Checking for Software Rasterizer: Not present. 
Checking for nVidia: not present. 
Checking for FBConfig: present. 
running under gnome seesion, checking for gnomecompat
Checking for Xgl: not present. 
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 
image format
I/O warning : failed to load external entity 
"/home/user1/.compiz/session/10ea06d6867fce948812482784231099240054350019"
** (nm-applet:5683): DEBUG: applet_common_device_state_changed
/usr/bin/compiz.real (cube) - Warn: Failed to load slide: 
/usr/share/gdm/themes/Human/ubuntu.png

In the failure case (2nd user), we have:

Checking for Software Rasterizer: present. 
Software rasterizer detected, abortingaborting and using fallback: 
/usr/bin/metacity 
Window manager warning: Failed to read saved session file 
/home/user2/.config/metacity/sessions/108c4cc618867bb54c1248296217745170089280019.ms:
 Failed to open file 
'/home/user2/.config/metacity/sessions/108c4cc618867bb54c1248296217745170089280019.ms':
 No such file or directory
Failed to play sound: Sound disabled

So the presence of the "Software Rasterizer" (presumably in the X
server) appears significant.

Going further to compare /var/log/Xorg.0.old (success) and
/var/log/Xorg.20.log (failure), the latter has the following lines
(there are other diffs preceding this that may be significant, see
attachment):

(II) [drm] DRM interface version 1.0
(EE) [drm] Could not set DRM device bus ID.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.

So, at least in my case, the problem appears to be that the second X
server is unable to initialise DRI (Direct Rendering Infrastructure --
acceleration), so the problem lies with the X server rather than within
Compiz. I guess this may be driver/hardware-specific? I have on-board
Intel G35 graphics.

Question: does this case (Compiz on two simultaneous X servers) work for
anyone, with any graphics hardware?

** Attachment added: "Diff between successful and failing /var/log/Xorg.NN.log"
   http://launchpadlibrarian.net/30391194/Xorg-log.diff

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

 suggests that inability to get
acceleration on more than one X server simultaneously is a well-known
issue with Intel graphics. However, I'm still searching for a more
convincing record of this known issue.

In the meantime, 
does suggest hope for the future: a comment from 2009-03-20 says "With
KMS and the current driver, thanks to Dave Airlie, you'll get multiple
servers with DRI support". (I don't know what that means in detail,
other than that perhaps it'll be fixed by Karmic. NB,
bugs.freedesktop.org uses an unusual SSL CA, so you may need to
temporarily install the root CA from
 just to follow that link! Grr.)

®om, do you have Intel graphics hardware?

** Bug watch added: freedesktop.org Bugzilla #19493
   https://bugs.freedesktop.org/show_bug.cgi?id=19493

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 383753] Re: Multiple users cannot run desktop effects simultaneously

[Jacob Nevins]

Oh, and in answer to my question "does this case (Compiz on two
simultaneous X servers) work for anyone, with any graphics hardware?":
 suggests that it does.

-- 
Multiple users cannot run desktop effects simultaneously
https://bugs.launchpad.net/bugs/383753
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 392826] Re: dhcp3-server is launched before NetworkManager and thus doesn't find interfaces

[Jacob Nevins]

I'm also running into this.

I've bodged around it by putting the attached script in /etc/network/if-
up.d/dhcp3-server . I don't claim it's the best solution, or that it
should be included in the package, but it works for my situation (where
I have a single interface "eth0" explicitly listed in
/etc/default/dhcp3-server), so it might be a useful workaround for
others.

** Attachment added: "/etc/network/if-up.d/dhcp3-server : bodge around ordering 
problem, LP #392826"
   http://launchpadlibrarian.net/30401683/dhcp3-server

-- 
dhcp3-server is launched before NetworkManager and thus doesn't find interfaces
https://bugs.launchpad.net/bugs/392826
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 48348] Re: kubuntu dapper LiveCD: various KDE things duplicated

[Jacob Nevins]

*** This bug is a duplicate of bug 40672 ***

This is still a problem on the Edgy LiveCD (I think you knew this, but
just in case...)

-- 
kubuntu dapper LiveCD: various KDE things duplicated
https://launchpad.net/bugs/48348

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

Re: [Bug 212711] [NEW] putty shutdown when trying to connect over http proxy

[Jacob Nevins]

> putty suddenly exit with the following error message when trying to
> connect over http proxy :
> 
> putty: ../unix/uxmisc.c:144: f_open: Assertion `mode[0] == 'w'' failed.
> Aborted (core dumped)

This can happen if you've enabled PuTTY's logging and it tries to append
to a file ('What to do if the log file already exists' either set to
'Always append to the end of it', or 'Ask the user every time' and the
user hit 'Append').

I don't think it's got anything to do with use of an HTTP proxy.

Can you confirm that this is what you're doing?

The bug I describe was introduced in 0.59 (r7084). It's happening
because PuTTY sets the 'is_private' flag to uxmisc.c:f_open() when
opening a log file, in an attempt to keep session logs private (because
that seemed like a good idea at the time; r7084 was mainly about
permissions on puttygen-generated keypairs). However, f_open() as
currently written fails the assertion above when presented with a file
mode of 'a' (append).

It's not clear to me what f_open() _should_ do in this situation
(although we shouldn't die, of course). The options are:

 - explicitly chmod the existing file to make it private (prevents users
   sharing a growing logfile);

 - carry on regardless of the existing file's permissions (risks
   disclosing sensitive data);

Or we could change our mind about session logs being private, and revert
to that being the user's responsibility.

> I am using hardy heron beta, and I am very up to date 
> 
> my kernel is 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686
> GNU/Linux, but the problem happened even at the previous kernel version
> (before I've updated)

I don't think any of those things is significant.

> -- 
> putty shutdown when trying to connect over http proxy
> https://bugs.launchpad.net/bugs/212711
> You received this bug notification because you are subscribed to putty
> in ubuntu.

-- 
putty shutdown when trying to connect over http proxy
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

The described problem definitely exists (in Ubuntu and upstream).

** Summary changed:

- putty shutdown when trying to connect over http proxy
+ Assertion failure when appending to log file

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

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

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 271277] Re: Putty compiled with gtk-1.2 instead of gtk-2

[Jacob Nevins]

There hasn't yet been an upstream release of PuTTY with Gtk 2 support --
it's only available in code snapshots (which is what you've compiled). I
suspect the package maintainer won't want to package a snapshot, which
could have all sorts of things wrong with it.

The upstream record for Gtk 2 support is
, FWIW.

(@leibra: you probably need to install a bunch of -dev packages, on
Ubuntu. Not having stdio.h is fairly fatal!)

-- 
Putty compiled with gtk-1.2 instead of gtk-2
https://bugs.launchpad.net/bugs/271277
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 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

I've tried the kubuntu gutsy beta LiveCD, and I can't find any instances
of this duplication any more. Hurrah.

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Sitsofe: I haven't seriously tried anything later than Dapper, I'm
afraid.

(FWIW, I've been running with just "nolapic" since my previous comment
in June, with no problems.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 67488] Re: tunnelling does not work

[Jacob Nevins]

I suspect http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist
/portfwd-addr-family.html is behind these reports. If so, a variety of
workarounds are detailed there.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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 67488] Re: tunnelling does not work

[Jacob Nevins]

'portfwd-addr-family' is now fixed upstream (as of r8150). It would
probably be easy to backport the fix to 0.60, if that's desired.

@Stephen Northcutt: PuTTY's Event Log would probably be useful. If
you're using the GUI, Ctrl+right-click brings up a menu with it on (and
you can copy entries by selecting them); if you're using plink, add the
"-v" option.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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 48348] Re: kubuntu dapper LiveCD: various KDE things duplicated

[Jacob Nevins]

*** This bug is a duplicate of bug 40672 ***

This is still a problem on the Edgy LiveCD (I think you knew this, but
just in case...)

-- 
kubuntu dapper LiveCD: various KDE things duplicated
https://launchpad.net/bugs/48348

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

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Yes, I think so. I've run two long sessions recently (both around 14
hours) with just "nolapic" without problems. I think that the problem
would normally have become evident in that time. I will change the
default to just "nolapic" and see if any problems occur.

"nolapic" is certainly sufficient to change /proc/interrupts from "IO-
APIC-xxx" to "XT-PIC". I've been unable to distinguish it from "noapic
nolapic".

Something else that may (or may not) be relevant: I've just noticed that
the message "BIOS bug, local APIC #0 not detected!..." flashes up during
the boot sequence, at least with "nolapic". This does not happen with
neither "noapic" nor "nolapic". I don't know if it happens with both
enabled; it shows in dmesg but doesn't get as far as /var/log/messages,
and I haven't checked that combination recently. (I suppose this could
just be a poorly-worded message triggered directly by inclusion of
"nolapic"; I haven't checked the source.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

This appeared to be a LiveCD-specific issue. Are there even LiveCDs for gutsy 
yet?
(I've observed this on the dapper and edgy LiveCDs, but I haven't tried feisty.)

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 114918] autopano-complete cannot find Mono executables

[Jacob Nevins]

Public bug reported:

Binary package hint: autopano-sift

Package: autopano-sift
Version: 2.4-0ubuntu4
Severity: normal

/usr/bin/autopano-complete looks for generatekeys.exe on $PATH, but in
this package it resides in /usr/lib/autopano-sift/. autopano-complete
thus fails with an obscure error message ("dirname: missing operand").

The why: I've manually installed Hugin 0.7-beta4 (and its dependencies)
in /usr/local on a Dapper machine, but since the latest autopano-sift
was already packaged I thought I'd use it. This version of Hugin uses
autopano-complete, which fails as described above (it expects it to be
called "autopano-complete.sh", but that's easy to deal with). Putting
/usr/lib/autopano-sift on $PATH is a successful bodge.

There is a commented-out bit at the start of autopano-complete to use a
hardcoded path instead of "which", which looks like the Right Thing
here.

(While this bug is reported against the Dapper version, 2.4-0ubuntu4,
I've also verified that it applies to the latest, 0ubuntu5.)

-- System Information:
Debian Release: testing/unstable
  APT prefers dapper-updates
  APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-26-386
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages autopano-sift depends on:
ii  libgdiplus   1.1.13.6-0ubuntu2   interface library for Mono class S
ii  libglade2.0-cil  2.8.2-0ubuntu5  CLI binding for the Glade librarie
ii  libglib2.0-cil   2.8.2-0ubuntu5  CLI binding for the GLib utility l
ii  libgtk2.0-cil2.8.2-0ubuntu5  CLI binding for the GTK+ toolkit 2
ii  mono-classlib-1.01.1.13.6-0ubuntu3.2 Mono class library (1.0)
ii  mono-jit 1.1.13.6-0ubuntu3.2 fast CLI JIT/AOT compiler for Mono

autopano-sift recommends no packages.

-- no debconf information

** Affects: autopano-sift (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
autopano-complete cannot find Mono executables
https://bugs.launchpad.net/bugs/114918
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

I ran into this error message and problem straight after installing
Dapper. "irqpoll" didn't help me either (the machine hung hard instead).

I notice that your /proc/interrupts has a suspiciously round number. I
found that when an interrupt packed in (for me it was usually USB or
sound, with concomitant symptoms), the interrupt count displayed in
/proc/interrupts was *always* a multiple of 10 (and sometimes
implausibly large). For instance, see IRQs 11 and 185:

$ cat /proc/interrupts
   CPU0
  0:2455783IO-APIC-edge  timer
  1:   3979IO-APIC-edge  i8042
  7:  0IO-APIC-edge  parport0
  8:  3IO-APIC-edge  rtc
  9:  1   IO-APIC-level  acpi
 11: 20   IO-APIC-level  uhci_hcd:usb1, uhci_hcd:usb2
 12:  78674IO-APIC-edge  i8042
 14:  15828IO-APIC-edge  ide0
 15: 266079IO-APIC-edge  ide1
169:1080436   IO-APIC-level  nvidia
177:146   IO-APIC-level  eth0
185: 60   IO-APIC-level  Ensoniq AudioPCI
NMI:  0
LOC:2455610
ERR:  0
MIS:  0

For me, the workaround is to add "noapic nolapic" to my kernel command
line. (May be a sledgehammer to crack a nut, but it works. I got it from
Wikipedia, of all places.)

The motherboard is an MSI K7T Turbo2. (I can post lspci type spew if
anyone's interested.)

Hope this info helps somebody. This was very frustrating until I found
the workaround.

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

Fixed upstream in r8461, by no longer attempting to keep the log file
private in any circumstances. (Which probably thus wants advertising in
the changelog.)

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 40672] Re: Double help topics list in the Contents pane

[Jacob Nevins]

I've tried the kubuntu gutsy beta LiveCD, and I can't find any instances
of this duplication any more. Hurrah.

-- 
Double help topics list in the Contents pane
https://bugs.launchpad.net/bugs/40672
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 66820] Re: nobody cares about via interrupt

[Jacob Nevins]

Sitsofe: I haven't seriously tried anything later than Dapper, I'm
afraid.

(FWIW, I've been running with just "nolapic" since my previous comment
in June, with no problems.)

-- 
nobody cares about via interrupt
https://bugs.launchpad.net/bugs/66820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 67488] Re: tunnelling does not work

[Jacob Nevins]

'portfwd-addr-family' is now fixed upstream (as of r8150). It would
probably be easy to backport the fix to 0.60, if that's desired.

@Stephen Northcutt: PuTTY's Event Log would probably be useful. If
you're using the GUI, Ctrl+right-click brings up a menu with it on (and
you can copy entries by selecting them); if you're using plink, add the
"-v" option.

-- 
tunnelling does not work
https://bugs.launchpad.net/bugs/67488
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

Re: [Bug 212711] [NEW] putty shutdown when trying to connect over http proxy

[Jacob Nevins]

> putty suddenly exit with the following error message when trying to
> connect over http proxy :
> 
> putty: ../unix/uxmisc.c:144: f_open: Assertion `mode[0] == 'w'' failed.
> Aborted (core dumped)

This can happen if you've enabled PuTTY's logging and it tries to append
to a file ('What to do if the log file already exists' either set to
'Always append to the end of it', or 'Ask the user every time' and the
user hit 'Append').

I don't think it's got anything to do with use of an HTTP proxy.

Can you confirm that this is what you're doing?

The bug I describe was introduced in 0.59 (r7084). It's happening
because PuTTY sets the 'is_private' flag to uxmisc.c:f_open() when
opening a log file, in an attempt to keep session logs private (because
that seemed like a good idea at the time; r7084 was mainly about
permissions on puttygen-generated keypairs). However, f_open() as
currently written fails the assertion above when presented with a file
mode of 'a' (append).

It's not clear to me what f_open() _should_ do in this situation
(although we shouldn't die, of course). The options are:

 - explicitly chmod the existing file to make it private (prevents users
   sharing a growing logfile);

 - carry on regardless of the existing file's permissions (risks
   disclosing sensitive data);

Or we could change our mind about session logs being private, and revert
to that being the user's responsibility.

> I am using hardy heron beta, and I am very up to date 
> 
> my kernel is 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686
> GNU/Linux, but the problem happened even at the previous kernel version
> (before I've updated)

I don't think any of those things is significant.

> -- 
> putty shutdown when trying to connect over http proxy
> https://bugs.launchpad.net/bugs/212711
> You received this bug notification because you are subscribed to putty
> in ubuntu.

-- 
putty shutdown when trying to connect over http proxy
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

The described problem definitely exists (in Ubuntu and upstream).

** Summary changed:

- putty shutdown when trying to connect over http proxy
+ Assertion failure when appending to log file

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 212711] Re: Assertion failure when appending to log file

[Jacob Nevins]

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

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

-- 
Assertion failure when appending to log file
https://bugs.launchpad.net/bugs/212711
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

This patch has also been committed to PuTTY upstream (r8516).

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 360271] Re: fzsftp crashed with SIGSEGV in free()

[Jacob Nevins]

Confirmed upstream (0.60 and svn -- now fixed)

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

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

** Changed in: putty
   Status: New => Fix Committed

-- 
fzsftp crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/360271
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 381288] Re: Character encoding setting saved in config doesn't stick

[Jacob Nevins]

This is a known bug upstream, and is believed fix as of svn r8592.

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

** Changed in: putty
   Status: New => Fix Committed

-- 
Character encoding setting saved in config doesn't stick
https://bugs.launchpad.net/bugs/381288
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