Bug#762029: Still happens
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.
Bug#928525: Confirming
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 it to this makes the problem go away. (Since I use postfix, I used "-t postfix/smtpd" instead of sendmail.) GI -- My wife told me I had to stop acting like a flamingo. So I had to put my foot down.
Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key
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 (erratically) fails outright as follows: $ echo getpin | pinentry-gtk-2 OK Pleased to meet you ** (pinentry-gtk-2:28071): WARNING **: it took 38 tries to grab the keyboard ** (pinentry-gtk-2:28071): CRITICAL **: could not grab pointer: already grabbed (1) ERR 83886179 Operation cancelled If I replace pinentry-gtk-2 with pinentry-qt or pinentry-curses I don't get any such warning anymore. (For pinentry-curses I have to type getpin, and redirect the stdin, of course.) It may or may not be related to the fact that I'm running under fvwm, and not a standard desktop environment. GI -- Did you hear about the blonde who threw away her weight loss video? She noticed that the people on the video weren't losing weight either!
Bug#848947: closed by Jerome Benoit <calcu...@rezozer.net> (Bug#848947: fixed in bibtool 2.66+ds-2)
Thanks! I confirm it's fixed on my system with the update. GI -- File not found. Should I fake it? (Y/N)
Bug#848947: bibtool: [Regression] Empty separators cause errors
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 reproduce the problem.
Running
bibtool -r bibtoolrsc < test.bib
produces
*** BibTool ERROR: Invalid separator specification.
@Book{Adams.Fournier,
author= {Adams, Robert A. and Fournier, John J. F.}
}
With earlier versions it used to produce
@Book{AdamsFournier,
author= {Adams, Robert A. and Fournier, John J. F.}
}
(i.e. the key is supposed to be "AdamsFournier" and not
"Adams.Fournier")
Best,
GI
--
Birthdays are good for health. Studies show that people who have more
birthdays live longer.
fmt.name.name = {}
key.format = {%2n(author)}
@Book{ AdamsFournier03,
author = {Adams, Robert A. and Fournier, John J. F.},
}
Bug#809982: closed by Sebastian Ramacher <sramac...@debian.org> (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)
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: whatever you say to them, they translate it into their own language, and forthwith it means something entirely different. -- Goethe
Bug#809982: closed by Sebastian Ramacher <sramac...@debian.org> (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)
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.
Bug#809982: zathura: Memory leak when PDF is refreshed
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.1-2 in Jessie still has the memory leak though. Best, Gautam -- 'Kleptomaniac' -- One who can't help himself from helping himself.
Bug#809982: zathura: Memory leak when PDF is refreshed
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,419 bytes in 31,730 blocks ==13647== suppressed: 0 bytes in 0 blocks ==13647== Reachable blocks (those to which a pointer was found) are not shown. ==13647== To see them, rerun with: --leak-check=full --show-leak-kinds=all Looks like there definitely is a memory leak which leaks sizable chunks of memory (not just a KB or two). GI -- The system requirements said 'Requires Windows 95 or better', so I bought a Mac.
Bug#809982: zathura: Memory leak when PDF is refreshed
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 version in testing later today. Thanks, GI -- 'Altruism' -- That occasional moment when your selfishness benefits someone else.
Bug#809982: zathura: Memory leak when PDF is refreshed
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 / inverse search in between to trigger it.) I'm not "cool enough" to valgrind. But I monitored memory usage using ps -o pid,vsz,pmem,pcpu,tty,cmd --sort -pmem,-pcpu -C zathura After about an hour of work (on a 2 / 3 page paper without any figures) the memory usage of zathura rises from a footprint of about 1.5% (about 50MB) initially to 20% (about 750MB) by the end of the hour. This is possibly fixed upstream here: https://git.pwmt.org/pwmt/zathura/commit/876d35de943b16de7b8a218065a0a7409b383634 Thanks and best, GI PS: I marked severity as normal since I didn't know if the correct section for higher severities. It does make Zathura unusable on my system though. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zathura depends on: ii libc6 2.19-18+deb8u1 ii libcairo2 1.14.0-2.1 ii libgirara-gtk3-1 0.2.3-1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-03.14.5-1+deb8u1 ii libmagic1 1:5.22+15-2 ii libpoppler-glib8 0.26.5-2 ii libsqlite3-0 3.8.7.1-1+deb8u1 ii libsynctex1 2014.20140926.35254-6 zathura recommends no packages. Versions of packages zathura suggests: ii chromium [www-browser]47.0.2526.80-1~deb8u1 ii google-chrome-beta [www-browser] 48.0.2564.48-1 ii iceweasel [www-browser] 38.5.0esr-1~deb8u2 ii konqueror [www-browser] 4:4.14.2-1 ii poppler-data 0.4.7-1 ii w3m [www-browser] 0.5.3-19 pn zathura-cb ii zathura-djvu 0.2.4-6 ii zathura-ps0.2.2-6 -- no debconf information -- A program is a device used to convert data into error messages.
Bug#755132: zathura: fails to start (symbol lookup error)
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 libgirara-gtk3.so.1 somewhere in library lookup path. Please attach ld -r /usr/bin/zathura. Hmm. I'm no LD guru: $ ld -r /usr/bin/zathura ld: attempted static link of dynamic object `/usr/bin/zathura' However, you are 100% right about an old copy of libgirara-gtk3.so.1 in my library lookup path. Running LD_LIBRARY_PATH= /usr/bin/zathura fixes the problem. Thanks a lot and sorry to bother you for a mistake of mine! Please close this bug. GI -- Don't have awk? Use this simple sh emulation: #!/bin/sh echo 'Awk bailing out!' exit 2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755132: zathura: fails to start (symbol lookup error)
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 testing chroot. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/dash Versions of packages zathura depends on: ii libc6 2.19-7 ii libcairo2 1.12.16-2 ii libgirara-gtk3-1 0.2.2-2 ii libglib2.0-0 2.40.0-3 ii libgtk-3-03.12.2-1+b1 ii libmagic1 1:5.19-1 ii libpoppler-glib8 0.26.2-2 ii libsqlite3-0 3.8.5-2 ii libsynctex1 2014.20140528.34243-4 zathura recommends no packages. Versions of packages zathura suggests: ii iceweasel [www-browser] 30.0-2 ii poppler-data 0.4.6-5 pn zathura-cb none ii zathura-djvu 0.2.3-5 ii zathura-ps 0.2.2-5 -- no debconf information -- Freedom of speech is wonderful - right up there with the freedom not to listen. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706990: Only fixed in testing
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 with iceweasel, of course, but is not in wheezy. Should users pull xul-ext-pentadactyl-1.0+hg6924-1 from testing? Or will there be a compatible version released for wheezy? (I don't mind pulling it from wheezy for now; but I'm concerned that somewhere down the road the xul-ext-pentadactyl/testing will stop working with iceweasel/wheezy...) GI PS: Sorry if I asked a standard procedure question, which you are already in the process of taking care off... -- 'Gambling' -- The sure way of getting nothing for something. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661171: Needs desktop-file-utils
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 -- Little Johnny was a scientist. Little Johnny is no more. For what he thought was H2O was H2SO4. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623194: Please upgrade fvwm to version 2.6.3
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 -- LIFE!Insert boring stuff here/LIFE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#315142: Gtk+Perl alternative to wacomcpl
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 resistance. GI -- 100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD 24. I will maintain a realistic assessment of my strengths and weaknesses. Even though this takes some of the fun out of the job, at least I will never utter the line No, this cannot be! I AM INVINCIBLE!!! (After that, death is usually instantaneous.) calibrate.pl Description: Perl program
Bug#627482: Segmentation fault on level 1 of area 2
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 the segfault happens. GI -- 'Oregon' -- When, after two days of rain, Monday arrives. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)
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 mastered debian packaging enough to try integrating this myself. something like this should do the job, or at least get you started: sudo apt-get build-dep xserver-xorg-video-intel # from the devscripts package, or git clone from git.debian.org: debcheckout xserver-xorg-video-intel cd xserver-xorg-video-intel git remote add upstream git://anongit.freedesktop.org/xorg/driver/xf86-video-intel git fetch upstream git cherry-pick 3145530feed879082bcfab11ffc8e7fd0911c920 dch --local +yournickname Cherry-pick 3145530feed879082bcfab11ffc8e7fd0911c920 from upstream. debuild -b sudo debi Thanks a ton! This worked. Though I presume you mean debuild -d (instead of -b) Also there were two other patches in the git upstream that might have been related; so instead of cherry picking, I did git pull upstream HEAD Now installing this driver solves all the problems on my system. I'll post back confirming though. I've heard reports that this bug is aggravated by repeated suspend / resumes. If things are working tip top in a few days, I'll post back confirming. Thanks a ton for the Debian package build instructions! It was exactly what I needed, GI -- 100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD 66. My security keypad will actually be a fingerprint scanner. Anyone who watches someone press a sequence of buttons or dusts the pad for fingerprints then subsequently tries to enter by repeating that sequence will trigger the alarm system. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)
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 back. (However the system is a lot more usable, since the bug is a lot lot less severe. Please let me know if there is anything I can do to help fix it. -- 'Committee' -- A cul-de-sac down which ideas are lured and then quietly strangled. signature.asc Description: Digital signature
Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)
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 strokes don't show up, until the pen/mouse leave the xournal window. When using the 2.6.32, or 2.6.38 kernels, when the display is rotated, the strokes show up after a delay. I followed this upstream and the bug was traced to the video driver: http://sourceforge.net/mailarchive/message.php?msg_id=27467219 http://sourceforge.net/mailarchive/message.php?msg_id=27480622 frozen-bubble-2.2.0-2 pangzero-1.3-2 In both games, there are numerous times (usually when I hold down a key) when the screen stops being updated. The bug is not present when I use the 2.6.32 kernel. 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 mastered debian packaging enough to try integrating this myself. (Trying to install xserver-xorg-video-intel/sid itself wanted me to upgrade xserver-xorg-core, which I wasn't prepared to do as this is my primary work machine). Finally, this might be related to Debian Bug #597696, or it might not be. I wasn't sure, so I opened a new issue. Thanks for any help with this, GI -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Dec 21 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1926464 Mar 25 23:49 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 Kernel version (/proc/version): --- Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 32106 Dec 23 2009 /var/log/Xorg.2.log -rw-r--r-- 1 root root 22147 Feb 19 22:49 /var/log/Xorg.1.log -rw-r--r-- 1 root root 29733 May 10 21:43 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [59.171] X.Org X Server 1.9.5 Release Date: 2011-03-17 [59.171] X Protocol Version 11, Revision 0 [59.171] Build Operating System: Linux 2.6.38-1-amd64 x86_64 Debian [59.171] Current Operating System: Linux mordor 2.6.38-2-amd64 #1 SMP Thu Apr 7 04:28:07 UTC 2011 x86_64 [59.171] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 root=UUID=9f504572-3101-4f1d-9c22-08938165f79d ro quiet [59.171] Build Date: 26 March 2011 03:32:34AM [59.171] xorg-server 2:1.9.5-1 (Cyril Brulebois k...@debian.org) [59.171] Current version of pixman: 0.21.4 [59.171]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [59.171] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [59.172] (==) Log file: /var/log/Xorg.0.log, Time: Tue May 10 07:43:42 2011 [59.269] (==) Using system config directory /usr/share/X11/xorg.conf.d [59.308] (==) No Layout section. Using the first Screen section. [59.308] (==) No screen section available. Using defaults. [59.308] (**) |--Screen Default Screen Section (0) [59.308] (**) | |--Monitor default monitor [59.309] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [59.309] (==) Automatically adding devices [59.309] (==) Automatically enabling devices [59.352] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [59.352]Entry deleted from font path. [59.476] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [59.476] (==) ModulePath set to /usr/lib/xorg/modules [59.476] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable
Bug#315142: Gtk+Perl alternative to wacomcpl
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 troops out to seize it. Instead I will send them out to seize something else and quietly put a Want-Ad in the local paper. calibrate.pl Description: Perl program
Bug#607603: zsh: Completion of fuser command does not detect psmisc version
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*, thanks a TON. I'm migrating my custom completions over from tcsh, and have a few new zsh completions, and corrections to old completions to contribute. What is the best way to post them? Debian bugzilla, or the mailing list? -- The short fortuneteller who escaped from prison was a small medium at large. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607603: zsh: Completion of fuser command does not detect psmisc version
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 insensitive matching, so the test fails on my system (even though my fuser is provided by psmisc). Changing line 6 in /usr/share/zsh/functions/Completion/Unix/_fuser from if _pick_variant -c $words[1] psmisc=psmisc unix -V; then to if _pick_variant -c $words[1] psmisc='(#i)psmisc' unix -V; then fixes the problem. GI -- 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.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages zsh depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3 support for getting/setting POSIX. ii libncursesw5 5.7+20100313-4 shared libraries for terminal hand Versions of packages zsh recommends: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi Versions of packages zsh suggests: ii zsh-doc 4.3.10-14 zsh documentation - info/HTML form -- no debconf information -- TOP 10 NEW FEATURES OF THE NEXT VERSION OF WINDOWS 3. Start-up .wav file replaced with the cha-ching sound of a cash register. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590231: improperly nested partition?
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 mbr of my swap). I just recreated my swap and all was fine: swapoff -a mkswap -f /dev/sda2 # WARNING: Make sure the device name is correct. # -f means force. Wrong name = lost data. You have to use the -f flag, otherwise your old boot sector won't be erased. On successful completion, you should get no warning message, and mkswap should have printed a UUID. Edit your /etc/fstab and replace the UUID of the old swap partition with the new one. Then run swapon -a and you're good to go. Oops. If you suspend to disk, then you need to update the swap UUID in /etc/initramfs-tools/conf.d/resume as well. Then run update-initramfs -k all -u update-grub # Probably not necessary and reboot. GI -- File not found. Should I fake it? (Y/N) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568608: Please reopen. Fixed upstream, but not in Debian.
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 vehement assertion -- It is useful to have some kind of authority relation to the audience. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590231: improperly nested partition?
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 all was fine: swapoff -a mkswap -f /dev/sda2 # WARNING: Make sure the device name is correct. # -f means force. Wrong name = lost data. You have to use the -f flag, otherwise your old boot sector won't be erased. On successful completion, you should get no warning message, and mkswap should have printed a UUID. Edit your /etc/fstab and replace the UUID of the old swap partition with the new one. Then run swapon -a and you're good to go. GI -- 'Microsecond' -- The time it takes for your state-of-the-art computer to become obsolete. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd
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 swapped them apologies. (I sent a correction email, but it got rejected by the BTS as there was no number assigned yet). The bug is present in 6.17.02-3. The bug is not present in 6.17.02-2. That's rather strange. The only difference between the two versions is the re-addition of an unrelated patch. Could you maybe recheck using the binary packages on http://snapshot.debian.org/package/tcsh/ ? Indeed. On rechecking, the bug is also present in 6.17.02-x. The bug is however *absent* in 6.17.00-3. Check what you get on your system with the following: tcsh: tcsh -f alias jobcmd echo -n '\e]0;\!#:q ($cwd)\a' /bin/echo hello world history On 6.17.00-3 the output of the last command is 1 21:12 alias jobcmd echo -n '\e]0;\!#:q ($cwd)\a' 2 21:12 /bin/echo hello world 3 21:12 history On 6.17.02-3 the output of the last command is 1 21:17 alias jobcmd echo -n '\e]0;\!#:q ($cwd)\a' 2 21:17 /bin/echo hello world -5000 21:17 /bin/echo hello 3 21:17 history The history event with number -5000 is a bug. Thanks, GI -- Actually officer, if you factor in the earth's rotation, we were all speeding. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd
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 apologies. (I sent a correction email, but it got rejected by the BTS as there was no number assigned yet). The bug is present in 6.17.02-3. The bug is not present in 6.17.02-2. Thanks, Gautam -- 'Common' Proof Techniques: 18. Proof by importance -- A large body of useful consequences all follow from the proposition in question. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd
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 was not present in 6.17.02-3 and is present in 6.17.02-2. Here's how you can reproduce this: 1. Set jobcmd to use !#:q in some way. E.g.: alias jobcmd echo -n '\e]0;\!#:q\a' 2. Run any command. E.g. /bin/echo a b 3. See the bottom of your history. 583 0:31/bin/echo a b -5000 0:31/bin/echo a 584 0:31history | tail 4. Alternately go up in the history (using the up key). You'll first see a command /bin/echo a (which you never typed). Pressing the up key again, you'll get the command /bin/echo a b which you typed. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages tcsh depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-2 shared libraries for terminal hand tcsh recommends no packages. tcsh suggests no packages. -- no debconf information -- A Windows user spends 1/3 of his life sleeping, 1/3 working, 1/3 waiting. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568608: closed by Cyril Brulebois k...@debian.org (Bug#568236: fixed in xorg-server 2:1.7.5.902-1)
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.5.902-1_amd64.deb xdmx_1.7.5.902-1_amd64.deb to main/x/xorg-server/xdmx_1.7.5.902-1_amd64.deb xnest_1.7.5.902-1_amd64.deb to main/x/xorg-server/xnest_1.7.5.902-1_amd64.deb xorg-server_1.7.5.902-1.diff.gz to main/x/xorg-server/xorg-server_1.7.5.902-1.diff.gz xorg-server_1.7.5.902-1.dsc to main/x/xorg-server/xorg-server_1.7.5.902-1.dsc xorg-server_1.7.5.902.orig.tar.gz to main/x/xorg-server/xorg-server_1.7.5.902.orig.tar.gz xserver-common_1.7.5.902-1_all.deb to main/x/xorg-server/xserver-common_1.7.5.902-1_all.deb xserver-xephyr_1.7.5.902-1_amd64.deb to main/x/xorg-server/xserver-xephyr_1.7.5.902-1_amd64.deb xserver-xfbdev_1.7.5.902-1_amd64.deb to main/x/xorg-server/xserver-xfbdev_1.7.5.902-1_amd64.deb xserver-xorg-core-dbg_1.7.5.902-1_amd64.deb to main/x/xorg-server/xserver-xorg-core-dbg_1.7.5.902-1_amd64.deb xserver-xorg-core-udeb_1.7.5.902-1_amd64.udeb to main/x/xorg-server/xserver-xorg-core-udeb_1.7.5.902-1_amd64.udeb xserver-xorg-core_1.7.5.902-1_amd64.deb to main/x/xorg-server/xserver-xorg-core_1.7.5.902-1_amd64.deb xserver-xorg-dev_1.7.5.902-1_amd64.deb to main/x/xorg-server/xserver-xorg-dev_1.7.5.902-1_amd64.deb xvfb_1.7.5.902-1_amd64.deb to main/x/xorg-server/xvfb_1.7.5.902-1_amd64.deb I just confirmed. This does NOT fix the problem! Can you please reopen the bug? Amongst the above, here's what I have installed currently on my system: xserver-common 2:1.7.6-1 xserver-xorg-core 2:1.7.6-1 xserver-xorg-dev2:1.7.6-1 The server hangs 8 seconds when I switch back to it from a console. The problem, as pointed out before, is with the WACOM serial device. I've heard that there is a fix upstream, but it has not propagated to testing yet, GI -- 'Shin' -- A device for finding furniture in the dark. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568608: Regression: Slow VT switching
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 Ron. I'll have to either wait for spring break, or the next upload (more likely the latter). Will let you know if the problem persists or not after that. GI -- 100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD 33. I won't require high-ranking female members of my organization to wear a stainless-steel bustier. Morale is better with a more casual dress-code. Similarly, outfits made entirely from black leather will be reserved for formal occasions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
