Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package foxeye
* Package name: foxeye
Version : 0.10.1-1
Upstream Author : Andriy Grytsenko
* URL : http://sourceforge.net/p/foxeye
* License : GPL-2
Package: qa.debian.org
The watch on qa.debian.org suddently stopped to update results. If you
look at https://qa.debian.org/cgi-bin/watch?pkg=menu-cache then you will
see it shows version 0.7.0 while actual one is 1.0.0~rc1 and on DDPO page
it is even worse: minus sigh is shown instead of watch
).
[ Josselin Mouette ]
* Update repository URL.
[ jbicha-guest ]
* use canonical Vcs-* fields
[ Colin Watson ]
* use dh_installdeb maintscript support (Closes: #659885).
[ Vlad Orlov ]
* 05_fix_selfconfig.patch: fixes current user's info retrieval. Closes:
#761806.
[ Andriy Grytsenko
.
Adjust gst_users_tool_finalize to fix some warnings/error messages
(Closes: #729477).
[ Andriy Grytsenko ]
* debian/control:
- Lower the relations with gnome-control-center to Suggests (Closes:
#753701).
- Bump Standards-Version to 3.9.6 (Fixes lintian warning).
- Remove invalid
-return-error-code.patch: new patch. Correctly return error code on
unknown dbus errors.
* 02-proper-warning.patch: new patch. Emit the unknown error warning only
when dbus error is really unknown (Closes: #761964).
[ Andriy Grytsenko ]
* debian/control:
- Bump Standards-Version
Yes, it is unavailable now to reflect the fact it requires XSettings daemon
to work. Yes, you can set gtk-color-scheme property in ~/.gtkrc-2.0 file
but unfortunately it will never affect colors of theme unless a XSettings
daemon is running (and then lxsession provides such service), that happens
Yuri D'Elia has written on Monday, 20 October, at 18:25:
Yes, but then lxappearance still shouldn't check explicitly for
lxsession, but only for a valid _XSETTINGS_S* atom.
There are several alternative XSETTINGS daemons: xsettings-kde and
xsettingsd come to my mind, but probably
.
Regards,
Andriy Grytsenko
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
-signature.
Regards,
Andriy Grytsenko
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
:
dget -x http://mentors.debian.net/debian/pool/main/l/lxtask/lxtask_0.1.6-1.dsc
Changes since the last upload:
* Merging upstream version 0.1.6.
* Bump Standards-Version to 3.9.6.
* Adding lintian-overrides file for debian-watch-may-check-gpg-signature.
Regards,
Andriy Grytsenko
Yuri D'Elia has written on Monday, 20 October, at 19:34:
I won't definitely have time to provide a patch for this, sorry.
You have nothing to be sorry for. Don't worry, upstream eventually add
support for other XSETTINGS daemons, just not right away. Thank you very
much for the notice. We will
Help us to debug it, please. To do that first thing required is to get
the coredump file - add a line into your ~/.profile file, please:
ulimit -c 20
After crash you can find file 'core' in your home directory and you can
explore it using program 'gdb'. Install packages 'gdb' and
Package: ftp.debian.org
Severity: normal
Please, change override of lxtask to optional (set in .deb) which I
believe is a correct one since it doesn't conflict with other packages
and is useful in common (so isn't specialized one).
Thank you.
--
To UNSUBSCRIBE, email to
Package: ftp.debian.org
Severity: normal
Please, change override of lxlauncher to optional (set in .deb) which I
believe is a correct one since it doesn't conflict with other packages
and is useful in common (so isn't specialized one).
Thank you.
--
To UNSUBSCRIBE, email to
Package: ftp.debian.org
Severity: normal
Please, change override of lxterminal to optional (set in .deb) which I
believe is a correct one since it doesn't conflict with other packages,
is dependency of another optional packages, and also is useful in common
(so isn't a specialized one).
Thank
Package: ftp.debian.org
Severity: normal
Please, change override of lxrandr to optional (set in .deb) which I
believe is a correct one since it doesn't conflict with other packages,
is a dependency of another optional package, and also is useful in common
(so isn't specialized one).
Thank you.
Thank you for noticing. It was partially fixed in uploaded version 0.5.1,
more pages coming later.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
control: reassign -1 lxde-common
I believe this is just an artefact from older setups. This will be fixed
in the lxde-common version 0.99.0 which is pending upload, the configs
for pcmanfm should be never copied because pcmanfm is good enough to find
configs from right places these days. Thank
control: reassing -1 openbox
I'm sorry but LXDE does nothing with windows positioning because it does
not have any own window manager. Since default window manager used is the
Openbox, I reassign this report to it, and I think somehow the issue was
fixed since 2008 a.d.
Thanks.
--
To
control: tags -1 + wontfix
control: close -1
Unfortunately moving galculator from depends will not fix your problem
because libthai0 is a dependency not from galculator but from libpango
which is a dependency for each application these times. Only way to go
without libthai0 is installing some old
As a note why I close this request just partially satistying it. The
package lxshortcut is in fact not required anymore, yes, and it is
virtual. But for lxsession-edit and lxpolkit that is not completely
true because those applications can be used standalone and therefore
those applications will
control: reassign -1 lxde-common
control: fixed -1 lxde-common/0.99.0-1
control: close -1
This issue was due to mistakes in both lxpanel and lxde-common, and we
believe those problems are now fixed in the latest versions of those
packages, which are available in Debian unstable now.
Thank you
Package: debian-maintainers
Severity: normal
Please add Andriy Grytsenko to the Debian Maintainers keyring. I'm
attaching the jetring changeset.
With best regards,
Andriy.Comment: Add Andriy Grytsenko and...@rep.kiev.ua as a Debian Maintainer
Date: Tue, 28 Oct 2014 12:36:06 +0200
Recommended
Thank you very much, everyone, for all that detailed comments.
I remove that Alias statement and hope that fixes the problem.
Reopen the ticket if something is still wrong, please.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
25 is not much a difference from current limitation which is 20.
When you tell about 10 - 10 is default, which can be changed in the
configuration dialog, but you cannot increase it over 20, only way to
increase is manually editing ini file but in that case you will be
forever prohibited to open
control: severity -1 important
After discussion with some people in #lxde channel I found out this may
be OK for new users but it affects usability on system upgrade because
users may get two icons in tray area due to both network-manager-gnome
and wicd installed in some cases, and even may have
alternative to wicd (Closes: #768390).
+
+ -- Andriy Grytsenko and...@rep.kiev.ua Wed, 12 Nov 2014 22:45:06 +0200
+
lxde-metapackages (5) unstable; urgency=low
[ Jackson Doak ]
diff -Nru lxde-metapackages-5/debian/control lxde-metapackages-6/debian/control
--- lxde-metapackages-5/debian/control
requires it.
+ * Cleaning lxsession_lxsession_vala.stamp, patching requires it.
+
+ -- Andriy Grytsenko and...@rep.kiev.ua Sat, 29 Nov 2014 14:55:02 +0200
+
lxsession (0.5.1-1) unstable; urgency=medium
[ Andriy Grytsenko ]
diff -Nru lxsession-0.5.1/debian/clean lxsession-0.5.1/debian/clean
control: tags -1 moreinfo
As for now, there is no PIUPARTS problems with any of LXDE related
packages. I suppose this bug may be closed, right?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
control: tags -1 fixed-upstream
This issue is fixed in latest upstream version which is about to appear
in the Debian experimental repository. You can try it from there. That
version will not appear in the Debian Jessie because Jessie is already
frozen so only release-critical changes
control: tags -1 fixed-upstream
This issue is fixed in latest upstream version which is about to appear
in the Debian experimental repository. You can try it from there. That
version will not appear in the Debian Jessie because Jessie is already
frozen so only release-critical changes are allowed
Thank you for the patch, I hope it works and fixes the problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
control: reassign -1 libfm4 1.2.3-1
control: tags -1 + moreinfo unreproducible
Thank you for reporting the issue. I'm sorry but I cannot reproduce your
issue, neither between different file systems, nor within the same file
system. Only way source file may be kept is the case if an error happened
Thank you very much for reporting this issue. To be honest, I'm not fan of
GTK3 themes myself. Although they are here so we have to live with them.
Since LXDE upstream developers team is open for any suggestions then give
your suggestions for theming of that pane and it hopefully will be added
in
control: severity -1 wishlist
lxpanel: missing-pkgconfig-dependency lxpanel = libfm
Thank you very much for reporting this. The pkgconfig file in this
package may be used only by plugins developers and therefore does not
affect usefulness of the package. Altough this issue may affect the
Hello!
Piotr Martycz has written on Sunday, 17 May, at 15:55:
This is a debian packaging problem unrelated to upstream.
Our unit file [1] assumes lxdm is going to acquire a
org.freedesktop.DisplayManager name on a dbus which is not the case,
apparently, therefore service is restarted after
control: forwarded -1 https://sourceforge.net/p/lxde/bugs/743/
Thank you very much for reporting this. The upstream author will be
notified about the problem and hopefully it will be fixed soon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
control: tag -1 + fixed moreinfo
Well, this very much likely is fixed now, we just need a feedback reply.
Thank you.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Pedro Ribeiro has written on Saturday, 20 June, at 17:04:
I don't know if the lib was updated, or if something in my system
changed, but now it appears to be working correctly.
I can confirm I'm not crazy though, I'm pretty sure that for months it
didn't work.
Well, last fixes on that matter
Package: libobrender29
Version: 3.6.0-1
Severity: grave
This is actually an upstream bug but it is a problem because it makes any
of packages dependent on libobrender29 broken completely, any application
compiled using libobrender29 version 3.5.x will crash using libobrender29
version 3.6.0-1.
Package: lxappearance-obconf
Version: 0.2.2-2
Severity: grave
The latest package in sid is built against openbox library libobrender29
version 3.6.0-1 with broken ABI (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788520)
and therefore version 0.2.2-2 of lxappearance-obconf should never
This issue may be related to similar one reported to upstream:
http://sourceforge.net/p/pcmanfm/bugs/917/
and the FUSE may be a culprit. Unfortunately it's still not reproducible for me.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Package: src:openbox
Version: 3.6.0-2
Severity: minor
The upstream released version 3.6.1 of Openbox recently which fixes ABI
incompatibility of version 3.6.0 so bumbed ABI number of libobrender to
32. Thus fix for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788520
made by patch in 3.6.0-2
control: severity -1 important
control: tags -1 moreinfo
Thank you very much for reporting this. I would like to know your panel
configuration to try reproducing it, the configuration files you can find
in the directory ~/.config/lxpanel. How often that problem happens?
--
To UNSUBSCRIBE,
Package: debian-maintainers
Severity: normal
Annual ping it is.
Thanks!
signature.asc
Description: Digital signature
control: tags -1 + patch pending upstream
Thank you very much for this fast patch! It will be included into next
release of the package which I hope may happen soon.
control: reassign -1 lxde-metapackages 6
Thank you very much for making such suggestion, the lxde actually can be
ran without openbox, yes.
Unfortunately, this exact suggestion is wrong as lxde-common is not a
WM-independent package, it actually isn't a common package needed to run
with any WM
control: severity -1 important
This bug, while afecting usability of the system, still does not make it
completely unusable, therefore, according to the BTS policy, should have
another severity, see https://www.debian.org/Bugs/Developer#severities as
a reference.
And since there was no solution
control: tags -1 unreproducible
Thank you for your report. Unfortunately, I cannot reproduce your issue
on my Debian Jessie machine. Was your file really deleted before you
copied a new one in place of it? Were there any warnings about the file
already exists? Frankly, I see no way how destroyed
control: tags -1 + moreinfo
Thank you very much for reporting this. I would like if you could provide
a bit more of useful info, such as a backtrace on the crash. You can read
more at https://wiki.debian.org/HowToGetABacktrace and relevant -dbg
packages for PCManFM are pcmanfm-dbg, libfm-dbg,
Thank you for reporting this. If this problem still exists then quote
output of 'xrandr' command here, please, for further investigation.
control: tags -1 + moreinfo
Thank you for your report. Although I don't see what exactly did you
mean? What exactly goes wrong?
Control: tags -1 + moreinfo
Thank you for reporting this. Could you provide more information, please?
Which parts of LXDE are not translated and what language you expected to
have in use?
Thank you very much for the backtrace provided, I'll start from it and
let you know when fix is available.
>I just see that pcmanfm is now in version 1.2.4-1.
>I have upgrated it.
Well, while 1.2.4 upstream version has many bugs fixed, I'm afraid this
particular one wasn't touched in that update so still would need some fix
and your backtrace input would be very appreciated.
Well, you might be right
I completely agree with blaming upstream to be ignorant so renaming the
package would be wise when working with such upstream.
I also think this bug severity is 'important', not 'normal' since it
affects usability of package, at least it confuses users. If I was the
maintainer of this package
Well, while your point is right, removal of system-tools-backends will
broke LXDE usability because there is no other alternative package to
manage users - other known users management tools are integrated into
GNOME and KDE, and gnome-system-tools is only standalone package which
can be used in
Oh, great! Thank you very much for the backtrace and steps provided.
I hope to get it fixed soon!
This is pretty much bad news, since libfm-extra4 was not changed at all
since version 1.2.0, so apparently something went bad in menu-cache-gen.
Only noticeable change was debug build was disabled, that makes it faster
but at cost - instead of tests and soft-failure a crash will appear. The
most
Thank you very much for information provided. I sincerely hope the issue
is now fixed, the version 0.9.3-1 is now in unstable. I would be glad and
grateful if you install the package and check if it's fixed (it can be
installed on either stable, testing, or unstable). I would like to ask
you to
control: tags -1 + jessie moreinfo
Have you tried to install version 0.9.3-1 from Stretch? I've not managed
to reproduce your issue yet but I suspect it is fixed in newer versions,
and it might be some configuration issue from MATE desktop as well.
Actually I've tried version 1.2.3 (downgraded both libfm and pcmanfm) and
behavior is the same. It seems something else is wrong, will test further
this issue.
Thank you for reporting this. It made me to wonder what may cause this.
No idea so far. Will try to reach some free computer to investigate but
currently don't have any estimate on that. I also would think about some
systemd integration. If you can get a log which would shed any light on
the issue
Thank you very much for a fix, will add it on next upload!
Package: wnpp
Severity: wishlist
* Package name: lxhotkey
* License: GPL
* URL: https://git.lxde.org/gitweb/?p=lxde/lxhotkey.git
* Programming Lang: C
I intend to add lxhotkey source package into Debian.
For now it contains only CLI but later it will contain (either or both)
GTK+ and Qt GUI.
>I just went to fix a reproducibility issue in foxeye, but I got stuck when
>I couldn't regenerate configure from configure.ac as the autoreconfing
>fails.
That is pretty much strange since I've added --with autoreconf to the dh
options in debian/rules and ran pbuilder against sid, then
Package: openbox
Version: 3.5.2-8
Version: 3.6.1-2
Severity: important
The openbox package in Debian does not support startup notifications and
such behavior creates big problems, especially on slow machines, tablets
and devices like Raspberry Pi, because users cannot see if application
they
Thank you very much for sharing thoughts, I will keep that in mind.
control: reassign -1 lxde-common
Thank you very much for reporting this. Apparently this issue is coming
from the fact there is no lxde-session package which is named lxde-common
and therefore many are confused because lxde package is just metapackage
with components but session files itself.
So it appear it was your local cache somehow broken and nobody (not even
yourself) cannot reproduce the issue, right?
If so, then this issue should be closed as not-reproducible. Thank you.
Package: openbox-kde-session
Version: 3.6.1-3
Severity: grave
After installing package openbox-kde-session one would expect to have a
GUI session available. Although it isn't. It fails on running the file
that executes session:
root@ag:/# openbox-kde-session
/usr/bin/openbox-kde-session: 20:
Package: debian-maintainers
Severity: normal
Annual ping it is.
Thanks!
signature.asc
Description: Digital signature
control: fixed -1 0.8.2-1
Thank you very much for reporting this issue. I believe mentioned problem
is fixed in version 0.8.2-1 which is currently in testing, and few other
problems should be fixed in upstream sources, a new version that includes
those fixes is going to be released soon.
control: reassign -1 libmenu-cache-bin 1.0.0-1
control: fixed -1 1.0.2-1
This issue is definitely a bug in menu-cache implementation, it somehow
updates only one cache file if something changed and forgets all others.
Thank you very much for reporting this issue, and I would like to cheer
you up
Ah, forget about previous message, found the problem.
Thank you for a report, fixed version will come soon.
>Package: openbox-lxde-session
>Version: 0.99.2-1
>Severity: grave
>When trying to install openbox-lxde-session package, dpkg fails with an error
>message:
> dpkg: error processing archive .../openbox-lxde-session_0.99.2-1_all.deb
> (--unpack):
> trying to overwrite
Thank you very much for a suggestion. Fairly sensible.
>Here is an example of what is shown in a tooltip:
>> Battery 0: 97% charged, 0:00 left
>> Energy full design: 56160 mWh
>> Energy full: 40930 mWh
>> Energy now: 39900 mWh
>> Power now:12804 mW
>> Current voltage: 12.178 V
Thank you very much for
control: reassign -1 lxde-common 0.99.2-2
Thank you very much for reporting this. It appears due to repackaging of
lxsession package, so lxde-common misses two dependencies now. Will fix
it ASAP.
Thank you for a suggestion. While using new libs might be an advantage,
libvte-2.91 uses GTK+ 3.0, while until now lxterminal package was using
GTK+ 2.0 (as well as rest of LXDE components). Switch to GTK+ 3.0 is not
much desirable since LXDE is positioned as a lightweight environment but
GTK+ 3.0
Hello!
>the two bug https://bugs.debian.org/858567 (just fixed in a very
>recent upload) and https://bugs.debian.org/857795 are not present in
>the initial upload of the according package version, only in the
>recent BinNMUs. So I wonder if these issues might stem from a recent
>build
Thank you for reminding on that, will look at it ASAP.
Hello!
>This is due to shipping a non-deterministic build config log. I
>don't believe shipping this file is very useful so we can simply
>drop it.
Yeah, that was my fault, I've tested build issues and forgot to remove
that log. Unfortunately it was too late to push update when I've noticed
control: fixed -1 libfm/1.2.5-1
Alf Gaida has written on Saturday, 8 July, at 20:58:
>Package: libmenu-cache-dev
>Version: 1.0.3~7-g4695338-1
>Severity: important
>just a reminder - we talked about in October/November last year.
I hope you've read about proper way of bootstraping which is
Thank you for noticing. I'm going to release 0.12.0 version soon, just a
bit more testing needed to be sure it's stable enough. :)
Both bugs in BTS will be fixed, as well as found ones since 0.11 versions.
.patch from upstream
+(Closes: #849356, #851748, LP #1558407).
+
+ -- Andriy Grytsenko <and...@rep.kiev.ua> Mon, 24 Apr 2017 23:02:01 +0300
+
menu-cache (1.0.2-1) unstable; urgency=medium
* Merging upstream version 1.0.2 (LP: #1635438).
diff -Nru
menu-cache-1.0.2/debian/patches/01-Fix-c
Package: libmenu-cache3
Version: 1.0.2-2
Severity: serious
Tags: upstream security
The socket placed in /tmp is predictable and public-writable. Therefore
if one user placed a symlink to another socket instead of socket for
another use then said another user will either be unable to get menu, or
Package: pcmanfm
Version: 1.2.5-2
Version: 1.2.3-1.1
Severity: serious
Tags: upstream security
The socket placed in /tmp is predictable and public-writable. Therefore
if one user placed a symlink to another socket instead of socket for
another user then said another user will either be unable to
Thank you very much!
control: fixed -1 libfm/1.2.5-1
Actually, if you would do proper bootstrapping described in details at
https://wiki.debian.org/DebianBootstrap page then there will be no FTBFS
at all (stage1 build will build all packages fine then stage2 build will
build rest of them, no FTBFS). Package libfm is
Actually this is a bug in gtk-doc, see
https://bugzilla.gnome.org/show_bug.cgi?id=783420
It should be fixed by gtk-doc upstream if I read that bugreport right,
although it's workarounded by libfm upstream, see the latest commit
b072ee0400432d72fdf86ba9fed74a7e0ec11ec1 in the libfm upstream GIT.
Package: debian-maintainers
Severity: normal
Annual ping it is.
Thanks!
signature.asc
Description: Digital signature
Thank you for this notice. I will try to find a way and handle this
situation ASAP, it's really complicated one, I cannot disagree.
Hello Adrian!
Thank you very much for pointing on this issue, will work on it ASAP.
Unfortunately, I cannot determine where the crash happens, from your data.
Could you, please, gather a crash debug info and give me access to it?
Thank you in advance.
control: tag -1 jessie
control: fixed -1 1.2.5-1
Thank you for reporting this, although I'm not sure if it's still
reasonable to backport it into Jessie at this point.
control: reassign -1 lxpolkit
Thank you for reporting this.
This seems to be an issue with policy kit configuration, when it comes
from xrdp it conflicts with one coming directly on desktop. Need a bit
more of investigation.
Dear Jonathan,
could you clarify your issue a bit more, please?
For me it seemed as if display manager started a wrong session. It would
be pretty helpful to see list of running processes when the issue happens.
The best you can do is to use 'ps -fx' command and then quote its output.
Thank you
control: reassign -1 lxpolkit
Thank you for reporting this.
Your issue seems as a lxpolkit configuration problem. Could you, please,
look if there aren't two lxpolkit processes running at the moment when
you are logged in?
Could you also check if there is a policy kit agent checked on in the
control: reassign -1 pcmanfm
control: affects -1 + lxde-common
Thank you for the report.
Actually you reported three issues into one, that is not an appropriate
way to do reports.
In regards of exact issue. Wrapping is done by the desktop manager in an
obvious reason - the text does not fit
1 - 100 of 140 matches
Mail list logo
