Public bug reported:
Binary package hint: rdesktop
If rdesktop 1.6.0-2ubuntu1 is run under VNC (vnc4server or
tightvncserver) the keyboard mapping is broken: keys produce wrong
characters and modifiers may be ignored or assumed (e.g. with a finnish
keymap the '0' key should produce "0=}" with its
@Michael Lazarev: in my separate bug report, which was then marked as a
duplicate of this bug, I described some symptoms with the fi keymap
under VNC:
https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/381567
though they may not be the same or similar ones that ktp420 is concerned
about.
rdesktop is run inside a VNC session, i.e. connect from desktop with
vncviewer to a server running vncserver, and start rdesktop there. There
was no problem running rdesktop locally (without -y, I did not try with
-y as it worked without it).
I reported the effects of keypresses, perhaps in a conf
This might be a duplicate of
https://bugs.launchpad.net/ubuntu/karmic/+source/cairo/+bug/419143,
depending on whether the workaround in comment #56 fixes the issue for
the original reporter. I had a similar problem, i.e. printing from
evince failing silently without any error messages with Dell 510
This seems to only affect i386. On amd64 the linux-image-virtual
installs a -server kernel, which works fine as a Xen domU.
--
Kernel installed by linux-image-virtual isn't usable as Xen DomU kernel
https://bugs.launchpad.net/bugs/461127
You received this bug notification because you are a membe
Public bug reported:
Binary package hint: nut
After upgrading from Jaunty to Karmic, I noticed that UPS monitoring
with nut stopped working. It took me a few moments to figure it out, but
then I noticed that /etc/nut/nut.conf had a new timestamp and in it the
variable MODE was (once again) set to
Public bug reported:
gtimer segfaults at startup when run on precise beta, with the following
info from gdb:
Program received signal SIGSEGV, Segmentation fault.
create_main_window_menu_bar () at main.c:2055
2055g_message(gettext("Building menu Failed: %s \n"), err->message);
My gues
** Patch added: "patch to fix startup segfault"
https://bugs.launchpad.net/bugs/974038/+attachment/3007800/+files/fix-startup-segfault-on-precise.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I ran into this bug while testing Lubuntu precise.
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903490
Title:
Desktop Pager leaves ghost / phantom windows
To manage notific
I have this bug on Gentoo, running xterm under compiz, Radeon card with
gallium drivers. Before hardware upgrade the system had nVidia card with
nVidia's proprietary drivers, software otherwise the same, and it did
not have this bug.
When I have time I plan to try upgrading to Gentoo's unstable ve
I installed liblightdm-gobject-1-0_1.2.3-0ubuntu1 and
lightdm_1.2.3-0ubuntu1 on Precise with the following results:
* Timed autologin does not work at all with unity-greeter (though I see
it's still marked as "In Progress").
* When switched to lightdm-gtk-greeter, the user is authenticated after
Installed packages liblightdm-gobject-1-0_1.2.3-0ubuntu1,
lightdm_1.2.3-0ubuntu1 and unity-greeter_0.2.9-0ubuntu1. Timed autologin
works when using unity-greeter, but the following problems remain:
* Only works when lightdm service started, not after logout from a
session.
* No visual countdown/o
Public bug reported:
Version 1.2.3-0ubuntu1 of lightdm (in Precise) fixed timed autologin for
the initial startup (see bug #902852), but timed autologin still does
not work after logging out from a session.
It is logical that *immediate* autologin doesn't work after logout, but
the purpose of *ti
AllenS: you can try setting autologin-session=XBMC to see if it fixes
the wrong session problem. About the short timeout, I think that the
timeout starts when lightdm starts, and it starts the greeter afterwards
and on slower computers the greeter may not have enough time to get to
presenting the l
Public bug reported:
The /initrd.img symlink is created with absolute target path in Precise.
This makes accessing the latest initrd difficult if the rootfs in
question is not *our* rootfs (e.g. nfsroot server). In Lucid the target
path was relative, and so is the kernel path in Precise:
/initrd.
apport-collect not run: does not use $http_proxy
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020004
Title:
/initrd.img symlin
The package from precise-proposed works OK (very simple fix so no
surprise there).
** Description changed:
Impact: gtimer sometimes fails to start and crashes with a segfault
+
Fix: the code does not initialize a variable it later uses causing
memory corruption
+
TEST CASE:
+
s
Public bug reported:
The default route cannot be provided via DHCPv6, it must be obtained
from router advertisements. However, when using the dhcp method for
inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
will set net.ipv6.conf..accept_ra=0, resulting in no default
route for
** Description changed:
The default route cannot be provided via DHCPv6, it must be obtained
from router advertisements. However, when using the dhcp method for
inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
will set net.ipv6.conf..accept_ra=0, resulting in no defaul
Public bug reported:
This happens on precise with Gnome Classic session and compiz, does not
appear to happen with unity.
When there are three or more horizontal workspaces, a maximized window
is sent to the leftmost workspace in the row whenever a workspace that
is to the right of the maximized
I noticed a focus issue between workspace switches, but (at least for
me, on precise and gnome-classic) it does not have anything to do with
maximized/fullscreen: when switching to a workspace that has no
focusable windows (i.e. empty), the focus is retained on the window and
workspace switched fro
Just this Friday I got around to testing compiz 0.9.8.6 on Gentoo (mesa
upgrades did not help), and it fixes this bug for me. Unfortunately
0.9.8 on Gentoo has issues with several plugins not working correctly
(e.g. place windows not working at all, all windows open at top left
corner), so I'll hav
I ran into this bug on Gentoo. The patch 2 in
https://bugzilla.mozilla.org/show_bug.cgi?id=631518 seems to have fixed
this. That patch was also used to fix
https://bugs.launchpad.net/compiz/+bug/438868 so looks like this bug
should be fixed in Ubuntu (at least Lucid and Maverick).
Also, I found a
This bug is still present on my 32-bit Maverick, with Intel Q35 graphics
chipset. The stutter may not be as severe as the original reporter
described, but it is still there. This did not happen in Lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Sure, I can fix it in my systems, and have done so. But other users
using the default settings will still have a potential security
vulnerability in their systems.
And the X11 files is a case we know about; there might be other programs
using /tmp in a similar way (such as the TigerVNC case), and
Huh, I did not mean to report this for systemd but for tigervnc (only),
but looks like the "Report a bug" link at the top-right of an existing
bug forces the package, even though it later lets you specify the
affected package... Anyway, I guess it's ok now(?)
And yeah, I can fix it for myself but
Uh-oh, bad news: I just tested it, and looks like Xtigervnc does not
check the owner/permissions of the password file at runtime, so if/when
the /tmp/tigervnc.XX directory is removed, an attacker can hijack
the VNC session by recreating the directory and password file (I did not
test with other
I guess upstream in this case would be Debian, since the use of
/tmp/tigervnc.XX (and Wrapper.pm as a whole) is a Debian thing which
does not exist in upstream TigerVNC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Reported to Debian here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1087925
** Bug watch added: Debian Bug tracker #1087925
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087925
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
On Ubuntu 24.04.1, systemd 255.4-1ubuntu8.4, the fix for bug #2019026
causes files under /tmp to be removed if their age is greater than 30
days. However, there are files under /tmp that should not be removed at
runtime regardless of their age (whether they belong in that dire
Public bug reported:
(Ubuntu 24.04.1, TigerVNC 1.13.1+dfsg-2build2)
On startup, tigervncserver (via Wrapper.pm) copies ~/.vnc/passwd (and
other credential files) into /tmp/tigervnc.XX directory and tells
Xtigervnc to use those instead. There are at least two problems with
this:
1: On Ubuntu,
Also, full disclosure: I have the noatime mount option set for the root
filesystem, which certainly exacerbates the problem, e.g. the TigerVNC
issue would have been less likely (instead of certain) without noatime.
But noatime is not the cause of the problem: all the bad scenarios
listed are perfec
Now that I have had more time to ponder this issue, I realize that it is
also a security vulnerability. And spurred by the realization, I vaguely
recall coming across several articles in the past (some from before
systemd was a thing) about how automatic runtime cleaning of /tmp and
/var/tmp is (or
What @bluca says is mostly true and valid. But it is how things should
be, not how things actually are, and getting from the latter to the
former is easier said than done. E.g. with Xorg it *might* be
straightforward to fix the server and simple clients (i.e. those that
just call XOpenDisplay). But
34 matches
Mail list logo
