Public bug reported:
Binary package hint: openswan
Contrary to what is said in the manpage for ipsec.conf, quote:
"leftnexthop: next-hop gateway IP address for the left participant’s
connection to the public network; [...] If the value is to be
overridden by the left=%defaultroute method (s
** Attachment added: "ipsec.conf file (anonymized) demonstrating the problem"
http://launchpadlibrarian.net/15692598/ipsec.conf.old
--
leftnexthop required even if left is %defaultroute
https://bugs.launchpad.net/bugs/244311
You received this bug notification because you are a member of Ubunt
Of course, /etc/ppp/ip-down has exactly the same problem.
Find attached a patch fixing this, too.
** Attachment added: "ip-down.patch"
http://launchpadlibrarian.net/15636537/ip-down.patch
--
Incorrect argument passing from ip-up to ip-up.local
https://bugs.launchpad.net/bugs/243384
You receiv
** Description changed:
The binary (i386) package for xl2tpd contains a directory /var/run/xl2tpd/.
This seems pretty futile since /var/run is cleared on each reboot, so the
newly-created directory persists only for the current session. After a reboot,
xl2tpd does not start anymore because
** Attachment added: "ip-up.patch"
http://launchpadlibrarian.net/15635954/ip-up.patch
--
Incorrect argument passing from ip-up to ip-up.local
https://bugs.launchpad.net/bugs/243384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: ppp
The startup script /etc/ppp/ip-up optionally calls another startup
script /etc/ppp/ip-up.local iff the latter exists and is executable.
However, it incorrectly passes its command line arguments on to ip-
up.local.
More precisely, line 47 in version 2
Public bug reported:
The binary (i386) package for xl2tpd contains a directory /var/run/xl2tpd/.
This seems pretty futile since /var/run is cleared on each reboot, so the
newly-created directory persists only for the current session. After a reboot,
xl2tpd does not start anymore because this dir
Today I tried xournal again with "Use XInput" deactivated (following
your suggestion above) and now most things seem to work almost as on
Feisty/Gutsy, except that the drawings aren't smooth as you already
noted.
I also checked against my Feisty installation of xournal (0.3.3) and
there the "Use X
Public bug reported:
Binary package hint: xournal
In the most recent version of xournal (0.4.1) on Hardy, most of xournal's tools
are broken.
In particular:
1) Pen & highlighter tool: Drawing / highlighting only becomes visible after
_releasing_ the mouse button.
2) Eraser tool: Sometime erases
Public bug reported:
The comment lines in /etc/X11/xorg.conf are missing the file and package name
on Hardy.
For example, the first line in xorg.conf on Hardy is:
# (xorg X Window System server configuration file)
whereas on Feisty it reads:
# /etc/X11/xorg.conf (xorg X Window System server conf
Public bug reported:
The metapackage "emacs-el" depends on "emacs21-el" in Hardy, whereas the latest
elisp source package is "emacs22-el".
N.B.: The latest emacs release installed via the metapackage "emacs" is
"emacs22", too, so this behaviour is inconsistent.
** Affects: emacs21 (Ubuntu)
** Attachment added: "Screenshot showing the "empty" terminal window during a
faulty session"
http://librarian.launchpad.net/7338341/Screenshot-1.png
--
Only first session works when Desktop effects are enabled
https://bugs.launchpad.net/bugs/107117
You received this bug notification because
Public bug reported:
Binary package hint: compiz
After the first session with desktop effects enabled has ended subsequent
sessions behave strangely if they have desktop effects switched on.
For example, terminal windows do not show any text (see attached screenshot),
many dialog boxes are miss
Public bug reported:
Binary package hint: gdm
When using Applications --> System Tools --> New Login to create a new
login screen, users with Desktop effects enabled cannot log in. For
users with Desktop effects disabled, everything works as usual.
How to reproduce:
0. Enable Desktop effects for
Sorry for so long without notice.
On my box this problem occurs with _every_ pdf file. I have no problems with
e.g. jpg files or so. As an example I attach one of the files for which I
verified that it doesn't open upon double-clicking (giving the cited error
message instead).
** Attachment add
Public bug reported:
When I double click on a PDF file (say somedoc.pdf) in Nautilus 2.16.1, instead
of opening the file in Evince a dialog box pops up saying
---
Cannot open ChomboDesign-1.4.pdf
The filename "ChomboDesign-1.4.pdf" indicates that
16 matches
Mail list logo
