So I have the problem as well (6 years later). I just found that sleepd
runs and fills up my swap entirely.
I'm running buster if it helps.
--
I always leave an empty milk carton is the refrigerator just in case
someone wants their coffee black.
Confirming I have this problem too. My /etc/sshguard/sshguard.conf has
LOGREADER="LANG=C /bin/journalctl -afb -p info -n1 -o cat SYSLOG_FACILITY=4
SYSLOG_FACILITY=10"
The example provided by upstream has
LOGREADER="LANG=C journalctl -afb -p info -n1 -t sshd -t sendmail -o cat"
Changing
Hi There,
I think this is a bug with pinentry-gtk-2. Running it almost always
results in the following warning:
$ echo getpin | pinentry-gtk-2
OK Pleased to meet you
** (pinentry-gtk-2:28067): WARNING **: it took 32 tries to grab the keyboard
D this is a test
OK
Sometimes it
Thanks! I confirm it's fixed on my system with the update.
GI
--
File not found. Should I fake it? (Y/N)
On Wed, Dec 21, 2016 at 04:34:43AM +, Jerome BENOIT wrote:
> Can you send a minimal material (sample(s) + procedure) that reproduce
> the issue ?
Dear Jerome,
Thanks for your quick response, and apologies for not being more
explicit.
I'm attaching a minimal bib file and rsc file to reproduc
On Fri, Jan 08, 2016 at 10:44:00AM +0100, Sebastian Ramacher wrote:
> The BTS knows about versions and keeps track of them. See the graph on
> the top right of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809982.
Oh I see. Thanks.
Best,
Gautam
--
Mathematicians are like Frenchmen: what
Please don't close this bug as long as 0.3.1-2 is still the only version
in Jessie! Some unsuspecting Jessie user will get burnt badly!
GI
--
One man's folly is another man's wife.
On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote:
> I'd recommend to try the new version available in unstable and check
> if the problem still exists.
It appears that the problem is fixed in 0.3.4-1 in testing. (If not,
I'll reopen a separate bug for 0.3.4-1).
The version 0.3.
On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote:
> Otherwise we need a more verbose valgrind log with the GTK+ leaks
> filtered out.
How do I get you this log? If you tell me what I should run on my system
to get you the info you need, I'm happy to do it.
I'll check out the ve
Update: I ran valgrind. Here's the summary:
==13647== LEAK SUMMARY:
==13647==definitely lost: 274,913 bytes in 62 blocks
==13647==indirectly lost: 29,937 bytes in 1,264 blocks
==13647== possibly lost: 71,528 bytes in 876 blocks
==13647==still reachable: 70,136,
Package: zathura
Version: 0.3.1-2
Severity: normal
Dear Maintainers,
There is a memory leak in zathura. Steps to reproduce:
1. Open a PDF file (e.g. output generated by LaTeX)
2. Scroll
3. Refresh the PDF (e.g. by recompiling the LaTeX document)
(You might have to do a forward / i
On Fri, Jul 18, 2014 at 09:04:20AM +0200, Sebastian Ramacher wrote:
>> When I run zathura it exits immediately with the message
>>
>> /usr/bin/zathura: symbol lookup error: /usr/bin/zathura: undefined
>> symbol: girara_template_add_variable
>
> Looks like you have an old copy of libgirar
Package: zathura
Version: 0.2.9-2
Severity: grave
Justification: renders package unusable
When I run zathura it exits immediately with the message
/usr/bin/zathura: symbol lookup error: /usr/bin/zathura: undefined
symbol: girara_template_add_variable
PS: Note I'm running zathura in a tes
I noticed that the iceweasel-17.0.6esr-1~deb7u1 is now pulled through
wheezy/updates from security.debian.org.
The xul-ext-pentadactyl-1.0~rc1-1 from wheezy is incompatible with
iceweasel-17.0.6esr-1~deb7u1 (as pointed out above).
The xul-ext-pentadactyl-1.0+hg6924-1 (from testing) is compatible
I had the same problem. However, I don't think there's a problem with
xdg-open. I don't think that xdg-open does any translation of %c or %i
(see the source). The translation seems to be done by mimeopen.
I installed desktop-file-utils, and did update-desktop-database. It
seems fine now,
GI
--
On Fri, Jan 20, 2012 at 09:31:42AM +, Michael Stevens wrote:
>> It would be great to see fvwm 2.6.3 in debian. Please Upgrade
>
> I too would like to see this.
I'd love to see this in Debian too.
GI
--
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subje
The upgrade to xserver-xorg-input-wacom 0.12.0-1 broke everything.
Here's an update of the calibration script to work with the new
xsetwacom syntax.
I've heard there's a way to set the calibration / etc. through HAL.
However, as long as xsetwacom "Works for me (tm)", I'll follow the path
of least
I have the same issue. I've noticed the segfault usually occurs when the
ball leaves the TOP of the screen. Initially there are a bunch of thin
yellow bricks, which break after the ball hits them once. The second
time the ball goes there, it goes through the gap and off the top of the
screen, and t
On Fri, May 13, 2011 at 09:49:23PM -0400, gi1242+debianb...@gmail.com wrote:
> Now installing this driver solves all the problems on my system. I'll
> post back confirming though.
OK. The bug is back. It is a little more sporadic, and a lot less
severe. But the bug is certainly bac
On Wed, May 11, 2011 at 10:30:10AM +0200, Cyril Brulebois wrote:
>> There was a suggestion on the Xournal mailing list that this bug is
>> related to
>>
>>
>> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=3145530feed879082bcfab11ffc8e7fd0911c920
>>
>> But I haven't mas
Package: xserver-xorg-video-intel
Version: 2:2.15.0-1
Severity: important
There are various instances when the screen is not updated. Usually this
happens when repeated keyboard, or mouse input is involved at the same
time. Some examples:
xournal
When using the 2.6.38 kernel, some st
Here's an updated version of the script. With the recent xsetwacom
upgrade, it wasn't harvesting device names correctly. Should be fixed
now,
GI
--
100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD
49. If I learn the whereabouts of the one artifact which can destroy me,
I will not send all my
Hi Clint,
Looks like there's a typo in your patch below:
> -if _pick_variant -c $words[1] psmisc=psmisc unix -V; then
> +if _pick_variant -c $words[1] psmisc='#(i)psmisc' unix -V; then
Should be '(#i)...' not '#(i)...' right?
Thanks,
GI
PS: I started using zsh 2 weeks ago. It is *AWESOME*, th
Package: zsh
Version: 4.3.10-14
Severity: normal
Tags: patch
The completion function for fuser tries to determine if fuser is
provided by PSmisc, or other the (less functional) generic Unix version.
It decides by checking the output of "fuser -V" for psmisc. However it
does not use case insensitiv
On Sat, Oct 23, 2010 at 03:43:53PM -0400, gi1242+debianb...@gmail.com wrote:
>> Perhaps grub-probe thinks that my /dev/sdb1 is an Extended partition,
>> rather than swap?
>
> I got the same set of warnings, and had the same issue (i.e. a partition
> table residing in the mb
On Mon, Oct 04, 2010 at 11:59:44AM +0800, Michael Deegan wrote:
> Perhaps grub-probe thinks that my /dev/sdb1 is an Extended partition,
> rather than swap?
I got the same set of warnings, and had the same issue (i.e. a partition
table residing in the mbr of my swap). I just recreated my swap and
Ok -- this problem has been fixed upstream. It's an issue with
xserver-xorg-input-wacom. It's fixed in 0.10.8, for which no Debian
package exists yet.
The bug is present in 0.10.5+20100416-1 which is the latest version
available with Debian.
GI
--
'Common' Proof Techniques:
23. Proof by vehemen
On Tue, Aug 24, 2010 at 09:13:31PM +0200, Lucas Nussbaum wrote:
The issue does not arise if you don't use the ":q" modifier. This bug
was not present in 6.17.02-3 and is present in 6.17.02-2.
>>>
>>> Huh? I guess you mistyped one of the new versions. Could you check?
>>
>> Yes, I swapp
On Tue, Aug 24, 2010 at 07:25:54AM +0200, Lucas Nussbaum wrote:
>> The issue does not arise if you don't use the ":q" modifier. This bug
>> was not present in 6.17.02-3 and is present in 6.17.02-2.
>
> Huh? I guess you mistyped one of the new versions. Could you check?
Yes, I swapped them apolog
Package: tcsh
Version: 6.17.02-3
Severity: normal
If the alias "jobcmd" contains "!#:q", then all your typed commands are
stored twice in the history. Once as typed, and once with only the first
argument (and aliases expanded).
The issue does not arise if you don't use the ":q" modifier. This bug
On Mon, Mar 15, 2010 at 11:51:25PM +, Debian Bug Tracking System wrote:
> We believe that the bug you reported is fixed in the latest version of
> xorg-server, which is due to be installed in the Debian FTP archive:
>
> xdmx-tools_1.7.5.902-1_amd64.deb
> to main/x/xorg-server/xdmx-tools_1.7
On Tue, Mar 02, 2010 at 12:31:34AM +1030, Ron wrote:
> This looks like you're probably just getting bitten by the fact that
> there is no support for serial tablets yet in the udev/config server.
> That should be coming soon. There is a patch in bug #568236 if you
> want it even sooner.
Thanks R
Ok, I think I know what the problem is. It has nothing to do with Intel
drivers/KMS. The problem is with Wacom!
If I remove the Wacom specific lines in my xorg.conf, VT switching is
instant.
I'll see if I can track down this bug better. Can you reassign it to the
Wacom maintainer?
GI
--
Altern
On Sun, Feb 28, 2010 at 10:52:44PM +0100, Cyril Brulebois wrote:
>> I'm attaching my current Xorg.0.log. If there's a different one you
>> want, just let me know.
>
> Last lines in dmesg would be nice, especially if you could mark the
> last line you got before switching back to X.
Ok. In dmesg,
On Sun, Feb 28, 2010 at 07:47:59PM +0100, Cyril Brulebois wrote:
>> Package: xserver-xorg-video-intel
>> Version: 2:2.9.1-2
>> Severity: normal
>
> Hi,
>
>> After my recent xorg server upgrade, I find that switching VT's
>> takes unusually long (about 8 seconds) when switching *BACK* to
>> X. Th
Package: xserver-xorg-video-intel
Version: 2:2.9.1-2
Severity: normal
After my recent xorg server upgrade, I find that switching VT's takes
unusually long (about 8 seconds) when switching *BACK* to X. This
happens every time I hibernate / resume for instance, and happens both
with and without KMS.
36 matches
Mail list logo
