Bug#1066239: gnome-system-tools: FTBFS: shares-tool.c:113:17: error: implicit declaration of function ‘table_add_share’ [-Werror=implicit-function-declaration]
Thank you very much for the patch. Applied it, it looks fine.
Bug#1008313: lxpolkit: no authentication dialog can't use it
Hello dear Paul and all Release Team! >Can you at least please comment on this bug? Do you recognize it? Can >you reproduce it (I would guess not, seems like this would make lxde >nearly useless for everybody)? *If* lxde is nearly useless for >everybody, I'd like to know, then I think we shouldn't ship it with >bookworm. Actually I did not managed yet to reproduce this bug although I have a bit of problems with electricity (you know, there is a war ongoing in Ukraine) so it's a bit hard right now to create a clean environment for testing. It would be good to get some help with this issue actually. I hope I can make some testing in the nearest future but cannot promise anything yet. I'm sorry. And yet I use LXDE myself each day, I cannot say it's *nearly useless* but many people use it and rarely have problems.
Bug#1005818: task-lxde-desktop: libreoffice is used as default pdf reader
Although it appears there is another way to make that, just for LXDE, using file /etc/xdg/lxde-mimeapps.list. May be it will be the best way after all.
Bug#1005818: task-lxde-desktop: libreoffice is used as default pdf reader
>> Since evince is automatically installed, it's "just" a matter of setting >> evince as the default application for PDF - as you already have tried to :-) >Sure. Well, if evince is installed then it should exist in the XDG MIME database and therefore it should be present in the "Open with ..." file manager menu. Although which application will be launched on simple Open action is defined by order: 1) use user defined default application for that MIME type 2) use system defined default application for that MIME type 3) use last registered for that MIME type by user 4) use last registered for that MIME type by system When (1) is used - this is what we do when we associate some file with some application, as it was said. Usage of (2) is Debian-wide, you know, and it definitely has no relation to LXDE package but rather to evince package (which may set system-wide default to evince at installation and drop it at removal). I see nothing what could be done in regards of (3) and (4) as we cannot determine order in which packages (and especially user applications such as WINE ones) are installed, and there is no preference order in terms of XDG MIME database. Please, clarify what we can do in that regard, and probably we should reassign this issue to evince package instead if we decide it should be set as system default. Thanks.
Bug#996276: foxeye: FTBFS with OpenSSL 3.0
>You can test it by installing the version from unstable. It is not in unstable yet, see https://packages.debian.org/search?keywords=libssl-dev and https://tracker.debian.org/pkg/openssl
Bug#996276: foxeye: FTBFS with OpenSSL 3.0
control: tags -1 - bookworm sid + bookworm-ignore experimental Could you explain, please, how this issue is an RC bug if sid contains version 1.1.1o and 3.0 version is only in experimental? And how should I do and test required changes if said version is not in sid at all?
Bug#988696: installation-reports: No network management in LXDE task
Thank you everyone for the analysis. Will check how to make it work correctly, let fix it on the next upload.
Bug#987086: unblock: lxpanel/0.10.1-2
Package: release.debian.org
Please unblock package lxpanel (0.10.1-2), it fixes the bug #985517 of
severity serious: lxpanel-dev has missing dependency on lxpanel.
Debiff between versions 0.10.1-1 and 0.10.1-2 follows:
diff -Nru lxpanel-0.10.1/debian/changelog lxpanel-0.10.1/debian/changelog
--- lxpanel-0.10.1/debian/changelog 2021-02-07 00:12:25.0 +0200
+++ lxpanel-0.10.1/debian/changelog 2021-04-17 13:22:04.0 +0300
@@ -1,3 +1,9 @@
+lxpanel (0.10.1-2) unstable; urgency=medium
+
+ * Making lxpanel-dev package Multi-Arch: no (Closes: #985517).
+
+ -- Andriy Grytsenko Sat, 17 Apr 2021 13:22:04 +0300
+
lxpanel (0.10.1-1) unstable; urgency=medium
* Merging upstream version 0.10.1.
diff -Nru lxpanel-0.10.1/debian/control lxpanel-0.10.1/debian/control
--- lxpanel-0.10.1/debian/control 2021-02-06 23:49:02.0 +0200
+++ lxpanel-0.10.1/debian/control 2021-03-20 13:19:28.0 +0200
@@ -63,8 +63,8 @@
Package: lxpanel-dev
Architecture: any
-Multi-Arch: same
-Depends: ${misc:Depends},
+Multi-Arch: no
+Depends: ${misc:Depends}, lxpanel (= ${binary:Version}),
libgtk2.0-dev, libfm-gtk-dev (>= 1.2.0)
Breaks: lxpanel (<< 0.8.2)
Replaces: lxpanel (<< 0.8.2)
Bug#987085: unblock: lxpanel/0.10.1-2
Package: lxpanel
Version: 0.10.1-2
Please unblock package lxpanel (0.10.1-2), it fixes the bug #985517 of
severity serious: lxpanel-dev has missing dependency on lxpanel.
Debiff between versions 0.10.1-1 and 0.10.1-2 follows:
diff -Nru lxpanel-0.10.1/debian/changelog lxpanel-0.10.1/debian/changelog
--- lxpanel-0.10.1/debian/changelog 2021-02-07 00:12:25.0 +0200
+++ lxpanel-0.10.1/debian/changelog 2021-04-17 13:22:04.0 +0300
@@ -1,3 +1,9 @@
+lxpanel (0.10.1-2) unstable; urgency=medium
+
+ * Making lxpanel-dev package Multi-Arch: no (Closes: #985517).
+
+ -- Andriy Grytsenko Sat, 17 Apr 2021 13:22:04 +0300
+
lxpanel (0.10.1-1) unstable; urgency=medium
* Merging upstream version 0.10.1.
diff -Nru lxpanel-0.10.1/debian/control lxpanel-0.10.1/debian/control
--- lxpanel-0.10.1/debian/control 2021-02-06 23:49:02.0 +0200
+++ lxpanel-0.10.1/debian/control 2021-03-20 13:19:28.0 +0200
@@ -63,8 +63,8 @@
Package: lxpanel-dev
Architecture: any
-Multi-Arch: same
-Depends: ${misc:Depends},
+Multi-Arch: no
+Depends: ${misc:Depends}, lxpanel (= ${binary:Version}),
libgtk2.0-dev, libfm-gtk-dev (>= 1.2.0)
Breaks: lxpanel (<< 0.8.2)
Replaces: lxpanel (<< 0.8.2)
Bug#985517: lxpanel-dev: broken symlink: /usr/lib/x86_64-linux-gnu/lxpanel/liblxpanel.so -> liblxpanel.so.0.0.0
Thank you very much for finding this. I just tried to make lxpanel-dev to be 'Multi-Arch: same' but apparently I was wrong and it should be marked 'Multi-Arch: no' instead, leaving its dependency on lxpanel as it used to be.
Bug#941081: O: clipit -- lightweight GTK+ clipboard manager
control: retitle -1 ITA: clipit -- lightweight GTK+ clipboard manager control: owner -1 ! I've missed the point when this package was orphaned. I have a desire to pick it up since I use it all the time and developers didn't abandoned it. Let return it back into Debian on next cycle. Thank you.
Bug#833268: task-lxde-desktop: LXDE desktop does not include a web browser
control: reassign -1 lxpanel 0.10.1-1 Thank you for reporting this and investigating on it. As much as I can see the root issue is that an icon on a panel does not work without a working x-www-browser alternative installed. That can be solved with adding a line TryExec: /usr/bin/x-www-browser into lxde-x-www-browser.desktop file. Therefore reassigning this bug to the lxpanel package to fix it.
Bug#960111: lxde: recommends deprecated clipit
I'm agree, ClipIt needs some alternative. Although from what I saw about Diodon it integrates into GNOME desktop and as such it will bring start of bunch of GNOME services (dconf, zeitgeist) which are not started by the ClipIt of course. Not very good for a desktop environment which is intended to be lightweight, thus I would not name Diodon as appropriate tool for LXDE albeit viable one. Another issue with Diodon is that it is too much minimalistic, it have neither correct right-click support (it is understandable for GNOME desktop which is now oriented on touchscreen so no right-click would be ever supported), nor history management, nor permanent history items, nor any history list configuration. So far Diodon vs ClipIt is a bycicle vs Tesla. I'll try to find if some viable alternative could be added beside clipit. Thank you for your notice. What is strange about ClipIt is why it was considered as deprecated while it is still developed (https://github.com/CristianHenzel/ClipIt) by the upstream, current version is 1.4.5. May be said "deprecated" state was inspired by some people behind Diodon to kill concurrency? May be it's better to take over clipit maintenance and return it back into Debian? I'll try to contact its maintainer for more information.
Bug#910508: lxde-common: closed bug #760971 still not fixed on debian 9.5 and lxde-common 0.99.2-3
Thank you for reporting that issue. I would like to ask you for few more details if that is possible. First od all I would like to see output of the command (when issue happens): ls -lR $HOME/.config/lxpanel/ Another this I would like to know is content of few environment variables such as XDG_CONFIG_DIRS and XDG_CURRENT_DESKTOP And last one thing I would ask you if your panel uses default command line options from installed file, please.
Bug#982395: pcmanfm: FTBFS cannot compile package from source
control: tags -1 + moreinfo control: notfound -1 libfm/1.3.1-1 I'm afraid your files were corrupted. This mentioned API stays the same since FmFolderView API was introduced in version 1.0.1 of LibFM and it is still the same in fm-folder-view.h: = voidfm_folder_view_item_clicked(FmFolderView* fv, GtkTreePath* path, FmFolderViewClickType type); = Check if your code was not came from some patch which you applied sometime.
Bug#969657: pcmanfm: relies on xfce4-panel, while LXDE uses lxpanel
control: reassign -1 xfce4-panel This is an issue from file /usr/share/applications/panel-desktop-handler.desktop which should contain 'OnlyShowIn=XFCE;' line but it does not have one. Dear maintainer of xfce4-panel, please, handle this issue. Thank you.
Bug#880537: Fails to start
control: tag -1 + moreinfo >From your report it seems you have not installed recommended package lxhotkey-plugin-openbox, without which you can use only command line interface for this application. Please, confirm that. Thank you.
Bug#932461: src:libfm: archivers.list fix xarchiver command
Hello! Andrew Lee has written on Friday, 29 January, at 19:05: >What's your opinion on this MR? I'll accept related MR for libfm-qt if you >accept this here for libfm. I thought if we should make it more flexible in a way to test for version and use one or other switch to command but couldn't find a reliable and simple way to test for version (command to retrieve version was changed by the author too, you know). Although it was so much time passed since that dramatic change made by xarchiver author that it might be mostly safe now to use it even in upstream sources despite the fact it might cause some problems for those who have older version of xarchiver. All the blames should come to the author who never thought about its users though. Being also upstream author I'll make it a release 1.3.2 which includes this change this week-end then so will make it packaged, updated and uploaded to Debian as well. With best regards, Andriy.
Bug#967686: Bug#967686: pcmanfm: depends on deprecated GTK 2
Hello! >It is not solution for Debian. Lxde just needs rebuild with gtk3 libs, >it'senough for fix this bug. I will do NMU after bullseye release if >maintainer won't do it. I'm against just rebuilding everything against GTK+ 3.0 and abandoning GTK+ 2.0. While version 3.0 still have some advanced features, it doesn't just take much more resources (which may be a big issue for devices like Raspberri Pi) but it also have some extra dependencies, and some people still prefer look and feel of GTK+ 2.0 and highly dislike GTK+ 3.0 one. So to solve this I believe it's much more appropriate to create parallel packages - one against GTK+ 2.0 (for tight, old platforms and people who dislike GTK+ 3.0) and another against GTK+ 3.0. I plan to do it all after coming release of Debian. Thank you for a suggestion, in any case.
Bug#957510: lxtask: diff for NMU version 0.1.9-1.1
>I've prepared an NMU for lxtask (versioned as 0.1.9-1.1) and uploaded >it to DELAYED/14. Please feel free to tell me if I should cancel it. Thank you very much. There is an issue with GIT which we tried to fix and failed. It was what delayed the actual fix for so long. After all it was decided to use another mirror of the GIT so update is going to come pretty soon. Thank you very much again, your change wouldn't be forgotten of course.
Bug#961559: pcmanfm: Rename folder in left side pane directory tree crashes pcmanfm
>However, this behaviour is still incorrect and unacceptable for many >reasons: Yes, I completely agree that is a bug. Whole reason why I asked you to do this was to get a bit more details for fixing it. Thank you very much for your help.
Bug#961559: pcmanfm: Rename folder in left side pane directory tree crashes pcmanfm
Well, in case if it just exits then probably path in main window became invalid and therefore window was closed. Please, look in the settings, what is your choice on the option 'When removable medium unmounted:'? Is it 'Close tab containing removable medium' probably? It yes then try to change it to 'Change folder in the tab to Home Folder', please. Your issue might be gone after that.
Bug#958169: lxterminal doesn't recognize URLs anymore
control: tags -1 fixed-upstream >Upstream LXTerminal has fixed this issue in the following commit: >https://github.com/lxde/lxterminal/commit/b1e3db193651b33db1e112a71ccc1e9868f37093 Thank you very much for pointing on that. Then it will be fixed on next upload which I hope happens soon.
Bug#888670: gnome-system-tools: has been unmaintained upstream for a long time
Hello! You have written on Friday, 14 February, at 20:39: >The new repository[1] that was supposedly fixing this bug report >doesn't even include the upstream sources (or their git history). >It's a plain packaging repo with only the debian/ directory. >I don't see how that's supposed to fulfil the need for you to >become your own uptream. You most likely want to create a fork >from the archived gnome repo[2]. Yes, I've created a fork and mentined it in in the debian/control file: Homepage: https://github.com/LStranger/gnome-system-tools I had a hope that it's enoungh. From your message it seems it's not. >Also please pick a (new) name for your fork as it's *not* THE >gnome-system-tools (anymore), unless you actually talk to the gnome >project to officially pick up as the gnome maintainer (but I suspect >at this point there's absolutely no interest from the gnome project to >have gnome-system-tools revived). >(Once a proper upstream fork exists, packaging that under the new name >and providing a transitional gnome-system-tools meta-package will give >current users a seemless upgrade experience.) I understand that it's possible but it would need creating new package and removing old one, thus involve some DD and some ftpmaster as well. I'm still just a DM so did what is available for me to do. Thank you for an advice, I'll decide how I can handle all this situation. >(Please also make sure to look into all the deprecated notices that is >being spit out during build. Those will likely become an issue in the >not too distant future. But first you might want to reconsider if you >really have the resources for taking on the task of becoming your own >upstream.) Yes, I understand all this said and, frankly speaking, I really have not enough resources to handle this whole bunch (it also includes liboobs and system-tools-backends) but unfortunately there is no another standalone GTK tool to manage users and date/time around, it was a whole reason why I've picked up this package in the first place. And as a LXDE maintainer, I cannot leave LXDE users without means to manage users and date/time. It's a pretty hard and problematic dilemma I have here, unless I start to write appropriate tools from scratch by myself but that would take a lot of time as well and this is also a problem. Well, as for LXDE I hope to handle date/time management by the panel indicator later (and actually it is almost never required as most of decent systems does not need manual managing due to NTP in action) but users still cannot be handled without this package. So in short, if I found some standalone tool to manage users then I would be very glad to get rid of these three packages. With best regards, Andriy.
Bug#885814: bumping severity of lxsession's use of libunique to Serious
Hi, >Personally, I was surprised that LXDE was kept in Debian; I thought it >was going to be replaced by LXQt. Are you planning to keep LXDE in >Bullseye? Actually LXDE and LXQt are just similar but pretty different desktop environments and not every LXDE user may feel happy to be forced to use LXQt, especially on old or small systems. >See the master bug https://bugs.debian.org/885813 for documentation >about migrating away from libunique. I believe it requires moving to >GTK3 which sounds like it might be a very large project for a desktop >environment. I think it should be safe to use GTK+3 build for lxsession, it's already done for lxterminal long time ago. For other applications I wouldn't be so sure as GTK+3 is still much more resource eager than GTK+2 is. With best regards, Andriy.
Bug#947530: gnome-system-tools: build-depends on deprecated gnome-doc-utils
Hello Andreas! Thank you very much for the patch. It appears you've done all the work and it worked like a charm. All porting guide steps are handled, I've rechecked that. Thank you very much. With best regards, Andriy.
Bug#888670: gnome-system-tools: has been unmaintained upstream for a long time
Hello Andreas! You have written on Sunday, 26 January, at 10:36: >Control: severity -1 serious >Hello, >On Sun, Jan 28, 2018 at 08:27:57PM +0200, Andriy Grytsenko wrote: >> 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. >The python2 removal efforts are upon us and with that gnome-doc-utils >is about to get removed (as it has been superseeded by yelp a very long >time ago so porting gnome-doc-utils isn't considered at all). >The gnome-system-tools package is basically the sole remaining blocker >for this now and it needs active effort to get ported over to yelp. >Discussion about this in #947530 >A plan for how gnome-system-tools is going to maintained is desperately >needed at this point. As there has been no followup on the above 2 year >old message it's unclear to me if such a plan exists, but my impression >is that very little has happened in the past 2 years despite many >outstanding really bothersome bug reports against this package. >If a plan is not presented very soon it looks like the only viable >option is to finally file a RoQA: RM bug report to get >gnome-system-tools removed from the archive, which I'm going to do >unless there's any evidence of active maintenance. >I've already notified the sole remaining reverse-dependency, >parl-desktop, in #888675. I'm also CCing the reverse recommends >which should either drop their recommends or need to step up >and help out if they want to see gnome-system-tools package >continue to be available in the debian archive. Mea culpa. Got too cluttered with real life events and completely forgot about this issue. I think it's a time to get to it ASAP, this time for real. This week I plan to investigate which way is better to solve this issue and then solve it. I think 10 days should be enough but I hope to fix it faster than that. I'm sorry for being so late with that. With best regards, Andriy.
Bug#805727: lxde: desktop fails to load
control: tags -1 + moreinfo Could you, please, clarify if this old issue ever happens again or not? Thank you very much.
Bug#677262: lxsession: system beeps (still?) not working under LXDE
Could you, please, provide output of command 'xset q' on your system?
Bug#788674: lxsession: LXDE not loading at login
This seems to be similar to bug reported against at-spi2-core package https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918776 but with another problem produced. I would like to hear if this problem is still present or reproducible on your system. Let us know, please.
Bug#923408: lxpanel: weather applet does not update at startup
>Thanks for fixing the weather applet by using the OpenWeatherMap API. >Here's another problem though: >When I start my LXDE session the weather applet does not show the >temperature etc., but rather says that weather information for my >location is not available. Thank you for your report. Actually I am aware of that but unfortunately time before freeze is so tight that I could not risk to develop reliable solution as it might take time to develop and test. It will be developed later so I hope to get it backported to the buster-backports.
Bug#854643: fix for this bug
I believe the mentioned file is appropriate for libnotify-bin and isn't appropriate for lxpanel package since lxpanel does not interact with the daemon directly. And thank you for a notice about dependencies. Both libnotify-bin and notification-daemon are added as Recommended by lxpanel now. The original issue is probably related to #84, so if current is missing from data then alarm will never go out. Fix for such case also pushed. Please, reopen this bug if issue still persists. Thank you very much.
Bug#914150: pcmanfm: SIGSEGV, Segmentation fault on opening folder
>Tryed with version of libgdk-pixbuf2.0-0 from stable, same problem. >I have 2 PC, both with Debian testing and Fluxbox as DE, pcmanfm crashes >on both opening that folder. Could you put said file somewhere so I could experiment with it and find a soultion if possible, please?
Bug#914150: pcmanfm: SIGSEGV, Segmentation fault on opening folder
>Thread 30 (Thread 0x7f681634a700 (LWP 24728)): >#0 0x7f6816c292c0 in () > at >/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so >#1 0x7f682029812d in () > at /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 >#2 0x7f6820298bd8 in gdk_pixbuf_loader_write () > at /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 >#3 0x7f6820296668 in gdk_pixbuf_get_file_info () > at /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 >#4 0x7f682095da06 in read_image_from_file > (filename=0x7f680c001570 >"/mnt/dati_linux/cns-doc/REGATE/RegateDOC/meteoCNS") at >gtk/fm-thumbnail.c:142 > w = 1 > h = 1 Apparently this is a bug in gdk_pixbuf_get_file_info() function which crashes reading your file /mnt/dati_linux/cns-doc/REGATE/RegateDOC/meteoCNS That function is a part of package libgdk-pixbuf2.0-0. Could you try some another version of that package, please, to check if this issue will be fixed or not? Thank you.
Bug#914150: pcmanfm: SIGSEGV, Segmentation fault on opening folder
Nicola has written on Saturday, 26 January, at 11:30: >Bug still exists. Opening a folder with many subfolder and files pcmanfm crash That is pretty bad. Thank you for such a notice. I would be glad if you could help with trace debug, please. For that you have to install debug symbols for both libfm and pcmanfm - that are libfm-dbg, libfm-gtk-dbg, pcmanfm-dbg packages. Then attach gdb to the running process, you can do that using next command: gdb pcmanfm $(pidof pcmanfm) and when you attach to it, simply enter 'c' (which means continue) and reproduce your issue. When it crashes, please, enter a GDB command to see backtraces: thread apply all bt full and then send the return of it to me or to BTS to diagnose what happens. Don't hesitate to contact me if you get into some troubles with GDB. Thank you in advance.
Bug#918467: lxpanel: Weather plugin uses obsolete APIs, does not work.
Yes, Yahoo unfortunately ended free service at January 3. New API requires registering the application and has unknown restrictions which probably will lead the weather plugin to DoS situation, because if developer registers API to get a key then that limitation will be applied to each user of that API so may be soon exceeded. Abother issue that new Yahoo API requires digital signature for each request which in turn will involve libssl with all their restrictions. Unfortunately all weather providers now made their API available via some kind of registration. We can force each user to register but that will be pretty inconvenient for users. Another approach is to register some token for LXDE developers public e-mail but if (for example) 50 users will use the plugin and we set update time once in two hours, that will make 50/120=4000 requests per minute, which exceeds number for any free subscription which definitely makes the plugin unusable at all, so this approach is not a way to go. Thus I have no idea what else to do except to remove the plugin from distribution.
Bug#907945: libfm FTBFS with glib 2.58
Hello Adrian! Thank you very much for pointing on this issue, will work on it ASAP.
Bug#830246: Problem with templates
control: severity -1 wishlist Thank you very much for reporting this. Actually this is not a bug but rather a missing feature. Therefore I change it into wishlist issue.
Bug#876614: libfm FTBFS with gtk-doc-tools 1.26: fm-module.xml:72: parser error : error parsing attribute name
Thank you for a NMU but that isn't needed, I think 1.3.0 will come pretty soon where this issue is fixed. Cheers!
Bug#851855: pcmanfm: F4 or "open current folder in terminal" always ends up in the home directory
I've tested this again recently and it appeared the behavior depends on the terminal in use - some terminals work just fine and some don't work. Could you verify if that is the same for you or not, please? If it is, then this issue should be addressed to terminals where it ceased to work lately (such as konsole for example) instead. Thank you very much.
Bug#842447: add "eject" as dependency
Thank you very much for reporting this. Actually "eject" should be a dependency of libglib2.0 what isn't the case. Will add it into libfm dependencies on next package release soon.
Bug#833270: poor text wrapping for Wastebasket icon in default install
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 into default space under the icon. There are two solutions for that: - decrease desktop font size (currently: Sans 12, in desktop config); - increase desktop cell size (currently: 100 pt, in pcmanfm sources). Note that in case of default font size we can change only value applied to newly created users or after ~/.config/pcmanfm reset. In other cases only manual changes may be applied.
Bug#864402: lxde "No session for pid ...." on screen after login.
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 list of autostarted processes? You can see that in lxsession default apps configuration program on tab 'Autostart'. If it's checked on then please, check it off and then report if it fixes the issue. Thank you in advance.
Bug#865116: After a clean reboot user A logs ok to desktop (through xrdp) but user B gets: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs
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.
Bug#876010: LXDE session doesn't properly load - desktop is managed but no panel is loaded.
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 in advance.
Bug#851786: Terminal emulator command arguments ignored in Preferences -> Advanced
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.
Bug#889514: Not work desktop icons and set wallpapper
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.
Bug#888670: gnome-system-tools: has been unmaintained upstream for a long time
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.
Bug#876614: libfm FTBFS with gtk-doc-tools 1.26: fm-module.xml:72: parser error : error parsing attribute name
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.
Bug#881537: Annual ping for Andriy Grytsenko
Package: debian-maintainers Severity: normal Annual ping it is. Thanks! signature.asc Description: Digital signature
Bug#873011: Avoid circular dependency between menu-cache and libfm
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 ready for bootstrapping since version 1.2.5-1. Thank you.
Bug#858435: Fixed upstream
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.
Bug#867707: Please fix cycle dependency between libfm and menu-cache for powerpcspe
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 explained in details at https://wiki.debian.org/DebianBootstrap page. The said libfm package is fixed in version 1.2.5-1 in that regard since last December and is ready for proper bootstrapping but it seems powerpcspe team could not get to process it yet. I will try to get in touch with them. Thank you very much.
Bug#862570: libmenu-cache: menu-cached socket may be blocked by another user.
Thank you very much!
Bug#862571: pcmanfm: single instance socket may be blocked by another user.
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 use pcmanfm, or may send requests to the first user's pcmanfm. Upstream released a fix for this issue: https://git.lxde.org/gitweb/?p=lxde/pcmanfm.git;a=commitdiff;h=bc8c3d871e9ecc67c47ff002b68cf049793faf08
Bug#862570: libmenu-cache: menu-cached socket may be blocked by another user.
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 will receive menu of some other user. Upstream released a fix for this issue: https://git.lxde.org/gitweb/?p=lxde/menu-cache.git;a=commitdiff;h=56f66684592abf257c4004e6e1fff041c64a12ce
Bug#861475: unblock: menu-cache/1.0.2-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package menu-cache
Package update which contains fix for #851748 of severity "important" (although
it can be considered "serious" since it affects usability of Desktop
Environment)
is already in sid. I would like to take the fix into testing as well. Change is
pretty small, see it below. Thank you.
diff -Nru menu-cache-1.0.2/debian/changelog menu-cache-1.0.2/debian/changelog
--- menu-cache-1.0.2/debian/changelog 2016-11-06 19:21:38.0 +0200
+++ menu-cache-1.0.2/debian/changelog 2017-04-24 23:05:22.0 +0300
@@ -1,3 +1,12 @@
+menu-cache (1.0.2-2) unstable; urgency=medium
+
+ * Removing override_dh_builddeb target from debian/rules, it fails on 32-bit
+archs.
+ * Adding 01-Fix-crash-with-invalid-Name-tag-in-a-menu.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-crash-with-invalid-Name-tag-in-a-menu.patch
menu-cache-1.0.2/debian/patches/01-Fix-crash-with-invalid-Name-tag-in-a-menu.patch
---
menu-cache-1.0.2/debian/patches/01-Fix-crash-with-invalid-Name-tag-in-a-menu.patch
1970-01-01 03:00:00.0 +0300
+++
menu-cache-1.0.2/debian/patches/01-Fix-crash-with-invalid-Name-tag-in-a-menu.patch
2017-04-24 22:59:44.0 +0300
@@ -0,0 +1,32 @@
+Author: Andriy Grytsenko <and...@rep.kiev.ua>
+Description: Fix crash with invalid tag in a menu. (Closes: #849356,
#851748)
+Bug: https://sourceforge.net/p/lxde/bugs/863
+Applied-Upstream: 54ab9e45764435634cdf5de360b295ee3a22817a
+
+--- a/menu-cache-gen/menu-merge.c
b/menu-cache-gen/menu-merge.c
+@@ -1,7 +1,7 @@
+ /*
+ * menu-file.c : parses .menu file and merges all XML tags.
+ *
+- * Copyright 2013-2016 Andriy Grytsenko (LStranger) <and...@rep.kiev.ua>
++ * Copyright 2013-2017 Andriy Grytsenko (LStranger) <and...@rep.kiev.ua>
+ *
+ * This file is a part of libmenu-cache package and created program
+ * should be not used without the library.
+@@ -138,11 +138,13 @@ static gboolean _menu_xml_handler_Name(FmXmlFileItem
*item, GList *children,
+guint n_attributes, gint line, gint
pos,
+GError **error, gpointer user_data)
+ {
++FmXmlFileItem *name_item;
+ const char *name;
+
+ RETURN_IF_IN_LAYOUT(item, error);
+-item = fm_xml_file_item_find_child(item, FM_XML_FILE_TEXT);
+-if (item == NULL || (name = fm_xml_file_item_get_data(item, NULL)) ==
NULL ||
++name_item = fm_xml_file_item_find_child(item, FM_XML_FILE_TEXT);
++if (name_item == NULL ||
++(name = fm_xml_file_item_get_data(name_item, NULL)) == NULL ||
+ strchr(name, '/') != NULL) /* empty or invalid tag */
+ {
+ RETURN_TRUE_AND_DESTROY_IF_QUIET(item);
diff -Nru menu-cache-1.0.2/debian/patches/series
menu-cache-1.0.2/debian/patches/series
--- menu-cache-1.0.2/debian/patches/series 1970-01-01 03:00:00.0
+0300
+++ menu-cache-1.0.2/debian/patches/series 2017-04-24 22:54:01.0
+0300
@@ -0,0 +1 @@
+01-Fix-crash-with-invalid-Name-tag-in-a-menu.patch
diff -Nru menu-cache-1.0.2/debian/rules menu-cache-1.0.2/debian/rules
--- menu-cache-1.0.2/debian/rules 2016-11-06 19:07:30.0 +0200
+++ menu-cache-1.0.2/debian/rules 2016-12-11 01:08:44.0 +0200
@@ -10,12 +10,8 @@
override_dh_auto_install:
dh_auto_install
-
rm -f debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.la
-override_dh_builddeb:
- dh_builddeb -- -Zxz -z9
-
override_dh_install:
dh_install --fail-missing
Bug#860373: foxeye: please make the build reproducible
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 that, due to Stretch freeze. It will be definitely fixed on next upload!
Bug#857795: /usr/@DATADIRNAME@/ only showed up with the recent -fPIE rebuilds: Maybe a debhelper or build system bug?
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 toolchain, e.g. debhelper or autotools issue: Since the issue is a result of some gettext/intltool variable deprecation (probably over a decade ago), I suppose that some never autotools script (autopoint probably) just dropped it, so problem appeared.
Bug#857795: Correct location for installed files is /usr/share/locale/
Thank you for reminding on that, will look at it ASAP.
Bug#856308: lxde-common: hardware power button immediately issues shutdown, no prompt
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 then that would be perfect. Thank you.
Bug#855521: lxpanel: freezes all the desktop environment if started or lauch no matter desktop are used
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.
Bug#851748: libfm-extra4 in debian/testing kills LXDE menus
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 probably it is what happened. I would be pretty grateful if you could collect crash info on menu-cache-gen crash (such as crash dump with stack tracelog, with appropriate debug info package installed) so bug can be localized and fixed. Thank you in advance. As a workaround I could suggest to downgrade libfm-extra4 but it would be better to fix it ASAP. So bad it was found so close to the Stretch freeze so it's pretty tough to make a fix in time before freeze.
Bug#845555: lxpanel: battery monitor no longer working
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 test it now to be sure it's fixed before freeze (and if it's not then I still can upload a fix before January 25, but timeframe is short).
Bug#851855: pcmanfm: F4 or "open current folder in terminal" always ends up in the home directory
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.
Bug#845555: Time left not shown
>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 providing this useful info. It appears that 'Power now' is missed in calculations. I hope to fix it soon.
Bug#850330: lxpanel: ScreenLock launcher no longer works (XScreenSaver?)
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.
Bug#790184: lxterminal: depends on vte which is deprecated
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 uses much more resources and has more bugs, some of which are not easy to workaround. Overall, users are negative on switching over to GTK+ 3.0 after some experience. And even if other applications aren't taken into consideration (I mean mostly style difference), use just one application with GTK+ 3.0 while other ones are GTK+ 2.0 may be a waste (as both GTK+ 2.0 and GTK+ 3.0 will be loaded at the same time).
Bug#848159: lxde: Please don't depend on transitional iceweasel
Thank you very much for a suggestion. Fairly sensible.
Bug#845926: Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1
Ah, forget about previous message, found the problem. Thank you for a report, fixed version will come soon.
Bug#845926: Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1
>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 '/etc/xdg/lxsession/LXDE/autostart', which is also > in package lxde-common 0.99.2-1 I believe it's some dpkg error, just look at list of files in lxde-common package at https://packages.debian.org/sid/all/lxde-common/filelist: /etc/xdg/lxpanel/LXDE/config /etc/xdg/lxpanel/LXDE/panels/panel /etc/xdg/pcmanfm/LXDE/pcmanfm.conf /usr/share/doc/lxde-common/README.Debian /usr/share/doc/lxde-common/changelog.Debian.gz /usr/share/doc/lxde-common/changelog.gz /usr/share/doc/lxde-common/copyright /usr/share/lxde/images/logout-banner.png /usr/share/lxde/images/lxde-icon.png /usr/share/lxde/wallpapers/lxde_blue.jpg /usr/share/lxde/wallpapers/lxde_green.jpg /usr/share/lxde/wallpapers/lxde_red.jpg there is no /etc/xdg/lxsession/LXDE/autostart file there! I have no idea what was happened in your system.
Bug#782834: dpkg/apt doesn't know lxde packages are installed
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.
Bug#845386: openbox-kde-session package is unusable
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: exec: startkde: not found The fix is pretty simple: package plasma-workspace which contains the mentioned startkde binary should be added to the Depends line.
Bug#791653: [lxpanel] Cannot interact properly with mwm window manager on the left or right sides
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.
Bug#820559: lxpanel: Application Launchbar doesn't show item unless Version key in .desktop file
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 since this issue should be fixed in testing repository, you may upgrade libmenu-cache-bin package and the issue should be fixed for you. You may want to upgrade libmenu-cache3 package as well, both packages should be binary compatible with jessie. Test it, please, and report back if something still does not work.
Bug#844032: Annual ping for Andriy Grytsenko
Package: debian-maintainers Severity: normal Annual ping it is. Thanks! signature.asc Description: Digital signature
Bug#843341: lxde: installing lxde doesn't give me an LXDE session
Thank you very much for sharing thoughts, I will keep that in mind.
Bug#843341: lxde: installing lxde doesn't give me an LXDE session
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.
Bug#835833: foxeye: please make the the package autoreconfable
>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 autoreconf did well, only problem was intl/ directory at build stage as newer autotools do not provide $MKINSTALLDIRS variable used by that ancient gettext, the fix is pretty simple though - replace version 0.11.5 mentioned in a file intl/VERSION with newer such as 0.17, then run autopoint -f, then repack the tarball, after that everything goes very smooth. Could you tell what was wrong in your tests, please? Thank you in advance (and thank you for your help in making it better).
Bug#840066: ITP: lxhotkey -- Lightweight global keyboard shortcuts configurator
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. This is a lightweight configurator independent of window manager and UI, which intended to work with any possible window manager from any kind of UI, using unified API. The most wanted such thing is for window managers which don't have own tool for managing keyboard shortcuts for the global actions such as screen / windows manipulations and executing commands or starting applications. Example of such window manager is Openbox.
Bug#838326: Openbox does not support startup notifications.
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 tried to start really started, and in some cases duplicated try may freeze whole system (if memory exhausted for example, or other resourse locked) so cold reboot is needed. Thus may be severity of this bug should be "serious" but "important" is the least. Fix is very much trivial though - just adding libxcursor-dev to build dependencies will fix the issue. Please, fix it both in jessie and in sid. Thank you.
Bug#835418: libfm: please make the build reproducible
Thank you very much for a fix, will add it on next upload!
Bug#821862: Do not release with stretch
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 any other DE. Yes, literally, there is no alternative to the gnome-system-tools and it depends on system-tools-backends.
Bug#793818: Pcmanfm crash sometimes at the end of file(s) copy
Oh, great! Thank you very much for the backtrace and steps provided. I hope to get it fixed soon!
Bug#793818: Pcmanfm crash sometimes at the end of file(s) copy
Thank you very much for the backtrace provided, I'll start from it and let you know when fix is available.
Bug#819703: Please continue providing a stable, high-quality X screensaver program in Debian
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 then I would raise the severity. signature.asc Description: Digital signature
Bug#793818: Pcmanfm crash sometimes at the end of file(s) copy
>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 and running under gdb may don't give any crashes but backtrace may be made from a coredump file as well, you just need to make sure you have enabled creating coredumps in your system: a) run command in terminal: sysctl kernel.core_pattern and see if output isn't something like /dev/null but a regular file path b) run command in terminal: ulimit -c and see if it's not set to 0 If coredumps creation is enabled then after crash happened just run a gdb in next form: gdb pcmanfm your-coredump-file-path and you'll be able to get backtrace. If -dbg package isn't installed then backtrace will lack most of useful information so that I would ask you to install mentioned -dbg packages before sending backtrace to us. Thank you in advance.
Bug#771168: lxde: please add localization to lxde
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?
Bug#782834: dpkg/apt doesn't know lxde packages are installed
control: tags -1 + moreinfo Thank you for your report. Although I don't see what exactly did you mean? What exactly goes wrong?
Bug#796113: lxrandr: Resolution reported by lxrandr is inconsistent with machine capability.
Thank you for reporting this. If this problem still exists then quote output of 'xrandr' command here, please, for further investigation.
Bug#793818: Pcmanfm crash sometimes at the end of file(s) copy
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, libfm-gtk-dbg.
Bug#792559: pcmanfm: deleted files replace copied files of the same name
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 file could come back from nowhere, it is nearly impossible to undelete files on the ext3/4 file systems.
Bug#810631: critical: cause found to lxdm pasword fail problem
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 found yet, there is no reason to release any package updates with patches that don't work. Thank you very much.
Bug#809328: lxde-common: package should not depend on a specific window manager
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 but is an x-session package for openbox session, it should
have been named openbox-lxde-session in the first place but due to some
historical reasons is named lxde-common. Actually it even would not work
without openbox until user makes some changes but to make those changes
user should start openbox session first. It's why the lxde-common package
depends on openbox.
To make it possible to use another WM with LXDE the hard dependency on
lxde-common should be removed from lxde metapackage and replaced with
lxde-common|x-session-manager then you can create another session file
instead of /usr/share/xsessions/LXDE.desktop (which uses executables
/usr/bin/openbox-lxde and /usr/bin/startlxde from lxde-common package).
I mean just clone lxde-common files set, modify & rename these mentioned
files and you're done for another WM.
Since said hard dependency on lxde-common in regards of this report is a
bug of lxde-metapackages, I reassign the report to that package.
Although if you would like to reuse /etc/xdg/{lxpanel,pcmanfm}/ files and
wallpapers from lxde-common package then let us know, please, it is still
possible to split said package to create an openbox-lxde-session with all
openbox/lxsession related files in it and leave independent files alone.
Bug#805031: Annual ping for Andriy Grytsenko
Package: debian-maintainers Severity: normal Annual ping it is. Thanks! signature.asc Description: Digital signature
Bug#801319: Icon size problem
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.
Bug#790740: Package Openbox version 3.6.1, please.
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 becomes irrelevant as it creates libobrender31 and libobt4 while in upstream version 3.6.1 those ABI numbers (i.e. the soversion) become as 32 and 2 respectively so should be libobrender32 and libobt2. Please, fix that and make packages to match upstream, otherwise it will be a whole mess. Just package 3.6.1, please, and remove patch which changes soversion, that's all. Thank you very much. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754229: lxpanel: sound volume plugin does not start alsamixer
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
Bug#770763: libfm-data: Cut-paste copies the file but does not delete the source
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 were back in version 1.1.0 so if your libfm was the one from wheezy then that might happen but if your one was from jessie/sid then nothing was changed since your report time and all this looks suspicious. In any case this is resolved, sorry for wasting your time. I really hope it is, and would not happen anymore. With best regards, Andriy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780758: pcmanfm: hangs while copying files
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. Trouble? Contact listmas...@lists.debian.org
