Bug#791491: lives: Crashes on startup
On 2015-07-11 10:24, Sebastian Ramacher wrote: On 2015-07-05 10:29:47, David Mohr wrote: LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser, line 4 ** Gtk:ERROR:/build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c:609:tick_cb: assertion failed: (priv-pulse2 priv-pulse1) I'm unable to reproduce the issue. Are you using a special theme or something that could mess with GTK+? I selected NOX in xfce4-settings-manager. AFAIK that's gtk2 though, gtk3 applications have this ugly white/grayish theme. I don't know of a better way to check. lives 2.4.0~ds0-1 should hit the archive any minute. Is this issue reproducible with the new upstream version? I don't see it yet, will report on it later. When reporting crashes, please include details of your operating system, distribution, and the LiVES version (2.2.8) and any information shown below: #0 0x7fb3543974c9 in __libc_waitpid (pid=873, stat_loc=stat_loc@entry=0x7ffefeee664c, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 #1 0x7fb357057433 in g_on_error_stack_trace (prg_name=0x1104700 /usr/lib/lives/lives-exe) at /tmp/buildd/glib2.0-2.44.1/./glib/gbacktrace.c:252 #2 0x0041ecd8 in () #3 0x7fb3543978d0 in signal handler called () #4 0x7fb35400d107 in __GI_raise (sig=sig@entry=6) #5 0x7fb35400e4e8 in __GI_abort () at abort.c:89 #6 0x7fb3570a7b55 in g_assertion_message (domain=domain@entry=0x7fb358d4b527 Gtk, file=file@entry=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x7fb358d9b4b7 tick_cb, message=message@entry=0x2a47ec0 assertion failed: (priv-pulse2 priv-pulse1)) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2356 #7 0x7fb3570a7bea in g_assertion_message_expr (domain=0x7fb358d4b527 Gtk, file=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=609, func=0x7fb358d9b4b7 tick_cb, expr=optimized out) #8 0x7fb358c1ae6e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #9 0x7fb358d0cf44 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #10 0x7fb357358504 in _g_closure_invoke_va (closure=0x145aec0, return_value=0x0, instance=0x11052c0, args=0x7ffefeee70c8, n_params=optimized out, param_types=0x0) at /tmp/buildd/glib2.0-2.44.1/./gobject/gclosure.c:831 #11 0x7fb357371fa7 in g_signal_emit_valist (instance=instance@entry=0x11052c0, signal_id=signal_id@entry=139, detail=detail@entry=0, var_args=var_args@entry=0x7ffefeee70c8) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3214 #12 0x7fb357372e4a in g_signal_emit_by_name (instance=0x11052c0, detailed_signal=0x7fb358792414 update) #13 0x7fb35872c3bc in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #14 0x7fb35871bcf8 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #15 0x7fb3570825e3 in g_timeout_dispatch (source=0x154f690, callback=optimized out, user_data=optimized out) #16 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #17 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #18 0x7fb357081f20 in g_main_context_iterate (context=context@entry=0x10bd3f0, block=block@entry=0, dispatch=dispatch@entry=1, self=optimized out) #19 0x7fb357081fcc in g_main_context_iteration (context=0x10bd3f0, may_block=0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #20 0x0041d531 in () #21 0x004b6b34 in () #22 0x00423b74 in () #23 0x00424b3f in () #24 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #25 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #26 0x7fb357081f20 in g_main_context_iterate (context=0x10bd3f0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) #27 0x7fb357082242 in g_main_loop_run (loop=0x11046a0) #28 0x7fb358bc6a85 in gtk_main () #29 0x00417421 in main () Please install lives-dbg and libgtk-3-0-dbg so that we know what the missing bits are. Ah yes, should've done that right away. Funny thing is that with the two -dbg packages installed, I don't get a backtrace anymore! (2120)-alucardo:~/tmp/lives% lives -debug LiVES 2.2.8 Copyright 2002-2015 Gabriel Finch (salsa...@gmail.com) and others. LiVES comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details. LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser
Bug#791491: lives: Crashes on startup
Running it directly in gdb allows me to get a backtrace: Reading symbols from /usr/lib/lives/lives-exe...Reading symbols from /usr/lib/debug/.build-id/4b/89b56dd51625e18b580231f82597f040d7c029.debug...done. done. (gdb) run Starting program: /usr/lib/lives/lives-exe [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe71d4700 (LWP 29544)] LiVES 2.2.8 Copyright 2002-2015 Gabriel Finch (salsa...@gmail.com) and others. LiVES comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details. LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser, line 4 ** Gtk:ERROR:/build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c:609:tick_cb: assertion failed: (priv-pulse2 priv-pulse1) Program received signal SIGABRT, Aborted. 0x72b9a107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) thread apply all bt Thread 2 (Thread 0x7fffe71d4700 (LWP 29544)): #0 0x72c4253d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x75bc9ebc in g_main_context_iterate (priority=2147483647, n_fds=2, fds=0x7fffe00010c0, timeout=-1, context=0x10597e0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:4103 #2 0x75bc9ebc in g_main_context_iterate (context=0x10597e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3803 #3 0x75bca242 in g_main_loop_run (loop=0x1059770) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:4002 #4 0x761c0af6 in gdbus_shared_thread_func (user_data=0x10597b0) at /tmp/buildd/glib2.0-2.44.1/./gio/gdbusprivate.c:274 #5 0x75bf0955 in g_thread_proxy (data=0x1046ca0) at /tmp/buildd/glib2.0-2.44.1/./glib/gthread.c:764 #6 0x72f160a4 in start_thread (arg=0x7fffe71d4700) at pthread_create.c:309 #7 0x72c4b07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x77f18a80 (LWP 29522)): #0 0x72b9a107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x72b9b4e8 in __GI_abort () at abort.c:89 #2 0x75befb55 in g_assertion_message (domain=domain@entry=0x778777a7 Gtk, file=file@entry=0x778c7570 /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x778c __FUNCTION__.52871 tick_cb, message=message@entry=0x29da860 assertion failed: (priv-pulse2 priv-pulse1)) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2356 #3 0x75befbea in g_assertion_message_expr (domain=domain@entry=0x778777a7 Gtk, file=file@entry=0x778c7570 /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x778c __FUNCTION__.52871 tick_cb, expr=expr@entry=0x778a027d priv-pulse2 priv-pulse1) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2371 #4 0x7774706e in tick_cb (widget=0x123e1c0 [GtkProgressBar], frame_clock=optimized out, user_data=optimized out) at /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c:609 #5 0x778391b4 in gtk_widget_on_frame_clock_update (frame_clock=0x10992c0 [GdkFrameClockIdle], widget=0x123e1c0 [GtkProgressBar]) at /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkwidget.c:5299 #6 0x75e9f504 in _g_closure_invoke_va (closure=0x13e9660, return_value=0x0, instance=0x10992c0, args=0x7fffc618, n_params=optimized out, param_types=0x0) at /tmp/buildd/glib2.0-2.44.1/./gobject/gclosure.c:831 #7 0x75eb8fa7 in g_signal_emit_valist (instance=instance@entry=0x10992c0, signal_id=signal_id@entry=139, detail=detail@entry=0, var_args=var_args@entry=0x7fffc618) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3214 #8 0x75eb9e4a in g_signal_emit_by_name (instance=instance@entry=0x10992c0, detailed_signal=detailed_signal@entry=0x772bc654 update) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3401 #9 0x7725644c in gdk_frame_clock_paint_idle (data=0x10992c0) at /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gdk/gdkframeclockidle.c:380 zsh: segmentation fault gdb /usr/lib/lives/lives-exe It crashed when the startup window said Loading realtime effect plugins... Not sure why the bt kills gdb... (but fyi, no other odd crashes on my system). ~David -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
On 2015-07-10 10:46, Michael Biebl wrote: Am 10.07.2015 um 18:38 schrieb Josh Triplett: On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: * Systemd has been fixed in v222 to no longer kill services on reload if BusName is set, so drop that part from 92_systemd_unit.patch. but that is EXACTLY what happened to me right now, in the middle of Right. Subsequent reloads of gdm3.service should no longer kill gdm3.service though. So this was indeed fixed in v222 but there seems to be a specific issue for the upgrade path. Once gdm3 has been restarted, a reload no longer causes it to be killed. Note, though, that it doesn't help for systemd to be upgraded first. Even if running the new systemd 222, upgrading gdm3 kills the active session. Well, that's exactly what I said, right? apt used this order on my system: 2015-07-09 12:05:33 status installed systemd:amd64 222-1 [...] 2015-07-09 12:05:46 status installed gdm3:amd64 3.14.2-1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791491: lives: Crashes on startup
Package: lives Version: 2.2.8~ds0-1 Severity: grave Justification: renders package unusable Dear Maintainer, just wanted to give lives a shot, but it crashes immediately after the startup dialog made some progress: % lives -debug LiVES 2.2.8 Copyright 2002-2015 Gabriel Finch (salsa...@gmail.com) and others. LiVES comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details. LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser, line 4 ** Gtk:ERROR:/build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c:609:tick_cb: assertion failed: (priv-pulse2 priv-pulse1) Unfortunately LiVES crashed. Please report this bug at http://sourceforge.net/tracker/?group_id=64341atid=507139 Thanks. Recovery should be possible if you restart LiVES. When reporting crashes, please include details of your operating system, distribution, and the LiVES version (2.2.8) and any information shown below: #0 0x7fb3543974c9 in __libc_waitpid (pid=873, stat_loc=stat_loc@entry=0x7ffefeee664c, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 #1 0x7fb357057433 in g_on_error_stack_trace (prg_name=0x1104700 /usr/lib/lives/lives-exe) at /tmp/buildd/glib2.0-2.44.1/./glib/gbacktrace.c:252 #2 0x0041ecd8 in () #3 0x7fb3543978d0 in signal handler called () #4 0x7fb35400d107 in __GI_raise (sig=sig@entry=6) #5 0x7fb35400e4e8 in __GI_abort () at abort.c:89 #6 0x7fb3570a7b55 in g_assertion_message (domain=domain@entry=0x7fb358d4b527 Gtk, file=file@entry=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x7fb358d9b4b7 tick_cb, message=message@entry=0x2a47ec0 assertion failed: (priv-pulse2 priv-pulse1)) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2356 #7 0x7fb3570a7bea in g_assertion_message_expr (domain=0x7fb358d4b527 Gtk, file=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=609, func=0x7fb358d9b4b7 tick_cb, expr=optimized out) #8 0x7fb358c1ae6e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #9 0x7fb358d0cf44 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #10 0x7fb357358504 in _g_closure_invoke_va (closure=0x145aec0, return_value=0x0, instance=0x11052c0, args=0x7ffefeee70c8, n_params=optimized out, param_types=0x0) at /tmp/buildd/glib2.0-2.44.1/./gobject/gclosure.c:831 #11 0x7fb357371fa7 in g_signal_emit_valist (instance=instance@entry=0x11052c0, signal_id=signal_id@entry=139, detail=detail@entry=0, var_args=var_args@entry=0x7ffefeee70c8) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3214 #12 0x7fb357372e4a in g_signal_emit_by_name (instance=0x11052c0, detailed_signal=0x7fb358792414 update) #13 0x7fb35872c3bc in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #14 0x7fb35871bcf8 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #15 0x7fb3570825e3 in g_timeout_dispatch (source=0x154f690, callback=optimized out, user_data=optimized out) #16 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #17 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #18 0x7fb357081f20 in g_main_context_iterate (context=context@entry=0x10bd3f0, block=block@entry=0, dispatch=dispatch@entry=1, self=optimized out) #19 0x7fb357081fcc in g_main_context_iteration (context=0x10bd3f0, may_block=0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #20 0x0041d531 in () #21 0x004b6b34 in () #22 0x00423b74 in () #23 0x00424b3f in () #24 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #25 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #26 0x7fb357081f20 in g_main_context_iterate (context=0x10bd3f0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) #27 0x7fb357082242 in g_main_loop_run (loop=0x11046a0) #28 0x7fb358bc6a85 in gtk_main () #29 0x00417421 in main () -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lives depends on: ii frei0r-plugins1:1.4-dmo4 ii imagemagick 8:6.8.9.9-5 ii libasound21.0.28-1 ii libatk1.0-0
Bug#788904: systemd fails to activate vg on crypt device after upgrade to 215-17+deb8u1
close 788904 thanks On 2015-06-16 00:19, Michael Biebl wrote: Am 16.06.2015 um 08:12 schrieb Michael Biebl: Am 16.06.2015 um 06:35 schrieb David Mohr: I have a crypto device which I use as a physical volume for LVM. After upgrading to systemd 215-17+deb8u1 my system fails to boot, because `vgchange -ay` is not run after the crypto device is set up (which [..] Please let me know if I can help to fix this, since I think that's a pretty bad regression. I assume you had 215-17 installed before the upgrade. Can you downgrade to that version again? The changes in 215-17+deb8u1 do not look like they could be related to your problem, but let's verify if the downgrade actually helps. downgrade both systemd and udev to be sure. Hm, I'm guessing it was a race condition... I tried several times and I couldn't reproduce the issue. ~David -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748253: aspell-de fails to install because /var/lib/aspell doesn't exist
Package: aspell-de Version: 20131206-3 Severity: grave Justification: renders package unusable Dear Maintainer, I'm upgrading aspell-de from 20131206-2 to 20131206-3 and get the following error message: % sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 52 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up aspell-de (20131206-3) ... /var/lib/dpkg/info/aspell-de.postinst: 58: /var/lib/dpkg/info/aspell-de.postinst: cannot create /var/lib/aspell/de.compat: Directory nonexistent dpkg: error processing package aspell-de (--configure): subprocess installed post-installation script returned error exit status 2 Processing triggers for dictionaries-common (1.23.2) ... Errors were encountered while processing: aspell-de E: Sub-process /usr/bin/dpkg returned an error code (1) ~David -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aspell-de depends on: ii aspell 0.60.7~20110707-1 ii dictionaries-common 1.23.2 aspell-de recommends no packages. aspell-de suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748253: aspell-de fails to install because /var/lib/aspell doesn't exist
Hi Roland, On 2014-05-15 10:24, Roland Rosenfeld wrote: On Thu, 15 May 2014, David Mohr wrote: Package: aspell-de Version: 20131206-3 Severity: grave Justification: renders package unusable I'm upgrading aspell-de from 20131206-2 to 20131206-3 and get the following error message: /var/lib/dpkg/info/aspell-de.postinst: 58: /var/lib/dpkg/info/aspell-de.postinst: cannot create /var/lib/aspell/de.compat: Directory nonexistent You're right, there is a problem when you have no other aspell dictionary package installed and upgrade from older aspell-de versions to 20131206-3. I'll try to fix this soon (seems to be necessary to create /var/lib/aspell in postinst and not only preinst, since it would otherwise be removed when the old aspell-de package is removed). As a quick work around just install aspell-de again, this should work without a problem (at least on my system). Installing aspell-en also fixed it; I guess because I didn't have it installed before. Danke, ~David -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555849: Workaround
As a workaround you can delete ~/.config/deluge/ipc/deluge-gtk.lock, after which deluge should start again. ~David -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517020: [Pkg-xfce-devel] Bug#517020: Bug#517020: thunar: potential exploits via application launchers
On Wed, Feb 25, 2009 at 12:08 AM, Michael Gilbert michael.s.gilb...@gmail.com wrote: On Wed, 25 Feb 2009 07:44:33 +0100 Yves-Alexis Perez wrote: Can you point me to your patch to the specs? And your patch to the code? i understand that there's going to be a lot of work involved, and its easy for me to submit the problem, and hard for you to fix it. i truely do appreciate that. and i also understand that you're a volunteer, so technically, you don't really have to do anything if you don't want to. i'm just trying to help get the ball rolling. are [1],[2] the spec you are refering to? [1] http://portland.freedesktop.org/xdg-utils-1.0/xdg-desktop-icon.html [2] http://portland.freedesktop.org/xdg-utils-1.0/xdg-desktop-menu.html Correct me if I'm wrong, but I think the point is that these specs do NOT mention the supposed fix that was getting talked about in the references on the bug report. A consensus is formed once the specs are updated - then the fix should be implemented. Notably there is no need to rush here because Thunar already behaves extremely well - and does NOT manage the desktop. So the issue is completely different than with KDE and GNOME. ~David -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509030: [Pkg-xfce-devel] Bug#509030: xfce4-terminal: Window decoration are not drawn even when enabled
On Wed, Dec 17, 2008 at 10:52 AM, john.lindg...@tds.net wrote: Package: xfce4-terminal Version: 0.2.8-5 Severity: grave I am attaching a screenshot that shows the problem better than any description. In the screenshot, compositing is enabled to show the outline of the window, but the problem happens just the same with or without compositing. It'd be good to know what theme you are using, and also if the same error occurs with other themes. ~David -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
