Bug#874051: swami 2.0.0-svn389-5 seg faults with error 4 in libgobject-2.0.so.0.5304.0
Package: swami Version: 2.0.0+svn389-5 Followup-For: Bug #874051 Dear Maintainer, The segfault seems to be related to the fluidsynth_plugin.so plugin. If I rename this plugin the crash no longer happens (there are other warnings then). Here is a stacktrace from gdb when the segfault happens. Sorry, I don't have swami debug symbols. (gdb) run Starting program: /usr/bin/swami [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". libswami-Message: 01:09:24.220: Loading plugins from /usr/lib/swami libswami-Message: 01:09:24.322: Loaded 4 plugins Program received signal SIGSEGV, Segmentation fault. 0x775d6b7d in g_type_fundamental () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (gdb) bt #0 0x775d6b7d in g_type_fundamental () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #1 0x775ba851 in g_object_new_with_properties () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #2 0x775bb581 in g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x77d4e9cc in () at /usr/lib/x86_64-linux-gnu/libswamigui.so.0 #4 0x775d6677 in g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x775b9398 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x775bab15 in g_object_new_with_properties () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x775bb581 in g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x77d4ff6a in swamigui_root_new () at /usr/lib/x86_64-linux-gnu/libswamigui.so.0 #9 0x5445 in main () Interestingly the segfault does not happen when swami is running within valgrind. valgrind also does not show any warnings that might explain the segfault. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages swami depends on: ii libc6 2.27-6 ii libfftw3-single33.3.8-2 ii libfluidsynth1 1.1.11-1 ii libglib2.0-02.58.1-2 ii libgnomecanvas2-0 2.30.3-4 ii libgtk2.0-0 2.24.32-3 ii libinstpatch-1.0-0 1.0.0-7 ii libswami0 2.0.0+svn389-5 Versions of packages swami recommends: ii jackd 5 swami suggests no packages. -- debconf-show failed
Bug#909818: firefox: Web Content is eating nearly 100% CPU, several of them
Package: firefox
Version: 62.0.2-1
Followup-For: Bug #909818
Dear Maintainer,
I can confirm the CPU-eating problem with firefox.
It might be related to the desktop environment. In my case I use XFCE and
the CPU eating problem goes away if I kill xfsettingsd.
stracing the "Web Conntent"-Process I see that firefox seems to do lots of
sendmsg() with references to font related files, not sure if this maybe is
related to fontconfig.
--- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_errno=ENOTDIR,
si_call_addr=0x7fc4874a1dbe, si_syscall=__NR_openat, si_arch=AUDIT_ARCH_X86_64}
---
socketpair(AF_UNIX, SOCK_SEQPACKET, 0, [35, 37]) = 0
sendmsg(30, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=16},
{iov_base="/usr/share/fonts/cmap/adobe-cns1"..., iov_len=51}, {iov_base=NULL,
iov_len=0}], msg_iovlen=3, msg_control=[{cmsg_len=20, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_RIGHTS, cmsg_data=[37]}], msg_controllen=24, msg_flags=0},
MSG_NOSIGNAL) = 67
close(37) = 0
recvmsg(35, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\354\377\377\377", iov_len=4}], msg_iovlen=1,
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 4
close(35) = 0
rt_sigreturn({mask=[]}) = -1 ENOTDIR (Not a directory)
openat(AT_FDCWD, "/usr/share/fonts/cmap/adobe-cns1/resource.frk/Adobe-CNS1-6",
O_RDONLY) = 257
--- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_errno=ENOTDIR,
si_call_addr=0x7fc4874a1dbe, si_syscall=__NR_openat, si_arch=AUDIT_ARCH_X86_64}
---
socketpair(AF_UNIX, SOCK_SEQPACKET, 0, [35, 37]) = 0
sendmsg(30, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=16},
{iov_base="/usr/share/fonts/cmap/adobe-cns1"..., iov_len=59}, {iov_base=NULL,
iov_len=0}], msg_iovlen=3, msg_control=[{cmsg_len=20, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_RIGHTS, cmsg_data=[37]}], msg_controllen=24, msg_flags=0},
MSG_NOSIGNAL) = 75
close(37) = 0
recvmsg(35, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\376\377\377\377", iov_len=4}], msg_iovlen=1,
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 4
close(35) = 0
rt_sigreturn({mask=[]}) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/fonts/cmap/adobe-cns1/.resource/Adobe-CNS1-6",
O_RDONLY) = 257
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages firefox depends on:
ii debianutils 4.8.6
ii fontconfig2.13.1-1
ii libatk1.0-0 2.30.0-1
ii libc6 2.27-6
ii libcairo-gobject2 1.15.12-1
ii libcairo2 1.15.12-1
ii libdbus-1-3 1.12.10-1
ii libdbus-glib-1-2 0.110-3
ii libevent-2.1-62.1.8-stable-4
ii libffi6 3.2.1-8
ii libfontconfig12.13.1-1
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.2.0-7
ii libgdk-pixbuf2.0-02.38.0+dfsg-6
ii libglib2.0-0 2.58.1-2
ii libgtk-3-03.24.1-2
ii libjsoncpp1 1.7.4-3
ii libnspr4 2:4.20-1
ii libnss3 2:3.39-1
ii libpango-1.0-01.42.4-3
ii libsqlite3-0 3.25.2-1
ii libstartup-notification0 0.12-5
ii libstdc++68.2.0-7
ii libvpx5 1.7.0-3
ii libx11-6 2:1.6.6-1
ii libx11-xcb1 2:1.6.6-1
ii libxcb-shm0 1.13-3
ii libxcb1 1.13-3
ii libxcomposite11:0.4.4-2
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes31:5.0.3-1
ii libxrender1 1:0.9.10-1
ii libxt61:1.1.5-1
ii procps2:3.3.15-2
ii zlib1g1:1.2.11.dfsg-1
Versions of packages firefox recommends:
ii libavcodec57 7:3.4.3-1
ii libavcodec58 7:4.0.2-2+b1
Versions of packages firefox suggests:
ii fonts-lmodern 2.004.5-5
ii fonts-stix [otf-stix] 1.1.1-4
ii libcanberra0 0.30-6
ii libgssapi-krb5-2 1.16-2
ii libgtk2.0-02.24.32-3
ii pulseaudio 12.2-2
-- debconf-show failed
Bug#746005: lilypond: please migrate to guile-2.0
Package: lilypond Followup-For: Bug #746005 Dear Maintainer, Small followup to my previous mail. I managed to miss a whole lot of recent discussion in the bug report and was under the impression that nobody cared. I apologize for being pushy. Thanks, Simon -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lilypond depends on: ii ghostscript9.19~dfsg-3 ii guile-1.8 1.8.8+1-10+b1 ii guile-1.8-libs 1.8.8+1-10+b1 ii libc6 2.24-5 ii libfontconfig1 2.11.0-6.7 ii libfreetype6 2.6.3-3+b1 ii libgcc11:6.2.0-9 ii libglib2.0-0 2.50.1-1 ii libgmp10 2:6.1.1+dfsg-1 ii libltdl7 2.4.6-2 ii libpango-1.0-0 1.40.3-3 ii libpangoft2-1.0-0 1.40.3-3 ii libstdc++6 6.2.0-9 ii lilypond-data 2.18.2-4.1 pn python:any Versions of packages lilypond recommends: ii lilypond-doc2.18.2-4.1 ii texlive-latex-base 2016.20161008-1 lilypond suggests no packages. -- debconf-show failed
Bug#746005: lilypond: please migrate to guile-2.0
Package: lilypond Version: 2.18.2-4.1 Followup-For: Bug #746005 Dear Maintainer, Please note, that guile-1.8 has been removed from the debian unstable release and hence lilypond (which has a hard dependency on it) is currently not installable (I currently try to keep the old guile packages around). Please consider consider putting a little more weight on the transition to guile-2.0. Thanks, Simon -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lilypond depends on: ii ghostscript9.19~dfsg-3 ii guile-1.8 1.8.8+1-10+b1 ii guile-1.8-libs 1.8.8+1-10+b1 ii libc6 2.24-5 ii libfontconfig1 2.11.0-6.7 ii libfreetype6 2.6.3-3+b1 ii libgcc11:6.2.0-9 ii libglib2.0-0 2.50.1-1 ii libgmp10 2:6.1.1+dfsg-1 ii libltdl7 2.4.6-2 ii libpango-1.0-0 1.40.3-3 ii libpangoft2-1.0-0 1.40.3-3 ii libstdc++6 6.2.0-9 ii lilypond-data 2.18.2-4.1 pn python:any Versions of packages lilypond recommends: ii lilypond-doc2.18.2-4.1 ii texlive-latex-base 2016.20161008-1 lilypond suggests no packages. -- debconf-show failed
Bug#796201: audacious : Segmentation fault
Package: audacious Version: 3.5-2 Followup-For: Bug #796201 Dear Maintainer, I can confirm this bug. Here is a backtrace from gdb: simon@mezzanine:~$ gdb audacious GNU gdb (Debian 7.9.1-1) 7.9.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from audacious...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/audacious [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffee44e700 (LWP 28205)] [New Thread 0x7fffeda47700 (LWP 28206)] Program received signal SIGSEGV, Segmentation fault. 0x7fffe47c91fc in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x7fffe47c91fc in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x7fffd7c12717 in ReSIDfpBuilder::create(unsigned int) () at /usr/lib/x86_64-linux-gnu/libsidplayfp.so.3 #2 0x7fffd8edf064 in xs_sidplayfp_init () at /usr/lib/x86_64-linux-gnu/audacious/Input/sid.so #3 0x7fffd8ee06be in xs_init () at /usr/lib/x86_64-linux-gnu/audacious/Input/sid.so #4 0x00418b75 in _start () It might be related to some libc incompability thing. Bye, Simon -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages audacious depends on: ii audacious-plugins3.5-1+b4 ii dbus 1.8.20-1 ii dbus-x11 1.8.20-1 ii gtk2-engines-pixbuf 2.24.28-1 ii libaudcore2 3.5-2 ii libc62.19-19 ii libgdk-pixbuf2.0-0 2.31.5-1 ii libglib2.0-0 2.44.1-1.1 ii libgtk-3-0 3.16.6-1 Versions of packages audacious recommends: ii unzip 6.0-18 audacious suggests no packages. -- no debconf information
Bug#788427: findutils: find -size gives wrong results for 'M' units
Andreas Metzler (ametz...@bebt.de) wrote: How many units sized one Megabyte each is a 512k sized file using? a) 0 b) 1 c) something else Obviously b. It uses some space, so it cannot be a). Ok. I see how it does that. I just hope that this has some historical reasoning relating to different media block sizes. Not sure if there are any practical purposes for this behaviour. Treating the letters as multiplicative shortcuts would be more useful to me. But I guess for compatibility reasons this cannot be changed. Thanks for clearing this up. Bye, Simon -- si...@budig.de http://simon.budig.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788427: findutils: find -size gives wrong results for 'M' units
Package: findutils Version: 4.4.2-9+b1 Severity: important Dear Maintainer, The -size option to find behaves wrongly for the 'M' units. Not sure what is going on there: simon@mezzanine:/tmp/test$ dd if=/dev/zero of=fump.bin bs=1M count=1 1+0 records in 1+0 records out 1048576 bytes (1.0 MB) copied, 0.00309158 s, 339 MB/s simon@mezzanine:/tmp/test$ dd if=/dev/zero of=bla.bin bs=512k count=1 1+0 records in 1+0 records out 524288 bytes (524 kB) copied, 0.00147233 s, 356 MB/s simon@mezzanine:/tmp/test$ find . -size 1024k ./fump.bin simon@mezzanine:/tmp/test$ find . -size 1M . ./fump.bin ./bla.bin I expect that both find invocations are equivalent and should give the exact same results. The manpage specifies that 'M' are units of 1048576 = 1024 * 1024 = 1024k bytes. It is totally unexpeced to me that this also returns the (smaller) bla.bin file. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages findutils depends on: ii libc6 2.19-18 findutils recommends no packages. Versions of packages findutils suggests: ii mlocate 0.26-1 -- 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#784796: blender: NDOF using spacenavd driver works in 2.72 (2014-12-03) but not 2.74 after update
Matteo F. Vescovi (m...@debian.org) wrote: On May 31, 2015 4:45 AM, Simon Budig si...@budig.de wrote: Package: blender Version: 2.74+dfsg0-2+b1 Followup-For: Bug #784796 The missing support for spacenaved is most likely related to the package being built without WITH_INPUT_NDOF=ON (which unfortunately defaults to OFF). I'll try to rebuild at the beginning of next week and upload a new revision with the feature enabled. Thanks for reporting. I can confirm that this did the trick for me. Attached is the change I did to debian/rules. Thanks! Simon -- si...@budig.de http://simon.budig.de/ --- debian/rules.orig 2015-05-31 04:28:16.0 +0200 +++ debian/rules 2015-05-31 04:30:03.0 +0200 @@ -27,6 +27,7 @@ -DWITH_IMAGE_OPENJPEG=ON \ -DWITH_FFTW3=ON \ -DWITH_GAMEENGINE=ON \ + -DWITH_INPUT_NDOF=ON \ -DWITH_JACK=ON \ -DWITH_PLAYER=ON \ -DWITH_INSTALL_PORTABLE=OFF \
Bug#784796: blender: NDOF using spacenavd driver works in 2.72 (2014-12-03) but not 2.74 after update
Package: blender Version: 2.74+dfsg0-2+b1 Followup-For: Bug #784796 Dear Maintainer, The missing support for spacenaved is most likely related to the package being built without WITH_INPUT_NDOF=ON (which unfortunately defaults to OFF). my spacenavd is at version ii spacenavd 0.6-1amd64daemon for using 3D input devices The package available at blender.org works with the debian unstable spacenavd out of the box. I am right now unable to rebuild the package so I can't really test if adding the -DWITH_INPUT_NDOF=ON to the debian/rules file really fixes it, but I'll gladly give feedback on newer package versions. Thanks, Simon -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages blender depends on: ii blender-data 2.74+dfsg0-2 ii fonts-droid1:4.4.4r2-6 ii libavcodec56 6:11.3-3+b3 ii libavdevice55 6:11.3-3+b3 ii libavformat56 6:11.3-3+b3 ii libavutil546:11.3-3+b3 ii libboost-date-time1.55.0 1.55.0+dfsg-3 ii libboost-filesystem1.55.0 1.55.0+dfsg-3 ii libboost-locale1.55.0 1.55.0+dfsg-3 ii libboost-regex1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libboost-thread1.55.0 1.55.0+dfsg-3 ii libc6 2.19-18 ii libfftw3-double3 3.3.4-2 ii libfreetype6 2.5.2-4 ii libgcc11:5.1.1-7 ii libgl1-mesa-glx [libgl1] 10.5.5-1 ii libglew1.101.10.0-3 ii libglu1-mesa [libglu1] 9.0.0-2 ii libgomp1 5.1.1-7 ii libilmbase61.0.1-6.1 ii libjack0 [libjack-0.116] 1:0.124.1+20140122git5013bed0-3 ii libjpeg62-turbo1:1.4.0-7 ii libjs-jquery 1.7.2+dfsg-3.2 ii libjs-jquery-ui1.10.1+dfsg-1 ii libopenal1 1:1.16.0-3 ii libopencolorio11.0.9~dfsg0-3+b1 ii libopenexr61.6.1-8 ii libopenimageio1.5 1.5.15~dfsg0-1 ii libopenjpeg5 1:1.5.2-3 ii libpng12-0 1.2.50-2+b2 ii libpython3.4 3.4.3-6 ii libsndfile11.0.25-9.1 ii libstdc++6 5.1.1-7 ii libswscale36:11.3-3+b3 ii libtiff5 4.0.3-13 ii libx11-6 2:1.6.3-1 ii libxi6 2:1.7.4-1+b2 ii libxxf86vm11:1.1.4-1 ii zlib1g 1:1.2.8.dfsg-2+b1 blender recommends no packages. blender 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#718360: Missing gtk/gdk doc in devhelp
Package: libgtk2.0-doc Version: 2.24.20-1 Followup-For: Bug #718360 Dear Maintainer, I can confirm that renaming the symlinks in /usr/share/gtk-doc/html/ to .../gtk2 and .../gdk2 resolves this issue. Please consider fixing this. Thanks, Simon -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash libgtk2.0-doc depends on no packages. Versions of packages libgtk2.0-doc recommends: ii libatk1.0-doc2.8.0-2 ii libglib2.0-doc 2.36.4-1 ii libpango1.0-doc 1.32.5-5 Versions of packages libgtk2.0-doc suggests: ii devhelp 3.8.2-2 -- 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#575250: libpango1.0-0: Pango 1.26.2 introduces kerning bug
Package: libpango1.0-0
Version: 1.26.2-1
Severity: important
Tags: patch
The debian package of libpango inherits a bug from upstream that has severe
implications on the usability of all applications that use pango layouts
for text layout. For example inkscape documents change appearance since
text flows differently for certain fonts.
The bug (upstream bug 605655 in gnome-bugzilla) has been fixed upstream with
the commit 9cac172f82dd492d068590434199989021be236e in the pango repository on
gnome.org, but I believe it to be important enough to be backported, since no
release containing the fix has been done yet.
The commit applies cleanly to the source tree from the debian package,
I have attached it for your convenience.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32.2 (PREEMPT)
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 libpango1.0-0 depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-2 The Cairo 2D vector graphics libra
ii libfontconfig1 2.8.0-2 generic font configuration library
ii libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii libglib2.0-02.22.4-1 The GLib library of C routines
ii libpango1.0-common 1.26.2-1 Modules and configuration files fo
ii libthai00.1.14-2 Thai language support library
ii libx11-62:1.3.3-2X11 client-side library
ii libxft2 2.1.14-2 FreeType-based font drawing librar
ii libxrender1 1:0.9.5-2X Rendering Extension client libra
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
libpango1.0-0 recommends no packages.
libpango1.0-0 suggests no packages.
-- no debconf information
commit 9cac172f82dd492d068590434199989021be236e
Author: Behdad Esfahbod beh...@behdad.org
Date: Tue Mar 16 03:46:17 2010 -0400
[HB] Fix the mystery bug!
A couple bugs joined forces to exhibit the mystery behavior of
crashes / infinite loops on OS X / wrong kerning / invalid memory
access. Pooh!
The bugs were involved:
- Wrong pointer math with ValueRecord in PairPosFormat1
- Fallout from avoiding flex arrays, code not correctly updated
to remove sizeof() usage.
We strictly never use sizeof() directly now. And the PairPos code
is cleaned up. Should fix them all. Bugs are:
Bug 605655 - Pango 1.26.2 introduces kerning bug
Bug 611229 - Pango reads from uninitialized memory
Bug 593240 - (pangoosx) Crash / infinite loop with Mac OS X
We were also doing wrong math converting Device adjustments to
hb_position_t. Fallout from FreeType days. Should shift 16, not
6. Fixed that too.
There's still another bug: we don't sanitize Device records
referenced from value records. Fixing that also.
diff --git a/pango/opentype/hb-open-file-private.hh
b/pango/opentype/hb-open-file-private.hh
index dda6b94..0947747 100644
--- a/pango/opentype/hb-open-file-private.hh
+++ b/pango/opentype/hb-open-file-private.hh
@@ -47,6 +47,8 @@ struct TTCHeader;
typedef struct TableDirectory
{
+ static inline unsigned int get_size () { return sizeof (TableDirectory); }
+
inline bool sanitize (SANITIZE_ARG_DEF, const void *base) {
TRACE_SANITIZE ();
return SANITIZE_SELF () SANITIZE (tag)
@@ -108,7 +110,7 @@ typedef struct OffsetTable
public:
inline bool sanitize (SANITIZE_ARG_DEF, const void *base) {
TRACE_SANITIZE ();
-if (!(SANITIZE_SELF () SANITIZE_MEM (tableDir, sizeof (tableDir[0]) *
numTables))) return false;
+if (!(SANITIZE_SELF () SANITIZE_MEM (tableDir, tableDir[0].get_size ()
* numTables))) return false;
unsigned int count = numTables;
for (unsigned int i = 0; i count; i++)
if (!SANITIZE_BASE (tableDir[i], base))
diff --git a/pango/opentype/hb-open-type-private.hh
b/pango/opentype/hb-open-type-private.hh
index f460f1a..06324ee 100644
--- a/pango/opentype/hb-open-type-private.hh
+++ b/pango/opentype/hb-open-type-private.hh
@@ -50,8 +50,8 @@
#define CONST_NEXT(T,X)(*(reinterpret_castconst T
*(CONST_CHARP((X)) + (X).get_size (
#define NEXT(T,X) (*(reinterpret_castT *(CHARP((X)) +
(X).get_size (
-#define CONST_ARRAY_AFTER(T,X) ((reinterpret_castconst T *(CONST_CHARP((X))
+ sizeof (X
-#define ARRAY_AFTER(T,X) ((reinterpret_castT *(CHARP((X)) + sizeof
(X
+#define CONST_ARRAY_AFTER(T,X) ((reinterpret_castconst T *(CONST_CHARP((X))
+ X.get_size (
+#define ARRAY_AFTER(T,X) ((reinterpret_castT *(CHARP((X)) +
X.get_size (
/*
* Class features
@@ -362,6 +362,7 @@ struct Sanitizer
#define DEFINE_INT_TYPE1(NAME,
Bug#347790: xterm: boldFont problem seems related to font encoding
Thomas Dickey ([EMAIL PROTECTED]) wrote:
On Sun, Feb 26, 2006 at 03:20:04AM +0100, Simon Budig wrote:
Package: xterm
Version: 208-3.1
Followup-For: Bug #347790
I too discovered that xterm no longer respects the boldFont ressource.
In my .Xresources file I have these lines:
I can't reproduce this (perhaps some other resource value or command-line
option is relevant).
What information do you need me to provide?
I start xterm with commandline
xterm -si -sk -geometry 80x55
and I have attached the output xrdb -query for both the broken fonts and
for working fonts.
The complete locale settings are:
[EMAIL PROTECTED]:~$ locale
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
If you can provide me a binary of xterm with trace enabled I am willing
to send a log for the different settings.
I hope this helps,
Simon
--
[EMAIL PROTECTED] http://simon.budig.de/
*xterm*title: Terminal
*vt100*font:-misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso10646-1
*vt100*boldFont:
-misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso10646-1
*vt100*saveLines: 5000
*vt100*boldMode:off
*vt100*boldColors: true
*vt100*colorBDMode: true
*vt100*color0: #00
*vt100*color1: #ac
*vt100*color2: #00aa00
*vt100*color3: #ac5500
*vt100*color4: #ac
*vt100*color5: #ac00ac
*vt100*color6: #00aaac
*vt100*color7: #acaaac
*vt100*color8: #525552
*vt100*color9: #ff5552
*vt100*color10: #52ff52
*vt100*color11: #52
*vt100*color12: #5255ff
*vt100*color13: #ff55ff
*vt100*color14: #55
*vt100*color15: #ff
*vt100*foreground: #acaaac
*vt100*background: #00
*charClass:
*mainMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*vtMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*fontMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*tekMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*Menu*foreground: black
; *Menu*font: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-15
URxvt.color0: #00
URxvt.color1: #ac
URxvt.color2: #00aa00
URxvt.color3: #ac5500
URxvt.color4: #ac
URxvt.color5: #ac00ac
URxvt.color6: #00aaac
URxvt.color7: #acaaac
URxvt.color8: #525552
URxvt.color9: #ff5552
URxvt.color10: #52ff52
URxvt.color11: #52
URxvt.color12: #5255ff
URxvt.color13: #ff55ff
URxvt.color14: #55
URxvt.color15: #ff
URxvt.foreground: #acaaac
URxvt.background: #00
URxvt.cursorColor: #FF
URxvt.visualBell: True
URxvt.scrollBar:False
URxvt.scrollTtyOutput: False
URxvt.scrollTtyKeypress:True
URxvt.saveLines:5000
URxvt.title:Terminal
URxvt.cutchars: `Ž()*;[]{|}
; URxvt.font:
-misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-15,xft:bitstream
vera sans mono:pixelsize=13:style=bold,xft:arial unicode
ms:pixelsize=12:style=bold
URxvt.font: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-*-*
URxvt.boldFont: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-15
URxvt.preeditStyle: OverTheSpot,Root,None
URxvt.pointerblank: True
URxvt.lineSpace:2
U*greektoggle_key: VoidSymbol
*xterm*title: Terminal
*vt100*font:-misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-1
*vt100*boldFont:
-misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-1
*vt100*saveLines: 5000
*vt100*boldMode:off
*vt100*boldColors: true
*vt100*colorBDMode: true
*vt100*color0: #00
*vt100*color1: #ac
*vt100*color2: #00aa00
*vt100*color3: #ac5500
*vt100*color4: #ac
*vt100*color5: #ac00ac
*vt100*color6: #00aaac
*vt100*color7: #acaaac
*vt100*color8: #525552
*vt100*color9: #ff5552
*vt100*color10: #52ff52
*vt100*color11: #52
*vt100*color12: #5255ff
*vt100*color13: #ff55ff
*vt100*color14: #55
*vt100*color15: #ff
*vt100*foreground: #acaaac
*vt100*background: #00
*charClass:
*mainMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*vtMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*fontMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*tekMenu*backgroundPixmap:
gradient:vertical?dimension=1start=whiteend=white
*Menu*foreground: black
; *Menu*font: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-15
URxvt.color0: #00
URxvt.color1: #ac
URxvt.color2: #00aa00
URxvt.color3: #ac5500
URxvt.color4: #ac
URxvt.color5: #ac00ac
URxvt.color6: #00aaac
URxvt.color7: #acaaac
Bug#347790: xterm: boldFont problem seems related to font encoding
Package: xterm Version: 208-3.1 Followup-For: Bug #347790 I too discovered that xterm no longer respects the boldFont ressource. In my .Xresources file I have these lines: *vt100*font: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-1 *vt100*boldFont: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso8859-1 *vt100*boldMode: off *vt100*boldColors: true *vt100*colorBDMode: true Now this does not work for some reason. *But* when I change the font to the unicode encoding: *vt100*font: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso10646-1 *vt100*boldFont: -misc-fixed-medium-r-semicondensed-*-*-120-*-*-c-*-iso10646-1 *vt100*boldMode: off *vt100*boldColors: true *vt100*colorBDMode: true then boldMode suddenly starts working for whatever reason. Hope this helps, Simon -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xterm depends on: ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libfontconfig12.3.2-1.1 generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libncurses5 5.5-1 Shared libraries for terminal hand ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxaw8 6.9.0.dfsg.1-4 X Athena widget set library ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxft2 2.1.8.2-3 FreeType-based font drawing librar ii libxmu6 6.9.0.dfsg.1-4 X Window System miscellaneous util ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii xlibs-data6.9.0.dfsg.1-4 X Window System client data ii zlib1g1:1.2.3-9 compression library - runtime Versions of packages xterm recommends: ii xutils6.9.0.dfsg.1-4 X Window System utility programs -- debconf information: * xterm/clobber_xresource_file: true xterm/xterm_needs_devpts: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347384: xterm: URLs are not the only thing you want to select...
Package: xterm Version: 208-3.1 Followup-For: Bug #347384 IMHO the changed charClass resource is a bad idea. It is trivial to doubleclick on the http and drag over the URL. The new setting makes it basically impossible to select e.g. the directory part of a fully qualified filename. Being able to select URLs with a doubleclick requires an awful lot of separator-like characters in them: '/', ':', '=', '' etc. pp. Just for example: Having '' no longer separating makes selecting of table cells in a LaTeX-Document very troublesome. Having '/' no longer separating makes selecting parts of a filename very inconvenient. , is inconvenient for CSV-formatted files (Comma separated values), and so on and so on. *Please* please please revert this change and restore the original behaviour by unsetting the charClass resource. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xterm depends on: ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libfontconfig12.3.2-1.1 generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libncurses5 5.5-1 Shared libraries for terminal hand ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxaw8 6.9.0.dfsg.1-4 X Athena widget set library ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxft2 2.1.8.2-3 FreeType-based font drawing librar ii libxmu6 6.9.0.dfsg.1-4 X Window System miscellaneous util ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii xlibs-data6.9.0.dfsg.1-4 X Window System client data ii zlib1g1:1.2.3-9 compression library - runtime Versions of packages xterm recommends: ii xutils6.9.0.dfsg.1-4 X Window System utility programs -- debconf information: * xterm/clobber_xresource_file: true xterm/xterm_needs_devpts: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339707: gdm: GDM must not mess with the dpi.
Package: gdm Version: 2.8.0.6-2 Followup-For: Bug #339707 Even if gnome messes around with the DPI (wrongly!), this is no reason to do it in gdm as well. You can change the gnome dpi setting at runtime, but you cannot do this with the changed gdm setting, since xdpyinfo will stick to that dpi setting. Applications relying on proper dpi information are doomed to failed and the user is bound to edit config files. Heck, even the explicit configuration of the monitor size in the xorg.conf file gets clobbered. If you need to work around broken autodetection of the display size from the x-server, do it by hardcoding a display size for the x-server in the xorg.conf (DisplaySize keyword in the Monitor section). This is the place where someone would look for that setting. GDM must not mess with this. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages gdm depends on: [...] ii xlibs6.9.0.dfsg.1-4 X Window System client libraries m -- debconf information: gdm/daemon_name: /usr/bin/gdm * shared/default-x-display-manager: gdm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353495: libwine: included FON bitmap font files should be avoided by fontconfig
Package: libwine Version: 0.9-1 Severity: normal The bitmap font files included in the libwine package should not be picked up by fontconfig, since they get rendered invisible in firefox. I stumbled across this when some webpages looked suspiciously empty and I tracked it down to the usage of the MS sans serif font, which gets provided by /usr/share/fonts/wine/sserife.fon. Apparently this file cannot be used by freetype, at least the command ftview ppem /usr/share/fonts/wine/sserife.fon yields empty letters. When selecting this font in gimp it spits out a warning: Pango-WARNING **: Error in FT_Set_Char_Size: 23 As soon as I disable the wine-provided fonts in my ~/.fonts.conf with this entry: ?xml version=1.0? !DOCTYPE fontconfig SYSTEM fonts.dtd fontconfig [...] rejectfont glob/usr/share/fonts/wine/*/glob /rejectfont /fontconfig The problem goes away by making the MS sans serif fonts unavailable to the applications that don't render them correctly. It is a bit hard to figure out which package to report the bug against, freetype should be able to render the .fon files, fontconfig should not pick up .fon files that cannot get rendered by freetype, pango should not warn, but I think the easiest route is to not include the bitmap fonts into the fonts managed by fontconfig. Hence the report against wine. I hope this helps, Simon -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libwine depends on: ii debconf [debconf-2.0] 1.4.67Debian configuration management sy ii libc6 2.3.5-8 GNU C Library: Shared libraries an ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc11:4.0.2-5 GCC support library ii libice66.8.2.dfsg.1-11 Inter-Client Exchange library ii libncurses55.5-1 Shared libraries for terminal hand ii libsm6 6.8.2.dfsg.1-11 X Window System Session Management ii libstdc++6 4.0.2-5 The GNU Standard C++ Library v3 ii libx11-6 6.8.2.dfsg.1-11 X Window System protocol client li ii libxext6 6.8.2.dfsg.1-11 X Window System miscellaneous exte ii libxml22.6.23.dfsg.1-0.1 GNOME XML library ii libxslt1.1 1.1.15-2 XSLT processing library - runtime ii libxxf86dga1 6.8.2.dfsg.1-11 X Direct Graphics Access extension ii libxxf86vm16.8.2.dfsg.1-11 X Video Mode selection library ii xlibs 6.8.2.dfsg.1-11 X Window System client libraries m ii zlib1g 1:1.2.3-9 compression library - runtime libwine recommends no packages. -- debconf information: wine/move_to_fhs: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307573: libcairo1-dev: Glitz backend is missing
Package: libcairo1-dev Version: 0.4.0-1 Severity: normal The Glitz backend is missing in libcairo. Although libglitz is available as a debian package there seems to be no way to use it with the glitz backend of cairo. I don't know how these compile-time dependencies ought to get handled and I understand that a dependency on glitz might result in an unwanted dependency on xlibmesa-gl, but it would be very nice, if there were a way to actually use cairo together with glitz. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libcairo1-dev depends on: ii libcairo1 0.4.0-1Multi-platform 2D graphics library ii libfontconfig1-dev2.3.1-2generic font configuration library ii libfreetype6-dev 2.1.7-2.4 FreeType 2 font engine, developmen ii libpixman1-dev0.1.4-1Cairo pixel manipulation library d ii libpng12-dev 1.2.8rel-1 PNG library - development ii libxrender-dev0.8.3-7X Rendering Extension client libra -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301593: gromit: Updated Manpage for Gromit
Oh, the bugtracker should get a copy as well... - Forwarded message from Simon Budig [EMAIL PROTECTED] - From: Simon Budig [EMAIL PROTECTED] To: Pierre Chifflier [EMAIL PROTECTED] Date: Sat, 9 Apr 2005 19:09:15 +0200 Subject: Re: Bug#301593: gromit: Updated Manpage for Gromit Pierre Chifflier ([EMAIL PROTECTED]) wrote: Thank you for updating the manpage. However, manpages are not funny to merge manually :/ Could you please send either the complete manpage, or a diff ? Uh, this *is* the complete manpage - or what did I miss? Anyway, Ill attach it as a MIME attachment, which is easier to handle anyway (I am not sure how to create an attachment with reportbug...) Bye, Simon -- [EMAIL PROTECTED] http://simon.budig.de/ .\ Hey, vim: ft=nroff .TH GROMIT 1 January 16, 2005 .\ Please adjust this date whenever revising the manpage. .\ .\ Some roff macros, for reference: .\ .nhdisable hyphenation .\ .hyenable hyphenation .\ .ad l left justify .\ .ad b justify to both left and right margins .\ .nfdisable filling .\ .fienable filling .\ .brinsert line break .\ .sp ninsert n+1 empty lines .\ for manpage-specific macros, see man(7) .SH NAME Gromit \- Presentation helper to make annotations on screen .SH SYNOPSIS .B gromit .RI [ options ] .br .SH DESCRIPTION \fBGromit\fP enables you to make annotations on your screen. It can run in the background and be activated on demand to let you draw over all your currently running applications. The drawing will stay on screen as long as you want, you can continue to use your applications while the drawing is visible. .br \fBGromit\fP is XInput-Aware, so if you have a graphic tablet you can draw lines with different strength, color, erase things, etc. .br Since you typically want to use the program you are demonstrating and highlighting something is a short interruption of you workflow, Gromit is activated by either a hotkey or a repeated invokation of Gromit (the latter can e.g. used by other applications or your windowmanager). .br .SH KEYBOARD CONTROL By default, Gromit grabs the Pause key (this can be change using the --key option), making it unavailable to other application. The available shortcuts are: .TP .B Pause toggle painting .TP .B SHIFT-Pause clear screen .TP .B CTRL-Pause toggle visibility .TP .B ALT-Pause quit Gromit .PP .SH OPTIONS (STARTUP) A short summary of the available commandline arguments for invoking Gromit, see below for the options to control an already running Gromit process: .TP .B \-a, \-\-active start Gromit and immediately activate it. .TP .B \-k keysym, \-\-key keysym will change the key used to grab the mouse. keysym can e.g. be Pause, F12, Control_R or Print. To determine the keysym for different keys you can use the \fBxev\fP(1) command. You can specify none to prevent Gromit from grabbing a key. .TP .B \-K keycode, \-\-keycode keycode will change the key used to grab the mouse. Under rare circumstances identifying the key with the keysym can fail. You can then use the keycode to specify the key uniquely. To determine the keycode for different keys you can use the \fBxev\fP(1) command. .TP .B \-d, \-\-debug gives some debug output. .SH OPTIONS (CONTROL) A sort summary of the available commandline arguments to control an already running Gromit process, see above for the options available to start Gromit. .TP .B \-q, \-\-quit will cause the main Gromit process to quit. .TP .B \-t, \-\-toggle will toggle the grabbing of the cursor. .TP .B \-v, \-\-visibility will toggle the visibility of the window. .TP .B \-c, \-\-clear will clear the screen. .SH BUGS Gromit may drastically slow down your X-Server, especially when you draw very thin lines. It makes heavily use of the shape extension, which is quite expensive if you paint a complex pattern on screen. Especially terminal-programs tend to scroll incredibly slow if something is painted over their window. There is nothing I can do about this. .br Gromit partially disables DnD, since it lays a transparent window across the whole screen and everything gets dropped to this (invisible) window. Gromit tries to minimize this effect: When you clear the screen the shaped window will be hidden. It will be resurrected, when you want to paint something again. However: The window does not hide, if you erase everything with the eraser tool, you have to clear the screen explicitely with the gromit --clear command or hide Gromit with gromit --visibility. .SH AUTHOR Simon Budig [EMAIL PROTECTED] .PP This manual page was written by Pierre Chifflier [EMAIL PROTECTED] and Simon Budig. - End forwarded message - -- [EMAIL PROTECTED] http://simon.budig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301593: gromit: Updated Manpage for Gromit
Package: gromit Version: 20041213-1 Followup-For: Bug #301593 I already have an updated manpage in my sources but I am not sure if this warrants a new release. Please feel free to include this text in the next package of Gromit. - snip - .\ Hey, vim: ft=nroff .TH GROMIT 1 January 16, 2005 .\ Please adjust this date whenever revising the manpage. .\ .\ Some roff macros, for reference: .\ .nhdisable hyphenation .\ .hyenable hyphenation .\ .ad l left justify .\ .ad b justify to both left and right margins .\ .nfdisable filling .\ .fienable filling .\ .brinsert line break .\ .sp ninsert n+1 empty lines .\ for manpage-specific macros, see man(7) .SH NAME Gromit \- Presentation helper to make annotations on screen .SH SYNOPSIS .B gromit .RI [ options ] .br .SH DESCRIPTION \fBGromit\fP enables you to make annotations on your screen. It can run in the background and be activated on demand to let you draw over all your currently running applications. The drawing will stay on screen as long as you want, you can continue to use your applications while the drawing is visible. .br \fBGromit\fP is XInput-Aware, so if you have a graphic tablet you can draw lines with different strength, color, erase things, etc. .br Since you typically want to use the program you are demonstrating and highlighting something is a short interruption of you workflow, Gromit is activated by either a hotkey or a repeated invokation of Gromit (the latter can e.g. used by other applications or your windowmanager). .br .SH KEYBOARD CONTROL By default, Gromit grabs the Pause key (this can be change using the --key option), making it unavailable to other application. The available shortcuts are: .TP .B Pause toggle painting .TP .B SHIFT-Pause clear screen .TP .B CTRL-Pause toggle visibility .TP .B ALT-Pause quit Gromit .PP .SH OPTIONS (STARTUP) A short summary of the available commandline arguments for invoking Gromit, see below for the options to control an already running Gromit process: .TP .B \-a, \-\-active start Gromit and immediately activate it. .TP .B \-k keysym, \-\-key keysym will change the key used to grab the mouse. keysym can e.g. be Pause, F12, Control_R or Print. To determine the keysym for different keys you can use the \fBxev\fP(1) command. You can specify none to prevent Gromit from grabbing a key. .TP .B \-K keycode, \-\-keycode keycode will change the key used to grab the mouse. Under rare circumstances identifying the key with the keysym can fail. You can then use the keycode to specify the key uniquely. To determine the keycode for different keys you can use the \fBxev\fP(1) command. .TP .B \-d, \-\-debug gives some debug output. .SH OPTIONS (CONTROL) A sort summary of the available commandline arguments to control an already running Gromit process, see above for the options available to start Gromit. .TP .B \-q, \-\-quit will cause the main Gromit process to quit. .TP .B \-t, \-\-toggle will toggle the grabbing of the cursor. .TP .B \-v, \-\-visibility will toggle the visibility of the window. .TP .B \-c, \-\-clear will clear the screen. .SH BUGS Gromit may drastically slow down your X-Server, especially when you draw very thin lines. It makes heavily use of the shape extension, which is quite expensive if you paint a complex pattern on screen. Especially terminal-programs tend to scroll incredibly slow if something is painted over their window. There is nothing I can do about this. .br Gromit partially disables DnD, since it lays a transparent window across the whole screen and everything gets dropped to this (invisible) window. Gromit tries to minimize this effect: When you clear the screen the shaped window will be hidden. It will be resurrected, when you want to paint something again. However: The window does not hide, if you erase everything with the eraser tool, you have to clear the screen explicitely with the gromit --clear command or hide Gromit with gromit --visibility. .SH AUTHOR Simon Budig [EMAIL PROTECTED] .PP This manual page was written by Pierre Chifflier [EMAIL PROTECTED] and Simon Budig. - snip - The Manpage still should contain a section on the configuration file format. I need to ponder about this a bit, but basically it should be the same as in the README. To change the error messages to something more meaningful is pretty trivial, I'll change it right now to this: Unknown Option to control a running Gromit process: and Unknown Option for Gromit startup: If someone has better suggestions for this text please tell me about it. Bye, Simon -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages gromit depends on: ii libatk1.0-0 1.8.0-4
