[Pkg-xfce-devel] Bug#480380: Bug#480380: xfce4: No easy way to add launchers from the menu to the panel

2008-05-13 Thread Yves-Alexis Perez
On ven, 2008-05-09 at 12:18 -0400, Daniel Dickinson wrote: To add a launcher you have to know the commandline command to launch the program. For a newbie this would be difficult, therefore having the ability to pick from a list, or right-click on a menu entry, in order to add a menu launcher

[Pkg-xfce-devel] Bug#480547: Bug#480547: xfce4-mount-plugin: Mount pluging requires device exist in fstab by device name

2008-05-13 Thread Yves-Alexis Perez
On sam, 2008-05-10 at 15:48 -0400, Daniel Dickinson wrote: If a mount does not exist in the fstab (such as a user mounted CIFS filesystem), or the mount is mounted by UUID not device name, the mount does not appear in the lists of mounts for the plugin/applet. I don't seem to be able to

[Pkg-xfce-devel] Processed: Re: Bug#480402: xfkc: segmentation faults

2008-05-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 480402 normal Bug#480402: xfkc: segmentation faults Severity set to `normal' from `grave' tag 480402 +unreproducible Bug#480402: xfkc: segmentation faults There were no tags set. Tags added: unreproducible thanks Stopping processing here.

[Pkg-xfce-devel] Bug#480402: Bug#480402: xfkc: segmentation faults

2008-05-13 Thread Yves-Alexis Perez
severity 480402 normal tag 480402 +unreproducible thanks On ven, 2008-05-09 at 20:37 +0200, Nyizsnyik Ferenc wrote: strace output can be found here: http://users.hszk.bme.hu/~nf696/docs/strace.xfkc.txt There's nothing useful here. Could you provide a backtrace with debugging symbols? Btw,

[Pkg-xfce-devel] Bug#480402: marked as done (xfkc: segmentation faults)

2008-05-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 May 2008 08:10:07 +0200 with message-id [EMAIL PROTECTED] and subject line Re: [Pkg-xfce-devel] Bug#480402: xfkc: segmentation fault has caused the Debian Bug report #480402, regarding xfkc: segmentation faults to be marked as done. This means that you claim that the

[Pkg-xfce-devel] Bug#480587: Bug#480587: xfwm4: Using Compositing causes X to eat major CPU

2008-05-13 Thread Yves-Alexis Perez
On sam, 2008-05-10 at 23:29 -0400, Daniel Dickinson wrote: With an accelerated video card with composting enabled in xorg.conf and for compositing works under GNOME, using compositing in Window Manager Tweaks results in X consuming huge amounts of CPU bringing the system to a crawl. So you're

[Pkg-xfce-devel] Bug#419354: Bug#419354: xfwm4: moving or resizing a window blocks other windows

2008-05-13 Thread Yves-Alexis Perez
On dim, 2007-04-15 at 10:08 +0200, Géraud Meyer wrote: With the xfwm4 options of not drawing the content of windows that are being moved or resized activated, moving or resizing a window seems to stop the other windows. This issue is now marked “Invalid” in Xfce bugzilla. You can see more info

[Pkg-xfce-devel] Bug#480380: Bug#480380: xfce4: No easy way to add launchers from the menu to the panel

2008-05-13 Thread Xr
Yves-Alexis Perez wrote: On ven, 2008-05-09 at 12:18 -0400, Daniel Dickinson wrote: To add a launcher you have to know the commandline command to launch the program. For a newbie this would be difficult, therefore having the ability to pick from a list, or right-click on a menu entry, in

[Pkg-xfce-devel] Bug#481086: xfce4-panel: plugins ignore multiscreen environment

2008-05-13 Thread David Mohr
Package: xfce4-panel Version: 4.4.2-4.2 Severity: normal Tags: patch Some plugins ignore the screen they are on in a multiscreen (i.e. :0.0 and :0.1) display, and always launch on the primary screen. Attached is a patch that fixes that problem. It is already in svn, see r26937 in the 4_4

[Pkg-xfce-devel] Bug#481085: xfce4-quicklauncher-plugin: ignores screen when run in multihead setup with several X screens

2008-05-13 Thread David Mohr
Package: xfce4-quicklauncher-plugin Version: 1.9.4-1.1 Severity: normal Tags: patch The configuration, the about window and launched programs don't respect the screen of the plugin and always launch on the primary screen (i.e. :0.0 when they should run on :0.1 in an old style multihead setup).