Bug#1008900: solved in 5.17 upstream
Hello again, My git bisect conclusion was right. The faulty commit has been reverted in linux 5.17: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.17/revert-swiotlb-rework-fix-info-leak-with-dma_from_device.patch Waiting for 5.17. Regards
Bug#1008900: probably ath9k related
On Sun, 3 Apr 2022 21:17:25 +0200 Pascal Dormeau wrote: > Hello, > > I have the same problem tonight with linux-5.16.0-5-amd64 although > it perfectly worked during the previous days. > > It could be a hardware problem, I will try to change the mini pci-e > adapter and see if it improves the situation. > > This bug can be closed as there is no evidence that is a software > problem. Sorry for the noise. Hello again, I withdraw what I wrote above. I have another laptop with an atheros adapter using ath9k. As it runs Testing, the linux-5.16.0-6-amd64 package was installed today and connection problems start occuring after reboot on the new kernel. The message from wpasupplicant is: "CTRL-EVENT-BEACON-LOSS" (repeatedly). Going back to linux-5.16.0-5-amd64 solves the issue. I believe it is a problem with ath9k driver. I tested other adapters with drivers like rtl8192cu (usb), rt2870 (usb) or iwlwifi (pci-e) and everything works smooth. Regards
Bug#1008900: Problem also with linux-5.16.0-5-amd64
Hello, I have the same problem tonight with linux-5.16.0-5-amd64 although it perfectly worked during the previous days. It could be a hardware problem, I will try to change the mini pci-e adapter and see if it improves the situation. This bug can be closed as there is no evidence that is a software problem. Sorry for the noise. Best regards --
Bug#950174: gvfs-udisks2-volume-monitor.service crashes: No GSettings schemas are installed on the system
Hello, I do not know if the following can help. So just in case. I met the same problem recently on a xfce4 setup. Digging in the bug reports I found this one that matches the same error messages I had. I finally solved my problem noticing that it happened after modifying the XDG_DATA_DIRS variable and after some some paths in that variable were deleted on my system. Removing the non-existing paths from XDG_DATA_DIRS variable solved my problem. Therefore, it might be worth verifying if all paths in the XDG_DATA_DIRS actually exit (or can be accessed). Best regards Pascal
Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version
On Mon, 12 Oct 2020 10:47:47 +0200 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst? = wrote: > tags 971584 + pending > thanks > The issue with the /var/lock/sane directory is fixed with > > commit736573a8db4bd098da28a4831ce4c601f880aacd > Hello Jörg, I tested the change in the commit but it did not work for me : - with systemd, the /var/lock/sane directory does not survive a reboot because /var/lock is volatile (/var/lock is a link to /var/run, see /usr/lib/tmpfiles.d/legacy.conf). I solved this by creating a tmpd-file with: d /var/lock/sane 0775root scanner - - in it - but it is not enough, I had to put myself in the scanner group, something I did not need with 1.0.27 version. By the way, why giving /var/lock/sane rights to "saned" exclusively instead of "scanner" ? (It is just a question, I do not know myself the right thing to do). The saned group is created when installing sane-utils and by default sane-utils adds "saned" to the scanner group. Moreover, sane-utils is not always installed (not necessary for a local scanner accessed by a client like simple-scan). Best regards Pascal
Bug#971693: webext-ublock-origin-firefox not compatible with non-empty user.js file
On Mon, 5 Oct 2020 21:02:09 +0200 Markus Koschany wrote: > Hello, Hello Markus, Thanks for replying. > I have searched for a solution for this kind of problem but the more I > dig into it the more I come to the conclusion that this kind of > behavior is intentional. If you normally install addons via Firefox' > addon feature, Firefox will tell you to restart the browser when you > make an upgrade. It is comparable to Debian upgrades, some of them > may require a restart and it can't be avoided. > > Regarding the user.js file: I have just created one in my profile > directory with a single line to change a setting, but I couldn't > reproduce this problem on Firefox 78.3 with uBo 1.30.0 in stable. My > workaround would be: save all your uBo settings (if you have made any > changes, better safe than sorry), shut down Firefox, then remove > user.js. Then restart Firefox and try to enable/disable the addon > again. Afterwards you can readd your custom user.js file. If I do this with my current profile, it fails, even before re-enabling the custom user.js file. If I create a fresh new profile, uBo is active. Then I close the browser and copy the preferences I need directly to the pref.js file at the end (instead of user.js), and restart the browser: - the preferences are accepted (checked in about:config), - and uBo remains active. But if after I create a user.js file with one only single preference, even with a default one like browser.cache.disk.enable (set to true), it fails. And surprisingly, it fails again after removing the user.js file. It seems to be related to the user.js file whatever the preferences inside. And is irreversible. It can be circumvented by adding all custom preferences to the pref.js only (and saving the most important one elsewhere) without creating a user.js file. > > If you send me your user.js file I can try to reproduce the problem in > unstable tomorrow. Any preference triggers the problem and one is enough. You can test this one for example (I gave another example above): user_pref("browser.tabs.tabMinWidth", 80); If you do this, consider to use a fresh new profile. > > There is also an addon debug mode for Firefox. This one allows you to > skip restarts and you can make modifications to Firefox and your addon > which get instantly applied. I will try that, but the most likely, I will stick to the normal addon from the addon firefox feature. Just one more remark: I met the same problem with webext-keepassxc-browser since 81.0 firefox version. Best regards Pascal
Bug#901789: mesa: white screen when running Xfwm4 with compositing
On Mon, 18 Jun 2018 14:06:10 +0200 Yves-Alexis Perez > since the upgrade from 18.0.5-1 to 18.1.1-1 of the various mesa > packages, xfwm4 with compositing enabling only display a white screen. > The cursor is shown on top, but no window appears. When restarting > xfwm4 I can briefly see the windows, then the white screen. > > Disabling compositing in xfwm4 workarounds the problem but then you > lose all compositing-related features. Hello, Not sure it helps, but I observe the same here (xfwm4 with compositing + mesa 18.1.1-1 fail, and a white screen is displayed) but only with xfwm4 in experimental (4.13.0-1). Unstable version (4.12.4-1) is perfectly fine with mesa 18.1.1-1 (intel graphics HD4000, CPU generation is Ivy Bridge, and modesetting driver is used). Yves-Alexis, which xfwm4 version do you use ? Best regards, Pascal Dormeau
Bug#851492: [systemd] tmpfs size mount option not correct when expressed in %
Package: systemd Version: 232-10 Severity: normal Dear maintainer, Systemd does not mount tmpfs file systems with the correct size when the size is expressed in % of physical RAM in /etc/fstab. I guess it does not read at all the % character, and the size is read in bytes. size=5% or size=10% results into file systems with a 4 k size (man mount says "The size is given in bytes, and rounded up to entire pages"). When expressed in k, m, g, the size is correct. 'mount -o remount' results in the correct size even if it is expressed in % in /etc/fstab Best regards Pascal Dormeau --- System information. --- Architecture: Kernel: Linux 4.8.0-2-amd64 Debian Release: stretch/sid 990 unstablehttpredir.debian.org --- Package information. --- Depends (Version) | Installed ===-+-= libacl1 (>= 2.2.51-8) | 2.2.52-3 libapparmor1 (>= 2.9.0-3+exp2) | 2.11.0-1 libaudit1 (>= 1:2.2.1) | 1:2.6.7-1 libblkid1 (>= 2.19.1) | 2.29-1 libc6 (>= 2.17) | 2.24-8 libcap2 (>= 1:2.10) | 1:2.25-1 libcryptsetup4 (>= 2:1.4.3) | 2:1.7.3-3 libgcrypt20 (>= 1.7.0) | 1.7.5-3 libgpg-error0 (>= 1.14) | 1.26-1 libidn11 (>= 1.13) | 1.33-1 libip4tc0 | 1.6.0+snapshot20161117-4 libkmod2(>= 5~) | 23-2 liblz4-1 (>= 0.0~r127) | 0.0~r131-2 liblzma5 (>= 5.1.1alpha+20120614) | 5.2.2-1.2 libmount1 (>= 2.26.2) | 2.29-1 libpam0g (>= 0.99.7.1) | 1.1.8-3.5 libseccomp2 (>= 2.3.1) | 2.3.1-2.1 libselinux1 (>= 2.1.9) | 2.6-3 libsystemd0 (= 232-10) | 232-10 util-linux (>= 2.27.1) | 2.29-1 mount (>= 2.26) | 2.29-1 adduser | 3.115 Package Status (Version) | Installed ==-+-=== udev | 232-10 dracut | initramfs-tools| 0.126 Recommends (Version) | Installed =-+-=== libpam-systemd| 232-10 dbus | 1.10.14-1 Suggests (Version) | Installed -+-=== systemd-ui | systemd-container| policykit-1 | 0.105-17 --- Output from package bug script --- /usr/bin/xterm: cannot load font '-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1'
Bug#834994: Apparently consolation needs to be started from the console
Hi, I have similar problem when using consolation : the number of columns or lines is limited and the mouse pointer cannot access to the whole term. However if I run consolation from inside the tty, everything is OK (and very well with scrolling, tapping etc...). If I launch it from inside a xterm like terminal the number of lines and columns in the tty is limited to that of the xterm terminal (lower than that of the tty is the xterm window is not in full screen). It seems that consolation considers the size of the window from which it is launched. I suspect that during boot with systemd the program does not know the tty size (but I don't know what it considers. Fall back values ?). systemctl status show that type of message: consolation[7071]: TIOCGWINSZ: Inappropriate ioctl for device I believe it is related to the 834994 bug, but if you think differently, I am ready to open a new one. Best regards Pascal Dormeau
Bug#823337: Problem comes from systemd-cron
Hello, After reading #823346, I removed systemd-cron and it solved the problem. This should be reassign to systemd-cron. Best regards. Pascal Dormeau
Bug#653349: udev: some usb cd/dvd burners have (wrongly?) ID_TYPE=generic
On Sat, 30 Jan 2016 21:04:17 +0100 Michael Biebl <bi...@debian.org> wrote: > Pascal, could you raise this issue upstream please at > https://github.com/systemd/systemd/issues/new > Reported upstream: https://github.com/systemd/systemd/issues/2485 Regards Pascal Dormeau
Bug#653349: [Pkg-xfce-devel] Bug#651877: xfburn does not detect external pluggable usb burner
On Fri, 29 Jan 2016 21:20:03 +0100 Michael Bieblwrote: > Do you still own this hardware and can you still reproduce the problem > on an up-to-date jessie or stretch system? Hi Michael, Yes I still own the dvdwiter, the laptop has changed but the problem is still here except that ID_TYPE=generic (instead of floppy previously). I am running stretch (sid). xfburn cannot detect the device unless I write a custom udev rule using ENV{ID_SERIAL}=="HLDS_Inc_SuperMulti_RW_001010164000FA655" /lib/udev/ata_id --export /dev/cdrom and /lib/udev/scsi_id --export /dev/cdrom show nothing. Please let me know what useful information I can provide. Regards dmesg output when plugging the device: [ 229.885184] usb 3-1.2: new high-speed USB device number 3 using ehci-pci [ 232.637689] usb 3-1.2: New USB device found, idVendor=152e, idProduct=1640 [ 232.637696] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 232.637700] usb 3-1.2: Product: SuperMulti RW [ 232.637703] usb 3-1.2: Manufacturer: HLDS Inc [ 232.637705] usb 3-1.2: SerialNumber: 001010164000FA655 [ 232.702880] usb-storage 3-1.2:1.0: USB Mass Storage device detected [ 232.703095] scsi host6: usb-storage 3-1.2:1.0 [ 232.703290] usbcore: registered new interface driver usb-storage [ 233.702149] scsi 6:0:0:0: CD-ROMHL-DT-ST DVDRAM GE20LU10 FE06 PQ: 0 ANSI: 0 [ 233.702874] scsi 6:0:0:0: Attached scsi generic sg1 type 5 [ 233.767979] sr 6:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [ 233.767985] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 233.768237] sr 6:0:0:0: Attached scsi CD-ROM sr0 Output of udevadm info --name=/dev/sr0 --query=all P: /devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/host6/target6:0:0/6:0:0:0/block/sr0 N: sr0 L: -100 S: cdrom S: cdrw S: disk/by-id/usb-HLDS_Inc_SuperMulti_RW_001010164000FA655 S: disk/by-path/pci-:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0 S: dvd S: dvdrw E: DEVLINKS=/dev/cdrom /dev/dvdrw /dev/cdrw /dev/disk/by-id/usb-HLDS_Inc_SuperMulti_RW_001010164000FA655 /dev/dvd /dev/disk/by-path/pci-:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0 E: DEVNAME=/dev/sr0 E: DEVPATH=/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/host6/target6:0:0/6:0:0:0/block/sr0 E: DEVTYPE=disk E: ID_BUS=usb E: ID_CDROM=1 E: ID_CDROM_CD=1 E: ID_CDROM_CD_R=1 E: ID_CDROM_CD_RW=1 E: ID_CDROM_DVD=1 E: ID_CDROM_DVD_PLUS_R=1 E: ID_CDROM_DVD_PLUS_RW=1 E: ID_CDROM_DVD_PLUS_R_DL=1 E: ID_CDROM_DVD_R=1 E: ID_CDROM_DVD_RAM=1 E: ID_CDROM_DVD_RW=1 E: ID_CDROM_MRW=1 E: ID_CDROM_MRW_W=1 E: ID_FOR_SEAT=block-pci-_00_1a_0-usb-0_1_2_1_0-scsi-0_0_0_0 E: ID_MODEL=SuperMulti_RW E: ID_MODEL_ENC=SuperMulti\x20RW\x20\x20\x20 E: ID_MODEL_ID=1640 E: ID_PATH=pci-:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0 E: ID_PATH_TAG=pci-_00_1a_0-usb-0_1_2_1_0-scsi-0_0_0_0 E: ID_REVISION=0159 E: ID_SERIAL=HLDS_Inc_SuperMulti_RW_001010164000FA655 E: ID_SERIAL_SHORT=001010164000FA655 E: ID_TYPE=generic E: ID_USB_DRIVER=usb-storage E: ID_USB_INTERFACES=:080550: E: ID_USB_INTERFACE_NUM=00 E: ID_VENDOR=HLDS_Inc E: ID_VENDOR_ENC=HLDS\x20Inc E: ID_VENDOR_ID=152e E: MAJOR=11 E: MINOR=0 E: SUBSYSTEM=block E: SYSTEMD_READY=0 E: TAGS=:uaccess:seat:systemd: E: USEC_INITIALIZED=234242419
Bug#762870: Indeed, works with busybox
Hi, I installed busybox, run update-initramfs -u, restarted the computer and it boots (with a message saying my root fs is clean). Regards Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762870: initramfs-tools: fails to boot after upgrade from 0.116 to 0.117
Hi Michael, On Thu, 25 Sep 2014 23:08:03 +0200 Michael Prokop m...@debian.org wrote: Do you have a separate /usr partition? If so, is it a normal partition or used on top of LVM/RAID/...? No separate /usr, no LVM or RAID. See my fstab (attached), quite not exotic Can you please execute: bash -x mkinitramfs -o /dev/null /tmp/trace.log 21 and provide us the resulting /tmp/trace.log file? trace.log attached. Thanks Regards Pascal trace.log Description: Binary data fstab Description: Binary data
Bug#761292: simple-scan should depend on theme with symbolic icons
Hello, I had the same problem (icons not displayed) and solved it by installing the gnome-icon-theme-symbolic (AFAIR call to symbolic icons is harcoded in the source). Adwaita-icon-theme also provides symbolic icons. So the dependency should have been: 'gnome-icon-theme-symbolic | adwaita-icon-theme' instead of just 'gnome-icon-theme' Note that gnome-icon-theme-symbolic will pull gnome-icon-theme. Now libgtk-3-common (in unstable) depends on adwaita-icon-theme so best is to remove any dependency on an icon-theme package. Hope that helps. Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: possible explanation and patch proposal
Hi Yves-Alexis, Please find hereafter an explanation of the problem based on my personal interpretation. Vincent has been very much involved in debugging so I CC him too. * What is going on : This happens when logind is running. Before logout, we have at least one logind user session and one logind lightdm session (implies that libpam-systemd is installed). At logout, lightdm immediately starts a new session (and runs a new lightdm-gtk-greeter process), then the former lightdm session is removed, and only then the user session is removed. So when the new lightdm-gtk-greeter process is launched, more than one logind session exists. lightdm-gtk-greeter checks if suspend, hibernate, restart, shutdown are allowed using the lightdm_get_can_suspend/hibernate/restart/shutdown() functions. If one of those actions is not allowed, it is hidden from the power menu, from beginning to end of the lightdm-gtk-greeter process. If logind is running, power actions are allowed according to /usr/share/polkit-1/actions/org.freedesktop.login1.policy. For multiple-sessions, restart and hibernate are allow_active auth_admin_keep. So at logout we have temporary a multi-sessions configuration implying that hibernate and restart are not allowed. Because the power menu is static inside a given lightdm-gtk-greeter process, hibernate and restart remain forbidden even after only one lightdm session remains. The bug could be in the way the different logind sessions are removed and created at logout, but still, lightdm-gtk-greeter is unable to track session changes (for instance, if someone else logs into a VT). * proposal The proposal is to check whether hibernate, restart, shutdown are allowed, only when the power menu is opened. The patch in attachment is doing this. But BIG WARNING: I spend only a couple of days digging into the GTK documentation available on the web, it's all new for me. It might be dirty. Check needed. Help also welcome for improvement (I guess there is a smarter way to avoid those 5 new GtkWidget objects). I run lightdm and lightdm-gtk-greteer with it, so far they behave as expected (in particular, if I log in a VT resulting into a multiple session situation, I can see the change in the menu). Regards Pascal Dormeau --- a/src/lightdm-gtk-greeter.c 2013-12-28 14:32:24.0 +0100 +++ b/src/lightdm-gtk-greeter.c 2013-12-28 14:31:55.323524021 +0100 @@ -51,6 +51,11 @@ static GtkWidget *menubar; static GtkMenu *session_menu, *language_menu; static GtkCheckMenuItem *keyboard_menuitem; +static GtkWidget *power_item; +static GtkWidget *suspend_item; +static GtkWidget *hibernate_item; +static GtkWidget *restart_item; +static GtkWidget *shutdown_item; /* Login Window Widgets */ static GtkWindow *login_window; @@ -1474,6 +1479,43 @@ return TRUE; } +static void +show_power_items_if_can (GtkWidget *menuitem, gpointer userdata) +{ +if (!lightdm_get_can_suspend ()) + { +gtk_widget_hide (GTK_WIDGET (suspend_item)); + } + else + { + gtk_widget_show (GTK_WIDGET (suspend_item)); + } +if (!lightdm_get_can_hibernate ()) + { +gtk_widget_hide (GTK_WIDGET (hibernate_item)); + } + else + { + gtk_widget_show (GTK_WIDGET (hibernate_item)); + } +if (!lightdm_get_can_restart ()) + { +gtk_widget_hide (GTK_WIDGET (restart_item)); + } + else + { +gtk_widget_show (GTK_WIDGET (restart_item)); + } +if (!lightdm_get_can_shutdown ()) + { +gtk_widget_hide (GTK_WIDGET (shutdown_item)); + } + else + { +gtk_widget_show (GTK_WIDGET (shutdown_item)); + } +} + int main (int argc, char **argv) @@ -1843,7 +1885,7 @@ gtk_container_add (GTK_CONTAINER (menuitem), image); /* Power menu */ -menuitem = GTK_WIDGET (gtk_builder_get_object (builder, power_menuitem)); +power_item = GTK_WIDGET (gtk_builder_get_object (builder, power_menuitem)); #if GTK_CHECK_VERSION (3, 0, 0) if (gtk_icon_theme_has_icon(icon_theme, system-shutdown-symbolic)) image = gtk_image_new_from_icon_name (system-shutdown-symbolic, GTK_ICON_SIZE_MENU); @@ -1853,16 +1895,15 @@ image = gtk_image_new_from_icon_name (system-shutdown, GTK_ICON_SIZE_MENU); #endif gtk_widget_show (image); -gtk_container_add (GTK_CONTAINER (menuitem), image); +gtk_container_add (GTK_CONTAINER (power_item), image); + + suspend_item = GTK_WIDGET (gtk_builder_get_object (builder, suspend_menuitem)); + hibernate_item = GTK_WIDGET (gtk_builder_get_object (builder, hibernate_menuitem)); + restart_item = GTK_WIDGET (gtk_builder_get_object (builder, restart_menuitem)); + shutdown_item = GTK_WIDGET (gtk_builder_get_object (builder, shutdown_menuitem)); -if (!lightdm_get_can_suspend ()) -gtk_widget_hide (GTK_WIDGET (gtk_builder_get_object (builder, suspend_menuitem))); -if (!lightdm_get_can_hibernate ()) -gtk_widget_hide (GTK_WIDGET (gtk_builder_get_object (builder, hibernate_menuitem))); -if (!lightdm_get_can_restart
Bug#732623: Bug#729576: duplicate of bug #726763
On Tue, 24 Dec 2013 23:52:50 +0100 Vincent Lefevre vinc...@vinc17.net wrote: No, the menu is refreshed since when I install or remove systemd + libpam-systemd, then log out, I can see changes. This is because when you log out, you create a new lightdm-gtk-greeter process and you see the change. However, inside one given lightdm-gtk-greteer process, the power_menu remains static. When libpam-systemd is removed, lightdm does not have anymore its own logind session. If no one else is logged, there is no more multi-session and the full power_menu can show up. If both libpam-systemd and systemd are removed I guess the lightdm_get_can_* () tests switch to consolekit and upower. I haven't tried installing or removing systemd + libpam-systemd from a VT while there's no user X session. I tried but as systemd is PID1, I just removed libpam-systemd and restarted systemd-login.service. I had to login with lightdm and logout to see the change (by running a new lightdm-gtk-greeter process). Shouldn't it run the lightdm_get_can_* () test at runtime when the user opens the power_menu ? When the user opens the menu would be the best, IMHO. I do not know how to achieve this. The best I could do to remove the gtk_widget_hide calls. The 4 items in the menu show up and the action fails when permission is not granted. But it is not user friendly since no feedback is given. Moreover, there is still this inconsistent behavior between shutdown and reboot (respectively suspend and hibernate) in case of multiple-sessions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: Bug#729576: duplicate of bug #726763
Message resent due to delivery failure Hi Vincent, On Tue, 24 Dec 2013 02:01:21 +0100 Vincent Lefevre vinc...@vinc17.net wrote: I'm wondering whether there is a race condition, making differences between machines. if (!lightdm_get_can_suspend ()) gtk_widget_hide (GTK_WIDGET (gtk_builder_get_object (builder, suspend_menuitem))); if (!lightdm_get_can_hibernate ()) gtk_widget_hide (GTK_WIDGET (gtk_builder_get_object (builder, hibernate_menuitem))); if (!lightdm_get_can_restart ()) gtk_widget_hide (GTK_WIDGET (gtk_builder_get_object (builder, restart_menuitem))); if (!lightdm_get_can_shutdown ()) gtk_widget_hide (GTK_WIDGET (gtk_builder_get_object (builder, shutdown_menuitem))); To exclude a possible race conditions, I re-built lightdm-gtk-greeter changing the order above, but the problem remains the same with only the suspend and the shutdown buttons showing. Then I had a look at /usr/share/polkit-1/actions/org.freedesktop.login1.policy reboot and shutdown (respectively suspend and hibernate) permissions differ inside the multiple-sessions stanza. It is allow_active yes for shutdown (respectively suspend) whereas allow_active auth_admin_keep for reboot (respectively hibernate). Forcing allow_active to yes for reboot and hibernate in the multiple-sessions stanza allows to get all 4 buttons. But I cannot explain the multiple-session thing, normally there is only one session (lightdm) if no one else is logged in. Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: Bug#729576: duplicate of bug #726763
On Tue, 24 Dec 2013 18:57:32 +0100 Vincent Lefevre vinc...@vinc17.net wrote: With D-Bus monitoring[*], I could see that there was between 1 or 3 sessions at the same time. Perhaps the user sessions were removed too late. [*] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732623#132 Indeed, I tried it and unless I am doing it wrong this is what i observe: - when the user is logged, there are one c_i lightdm session, and of course the j user session that is active. - when the user logs out: . a new c_i+1 lightdm session is created and becomes active . then the c_i lightdm session is removed . then only the j user session is removed I guess lightdm-gtk-greeter is run when creating the new c_i+1 session, in such case there would be two other simultaneous sessions. Unless I am wrong again, I understand that lightdm-gtk-greeter creates its power_menu once and for all when first launched and does not refresh it after. Shouldn't it run the lightdm_get_can_* () test at runtime when the user opens the power_menu ? After all, the idea of using systemd is to track session changes. Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout
On Sun, 22 Dec 2013 00:12:14 +0100 Vincent Lefevre vinc...@vinc17.net wrote: When I upgraded my second machine yesterday, I noticed that both libpam-systemd and systemd had been installed, so that I thought the bug was related to one of them. So, I did some tests to see what minimal change triggered the problem, and it was not due to libpam-systemd (which depends on systemd), but to systemd itself. That's why I've reassigned the bug to systemd. Well that might be more tricky than that, here systemd is used as PID1 (thus logind running) and lightdm works as expected without libpam-systemd. Only installing libpam-systemd triggers the problem. Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout
On Sat, 21 Dec 2013 20:57:08 +0100 Vincent Lefevre vinc...@vinc17.net wrote: I would like to know whether other users can reproduce the problem with twm, just by logging in then logging out. Since twm is a minimalist window manager, which doesn't start anything special, this could give an idea... Hi Vincent, Contrary to what I though (and wrote), I can reproduce the same with xfce4-session or twm. On my side, it seems to have to do with libpam-systemd, removing it allows all 4 buttons. The problem is triggered as soon as libpam-systemd is installed (installing upower does not change anything to it). Best regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: consolekit and libpam-systemd together
Hi Yves-Alexis, Bug report should be renamed to: no consolekit session available when libpam-systemd is present (not libpam-consolekit). Following https://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2013-November/000812.html that states that there is no problem to have consolekit and libpam-systemd together, I tried a modified version of lightdm that allows it (pach in attachment). Note that one can achieve the same after installing libpam-ck-connector (+removing the nox11 option) and tweaking /etc/X11/Xsession.d/90consolekit so that consolekit is run unconditionally. So far i had no problem running lightdm+xfce4-session with consolekit only installed as well as with consolekit+libpam-systemd installed. Test is not extensive (restart, shutdown, udisk are ok). Given my poor coding experience, writing that patch looks too obvious and I suspect I may have missed something, then I recommend to review it carefully (upstream, maybe ?) in case you intend to use it. BTW, this is unrelated because it affects lightdm and xfce4-session versions already in archive, when libpam-systemd is installed, if I leave a session and log in again, loginctl shows previous sessions on the same seat. Example: $: loginctl -a SESSIONUID USER SEAT 1 1000 pascal seat0 2 1000 pascal seat0 c3102 lightdm seat0 3 1000 pascal seat0 4 sessions listed. $: ck-list-sessions Session6: unix-user = '1000' realname = '' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2013-11-28T20:37:11.191451Z' login-session-id = '3' I would have expected seeing only one session for the user (assuming previous sessions have ended). I do not know if it is the normal behavior or not and I do not know who to blame (lightdm or xfce-session ?). I can open a bug report for that if you wish. Regards Pascal Dormeau --- a/src/session.c 2013-10-30 21:41:46.0 +0100 +++ b/src/session.c 2013-11-28 19:59:37.218510065 +0100 @@ -766,8 +766,8 @@ if (login1_is_running ()) session-priv-login1_session = read_string_from_child (session); -if (!session-priv-login1_session) -session-priv-console_kit_cookie = read_string_from_child (session); + +session-priv-console_kit_cookie = read_string_from_child (session); } void @@ -778,7 +778,7 @@ { if (session-priv-login1_session) login1_lock_session (session-priv-login1_session); -else if (session-priv-console_kit_cookie) +if (session-priv-console_kit_cookie) ck_lock_session (session-priv-console_kit_cookie); } } @@ -791,7 +791,7 @@ { if (session-priv-login1_session) login1_unlock_session (session-priv-login1_session); -else if (session-priv-console_kit_cookie) +if (session-priv-console_kit_cookie) ck_unlock_session (session-priv-console_kit_cookie); } } --- a/src/session-child.c 2013-11-28 20:24:07.0 +0100 +++ b/src/session-child.c 2013-11-28 20:01:55.738515458 +0100 @@ -476,8 +476,8 @@ write_string (login1_session); } -if (!login1_session) -{ + + /* Open a Console Kit session */ g_variant_builder_init (ck_parameters, G_VARIANT_TYPE ((a(sv; g_variant_builder_open (ck_parameters, G_VARIANT_TYPE (a(sv))); @@ -506,7 +506,7 @@ pam_putenv (pam_handle, value); g_free (value); } -} + /* Write X authority */ if (x_authority)
Bug#728361: consolekit and libpam-systemd together
On Thu, 28 Nov 2013 22:35:10 +0100 Yves-Alexis Perez cor...@debian.org wrote: BTW, this is unrelated because it affects lightdm and xfce4-session versions already in archive, when libpam-systemd is installed, if I leave a session and log in again, loginctl shows previous sessions on the same seat. Example: I would have expected seeing only one session for the user (assuming previous sessions have ended). I do not know if it is the normal behavior or not and I do not know who to blame (lightdm or xfce-session ?). I can open a bug report for that if you wish. Indeed. Something is not cleaning the logind session, I guess. It does happen with an unpatched lightdm and libpam-systemd? yes, with unpatched lightdm and libpam-systemd installed Regards, Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: xfce4: Nor working restart/shutdown buttons
Hello, I could be wrong here, but looking in session-child.c, one can find (line 470): if (login1_is_running ()) { login1_session = login1_get_session_id (); write_string (login1_session); } if (!login1_session) { /* Open a Console Kit session */ My programming knowledge is limited but I understand this as consolekit being launched only if no logind session is launched. And if libpam-systemd is installed, only the logind session is launched. I am not sure that xfce4-session has logind support (I saw a patch waiting in the pkg-xfce svn that could allow logind support at runtime). Again that is just a mere supposition, because I cannot easily read a source code. Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642929: upcoming scim release
On Thu, 17 May 2012 12:50:13 +0800 Rolf Leggewie debian-b...@rolf.leggewie.biz wrote: REMINDER Hello Tz-Huan and Pascal, Hi Rolf, Sorry to answer so late, have been traveling since beginning of this month. Can you please download the packages from http://oss.leggewie.org/deb/scim.md5, verify against http://oss.leggewie.org/deb/scim.md5 and let me know if indeed the problem is gone? Thank you. You might need the newly-introduced scim-gtk3-immodule package. I tested 1.4.13-1 version, it works, in particular, scim-gtk2-immodule now works with iceweasel. Note that I could not test the gtk3 module (no gtk3 application installed here). Best regards Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664285: i3lock: does not always honour color argument
Package: i3lock Version: 2.3.1-1 Severity: minor Dear Maintainer, With new version (2.3.1), i3lock defaults to white even if another color is specified as option. This does not always happen like this, I noticed that color argument is accepted if it contains 00 for one of the rr, gg or bb values. ff is accepted, 00 also, but 55 defaults to white (accepted here means does not default to white, I did not check if the result is correct). Best regards Pascal Dormeau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages i3lock depends on: ii libc6 2.13-27 ii libcairo2 1.10.2-7 ii libev41:4.11-1 ii libpam0g 1.1.3-7 ii libx11-6 2:1.4.4-4 ii libxcb-dpms0 1.8-2 ii libxcb-image0 0.3.8-1 ii libxcb-keysyms1 0.3.8-1 ii libxcb-shm0 1.8-2 ii libxcb-xinerama0 1.8-2 ii libxcb1 1.8-2 i3lock recommends no packages. i3lock suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664288: i3lock: if launched with xautolock visual unlock indicator does not show up
Package: i3lock Version: 2.3.1-1 Severity: minor Dear Maintainer, When i3lock is launched with xautolock as its 'locker', the unlock visual indicator does not show up. It still shows up if launched from, for instance: - xterm, - xsessionrc, - xfce4 panel launcher - a sh script launched from the xterm Maybe the problem is xautolock, however one of the interesting use of i3lock is to be activated by xautolock (although the indicator is not absolutely necessary, previous versions did not have). Best regards Pascal Dormeau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages i3lock depends on: ii libc6 2.13-27 ii libcairo2 1.10.2-7 ii libev41:4.11-1 ii libpam0g 1.1.3-7 ii libx11-6 2:1.4.4-4 ii libxcb-dpms0 1.8-2 ii libxcb-image0 0.3.8-1 ii libxcb-keysyms1 0.3.8-1 ii libxcb-shm0 1.8-2 ii libxcb-xinerama0 1.8-2 ii libxcb1 1.8-2 i3lock recommends no packages. i3lock suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653349: Bug#651877: [Pkg-xfce-devel] Bug#651877: xfburn does not detect external pluggable usb burner
On Tue, 27 Dec 2011 12:30:50 +0100 m...@linux.it (Marco d'Itri) wrote: Please report the output of: /lib/udev/scsi_id --export /dev/cdrom2 /lib/udev/ata_id --export /dev/cdrom2 Hi, Sorry, both commands produce no output (I checked that a /dev/cdrom2 symlink is created and pointing to /dev/sr1) I get the following in the syslog: ata_id[2831]: HDIO_GET_IDENTITY failed for '/dev/cdrom2': Invalid argument Best regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651877: [Pkg-xfce-devel] Bug#651877: xfburn does not detect external pluggable usb burner
On Fri, 23 Dec 2011 22:31:43 +0100 Lionel Le Folgoc mrpo...@gmail.com wrote: tags 651877 + moreinfo thanks Hi, Hi, Could you check if there's any message from xfburn in .xsession-errors, and that your burner is correctly detected as such by udev? e.g. with udevadm info --name=/dev/sr1 --query=all yes it is (udev also creates the usual aliases I use for burning with cdrskin): P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host5/target5:0:0/5:0:0:0/block/sr1 N: sr1 S: cdrom2 S: cdrw2 S: disk/by-id/usb-HLDS_Inc_SuperMulti_RW_001010164000FA655 S: disk/by-path/pci-:00:1d.0-usb-0:1.2:1.0-scsi-0:0:0:0 S: dvd2 S: dvdrw2 E: DEVLINKS=/dev/cdrom2 /dev/cdrw2 /dev/disk/by-id/usb-HLDS_Inc_SuperMulti_RW_001010164000FA655 /dev/disk/by-path/pci-:00:1d.0-usb-0:1.2:1.0-scsi-0:0:0:0 /dev/dvd2 /dev/dvdrw2 E: DEVNAME=/dev/sr1 E: DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host5/target5:0:0/5:0:0:0/block/sr1 E: DEVTYPE=disk E: GENERATED=1 E: ID_BUS=usb E: ID_CDROM=1 E: ID_CDROM_CD=1 E: ID_CDROM_CD_R=1 E: ID_CDROM_CD_RW=1 E: ID_CDROM_DVD=1 E: ID_CDROM_DVD_PLUS_R=1 E: ID_CDROM_DVD_PLUS_RW=1 E: ID_CDROM_DVD_PLUS_R_DL=1 E: ID_CDROM_DVD_R=1 E: ID_CDROM_DVD_RAM=1 E: ID_CDROM_DVD_RW=1 E: ID_CDROM_MRW=1 E: ID_CDROM_MRW_W=1 E: ID_MODEL=SuperMulti_RW E: ID_MODEL_ENC=SuperMulti\x20RW\x20\x20\x20 E: ID_MODEL_ID=1640 E: ID_PATH=pci-:00:1d.0-usb-0:1.2:1.0-scsi-0:0:0:0 E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_2_1_0-scsi-0_0_0_0 E: ID_REVISION=0159 E: ID_SERIAL=HLDS_Inc_SuperMulti_RW_001010164000FA655 E: ID_SERIAL_SHORT=001010164000FA655 E: ID_TYPE=floppy E: ID_USB_DRIVER=usb-storage E: ID_USB_INTERFACES=:080550: E: ID_USB_INTERFACE_NUM=00 E: ID_VENDOR=HLDS_Inc E: ID_VENDOR_ENC=HLDS\x20Inc E: ID_VENDOR_ID=152e E: MAJOR=11 E: MINOR=1 E: SUBSYSTEM=block E: TAGS=:udev-acl: E: UDEV_LOG=3 E: UDISKS_PRESENTATION_NOPOLICY=0 E: USEC_INITIALIZED=289702410 as for xsession-errors: (process:3823): GLib-WARNING **: /tmp/buildd/glib2.0-2.30.2/./glib/goption.c:2168: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:3823): GLib-WARNING **: /tmp/buildd/glib2.0-2.30.2/./glib/goption.c:2168: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message:Using UDEV ** Message: Using Transcodeur GStreamer transcoder. I also made a try with the device already plugged at boot but same result: xfburn 0.4.3-4 does not detect it. Could it be related with usb (since here the burner on S-ATA is detected) ? Thanks. Thank you too Best regards Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651877: [Pkg-xfce-devel] Bug#651877: xfburn does not detect external pluggable usb burner
On Sat, 24 Dec 2011 13:41:24 +0100 Lionel Le Folgoc mrpo...@gmail.com wrote: Hi again, Thanks for answering quickly E: ID_TYPE=floppy Now this is weird. Your external usb burner is set as a floppy drive (?!) by udev. Xfburn 0.4.3-4 only cares about ID_TYPE=cd (my external burner has that type), and ignores other drives. I did not notice that. Sorry. Could you file a bug against the udev package, as it looks like it misdetects your drive? (if the udev maintainer thinks this is normal, I guess I'll add a workaround in xfburn…) There are bugs in BTS where udev is suspected to assign media to floppy group (645466, 648810), but it is not the case here: ls -l /dev/sr* brw-rw---T+ 1 root cdrom 11, 0 déc. 24 11:51 /dev/sr0 brw-rw---T+ 1 root cdrom 11, 1 déc. 24 14:07 /dev/sr1 Moreover, udev detects the drive as a cd writer since it recreates the 70-persistent-cd.rules after I delete it. I am ok to file a bug against udev package but should not this one be re-assigned to udev instead ? Thanks and merry Christmas too. Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651877: xfburn does not detect external pluggable usb burner
Package: xfburn Version: 0.4.3-4 Severity: normal Dear Maintainer, xfburn cannot detect my external usb burner anymore after upgrading from 0.4.3-3 to 0.4.3-4 version (downgrading to 0.4.3-3 actually solves the problem). Whereas cdrskin can still detect all drives: [pascal@kiwi ~]$ cdrskin -scanbus cdrskin 1.1.8 : limited cdrecord compatibility wrapper for libburn cdrskin: scanning for devices ... cdrskin: ... scanning for devices done Using libburn version '1.1.8'. scsibus1: 1,0,0 0) 'MATSHITA' 'DVD-RAM UJ890AS ' '1.00' Removable CD-ROM scsibus5: 5,0,0 1) 'HL-DT-ST' 'DVDRAM GE20LU10 ' 'FE06' Removable CD-ROM 1st one is internal burner, xfburn 0.4.3-4 detects the 1st one only (on /dev/sr0). Second one is the pluggable drive (/dev/sr1) And I can still burn optical media with the external usb drive using cdrskin. I have consolekit, policykit-1 and gvfs installed and the user session is active, started with lightdm (but obviously the user is granted rights to use the external usb drive, since he can access it with cdrskin) Best regards Pascal Dormeau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfburn depends on: ii libburn4 1.1.8-1 ii libc62.13-21 ii libexo-1-0 0.6.2-3 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-0 2.30.2-4 ii libgstreamer-plugins-base0.10-0 0.10.35-1 ii libgstreamer0.10-0 0.10.35-1 ii libgtk2.0-0 2.24.8-2 ii libgudev-1.0-0 175-3 ii libisofs61.1.6-1 ii libxfce4ui-1-0 4.8.0-3 ii libxfce4util44.8.2-1 xfburn recommends no packages. xfburn suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644917: [Pkg-xfce-devel] Bug#644917: lightdm: (null) is passed as argument to /etc/X11/Xsession
On Fri, 04 Nov 2011 12:47:09 +0100 Yves-Alexis Perez cor...@debian.org wrote: By the way, it seems fixed in 1.0.4-1, could you check and report back? Hello Yves-Alexis, I tested 1.0.6-1 version and the problem no more exists. This bug can be closed now. Thanks a lot, Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642929: still a problem with iceweasel
On Wed, 12 Oct 2011 20:09:37 +0800 Rolf Leggewie debian-b...@rolf.leggewie.biz wrote: Pascal, Hi Rolf, thank you for your continued stream of information and help to troubleshoot this problem. Well I am sorry but I did not check enough. It appears finally that it still fails with iceweasel (whereas 1.4.9-6 version works with iceweasel, whatever the gtk2 version). Sorry for the bad news. Best Regards Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642929: solved with libgtk2.0-0 with multiarch support
Hi Rolf, Finally I just installed libgtk2.0-0 from unstable and it solved the problem. No need to rebuild against libgtk2-dev from unstable. Note that scim-gtk2-immodule.immodules is finally not needed, instead /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/gtk.immodules is created by /usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0 and it seems to do the job. So for scim-gtk2-immodule to work it just needs to depend on a libgtk2.0-0 version with multiarch support. I should have found this before, that was obvious (at least easy to test). Sorry for that. However, the fix you proposed concerning /etc/X11/xinit/xinput.d/scim-immodule might still be needed for im-config support. Best regards Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644917: lightdm: (null) is passed as argument to /etc/X11/Xsession
Package: lightdm Version: 1.0.3-1 Severity: minor Dear Maintainer, This occurs when upgrading lightdm from 1.0.2-1 to 1.0.3-1. user-session is set to lightdm-xsession that should pass default as argument to /etc/X11/Xsession, but (null) argument is passed. This can be seen in xsession-errors: Xsession: unable to launch (null) X session --- (null) not found; falling back to default session. This has no visible drawback except when x11-utils is installed. In such case, xmessage exposes the error message and the user has to acknowledge it before allowing the (default) session to be launched. Best regards Pascal Dormeau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lightdm depends on: ii adduser3.113 ii consolekit 0.4.5-1 ii dbus 1.4.16-1 ii debconf [debconf-2.0] 1.5.40 ii libc6 2.13-21 ii libglib2.0-0 2.28.6-1 ii libpam0g 1.1.3-4 ii libxcb11.7-3 ii libxdmcp6 1:1.1.0-3 ii lightdm-gtk-greeter1.0.3-1 Versions of packages lightdm recommends: ii xserver-xorg 1:7.6+9 Versions of packages lightdm suggests: pn accountsservice none -- Configuration Files: /etc/lightdm/lightdm.conf changed: [LightDM] seats=Seat:0 Seat:1 [SeatDefaults] xserver-allow-tcp=false greeter-hide-users=false user-session=lightdm-xsession allow-guest=false session-wrapper=/etc/X11/Xsession greeter-setup-script=/usr/bin/numlockx on session-setup-script=/usr/bin/numlockx off [XDMCPServer] [VNCServer] [Seat:0] vt=7 [Seat:1] vt=8 -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642929: proposed fix
On Fri, 30 Sep 2011 17:46:20 +0800 Rolf Leggewie f...@rolf.leggewie.biz wrote: Hello Leo and Pascal, Hello Rolf Pascal, thank you for reporting the regression and Leo, thank you for your analysis which I believe is spot-on. Can you guys please patch your local copy of /etc/X11/xinit/xinput.d/scim-immodule as shown in http://paste.debian.net/132934/ and let me know if that fixes the issue for you? Thanks. I already tried such approach but it fails here. There might be other things missing, for instance, in 1.4.9-6 version, there is a file created by dh_gtkmodules that does not appear in 1.4.9.7: /usr/lib/gtk-2.0/2.10.0/immodule-files.d/scim-gtk2-immodule.immodules I do not know what to do with this one (what to put inside, where to put it) Regards Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642929: scim-gtk2-immodule: gtk immodule fails after update to 1.4.9-7
Package: scim-gtk2-immodule Version: 1.4.9-7 Severity: normal Dear Maintainer, After upgrading scim from 1.4.9-6 to 1.4.9-7 the gtk immodule is not loaded anymore when launching a gtk application (sorry I do not know if loaded is the right term) For information, here is the relevant extract of my xsessionrc: GTK_IM_MODULE=scim export GTK_IM_MODULE scim -d And this is the relevant xsession-errors extract: Smart Common Input Method 1.4.9 Launching a SCIM daemon with Socket FrontEnd... Loading simple Config module ... Creating backend ... Loading socket FrontEnd module ... Starting SCIM as daemon ... Launching a SCIM process with x11... Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.9 Starting SCIM as daemon ... SCIM has been successfully launched. And scim is visible in the systray. But it has no effect when a gtk application is launched. I am ready to provide the useful information that you can ask to me. Best regards Pascal Dormeau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages scim-gtk2-immodule depends on: ii libatk1.0-0 2.0.1-2 ii libc62.13-21 ii libcairo21.10.2-6.1 ii libfontconfig1 2.8.0-3 ii libfreetype6 2.4.6-2 ii libgcc1 1:4.6.1-4 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-0 2.28.6-1 ii libgtk2.0-0 2.24.4-3 ii libpango1.0-01.28.4-3 ii libscim8c2a 1.4.9-7 ii libstdc++6 4.6.1-4 ii scim 1.4.9-7 ii scim-modules-socket 1.4.9-7 scim-gtk2-immodule recommends no packages. scim-gtk2-immodule suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637796: iptables-persistent: init script too zealous ?
Package: iptables-persistent Version: 0.5.2 Severity: wishlist Hello, Trying to give a try to iptables-persistent, I fell onto the following problem: I got skipping IPv4 (no module loaded) message at startup (same for IPV6) whereas doing up /sbin/iptables-restore /etc/iptables/rules.v4 in my /etc/network/interface load my iptables rules at startup without any error. The init script (load_rules) checks if /proc/net/ip_tables_names is present before loading the rules, meaning that tables modules must be loaded first. It seems that with current iptables and kernels shipped with Debian, it is not necessary. If I comment the part with the /proc/net/ip_tables_names test, my rules are loaded at startup. man iptables states: -t, --table table This option specifies the packet matching table which the command should operate on. If the kernel is configured with automatic module loading, an attempt will be made to load the appropriate module for that table if it is not already there. And kernels in Wheezy seem to automatic load the appropriate modules. I understand that iptables-persistent should take into account other kernels than the official Debian ones, but I still wonder if the test is really necessary. If modules cannot be loaded automatically and if /proc/net/ip_tables_names does not exist, iptables-restore will just fail and the result will be the same (no rules loaded). Moreover, the initscript checks if the table modules are loaded, not if that other specific modules required by the rules in /etc/iptables/rules.v4 can be loaded (but risk is limited here if the rules.v4 is created with the debconf script or by /etc/init.d/iptables-presistent save_rules). There might be some good reasons doing it that way, I such case, please disregard this bug report (and close it). Best regards Pascal Dormeau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iptables-persistent depends on: ii debconf [debconf-2.0] 1.5.40 Debian configuration management sy ii iptables 1.4.12-1 administration tools for packet fi ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip iptables-persistent recommends no packages. iptables-persistent suggests no packages. -- Configuration Files: /etc/init.d/iptables-persistent changed: .. /lib/lsb/init-functions rc=0 load_rules() { log_action_begin_msg Loading iptables rules #load IPv4 rules if [ -f /etc/iptables/rules.v4 ]; then log_action_cont_msg IPv4 iptables-restore /etc/iptables/rules.v4 2 /dev/null if [ $? -ne 0 ]; then rc=1 fi fi #load IPv6 rules if [ -f /etc/iptables/rules.v6 ]; then log_action_cont_msg IPv6 ip6tables-restore /etc/iptables/rules.v6 2 /dev/null if [ $? -ne 0 ]; then rc=1 fi fi log_action_end_msg $rc } save_rules() { log_action_begin_msg Saving rules #save IPv4 rules if [ ! -f /proc/net/ip_tables_names ]; then log_action_cont_msg skipping IPv4 (no module loaded) elif [ -x /sbin/iptables-save ]; then log_action_cont_msg IPv4 iptables-save /etc/iptables/rules.v4 if [ $? -ne 0 ]; then rc=1 fi fi #save IPv6 rules if [ ! -f /proc/net/ip6_tables_names ]; then log_action_cont_msg skipping IPv6 (no module loaded) elif [ -x /sbin/ip6tables-save ]; then log_action_cont_msg IPv6 ip6tables-save /etc/iptables/rules.v6 if [ $? -ne 0 ]; then rc=1 fi fi log_action_end_msg $rc } flush_rules() { log_action_begin_msg Flushing rules if [ ! -f /proc/net/ip_tables_names ]; then log_action_cont_msg skipping IPv4 (no module loaded) elif [ -x /sbin/iptables ]; then log_action_cont_msg IPv4 for param in F Z X; do /sbin/iptables -$param; done for table in $(/proc/net/ip_tables_names) do /sbin/iptables -t $table -F /sbin/iptables -t $table -Z /sbin/iptables -t $table -X done for chain in INPUT FORWARD OUTPUT do /sbin/iptables -P $chain ACCEPT done fi if [ ! -f /proc/net/ip6_tables_names
Bug#626730: consolekit: Inconsistent behavior between x86-32 and x86-64 regarding login-session-id
Package: consolekit Version: 0.4.4-1 Severity: minor Hello, On two laptops, one with i386 and the other with amd64, with roughly the same configuration, I can have an active X session with consolekit working in the amd64 case but not in the i386 case (unless I make use of pam_loginuid). For amd64, /proc/self/loginuid, /proc/self/sessionid and ck-lists-session (login-session-id) always return 4294967295 for login-session-id (for everybody logged in, in a X session or in a console). For i386, /proc/self/loginuid, /proc/self/sessionid always return 4294967295 (for everybody logged in, in a X session or in a console), but ck-lists-session always report empty login-session-id. I do not know here what should be the correct behavior. To have an active X session with non empty login-session-id on the i386, I have to make use of pam_loginuid module (in /etc/pam.d/common-session). In such case, /proc/self/loginuid reports correct uid, /proc/self/sessionid and ck-lists-session (login-session-id) reports the same id, specific to each session (and different from 4294967295). And finally ck-list-session reports that the X session is active. I do not have to do that on amd64. Additional information in case it matters: on both systems, the X session can be started by either xdm or startx. libpam-ck-connector is installed and /etc/X11/Xsession.d/90consolekit is modified such as to unconditionally run ck-launch-session. Best regards, Pascal Dormeau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages consolekit depends on: ii dbus1.4.8-3 simple interprocess messaging syst ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libck-connector00.4.4-1 ConsoleKit libraries ii libdbus-1-3 1.4.8-3 simple interprocess messaging syst ii libdbus-glib-1-20.92-1 simple interprocess messaging syst ii libglib2.0-02.28.6-1 The GLib library of C routines ii libpolkit-gobject-1-0 0.101-4 PolicyKit Authorization API ii libx11-62:1.4.3-1X11 client-side library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages consolekit recommends: ii libpam-ck-connector 0.4.4-1ConsoleKit PAM module consolekit suggests no packages. -- Configuration Files: /etc/X11/Xsession.d/90consolekit changed: CK_LAUNCH_SESSION=/usr/bin/ck-launch-session is_on_console() { session=$(dbus-send --system --dest=org.freedesktop.ConsoleKit \ --type=method_call --print-reply --reply-timeout=2000 \ /org/freedesktop/ConsoleKit/Manager \ org.freedesktop.ConsoleKit.Manager.GetCurrentSession \ | grep path | awk '{print $3}' | sed s/\//g) x11_display=$(dbus-send --system --dest=org.freedesktop.ConsoleKit \ --type=method_call --print-reply --reply-timeout=2000 \ $session org.freedesktop.ConsoleKit.Session.GetX11Display \ | grep string | awk '{print $2}' | sed s/\//g) if [ -z $x11_display ] ; then return 0 else return 1 fi } if [ -z $GDMSESSION ] [ -x $CK_LAUNCH_SESSION ] ; then STARTUP=$CK_LAUNCH_SESSION $STARTUP fi -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619433: Follow-up
Hello, Just to inform that the bug has found a fix upstream (commit 7bed50c5edf5cba8dd515a31191cbfb6065ddc85, details can be found at https://bugzilla.kernel.org/show_bug.cgi?id=31872). The fix has been included in linux-2.6 tree and is waiting in the queue-2.6.38 subdirectory. I am currently running a self built linux-2.6.38 image with the above fix included, and it seems that the bug did not touch any one but me (given my buggy bios). I can now wait for next upload in Debian (next 2.6.38 if any, or next 2.6.39 in experimental or unstable), so I believe you can just close this bug without any further action. Best regards and thank you for pointing me to the right place. Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619433: Reported upstream
Hello, The bug has been reported to upstream: https://bugzilla.kernel.org/show_bug.cgi?id=31872 Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619433: linux-image-2.6.38-1-686: early crash with ACPI (regression)
- Ben Hutchings b...@decadent.org.uk a écrit : Please report this upstream at https://bugzilla.kernel.org, under product 'ACPI', component 'ACPICA-Core'. Let us know the bug URL so we can track it. You should link *directly* to the video, if possible, because it took me some time to work out where the link was on the 'getfile.pl' page. Also you should provide the most important lines as text, which appear to be: do_page_fault+0x0/0x35d error_code+0x67/0x6c __kmalloc+0x??/0x10b acpi_ns_internalize_name+0x2e/0x61 acpi_ns_search_one_scope+0x12/0x31 I was going to ask you to use the 'boot_delay' kernel parameter to slow down log output, but now I realise this isn't enabled in the Debian kernel packages. If you can build a custom kernel with CONFIG_BOOT_PRINTK_DELAY=y and test it with boot_delay=1000 then you should be able to get still pictures of the whole of the 'oops' message. But the above lines may be enough of a clue to the ACPI developers. Thanks a lot for your prompt answer. I will report upstream once I have rebuild a custom kernel with the CONFIG_BOOT_PRINTK_DELAY option and will let you know. Sorry for the video, I did not realize about the indirect link. I will try to give a more direct link or find another site for hosting the new video. Regards Pascal Dormeau Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619433: linux-image-2.6.38-1-686: early crash with ACPI (regression)
Package: linux-2.6 Version: 2.6.38-1 Severity: important Hello, My laptop cannot boot anymore with latest 2.6.38 kernel (also tested with all available 2.6.38 rc in experimental) while ACPI support is enabled. As mentioned in the object, I suspect an ACPI related problem. Indeed booting with ACPI=off allows ending the boot sequence but many functionalities are lost including the cardbus support and consequently the wifi connexion (I must admit that I have not investigated a lot how to recover it without acpi). I wish I could have ACPI support as I had with all older kernels up to 2.6.37. I am currently running 2.6.37-2-686 version without any problem. I cannot provide a descent dmesg output because the crash occurs early in the boot. I recorded the boot and the video is available at http://dl.free.fr/kUzM29dEp but I fair it does not give usefull information. I am aware that only this and lspci output do not result in a valuable bug report. Could you please tell me what usefull information I could provide? Can a dmesg from the working 2.6.37 help ? Can a dmesg with 2.6.38 and ACPI=off help ? Thanks in advance for advice. Regards Pascal Dormeau -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: ATI Technologies Inc R200 AGP Bridge [Mobility Radeon 7000 IGP] [1002:cab3] (rev 05) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 Region 0: Memory at b000 (32-bit, prefetchable) [size=64M] Region 1: Memory at b400 (32-bit, prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: agpgart-ati 00:01.0 PCI bridge [0604]: ATI Technologies Inc PCI Bridge [IGP 340M] [1002:7010] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: c000-dfff Memory behind bridge: e000-efff Prefetchable memory behind bridge: a000-afff Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:13.0 USB Controller [0c03]: ATI Technologies Inc OHCI USB Controller #1 [1002:4347] (rev 01) (prog-if 10 [OHCI]) Subsystem: Toshiba America Info Systems Device [1179:ff10] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at f0001000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:13.1 USB Controller [0c03]: ATI Technologies Inc OHCI USB Controller #2 [1002:4348] (rev 01) (prog-if 10 [OHCI]) Subsystem: Toshiba America Info Systems Device [1179:ff10] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at f0002000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:13.2 USB Controller [0c03]: ATI Technologies Inc EHCI USB Controller [1002:4345] (rev 01) (prog-if 20 [EHCI]) Subsystem: Toshiba America Info Systems Device [1179:ff10] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at 5c00 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc SMBus [1002:4353] (rev 18) Subsystem: Toshiba America Info Systems Device [1179:ff10] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Region 0: I/O ports at e000 [size=16] Region 1: Memory at f000 (32-bit, non
Bug#602242: actually only a layout problem
Hi Michael Thanks to the fix for #602101, I could narrow the problem. This is due to numbers in password (again). Indeed the problem I reported does not more exist if I use the numpad (provided i3lock is built with the fix for #602101). Therefore i3lock actually remains responsive but the problem is still here. I must mention that I use a french keyboard layout with: XKBMODEL=pc105 XKBLAYOUT=fr XKBVARIANT=oss XKBOPTIONS=lv3:ralt_switch,compose:rwin If I do not use the numpad, I need to use the shift key for numbers (using keys from first row). And this does not work, unless a key (any one) has been hit before i3lock is started. I also noticed that if I use the capslock key instead of the shift key for numbers (only for numbers because capital and minuscule letters are also inverted), I can authenticate. BTW, the simplest test case I found is: startx -- :3 with .xinitrc containing: sleep 5 i3lock -n The sleep command allows testing the impact of a key being hit before i3lock is started. To sum up (tested with latest version from git tree): - no key hit before i3lock starts; numbers with numpad - ok - no key hit before i3lock starts; numbers with capslock and first row- ok - no key hit before i3lock starts; numbers with shift key and first row- fail - random key hit before i3lock starts - ok anyway Moreover, for the cases were no key is hit before i3locks start, the following message is printed on the console (from which startx is launched): WARNING: unhandled event of type 34 Hope this additional information can help. Kind regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602101: i3lock: Using numpad: Keysym could not be converted to UCS
On Mon, 08 Nov 2010 14:53:16 +0100 Michael Stapelberg michael+db20090...@stapelberg.de wrote: Hi Pascal, This bug should be fixed in the latest git version of i3lock [1]. Can you please install it and confirm? The fix will be included in the next release. Best regards, Michael [1] http://code.stapelberg.de/git/i3lock/ Hi Michael, I cloned latest git tree and built the binary: I confirm it is fixed now. Thanks a lot, Michael Best regards Pascal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602242: i3lock remains unresponsive if no key has been struck before it is launched
Package: i3lock Version: 2.0-2 Severity: minor Hello, This is a problem I met since upgrade to i3lock 2.0 (no problem with 1.0 version). It happens if the keyboard is not used after the X server is started and before i3lock is launched. Typically using startx and launching i3lock as first client in the X session (if I use xdm there is no problem since xdm forces me to type my username and password) If I write in my .xsessionrc the following: sleep 5 i3lock -n and I launch the X server using startx, if I don't strike any keyboard key during the 5 s period, i3lock will then remain unresponsive once started. If I strike some keys within the 5 s period, i3lock will unlock screen after I type the password. The example above is a corner case. But another more common case where it could happen is when launching the X session with startx, being disturbed by something (e.g. phone) and leaving the computer, with i3lock being started automatically by xautolock. Kind regards Pascal Dormeau -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages i3lock depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libpam0g 1.1.1-6.1 Pluggable Authentication Modules l ii libxcb-dpms0 1.6-1 X C Binding, dpms extension ii libxcb-image0 0.3.6-1utility libraries for X C Binding ii libxcb-keysyms1 0.3.6-1utility libraries for X C Binding ii libxcb-shm0 1.6-1 X C Binding, shm extension ii libxcb1 1.6-1 X C Binding i3lock recommends no packages. i3lock suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602101: i3lock: Using numpad: Keysym could not be converted to UCS
Package: i3lock Version: 2.0-2 Severity: minor Hello, When password contains numerals it is not possible to unlock screen using numpad. I get the following message for each typed number: Keysym could not be converted to UCS, skipping This only affects version in unstable, I checked that version in testing (1.0) still offers numpad support. There is a chance that it is a libxcb related problem but I do not know how to get more clues, feel free to reassign in this case. Thanks for developing and maintaining i3lock. Best regards, Pascal Dormeau -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages i3lock depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libpam0g 1.1.1-6.1 Pluggable Authentication Modules l ii libxcb-dpms0 1.6-1 X C Binding, dpms extension ii libxcb-image0 0.3.6-1utility libraries for X C Binding ii libxcb-keysyms1 0.3.6-1utility libraries for X C Binding ii libxcb-shm0 1.6-1 X C Binding, shm extension ii libxcb1 1.6-1 X C Binding i3lock recommends no packages. i3lock suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596467: Please make libsane-hpaio recommend hplip (not depend on)
- Till Kamppeter till.kamppe...@gmail.com a écrit : Much better this way. I have implemented it as follows now (in the Debian SVN repo, release 3.10.6-1ubuntu7): - libsane-hpaio recommends hplip. - The file /etc/hp/hplip.conf moved from hplip to libsane-hpaio. This makes libsane-hpaio work without hplip. - As hplip needs /etc/hp/hplip.conf hplip depends on libsane-hpaio again, as before (It was even wrong to lift this dependency as /usr/share/hplip/data/models/models.dat was already in libsane-hpaio). Now it is assured that libsane-hpaio always works and minimum installations are possible. Till Hi Till, Glad to see that did not chose the depend way. However, i have a remark about the hplip.conf file. Before this bug was opened, I tried to dig myself into the hplip related packages and yes the hplip.conf was shipped (up to now) with the hplip package. It seems that it is still updated after installation through the hplip postinst script (to fix PPD file paths). Could it be harmful (for instance a user that first installs libsane-hpaio then later decides to install hplip)? Well, I raise the question just in case (I guess there is no problem because there is no reason to modify the file with only libsane-hpaio installed), and I am quite sure that you have regarded this already. Thanks anyway Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596467: Please make libsane-hpaio recommend hplip (not depend on)
Hello, I had a look to the way this problem is solved for Ubuntu in Launchpad (make libsane-hpaio depend on hplip) and I believe this solution will prevent users from installing libsane-hpaio in stand-alone (without hplip), as publicized in the package description: This package is useful for a minimal footprint headless scanning solution I may have seen only a limited part of the problem, but from my own experience, it seems that the only thing missing is a /etc/hp/hplip.conf containing a stanza with the path to the data directory. Like this: [dirs] home=/usr/share/hplip And of course, a little explanation in a README.Debian. Making libsane-hpaio recommend hplip will prevent problems for most users, and will allow minimal installation (I can use my psc1510 with only hpijs and libsane-hpaio), even if creating the /etc/hp/hplip.conf like above solves only a part of the problem encountered by the original poster. Thanks for your attention. Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#456233: gconf2 dependency still needed, package broken
Hello, With 0.14.1-1 version, the following is still automatically added into the postinst file : # Automatically added by dh_gconf if [ $1 = configure ]; then gconf-schemas --register ufraw.schemas fi generating dpkg errors and breaking the installation if gconf2 is not installed (gconf2 is no more a dependency). Similar problem with prerm and postrm scripts. I guess this is because of the 'dh_gconf -n' line in the rules file, I still believe that this line could be commented as I suggested in the original bug report (provided the postinst script makes proper registration). As far as the postinst (or prerm) script still makes call to gconf-schemas without checking if it is installed, the gconf2 dependency is still unavoidable (I am wondering if dh_gconf should not do this check by itself, that would be much simpler). I am sorry to have inspired such a modification that prevents the package to be installed and finally breaks it. Best regards, Pascal Dormeau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501828: slim 1.3.0-1 - Cannot stop daemon
Package: slim Version: 1.3.0-1 Severity: normal Hello, The following happens when slim has been started but no X session is launched (user not yet logged in or user already logged out). 'kill -TERM pid' (where pid is pid number for slim daemon) does not stop slim. The command in the /etc/init.d/slim script: 'start-stop-daemon --stop --pid-file /var/run/slim.lock --name slim --retry TERM/5/TERM/5' fails with: Program slim, 1 process(es), refused to die As a consequence 'invoke-rc.d slim stop' fails with: slim not responding to TERM signals (same with 'invoke-rc.d slim restart') The only way I found for stopping slim in such case is to use: 'kill -9 pid' (but it does not even stop the X server process). When a X session has been launched (user logged in) the daemon is stopped (with X server stopped also) by 'invoke-rc.d slim stop' as expected. Best regards, Pascal Dormeau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491568: sylpheed: Segmentation fault
Hello, I observe something similar here (segmentation fault). For me this happened after upgrading libgtk2.0-0 to 2.12.11-2 (current sid version). Downgrading libgtk2.0-0 to 2.12.10-2 again (current testing version) solves it. Best regards, Pascal Dormeau. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477200: epdfview: segmentation fault when opening print dialog
Package: epdfview Version: 0.1.6-3 Severity: normal Hello, I got a segmentation fault when trying to open the print dialog. This never happened to me before epdfview entered into Debian (before I used to run the svn trunk version and since that, I have never tried to print a pdf file). Moreover, there is no crash when I open the print dialog while the cups server is not running (but of course the print dialog is empty: no printer queue). I found that it maybe related to something that was corrected in rev. 281 of svn trunk (Added check to prevent segfaults while opening the print dialog if the PPD file doesn't have the option that was requrested), then introduced in svn trunk after 0.1.6 release. Indeed, after rebuilding epdfview package with the patch directly taken from svn (in attachment, I just put it into the debian/patches directory), I can now run epdfview without any crash when trying to open the print dialog. By the way, what to you think of packaging epdfview from a recent svn trunk snapshot? It seems more mature and brings many improvements. And as far as I remember it is at least as stable as the 0.1.6 release. Best regards, Pascal Dormeau --- /trunk/src/PrintPter.cxx (revision 262) +++ /trunk/src/PrintPter.cxx (revision 281) @@ -231,17 +231,24 @@ view.clearPageSizeList (); int pageSizeToSelect = 0; -ppd_choice_t *pageSizeChoice = pageSizeOption-choices; -for ( int currentSize = 0 ; - currentSize pageSizeOption-num_choices ; - ++currentSize, ++pageSizeChoice ) -{ -const gchar *sizeName = pageSizeChoice-text; -const gchar *sizeValue = pageSizeChoice-choice; - -view.addPageSize (_(sizeName), sizeValue); -if ( pageSizeChoice-marked ) +if ( 0 != pageSizeOption ) +{ +ppd_choice_t *pageSizeChoice = pageSizeOption-choices; +for ( int currentSize = 0 ; + currentSize pageSizeOption-num_choices ; + ++currentSize, ++pageSizeChoice ) { -pageSizeToSelect = currentSize; +const gchar *sizeName = pageSizeChoice-text; +const gchar *sizeValue = pageSizeChoice-choice; + +view.addPageSize (_(sizeName), sizeValue); +if ( pageSizeChoice-marked ) +{ +pageSizeToSelect = currentSize; +} } +} +else +{ +view.addPageSize (_(A4), A4); } view.selectPageSize (pageSizeToSelect); @@ -252,17 +259,24 @@ view.clearResolutionList (); int resolutionToSelect = 0; -ppd_choice_t *resolutionChoice = resolutionOption-choices; -for ( int currentRes = 0 ; - currentRes resolutionOption-num_choices ; - ++currentRes, ++resolutionChoice ) -{ -const gchar *resName = resolutionChoice-text; -const gchar *resValue = resolutionChoice-choice; - -view.addResolution (_(resName), resValue); -if ( resolutionChoice-marked ) +if ( 0 != resolutionOption ) +{ +ppd_choice_t *resolutionChoice = resolutionOption-choices; +for ( int currentRes = 0 ; +currentRes resolutionOption-num_choices ; +++currentRes, ++resolutionChoice ) { -resolutionToSelect = currentRes; +const gchar *resName = resolutionChoice-text; +const gchar *resValue = resolutionChoice-choice; + +view.addResolution (_(resName), resValue); +if ( resolutionChoice-marked ) +{ +resolutionToSelect = currentRes; +} } +} +else +{ +view.addResolution (_(300 DPI), 300x300dpi); } view.selectResolution (resolutionToSelect); @@ -272,7 +286,7 @@ ppdFindOption (printerPPD, ColorModel); view.clearColorModelList (); +int colorModelToSelect = 0; if ( NULL != colorModelOption ) { -int colorModelToSelect = 0; ppd_choice_t *colorModelChoice = colorModelOption-choices; for ( int currentColor = 0 ; @@ -289,5 +303,4
Bug#475249: Problem with tty console: confirmed
Hello, I confirm a strange behavior of the tty console from which slim is launched: the most visible aspect is that the keyboard is very slow. The problem is bearable at the beginning (just after slim has launched the X session), but worsens with time to the point the tty console is no more usable. I now avoid using the tty1 console. slim is normally started from tty1, but if I restart slim from tty2 for instance, then the problem appears on tty2 instead of tty1. Note that I do not observe any problem with slim running until and an X session is launched. Problems stop as soon as I disconnect from the X session. It does not seem to be related to the X session type (xfce4, fluxbox, ...). If I start my X session, logging on the console as user and using startx instead of slim, there is no problem with the tty console. As far as I remember, the problem was already present with previous version 1.2.6. Best regards, Pascal Dormeau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471061: audacious 1.5.0-1: please disable sse2 support
Just to mention in case you decide to disable sse2 on all architectures: I checked on wikipedia and it seems that sse2 is supported by all x86-64 CPUs and should not be harmful on amd64 architecture (which is not the case for i386, not all CPUs are supporting SSE2). Same article says that the increase in performance is not significant... Best regards. Pascal Dormeau
Bug#471061: audacious 1.5.0-1: please disable sse2 support
Package: audacious Version: 1.5.0-1 Severity: normal audacious 1.5.0-1 cannot run (illegal instruction) on my old PIII machine whereas there is no problem on my laptop (PIV cpu). I guess this is because audacious has been built with sse2 support (enabled by default). Rebuilding the package with explicit --disable-sse2 configure instruction in the debian/rules file solves the problem for me. Best regards. Pascal Dormeau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457763: xserver-xorg-video-ati: sets wrong DPI after upgrade from 6.6.193-3 to 6.7.197-1
Package: xserver-xorg-video-ati Version: 1:6.7.197-1 Severity: normal With 6.7.197-1, the log reports: (**) RADEON(0): Display dimensions: (304, 228) mm (**) RADEON(0): DPI set to (85, 114) and xdpyinfo | grep resolution reports resolution:96x96 dots per inch Whereas with 6.6.193-3 version DPI set to (85, 85) in the log and xdpyinfo | grep resolution reports resolution:85x85 dots per inch The 304 x 228 mm dimensions are specified in the xorg.conf. Best regards. Pascal Dormeau -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2006-07-04 21:51 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1672764 2007-12-22 01:43 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility 7000 IGP /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 4869 2007-12-25 12:45 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (Xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom # md5sum /etc/X11/xorg.conf /var/lib/x11/xorg.conf.md5sum # dpkg-reconfigure xserver-xorg Section Files # local font server # FontPath unix/:7100 # if the local font server has problems, we can fall back on these # FontPath /usr/share/fonts/X11/misc:unscaled # FontPath /usr/share/fonts/X11/100dpi:unscaled # FontPath /usr/share/fonts/X11/75dpi:unscaled # FontPath /usr/share/fonts/X11/Type1 ##FontPath /usr/share/fonts/X11/Speedo # FontPath /usr/share/fonts/X11/100dpi # FontPath /usr/share/fonts/X11/75dpi # FontPath /usr/share/fonts/truetype/openoffice # Fonts handled by defoma and x-ttcidfont-conf # FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType ##FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/CID EndSection Section ServerFlags Option StandbyTime 1 Option SuspendTime 2 Option OffTime 3 EndSection Section Module # LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri # Loadevdev # not used Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord # Loadtype1 # does not exist Loadvbe Loadsynaptics EndSection Section Extensions Option Composite Disable EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout fr(oss) EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice Driver synaptics Identifier touchpad Option Device/dev/psaux Option Protocol auto-dev Option LeftEdge 1700 Option RightEdge 5300 Option TopEdge 1700 Option BottomEdge4200 Option FingerLow 25 Option FingerHigh30 Option MaxTapTime180 Option MaxTapMove220 Option VertScrollDelta 100 Option MinSpeed 0.06 Option MaxSpeed 0.12 Option AccelFactor 0.0010 # Option SHMConfig on # Option Repeater /dev/ps2mouse EndSection Section Device Identifier Radeon 7000 IGP Driver radeon BusID PCI:01:05:0 Option AGPMode 4
Bug#456233: ufraw: gconf2 dependency no more needed
Package: ufraw Version: 0.13-1 Severity: wishlist According to http://lists.debian.org/debian-devel/2007/11/msg00030.html, ufraw dependency on gconf2 should not be needed anymore, since the functionality is optional. Could you please remove gconf2 dependency for next package release ? Thanks in advance. Note that the postinst and prerm scripts installed by dh_gconf do not test if gconf-schemas is available, therefore a possibility is to comment the dh_gconf line in the rules file and to add modified scritps. Examples in attachment. Best regards, Pascal Dormeau ufraw.postinst Description: Binary data ufraw.postrm Description: Binary data ufraw.prerm Description: Binary data
Bug#454985: xfce4-utils: /etc/xdg/xfce4/xinitrc needs x11-xserver-utils
Package: xfce4-utils Version: 4.4.2-1 Severity: wishlist /etc/xdg/xfce4/xinitrc makes use of xrdb, xmodmap, xsetroot... that belong to x11-xserver-utils. Does not this mean that xfce4-utils should now depend on x11-xserver-utils ? Best regards. Pascal Dormeau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454985: xfce4-utils: /usr/bin/startxfce4 needs xinit
Sorry, I submitted too quickly, and forgot this one: there is also a chance that xfce4-utils also depends on xinit. This is related to the same root cause (xbase-clients now being a metapackage and and xserver-xorg depending on x11-xkb-utils only) then I do not submit a new bug report. Best regards, Pascal DORMEAU -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446811: sylpheed_claws scriptlet: XAUTHORITY may not be exported
Package: hibernate Version: 1.96~pre-svn.r1136-1 Severity: wishlist Hello The sylpheed_claws scriptlet makes the implicit assumption that the XAUTHORITY variable is exported when calling get_env_var_of_process. Given my poor understanding of the X session mechanism, I might probably be wrong, but I suspect that XAUTHORITY is not always exported and that even more, it is not mandatory at all to export it. Provided the here above assumption is correct, the xauthority variable obtained thru get_env_var_of_process might sometimes be empty and the commands using the variable in the scriptlet might fail. Shouldn't sylpheed_claws scriptlet make the additional checking that xauthority variable is not empty and fall back to $HOME/.Xauthority to give itself a chance to succeed? It seems that it is what the main script does within FindXServer(): it does not rely only on /proc/pid/environ and proceeds to additional checkings. The proposed patch for sylpheed_claws in attachment is inspired by FindXServer() and proceeds to the same checkings. It applies to current SVN upstream trunk (rev. 1161). In the other hand I might be completely wrong because maybe my x-session-manager does not behave correctly or because I should always export XAUTHORITY in my .Xession (I used to export XAUTHORITY as a simple mean to be able to launch X applications after su to root but I recently dropped it in favor of pam_xauth...and hibernate is the only drawback I found). Best regards. Pascal D. --- sylpheed_claws 2007-10-15 20:55:33.0 +0200 +++ sylpheed_claws.new 2007-10-15 21:37:20.0 +0200 @@ -20,11 +20,17 @@ local pid i=0 for pid in `pidof sylpheed-claws`; do - local user display xauthority + local user display xauthority xhome + +[ -d /proc/$pid/ ] || continue user=$(get_env_var_of_process $pid USER) display=$(get_env_var_of_process $pid DISPLAY) xauthority=$(get_env_var_of_process $pid XAUTHORITY) +xhome=$(get_env_var_of_process $pid HOME) +[ -z $xauthority ] [ -n $xhome ] [ -f $xhome/.Xauthority ] xauthority=$xhome/.Xauthority + +[ -z $xauthority ] continue # using this eval-crap to be POSIX-compliant (arrays are nonstandard) eval SYLPHEEDCLAWS_LOGGED_OUT_SESSIONS_USER_$i='$user'
Bug#433003: Suggestion: moving get_env_var_of_process into the main script
martin f krafft a écrit : Argh! sylpheed_claws and galeon weren't supposed to be included. But are you using them? I am uneasy including them since it's too far off hibernate's real job, but if people use them, why not? To be honest I am not using them but the sylpheed_claws scriplet inspired me for solving a problem I had with conky. Therefore I am using the get_env_var_of_process function... Maybe such scriplets could be located in a /usr/share/doc/hibernate/contrib or /usr/share/doc/hibernate/examples section? Or in the sylpheed-claws and galeon packages themselves ? Would you prepare a patch for me? Sorry I should have started with it, please forgive my rudeness. get_env_var_of_process has been moved to the Helper functions section in the attached patch. Best regards. Pascal D. diff -Naur hibernate-1.96~pre-svn.r1136/hibernate.sh hibernate-1.96~pre-svn.r1136.new/hibernate.sh --- hibernate-1.96~pre-svn.r1136/hibernate.sh 2007-07-04 19:41:43.0 +0200 +++ hibernate-1.96~pre-svn.r1136.new/hibernate.sh 2007-07-14 20:12:06.0 +0200 @@ -810,6 +810,14 @@ SUSPEND_ABORT=1 } +# Gets the value of the environment variable with the given name of the process with the given PID. +get_env_var_of_process() +{ +local pid=$1 envvar=$2 + +tr '\0' '\n' /proc/$pid/environ | sed -ne 's/^'$envvar'=\(.*\)$/\1/p' +} + ### MAIN # # Some starting values: diff -Naur hibernate-1.96~pre-svn.r1136/scriptlets.d/gaim hibernate-1.96~pre-svn.r1136.new/scriptlets.d/gaim --- hibernate-1.96~pre-svn.r1136/scriptlets.d/gaim 2007-07-09 22:44:07.0 +0200 +++ hibernate-1.96~pre-svn.r1136.new/scriptlets.d/gaim 2007-07-14 20:13:05.0 +0200 @@ -11,14 +11,6 @@ AddConfigHelp GaimLogoutMessage string Status message to set when logging out Gaim. AddConfigHelp GaimLoginMessage string Status message to set when logging in Gaim. -# Gets the value of the environment variable with the given name of the process with the given PID. -get_env_var_of_process() -{ -local pid=$1 envvar=$2 - -tr '\0' '\n' /proc/$pid/environ | sed -ne 's/^'$envvar'=\(.*\)$/\1/p' -} - LogoutGaim() { [ x$LOGOUT_GAIM != x1 ] return 0 diff -Naur hibernate-1.96~pre-svn.r1136/scriptlets.d/galeon hibernate-1.96~pre-svn.r1136.new/scriptlets.d/galeon --- hibernate-1.96~pre-svn.r1136/scriptlets.d/galeon 2007-07-14 20:03:32.0 +0200 +++ hibernate-1.96~pre-svn.r1136.new/scriptlets.d/galeon 2007-07-14 20:12:50.0 +0200 @@ -10,14 +10,6 @@ AddConfigHelp GaleonOffline boolean Changes all locally running Galeon's status to offline before suspending, and (optionally) change it back to the original state after resuming. AddConfigHelp GaleonRestoreStatus boolean Change status of Galeon back to the original state after resuming. -# Gets the value of the environment variable with the given name of the process with the given PID. -get_env_var_of_process() -{ -local pid=$1 envvar=$2 - -tr '\0' '\n' /proc/$pid/environ | sed -ne 's/^'$envvar'=\(.*\)$/\1/p' -} - GaleonOffline() { [ x$GALEON_OFFLINE != x1 ] return 0 diff -Naur hibernate-1.96~pre-svn.r1136/scriptlets.d/sylpheed_claws hibernate-1.96~pre-svn.r1136.new/scriptlets.d/sylpheed_claws --- hibernate-1.96~pre-svn.r1136/scriptlets.d/sylpheed_claws 2007-07-14 20:03:32.0 +0200 +++ hibernate-1.96~pre-svn.r1136.new/scriptlets.d/sylpheed_claws 2007-07-14 20:12:25.0 +0200 @@ -9,14 +9,6 @@ AddConfigHelp SylpheedClawsOffline boolean Changes status of all locally running Sylpheed Claws to offline before suspending, and (optionally) change it to online after resuming. AddConfigHelp SylpheedClawsOnline boolean Changes status of all locally running Sylpheed Claws to online after resuming. -# Gets the value of the environment variable with the given name of the process with the given PID. -get_env_var_of_process() -{ -local pid=$1 envvar=$2 - -tr '\0' '\n' /proc/$pid/environ | sed -ne 's/^'$envvar'=\(.*\)$/\1/p' -} - SylpheedClawsOffline() { [ x$SYLPHEEDCLAWS_OFFLINE != x1 ] return 0
Bug#433003: Suggestion: moving get_env_var_of_process into the main script
Package: hibernate Version: 1.96~pre-svn.r1136-1 Severity: wishlist hibernate 1.96~pre-svn.r1136-1 introduced a new function: get_env_var_of_process(). It is included in gaim, sylpheed_claws and galeon scriptlets. It is very efficient and useful and because the gaim, sylpheed_claws and galeon scriptlets are sourced into the main script, it is in fact available for any other scriptlet. But people writing custom scriptlets are not necessarily aware of its existence (unless reading each scriptlet one by one). May I suggest to move this function into the main script? I am conscious that there is no problem with the current situation and that moving it into the main script is pure comestic but it would also better comply with the SCRIPTLET-API that recommends that Function and variable names within the scriptlet should be sufficiently unique. Note that it could also be used in the main script (lines 225 to 227 for instance). Best regards. Pascal D. PS: there may be also a typo in the function description, as far as I understand, it does not use the process name. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431886: xfce4-session: please allow dbus support for shutdown/reboot with hal
Package: xfce4-session Version: 4.4.4-1 Severity: wishlist The README file states that if you have HAL installed on your system, and your account is allowed to shutdown/reboot the computer using HAL, you don't need to setup sudo at all. This works only if: - the user belongs to the powerdev group, - xfce4-session is built against libdbus-1-dev which is not the case currently (xfce4-session-4.4.1/xfce4-session/xfsm-shutdown-helper.c uses dbus functions). Could you please build xfce4-session against libdbus-1-dev ? I rebuilt it on my box with dbus support and I can now shutdown/reboot without sudo at all. If libdbus-1-dev is installed, xfce4-session is build with dbus support by default (according to configure file --enable-dbus is the default, --with-shutdown-style=hal flag in the current rules file does not seem to be considered). The only drawback is a new dependency (on libdbus-1-3) and maybe dbus as 'recommends' (to have the dbus daemon running). This could also help a little with #379192. Best regards. Pascal D. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409502: xarchiver: Icons for Add and Extract at wrong location
Hello, Could it be that xarchiver expects to find those icons in $DATADIR/pixmaps/xarchiver aka /usr/share/pixmaps/xarchiver (cf. xarchiver-0.4.6/src/support.c) but they are moved to another location during package build (to /usr/share/icons/pixmaps/xarchiver) ? Removing the line: 'mv debian/xarchiver/usr/share/pixmaps debian/xarchiver/usr/share/icons' in the debian/rules file seems to fix the issue (since 'make install' already puts the icons at the expected location). Best regards. Pascal D. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403247: no automatic refresh also with thunar_0.8.0-1
Michael Banck a écrit : So, Maximiliano Curia found an upstream patch which fixes things for him. Could you all please install and test gamin_0.1.8-2 from deb http://people.debian.org/~mbanck/unstable/ ./ or http://people.debian.org/~mbanck/unstable/gamin_0.1.8-2_i386.deb http://people.debian.org/~mbanck/unstable/libgamin0_0.1.8-2_i386.deb again? Sorry about the same package name, just use --reinstall for apt-get or so. Does this fix thunar and/or pcmanfm for you. Hi Michael, Fixed for me also. Tested with: thunar_0.4.0rc1-3 + libthunar-vfs-1-2_0.4.0rc1-3 (testing) thunar_0.5.0rc2-1 + libthunar-vfs-1-2_0.5.0rc2-1 (unstable) thunar_0.8.0-1 + libthunar-vfs-1-2_0.8.0-1 (experimental) pcmanfm_0.3.2.2-1 (testing/unstable) So far, I could not trigger the bug, and I did not meet any problem. Note that I did not tested very extensively because I checked the three thunar versions this evening (I originally reported the bug against the thunar version in testing) and each time I had to make sure that the new thunar version was correctly taken into account, that the gam_server was correctly started by the corresponding version, that there were not other environment side effect (in practice, I killed the gam_server and restarted the xfce4-session). I probably did not do it so carefully when I too early announced that the problem was solved with thunar_0.8.0-1 two weeks ago. I do not have the skills to understand Maximiliano explanations about why the patch fixes the bug, but I trust him because it works now. Thank you, Michael and Maximiliano. Pascal D.
Bug#403247: no automatic refresh also with thunar_0.8.0-1
Michael Banck a écrit : Hi, can you guys maybe try the following gamin_0.1.8-2 package, and see whether it fixes your problems? http://people.debian.org/~mbanck/unstable/gamin_0.1.8-2_i386.deb http://people.debian.org/~mbanck/unstable/libgamin0_0.1.8-2_i386.deb Hello again Michael, I tested gamin_0.1.8-2 (I took care to kill everything: stopping xfce4-session, killing gam_server to be sure not to use the 0.1.8-1 version, restarting xfce4-session). But unfortunately the problem is still there. I also noticed: - if /mnt/archives (/etc/fstab: /dev/hda15 /mnt/archives ext3 noauto,user 0 0 ) is mounted before thunar and gam_server are started, and if I navigate with thunar inside, thunar is no more notified by gam_server (the problem is not triggered by the fact the file system is mounted, but rather more by the fact thunar is used to navigate inside), I extended the test to other file systems/media: - if I mount a usb stick and if I navigate with thunar inside, thunar is no more notified by gam_server, - if I mount a CDROM and navigate with thunar inside, thunar is still notified by gam_server (test repeated twice only). Could it have something to do with the user 's ownership on the concerned file systems? It seems (as far as I can see) that it only occurs when the user has write permission on given file system and thunar is used to navigate inside. No more clue here. Best regards. Pascal D.
Bug#403247: no automatic refresh also with thunar_0.8.0-1
Michael Banck a écrit : Can you try to add (or create) either poll /mnt/archives or notify /mnt/archives to your ~/.gaminrc and see if any of those help? I tested both, but none of them helps. Other interesting thing (maybe not relevant): - I navigate inside the faulty directory (I know it will make thunar not being notified by gam_server anymore), - I open ~/tmp with thunar, - I check if gam_server is still running: OK - in xfce4-terminal I run 'touch tmp/test0', thunar is not notified (that 's the bug), - I check if gam_server is still running:OK - I make a manual refresh, - I check if gam_server is still running: gam_server has been killed. Note that it may be the expected behavior: maybe thunar kills gam_server on purpose since it knows gam_server is no more useful. Best regards. Pascal D.
Bug#403247: no automatic refresh also with thunar_0.8.0-1
Michael Banck a écrit : How exactly are you reproducing this? Do you have a directory open in thunar and try touch foo, touch bar, rm foo, rm bar etc.? Yes, $HOME/tmp is opened in Thunar and from xfce4-terminal I run 'touch tmp/test0', 'rm tm/test0'. This is the method I use to check if thunar self-refreshes (or not). If you do that, does thunar get notified after the second or third operation at least? No, never, the only way to get thunar notified is to perform a manual refresh (click on refresh button or hit ctrl r). Just like gam_server had died (but it seems to have not, according to 'ps'). I could reproduce it again tonight. This how I triggered it: I have the following line in my /etc/fstab: /dev/hda15 /mnt/archives ext3 noauto,user 0 0 First I mount /mnt/archives (using mount in xfce4-terminal), then I navigate inside /mnt/archives using thunar. Starting from that moment, thunar does not self-refresh anymore (whatever the directory opened in thunar). I repeated the operation several times (leaving the Xfce4-session and re-entering into between). Each time, I triggered the problem once entering into /mnt/archives with thunar. This does not happen with gamin_0.1.7-4 (only with gamin_0.1.8-1). I don't know if that helps. Best regards. Pascal D.
Bug#403247: no automatic refresh also with thunar_0.8.0-1
The good news is that the symptoms I described previously for #403247 have disappeared with thunar_0.8.0-1 and gamin_0.1.8-1. But the Debian Sorry, I reported too quickly, I finally encountered problems today with gamin_0.1.8-1 and thunar_0.8.0-1 not auto refreshing. Please note that upgrading to a thunar version built against libfam-dev may then not be a reliable solution (as I half suggested in a previous message). Unfortunately, I don't know how to reproduce it. It is strange because I have been using it for 10 days without noticing any problem. Best regards, Pascal D. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403247: automatic refresh came back with thunar-0.8.0-1
Since I opened this bug (it concerned problems with thunar 0.4.0rc1-2 and 0.5.0rc2-1 versions), I have upgraded to thunar_0.8.0-1 (the one in experimental) but I have kept gamin_0.1.7-4 to Pin-Priority 1001 in my apt/preferences until today. After reading a message related to #410929 and #403247 on the pkg-xfce-devel list archives, I remembered that I opened #403247 report bug and that it was worth checking if the bug was still there with thunar_0.8.0-1. I gave a try again to gamin_0.1.8-1. The good news is that the symptoms I described previously for #403247 have disappeared with thunar_0.8.0-1 and gamin_0.1.8-1. But the Debian changelog indicates that thunar_0.8.0-1 is now built against libfam-dev instead of libgamin-dev as for previous thunar versions... The following thread on the thunar-dev list let me believe however that something happened between gamin_0.1.7 and gamin_0.1.8: http://foo-projects.org/pipermail/thunar-dev/2007-January/003895.html Best regards, Pascal D. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403247: No more automatic refresh since last gamin update
Yves-Alexis is right, I first reported against the wrong package (and I wrongly named the bug report). I tested last gamin version with pcmanfm, and same bug as with thunar occurs. After doing some testings with 0.1.8-1 version, I noticed that automatic refresh is lost after mounting a partition (I have not performed extended testings, for the present case it is a partition on the local drive. Not tested with a removable media for instance). Before mounting any partition, it works flawlessly. Regards. Pascal D. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403247: thunar: No more automatic refresh since last gamin update
Package: thunar Version: 0.4.0rc1-2 Severity: minor I am not sure it is gamin's fault or thunar's fault. Please forgive if I report to the wrong package: Thunar does not automatically resfresh directories anymore (need to perform manual refresh or ctrl r after a new file is created or deleted in order to see the change in the directory) since last gamin/libgamin0 update (I think from 0.1.7-4 to 0.1.8-1). Current thunar version for testing is 0.4.0rc1-2 (but tested with 0.5.0rc2-1: same). When I revert gamin version to 0.1.7.4, thunar behaves as before. Regards. Pascal D. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19-1.raisin.1 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages thunar depends on: ii desktop-file-utils 0.11-1Utilities for .desktop files ii libatk1.0-01.12.3-1 The ATK accessibility toolkit ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libdbus-1-31.0.2-1 simple interprocess messaging syst ii libdbus-glib-1-2 0.71-3simple interprocess messaging syst ii libexo-0.3-0 0.3.1.12rc2-1 Library with extensions for Xfce ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libgtk2.0-02.8.20-3 The GTK+ graphical user interface ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libpango1.0-0 1.14.8-2 Layout and rendering of internatio ii libsm6 1:1.0.1-3 X11 Session Management library ii libthunar-vfs-1-2 0.4.0rc1-2VFS abstraction used in thunar ii libxfce4util4 4.3.99.2-1Utility functions library for Xfce ii shared-mime-info 0.19-1FreeDesktop.org shared MIME databa ii xfce4-panel4.3.99.2-1The Xfce4 desktop environment pane Versions of packages thunar recommends: ii hal 0.5.8.1-4 Hardware Abstraction Layer ii pmount 0.9.13-1+b1 mount removable devices as normal -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380519: vlc: Can't drag and drop
Rémi Denis-Courmont a écrit : Drag'n'Drop works. But the source application inserted a bogus carriage return at the end of the filename. Please reassign the bug to your file browser. I am very sorry, I have not used vlc for quite a long time (because of the alsa debug: recovered from buffer underrun main debug: audio output is starving (x), playing silence problem). Re-tested this morning: with latest thunar version (0.4.0rc1-2) and latest vlc version (0.8.6-svn20061012.debian-1): the bug is no more there, I can drag and drop files in vlc. I believe you can close this bug now (and no need for re-assigning it). Best regards.
Bug#389787: xcdroast should still depend on the cdrecord transition package
Package: xcdroast Version: 0.98+0alpha15-8 Severity: normal For [not hurd-i386, m68k], xcdroast does not strickly depend on cdrecord. However the dependency is still needed as only the cdrecord package provides the symlink (to /usr/bin/wodim). The wodim package itself does not seem to provide such symlink (IMHO it should as it pretends to provide cdrecord, could it be solved with /etc/alternatives ?). [EMAIL PROTECTED] ~]$ xcdroast ** (xcdroast:5142): WARNING **: No /usr/bin/cdrecord installed ** (xcdroast:5142): WARNING **: (Invalid lib-directory? Check -l option) Simply adding the symlink by hand allows me starting xcdroast. I fill this bug against xcdroast but it could also concern wodim/cdrkit. Best regards Pascal -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-0.raisin.2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages xcdroast depends on: ii cdda2wav5:1.0~pre4-1 Creates WAV files from audio CDs ii debconf [debconf-2.0] 1.5.4Debian configuration management sy ii libatk1.0-0 1.12.2-1 The ATK accessibility toolkit ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libcairo2 1.2.4-1 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.1-2 generic font configuration library ii libglib2.0-02.12.3-2 The GLib library of C routines ii libgtk2.0-0 2.8.20-1 The GTK+ graphical user interface ii libpango1.0-0 1.12.4-1 Layout and rendering of internatio ii libx11-62:1.0.0-9X11 client-side library ii libxcursor1 1.1.7-4 X cursor management library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-4X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.1-3X11 Input extension library ii libxinerama11:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.1-3X Rendering Extension client libra ii mkisofs 5:1.0~pre4-1 Creates ISO-9660 CD-ROM filesystem ii wodim 5:1.0~pre4-1 command line CD writing tool xcdroast recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383220: CapsShift seems to be ignored by directfb
Package: directfb Severity: normal When I set keyboard to fr-latin9, the shift+key does not work with direcfb. If I add those two lines in my /etc/console-tools/remap: s/keycode 42 = CapsShift/keycode 42 = Shift/; s/keycode 54 = CapsShift/keycode 54 = Shift/; I can use again the shift+key. Note that this has similarities with #339352. Regards, Pascal PS: tested with 0.9-24 and 0.9-25 versions -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-8.raisin.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380519: vlc: Can't drag and drop
Package: vlc Version: 0.8.5.debian-2 Severity: normal Hi, When I want to drag and drop a file to the playlist, I get an error message. There is no problem when I load the file from the menu. In the following output one can see what happens when I try to drag an drop a file: [EMAIL PROTECTED] ~]$ LANG=C vlc - VLC media player 0.8.5 Janus [0001] main vlc debug: opening config file /home/pascal/.vlc/vlcrc [0001] main vlc debug: checking builtin modules [0001] main vlc debug: checking plugin modules [0001] main vlc debug: loading plugins cache file /home/pascal/.vlc/cache/plugins-04041e.dat [0001] main vlc warning: This doesn't look like a valid plugins cache (language changed) [0001] main vlc debug: recursively browsing `modules' [0001] main vlc debug: recursively browsing `/usr/lib/vlc' [0001] main vlc debug: recursively browsing `plugins' [0001] main vlc debug: module bank initialized, found 211 modules [0001] main vlc debug: opening config file /home/pascal/.vlc/vlcrc [0001] main vlc debug: CPU has capabilities 486 586 MMX MMXEXT SSE SSE2 FPU [0001] main vlc debug: looking for memcpy module: 1 candidate [0001] main vlc debug: using memcpy module memcpy [0269] main playlist debug: waiting for thread completion [0269] main playlist debug: thread 3041827760 (playlist) created at priority 0 (playlist/playlist.c:184) [0270] main private debug: waiting for thread completion [0270] main private debug: thread 3033435056 (preparser) created at priority 0 (playlist/playlist.c:210) [0271] main interface debug: looking for interface module: 1 candidate [0271] main interface debug: using interface module hotkeys [0271] main interface debug: thread 3025042352 (interface) created at priority 0 (interface/interface.c:231) [0272] main interface debug: looking for interface module: 1 candidate [0272] main interface debug: using interface module screensaver [0272] main interface debug: thread 3014654896 (interface) created at priority 0 (interface/interface.c:231) [0273] main interface debug: looking for interface module: 5 candidates [0273] main interface debug: using interface module wxwidgets [0273] main interface debug: thread 3006262192 (manager) created at priority 0 (interface/interface.c:216) [0273] wxwidgets interface debug: Using last windows config '(-1,0,0,1024,768)(0,442,75,421,83)(6,0,0,-1,150)' [0273] wxwidgets interface debug: id=0 p=(442,75) s=(421,83) [0273] wxwidgets interface debug: id=6 p=(0,0) s=(-1,150) [0269] main playlist debug: adding playlist item `/home/pascal/tmp/test.ogg ' ( /home/pascal/tmp/test.ogg ) [0269] main playlist debug: creating new input thread [0274] main input debug: waiting for thread completion [0274] main input debug: thread 2997595056 (input) created at priority 0 (input/input.c:261) [0274] main input debug: `/home/pascal/tmp/test.ogg ' gives access `' demux `' path `/home/pascal/tmp/test.ogg ' [0274] main input debug: creating demux: access='' demux='' path='/home/pascal/tmp/test.ogg ' [0275] main demuxer debug: looking for access_demux module: 2 candidates libdvdnav: Using dvdnav version 0.1.9 from http://dvd.sf.net libdvdread: Using libdvdcss version 1.2.9 for DVD access libdvdread: Can't stat /home/pascal/tmp/test.ogg No such file or directory libdvdnav: vm: faild to open/read the DVD [0275] dvdnav demuxer warning: cannot open dvdnav [0274] main input debug: creating access '' path='/home/pascal/tmp/test.ogg ' [0276] main access debug: looking for access2 module: 5 candidates [0276] vcdx access warning: Can't get file status for /home/pascal/tmp/test.ogg : No such file or directory [0276] access_file access warning: /home/pascal/tmp/test.ogg : No such file or directory [0276] cdda access warning: could not open /home/pascal/tmp/test.ogg [0274] main input debug: creating access '' path='/home/pascal/tmp/test.ogg ' [0277] main access debug: looking for access2 module: 5 candidates [0277] vcdx access warning: Can't get file status for /home/pascal/tmp/test.ogg : No such file or directory [0277] access_file access warning: /home/pascal/tmp/test.ogg : No such file or directory [0277] cdda access warning: could not open /home/pascal/tmp/test.ogg [0274] main input error: no suitable access module for `/home/pascal/tmp/test.ogg ' [0274] main input debug: thread 2997595056 joined (input/input.c:399) [0274] main input warning: refcount is 1, delaying before deletion (id=274,type=-7) [0269] main playlist warning: unable to find parent! [0269] main playlist: nothing to play Now, in the same instance, using ctrl-F to open the same file: [0269] main playlist debug: adding playlist item `/home/pascal/tmp/test.ogg' ( /home/pascal/tmp/test.ogg ) [0269] main playlist debug: creating new input thread [0279] main input debug: waiting
Bug#377715: nautilus: Inconsistent volumes display in computer:/// with hal
Package: nautilus Version: 2.14.1-5 Severity: normal I just upgraded from Sarge to Etch With hal installed, computer:/// displays all hard drive volumes as far as they do not belong to the first level of the file system tree (e.g. /dev/hda8 mounted on /usr will not be shown whereas /dev/hda9 mounted on /usr/local will be !). Moreover, all those volumes are named 'Volume size_of_volume' which is not convenient to identify them. It must be added that most of them are not mountable/umountable by a normal user (therefore I do not see the interest for them to be displayed in computer:///). Therefore computer:/// is not usable with hal installed. lshal does not exhibit device property differences that could explain that /dev/hda8 is shown but not /dev/hda9, apart from the mount points. With hal not installed (and it was the behavior in Sarge with hal installed), computer:/// displays only hard drive volumes with mount points in /mnt and /media. Moreover they are nammed in a convenient way (e.g. /dev/hda13 mounted on /mnt/mp3 is called mp3). May be this could be handled through a fdi rule (too difficult for a standard user like me, I do not see how to manipulate the volume.mount_point property) or through the gconf properties (but this lacks documentation). Note that #373087 already mentions a related problem though it does not make the link with hal. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-4.raisin.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages nautilus depends on: ii desktop-file-utils 0.10-1Utilities for .desktop files ii gnome-control-center 1:2.14.2-1utilities to configure the GNOME d ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-01.11.4-2 The ATK accessibility toolkit ii libbonobo2-0 2.14.0-1 Bonobo CORBA interfaces library ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libeel2-2 2.14.1-2 Eazel Extensions Library (for GNOM ii libesd00.2.36-3 Enlightened Sound Daemon - Shared ii libexif12 0.6.13-4 library to parse EXIF files ii libgail-common 1.8.11-2 GNOME Accessibility Implementation ii libgail17 1.8.11-2 GNOME Accessibility Implementation ii libgconf2-42.14.0-1 GNOME configuration database syste ii libglade2-01:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.10.2-1 The GLib library of C routines ii libgnome-desktop-2 2.14.2-2 Utility library for loading .deskt ii libgnome2-02.14.1-2 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.14.0-2 A powerful object-oriented display ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.2-1 GNOME virtual file-system (runtime ii libgtk2.0-02.8.18-1 The GTK+ graphical user interface ii libnautilus-extension1 2.14.1-5 libraries for nautilus components ii liborbit2 1:2.14.0-2libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.12.3-1 Layout and rendering of internatio ii libpopt0 1.10-2lib for parsing cmdline parameters ii librsvg2-2 2.14.4-2 SAX-based renderer library for SVG ii libstartup-notification0 0.8-1 library for program launch feedbac ii libx11-6 2:1.0.0-7 X11 client-side library ii libxml22.6.26.dfsg-1 GNOME XML library ii nautilus-data 2.14.1-5 data files for nautilus ii shared-mime-info 0.17-2FreeDesktop.org shared MIME databa Versions of packages nautilus recommends: ii desktop-base 0.3.17 common files for the Debian Deskto pn eject none (no description available) pn fam none (no description available) pn libgnomevfs2-extranone (no description available) ii librsvg2-common 2.14.4-2 SAX-based renderer library for SVG pn nautilus-cd-burnernone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324363: RESOLVED Mozilla-firefox: What-do-you-want-to-do-with-this-file dialog broken with 1.0.4-2sarge2
I just installed the latest stable release 1.0.4-2sarge3, and the dialog box is fixed now. For me, it is resolved. Thank you for the fix. Pascal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324363: Mozilla-firefox: What-do-you-want-to-do-with-this-file dialog broken with 1.0.4-2sarge2
Package: mozilla-firefox Version: 1.0.4-2sarge2 Severity: normal *** Please type your report below this line *** When I click on a URL pointing to a file, the What-do-you-want-to-do-with-this-file dialog opens during first session only. For instance if I click on http://www.debian.org/doc/manuals/reference/reference.en.pdf, the What-do-you-want-to-do-with-this-file dialog opens and I can chose to view the target file with a pdf-viewer (ex: /usr/sbin/xpdf) or I can chose to download it. If I close mozilla-firefox and open it again, the box will no more appear. In my previous example clicking on http://www.debian.org/doc/manuals/reference/reference.en.pdf will do nothing, the link looks like a dead link. To have the What-do-you-want-to-do-with-this-file dialog working again, I have to do: # dpkg-reconfigure mozilla-firefox. Apart from dpkg-reconfiguring mozilla-firefox before launching a new mozilla-firefox session, the only way to avoid dead links is to select the option always use the application (for instance always use /usr/bin/xpdf to open pdf files). I did not have this problem with 1.0.4-2sarge1 and previous versions. pdf is an example, I met similar problems with other types of files like tar.gz, tar.bz2. However I tested only a limited number of mime-types before downgrading to 1.0.4-2sarge1. Pascal -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.13-rc6.raisin.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages mozilla-firefox depends on: ii debianutils2.8.4 Miscellaneous utilities specific t ii fontconfig 2.3.1-2 generic font configuration library ii libatk1.0-01.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc11:3.4.3-13GCC support library ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libgtk2.0-02.6.4-3 The GTK+ graphical user interface ii libidl00.8.5-1 library for parsing CORBA IDL file ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libpng12-0 1.2.8rel-1PNG library - runtime ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxft22.1.7-1 FreeType-based font drawing librar ii libxp6 4.3.0.dfsg.1-14 X Window System printing extension ii libxt6 4.3.0.dfsg.1-14 X Toolkit Intrinsics ii psmisc 21.5-1Utilities that use the proc filesy ii xlibs 4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324362: mozilla-firefox: What-do-you-want-to-do-with-this-file dialog broken with 1.0.4-2sarge2
Package: mozilla-firefox Version: 1.0.4-2sarge2 Severity: normal -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.13-rc6.raisin.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages mozilla-firefox depends on: ii debianutils2.8.4 Miscellaneous utilities specific t ii fontconfig 2.3.1-2 generic font configuration library ii libatk1.0-01.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc11:3.4.3-13GCC support library ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libgtk2.0-02.6.4-3 The GTK+ graphical user interface ii libidl00.8.5-1 library for parsing CORBA IDL file ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libpng12-0 1.2.8rel-1PNG library - runtime ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxft22.1.7-1 FreeType-based font drawing librar ii libxp6 4.3.0.dfsg.1-14 X Window System printing extension ii libxt6 4.3.0.dfsg.1-14 X Toolkit Intrinsics ii psmisc 21.5-1Utilities that use the proc filesy ii xlibs 4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324362: Mozilla-firefox: What-do-you-want-to-do-with-this-file dialog broken with 1.0.4-2sarge2
I am sorry I messed up with reportbug and I stupidly sent twice the same message but nothing is reported in this one. Is it feasible to close this one or merge it with #324363? I feel very confused and very sorry. Pascal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]