Bug#731255: synergy: Jessie synergyc (1.4.12-3) cannot connect to Wheezy synergys (1.3.8-2)
On 03/31/2014 07:29 AM, Axel Beckert wrote: From my point of view it does not render the package generally unusable, just for the case where the server is an significantly older version. Then again, the case with Jessie and Wheezy is likely no seldom one, so I think if there's a chance to fix this issue, it should be fixed before the freeze for Jessie. I checked the upstream bug tracker and found only one entry similar to this issue. Unfortunately it was tagged invalid: http://synergy-foss.org/spit/issues/details/3562/ My plan to fix this bug is to make a version of synergy 1.4 available in wheezy-backports. As another workaround, 1.3 synergyc can talk to 1.4 synergys, but this would require switching the mouse and keyboard to a different system. I suspect this will become a problem more and more with other distros as well; upstream considers 1.3 to be obsolete, and other distros are updating synergy as well. So, I consider the existence of a backport for wheezy to be the best resolution we can hope for. signature.asc Description: OpenPGP digital signature
Bug#714634: [lsb-discuss] Bug#714634: Clarification of general LSB requirements
On 07/11/2013 02:22 AM, Didier 'OdyX' Raboud wrote: Le mercredi, 10 juillet 2013 20.20:21, Steve Langasek a écrit : Well, I think that package description is silly in its lawyeresque weaselness. The raison d'être of the package is to provide an LSB-compliant layer, which is what it means to support installing and running LSB packages. I don't see any reason the package description should have this long disclaimer about the possibility of bugs in the implementation. The core of what this phrasing [0] conveys is this package doesn't imply that Debian is LSB-compliant but is our best-effort at it; I would welcome any patch in that direction, if possible acked by Jeff/LSB. We've always considered the lsb package to be a functional component, and not to indicate any kind of implied legal requirement or promise beyond the usual concern an upstream has that a package be as bug-free and correct as possible. So feel free to do what you wish regarding the disclaimer, including dropping it entirely. (Though I will defer to someone else to actually write the patch given my own conflict of interest.) -- Jeff Licquia The Linux Foundation +1 (317) 915-7441 licq...@linuxfoundation.org Linux Foundation Events Schedule: events.linuxfoundation.org Linux Foundation Training Schedule: training.linuxfoundation.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714634: lsb-core: Remove lsb-invalid-mta as a dependency of lsb-core; require an actual MTA instead
On 07/07/2013 04:09 AM, Aaron Sowry wrote: Ubuntu has another long-standing (at least 11.10 - 13.04) LSB bug[1] which makes install_initd fail. This means that it's not possible to install services on Ubuntu as per the LSB spec. It's been fixed, I see. Pretend you're developing software to be run on LSB-compliant systems - let's say a program which sends administrative emails to a specified address whenever certain system states are encountered. In this case, Ubuntu is an example of a system on which the software cannot be installed, cannot perform it's function even when installed by other (non-LSB) means, but does not violate the LSB in either of these regards. I'm sorry, but if this is the case (and I certainly hope it isn't) then, at least from a developer's perspective, the LSB is an irrelevant specification. Someone once said Politics is the art of the possible. So are standards in the free software world. That's life. I suspect, though, that you're undervaluing the 99% of the spec that doesn't have to do with sendmail. BTW, if you feel strongly about this, I'd encourage you to file the appropriate bugs and have this discussion over there. No one here needs convincing, I think, that lsb-invalid-mta is a bad idea. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714634: lsb-core: Remove lsb-invalid-mta as a dependency of lsb-core; require an actual MTA instead
On 07/06/2013 08:39 AM, Aaron Sowry wrote: Anyway, we could sit here and discuss the semantics of the LSB specification all week, however I'm of the firm belief that the authors of the specification did not include a sendmail command just because it might be fun to have a command called sendmail which does nothing; rather, it is intended to be a functional interface through which applications can send email. I've CC'd Jeff Licquia on this mail, hopefully he can chime in with his thoughts. hat type=lsb-spec-author The LSB is, first and foremost, about compatibility for apps. If apps expect something to be there, and for it to act in a certain way, then that's our top priority. Everything else is secondary. I don't like lsb-invalid-mta, but as mentioned in the thread leading up to this bug, we agreed on it with the Ubuntu folks because it at least preserves app expectations. It was the preferred alternative to Ubuntu's planned move: just get rid of the MTA requirement entirely, and thus break compatibility. To the extent that lsb-invalid-mta preserves app compatibility, therefore, it's OK by us; not ideal, or even recommended, but a valid option. Apps expect sendmail to be there, and they are expected to be able to handle errors sendmail might produce (especially with something as potentially flaky as email). The lsb-invalid-mta package satisfies those criteria. Whether Debian decides that they want to support MTA-less configurations using lsb-invalid-mta is up to Debian. /hat hat type=debian-developer Since we install an MTA by default, I expect that there are very few installations of lsb-invalid-mta (perhaps none). So I don't think getting rid of it for jessie is necessarily out of the question. It certainly doesn't serve the same purpose in Debian as it does in Ubuntu. I will say that I enthusiastically support this part of the change, and would advocate that it happen: That's probably where I'd be open to changes: making lsb-core depend on default-mta | mail-transport-agent on Debian (and still lsb-invalid- mta | mail-transport-agent on Ubuntu) might be a worthwhile change. I'd even support this as a bug-fix for wheezy, not just in jessie. That said, we released Wheezy with both lsb-invalid-mta and the dependency on it from lsb-core so we would need to respect the choice of admins that actually _want_ a non-working sendmail in their lsb dependencies across upgrades. This isn't really an administrator's problem, it's a problem for developers of applications designed to be run on LSB-compliant systems. I can't think of any reason an administrator would ever want a non-functional sendmail command on their system. I believe this ship has sailed for wheezy, certainly. But for jessie, I tend to agree with Aaron. Too much stuff on a Debian system assumes a working MTA to make lsb-invalid-mta an interesting choice for Debian users. So dropping it wouldn't necessarily be bad for our users. That said, I'm not dogmatic about it. If we want to make the choice available, cool. Just as long as the choice isn't the default (i.e. Depends: default-mta | mail-transport-agent). /hat -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710157: potential patch for essex
https://bugs.launchpad.net/nova/+bug/1177830/comments/21 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691422: init-functions: order of arguments is not context-free
On 11/04/2012 12:02 PM, Arno Töll wrote:
That said, I can live with you not wanting to fix it, but please give an
error message at least, if you got an unexpected keyword argument after
a positional if you do not intend to support it:
I've attached a patch which will add some sanity checking to pidofproc's
command-line argument parsing. With this patch, pidofproc will fail if
it finds more than one non-dashed argument under any circumstances.
I've also created a simple test.
I'll leave it up to Didier as to whether to apply it or just leave the
bug wontfix.
From 5772eb3bfb45ea3de2f0e06bb4f3dd3eeafccdf6 Mon Sep 17 00:00:00 2001
From: Jeff Licquia licq...@debian.org
Date: Sat, 10 Nov 2012 10:26:30 -0500
Subject: [PATCH] Sanity-check pidofproc parameters per Debian bug 691422.
---
init-functions |4
test/lsb-test.sh | 28
2 files changed, 32 insertions(+)
diff --git a/init-functions b/init-functions
index 5cb28dc..046dfb9 100644
--- a/init-functions
+++ b/init-functions
@@ -75,6 +75,10 @@ pidofproc () {
esac
done
shift $(($OPTIND - 1))
+if [ $# -ne 1 ]; then
+echo $0: invalid arguments 2
+return 4
+fi
base=${1##*/}
if [ ! $specified ]; then
diff --git a/test/lsb-test.sh b/test/lsb-test.sh
index 1168a62..2db3457 100644
--- a/test/lsb-test.sh
+++ b/test/lsb-test.sh
@@ -8,3 +8,31 @@ log_success_msg This should succeed
log_failure_msg This fails miserably
echo OK!
+
+# Test pidofproc sanity checking.
+
+echo Testing pidofproc command line checks
+
+echo Simple check, no options:
+pidofproc nonexistent
+RETVAL=$?
+if [ $RETVAL -ne 3 ]; then
+echo Unexpected return value $RETVAL
+fi
+
+echo With -p option:
+pidofproc -p /var/run/nonexist.pid nonexistent
+RETVAL=$?
+if [ $RETVAL -ne 3 ]; then
+echo Unexpected return value $RETVAL
+fi
+
+echo With -p option, but in wrong place:
+pidofproc nonexistent -p /var/run/nonexist.pid
+RETVAL=$?
+if [ $RETVAL -ne 4 ]; then
+echo Unexpected return value $RETVAL
+fi
+
+echo OK!
+
--
1.7.10.4
Bug#691422: init-functions: order of arguments is not context-free
On 11/10/2012 11:16 AM, Didier 'OdyX' Raboud wrote: Now I am slightly relunctant to add it to wheezy, not sure it would warrant an unblock (although [0] shows no forecoming problem). This fix could potentially break existing initscripts (admittedly relying on that broken behaviour), so I have uploaded to experimental for now. Opinions ? I think that's prudent. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692791: [Pkg-cups-devel] Bug#692791: members of lpadmin can read every file on server via cups
Control: found -1 1.4.4-7+squeeze1 On 11/10/2012 06:48 AM, Didier 'OdyX' Raboud wrote: I have successfully used your exploit script on the Sid version, tagging as found there. Just to complete the picture, I tried the exploit on squeeze, and it works there too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692791: [Pkg-cups-devel] Bug#692791: Bug#692791: members of lpadmin can read every file on server via cups
[Re-adding security team to CC.]
On 11/10/2012 07:44 AM, Martin Pitt wrote:
Didier 'OdyX' Raboud [2012-11-10 12:48 +0100]:
* Have cupsd run as lp user
We had done that in Debian for several years for security reasons. We
had a huge patch to make most of cups work as user lp, but at some
point I gave up: it caused too many bugs, didn't work with a lot of
third-party drivers, and broke with every new upstream release.
Upstream has never bought into the idea of running the main server as
an unprivileged system user unfortunately.
So this is possible in principle, but will mean a huge maintenance
overhead.
Maybe this situation will help make the case. :-)
* Forbid any changes to the config file from the webinterface
That would drop a huge piece of functionality.
CUPS allows changes to the config file in two ways: changing a small
subset of settings in a way that's checked server-side, and editing
cupsd.conf in a browser by downloading the file, and then uploading the
edited version post-edit. The latter functionality is what's being
exploited here, and it strikes me as far more dangerous than the former.
I've attached a proposed dpatch which disables just cupsd.conf editing.
It's against the squeeze version, but applies fairly cleanly to the
wheezy version. I've tested it against the exploit script, which no
longer dumps /etc/shadow to stdout with the patch applied.
Best of all, this patch doesn't completely disable configuring the
server from a browser, just the wholesale cupsd.conf edit.
I'm not sure this is upstream-worthy, but it might do until upstream
gets a better fix written.
* Another idea ?
cupsd could temporarily drop privileges to lp when reading log files;
with that you are restricted to reading world-readable files as well
as cups' own files, which should be fine?
I suspect this fix would end up in a game of whack-a-mole, as we find
interesting settings which trick cupsd into doing nefarious things.
#! /bin/sh /usr/share/dpatch/dpatch-run
## bug-692791.dpatch by Jeff Licquia licq...@debian.org
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Disable editing of cupsd.conf via web interface.
@DPATCH@
diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch'
'--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' cups-1.4.4~/cgi-bin/admin.c
cups-1.4.4/cgi-bin/admin.c
--- cups-1.4.4~/cgi-bin/admin.c 2012-11-10 16:12:08.0 -0500
+++ cups-1.4.4/cgi-bin/admin.c 2012-11-10 16:20:37.0 -0500
@@ -1881,6 +1881,24 @@
else if (cgiGetVariable(SAVECHANGES) cgiGetVariable(CUPSDCONF))
{
/*
+* XXX: Disable web editing of config file for security reasons.
+* This is a quick-n-dirty hack to just turn the functionality
+* off temporarily until upstream/someone has time to fix the
+* problem properly. See Debian bug 692791 for details.
+*/
+
+cgiStartHTML(cgiText(_(Edit Configuration File)));
+cgiSetVariable(MESSAGE, cgiText(_(Unable to upload cupsd.conf file:)));
+cgiSetVariable(ERROR, strerror(EPERM));
+cgiCopyTemplateLang(error.tmpl);
+cgiEndHTML();
+return;
+
+ /*
+* End of quick security hack. Original implementation follows.
+*/
+
+ /*
* Save hand-edited config file...
*/
Bug#681598: Anything else required?
On 11/07/2012 06:21 PM, Nikolaus Rath wrote: I'll wait until it happens again and you can take a look. Can you send me your ssh key? You don't need root access, right? We'll have to coordinate a time, the machine doesn't have a fixed ip. Nope, shouldn't need root. I'll send the ssh key out-of-band. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681598: Anything else required?
On 10/22/2012 09:24 AM, Nikolaus Rath wrote: This problem continues to occur regularly. Is there something else I can do to help? I took another look to see if I could figure out what might be happening, and came up empty. About the only possibility left would be to debug the Python code when get_distro_information() fails to return a CODENAME, and figure out why. If you're up for that, definitely send along any information you find. If not, you could let me into your box when it's happening, and I could do the debugging. Of course, you'd have to trust that I wouldn't do anything bad while working on your system. Another idea that comes to mind: It occurs to me that some of your repos seem to be defined in sources.list, and some via files in sources.list.d. If you changed things such that all of your repos were in sources.list (i.e. sources.list.d is empty), and if the problem then went away, that might indicate a bug in apt. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691118: htmldoc: problem with some site with windows server
On 10/21/2012 12:26 PM, patrick295767 wrote: If you try to get it to an html: wget -k http://www.energetics.eu/contact and then : htmldoc --links --numbered --landscape --continuous file.html -f myfileaspdf.pdf then you will see that ^M is giving a error. It crashes all the time. maybe a awk or sed before? what could you propose? A fast reply would be expended if possible. I was unable to reproduce the crash using your example, on either squeeze or wheezy. Do you have a site that crashes consistently? Or, perhaps, a particular HTML file which causes htmldoc to crash? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691119: bug: crashing on a simple pages
On 10/21/2012 12:28 PM, patrick295767 wrote: I did try to convert a html to pdf. Is this bug related to the previous bug you filed? If not, do you have the HTML which caused this error? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691422: init-functions: order of arguments is not context-free
On 10/25/2012 09:53 AM, Arno Töll wrote: As spotted in #691365, it turns out that the pidofproc function provided in /lib/lsb/init-functions is not context free. Calling pidofproc $DAEMON -p $PIDFILE in contrast to pidofproc -p $PIDFILE $DAEMON yields different results if the file in $PIDFILE does not exist. This yields to a non-context-freeness which is probably not what the user calling this function expects. The LSB spec for pidofproc is here: https://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptfunc.html It defines the command line arguments for pidofproc as your second form, with the -p parameter first. This is in line with a number of other commands which require that dashed parameters come before bare arguments, and is also consistent with the implementation of getopt(1), getopt(3), and the getopts shell function in POSIX (the latter of which our script relies on for argument parsing). Given this, I'm inclined to mark this bug wontfix. But I'm willing to be convinced otherwise. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504654: test fix in recent synergy?
On 08/08/2012 08:24 AM, Nathan Schulte wrote: I wasn't subscribed to this bug report, so I didn't see the updates. I no longer have this specific setup, so I cannot verify that I still receive the error. I have a setup available at work that I can try to reproduce this error, and if so, I will test with the newer releases of synergy from experimental, etc. I may even take the time to install Debian Lenny if I can't reproduce it with Squeeze, for the sake of closing the bug report. If not, I would mark it unreproducible and/or call it fixed and/or close the bug. Have you had a chance to try this out? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681598: update
On 08/11/2012 09:49 PM, Nikolaus Rath wrote: Here we go: I've played with this a little, using the results from the dir listings (which don't look odd to me). From what I can tell, the ultimate cause of the failure is when apt decides to invalidate all repositories and apt-cache policy only reports the local dpkg database as a valid repo. At that point, the code uses different logic to try and figure out the distro information, which doesn't include the CODENAME. So there are a number of ways to fix the problem: - When unattended-upgrades decides to stop working, I would bet that apt-cache policy only returns the 100 /var/lib/dpkg/status package file. Figure out why that's happening and make it not happen, and I'm sure lsb_release would fall into line. - Assuming there's a good reason for apt-cache policy to do this, we might be able to do better at guessing the release. We read /etc/debian_version, and understand versions like wheezy/sid (its current contents as of today). We parse off the /sid and keep hold of the prefix (so long as it's not testing), but if the apt check fails, we end up just discarding it. We might be able to fall back to something like parsing sources.list to determine if we're running sid or not, and based on that, set the CODENAME. - Of course, another way to fix this would be for unattended-upgrades to be a little more robust about a missing CODENAME; maybe it could use some fallback, or a different value from the info returned by get_distro_information(), or something. Anyone want to weigh in on which is the best solution? (or point out where I'm totally off base) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681598: Same problem
On 08/04/2012 11:26 AM, Nikolaus Rath wrote: Problem happened again today. sources.list hasn't been touched, but suddenly release detection fails: [...] Based on previous experiments, it will now work for a while and then suddenly start failing again. Next time it does, could you send on a directory listing in /var/lib/apt/lists? (Before running the update; i.e. while get_distro_information() still fails.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554967: Still a problem with newer versions?
Can you test that synergy still has this problem with newer versions? Unstable has 1.3.8-2, and experimental has 1.4.8-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670382: Update to 1.3.x may also fix this
I've uploaded 1.3.8-2 to unstable, which contains a segfault fix which may also solve this problem. If anyone is seeing this issue, could you please test with the unstable version? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664217: synergy: multiple crashes fixed in 1.3.8-1
I've uploaded 1.3.8-2, with a segfault fix that seems to have fixed a number of reported problems (both in and out of Debian). Can you test with that version, and let me know if you still see the problem? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658366: synergy: segfault fix in unstable
I've uploaded 1.3.8-2 of synergy to unstable, which fixes at least one segfault problem. It also seems to have fixed problems in a number of places, from upstream reports. Can you test with that version and see if it has fixed your problem with the clipboard and NX? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504654: test fix in recent synergy?
I'm fairly certain this fix has made it into upstream. Could you try with either 1.3.8-2 from unstable or the 1.4.x version in experimental? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681598: /usr/share/pyshared/lsb_release.py: release detection fails with http.debian.net redirector in sources.list
On 07/14/2012 11:45 AM, Nikolaus Rath wrote:
When using the http.debian.net redirector, though
| deb-src http://http.debian.net/debian/ testing main contrib non-free
| deb http://http.debian.net/debian/ testing main contrib non-free
the detection fails:
Cannot duplicate on my system:
jeff@virtpc-wheezy:~$ python
Python 2.7.3rc2 (default, Apr 22 2012, 22:30:17)
[GCC 4.6.3] on linux2
Type help, copyright, credits or license for more information.
import lsb_release
lsb_release.get_distro_information()
{'DESCRIPTION': u'Debian GNU/Linux testing (wheezy)', 'RELEASE':
u'testing', 'CODENAME': 'wheezy', 'OS': 'GNU/Linux', 'ID': 'Debian'}
jeff@virtpc-wheezy:~$ cat /etc/apt/sources.list
deb http://http.debian.net/debian/ testing main contrib non-free
deb-src http://http.debian.net/debian/ testing main contrib non-free
#deb http://security.debian.org/ testing/updates main contrib non-free
#deb-src http://security.debian.org/ testing/updates main contrib non-free
#deb http://ftp.uwsg.indiana.edu/linux/debian/ wheezy-updates main
contrib non-free
#deb-src http://ftp.uwsg.indiana.edu/linux/debian/ wheezy-updates main
contrib non-free
jeff@virtpc-wheezy:~$
One potential issue I did find: lsb_release did get quite confused when
I changed sources.list but did not apt-get update afterwards. Can you
check that and see if apt-get update makes a difference?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513161: Seems to be solved in the newer version
On 06/05/2012 06:47 AM, ilya brik wrote: See: http://synergy-foss.org/tracker/issues/3066 I've downloaded the last .deb (1.4.8) from Synergy's site and the issue does not occur anymore (2 PCs with an updated Debian wheezy installed) It's not 100% clear that the issue you mention is related; however, I've uploaded 1.3.8-2 just now, with that fix included. Could someone having this issue try the new synergy when it becomes available, and see if it fixes the image problem? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680592: lsb-base: reporting errors and diagnostics in init scripts
On 07/07/2012 01:21 AM, Russ Allbery wrote: To take an example, the openafs-client init script. It loads a kernel module and then starts a daemon. It can't load the kernel module unless the module is present; if it's not present, it does: cat EOF 2 AFS module $MODULEDIR/$LIBAFS does not exist. Not starting AFS. Please consider building kernel modules using instructions in /usr/share/doc/openafs-client/README.modules EOF I'm not sure how I should do this using the output functions provided by lsb-base. Converting this to a one-line message feels like it would lose information. It does feel that way. OTOH, on a starting system, the information you printed to the console could scroll off-screen and be lost. With the lsb-base function, a hook could capture and log that information. So there's a tradeoff here, I think. Would it be acceptable to do something like this: log_action_msg Loading AFS module $MODULEDIR/$LIBAFS load_afs_module if afs_module_load_failed; then log_failure_msg Module not found; see \ /usr/share/doc/openafs-client/README.modules fi (with additional info like the message you currently write put into the docs) Related, using the LSB functions seems to result in hard-to-read messages when the daemon that's being started produces an error. This is because the format necessarily involves printing out the start of a line, then starting a daemon and printing out the end of the line, reporting the status. The traditional Debian output doesn't provide much better tools, but with the traditional output format I can at least just print out the full startup message first and then start the daemon, since the exit status isn't part of the output format. I've seen that happen with other scripts. I agree that it probably involves some arcane shell-fu, but I would think that lsb-base should do the arcane shell-fu for you. Something like this: log_begin_msg Starting AFS services: afsd start_daemon /sbin/afsd || log_start_failure log_success_msg . Success could look something like this: [ok] Starting AFS services: afsd. And failure: [error] Starting AFS services: afsd afsd: too much mimsy in the borogroves Where start_daemon would do the funky output capture in a way that log_start_failure would then be able to use. (Apologies if I haven't represented Didier's excellent fancy-output stuff right.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675051: synergy: keyboard autorepeat is turned off sporadically
On 05/29/2012 11:04 AM, Mason Loring Bliss wrote: With the synergy client running, keyboard autorepeat is sporadically and unpredictably disabled. It can be re-enabled with 'xset r', but this is at best a band-aid. Hi, Mason; sorry for the late reply. Can you try downloading the wheezy version of synergy (1.3.8-1) and see if that works? It should install on squeeze OK. Let me know if you have trouble getting it installed, and I'll try to help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625502: Inquiry re: adopting qt3
I'd like to ask to adopt Qt 3, entirely for the sake of the LSB. The LSB is working on removing Qt 3, but that effort won't be ready in time for wheezy, and I'd like for full LSB support to remain possible in Debian. What are your thoughts? I don't think this would take away from the release goal of ridding Qt 3 dependencies from Debian; it would be good, I think, to release with only LSB depending on Qt 3. I understand it's a C++ package of some complexity, and that I'd be responsible for analyzing security fixes, bugs, etc. on my own without upstream support from TrollTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660156: Fwd: Re: synergy and gedit bug
Original Message Subject: Re: synergy and gedit bug Date: Mon, 7 May 2012 14:37:25 +0200 From: Bzzz lazyvi...@gmx.com Organization: Anyone, anywhere BUT in banana demokratik republik of france To: Jeff Licquia licq...@debian.org On Sun, 06 May 2012 23:19:47 -0400 Jeff Licquia licq...@debian.org wrote: Hi! I'm the maintainer of synergy for Debian. The bug you filed against gedit was forwarded to me to look at. Hi Jeff, Have you still been having the problem? Yep, in fact it seems linked to GTK2 because it happens in the 2 applications I use the most: gedit and gcstars If so, which versions of synergy are you running client-side and server-side? If I read the bug correctly, gedit is dying on the server side; what system is running on the client? Both are Debian Linux, svr is sid, client is squeeze+backports, svr ver: 1.3.8-1 cli ver: 1.3.1-5 There's an experimental version of synergy available in the experimental package repository. Assuming you're still having the problem, would you be willing to try that and see if the problem resolves itself there? Ok, I installed 1.4.8-1 from experimental and as first sight it seems not to fail anymore; now, as synergy's death was pretty much random I need to re-test it thoroughly - It will take some times as I'm leaving now. Lets say if still have this problem I'll go back to you before the next week end and if it's alright not at all. Thanks for your time Jeff and best regards. Jean-Yves -- Lao Tseu say: Man that scratch his butt at night awakes with stinking fingers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#507047: message to original filer bounced
My message to Ignacio Díez Arias bounced; the account apparently no longer exists. I will close shortly if there is no new activity on the bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671730: /etc/lsb-base is there. Do mv /etc/lsb-base-logging.sh /etc/lsb-base/logging.sh
On 05/06/2012 09:17 AM, Regid Ichira wrote: I think it is more obvious, and less cluttering /etc: I'm not sure how replacing a file with a directory creates less clutter in /etc. It would be different if there were multiple lsb-base-* files we could move in there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671730: /etc/lsb-base is there. Do mv /etc/lsb-base-logging.sh /etc/lsb-base/logging.sh
retitle 671730 /etc/lsb-base is unused; consider removing it severity 671730 minor tags 671730 - patch thanks On 05/06/2012 11:06 AM, Regid Ichira wrote: And, in my case, the directory is empty. There's the problem; we create the directory, but don't use it. Since /etc/lsb-base-logging.sh has been a well-known path since at least 2005, there should be a clear and compelling reason to move it and incur all the hassle of checking for old versions, moving them, etc. I've looked through the package, and can't find any place where the directory is used for anything. So I'd vote that we just drop the directory. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671730: /etc/lsb-base is there. Do mv /etc/lsb-base-logging.sh /etc/lsb-base/logging.sh
On 05/06/2012 05:23 PM, Adrian Fita wrote: Hi. Please excuse my tresspassing into this discussion, but wouldn't putting lsb-base configuration vars in a file in the /etc/default directory (something like /etc/default/lsb-base) be more in accordance with the Debian Policy and FHM recommendations? This would mean dropping /etc/lsb-base-logging.sh and altering the /lib/lsb/init-functions to account for this change. This justification works better for creating new files than for moving existing files, as I mentioned earlier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670382: Fwd: Re: Bug#670382: synergys segfaults when losing connection with client
Original Message Subject: Re: Bug#670382: synergys segfaults when losing connection with client Date: Fri, 27 Apr 2012 06:38:44 + From: David, Erwan eda...@nds.com To: Jeff Licquia licq...@debian.org The client is running Fedora 14, synergyc 1.3.7 -- Erwan DAVID IT Unix/Network, France tel: +33 155 006 116 mob: +33 622 174 037 From: Jeff Licquia licq...@debian.orgmailto:licq...@debian.org Sent: Wed, 25 Apr 2012 09:49:57 -0400 To: Erwan David eda...@nds.commailto:eda...@nds.com, 670...@bugs.debian.orgmailto:670...@bugs.debian.org Subject: Re: Bug#670382: synergys segfaults when losing connection with client On 04/23/2012 08:22 AM, Erwan David wrote: Each time the connection between client and server is lost (eg client is disconnected from network), server crashes with error A few questions: - I assume the info from reportbug is for the server; what's the client running? - I've uploaded 1.4.8 to experimental (still considered beta upstream). Can you try that, and report back if it works any better for you? This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. An NDS Group Limited company. www.nds.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#382063: Are you still having problems with synergy?
I know it's been a long time ago, but you once filed a bug with Debian reporting problems with synergy losing its connection occasionally. You can refresh your memory here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382063 I was wondering: are you still having the problem? If so, have there been any changes in the intervening time which might have mitigated the problem? I realize that a lot has probably changed. If you've completely moved on, just let me know, and I'll close the bug report for you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505573: Still having problems with 32- and 64-bit synergy?
I'm going through old bugs on synergy's Debian package, and noted that there never was a conclusion to the 32- and 64-bit issues we were discussion in this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505573 I realize that your situation has probably changed since then, but I wanted to make sure the problem was solved or that you had moved on before just closing the bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#507047: Are you still having problems with synergy on Debian?
I'm going through some old bugs, and noticed that your bug dropped through the cracks. It was a bug in synergy, where full-screen applications on the server caused synergy to act strange. Here's the bug report, in case you need to refresh your memory: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507047 Are you still running in a similar configuration? If so, has the release of squeeze made a difference? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534239: 1.3.8 segfaults too :-(
On 04/04/2012 10:48 AM, Javier Barroso wrote: Finally synergyc 1.3.8 in squeeze got segfault (not significative trace with -d DEBUG (and now I haven't access to exact log / strace trace)). Now I'm trying synergy 1.4.7 and seems like it is working fine, but really will have to wait two or three days and see if it get again a segfault ... Any luck? I've uploaded synergy 1.4.8 recently; if you've experienced any crashes with 1.4.7, you could try that. I'm not aware of any reason why 1.4.8 would improve on 1.4.7, but I know that upstream continues to work on issues like these. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660156: synergy and gedit bug
Hi! I'm the maintainer of synergy for Debian. The bug you filed against gedit was forwarded to me to look at. Have you still been having the problem? If so, which versions of synergy are you running client-side and server-side? If I read the bug correctly, gedit is dying on the server side; what system is running on the client? There's an experimental version of synergy available in the experimental package repository. Assuming you're still having the problem, would you be willing to try that and see if the problem resolves itself there? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670990: setup/uninst GUI setup programs not built on all archs
Package: epm Version: 4.2-6 Severity: normal The setup and uninst GUI programs used by epm to build wizard-like installers are limited to building on i386 and amd64 only. This is an artificial limitation, and is only needed because of the inconsistent state of libfltk and its dependencies with regards to building with -fPIC. On most architectures, libfltk can be linked statically, but on some (kfreebsd-amd64 and mips, as of 4.2-5), the trick to linking it statically is still a mystery. Static linking is essential because the setup and uninst programs are intended to be copied to other systems and run. Runtime dependencies must be as loose as they possibly can be. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670382: synergys segfaults when losing connection with client
On 04/23/2012 08:22 AM, Erwan David wrote: Each time the connection between client and server is lost (eg client is disconnected from network), server crashes with error A few questions: - I assume the info from reportbug is for the server; what's the client running? - I've uploaded 1.4.8 to experimental (still considered beta upstream). Can you try that, and report back if it works any better for you? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667930: epm: CPPFLAGS hardening flags missing
severity 667930 normal forwarded 667930 http://www.epmhome.org/str.php?L38+P0+S-2+C0+I0+E0+M10+Q thanks I've forwarded part of the patch upstream, as indicated above; it's the part where CPPFLAGS is not respected. I'm not particularly interested in the patch to doc/Makefile.in, since the resulting binary is a build artifact and not shipped in the final package. I'm also not inclined to enable more hardening flags without testing their impact on setup, which is intended to be bundled with a built application to provide a Windows-style install GUI that runs on all Linux distributions. When my testing is done, I'll decide whether the bindnow feature is appropriate to enable. (Yes, I'm aware that I could be in a pickle if PIE causes portability problems; I'll cross that bridge when I come to it.) I'm setting the severity to normal because epm doesn't look to be in the first line of important packages to harden; it hasn't had a DSA recently, is not priority important, is not a daemon, and is not an interpreter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630411: #630411: libc6 should define /lib/ld-lsb-x86-64.so.3 on AMD64
On 03/02/2012 12:20 PM, Didier Raboud wrote: François Petitjean wrote: In other words, on small (embedded?) systems it would be useful to be able to run some LSB binaries without pulling in the entire LSB core. Does that sound like something worth supporting to you? Perhaps we just need some documentation somewhere like the Debian Reference or glibc's README.Debian to explain how people can create the symlink themselves. A few points of interest: - the requirements for the dynamic linker symlink are documented in the LSB specification (see refspecs.linuxbase.org for those) - upstream LSB will be working on a solution for pulling in parts of the LSB as part of the 5.0 development effort -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604360: Preparations for the removal of the KDE3 and Qt3 libraries
On 02/23/2012 09:31 AM, Didier 'OdyX' Raboud wrote: Given that LSB has deprecated the use of Qt3 libraries since its 3.2 version, I propose to demote the relationship on libqt3-mt from Depends to Recommends. This would mean that Qt3 would still be installed by lsb-desktop in default installations (where apt recommends are enabled) but at the same time make the LSB support in Debian future-proof and allow seamless removal of Qt3 when its time will have come. Opinions ? I would definitely not go that far, at least not yet. Qt 3 is deprecated, yes, but definitely still required for full LSB support. LSB 5.0 (currently in development) will drop Qt 3. At that point, the dependency can be dropped entirely. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616131: ITA: LSB package maintenance in Debian
On 02/16/2012 12:12 PM, Didier 'OdyX' Raboud wrote: I just noticed the worrying state of the LSB package in Debian: * Still in version 3.2 (released in January 2008) while 4.1 is out since a year (coincidently today); * RFA'd - #616131; * behind Ubuntu since at least Karmic (9.10) which already had 4.0. I would like to get the LSB package up to date before Wheezy's freeze, planned for June. For now, I just filled a Git repository [0] with all past Debian (at least those available on snapshot.debian.org) and Ubuntu releases (on the master-ubuntu branch). I think I mostly got authors and dates straight, but it was not fun. Now my intentions (despite limited available time) are: 1) put it under explicit team maintenance; Maintainer: debian-...@lists.debian.org ? [1] Uploaders: Myself + Chris ? 2) push the repository to collab-maint; 3) merge most of the current lsb (4.0) Ubuntu package into it, including dpkg-vendor magic to have both distros handled. 4) if needed, update it to 4.1; 5) upload a new version to experimental as soon as possible; 6) triage and if possible address all Debian bugs; 7) update the packaging to modern practices (short dh, etc) So, is anybody willing to join the fun ? Steve, Colin, Matthias: as the 3 last persons that uploaded the Ubuntu lsb package: would you be interested in merging the effort and (once done) try maintaining it in Debian first ? FWIW, this has been something the LSB has been discussing upstream, and we're willing to help with the work. If the project is willing, I'd appreciate having commit access and being an uploader. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658366: synergy: when clipboard include text copied from NX client, cursor move from server to client causes segfault
The log file didn't appear to make it; I have just a blank file, as does the Debian BTS. I recently uploaded synergy 1.4.5-1 to experimental. Does using that help? (possibly with 1.4.x on the Mac as well) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652455: doclifter does not support tables
On 12/17/2011 07:41 AM, Mathieu Malaterre wrote: it would be nice if doclifter would support tables, for openslide-show-properties.1 it converts: Can you try the version in testing currently, and see if it works better? (That version is 2.7-1.) If it is not better, could you send a sample man page (or point to one available in Debian)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653257: Synergy bug 3063
Package: synergy Version: 1.3.8-1 On 12/25/2011 03:23 PM, Dr. David Alan Gilbert wrote: Hi, I hit Synergy's bug 3063 - a crash on cross-machine paste. I've pulled in one of the patches that fix it into an ubuntu bzr branch and thought I should tell you; see: https://code.launchpad.net/~ubuntu-treblig/ubuntu/precise/synergy/synergy-lp908578fix-ups3063 It's probably worth pulling that in, since it's a regression from old synergy. I'm going to record this in Debian's bug tracker, since it's most likely in Debian's build of the package as well as Ubuntu's, and I'll add the upstream reference in a sec. I'm perfectly happy with pulling in a patch already accepted upstream, but I'm not so thrilled if there's a dispute about the patch. Such disputes should be resolved upstream. Right now, if forced, I'd pick the patch from bug 3063 (the one upstream pulled in). But I'd much rather see if upstream decides to do anything different based on that feedback. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649208: synergy: 'synergys doesn't work with gnome3'
On 11/29/2011 01:26 PM, Igor Soares wrote: Here it is. It's a simple 2 PCs side by side. Thanks for that. In the future, could you reply all so the information is included in the bug report, too? That way, other people can look at the bug and check things out on their own. I've reproduced the bug, and also confirmed that it's the same bug as bug 2958 upstream: http://synergy-foss.org/tracker/issues/2958 The behavior is the same for me; I can even get synergy to work by moving a window across the border edge, or running an app full-screen. That bug is fixed, and there are patches in the bug report, so I anticipate this won't be difficult to fix. Unfortunately, the patch is to upstream's beta 1.4.x series, but I don't have a problem applying it to the 1.3.x series (assuming I can figure out the differences). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649208: synergy: 'synergys doesn't work with gnome3'
On 11/18/2011 04:06 PM, Igor Bruno Pereira Soares wrote: 'synergys' is not working with gnome3, using gnome-shell or the fallback. The mouse pointer simply don't go from one screen to another through the screen edge. It works fine with other window managers (I tried KDE,Fluxbox,LXDE). If I change the order, using another PC as the server, 'synergyc' works fine too. The other PC is with Gentoo linux and LXDE, with 'x11-misc/synergy-plus' v1.3.4 installed. This bug is sent as a 'synergy' problem, but it may be a 'gnome3' (ver. 3.0+3) problem. Thanks for the bug report. Sorry I've been slow in getting back to you. Could you send along your .synergy.conf on the GNOME 3 box (the one that's active when things don't work)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557220: any news about this bug 557220?
On 11/04/2011 05:55 PM, Andres Cimmarusti wrote: Are there any new developments regarding this bug? In my case, Alt+tab is not what causes it. I haven't been able to isolate what is the cause of the problem. I get many disconnections and like I said before, the server refuses to take the client back... Have you had a chance to test the more recent version in testing/unstable? (1.3.7-1) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557220: any news about this bug 557220?
On 11/07/2011 01:51 PM, Andres Cimmarusti wrote: Have you had a chance to test the more recent version in testing/unstable? (1.3.7-1) I have not and I would like to. However my systems are running stable and at this point I can't upgrade to testing. If synergy is a trivial package to backport, I could do it myself from the testing sources using dpkg-buildpackage If it has other dependencies, perhaps a backport could be uploaded to Squeeze-backports? I will give the first option a try first when I get a chance. It should be. I try to make sure my packages are at least buildable on current stable. If you have any trouble, please let me know. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596831: Wishlist item
severity 596831 wishlist thanks Setting up a Synergy configuration via debconf will be a lot of work, and I'm definitely not convinced it's needed. And without such configuration, there's no way it would be appropriate to add Synergy to the X configuration. Feel free to provide a set of patches to provide this functionality. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534239: Any better?
Have you had this problem recently? There's some indication that this bug may have been fixed with newer xcb versions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642039: Downgrading
severity 642039 normal thanks We've transmitted some logs. At this point, I'm not convinced that there isn't some issue with the X server or video driver here, and I can't reproduce the problem. So I'm dropping the severity to normal. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#449255: Testing with recent synergy
If anyone is still having this problem, can they test with a more recent version? We're up to 1.3.6 as of this moment, with 1.3.7 on the way. Quite a few fixes have been made since the squeeze version. If anyone has trouble getting this running on stable, please let me know. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#446061: new upstream bug
forwarded 446061 http://synergy-foss.org/pm/issues/72 thanks There have been some project shuffles, and upstream is no longer using SourceForge. The original bug(s) have been marked invalid, but the duplicate filed above now seems to be the proper upstream bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#321055: new upstream bug
forwarded 321055 http://synergy-foss.org/pm/issues/20 thanks Upstream has changed hands, and this bug's new home upstream appears to be the link above. The SourceForge bug appears to have been imported, then closed as too old. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#421512: tracked upstream
forwarded 421512 http://synergy-foss.org/pm/issues/13 thanks I believe this feature is being implemented upstream; the above bug is being used to track it. There are some notes about implementing this as an add-on/optional feature due to possible legal issues; anyone with experience in this might want to send a comment upstream, or comment here and I'll forward it. Of course, we'll incorporate this when upstream does. I'm not inclined to do anything outside of upstream's efforts; it's easy enough to port forward with ssh or use stunnel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#415604: new gui upstream
The 1.4.x series of synergy includes a Qt-based setup GUI. I'm looking into uploading 1.4.4 to experimental, since it's currently advertised as beta by upstream, but when 1.4.x (or its successor) finally makes it into unstable, I'll close this bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642039: speed is an issue
On 09/19/2011 04:01 PM, Moshe Yudkowsky wrote: I should mention that in each case when there was a crash, I moved the mouse very rapidly from one screen to the other. Thanks for all the testing; it's very helpful. When you move the mouse rapidly between screens, does it crash every time? If not, does it seem to make crashes happen more quickly? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642039: speed is an issue
On 09/19/2011 06:51 PM, Moshe Yudkowsky wrote: I'd switch to a different window manager if I could find one that switches between virtual desktops when I hit the edge of the current desktop. In fact no others seem to allow virtual desktops inside a workspace, or perhaps I'm reading the documentation incorrectly. I know it would be painful to your current mode of working, but it might also help if you could run a standard GNOME desktop, with the default workspace layout and no edge limits on synergy. If you got through, say, a whole day without crashing, that might tell us something. I should have mentioned this before, too, but could you run synergys with -d DEBUG1 -l logfile and send me the resulting log once it crashes again? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642039: synergy: switch to another computer causes immediate gdm restart
On 09/18/2011 04:34 PM, Moshe Yudkowsky wrote: I have synergy server running on Linux, and a synergy client running on the Mac. Both client and server run at 1.3.6. When I move my cursor from the Linux to the Mac, from time to time gdm will immediately halt and restart. This makes using syslog chancy at best. I have a ~/synergy.conf file - note that it does *not* have a leading . but works regardless. The contents are: I'm a little confused. Are you running synergys on startup? If so, it will not read your per-user synergy.conf (unless you're giving it the config file on the command line, in which case its name makes no difference). If your user session is just crashing, giving you the gdm login window once the crash has settled down, please just say that. I'm also unclear as to what the problem with syslog is. Can you try a few things to help and see where the problem might be? Tell me if changing your configuration in the following ways helps: - Dropping the ranges in the links. - Dropping the switchCorners option. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624366: [Pkg-cups-devel] Bug#624366: Bug#624366: Bug#624366: Hello?
On 08/26/2011 02:48 PM, Jeff Licquia wrote: As it turns out, I find myself serving a printer from squeeze, and with a Window 7 VM I haven't set up printing for. I'll try to get some time to try setting up printing. And I've now done this successfully, with no issues. If you're still having problems, we're going to need to get more details on how you add your printer and why it's not working. Here's the procedure I used. Server: Debian squeeze i386, cups 1.4.4-7. Client: Windows 7 Professional 64-bit running under KVM on Ubuntu 11.10. The printer otherwise works on a mixed Debian/Ubuntu network, with all clients able to autodiscover the printer. - On the server, use w3m to navigate to localhost:631. - Choose Add Printer/Class. On the next screen, pick the local printer, and select Continue. Proceed through the options and set as appropriate until you get to where it asks for the printer make and model. - For the make, select Raw. The model should get set up automatically to Raw queue. - Finish up with the new printer wizard. Don't print a test page (since it would obviously not work right). - On the client, click the Windows logo, then Control Panel. - Select Devices, then Add printer. - Select Network printer. - Interrupt the printer search, and tell Windows your option isn't listed. - For the printer location, give it the URL for the printer. This will look something like... http://server:631/printers/myprinter-raw - Windows tries to connect to the printer, and eventually asks you for the make and model of the printer. Select the appropriate ones. - Print a test page. Hope that helps. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624366: [Pkg-cups-devel] Bug#624366: Hello?
On 08/25/2011 04:13 PM, Chris wrote: This is a pretty major issue, why hasn't anyone acknowledged this yet? It has been 4 months. Raw printing is integral to print serving for print serving to windows boxes... I took a look at the bug. The biggest problem, it appears, is here: D [27/Apr/2011:15:12:56 -0400] Returning HTTP Unauthorized for Print-Job (http://10.99.99.126:631/printers/CUPS-Test) from 10.99.99.199 So you need to tell cupsd that the Windows system is authorized to print. That's done in cupsd.conf; see the man page for the details. Out of curiosity, it's been quite a while since I've had to mess with Windows, but the recommendation back then was to use Samba as a proxy between Windows and CUPS for printing. Is there a reason why this doesn't work for you? It might make life a bit easier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624366: [Pkg-cups-devel] Bug#624366: Bug#624366: Hello?
On 08/26/2011 12:54 PM, Chris wrote: I did tell cupsd that everyone is authorized to print. I opened it up to all computers on the network. It didn't matter who sent the job, if I used raw queues, it would not go through. It would seem that cupsd doesn't agree, if the log posted to the bug is any indication. Could you send along your cupsd.conf* files? Also I am using it as a proxy, I have been doing this for years. It works on lenny, it does not work on squeeze. I have done this on previous releases of debian, redhat, and gentoo with no problems. It is only an issue on squeeze. Then I'm confused. Your original report contains a log which you claim was generated when sharing a printer via IPP to Windows 7. The log is consistent with that, since it looks like the job is being directly submitted over the network instead of locally, as it would look if submitted via Samba. Do you have logs of successful printing from one of the other distros we can compare? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624366: [Pkg-cups-devel] Bug#624366: Bug#624366: Bug#624366: Hello?
On 08/26/2011 02:20 PM, Chris wrote: Have you tried to replicate what I'm talking about here though? It was pretty easily replicable with a stock install. I have been following well documented materials in what I'm doing regarding setting up cups with raw print queues. I was not doing anything strange -- unless there is something just plain different about this version of cups in squeeze. Like I said, I have been doing this for years and never had any issues like this, and backing down to lenny or switching distros fixed the issue... As it turns out, I find myself serving a printer from squeeze, and with a Window 7 VM I haven't set up printing for. I'll try to get some time to try setting up printing. Again, I'm happy to start over if we can get to the bottom of this -- I have clients (customers) I'd really like to update to squeeze yet, but I don't want to put their operations at risk by upgrading and running into this problem again. I'll set up a box tonight, try again, and get back to you... Also, if you prefer, I can email you directly, and leave this out of the bug system until we have a better handle on what is going on -- if you like. OK, let's do that. I will post/retitle/close as appropriate once we figure out what's going on. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638358: synergys causes hover/focus issues with gnome-panel
On 08/18/2011 04:09 PM, Andres Cimmarusti wrote: The conclusion seems to be that gtk+ needs to be rebuilt using the patch attached to comment #21. Though only one user has reported back with success, but a price... The patch makes me nervous; passing on GDK_NATIVE_WINDOWS looks to me (from my admittedly non-expert reading) to potentially break a number of other things. Supposedly, Flash support in Web browsers relies on non-native windows, among other things. There's an alternative way to get GDK_NATIVE_WINDOWS set on just the panel. Move /usr/bin/gnome-panel to /usr/bin/gnome-panel.bin and create the following shell script as /usr/bin/gnome-panel: - #!/bin/sh GDK_NATIVE_WINDOWS=1 export GDK_NATIVE_WINDOWS exec /usr/bin/gnome-panel.bin - It's a hack (and will be undone next time gnome-panel updates, and leave the gnome-panel.bin file behind as cruft), but if you do that and gnome-panel works properly under synergy, then we've confirmed that setting native windows on just the panel will fix the problem. Once we've figured that out, we can see if the gnome-panel folks in Debian are willing to accept a more permanent fix, or if anyone with Synergy upstream has an idea what might be going on. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620870: FHS update regarding this issue
FWIW, the LSB workgroup is working on an update to the FHS, and this issue is one of the primary motivations for the update. The FHS bug linked above is where we are coordinating our work. In addition, see the fhs-discuss thread here: https://lists.linux-foundation.org/pipermail/fhs-discuss/2011-May/61.html Our conclusion seems to be, so far: /run shall exist for the same basic purpose as /var/run historically, and its contents shall not be assumed to be persistent. Please comment on the FHS bug if you feel this is not sufficient or otherwise wrong. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620026: synergy: Mouse stuck on left edge of client computer
On 03/29/2011 07:13 AM, Sam Morris wrote: When I move the mouse off the left edge of the server (leela)'s, it warps to the left edge of jeffry (the client)'s screen and stays there. There is no way to move it back. Moving the mouse up and down does result in vertical motion in the mouse cursor, but the motion of the cursor always seems to be delayed by a fixed number of motion events. It is quite hard to explain, but if I move the mouse up, the mouse pointer on the client will not move for a while, then move up. If I then move the mouse down, the pointer on the client will continue to move up for a while, then slow, reverse, and eventually move down. If I then reverse the mouse again, the mouse pointer continues to move down, then slows, and then moves up again. Are the two machines communicating via a wireless network? I have noticed the speedup/slowdown behavior myself when running over wireless, which went away when I switched to a wired connection. As for the weird warping behavior: is it consistent, or does it do this every single time? Would you mind trying a few things for me? - Running synergy 1.3.6 for Mac. I don't know of any reason why the version would matter (and I ran 1.3.1 and synergy+ 1.3.4 for a short while together), but there might be a reason. - Swapping the client and server. Does it work better with Mac OS X as the server and Debian as the client? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554803: Additional notes on FTBFS
The proper fix for the problem, IMHO, is to simply Build-Depend on libxpm-dev, since the call to XCreateBitmapFromData is only used if libXpm is not detected by configure. My Debian upload fixes the problem in this way. Nevertheless, there is a bug in the fallback code; if the intent is to support systems without libXpm, it has failed. I've taken the configure.in patch and sent it upstream. You can see the bug report here: http://www.htmldoc.org/str.php?L245+P0+S-2+C0+I0+E0+M10+Q -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552568: getting synergy-plus into Debian
On 10/08/2010 08:25 AM, Mehdi Dogguy wrote: Please don't upload to unstable during the freeze and use experimental instead. 1.3.4-1 is now in experimental. Sorry for taking so long, everyone. I'll close this bug when the unstable upload is done (after squeeze). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529630: [Pkg-cups-devel] Bug#529630: cups-bsd contains incorrect dependency fields
j t wrote: I think that this is incorrect: I don't think that cups-bsd should recommend cups, although I am not sure about the depends on debconf and update-inetd. The cups-bsd package contains a lpd server which can accept jobs via the lpd protocol and send them to cupsd. Both debconf and update-inetd are used to support that. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527975: [Pkg-utopia-maintainers] Bug#527975: Lost ability to start OpenVPN connection after upgrade
Michael Biebl wrote: Have you actually read the bug report? Your proposed patch opens a security hole and doesn't really fix the issue (it's a very ugly and bad workaround) Thought I had, but obviously I missed that part. The problem you run into only happens when you are logged in as root, which is not the norm on linux, thus only severity normal. I had been seeing the problem when logged in as my user, not root. The odd thing is that, after reverting the patch and rebooting, everything still seems to work. I was even able to start a root shell (su - in gnome-terminal), and disconnect and reconnect the VPN without problems. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527975: Lost ability to start OpenVPN connection after upgrade
Package: network-manager-openvpn Version: 0.7.1-1 Severity: grave Tags: patch After upgrading from the previous version of the package in squeeze to the current version, I was unable to start the OpenVPN connection I use to secure my wireless network. Looking in /var/log/syslog revealed this: May 9 17:03:15 lflap2 NetworkManager: info VPN plugin state changed: 3 May 9 17:03:15 lflap2 NetworkManager: info VPN connection 'Home (at home)' (Connect) reply received. May 9 17:03:15 lflap2 NetworkManager: WARN nm_vpn_connection_connect_cb(): VPN connection 'Home (at home)' failed to connect: 'No VPN secrets!'. May 9 17:03:15 lflap2 NetworkManager: WARN connection_state_changed(): Could not process the request because no VPN connection was active. May 9 17:03:15 lflap2 NetworkManager: info Policy set 'Auto LICQUIA' (wlan0) as default for routing and DNS. Searching on the phrase No VPN secrets brought me to this Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/360818 which contained this patch for the vpnc plugin: --- nm-vpnc-service.conf.fixed 2009-04-18 17:56:45.0 -0500 +++ nm-vpnc-service.conf2009-04-18 17:57:37.0 -0500 @@ -6,6 +6,10 @@ allow own=org.freedesktop.NetworkManager.vpnc/ allow send_destination=org.freedesktop.NetworkManager.vpnc/ /policy + policy user=at_console + allow own=org.freedesktop.NetworkManager.vpnc/ + allow send_destination=org.freedesktop.NetworkManager.vpnc/ + /policy policy context=default deny own=org.freedesktop.NetworkManager.vpnc/ deny send_destination=org.freedesktop.NetworkManager.vpnc/ (Sorry if that's all screwed up; time to switch my default editor.) Applying that patch to /etc/dbus-1/system.d/nm-openvpn-service.conf, logging out, and logging back in caused OpenVPN support to work again. Why grave? Without this patch, I found it impossible to use OpenVPN from NetworkManager. That seems to qualify as making the package unusable for all or most users. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager-openvpn depends on: ii libc6 2.9-4 GNU C Library: Shared libraries ii libdbus-1-3 1.2.12-1 simple interprocess messaging syst ii libdbus-glib-1-2 0.80-4 simple interprocess messaging syst ii libglib2.0-0 2.20.0-2 The GLib library of C routines ii libnm-glib-vpn0 0.7.1-1network management framework (GLib ii libnm-glib0 0.7.1-1network management framework (GLib ii libnm-util1 0.7.1-1network management framework (shar ii openvpn 2.1~rc11-1 virtual private network daemon network-manager-openvpn recommends no packages. network-manager-openvpn suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505573: Synergy keypress bug
Christoph Blank wrote: Hi, I came across this bug when using synergy in debian unstable: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505573 Is there any information about this? The report seems to be quite old, and the bug still exists. Greetings, Christoph There have been some reports of issues with 32-to-64-bit interaction. Are you using mixed word size platforms? (i.e. 32-bit on one side and 64-bit on the other)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505573: [Fwd: Re: Synergy keypress bug]
---BeginMessage--- Hi Jeff, yep exactly that's the case, I didn't think about that... On Thu, Apr 23, 2009 at 12:04:23PM -0400, Jeff Licquia wrote: There have been some reports of issues with 32-to-64-bit interaction. Are you using mixed word size platforms? (i.e. 32-bit on one side and 64-bit on the other)? ---End Message---
Bug#449255: [Fwd: Synergy SegFault Patch]
---BeginMessage---
Hello,
I saw your name posted as the maintainer for synergy in debian. I'm
not sure if synergy is actively maintained (latest release is 2006),
so I figured you might be the best person to send this to:
I made a patch that will fix a bug that causes a segmentation fault in
synergys. The problem occurs when a hotkey is used to switch.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449255
The patch is below, and also included in an attachment.
Thank you,
Alex
+++ CServer.cpp 2009-04-12 21:37:01.0 -0500
@@ -439,6 +439,14 @@
{
SInt32 dx, dy, dw, dh;
dst-getShape(dx, dy, dw, dh);
+
+ // If given mouse position is invalid (e.g. during a
hotkey screen switch)
+ // then set the new mouse position as the center of
the screen to be switched to
+ if (x dx || y dy || x (dx + dw) || y (dy + dh)) {
+ x = (dw / 2);
+ y = (dh / 2);
+ }
+
assert(x = dx y = dy x dx + dw y dy + dh);
}
#endif
+++ CServer.cpp 2009-04-12 21:37:01.0 -0500
@@ -439,6 +439,14 @@
{
SInt32 dx, dy, dw, dh;
dst-getShape(dx, dy, dw, dh);
+
+ // If given mouse position is invalid (e.g. during a hotkey screen switch)
+ // then set the new mouse position as the center of the screen to be switched to
+ if (x dx || y dy || x (dx + dw) || y (dy + dh)) {
+ x = (dw / 2);
+ y = (dh / 2);
+ }
+
assert(x = dx y = dy x dx + dw y dy + dh);
}
#endif
---End Message---
Bug#449255: Synergy SegFault Patch
tags 449255 + patch thanks Alex wrote: I made a patch that will fix a bug that causes a segmentation fault in synergys. The problem occurs when a hotkey is used to switch. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449255 Thanks. I've forwarded the patch to the bug, so I can keep track of it better. You can always send your patches to particular bugs in Debian's BTS. Any comments sent to bug-number@bugs.debian.org becomes part of the bug, and the package's maintainer gets sent a copy as well. I'll give it a look-see, and may include it in a future version of the package. Right now, I'm dealing with an autobuild failure on MIPS, so the patch may get a chance sooner rather than later. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522135: ITP: python-pip -- Alternative Python package installer
Package: wnpp Severity: wishlist Owner: Jeff Licquia licq...@debian.org * Package name: python-pip Version : 0.3.1 Upstream Author : Ian Bicking * URL : http://pip.openplans.org/ * License : MIT/X Programming Lang: Python Description : Alternative Python package installer This is Ian Bicking's easy_install replacement. It integrates with virtualenv, and does a number of things better. The package is pretty much done and is being tested. If you're impatient, my bzr repository should be here soon: http://bzr.licquia.org/pip/debian -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#507896: epm: does not allows non-alphanum characters in product names
Hi! Sorry for taking so long to reply. I wasn't able to find out more information about the patch. Has this patch been introduced upstream? What was the response? What problem is it trying to solve? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504322: htmldoc: Incorrect package homepage
Vladimir Zapolskiy wrote: Please change the package homepage to http://www.htmldoc.org/. That's a bit confusing that it is not quite the same as http://htmldoc.org/ Thanks! It seems to work for me. Are you experiencing any problems with the original URL? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501257: ITA: cvsps -- Tool to generate CVS patch set information
retitle 501257 ITA: cvsps -- Tool to generate CVS patch set information owner 501257 Jeff Licquia [EMAIL PROTECTED] thanks I think I'll adopt this package, as it's still important for people converting their CVS repositories to other version control systems. I'm also in touch with upstream, and may adopt upstream as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503168: virtualenv bin/activate: PYTHONPATH
Adrian von Bidder wrote: My mistake. I moved the environment and didn't realise that the problem I've been having stems from having the old absolute path inside bin/activate and not from not having PYTHONPATH. So the proper solution [for me] would be to look at $0 and pwd and figure out the root dir of the virtualenv from there. (I like to be able to move/copy around the virtualenv to organize my projects.) The latest virtualenv (1.3) has a --relocatable option that does pretty much what you want. I've merged it in my Bazaar repo, but haven't uploaded packages for it yet. If you're impatient, you can pull it from here: http://bzr.licquia.org/virtualenv/debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503168: virtualenv bin/activate: PYTHONPATH
Adrian von Bidder wrote: Shouldn't PYTHONPATH be set inside a virtual environment to allow easy installation of local modules? I don't think so. Wouldn't that break if the user sets PYTHONPATH manually? It shouldn't be necessary, either. I just tested installing new local modules in a virtualenv using activate, and was able to use both easy_install and python setup.py install. Were you having problems installing local modules before? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464090: git repo does not appear to be accessible
Jeff Licquia wrote: Not being a git expert, I'm not sure how to fix this, but at the moment it doesn't appear possible to get a hold of those patches. Never mind. I educated myself. FWIW, after the clone attempt, you have to do something like this in the partially cloned git tree: git checkout origin/master git branch master git checkout master (At least, that's what I did, and git seems happy now.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464090: git repo does not appear to be accessible
When I try to clone the git repository mentioned on the cvsps page, I get this error: error: Couldn't get http://ydirson.free.fr/soft/git/cvsps.git/HEAD for HEAD The requested URL returned error: 404 And later: warning: remote HEAD refers to nonexistent ref, unable to checkout. Not being a git expert, I'm not sure how to fix this, but at the moment it doesn't appear possible to get a hold of those patches. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502638: oo.o packages don't depend on ttf-bitstream-vera for ui font
Package: openoffice.org Version: 1:2.4.1-11 Severity: normal If the Bitstream Vera fonts (package ttf-bitstream-vera) are not installed, OpenOffice.org uses ugly fonts for the UI. Worse, the font metrics are way off, resulting in huge drop-downs, text boxes, menus, etc. Most of the toolbars are off the screen when it's doing this. I can confirm that installing ttf-bitstream-vera causes OpenOffice.org to look like any other application on the system, and removing it causes the UI font to mess up again. Either OpenOffice.org should be switched to use DejaVu as the default font (which it depends on), or the package should depend or recommend ttf-bitstream-vera. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages openoffice.org depends on: ii openoffice.org-base 1:2.4.1-11 OpenOffice.org office suite - data ii openoffice.org-calc 1:2.4.1-11 OpenOffice.org office suite - spre ii openoffice.org-core 1:2.4.1-11 OpenOffice.org office suite archit ii openoffice.org-draw 1:2.4.1-11 OpenOffice.org office suite - draw ii openoffice.org-filter-mobil 1:2.4.1-11 Mobile Devices Filters for OpenOff ii openoffice.org-impress 1:2.4.1-11 OpenOffice.org office suite - pres ii openoffice.org-java-common 1:2.4.1-11 OpenOffice.org office suite Java s ii openoffice.org-math 1:2.4.1-11 OpenOffice.org office suite - equa ii openoffice.org-officebean 1:2.4.1-11 OpenOffice.org Office Bean ii openoffice.org-report-build 1:2.4.1-11 OpenOffice.org Report Builder exte ii openoffice.org-writer 1:2.4.1-11 OpenOffice.org office suite - word ii openoffice.org-writer2latex 0.5-8Writer/Calc to LaTeX/XHTML convert ii ttf-dejavu 2.25-3 Metapackage to pull in ttf-dejavu- ii ttf-liberation 1.04~beta2-2 Free fonts with the same metrics a Versions of packages openoffice.org recommends: pn openoffice.org-filter-binfilt none (no description available) Versions of packages openoffice.org suggests: ii cups-bsd [cupsys-bs 1.3.8-1lenny2Common UNIX Printing System(tm) - ii cupsys-bsd 1.3.8-1lenny2Common UNIX Printing System (trans ii gstreamer0.10-ffmpe 0.10.4-3 FFmpeg plugin for GStreamer ii gstreamer0.10-plugi 0.10.7-2 GStreamer plugins from the bad s ii gstreamer0.10-plugi 0.10.19-2GStreamer plugins from the base ii gstreamer0.10-plugi 0.10.8-4 GStreamer plugins from the good ii gstreamer0.10-plugi 0.10.8-1 GStreamer plugins from the ugly pn hunspell-dictionary none (no description available) ii iceweasel 3.0.3-2 lightweight web browser based on M ii imagemagick 7:6.3.7.9.dfsg1-2+b2 image manipulation programs ii java-gcj-compat [ja 1.0.78-2 Java runtime environment using GIJ ii libgl1-mesa-glx [li 7.0.3-6 A free implementation of the OpenG pn libpaper-utils none (no description available) ii libsane 1.0.19-21API library for scanners ii libxrender1 1:0.9.4-2X Rendering Extension client libra ii menu2.1.40 generates programs menu for all me ii myspell-en-us [mysp 1:2.4.0-2English_american dictionary for my pn openclipart-openoff none (no description available) ii openoffice.org-gnom 1:2.4.1-11 GNOME Integration for OpenOffice.o ii openoffice.org-help 1:2.4.1-11 English_american help for OpenOffi pn openoffice.org-hyph none (no description available) pn openoffice.org-l10n none (no description available) ii openoffice.org-thes 1:2.4.0-2English Thesaurus for OpenOffice.o pn pstoeditnone (no description available) pn unixodbcnone (no description available) Versions of packages openoffice.org-core depends on: ii fontconfig 2.6.0-1 generic font configuration library ii libc6 2.7-14GNU C Library: Shared libraries ii libcairo2 1.6.4-6 The Cairo 2D vector graphics libra ii libcurl3 7.18.2-5 Multi-protocol file transfer libra ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [ ii libexpat1 2.0.1-4 XML parsing C library - runtime li ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib ii libgcc11:4.3.2-1 GCC support library ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii libgstreamer-plugins-b 0.10.19-2 GStreamer
Bug#502428: epm: double free or corruption
Al Nikolov wrote: $ epm -f rpm package *** glibc detected *** double free or corruption (out): 0xb7fa9090 *** Packaging failed! Can you send me your package.list, and the files you have listed there? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502428: epm: double free or corruption
Also, if you see this, can you update your email address, so I can send replies to you? My last message bounced: [EMAIL PROTECTED]: host mail.dev.drweb.com[84.204.76.120] said: 550 5.1.1 [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) If you don't know how to update your email address in the Debian bug tracking system, just send me personal email, and I'll do it for you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497056: lsb-base: /lib/lsb/init-functions NON-DSFG Licence ?
root wrote: Please investigate if files included in lsb-base conform to DFSG. A lincense change to GPL would be better suited for Debian. I'm confused. The license posted looks like a straight 3-clause BSD license to me, which is surely DFSG-free. What problems do you have with it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495498: xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed.
Carlo Wood wrote: Any progress yet? Things I can test? Nope, sorry. I probably won't have much to report for a while; day job interferes. I noticed that you are using threads in synergys. The assertion that we run into can be caused if multiple threads do calls to GUI calls (X, Xt). All such calls must be done from one thread. Are you doing X calls from more than one thread? I'm not entirely sure. If you look at the history of the package, the most recent upload was done to fix a problem in synergyc that was somewhat related, in that xcb seemed to trigger it. The problem there was that we were noticing events from watching the X socket. The problem is that X events could sneak through due to a race condition, and the client would appear to hang. For that problem, the client didn't do anything thread-unsafe with X calls, but it did detect events and handle them in separate threads. I suspect something similar may be happening in the server, but have no idea if that's causing this or some other problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495498: xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed.
Carlo Wood wrote: Please ask if you need more info. Those are helpful, but please be sure to CC the bug, so there's a record that anyone can see and comment on. I've asked the others, but it's worth asking you: do you have the ability to test synergys from 1.3.1-4 on etch? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495498: xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed.
Carlo Wood wrote: Note that I already am running/testing synergy 1.3.1-4. But no, I only have debian lenny/sid on both machines. I could run synergys in an etch chroot though, 64bit or 32bit. The only difference would be the versions of the libraries it links with. That's exactly what I'm wanting to test. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495498: xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed.
Carlo Wood wrote: Since my last apt-get update/upgrade, synergys crashes more often than before. It now crashes with the output: ... DEBUG1: CClientProxy1_0.cpp,253: send enter to taryn, 0,881 3 DEBUG1: CServer.cpp,780: try to leave taryn on left INFO: CServer.cpp,447: switch from taryn to hikaru at 3345,876 DEBUG1: CClientProxy1_0.cpp,261: send leave to taryn synergys: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed. Aborted I've gotten a number of bug reports on this, and am still trying to figure it out. I take it hikaru is the server, and taryn is the client, set up on the left? Which operating system is taryn running? For both, what is the desktop setup? (The last question may be obvious if the client is Mac OS X or Windows.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494368: synergy: Synergy quits with assertion failure.
Marc Oscar Singer wrote: Jeff Licquia wrote: Do you have any etch boxes you could test for this with? It may be too much to ask, I know, to run etch for a few days. :-) what test do you want run? Just try to duplicate the crash you're seeing when running synergys under etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494368: synergy: Synergy quits with assertion failure.
Marc Singer wrote: Started synergys with the following command line: synergys -f -d INFO After running for a couple of days, it reported an assertion failure on the console. synergys: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int)((xcb_req) - (dpy-request)) = 0)' failed. This *could* be the same as the core dumping crashes, but there is no way to tell from the output. Looks similar to me; I think I'll end up merging them. What desktop setup do you have? Anything unusual (compiz, weird GNOME/KDE setup, etc.)? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494368: synergy: Synergy quits with assertion failure.
Marc Oscar Singer wrote: Jeff Licquia wrote: Looks similar to me; I think I'll end up merging them. As you wish. The assert makes it very debug-able. IMHO, this looks like memory corruption. I haven't run with MALLOC_CHECK_ (IIRC) just to see if the libc can tell us something about memory. It could be, but my working theory right now is that synergy is not conforming to the X11 spec; it's assuming something that used to be true, but strictly speaking couldn't be assumed. Moving from the old X11 libs to the new XCB-based ones changed things, I think. We had a similar problem with the client that should now be fixed. Do you have any etch boxes you could test for this with? It may be too much to ask, I know, to run etch for a few days. :-) Using Gnome. Nothing non-standard ITO my Debian install. The other computer is a Mac. OK, thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493706: synergys dumps core frequently
Gregoire Banderet wrote: XFCE, nothing special. The PC where synergys is running has a multi-head GFX card but I use only one output. Thanks. My second monitor is connected to a Windows PC (where synergyc 1.3.1) is running. I had no problem during 3 years with the same setup but Debian Etch instead of Lenny. This, combined with the details of the crash, implies that the new XCB may be the source of the problem. We've had at least one bug caused by that in synergyc. I'm a C programmer, I can recompiled the source with others options or some printfs if you want. I have also some core files if you want (just tell me where to send them, a file is ~17MB). Can you keep those cores around for me for a short while, or do you need the disk space back? I'll need to make arrangements to transfer the cores. Also, to test my theory that interaction with XCB is to blame: do you have any etch boxes left? If so, can you build the synergy package for etch and check to see if you have the same problem there? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493706: synergys dumps core frequently
Gregoire Banderet wrote: Package: synergy Version: 1.3.1-4 Severity: important Output when run with --no-daemon: DEBUG: CXWindowsClipboard.cpp,555: added format 2 for target text/html (508) (360 bytes) DEBUG: CXWindowsClipboard.cpp,555: added format 0 for target UTF8_STRING (243) (22 bytes) DEBUG: CXWindowsClipboard.cpp,348: close clipboard 1 DEBUG: CServer.cpp,1435: ignored screen tux update of clipboard 1 (unchanged) synergys: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed. Aborted (core dumped) What is your normal desktop setup? GNOME/KDE + any differences from standard, or other preferred window manager? Multi-head? Other interesting things about your setup? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488460: unchecked error return codes
Kees Cook wrote: This patch fixes a number of cases where error conditions are untested, which cause problems when compiling with -D_FORTIFY_SOURCE=2. Hi! Sorry for the late reply; just got back from vacation. I'm not super-keen on diverging from upstream in general unless absolutely necessary. Most of the changes in the patch are tool patches; they don't really fix problems in the code itself, but just issues with Fortify. I'm not inclined to include them unless they come down from upstream. The only two parts that fix real issues, as I see it, are: - the daemonization code - the pipe flush (read) in lib/arch/CArchNetworkBSD.cpp The daemonization code is just ugly. I smell a future bug in the code that relies on sequential file descriptor assignment by the OS. So that needs more work. The pipe flush code is probably a little more correct, but I'd also like to see better handling of unexpected error conditions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
