This missing kernel headers on our latest stable release madness...
I've been absolutely flooded with informal reports over a period of several months now of 12.10 being still broken with regards to proprietary drivers. Reports like this are typical, especially after the influx of steam users: "Installed ubuntu + proprietary amd drivers, got no unity at 800x600 on next reboot and uninstalled." The proximate cause is a combination of https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1068341 and https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1070427 But more worrisome is that this appears to be something we still haven't fixed for 12.10, even if the fix is a hackish ugly workaround such as forcing the install of the headers-generic pacakge in the additional drivers tool. I'm not sure what the underlying fix should be, but it is making me question if there's some sort of larger process issue here because we've managed to drop this on the floor for so long. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Patch pilot report 2013-02-21
On my shift today I got through the following: telepathy-logger (#1131079): some packaging fixes, upload gnome-system-monitor (#1130956): upload libpciaccess (#1124660): upload libxcb (#1129376): upload nvidia-graphics-drivers (#950963): upload dctrl-tools (#1129373): upload lp:~mterry/update-manager/toggle-fix: merged, but package build is broken; followed up in #1129191 lp:~gunnarhj/ubuntu/raring/language-selector/im-combobox: upload lp:~gunnarhj/ubuntu/raring/im-config/disable-im-switch: upload julius-voxforge (#1118159): upload lp:~jderose/ubuntu/raring/python3.3/fix-1131183: upload lp:~louis-bouchard/apport/apport_kdump-tools-blueprint: needs fixing Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Feedback on Upstart script for Synergy client
On 19 February 2013 06:22, Jason Heeris wrote: > I'm writing an Upstart job conf for the Synergy client[1]. Synergy > basically allows you to share a mouse and keyboard with another PC, > and it's useful to have it start up right from the moment there's a > graphical login screen. Typically people use lightdm scripts for this, > but I think an Upstart job would be more universal and easier to > distribute. > > I started by getting something that just works on my machine, and it's > included below; but a quick look at it will show that it's very > fragile, and specific to lightdm. So I'd like some advice on improving > it. Specifically: > > 1. For this to work under lightdm, I need to set XAUTHORITY to > '/var/run/lightdm/root/:0'. Is there a better way to do this? Is there > a DM independent way to do this, or do I need to detect whether it's > running under lightdm, gdm, kdm, etc. and take separate action for > each of them? > > 2. Synergy doesn't detect new devices or changes in resolution, so I > make it restart on as many graphics-related events as I can find. Are > any of those redundant with each other? Or deprecated? Have I missed > any? > > 3. Slurping the client address from a file in /etc seemed the simplest > possible way to get it. Are there problems with this? > > Of course, feel free to offer criticism on any other aspect of it too. > > /etc/init/synergyc.conf > # Synergy Client > # > # Starts the synergy client when an X session is up and running. > > description "Synergy Client" > author "Jason Heeris " > > start on (login-session-start > or drm-device-added > or drm-device-changed > or drm-device-removed > or graphics-device-added > or graphics-device-changed > or graphics-device-removed > or bdi-device-added > or bdi-device-changed > or bdi-device-removed) > Looks good, in ubiquity we use: start on (starting gdm or starting kdm or starting xdm or starting lxdm or starting lightdm) To cover more DMs. > stop on (drm-device-added > or drm-device-changed > or drm-device-removed > or graphics-device-added > or graphics-device-changed > or graphics-device-removed > or bdi-device-added > or bdi-device-changed > or bdi-device-removed) > > env XAUTHORITY=/var/run/lightdm/root/:0 > I have used the following hack instead script test -f /usr/share/acpi-support/power-funcs || exit 0 . /usr/share/acpi-support/power-funcs getXconsole test -n "$XAUTHORITY" || exit 0 ...(continue doing your things) Which will set XAUTHORITY environment variable, DISPLAY, user, etc. Regards, Dmitrijs. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Feedback on Upstart script for Synergy client
I'm writing an Upstart job conf for the Synergy client[1]. Synergy
basically allows you to share a mouse and keyboard with another PC,
and it's useful to have it start up right from the moment there's a
graphical login screen. Typically people use lightdm scripts for this,
but I think an Upstart job would be more universal and easier to
distribute.
I started by getting something that just works on my machine, and it's
included below; but a quick look at it will show that it's very
fragile, and specific to lightdm. So I'd like some advice on improving
it. Specifically:
1. For this to work under lightdm, I need to set XAUTHORITY to
'/var/run/lightdm/root/:0'. Is there a better way to do this? Is there
a DM independent way to do this, or do I need to detect whether it's
running under lightdm, gdm, kdm, etc. and take separate action for
each of them?
2. Synergy doesn't detect new devices or changes in resolution, so I
make it restart on as many graphics-related events as I can find. Are
any of those redundant with each other? Or deprecated? Have I missed
any?
3. Slurping the client address from a file in /etc seemed the simplest
possible way to get it. Are there problems with this?
Of course, feel free to offer criticism on any other aspect of it too.
/etc/init/synergyc.conf
# Synergy Client
#
# Starts the synergy client when an X session is up and running.
description "Synergy Client"
author "Jason Heeris "
start on (login-session-start
or drm-device-added
or drm-device-changed
or drm-device-removed
or graphics-device-added
or graphics-device-changed
or graphics-device-removed
or bdi-device-added
or bdi-device-changed
or bdi-device-removed)
stop on (drm-device-added
or drm-device-changed
or drm-device-removed
or graphics-device-added
or graphics-device-changed
or graphics-device-removed
or bdi-device-added
or bdi-device-changed
or bdi-device-removed)
env XAUTHORITY=/var/run/lightdm/root/:0
script
SYNERGY_HOST_FILE="/etc/synergy/client"
if [ -e "${SYNERGY_HOST_FILE}" ]; then
CLIENT_ADDR=$(cat "${SYNERGY_HOST_FILE}")
exec synergyc -f "${CLIENT_ADDR}"
fi
end script
Cheers,
Jason
[1] http://synergy-foss.org/
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
