Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
Thorsten Bonow writes:
[...]
But what's POSIX take on this? I couldn't find anything. Is this a
bug in dash or in setupcon?
I'm stupid[1]. It's a bug in setupcon, POSIX requires the space:
"The syntax of the shell command language has an ambiguity for
expansions beginning with "$((", which can introduce an arithmetic
expansion or a command substitution that starts with a subshell.
Arithmetic expansion has precedence; that is, the shell shall first
determine whether it can parse the expansion as an arithmetic
expansion and shall only parse the expansion as a command substitution
if it determines that it cannot parse the expansion as an arithmetic
expansion. The shell need not evaluate nested expansions when
performing this determination. If it encounters the end of input
without already having determined that it cannot parse the expansion
as an arithmetic expansion, the shell shall treat the expansion as an
incomplete arithmetic expansion and report a syntax error. A
conforming application shall ensure that it separates the "$(" and '('
into two tokens (that is, separate them with white space) in a command
substitution that starts with a subshell. For example, a command
substitution containing a single subshell could be written as:
$( (command) )"
Footnotes:
[1]
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
Package: console-setup
Version: 1.225
Severity: grave
After the upgrade from 1.223, console-setup.service failed to start
due
to a syntax error in the setupcon script:
,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`
It looks like dash does not like the construct in line 907 where
there
is an opening '$((' but the closing parentheses are split.
,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`
I tried
dash << 'EOF'[15:28:53]
if $( (true) 2>/dev/null); then
echo "42"
fi
EOF
42
which only works in dash because of the added space between the
command substitution $(...) and the subshell (...).
Does dash think it has to do arithmetic expansion "$((...))"?
bash and zsh in sh mode accept nesting a subshell within the command
substitution without an extra space. In the last version of the
script, backticks were used, circumventing this issue.
But what's POSIX take on this? I couldn't find anything. Is this a
bug in dash or in setupcon?
Toto
PS: To the proposal of a cleanup: 'checkbashisms' doesn't return any
errors, but IMHO, at least closing (double) quotes on
a line of their own should be fixed:
$ cat /bin/setupcon | grep -n "^\(\"\|'\)$"
[15:47:07]
87:'
145:"
148:"
190:"
193:"
208:"
Bug#1054348: parcellite: windows fail to appear
Package: parcellite Version: 1.2.1-7 Severity: grave X-Debbugs-Cc: none, Thorsten Bonow Dear Maintainer, when starting parcellite with "parcellite" or "parcellite -n" (I'm using LarsWM, a window manager without icon support), I can no longer access the programm. The hotkeys (C-M-ö for the clipboard history, C-M-ß for the persistent history or C-M-ä for actions) don't open any windows. Downgrading the parcellite package to parcellite_1.2.1-5_amd64.deb solves the problem for me! The new version 1.2.1-7 gives the following output after startup: Flag 0x0001, status 0, EXIT 1 STAT 0 Flag 0x0001, status 0, EXIT 1 STAT 0 Upon pressing a hotkey, this output is generated: (parcellite:660159): Gdk-CRITICAL **: 12:45:55.482: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Thx for any help. Toto -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages parcellite depends on: ii libc6 2.37-12 ii libglib2.0-02.78.0-2 ii libgtk-3-0 3.24.38-5 ii libpango-1.0-0 1.51.0+ds-2 ii libx11-62:1.8.7-1 parcellite recommends no packages. parcellite suggests no packages. -- debconf-show failed
Bug#1028091: mc: Subshell not starting on heavily modified zsh shell
Hi, this has already been fixed upstream in version 4.8.29: https://midnight-commander.org/ticket/3121 Toto -- Sent from my GNU Emacs running on GNU/Linux
Bug#1017817: emacs: new release seems to have funny ideas about byte-compiling process
(Also a bit surprised this hasn't already been reported, and thus afraid it's some quirk of my installation, but if not it's *got* to be biting some other folks as least as badly.) Hi, this has happened to me, too. OOM killer didn't prevent the system from becoming totally unresponsive. (I was afk for a few hours.) This appeared to have happened during compilation of the following packages: cdargs emms elpa-bind-chord ecb De-installing these packages made the emacs package installation possible on my system. Afterwards I was able to install the packages mentioned above one after the other, only the ecb package still leads to the "thundering compilation herd"... GNU Emacs 28 spits out a lot of warnings once in a while but runs smoothly otherwise. (I haven't updated to 1:28.1+1-2 yet.) Thanks for the good work! Toto
Bug#962847: exim4: takes forever to send a mail after sleeping
Hi, I can reproduce the bug on my system, but I think it's GNU Emacs related: After I put my system to sleep for 5 minutes, sending a test mail with GNU Emacs took 5 minutes, while sending one with "/usr/bin/bsd-mailx" was possible without the lag. The bug bit me for 2 days, I wasn't able to send mails in the morning---after my system was suspended during the night. A reboot fixed the problem. Everything else I tried failed. I'm using GNU Emacs with the Mew Mailer (package "mew-beta") on an up to date Debian Sid system (exim 4.94-2, configured with my provider's mail server as smarthost). During the last 5 minute test, the logs looked normal, the other mails stuck created something like this every 30 minutes: "2020-06-16 13:22:18 1jl9X4-005JlN-Vw Spool file for 1jl9X4-005JlN-Vw is locked (another process is handling this message)" On sending a mail which becomes stuck, Mew displays "Sending in background..." forever. After restarting GNU Emacs and Mew, I can see the mail in the +queue folder; sending it is possible after a system reboot. I'm not an expert but I will try to look into the problem. Thanks, Toto -- Sent from my GNU Emacs running on GNU/Linux
Bug#962275: snort: Failed to start LSB
Javier Fernandez-Sanguino writes: Could you please confirm if the 'eth0' interface is available in the system? One possible reason for startup failing is that the interface is not the correct one (administrator should configure the proper one via debconf). Dear Javier, the 'eth0' interface is available: $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 74:d4:35:f8:9a:70 brd ff:ff:ff:ff:ff:ff altname enp0s25 inet 192.168.1.27/24 brd 192.168.1.255 scope global dynamic eth0 valid_lft 27084sec preferred_lft 27084sec inet6 fe80::76d4:35ff:fef8:9a70/64 scope link valid_lft forever preferred_lft forever Best regards Toto
Bug#962275: snort: Failed to start LSB
Package: snort Version: 2.9.15.1-2 Severity: grave Dear Maintainer, installation of 'snort' fails with a subprocess error (fresh install, /etc/snort doesn't exist before installation. Accepting the propose d network settings: 192.168.0.0/16). Aptitude output: ** Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done Preconfiguring packages ... Snort configuration: interface default not set, using 'eth0' Selecting previously unselected package snort-common-libraries. (Reading database ... 649619 files and directories currently installe d.) Preparing to unpack .../0-snort-common-libraries_2.9.15.1-2_amd64.deb ... Unpacking snort-common-libraries (2.9.15.1-2) ... Preparing to unpack .../1-snort-rules-default_2.9.15.1-2_all.deb ... Unpacking snort-rules-default (2.9.15.1-2) ... Preparing to unpack .../2-snort-common_2.9.15.1-2_all.deb ... Unpacking snort-common (2.9.15.1-2) ... Selecting previously unselected package libdaq2. Preparing to unpack .../3-libdaq2_2.0.7-2_amd64.deb ... Unpacking libdaq2 (2.0.7-2) ... Selecting previously unselected package snort. Preparing to unpack .../4-snort_2.9.15.1-2_amd64.deb ... Unpacking snort (2.9.15.1-2) ... Preparing to unpack .../5-oinkmaster_2.0-4_all.deb ... Unpacking oinkmaster (2.0-4) ... Setting up oinkmaster (2.0-4) ... Setting up snort-common (2.9.15.1-2) ... Setting up libdaq2 (2.0.7-2) ... Setting up snort-rules-default (2.9.15.1-2) ... Setting up snort-common-libraries (2.9.15.1-2) ... Setting up snort (2.9.15.1-2) ... Snort configuration: interface default not set, using 'eth0' WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) since Fri 2020-06-05 13:41:4 3 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 259261 ExecStart=/etc/init.d/snort start (code=exited, status=1/FAILURE) Jun 05 13:41:43 holly systemd[1]: Starting LSB: Lightweight network i ntrusion detection system... Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/snort/snort.conf Jun 05 13:41:43 holly snort[259273]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/sno Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface con Jun 05 13:41:43 holly snort[259275]: Starting Jun 05 13:41:43 holly systemd[1]: snort.service: Control process exit ed, code=exited, status=1/FAILURE Jun 05 13:41:43 holly systemd[1]: snort.service: Failed with result ' exit-code'. Jun 05 13:41:43 holly systemd[1]: Failed to start LSB: Lightweight ne twork intrusion detection system. dpkg: error processing package snort (--configure): installed snort package post-installation script subprocess returne d error exit status 1 Processing triggers for systemd (245.5-3) ... Processing triggers for man-db (2.9.2-1) ... Processing triggers for libc-bin (2.30-8) ... Errors were encountered while processing: snort [ Rootkit Hunter version 1.4.6 ] File updated: searched for 181 files, found 152 needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up snort (2.9.15.1-2) ... Snort configuration: interface default set, using eth0 WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) since Fri 2020-06-05 13:41:5 4 CEST; 4ms ago Docs: man:systemd-sysv-generator(8) Process: 269896 ExecStart=/etc/init.d/snort start (code=exited, status=1/FAILURE) Jun 05 13:41:54 holly systemd[1]: Starting LSB: Lightweight network i ntrusion detection system... Jun 05 13:41:54 holly snort[269896]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/snort/snort.conf Jun 05 13:41:54 holly snort[269907]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/sno Jun 05 13:41:54 holly snort[269896]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface con Jun 05 13:41:54 holly snort[269909]: Starting Jun 05 13:41:54 holly
Bug#945920: Random Chromium crashes
On Mon, 30 Dec 2019 13:50:36 -0800 Eloston wrote: [...] $ ./debian/rules get-orig-source Hi, this fails for me: [...] test ! -e debian || rm -rf debian cp -r ../debian ./ cp: cannot stat '../debian': No such file or directory make: *** [debian/rules:212: get-orig-source] Error 1 ./debian/rules get-orig-source 441.08s user 24.95s system 92% cpu 8:25.08 total Files and directories: $ ll total 12K drwxr-sr-x 50 toto staff 4.0K Dec 31 14:40 chromium-79.0.3945.79 -rw-r--r-- 1 toto staff 2.9K Dec 31 14:30 chromium-build-deps_79.0.3945.79-1_all.deb -rw-r--r-- 1 toto staff 3.6K Dec 31 12:28 enable-tracing.patch $ pwd /usr/local/src/chromium/chromium-c88b97a6dc183a6a7f8a05aee9e99957285a9371 Regards, Toto -- Sent from my GNU Emacs running on GNU/Linux
Bug#870499: wxmaxima: Plots too small
Package: wxmaxima Version: 16.12.2-2 Severity: normal Dear Maintainer, inline plots created e.g. with wxplot2d([x^2], [x,-5,5])$ lead to a very small image of the plot displayed. Setting the image size manually with wxplot_size:[1200,800]$ doesn't change anything. Neither does setting the plot size with the Menu Edit|Configure|Default plot size for new Maxima sessions. Both methods of changing the plot size are honored when right clicking the small image and saving it to a file. Toto -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wxmaxima depends on: ii ibus-gtk31.5.14-3 ii imagemagick 8:6.9.7.4+dfsg-15 ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-15 ii libc62.24-14 ii libgcc1 1:7.1.0-11 ii libstdc++6 7.1.0-11 ii libwxbase3.0-0v5 3.0.2+dfsg-4 ii libwxgtk3.0-0v5 3.0.2+dfsg-4 ii maxima 5.40.0-1 ii maxima-doc 5.40.0-1 Versions of packages wxmaxima recommends: ii fonts-jsmath 0.090709+0-3 ii texlive-latex-extra 2017.20170801-1 wxmaxima suggests no packages. -- no debconf information
Bug#853787: Found the problem!
> A workaround (that would temporarily loose wxMaxima's ability to set > maxima's current working directory until a fix is found) would be > deleting the line from the affected file that reads: >#+gcl (si:chdir dir) > Will fix the bug as soon as someone finds out how. Hi, I think you just have to add a colon: Change #+gcl (si:chdir dir) into #+gcl (si::chdir dir) On my system, the error message vanishes and I can call the "wxcd" function from within maxima (maxima appears to work normally, too): :lisp (wx-cd "/usr/lib/"); /usr/lib/ I think the bug is caused because in newer versions of gcl, "chdir" is still defined in the "si" package, but isn't exported---meaning that it does not belong to the public part of the API of the package which is accessible from other packages by calling it with the package name and a one colon qualifier. Using two colons makes it possible to access any symbol in a package[1]. I believe it's a bug in gcl (I'm not a Lisper). On a Debian Stable box, I get the following result when calling "si:chdir": icafe@cafe2016:~$ gcl GCL (GNU Common Lisp) 2.6.12 CLtL1Oct 28 2014 10:02:30 Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl) Binary License: GPL due to GPL'ed components: (XGCL READLINE UNEXEC) Modifications of this banner must retain notice of a compatible license Dedicated to the memory of W. Schelter Use (help) to get some basic information on how to use GCL. Temporary directory for compiler files set to /tmp/ >(si:chdir "/home") "/home" Doing the same on Debian Unstable: toto@talkietoaster: ~ $ /usr/bin/gcl [12:34:07] GCL (GNU Common Lisp) 2.6.12 CLtL1Fri Apr 22 15:51:11 UTC 2016 Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl) Binary License: GPL due to GPL'ed components: (XGCL READLINE UNEXEC) Modifications of this banner must retain notice of a compatible license Dedicated to the memory of W. Schelter Use (help) to get some basic information on how to use GCL. Temporary directory for compiler files: /tmp/ >(si:chdir "/home") Error: ERROR "Cannot find the external symbol CHDIR in #<\"SYSTEM\" package>." Fast links are on: do (si::use-fast-links nil) for debugging Signalled by SYSTEM::GCL-TOP-LEVEL. ERROR "Cannot find the external symbol CHDIR in #<\"SYSTEM\" package>." Broken at SYSTEM::GCL-TOP-LEVEL. Type :H for Help. 1 Return to top level. >>1 Top level. >(si::chdir "/home") #p"/home/" I can fix this by manually exporting "chdir": >(in-package :si) #<"SYSTEM" package> SYSTEM>(export 'chdir) T SYSTEM>(in-package "COMMON-LISP-USER") #<"COMMON-LISP-USER" package> >(si:chdir "/home") #p"/home/" The output is somewhat different, "/home/" vs. #p"/home/". I don't know if that's important. Toto Footnotes: [1] Peter Seibel: Practical Common Lisp, chapter 21, page 264 (http://www.gigamonkeys.com/book/programming-in-the-large-packages-and-symbols.html)
Bug#827031: xvnc4viewer: crashes with stack smashing on startup
Package: xvnc4viewer
Version: 4.1.1+X4.3.0-38
Severity: grave
Dear Maintainer,
since the last update, vncviewer crashes when I try to connect
(output appended below).
I think the problem is caused by the viewer and not by the server
("vnc4server 4.1.1+X4.3.0-37.6 i386" on a Debian stable host), because
connecting is possible from the host itself with the viewer from
stable. Downgrading the viewer on my system to "4.1.1+X4.3.0-37.6
amd64" fixes the problem.
Best regards,
Toto
toto@talkietoaster: ~ $ vncviewer localhost:42 [12:45:30]
VNC Viewer Free Edition 4.1.1 for X - built Jun 9 2016 23:13:27
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Sat Jun 11 12:45:36 2016
CConn: connected to host localhost port 5942
*** stack smashing detected ***: vncviewer terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x71fc5)[0x7fe667e34fc5]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fe667ebc2c7]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7fe667ebc290]
vncviewer[0x435185]
vncviewer[0x40cac5]
vncviewer[0x4053e7]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fe667de35f0]
vncviewer[0x405c6e]
=== Memory map:
0040-0044a000 r-xp fe:01 262336
/usr/bin/xvnc4viewer
0064a000-0064c000 r--p 0004a000 fe:01 262336
/usr/bin/xvnc4viewer
0064c000-0064d000 rw-p 0004c000 fe:01 262336
/usr/bin/xvnc4viewer
0064d000-0064f000 rw-p 00:00 0
01fcd000-0202 rw-p 00:00 0 [heap]
7fe666d66000-7fe666d71000 r-xp fe:01 6291757
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fe666d71000-7fe666f7 ---p b000 fe:01 6291757
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fe666f7-7fe666f71000 r--p a000 fe:01 6291757
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fe666f71000-7fe666f72000 rw-p b000 fe:01 6291757
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fe666f72000-7fe666f78000 rw-p 00:00 0
7fe666f78000-7fe666f7d000 r-xp fe:01 270059
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7fe666f7d000-7fe66717c000 ---p 5000 fe:01 270059
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7fe66717c000-7fe66717d000 r--p 4000 fe:01 270059
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7fe66717d000-7fe66717e000 rw-p 5000 fe:01 270059
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7fe66717e000-7fe667187000 r-xp fe:01 274619
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7fe667187000-7fe667386000 ---p 9000 fe:01 274619
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7fe667386000-7fe667387000 r--p 8000 fe:01 274619
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7fe667387000-7fe667388000 rw-p 9000 fe:01 274619
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7fe667388000-7fe667392000 r-xp fe:01 270094
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7fe667392000-7fe667591000 ---p a000 fe:01 270094
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7fe667591000-7fe667592000 r--p 9000 fe:01 270094
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7fe667592000-7fe667593000 rw-p a000 fe:01 270094
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7fe667593000-7fe667598000 r-xp fe:01 289827
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7fe667598000-7fe667797000 ---p 5000 fe:01 289827
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7fe667797000-7fe667798000 r--p 4000 fe:01 289827
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7fe667798000-7fe667799000 rw-p 5000 fe:01 289827
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7fe667799000-7fe66779c000 r-xp fe:01 269527
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7fe66779c000-7fe66799b000 ---p 3000 fe:01 269527
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7fe66799b000-7fe66799c000 r--p 2000 fe:01 269527
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7fe66799c000-7fe66799d000 rw-p 3000 fe:01 269527
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7fe66799d000-7fe66799f000 r-xp fe:01 6291667
/lib/x86_64-linux-gnu/libdl-2.22.so
7fe66799f000-7fe667b9f000 ---p 2000 fe:01 6291667
/lib/x86_64-linux-gnu/libdl-2.22.so
7fe667b9f000-7fe667ba r--p 2000 fe:01 6291667
/lib/x86_64-linux-gnu/libdl-2.22.so
7fe667ba-7fe667ba1000 rw-p 3000 fe:01 6291667
Bug#807911: bzflag-server: bzfs always launched on boot; RUN_AT_STARTUP setting ignored
Package: bzflag-server Version: 2.4.2+ds1-6+b1 Severity: normal Dear Maintainer, it is not possible to start a bzfs server from within BZFlag because there is one already running, launched during startup. Default setting 'RUN_AT_STARTUP="no"' in '/etc/default/bzflag' is ignored. Manually stopping the server solves the problem. The systemd service file has 'EnvironmentFile=-/etc/default/bzflag line, so the default settings should be honoured. Thx for packaging my favourite game. Toto $ ps aux | grep bzfs | grep -v grep games 1100 0.0 0.2 88656 8668 ?Ss 13:04 0:00 /usr/games/bzfs -advertise NONE $ service bzflag status ● bzflag.service - BZFlag game server Loaded: loaded (/lib/systemd/system/bzflag.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2015-12-14 13:04:12 CET; 5min ago Docs: man:bzfs(6) Main PID: 1100 (bzfs) CGroup: /system.slice/bzflag.service └─1100 /usr/games/bzfs -advertise NONE Dec 14 13:04:12 talkietoaster systemd[1]: Started BZFlag game server. Dec 14 13:04:12 talkietoaster bzfs[1100]: Note: no acceleration limit has been set. Players using "mouse Dec 14 13:04:12 talkietoaster bzfs[1100]: enhancements" may cause problems on this server due to very high Dec 14 13:04:12 talkietoaster bzfs[1100]: acceleration rates which are not handled well by dead reckoning Dec 14 13:04:12 talkietoaster bzfs[1100]: algorithms. To eliminate this warning, set the -a switch in your Dec 14 13:04:12 talkietoaster bzfs[1100]: configuration. '-a 50 38' is recommended for standard-speed servers. Dec 14 13:04:12 talkietoaster bzfs[1100]: Higher speed servers will need higher values for -a in order to not Dec 14 13:04:12 talkietoaster bzfs[1100]: affect gameplay. '-a 0 0' may be used to shut this message up without Dec 14 13:04:12 talkietoaster bzfs[1100]: affecting any players, including those using "mouse enhancements". $ cat /etc/default/bzflag # RUN_AT_STARTUP # "yes|true|enabled", /etc/init.d/bzflag will start bzfs. # Any other value, /etc/init.d/bzflag will exit silently. # RUN_AT_STARTUP="no" # OPTIONS # Command line options to pass to bzfs. See bzfs(6) for more details. # OPTIONS="-advertise NONE" $ cat /etc/systemd/system/multi-user.target.wants/bzflag.service [Unit] Description=BZFlag game server Documentation=man:bzfs(6) After=network.target [Service] Environment="OPTIONS=-advertise NONE" EnvironmentFile=-/etc/default/bzflag User=games Group=games ExecStart=/usr/games/bzfs $OPTIONS [Install] WantedBy=multi-user.target -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-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/dash Init: systemd (via /run/systemd/system) Versions of packages bzflag-server depends on: ii init-system-helpers 1.24 ii libc-ares2 1.10.0-2 ii libc62.21-4 ii libcurl3-gnutls 7.45.0-1+b1 ii libgcc1 1:5.3.1-3 ii libncurses5 6.0+20151024-2 ii libstdc++6 5.3.1-3 ii libtinfo56.0+20151024-2 ii zlib1g 1:1.2.8.dfsg-2+b1 bzflag-server recommends no packages. bzflag-server suggests no packages. -- no debconf information
Bug#807911: bzflag-server: bzfs always launched on boot; RUN_AT_STARTUP setting ignored
>>>>> Markus Koschany <a...@gambaru.de> writes: > Am 14.12.2015 um 13:39 schrieb Thorsten Bonow: >> Package: bzflag-server Version: 2.4.2+ds1-6+b1 Severity: normal >> >> Dear Maintainer, >> >> it is not possible to start a bzfs server from within BZFlag >> because there is one already running, launched during >> startup. Default setting 'RUN_AT_STARTUP="no"' in >> '/etc/default/bzflag' is ignored. >> >> Manually stopping the server solves the problem. The systemd >> service file has 'EnvironmentFile=-/etc/default/bzflag line, so the >> default settings should be honoured. >> >> Thx for packaging my favourite game. >> >> Toto > Hello Toto, > the default policy for service files is to enable them by > default. Now I understand that the options in /etc/default/bzflag > cannot be completely honored because "RUN_AT_STARTUP" is a sysV init > specific option that is only valid if you use the old sysV init > system instead of systemd. > The recommended way to change options and service files is to create > a custom service file and to move it to /etc/systemd/system. If you > want to disable the server on startup then you must run > systemctl disable bzflag.service > or you must only install bzflag-client. > I will remove the EnvironmentFile and Environment lines from the > service file to avoid any confusion in the future and document this > new behavior in README.Debian. > Regards, > Markus Hello Markus, thx for the quick reply and explanation. Disabling the service works for me. Regards, Toto
Bug#780585: Mysterious failure to update/install packages
Hi! Package: dpkg Version: 1.17.23 Severity: normal I had to test something quickly in an older sid chroot (hence the many not updated packages) and updating libgcc1 + libc6 failed without clear reason why. Running dpkg --configure -a configured the 2 packages just fine. I'm unsure what went wrong there. Is dpkg screwing up the order in which packages get configured or is apt-get? Or what ios going on there? dpkg does what it is told, I'm assuming some problem in apt, or its invocation. I've been bitten by this bug during the libc6:amd64|i386 update yesterday. Here is what aptitude has to say: Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done Preconfiguring packages ... dpkg: error processing package libc6:amd64 (--configure): package libc6:amd64 2.19-17 cannot be configured because libc6:i386 is at a different version (2.19-15) dpkg: dependency problems prevent configuration of apt: apt depends on libc6 (= 2.15); however: Package libc6:amd64 is not configured yet. dpkg: error processing package apt (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libc6:amd64 apt E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: dpkg: error processing package libc6:amd64 (--configure): package libc6:amd64 2.19-17 cannot be configured because libc6:i386 is at a different version (2.19-15) dpkg: error processing package libc6:i386 (--configure): package libc6:i386 2.19-15 cannot be configured because libc6:amd64 is at a different version (2.19-17) dpkg: dependency problems prevent configuration of apt: apt depends on libc6 (= 2.15); however: Package libc6:amd64 is not configured yet. dpkg: error processing package apt (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libc-dev-bin: libc-dev-bin depends on libc6 ( 2.19); however: Package libc6:amd64 is not configured yet. libc-dev-bin depends on libc6 ( 2.20); however: Package libc6:amd64 is not configured yet. dpkg: error processing package libc-dev-bin (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libc6-dev:amd64: libc6-dev:amd64 depends on libc6 (= 2.19-17); however: Package libc6:amd64 is not configured yet. libc6-dev:amd64 depends on libc-dev-bin (= 2.19-17); however: Package libc-dev-bin is not configured yet. dpkg: error processing package libc6-dev:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libc6-dbg:amd64: libc6-dbg:amd64 depends on libc6 (= 2.19-17); however: Package libc6:amd64 is not configured yet. dpkg: error processing package libc6-dbg:amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libc6:amd64 libc6:i386 apt libc-dev-bin libc6-dev:amd64 libc6-dbg:amd64 Press Return to continue. Running dpkg directly with 'dpkg -a --configure' fails; apt-get, too (Beeing a fool, I've tried downgrading apt before running apt-get): apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: lib32stdc++6 libc6-x32 locales The following NEW packages will be installed: lib32stdc++6 libc6-x32 The following packages will be upgraded: locales 1 upgraded, 2 newly installed, 0 to remove and 42 not upgraded. 6 not fully installed or removed. Need to get 0 B/6,801 kB of archives. After this operation, 11.3 MB of additional disk space will be used. Do you want to continue? [Y/n] Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done Preconfiguring packages ... dpkg: error processing package libc6:amd64 (--configure): package libc6:amd64 2.19-17 cannot be configured because libc6:i386 is at a different version (2.19-15) dpkg: dependency problems prevent configuration of apt: apt depends on libc6 (= 2.15); however: Package libc6:amd64 is not configured yet. dpkg: error processing package apt (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libc6:amd64 apt E: Sub-process /usr/bin/dpkg returned an error code (1) Will my system survive a reboot in this state? Any help is appreciated. Toto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750590: gnuplot-x11: Crashes with wxt terminal
Package: gnuplot-x11 Version: 4.6.5-3 Severity: important Dear Maintainer, gnuplot crashes when the terminal is set to 'wxt' with the output attached below. Setting the terminal to 'x11' works. The bug appears to have been introduced in 4.6.5.2, which shows the same behaviour. Downgrading to gnuplot_4.6.5-1_all.deb gnuplot-doc_4.6.5-1_all.deb gnuplot-x11_4.6.5-1_i386.deb fixed the problem for me. Best regards, Toto toto@catweazle:~$ gnuplot G N U P L O T Version 4.6 patchlevel 5last modified February 2014 Build System: Linux i686 Copyright (C) 1986-1993, 1998, 2004, 2007-2014 Thomas Williams, Colin Kelley and many others gnuplot home: http://www.gnuplot.info faq, bugs, etc: type help FAQ immediate help: type help (plot window: hit 'h') Terminal type set to 'wxt' gnuplot plot x**2 ../src/gtk/dcclient.cpp(2041): assert m_window failed in DoGetSize(): GetSize() doesn't work without window [in thread b54a4b40] Call stack: [00] wxOnAssert(char const*, int, char const*, char const*, wchar_t const*) [01] wxClientDCImpl::DoGetSize(int*, int*) const [02] wxBufferedDC::UnMask() [03] 0xb76b566c [04] wxAppConsoleBase::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent), wxEvent) const [05] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor, wxEvent) const [06] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const, wxEvtHandler*, wxEvent) [07] wxEventHashTable::HandleEvent(wxEvent, wxEvtHandler*) [08] wxEvtHandler::TryHereOnly(wxEvent) [09] wxEvtHandler::ProcessEventLocally(wxEvent) [10] wxEvtHandler::ProcessEvent(wxEvent) [11] wxEvtHandler::SafelyProcessEvent(wxEvent) [12] wxWindowBase::HandleWindowEvent(wxEvent) const [13] wxWindow::GTKProcessEvent(wxEvent) const [14] 0xb714e2d6 [15] g_cclosure_marshal_VOID__BOXED [16] g_closure_invoke [17] 0xb6ca8089 [18] g_signal_emit_valist [19] g_signal_emit [20] gtk_widget_size_allocate [xcb] Unknown request in queue while dequeuing [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. gnuplot: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed. Aborted -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/1 CPU core) 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 gnuplot-x11 depends on: ii aglfn1.7-3 ii libc62.18-7 ii libcairo21.12.16-2 ii libedit2 3.1-20140213-1 ii libgcc1 1:4.9.0-5 ii libgd3 2.1.0-3+b1 ii libglib2.0-0 2.40.0-3 ii liblua5.1-0 5.1.5-5 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libstdc++6 4.9.0-5 ii libwxbase3.0-0 3.0.0-4 ii libwxgtk3.0-03.0.0-4 ii libx11-6 2:1.6.2-2 gnuplot-x11 recommends no packages. Versions of packages gnuplot-x11 suggests: ii gnuplot-doc 4.6.5-3 -- 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#750590: gnuplot-x11: Crashes with wxt terminal
The bug has already been reported (#750045). Can't understand how I could miss it. Sry for the noise. Toto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743880: maxima: Segmentation fault
Package: maxima Version: 5.33.0-1 Severity: grave Dear Maintainer, calling 'maxima' on my system leads to a segmentation fault: toto@catweazle:~$ maxima -v + '[' gcl = clisp ']' + '[' gcl = cmucl ']' + '[' gcl = scl ']' + '[' gcl = gcl ']' + exec /usr/lib/maxima/5.33.0/binary-gcl/maxima -eval '(cl-user::run)' -f -- -v '' '' '' '' '' '' '' '' Segmentation fault Downgrading the maxima packages down to 5.32.1-1 makes 'maxima' usable again. Toto -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) 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 maxima depends on: ii gnuplot-x11 4.6.5-1 ii libc6 2.18-4 ii libgmp10 2:6.0.0+dfsg-2 ii libreadline6 6.3-6 ii libx11-6 2:1.6.2-1 Versions of packages maxima recommends: ii maxima-share 5.32.1-1 Versions of packages maxima suggests: ii maxima-doc5.32.1-1 ii maxima-emacs 5.32.1-1 pn texmacs none ii tk [wish] 8.6.0+8 ii xmaxima 5.32.1-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#742426: slime: package update fails
Milan == Milan Zamazal p...@debian.org writes: TB == Thorsten Bonow thorsten.bo...@withouthat.org writes: TB updating to the newest version of the slime package failed TB with the messages attached below. Downgrading to TB cl-swank_20130626-1_all.deb and slime_20130626-1_all.deb TB worked. TB One more thing: I'm using emacs24-lucid and slime TB complains---the package recommends emacs24 (= 24.3) | TB emacs-snapshot | xemacs21. Milan Both the problems should be fixed in slime 2.4-2. Milan Please note the (harmless) error message will be still Milan present on the first upgrade/install due to emacsen-common Milan bug #736062. Milan Thanks for the report. Hi, thanks for your help, but now I get the following (even after purging slime and doing a fresh install): root@catweazle:/var/cache/apt/archives# dpkg -i slime_2%3a2.4-2_all.deb Selecting previously unselected package slime. (Reading database ... 527272 files and directories currently installed.) Preparing to unpack slime_2%3a2.4-2_all.deb ... ERROR: slime is broken - called emacs-package-install as a new-style add-on, but has no compat file. Unpacking slime (2:2.4-2) ... Setting up slime (2:2.4-2) ... Install emacsen-common for emacs23 emacsen-common: Handling install of emacsen flavor emacs23 Wrote /etc/emacs23/site-start.d/00debian-vars.elc Wrote /usr/share/emacs23/site-lisp/debian-startup.elc Install emacsen-common for emacs24 emacsen-common: Handling install of emacsen flavor emacs24 Wrote /etc/emacs24/site-start.d/00debian-vars.elc Wrote /usr/share/emacs24/site-lisp/debian-startup.elc Install slime for emacs23 Install slime for emacs24 install/slime: Handling install for emacsen flavor emacs24 Loading 00debian-vars... Loading /etc/emacs/site-start.d/20apel.el (source)... Loading /etc/emacs/site-start.d/50a2ps.el (source)... Loading /etc/emacs/site-start.d/50auctex.el (source)... Loading /usr/share/emacs/site-lisp/auctex.el (source)... Loading /usr/share/emacs/site-lisp/preview-latex.el (source)... Loading /etc/emacs/site-start.d/50auto-complete-el.el (source)... Loading /etc/emacs/site-start.d/50autoconf.el (source)... Loading /etc/emacs/site-start.d/50ccrypt.el (source)... Loading /etc/emacs/site-start.d/50cmake-data.el (source)... Loading /etc/emacs/site-start.d/50cxref-emacs.el (source)... Loading /etc/emacs/site-start.d/50develock-el.el (source)... Real cl-lib shadowed by compatibility cl-lib? (/usr/share/emacs/24.3/site-lisp/slime/lib/cl-lib.el) cl-letf already defined, not rebinding Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)... Loading debian-ispell... Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)... Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)... Loading /etc/emacs/site-start.d/50doxymacs.el (source)... Loading /etc/emacs/site-start.d/50ecb.el (source)... ECB 2.40 uses CEDET 2.0 (contains semantic 2.2, eieio 1.4, speedbar unknown version). ../ecb/ecb.elc:Warning: `interactive-p' is an obsolete function (as of 23.2); use `called-interactively-p' instead. ../ecb/ecb.elc:Warning: `interactive-p' is an obsolete function (as of 23.2); use `called-interactively-p' instead. ../ecb/ecb.elc:Warning: `interactive-p' is an obsolete function (as of 23.2); use `called-interactively-p' instead. Loading /etc/emacs/site-start.d/50flim.el (source)... Loading /etc/emacs/site-start.d/50global.el (source)... Loading /etc/emacs/site-start.d/50gnuplot-mode.el (source)... Loading /etc/emacs/site-start.d/50gnus-bonus-el.el (source)... Loading /etc/emacs24/site-start.d/50mailcrypt.el (source)... Loading /etc/emacs/site-start.d/50maxima-emacs.el (source)... Loading /etc/emacs/site-start.d/50mew.el (source)... Loading /etc/emacs/site-start.d/50namazu2.el (source)... Loading /etc/emacs/site-start.d/50psvn.el (source)... Loading /etc/emacs/site-start.d/50slime.el (source)... Loading /usr/share/emacs/site-lisp/slime/slime-autoloads.el (source)... Loading /etc/emacs/site-start.d/50w3m-el-snapshot.el (source)... Loading /etc/emacs/site-start.d/50whizzytex.el (source)... Loading /etc/emacs/site-start.d/50yasnippet.el (source)... `flet' is an obsolete macro (as of 24.3); use either `cl-flet' or `cl-letf'. (lambda (field1 field2) ...) quoted with ' rather than with #' `flet' is an obsolete macro (as of 24.3); use either `cl-flet' or `cl-letf'. Loading /etc/emacs/site-start.d/51debian-el.el (source)... Loading /etc/emacs/site-start.d/55ecb.el (source)... Error while loading 55ecb: Cannot open load file: ecb-autoloads Loading /etc/emacs/site-start.d/70x-face-el.el (source)... Package assoc is obsolete! Real cl-lib shadowed by compatibility cl-lib? (/usr/share/emacs24/site-lisp/slime/lib/cl-lib.el) Wrong type argument: stringp, nil ERROR: install script from slime package failed dpkg: error processing package slime (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers
Bug#742426: slime: package update fails
Package: slime Version: 2:2.4-1 Severity: normal Dear Maintainer, updating to the newest version of the slime package failed with the messages attached below. Downgrading to cl-swank_20130626-1_all.deb and slime_20130626-1_all.deb worked. One more thing: I'm using emacs24-lucid and slime complains---the package recommends emacs24 (= 24.3) | emacs-snapshot | xemacs21. What's wrong with lucid? Does slime really requires something toolkit specific? It works for me with lucid. Thanks for your support. Toto gepetto:/home/toto/4bkk# dpkg -i slime_2.4-1_all.deb cl-swank_2.4-1_all.deb (Reading database ... 542939 files and directories currently installed.) Preparing to unpack slime_2.4-1_all.deb ... Remove slime for emacs Remove slime for emacs23 remove/slime: purging byte-compiled files for emacs23 Remove slime for emacs24 remove/slime: purging byte-compiled files for emacs24 ERROR: slime is broken - called emacs-package-install as a new-style add-on, but has no compat file. Unpacking slime (2:2.4-1) over (1:20130626-1) ... Preparing to unpack cl-swank_2.4-1_all.deb ... Unpacking cl-swank (2:2.4-1) over (1:20130626-1) ... Setting up slime (2:2.4-1) ... ERROR: slime is broken - called emacs-package-install as a new-style add-on, but has no compat file. Install emacsen-common for emacs23 emacsen-common: Handling install of emacsen flavor emacs23 Wrote /etc/emacs23/site-start.d/00debian-vars.elc Wrote /usr/share/emacs23/site-lisp/debian-startup.elc Install emacsen-common for emacs24 emacsen-common: Handling install of emacsen flavor emacs24 Wrote /etc/emacs24/site-start.d/00debian-vars.elc Wrote /usr/share/emacs24/site-lisp/debian-startup.elc Install slime for emacs Install slime for emacs23 Install slime for emacs24 install/slime: Handling install for emacsen flavor emacs24 Loading 00debian-vars... Loading /etc/emacs/site-start.d/20apel.el (source)... Loading /etc/emacs/site-start.d/50auctex.el (source)... Loading /usr/share/emacs/site-lisp/auctex.el (source)... Loading /usr/share/emacs/site-lisp/preview-latex.el (source)... Loading /etc/emacs/site-start.d/50auto-complete-el.el (source)... Loading /etc/emacs/site-start.d/50autoconf.el (source)... Loading /etc/emacs/site-start.d/50ccrypt.el (source)... Loading /etc/emacs/site-start.d/50cxref-emacs.el (source)... Loading /etc/emacs/site-start.d/50develock-el.el (source)... Real cl-lib shadowed by compatibility cl-lib? (/usr/share/emacs/24.3/site-lisp/slime/lib/cl-lib.el) cl-letf already defined, not rebinding Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)... Loading debian-ispell... Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)... Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)... Loading /etc/emacs/site-start.d/50doxymacs.el (source)... Loading /etc/emacs/site-start.d/50ecb.el (source)... ECB 2.40 uses CEDET 2.0 (contains semantic 2.2, eieio 1.4, speedbar unknown version). ../ecb/ecb.elc:Warning: `interactive-p' is an obsolete function (as of 23.2); use `called-interactively-p' instead. ../ecb/ecb.elc:Warning: `interactive-p' is an obsolete function (as of 23.2); use `called-interactively-p' instead. ../ecb/ecb.elc:Warning: `interactive-p' is an obsolete function (as of 23.2); use `called-interactively-p' instead. Loading /etc/emacs/site-start.d/50flim.el (source)... Loading /etc/emacs/site-start.d/50global.el (source)... Loading /etc/emacs/site-start.d/50gnuplot-mode.el (source)... Loading /etc/emacs/site-start.d/50latex-cjk-common.el (source)... Loading cjk-enc... Loading /etc/emacs/site-start.d/50latex-cjk-thai.el (source)... Loading /etc/emacs24/site-start.d/50mailcrypt.el (source)... Loading /etc/emacs/site-start.d/50maxima-emacs.el (source)... Loading /etc/emacs/site-start.d/50mew.el (source)... Loading /etc/emacs/site-start.d/50namazu2.el (source)... Loading /etc/emacs/site-start.d/50pydb.el (source)... Loading /etc/emacs/site-start.d/50slime.el (source)... Loading /usr/share/emacs/site-lisp/slime/slime-autoloads.el (source)... Loading /etc/emacs/site-start.d/50w3m-el-snapshot.el (source)... Loading /etc/emacs/site-start.d/50whizzytex.el (source)... Loading /etc/emacs/site-start.d/50xcscope-el.el (source)... Loading /etc/emacs/site-start.d/50yasnippet.el (source)... `flet' is an obsolete macro (as of 24.3); use either `cl-flet' or `cl-letf'. (lambda (field1 field2) ...) quoted with ' rather than with #' `flet' is an obsolete macro (as of 24.3); use either `cl-flet' or `cl-letf'. Loading /etc/emacs/site-start.d/51debian-el.el (source)... Loading /etc/emacs/site-start.d/60cltl.el (source)... Loading /etc/emacs/site-start.d/60hyperspec.el (source)... Loading /etc/emacs/site-start.d/70x-face-el.el (source)... Package assoc is obsolete! Real cl-lib shadowed by compatibility cl-lib? (/usr/share/emacs24/site-lisp/slime/lib/cl-lib.el) Wrong type argument: stringp, nil ERROR: install script from slime package failed dpkg: error processing package slime (--install):
Bug#726559: exaile: Segmentation fault after a second of playing
Vincent == Vincent Cheng vincentc1...@gmail.com writes: Vincent On Thu, Oct 17, 2013 at 3:02 AM, Thorsten Bonow Vincent thorsten.bo...@withouthat.org wrote: Toto == Thorsten Bonow thorsten.bo...@withouthat.org writes: Toto Package: exaile Version: 3.3.1-1 Severity: grave [...] Hi, the crash appears to be related to the Wikipedia-plugin. If I disable the plugin, exaile works again. It occured to me to disable the plugin after checking my syslog (sry, must have had a nail in my had): Oct 17 10:42:33 gepetto kernel: [91597.061624] exaile[29414]: segfault at 2c ip b2bc0df5 sp bf9cd580 error 4 in libwebkitgtk-1.0.so.0.19.8[b26eb000+1bd8000] Although libwebkitgtk and related packages were updated in the last few days, downgrading to libjavascriptcoregtk-1.0-0_2.1.90.1-1_i386.deb libwebkitgtk-1.0-0_2.1.90.1-1_i386.deb libwebkitgtk-1.0-common_2.1.90.1-1_all.deb doesn't fix the problem; only disabling the plugin helps. Toto Vincent Thanks for the report! Unfortunately, I can't seem to Vincent reproduce this bug at all, whether or not the wikipedia Vincent plugin is enabled. Vincent Can you please attach the output of exaile --debug and Vincent try to get exaile to crash again, then file a bug report Vincent directly upstream at [1]? Vincent Regards, Vincent Vincent [1] https://bugs.launchpad.net/exaile/+filebug Hi, thanks for your quick reply. I filed the bug report (Bug #1243712) upstream. Regards, Toto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726559: exaile: Segmentation fault after a second of playing
Toto == Thorsten Bonow thorsten.bo...@withouthat.org writes: Toto Package: exaile Version: 3.3.1-1 Severity: grave [...] Hi, the crash appears to be related to the Wikipedia-plugin. If I disable the plugin, exaile works again. It occured to me to disable the plugin after checking my syslog (sry, must have had a nail in my had): Oct 17 10:42:33 gepetto kernel: [91597.061624] exaile[29414]: segfault at 2c ip b2bc0df5 sp bf9cd580 error 4 in libwebkitgtk-1.0.so.0.19.8[b26eb000+1bd8000] Although libwebkitgtk and related packages were updated in the last few days, downgrading to libjavascriptcoregtk-1.0-0_2.1.90.1-1_i386.deb libwebkitgtk-1.0-0_2.1.90.1-1_i386.deb libwebkitgtk-1.0-common_2.1.90.1-1_all.deb doesn't fix the problem; only disabling the plugin helps. Toto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726559: exaile: Segmentation fault after a second of playing
Package: exaile Version: 3.3.1-1 Severity: grave Dear Maintainer, since doing a complete update of my Debian Unstable computer today, exaile starts up normally but when I try to play an mp3, it crashes after a second of playing the file (see log below). Since there was no update of exaile itself, the problem should be caused by the interaction with a package updated on the 15. or 14. of October. After the last update on the 13th, exaile did work. Up to now I haven't figured out which package to downgrade in order to solve the problem. Thx for your work and help. Toto INFO: Loading Exaile 3.3.1 on Python 2.7.5+... INFO: Loading settings... INFO: Loading plugins... INFO: Attempting to connect to AudioScrobbler (http://post.audioscrobbler.com/) INFO: Loading collection... INFO: Logged in successfully to AudioScrobbler (http://post.audioscrobbler.com/) INFO: Connected to AudioScrobbler INFO: Loading devices... WARNING : Failed to connect to HAL, autodetection of devices will be disabled. INFO: Loading interface... INFO: Using GTK+ 2.24.21 INFO: Loading main window... INFO: Connecting main window events... INFO: Loading panels... INFO: Connecting panel events... INFO: Done loading main window... Error grabbing key 173, 0x8c0a008 Error grabbing key 171, 0x8c0a008 Error grabbing key 172, 0x8c0a008 Error grabbing key 209, 0x8c0a008 Error grabbing key 174, 0x8c0a008 INFO: Playing file:///home/toto/mp3/Prefab%20Sprout/Andromeda%20Heights/02%20-%20A%20Prisoner%20Of%20The%20Past%20(Album%20Version).mp3 (exaile.py:24033): GStreamer-CRITICAL **: gst_caps_ref: assertion `GST_CAPS_REFCOUNT_VALUE (caps) 0' failed (exaile.py:24033): GStreamer-CRITICAL **: gst_caps_ref: assertion `GST_CAPS_REFCOUNT_VALUE (caps) 0' failed (exaile.py:24033): GStreamer-CRITICAL **: gst_caps_unref: assertion `GST_CAPS_REFCOUNT_VALUE (caps) 0' failed /usr/lib/exaile/xlgui/__init__.py:53: Warning: cannot register existing type `GstObject' gtk.main() /usr/lib/exaile/xlgui/__init__.py:53: Warning: g_once_init_leave: assertion `result != 0' failed gtk.main() /usr/lib/exaile/xlgui/__init__.py:53: Warning: g_type_register_static: assertion `parent_type 0' failed gtk.main() (exaile.py:24033): GStreamer-CRITICAL **: gst_element_class_set_metadata: assertion `GST_IS_ELEMENT_CLASS (klass)' failed -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.10-3-686-pae (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 exaile depends on: ii gstreamer0.10-plugins-good 0.10.31-3+nmu1 ii librsvg2-common 2.36.4-2 ii python 2.7.5-5 ii python-dbus 1.2.0-2+b1 ii python-gobject 3.10.1-1 ii python-gst0.10 0.10.22-3 ii python-gtk2 2.24.0-3+b1 ii python-mutagen 1.21-1 Versions of packages exaile recommends: ii gstreamer0.10-ffmpeg 1:0.10.13-dmo1 ii python-cddb 1.4-5.1+b3 ii python-mmkeys 1.6.2.1-5 ii python-notify 0.1.1-3 Versions of packages exaile suggests: ii exaile-plugin-contextinfo 3.3.1-1 pn exaile-plugin-ipod none ii exaile-plugin-moodbar 3.3.1-1 pn exfalso none ii gstreamer0.10-plugins-bad 0.10.23-7.1 ii gstreamer0.10-plugins-ugly 0.10.19-2+b3 pn ipython none pn notify-osd none pn python-avahinone ii python-beautifulsoup3.2.1-1 ii python-eggtrayicon 2.25.3-12 ii python-pymtp0.0.6-1 ii streamripper1.64.6-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#711965: wxmaxima: Won't start
Package: wxmaxima Version: 12.04.0-1 Severity: grave Dear Maintainer, wxmaxima stopped working for me. It won't start, giving the following message: wxmaxima: relocation error: wxmaxima: symbol _Z31_wx_link_dummy_func_gnome_printv, version WXU_2.8 not defined in file libwx_gtk2u_core-2.8.so.0 with link time reference Downgrading from version *-13 to*-12 of these packages made wxmaxima start again: libwxbase2.8-0_2.8.12.1-12_i386.deb libwxbase2.8-dbg_2.8.12.1-12_i386.deb libwxbase2.8-dev_2.8.12.1-12_i386.deb libwxgtk2.8-0_2.8.12.1-12_i386.deb libwxgtk2.8-dbg_2.8.12.1-12_i386.deb libwxgtk2.8-dev_2.8.12.1-12_i386.deb python-wxgtk2.8_2.8.12.1-12_i386.deb python-wxtools_2.8.12.1-12_all.deb wx2.8-doc_2.8.12.1-12_all.deb wx2.8-examples_2.8.12.1-12_all.deb wx2.8-headers_2.8.12.1-12_i386.deb wx2.8-i18n_2.8.12.1-12_all.deb wx-common_2.8.12.1-12_i386.deb My guess is that wxmaxima needs to be recompiled with yesterday's upgraded wx library. Regards, Toto -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.9-1-686-pae (SMP w/1 CPU core) 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 wxmaxima depends on: ii libc6 2.17-5 ii libgcc1 1:4.8.1-2 ii libstdc++6 4.8.1-2 ii libwxbase2.8-0 2.8.12.1-13 ii libwxgtk2.8-0 2.8.12.1-13 ii maxima 5.30.0-6 ii maxima-doc 5.30.0-6 Versions of packages wxmaxima recommends: ii fonts-jsmath [ttf-jsmath] 0.090709+0-3 ii libgnomeprintui2.2-0 2.18.6-3 ii ttf-jsmath 0.090709+0-3 wxmaxima 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#700100: emacs24-lucid: segfaults on startup
Ivan == Ivan Shmakov oneing...@gmail.com writes: Thorsten Bonow thorsten.bo...@withouthat.org writes: [...] Program received signal SIGSEGV, Segmentation fault. 0xb7ef9228 in XtInitializeWidgetClass () from /usr/lib/i386-linux-gnu/libXt.so.6 Ivan Could you please issue the “bt” command right after Ivan this message (for gdb to dump the backtrace)? [...] Hi, thx for your assistance. The backtrace follows below. Toto toto@gepetto:~$ gdb emacs24-lucid GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 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 i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/emacs24-lucid...Reading symbols from /usr/lib/debug/.build-id/66/345ef04ddb20d03e0351b78f1753d3df49d9d3.debug...done. done. (gdb) run Starting program: /usr/bin/emacs24-lucid [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [New Thread 0xb6622b70 (LWP 20775)] [New Thread 0xb5e21b70 (LWP 20776)] Program received signal SIGSEGV, Segmentation fault. 0xb7ef9228 in XtInitializeWidgetClass () from /usr/lib/i386-linux-gnu/libXt.so.6 (gdb) bt #0 0xb7ef9228 in XtInitializeWidgetClass () from /usr/lib/i386-linux-gnu/libXt.so.6 #1 0xb7ef9d68 in _XtCreateWidget () from /usr/lib/i386-linux-gnu/libXt.so.6 #2 0xb7efa056 in XtCreateWidget () from /usr/lib/i386-linux-gnu/libXt.so.6 #3 0x0810d6b4 in x_window (f=f@entry=0x8662800, window_prompting=window_prompting@entry=0, minibuffer_only=error reading variable: Unhandled dwarf expression opcode 0xfa) at xfns.c:2433 #4 0x0810e9bd in Fx_create_frame (parms=138821598) at xfns.c:3377 #5 0x081a5028 in Ffuncall (nargs=nargs@entry=2, args=args@entry=0xbfffe6f0) at eval.c:3001 #6 0x081dbb5c in exec_byte_code (bytestr=optimized out, vector=137063965, maxdepth=16, args_template=138843418, nargs=nargs@entry=0, args=optimized out, args@entry=0x0) at bytecode.c:785 #7 0x081a4a65 in funcall_lambda (fun=137063909, nargs=nargs@entry=1, arg_vector=arg_vector@entry=0xbfffe864) at eval.c:3232 #8 0x081a4e33 in Ffuncall (nargs=nargs@entry=2, args=args@entry=0xbfffe860) at eval.c:3062 #9 0x081dbb5c in exec_byte_code (bytestr=optimized out, vector=137393533, maxdepth=20, args_template=138843418, nargs=nargs@entry=0, args=optimized out, args@entry=0x0) at bytecode.c:785 #10 0x081a4a65 in funcall_lambda (fun=137393485, nargs=nargs@entry=1, arg_vector=arg_vector@entry=0xbfffe9e4) at eval.c:3232 #11 0x081a4e33 in Ffuncall (nargs=nargs@entry=2, args=args@entry=0xbfffe9e0) at eval.c:3062 #12 0x081dbb5c in exec_byte_code (bytestr=optimized out, vector=137390829, maxdepth=24, args_template=138843418, nargs=nargs@entry=0, args=optimized out, args@entry=0x0) at bytecode.c:785 #13 0x081a4a65 in funcall_lambda (fun=137390781, nargs=nargs@entry=0, arg_vector=arg_vector@entry=0xbfffeb64) at eval.c:3232 #14 0x081a4e33 in Ffuncall (nargs=nargs@entry=1, args=args@entry=0xbfffeb60) at eval.c:3062 #15 0x081dbb5c in exec_byte_code (bytestr=optimized out, vector=137083765, maxdepth=72, args_template=args_template@entry=0, nargs=nargs@entry=0, args=optimized out, args@entry=0xbfffed18) at bytecode.c:785 #16 0x081a4ac4 in funcall_lambda (fun=137083717, nargs=nargs@entry=0, arg_vector=arg_vector@entry=0xbfffed18) at eval.c:3166 #17 0x081a4e33 in Ffuncall (nargs=nargs@entry=1, args=args@entry=0xbfffed14) at eval.c:3062 #18 0x081dbb5c in exec_byte_code (bytestr=optimized out, vector=137080957, maxdepth=32, args_template=args_template@entry=0, nargs=nargs@entry=0, args=optimized out, args@entry=0xbfffee20) at bytecode.c:785 #19 0x081a4ac4 in funcall_lambda (fun=fun@entry=137080909, nargs=nargs@entry=0, arg_vector=arg_vector@entry=0xbfffee20) at eval.c:3166 #20 0x081a3f46 in apply_lambda (fun=137080909, args=optimized out) at eval.c:3109 #21 0x081a42ae in eval_sub (form=form@entry=139048830) at eval.c:2413 #22 0x081a6ead in Feval (form=139048830, lexical=138843418) at eval.c:2203 #23 0x08135869 in top_level_2 () at keyboard.c:1169 #24 0x081a33d0 in internal_condition_case (bfun=bfun@entry=0x8135850 top_level_2, handlers=138874498, hfun=hfun@entry=0x8136f20 cmd_error) at eval.c:1514 #25 0x081360b5 in top_level_1 (ignore=ignore@entry=138843418) at keyboard.c:1177 #26 0x081a32fb in internal_catch (tag=138872450, func=func@entry=0x8136050 top_level_1, arg=138843418) at eval.c:1271 #27 0x08136a3c in command_loop () at keyboard.c:1132 #28 recursive_edit_1 () at keyboard.c:759 #29 0x08136d4d in Frecursive_edit () at keyboard.c:823 #30 0x08056cc5 in main (argc=optimized out, argv
Bug#700100: emacs24-lucid: segfaults on startup
Package: emacs24-lucid Version: 24.2+1-2 Followup-For: Bug #684788 If either of you have time, could you retry with 24.2+1-2 (once it migrates to unstable), and if emacs still crashes, could you install the new emacs24-lucid-dbg package so that gdb can (hopefully) provide a bit more information? Dear Maintainer, even with emacs24-lucid-dbg installed, there isn't more information. See below for the output from gdb. Toto toto@gepetto:~$ gdb emacs24-lucid GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 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 i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/emacs24-lucid...Reading symbols from /usr/lib/debug/.build-id/66/345ef04ddb20d03e0351b78f1753d3df49d9d3.debug...done. done. (gdb) run Starting program: /usr/bin/emacs24-lucid [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [New Thread 0xb6622b70 (LWP 19290)] [New Thread 0xb5cffb70 (LWP 19291)] Program received signal SIGSEGV, Segmentation fault. 0xb7ef9228 in XtInitializeWidgetClass () from /usr/lib/i386-linux-gnu/libXt.so.6 (gdb) quit A debugging session is active. Inferior 1 [process 19287] will be killed. Quit anyway? (y or n) y -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 emacs24-lucid depends on: ii emacs24-bin-common 24.2+1-2 ii libasound2 1.0.25-4 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libdbus-1-3 1.6.8-1 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgif4 4.1.6-10 ii libglib2.0-02.33.12+really2.32.4-5 ii libgnutls26 2.12.20-4 ii libgomp14.7.2-5 ii libgpm2 1.20.4-6 ii libice6 2:1.0.8-2 ii libjpeg88d-1 ii libm17n-0 1.6.4-1 ii libmagickcore5 8:6.7.7.10-5 ii libmagickwand5 8:6.7.7.10-5 ii libncurses5 5.9-10 ii libotf0 0.9.13-1 ii libpng12-0 1.2.49-3 ii librsvg2-2 2.36.1-1 ii libselinux1 2.1.9-5 ii libsm6 2:1.2.1-2 ii libtiff43.9.6-11 ii libtinfo5 5.9-10 ii libx11-62:1.5.0-1 ii libxext62:1.3.1-2 ii libxft2 2.3.1-1 ii libxml2 2.8.0+dfsg1-7 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxrender1 1:0.9.7-1 ii libxt6 1:1.1.3-1 ii xaw3dg 1.5+E-18.2 ii zlib1g 1:1.2.7.dfsg-13 emacs24-lucid recommends no packages. Versions of packages emacs24-lucid suggests: ii emacs24-common-non-dfsg 24.2+1-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
