Your message dated Sat, 6 May 2017 01:03:13 +0200
with message-id <[email protected]>
and subject line Re: Bug#860051: praat: Crashes on any attempt to run
has caused the Debian Bug report #860051,
regarding praat: Crashes on any attempt to run
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
860051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860051
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: praat
Version: 5.4.0-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
When I invoke `praat' without arguments from an ordinary shell
prompt, it crashes and displays error messages.
Here is a transcript:
$ praat
(praat:9464): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(praat:9464): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed
(praat:9464): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion
'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_colormap_get_visual: assertion
'GDK_IS_COLORMAP (colormap)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion
'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion
'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion
'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_window_new: assertion 'GDK_IS_WINDOW
(parent)' failed
Segmentation fault
-- System Information:
Debian Release: 8.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.4.30-ti-r64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages praat depends on:
ii libatk1.0-0 2.14.0-1
ii libc6 2.19-18+deb8u7
ii libcairo2 1.14.0-2.1+deb8u2
ii libfontconfig1 2.11.0-6.3+deb8u1
ii libfreetype6 2.5.2-3+deb8u1
ii libgcc1 1:4.9.2-10
ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5
ii libglib2.0-0 2.42.1-1+b1
ii libgtk2.0-0 2.24.25-3+deb8u1
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libpangoft2-1.0-0 1.36.8-3
ii libstdc++6 4.9.2-10
ii oss-compat 6
ii python 2.7.9-1
Versions of packages praat recommends:
ii xfonts-100dpi 1:1.0.3
ii xfonts-75dpi 1:1.0.3
praat suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 praat/6.0.23-1
Ok, great. I am hereby closing this bug report.
Rafael
* Alex Hedges <[email protected]> [2017-05-05 17:56]:
Yes, it does. Sorry. My .bash_history doesn't have the original command
because it has been a while since I submitted my bug report. This works
now. I guess the testing version fixed the bug. Thank you for your time.
- Alex
On Fri, May 5, 2017 at 4:39 PM, Rafael Laboissière <[email protected]>
wrote:
Does the following work for you?
praat --run getPitchTier.Praat
Rafael
* Alex Hedges <[email protected]> [2017-05-05 11:46]:
The problem persists using the testing version of the package. I believe
the problem with running praat is that my system lacks a monitor. I can
only access it through the terminal, but it crashes, even when I only try
to run a script that has no GUI-based IO. For a specific instance, I ran
the command praat --open "getPitchTier.Praat", where getPitchTier.Praat
contains the following contents:
Read from file: "sentence.wav" selectObject: "Sound sentence" To
Manipulation: 0.01, 75, 600 Extract pitch tier Save as PitchTier
spreadsheet file: "oldPitchTier.PitchTier"
However, praat crashes regardless of input given.
- Alex
On Fri, May 5, 2017 at 8:21 AM, Rafael Laboissière <[email protected]>
wrote:
Control: tags -1 + moreinfo unreproducible
Thank you for the bug report. I cannot reproduce it in my system and I
am hereby requesting Assistance in diagnosing the cause of the problem.
Could you please check whether the problem persists using the testing or
the experimental versions of the package ?
Best,
Rafael Laboissière
* Alex Hedges <[email protected]> [2017-04-10 16:33]:
Package: praat
Version: 5.4.0-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
When I invoke `praat' without arguments from an ordinary shell prompt,
it crashes and displays error messages. Here is a transcript:
$ praat
(praat:9464): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(praat:9464): GLib-GObject-CRITICAL **: g_signal_connect_data:
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(praat:9464): Gtk-WARNING **: Screen for GtkWindow not set; you must
always set a screen for a GtkWindow before using the window
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap:
assertion 'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_colormap_get_visual: assertion
'GDK_IS_COLORMAP (colormap)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap:
assertion 'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window:
assertion 'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window:
assertion 'GDK_IS_SCREEN (screen)' failed
(praat:9464): Gdk-CRITICAL **: IA__gdk_window_new: assertion
'GDK_IS_WINDOW (parent)' failed Segmentation fault
-- System Information: Debian Release: 8.7 APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf
(armv7l)
Kernel: Linux 4.4.30-ti-r64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages praat depends on: ii libatk1.0-0
2.14.0-1 ii libc6 2.19-18+deb8u7 ii libcairo2
1.14.0-2.1+deb8u2 ii libfontconfig1 2.11.0-6.3+deb8u1 ii
libfreetype6 2.5.2-3+deb8u1 ii libgcc1 1:4.9.2-10 ii
libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-0 2.42.1-1+b1
ii libgtk2.0-0 2.24.25-3+deb8u1 ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii
libstdc++6 4.9.2-10 ii oss-compat 6 ii python
2.7.9-1
Versions of packages praat recommends: ii xfonts-100dpi 1:1.0.3 ii
xfonts-75dpi 1:1.0.3
praat suggests no packages.
-- no debconf information
--- End Message ---
