Thank you for fixing this in libgrip. Could you also apply the necessary
change to geis?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276333
Title:
evince/eog crash when using untrusted X11
To
Public bug reported:
When starting eog/evince using 'ssh -X' with 'ForwardX11Trusted no' ond
12.04.4 startup is really slow (see log below) and closing the program
by clicking on the close button of the window manager button (x) does
not work (the window is responging error message pops up).
Public bug reported:
tk does not handle X11 errors correctly and fails with a xlib protocol error
when used over an untrusted X11
connection ('ssh -X' with config 'ForwardX11Trusted no'):
X Error of failed request: BadAccess (attempt to access private resource
denied)
Major opcode of
*** This bug is a duplicate of bug 1276333 ***
https://bugs.launchpad.net/bugs/1276333
** This bug has been marked a duplicate of bug 1276333
evince/eog crash when using untrusted X11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
evince/eog crash when using untrusted X11 connection (ssh -X with
ForwardX11Trusted no) .
Somehow geis-backend ends up being NULL in this case, and it crashes in
geis_backend_create_token which is called with a NULL argument from
geis_backend_token_new (geis.c). I am not
Public bug reported:
eog and evince crash in libgeis1 when started using a un-trusted X
connection (ForwardX11Trusted no in .ssh/config)
(gdb) run
Starting program: /usr/bin/eog
[Thread debugging using libthread_db enabled]
Using host libthread_db library
Public bug reported:
Binary package hint: linux-image-2.6.24-24-generic
System crashed under load.
Kernel package version: 2.6.24-24.53
May 12 15:27:05 nmr-fire2 kernel: [2484482.261216] qla2xxx :0a:02.0: LIP
reset occured (f704).
May 12 15:27:05 nmr-fire2 kernel: [2484482.286277]
Change status to avoid expiring. There is nothing which needs to be
confirmed.
** Changed in: ekiga (Ubuntu)
Status: Incomplete = Confirmed
--
support for symmetric NAT
https://bugs.launchpad.net/bugs/178743
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: network-manager-vpnc
When vpn is unable to connect to the vpn gateway it shows an error dialog. This
error dialogs are for some reason not shown at the top of other windows but
often hidden behind them where they silently accumulate until I find them
A hint to the advanced user that he might be able to resolve the issue by
configuring port forwarding as suggested in this other bug report, is certainly
usefull. But this it not always possible and can not be expected from a
nontechnical person. Skype is normally able to communicate in this
Hi,
The best solution is indeed a SIP proxy. But, Martin, you should
consider symmetric NAT is a minority of NAT. What you propose is setting
the outbound proxy in Ekiga as something like voip.ubuntu.com. This
will affect every Ekiga user, thus this will use much more bandwidth
than
Public bug reported:
Skype even works behind a symmetric NAT (by falling back to relaying the
data over a third party). Working with nearly every possible router
configuration without any hassle is one of the major advantages of Skype
over Ekiga. It would be nice if this situation could be
** Summary changed:
- better support for symmetric NAT
+ support for symmetric NAT
--
support for symmetric NAT
https://bugs.launchpad.net/bugs/178743
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: policycoreutils
The policy must be loaded early in the boot process
(before the real init is started by the init in the initramdisk).
At this time /usr might not be available yet.
** Affects: policycoreutils (Ubuntu)
Importance: Undecided
Public bug reported:
Binary package hint: network-manager
Somehow network-manager ( 0.6.5-0ubuntu7) started to hang while connecting to
my home network.
After checking with iwconfig I found out that the essid was set to some
different network while the
wireless key was correctly set. The
Am Mittwoch, den 04.07.2007, 13:53 + schrieb Sebastien Bacher:
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
Sorry, I can't reproduce
Public bug reported:
After upgrading to gutsy vpnc stopped working. The connection terminates
directly after
it is established (see debug output). The version 0.4,0-2ubuntu1 from feisty
works.
(BTW: network-manger gives no usefull information and the configure menu for
vpn stopped working in
Public bug reported:
Binary package hint: evolution
...don't know..
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Jul 4 12:35:58 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: cdrom
Package: evolution 2.11.4-0ubuntu1
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/8299290/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/8299291/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/8299292/ProcMaps.txt
** Attachment
19 matches
Mail list logo
