Bug#746339: caja: Caja crashed, but spawn infinity, unable to launch others.
On Sun, 31 Jan 2016 19:33:21 +0900 "K.Ohta" wrote: > Package: caja > Version: 1.12.2-1 > > With above version, this bug seems to be fixed,not crash. > > Regards, > Ohta. > > > On Sun, 31 Jan 2016 12:41:06 +0300 > Vlad Orlov wrote: > > > > Now, with Caja 1.12.2 (sid), this issue(s) are not happened. > > > Seems to be working fine, excepts not exiting when close > > > from the window manager. > > > Sorry. > > > > Well... I guess you can close the bug then. > > > > Sorry. m(_ _)m > > Hi, Installing Mate Desktop today, Debian Jessie up-to-date. Bug is still present, Caja starts an infinite number of instances.
Bug#794102: KDE windows decoration still absent
Hi guys, Just installed testing/kde today. The bug is still present, I have no windows decoration. It's impossible to install kwin-x11 (which needs kwin-commons, which needs libkdecorations2-5, which needs libkdecorations2private5) without removing the whole kde desktop previously installed. So I can't get a usable KD desktop. Thanks in advance if you know what is going bad, and, if possible, when it's planned to be solved. Thanks for your work. Folco
Bug#797039: systemd: Jessie won't boot if a filesystem in /etc/fstab is missing
First, thanks for your quick answer ! >I suppose this was the wrong entry? "Data" is not a valid device name. It is in a Virtualbox context. Once booted, "mount -a" mounts this partition to /mnt/Data, without any poblem. But it fails at boot, so I need to comment it, then modify /etc/fstab, then 'mount -a'. >So mark it as "defaults,nofail" to tell that this isn't a critical partition. Thanks for the hint. I have tested that, and it works, the virtual machine is able to boot now. But when doing a "mount -a" right after the boot, I get that : root@blah:/home/folco# mount -a unknown mount option `nofail' valid options: [...] So I still have to modify ym fstab in order to use my partition. Why can't it be mounted while booting ?
Bug#797039: Additional informations
As you can see in my fstab, the last line is : #Data /mnt/Data vboxsf defaults 0 0 Data exist from time to time /mnt/Data always exists. I have to comment that line in order to boot my system. Else, instead of showing the mount error, and continue booting, the system shows an emergency prompt, and is unable to boot. I think that is a real problem that a sysetm is unable to boot just because a data partition is not accessible. The behaviour with sysvinit was smarter. Regards.
Bug#746339: caja: Caja crashed, but spawn infinity, unable to launch others.
>
> as seen in [1], the issue is related to non-ASCII file names
> (background image).
>
> Is that the case for your setup?
>
> Mike
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746339#22
> --
>
> DAS-NETZWERKTEAM
> mike gabriel, herweg 7, 24357 fleckeby
> fon: +49 (1520) 1976 148
>
> GnuPG Key ID 0x25771B31
> mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
>
> freeBusy:
>
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
Thank you Mike.
It doesn't seems that it is the case for me, but I got it !
I get the bug if the file .gtkrc-2.0 is present in $HOME
Removing this file fixes the problem.
(another file is present, .gtkrc-2.0-kde4, which link to the previous one.
I removed it too)
Here is the content of this file :
>>>BEGIN
# File created by KDE Gtk Config
# Configs for GTK2 programs
include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"
style "user-font"
{
font_name="DejaVu Sans Condensed"
}
widget_class "*" style "user-font"
gtk-font-name="DejaVu Sans Condensed 9"
gtk-theme-name="oxygen-gtk"
gtk-icon-theme-name="oxygen"
gtk-fallback-icon-theme="gnome"
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-menu-images=1
gtk-button-images=1
>>>END
I don't see any char which should be non-ascii.
Next question : where is the exact place to report that ? The GTK guys ?
KDE guys ? Debian guys ?
I'm not so familiar with bug reporting, sorry :(
Thanks again for your help Mike. :)
Bug#746339: caja: Caja crashed, but spawn infinity, unable to launch others.
I get the same problem, with the same error message as described here : https://github.com/mate-desktop/caja/issues/150 I have an up-to-date Debian Jessie x86_64. KDE, Fluxbox and Mate from the official repos. I tried various workaround found here and there, but none of them fixed the crash for me. Removing all .gnome* or .dconf from ~ didn't change anything. It's hard to diagnostic, because the entries in the Mate taskbar doesn't allow to show the window which they should be attached to. And when the constant tasks spontaneous generation stops, I can't run Caja anymore, even with tools like valgrind, because a "max" seems to be reached. So I don't know how to investigate this problem. I can do any test and try that you want to help you. Thanks in advance for your attention.
