Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #176786 > unrolled thread

LXDE lost menus

Started byHans <hans.ullrich@loop.de>
First post2017-01-17 17:50 +0100
Last post2017-01-24 11:10 +0100
Articles 6 — 3 participants

Back to article view | Back to linux.debian.user


Contents

  LXDE lost menus Hans <hans.ullrich@loop.de> - 2017-01-17 17:50 +0100
    Re: LXDE lost menus kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2017-01-23 06:00 +0100
      Re: LXDE lost menus Hans <hans.ullrich@loop.de> - 2017-01-23 10:50 +0100
        Re: LXDE lost menus Jonathan Dowland <jmtd@debian.org> - 2017-01-23 11:10 +0100
          Re: LXDE lost menus Hans <hans.ullrich@loop.de> - 2017-01-23 11:30 +0100
            Re: LXDE lost menus Jonathan Dowland <jmtd@debian.org> - 2017-01-24 11:10 +0100

#176786 — LXDE lost menus

FromHans <hans.ullrich@loop.de>
Date2017-01-17 17:50 +0100
SubjectLXDE lost menus
Message-ID<t0F7l-Zg-23@gated-at.bofh.it>
Hi all,

it looks like there is a bug in famous LXDE. After an update all menus are 
gone. There is already filed a bugreport to kali-linux, but I want to mention 
it for debian, too.

If LXDE users did not not notice it, then it is because of cached files. If you 
move ~/.cache/* away, then the menus are not rebuild again.

WARNING: For testing backup the cached files, so you can return them back, 
otherwise it will brick your LXDE.

Do the LXDE developers know of this? Shall we file another bugreport to the 
LXDE maintainers?

Best regards

Hans

[toc] | [next] | [standalone]


#176921

Fromkamaraju kusumanchi <raju.mailinglists@gmail.com>
Date2017-01-23 06:00 +0100
Message-ID<t2ETv-1RE-5@gated-at.bofh.it>
In reply to#176786
On Tue, Jan 17, 2017 at 11:48 AM, Hans <hans.ullrich@loop.de> wrote:
> Hi all,
>
> it looks like there is a bug in famous LXDE. After an update all menus are
> gone. There is already filed a bugreport to kali-linux, but I want to mention
> it for debian, too.

Update from which version to which version? What version of LXDE shows
this bug? Can you provide a link to the kali-linux bug report?

> Do the LXDE developers know of this? Shall we file another bugreport to the
> LXDE maintainers?

I do not see anything like this reported at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lxde;dist=unstable .
So it is possible that the maintainers are not aware of this.

As to whether the bug has to be reported in Debian, the answers is
that it depends. If the bug exists in the version that is carried by
Debian, then it makes sense to report it. Also, check if the upstream
(i.e authors of lxde) are aware of this and if it is fixed in future
versions.

hope that helps
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [next] | [standalone]


#176930

FromHans <hans.ullrich@loop.de>
Date2017-01-23 10:50 +0100
Message-ID<t2Jq9-4Km-15@gated-at.bofh.it>
In reply to#176921
Am Sonntag, 22. Januar 2017, 23:57:59 CET schrieb kamaraju kusumanchi:

> Update from which version to which version? What version of LXDE shows
> this bug? Can you provide a link to the kali-linux bug report?
See here:
https://bugs.kali.org/view.php?id=3822
> 
> > Do the LXDE developers know of this? Shall we file another bugreport to
> > the
> > LXDE maintainers?
>

Yes, they are.
> I do not see anything like this reported at
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lxde;dist=unstable .
> So it is possible that the maintainers are not aware of this.
> 

Search for a bugreport for libfm-extra4.

> As to whether the bug has to be reported in Debian, the answers is
> that it depends. If the bug exists in the version that is carried by
> Debian, then it makes sense to report it. Also, check if the upstream
> (i.e authors of lxde) are aware of this and if it is fixed in future
> versions.
> 

see above.
> hope that helps
> raju

Best

Hans

[toc] | [prev] | [next] | [standalone]


#176931

FromJonathan Dowland <jmtd@debian.org>
Date2017-01-23 11:10 +0100
Message-ID<t2JJw-56E-33@gated-at.bofh.it>
In reply to#176930

[Multipart message — attachments visible in raw view] — view raw

The first thing to establish is does this bug actually exist in Debian.
That doesn't mean knowing that it is present in an upstream version that
Debian carries, it means someone has to verify the bug in person with the
installed package.

On Mon, Jan 23, 2017 at 10:44:50AM +0100, Hans wrote:
> Search for a bugreport for libfm-extra4.

Do you mean to suggest that you know that this bug is confirmed to exist
in Debian and has already been reported?


-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.

[toc] | [prev] | [next] | [standalone]


#176932

FromHans <hans.ullrich@loop.de>
Date2017-01-23 11:30 +0100
Message-ID<t2K2R-5dc-17@gated-at.bofh.it>
In reply to#176931
> Do you mean to suggest that you know that this bug is confirmed to exist
> in Debian and has already been reported?

Yes, that is. See here:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851748

You can test it this way:

1. Move ~/.config/menus* somewhere
2. Start LXDE, no more menus.
3. Install libfm-extra4-1.2.3-1 and start LXDE again, menus are newly created.
4. Verify

The last working version is 1.2.4-1 from kali.


If it is correct, what Andriy told and there were no code changes, then I 
suggest, just to use the 1.2.4-1 version and create a package, with a version 
higher than 1.2.5-1. 

I am just building a live file system of kali linux (LXDE) by putting a self 
rebuild 1.2.5-2-version into live-build-config/config/packages-chroot/ and hope, 
this will be overwrite the one from the repo.

If it works (what I will see in a few hours), I will report.

Happy hacking

Hans 

[toc] | [prev] | [next] | [standalone]


#176967

FromJonathan Dowland <jmtd@debian.org>
Date2017-01-24 11:10 +0100
Message-ID<t36d5-2Xs-33@gated-at.bofh.it>
In reply to#176932

[Multipart message — attachments visible in raw view] — view raw

On Mon, Jan 23, 2017 at 11:21:35AM +0100, Hans wrote:
> > Do you mean to suggest that you know that this bug is confirmed to exist
> > in Debian and has already been reported?
> 
> Yes, that is. See here:
> 
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851748

Great! (that it's reported, that is. It's a shame the bug exists).

And coincidentally I have just learned about the existence of "menu-cache-gen",
which probably explains the unrelated LXDE bug I hit/reported yesterday:

	lxpanel: stale menu entries when desktop files modified
	https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852316


-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web