Bug#874701: Acknowledgement (RT3573 does not work on 4.12.x but works OK on 4.11.x)
The bug can be closed as it seams that the bug has been already fixed in the package linux-image-4.12.0-2-amd64. Whatever the WLAN device is working normal again.
Bug#874701: RT3573 does not work on 4.12.x but works OK on 4.11.x
Package: linux-image Version: 4.12.0-1-amd64 Bus 003 Device 006: ID 148f:3573 Ralink Technology, Corp. RT3573 Wireless Adapter This device does not work with the newest kernel 4.12. This bug has been fixed by Red Hat already. https://bugzilla.redhat.com/show_bug.cgi?id=1480829 Can we get this fix into the Debian distribution?
Bug#849568: aufs-dkms: dkms install fails
The DKMS module did not compile for me, when the patch 0003-enable-CONFIG_AUFS_EXPORT.patch has been enabled. But it worked well, after I commented out the $(error hier) line. config.mk 54c54 < $(error hier) --- > #$(error hier)
Bug#841348: Request to Steam to fix the issue
The issue is resolved in the package version 1.0.0.52-3.
Bug#841348: Request to Steam to fix the issue
This is not a bug in the Debian package, but an incompatibility of the
STEAM RUNTIME to the liggpg-error.so.0 library.
---
Dear Steam Support
I'm running Debian Linux amd64 SID, which the i386 libraries installed.
It seams an issue with the newest MESA libraries version 12.
gabriel@andromeda:~$ uname -r
4.8.0-1-amd64
gabriel@andromeda:~/.steam$ LIBGL_DEBUG=verbose steam
Running Steam on debian 64-bit
STEAM_RUNTIME is enabled automatically
[2016-11-06 14:48:41] Startup - updater built Sep 20 2016 18:20:24
SteamUpdateUI: An X Error occurred
X Error of failed request: BadValue (integer parameter out of range for
operation)
^C
The steam error.log did contain:
gabriel@andromeda:~/.steam$ cat error.log-2
/home/gabriel/.steam/steam.sh: Zeile 154: VERSION_ID ist nicht gesetzt.
rm: das Entfernen von '/home/gabriel/.steam/steam' ist nicht möglich:
Ist ein Verzeichnis
rm: das Entfernen von '/home/gabriel/.steam/bin' ist nicht möglich: Ist
ein Verzeichnis
/home/gabriel/.steam/steam.sh: Zeile 154: VERSION_ID ist nicht gesetzt.
/home/gabriel/.steam/steam.sh: Zeile 154: VERSION_ID ist nicht gesetzt.
grep: symbol lookup error: grep: undefined symbol: pcre_jit_stack_alloc
grep: symbol lookup error: grep: undefined symbol: pcre_jit_stack_alloc
grep: symbol lookup error: grep: undefined symbol: pcre_jit_stack_alloc
Installing breakpad exception handler for appid(steam)/version(1474415843)
libGL: Can't open configuration file /home/gabriel/.drirc: Datei oder
Verzeichnis nicht gefunden.
libGL: pci id for fd 7: 8086:0412, driver i965
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/i965_dri.so
libGL: dlopen /usr/lib/i386-linux-gnu/dri/i965_dri.so failed
(/lib/i386-linux-gnu/libgcrypt.so.20: symbol gpgrt_lock_lock, version
GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time
reference)
libGL: OpenDriver: trying ${ORIGIN}/dri/tls/i965_dri.so
libGL: OpenDriver: trying ${ORIGIN}/dri/i965_dri.so
libGL: dlopen ${ORIGIN}/dri/i965_dri.so failed
(/lib/i386-linux-gnu/libgcrypt.so.20: symbol gpgrt_lock_lock, version
GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time
reference)
libGL: OpenDriver: trying /usr/lib/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/dri/i965_dri.so
libGL: dlopen /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so:
Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht
gefunden)
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL: pci id for fd 7: 8086:0412, driver i965
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/i965_dri.so
libGL: dlopen /usr/lib/i386-linux-gnu/dri/i965_dri.so failed
(/lib/i386-linux-gnu/libgcrypt.so.20: symbol gpgrt_lock_lock, version
GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time
reference)
libGL: OpenDriver: trying ${ORIGIN}/dri/tls/i965_dri.so
libGL: OpenDriver: trying ${ORIGIN}/dri/i965_dri.so
libGL: dlopen ${ORIGIN}/dri/i965_dri.so failed
(/lib/i386-linux-gnu/libgcrypt.so.20: symbol gpgrt_lock_lock, version
GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time
reference)
libGL: OpenDriver: trying /usr/lib/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/dri/i965_dri.so
libGL: dlopen /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so:
Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht
gefunden)
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/swrast_dri.so
libGL: dlopen /usr/lib/i386-linux-gnu/dri/swrast_dri.so failed
(/lib/i386-linux-gnu/libgcrypt.so.20: symbol gpgrt_lock_lock, version
GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time
reference)
libGL: OpenDriver: trying ${ORIGIN}/dri/tls/swrast_dri.so
libGL: OpenDriver: trying ${ORIGIN}/dri/swrast_dri.so
libGL: dlopen ${ORIGIN}/dri/swrast_dri.so failed
(/lib/i386-linux-gnu/libgcrypt.so.20: symbol gpgrt_lock_lock, version
GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time
reference)
libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
libGL: dlopen /usr/lib/dri/swrast_dri.so failed
(/usr/lib/dri/swrast_dri.so: Kann die Shared-Object-Datei nicht öffnen:
Datei oder Verzeichnis nicht gefunden)
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Removing the the liggpg-error.so.0 from the STEAM RUNTIME libraries and
using the system libraries did resolve the error.
mv
./steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libgpg-error.so.0
Bug#775370: libegl1-mesa-drivers: Version 10.4.2-1 has no Multi Arch (i386/amd64) support
Package: libegl1-mesa-drivers Version: 10.4.2-1 Severity: important Tags: newcomer The current version 10.4.2-1 of the libegl1-mesa-drivers, does not have multi arch support. On multi arch systems i386/amd64 this produces this error (sorry, it is in german): Fehler traten auf beim Bearbeiten von: /home/gabriel/Downloads/libegl1-mesa-drivers_10.4.2-1_i386.deb andromeda:/var/cache/apt/archives# dpkg -i /home/gabriel/Downloads/libegl1 -mesa-drivers_10.4.2-1_i386.deb libegl1-mesa-drivers_10.4.2-1_amd64.deb dpkg: Fehler beim Bearbeiten des Archivs /home/gabriel/Downloads/libegl1-mesa- drivers_10.4.2-1_i386.deb (--install): libegl1-mesa-drivers:i386 10.4.2-1 (Multi-Arch: no) kann nicht zusammen mit libegl1-mesa-drivers installiert werden, welches mehrere installierte Instanzen hat dpkg: Fehler beim Bearbeiten des Archivs libegl1-mesa- drivers_10.4.2-1_amd64.deb (--install): libegl1-mesa-drivers:amd64 10.4.2-1 (Multi-Arch: no) kann nicht zusammen mit libegl1-mesa-drivers installiert werden, welches mehrere installierte Instanzen hat Fehler traten auf beim Bearbeiten von: /home/gabriel/Downloads/libegl1-mesa-drivers_10.4.2-1_i386.deb libegl1-mesa-drivers_10.4.2-1_amd64.deb As it is an traditional package, shouldn't it be removed automatcally? system:# apt-get remove --purge libegl1-mesa-drivers After a manual remove, everything is fine. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_CH.UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libegl1-mesa-drivers depends on: ii libc6 2.19-13 ii libdrm-nouveau2 2.4.58-2 ii libdrm-radeon12.4.58-2 ii libdrm2 2.4.58-2 ii libegl1-mesa 10.4.2-1 ii libelf1 0.159-4 ii libffi6 3.1-2+b2 ii libgbm1 10.4.2-1 ii libgcc1 1:4.9.2-10 ii libgl1-mesa-dri 10.4.2-1 ii libglapi-mesa 10.4.2-1 pn libllvm3.3none ii libopenvg1-mesa [libopenvg1] 10.3.2-1 ii libstdc++64.9.2-10 ii libudev1 215-9 ii libwayland-client01.6.0-2 ii libwayland-server01.6.0-2 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii multiarch-support 2.19-13 libegl1-mesa-drivers recommends no packages. libegl1-mesa-drivers suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: GDM3 Autologin
Got working gdm 3.8.4-3 for me. The issue was the enabled autologin. /etc/gdm3/daemon.conf: [daemon] # AutomaticLoginEnable = false # AutomaticLogin = Which seams to use su in background and run into the runtime_path bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: XDG_RUNTIME_DIR has incorrect value
Same issue for me after upgrading to gdm 3.8.4-3. A black screen after starting gdm, except if I chmod 777 /run/user/0. /var/log/gdm3/:0-slave.log: gdm-simple-slave[5325]: Failed to give slave programs access to the display. Trying to proceed. gdm-launch-environment][5358]: pam_env(gdm-launch-environment:session): Unable to open env file: /etc/environment: Datei oder Verzeichnis nicht gefunden gdm-launch-environment][5358]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) gdm-launch-environment][5358]: pam_systemd(gdm-launch-environment:session): Asking logind to create session: uid=115 pid=5358 service=gdm-launch-environment type=x11 class=greeter seat=seat0 vtnr=7 tty= display=:0 remote=no remote_user= remote_host= gdm-launch-environment][5358]: pam_systemd(gdm-launch-environment:session): Reply from logind: id=c1 object_path=/org/freedesktop/login1/session/c1 runtime_path=/run/user/0 session_fd=13 seat=seat0 vtnr=1 gdm-launch-environment][5358]: pam_ck_connector(gdm-launch-environment:session): nox11 mode, ignoring PAM_TTY :0 gdm3][5591]: pam_env(gdm3:session): Unable to open env file: /etc/environment: Datei oder Verzeichnis nicht gefunden gdm3][5591]: pam_unix(gdm3:session): session opened for user gabriel by (uid=0) gdm3][5591]: pam_systemd(gdm3:session): Asking logind to create session: uid=1000 pid=5591 service=gdm3 type=x11 class=user seat=seat0 vtnr=7 tty= display=:0 remote=no remote_user= remote_host= gdm3][5591]: pam_systemd(gdm3:session): Reply from logind: id=c1 object_path=/org/freedesktop/login1/session/c1 runtime_path=/run/user/0 session_fd=15 seat=seat0 vtnr=1 gdm3][5591]: pam_ck_connector(gdm3:session): nox11 mode, ignoring PAM_TTY :0 gdm-launch-environment][5358]: pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm gdm-simple-slave[5325]: Failed to remove slave program access to the display. Trying to proceed. gdm-simple-slave[5325]: Child process -5369 was already dead. gdm3][5591]: pam_unix(gdm3:session): session closed for user gabriel gdm-simple-slave[5325]: GLib-GObject: g_object_ref: assertion `object-ref_count 0' failed gdm-simple-slave[5325]: GLib-GObject: g_object_unref: assertion `object-ref_count 0' failed If I login with my user account, I still get the wrong runtime_path. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: g_get_user_runtime_dir () bug
Dear all
This must be a bug in the function g_get_user_runtime_dir () relating
Glib. I have wrote a small piece of code:
user@machine:~/Work$ cat run.c
#include glib.h
void main()
{
g_printf(%s\n, g_get_user_runtime_dir ());
}
user@machine:~/Work$ gcc `pkg-config --cflags --libs glib-2.0` -o run run.c
user@machine:~/Work$ ./run
/run/user/0
Which should be /run/user/1000 for my user!
Regards,
Gabriel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: XDG_RUNTIME_DIR has incorrect value
What's your $XDG_RUNTIME_DIR environment variable? My $XDG_RUNTIME_DIR as user gabriel (uid=1000) is /run/user/0 and should in my opinion be /run/user/1000. If it's /run/user/0, then GLib is behaving as expected, and the bug is in some other component (which should either not set this variable, unset this variable when it switches uid, or set this variable to a more appropriate value for uid 1000). I agree that Glib is working correctly. user@machine:~/Work$ echo $XDG_RUNTIME_DIR /run/user/0 user@machine:~/Work$ ./run /run/user/0 user@machine:~/Work$ XDG_RUNTIME_DIR=/run/user/1000 user@machine:~/Work$ export XDG_RUNTIME_DIR user@machine:~/Work$ echo $XDG_RUNTIME_DIR /run/user/1000 user@machine:~/Work$ ./run /run/user/1000 user@machine:~/Work$ unset XDG_RUNTIME_DIR user@machine:~/Work$ ./run /home/gabriel/.cache What seems related is the but in gdm3 which fails to start when libpam-systemd is not installed [1]. libpam-systemd is responsible for creating and setting XDG_RUNTIME_DIR. So I assume Gabriel didn't have this package installed. Is that correct? No, libpam-systemd is installed correctly on my system. user@machine:~/Work$ dpkg -s libpam-systemd Package: libpam-systemd Status: install ok installed Priority: optional Section: admin Installed-Size: 64 Maintainer: Debian systemd Maintainers pkg-systemd-maintain...@lists.alioth.debian.org Architecture: i386 Multi-Arch: same Source: systemd Version: 204-5 So from a cursory look, it seems like glib is behaving correctly and as Simon suspects, some other component simply sets XDG_RUNTIME_DIR to an incorrect value. I agree. Some other relevant info: * is this in X11 or at a text virtual console? This is in X11. * if in X11, which display manager (gdm3, lightdm, xdm, kdm, etc.), or did you use startx or something from a text virtual console? Currently I get with gdm3 only a black screen. So my only possibility is to chmod my /run/user/0 directory. Switch with su - gabriel to my account and execute startx. * are you using systemd or sysvinit as your init (process 1)? # ps ax PID TTY STAT TIME COMMAND 1 ?Ss 0:01 init [2] Should be the good old sysvinit. Never changed to systemd. * which PAM modules do you have (dpkg-query -W 'libpam*'), and have you reconfigured the PAM stack or are you using defaults? # dpkg-query -W 'libpam*' libpam-cap:i386 1:2.22-1.2 libpam-ck-connector:i3860.4.6-3+b1 libpam-dev libpam-doc libpam-gnome-keyring3.8.2-2 libpam-mkhomedir libpam-modules:i386 1.1.3-10 libpam-modules-bin 1.1.3-10 libpam-motd libpam-mount libpam-runtime 1.1.3-10 libpam-smbpass libpam-ssh libpam-systemd:i386 204-5 libpam-umask libpam0g:i386 1.1.3-10 libpam0g-dev:i386 1.1.3-10 libpam0g-util I have found out, if I do login on tty1 and stop gdm3. And do a login on tty2 direct as user the XDG_RUNTIME_DIR variable is set correctly /run/user/1000. I can start X with the command startx without any changes. But if I switch the user from root with su - gabriel the XDG_RUNTIME_DIR variable remains on /run/user/0. This could may be an issue for gdm3, when switching user context. Changed in file /etc/pam.d/common-session session optionalpam_systemd.so to session optionalpam_systemd.so debug=1 Set following output in /var/log/auth.log Oct 23 15:08:03 machine su[5608]: Successful su for gabriel by root Oct 23 15:08:03 machine su[5608]: + /dev/tty1 root:gabriel Oct 23 15:08:03 machine su[5608]: pam_env(su:session): Unable to open env file: /etc/environment: Datei oder Verzeichnis nicht gefunden Oct 23 15:08:03 machine su[5608]: pam_unix(su:session): session opened for user gabriel by root(uid=0) Oct 23 15:08:03 machine su[5608]: pam_systemd(su:session): Asking logind to create session: uid=1000 pid=5608 service=su type=tty class=user seat=seat0 vtnr=1 tty=/dev/tty1 display= remote=no remote_user=root remote_host= Oct 23 15:08:03 machine su[5608]: pam_systemd(su:session): Reply from logind: id=c1 object_path=/org/freedesktop/login1/session/c1 runtime_path=/run/user/0 session_fd=6 seat=seat0 vtnr=1 Oct 23 15:09:01 machine CRON[5680]: pam_env(cron:session): Unable to open env file: /etc/environment: Datei oder Verzeichnis nicht gefunden The runtime_path is set to /run/user/0. Don't know if this is correct or wrong. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: XDG_RUNTIME_DIR has incorrect value
On 23.10.2013 16:18, Simon McVittie wrote:
Making /run/user/${UID} writable by users other than ${UID} is probably
a security vulnerability, so I would advise not doing that.
If course not. This is only a workaround to get X working again. But
login direct as user avoid this workaround anyway.
Oct 23 15:08:03 machine su[5608]: pam_unix(su:session): session opened
for user gabriel by root(uid=0)
Oct 23 15:08:03 machine su[5608]: pam_systemd(su:session): Asking logind
to create session: uid=1000 pid=5608 service=su type=tty class=user
seat=seat0 vtnr=1 tty=/dev/tty1 display= remote=no remote_user=root
remote_host=
Oct 23 15:08:03 machine su[5608]: pam_systemd(su:session): Reply from
logind: id=c1 object_path=/org/freedesktop/login1/session/c1
runtime_path=/run/user/0 session_fd=6 seat=seat0 vtnr=1
That doesn't look right - shouldn't systemd-logind be returning
/run/user/1000 here? This might be a systemd-logind bug.
The same behavior is described in this case:
https://bugzilla.redhat.com/show_bug.cgi?id=753882
In my opinion this is a bug from systemd. Of course
su user
should preserve the environment variables, but
su - user
not.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: XDG_RUNTIME_DIR has incorrect value
Created a bug report for systemd. https://bugs.freedesktop.org/show_bug.cgi?id=70810. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#476929: Python rtupdate does not work with boa-constructor
Package: python
Version: 2.5.2-1
Distribution: sid
The python package can not be installed, when the package
boa-constructor (Version: 0.6.1-3) is installed.
# dpkg -i Desktop/python_2.5.2-1_all.deb
(Reading database ... 264231 files and directories currently installed.)
Preparing to replace python 2.5.2-1 (using
Desktop/python_2.5.2-1_all.deb) ...
Ignoring nonregistered document `python-policy'
Unpacking replacement python ...
Setting up python (2.5.2-1) ...
running python rtupdate hooks for python2.5...
Compiling /usr/share/boa-constructor/ZopeLib/zoa/metatypes.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/metatypes.py, line 13
return obj.objectMap()
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/subobj_.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/subobj_.py, line 17
return subobj
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/DBAdapter.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/props/DBAdapter.py, line 10
return {'title': context.title,
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/User.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/props/User.py, line 12
return {'id': user.getId(),
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/DTMLMethod.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/props/DTMLMethod.py,
line 12
return {'title': meth.title,
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/ExternalMethod.py ...
File
/usr/share/boa-constructor/ZopeLib/zoa/props/ExternalMethod.py, line 12
return {'title':meth.title,
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/MailHost.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/props/MailHost.py, line 11
return {'title': ctx.title,
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/SiteErrorLog.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/props/SiteErrorLog.py,
line 12
return context.aq_parent.aq_parent.getProperties()
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/SQLMethod.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/props/SQLMethod.py, line 10
return {'connection_id': context.connection_id,
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/props/PageTemplate.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/props/PageTemplate.py,
line 12
return {'title': pt.title,
SyntaxError: 'return' outside function
Compiling
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/move_field.py ...
File
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/move_field.py,
line 14
return ctx.manage_move_field_up(group, REQ)
SyntaxError: 'return' outside function
Compiling
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/GroupedFields.py ...
File
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/GroupedFields.py,
line 17
return result
SyntaxError: 'return' outside function
Compiling
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/Form.py ...
File
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/Form.py, line 12
return {'title': ctx.title,
SyntaxError: 'return' outside function
Compiling
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/Field.py ...
File
/usr/share/boa-constructor/ZopeLib/zoa/props/Formulator/Field.py, line 27
return fields
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/docsrc.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/docsrc.py, line 10
return context.aq_parent.document_src()
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/iconpath.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/iconpath.py, line 10
return context.aq_parent.icon
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/find.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/find.py, line 22
return [(obj.meta_type, id) for id, obj in results]
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/filteredmetatypes.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/filteredmetatypes.py,
line 10
return context.aq_parent.filtered_meta_types()
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/ownerinfo.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/ownerinfo.py, line 13
try: return obj.owner_info()
SyntaxError: 'return' outside function
Compiling /usr/share/boa-constructor/ZopeLib/zoa/proxyroles.py ...
File /usr/share/boa-constructor/ZopeLib/zoa/proxyroles.py, line 16
return res
SyntaxError: 'return' outside function
Compiling
Bug#458525: Problem with default card when cx88_alsa module is used
Package: alsa-base Version: 1.0.15-3 Severity: minor In the modprobe file from the alsa-base /etc/modprobe.d/alsa-base, is an option configured to ensure that the snd-cx88_alsa module is not grabbing the index 0. But this is not working, because the module was renamed. I have changed: options snd-cx88_alsa index=-2 to options cx88_alsa index=-2 See also this Ubuntu Bug: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/126864 I am using Debian GNU/Linux sid, kernel 2.6.23-1-686 and libc6 2.7-5. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#311015: System root incorrectly reset to first partition
Package: grubconf Version: 0.5.1-4 When an Linux boot entry is modified, grubconf reset the system root to /dev/hda1. That makes the configuration unuseful. It seems to be an known error: http://sourceforge.net/tracker/index.php?func=detailaid=1146271group_id=17229atid=117229 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
