Bug#496632: It's neither gtk_window_present, nor the urgency hint; it's a RIDDLE!
On 08/10/2013 02:38 AM, Carsten Schoenert wrote: Hello John, -snip- are you willing to write a little tip to the wiki? https://wiki.debian.org/Icedove#Tips I don't think we will change the default behavior of this setting, at least it may be possible to add a Debconf functionality to change this while installation or a dpkg-reconfigure. @Martin What do you think? Can you please recheck the behavior of this bug with the change of this setting? Thanks. Regards Carsten I'll write a tip for the wiki. Should I send the text of the tip to you? I don't have write access. On 08/10/2013 02:39 AM, martin f krafft wrote: -snip- Setting browser.tabs.loadDivertedInBackground substantially changes the behaviour of the browser, which I am not willing to accept. I don't think it's reasonable to expect users to change their browsing habits just because Mozilla doesn't behave properly wrt urgency hints. I see your point. I've spent a little time using xtrace to try to understand the X11 calls occuring at or near the time of the focus change. Until I can better filter out unrelated traffic, I don't see that xtrace is going to much help. I go back at it when I have time. Regards, John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496632: It's neither gtk_window_present, nor the urgency hint; it's a RIDDLE!
This issue has bothered me for a long time. Finally, I found a solution [1] while searching the web. In address bar, enter about:config; this takes you to advanced settings page. After clicking on the I'll be careful, I promise! button, the settings page loads. Set browser.tabs.loadDivertedInBackground to true by double clicking. Reloading iceweasel enables the changed setting. Worked for me. Cheers, John [1] http://www.techsupportalert.com/content/how-stop-firefox-stealing-window-focus.htm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708310: [xserver-xorg-video-nouveau] zaphodheads configure option no longer works
Package: xserver-xorg-video-nouveau
Version: 1:1.0.7-1
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
Dear Maintainer,
After upgrading to the 1.0.7 nouveau package, my configuration stopped
working. Downgrading back to 1.0.1 fixed the problem. I discussed the
issue with some of the nouveau devs on irc. They suggesting doing a git
bisect. After that, Dave Airlie made a patch, which I tested. He has
since added that fix in recent commits. I have tested that and submit
here a patch that would bring the 1.0.7 release up to nouveau.git and
fixes the problem for me.
Thank You,
John Vogel
--- System information. ---
Architecture: amd64
Kernel: Linux 3.8.12
Debian Release: jessie/sid
900 unstabledebian.cs.binghamton.edu
800 testing security.debian.org
800 testing debian.cs.binghamton.edu
500 experimentalmozilla.debian.net
500 experimentaldebian.cs.binghamton.edu
--- Package information. ---
Depends (Version) | Installed
===-+-==
libc6 (= 2.15) | 2.17-2
libdrm-nouveau2 (= 2.4.34) | 2.4.40-1
libudev0 (= 146) | 175-7.2
xorg-video-abi-12 |
xserver-xorg-core (= 2:1.12.3.901) | 2:1.12.4-6
Recommends(Version) | Installed
===-+-
libgl1-mesa-dri (= 7.11.1) | 8.0.5-4+b1
Package's Suggests field is empty.
-8---8---8---8---8---8---8---8---8--
Please attach the file:
/tmp/reportbug-ng-xserver-xorg-video-nouveau-idV6Hs.txt
to the mail. I'd do it myself if the output wasn't too long to handle.
Thank you!
-8---8---8---8---8---8---8---8---8--
diff --git a/src/nouveau_xv.c b/src/nouveau_xv.c
index f7dc2bc..8eafcf0 100644
--- a/src/nouveau_xv.c
+++ b/src/nouveau_xv.c
@@ -1095,7 +1095,7 @@ NVPutImage(ScrnInfoPtr pScrn, short src_x, short src_y, short drw_x,
NVCopyNV12ColorPlanes(buf + s2offset,
buf + s3offset, dst,
line_len, srcPitch2,
- nlines, line_len);
+ nlines, npixels);
}
} else {
for (i = 0; i nlines; i++) {
@@ -1161,7 +1161,7 @@ CPU_copy:
NVCopyNV12ColorPlanes(buf + s2offset,
buf + s3offset,
map, dstPitch, srcPitch2,
- nlines, line_len);
+ nlines, npixels);
}
} else {
/* YUY2 and RGB */
diff --git a/src/nv_accel_common.c b/src/nv_accel_common.c
index b06fe0c..18e6a2f 100644
--- a/src/nv_accel_common.c
+++ b/src/nv_accel_common.c
@@ -649,8 +649,10 @@ NVAccelCommonInit(ScrnInfoPtr pScrn)
else
if (pNv-Architecture NV_ARCH_E0)
INIT_CONTEXT_OBJECT(M2MF_NVC0);
- else
+ else {
INIT_CONTEXT_OBJECT(P2MF_NVE0);
+ INIT_CONTEXT_OBJECT(COPY_NVE0);
+ }
/* 3D init */
switch (pNv-Architecture) {
@@ -702,6 +704,7 @@ void NVAccelFree(ScrnInfoPtr pScrn)
nouveau_object_del(pNv-NvMemFormat);
nouveau_object_del(pNv-NvSW);
nouveau_object_del(pNv-Nv3D);
+ nouveau_object_del(pNv-NvCOPY);
nouveau_bo_ref(NULL, pNv-scratch);
}
diff --git a/src/nv_driver.c b/src/nv_driver.c
index 2b74fc6..8a112db 100644
--- a/src/nv_driver.c
+++ b/src/nv_driver.c
@@ -60,7 +60,7 @@ static Bool NVUnmapMem(ScrnInfoPtr pScrn);
#define NOUVEAU_PCI_DEVICE(_vendor_id, _device_id) \
{ (_vendor_id), (_device_id), PCI_MATCH_ANY, PCI_MATCH_ANY,\
- 0x0003, 0x00ff, 0 }
+ 0x0003, 0x00ff, 0 }
static const struct pci_id_match nouveau_device_match[] = {
NOUVEAU_PCI_DEVICE(0x12d2, PCI_MATCH_ANY),
@@ -80,6 +80,13 @@ static Bool NVPlatformProbe(DriverPtr driver,
intptr_t dev_match_data);
#endif
+_X_EXPORT int NVEntityIndex = -1;
+
+static int getNVEntityIndex(void)
+{
+ return NVEntityIndex;
+}
+
/*
* This contains the functions needed by the server after loading the
* driver module. It must be supplied, and gets added the driver list by
@@ -228,6 +235,8 @@ NVDriverFunc(ScrnInfoPtr scrn, xorgDriverFuncOp op, void *data)
static void
NVInitScrn(ScrnInfoPtr pScrn, int entity_num)
{
+ DevUnion *pPriv;
+
pScrn-driverVersion= NV_VERSION;
pScrn-driverName = NV_DRIVER_NAME;
pScrn-name = NV_NAME;
@@ -242,6 +251,15 @@ NVInitScrn(ScrnInfoPtr pScrn, int entity_num)
pScrn-FreeScreen = NVFreeScreen;
xf86SetEntitySharable(entity_num);
+ if (NVEntityIndex == -1)
+ NVEntityIndex = xf86AllocateEntityPrivateIndex();
+
+ pPriv = xf86GetEntityPrivate(entity_num,
+ NVEntityIndex);
+ if (!pPriv-ptr) {
+ pPriv-ptr = xnfcalloc(sizeof(NVEntRec), 1);
+ }
+
xf86SetEntityInstanceForScreen(pScrn, entity_num,
xf86GetNumEntityInstances(entity_num) - 1);
}
@@ -303,6 +321,7 @@ NVHasKMS(struct pci_device *pci_dev)
case 0xc0:
case 0xd0:
case 0xe0:
+ case 0xf0:
break;
default:
xf86DrvMsg(-1, X_ERROR, Unknown chipset: NV%02x\n, chipset);
@@ -682,15 +701,37 @@ nouveau_setup_capabilities(ScrnInfoPtr pScrn
Bug#693494: [stterm] TNAME is still defined as st-256color
Package: stterm
Version: 0.0~20120227+hg244-1
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
After starting stterm, terminal based programs give error about
non-functional terminal. The define in config.def.h is set to
st-256color, should be stterm-256color. Patch attached.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.5-trunk-amd64
Debian Release: wheezy/sid
900 unstableftp-nyc.osuosl.org
800 testing security.debian.org
800 testing ftp-nyc.osuosl.org
500 experimentalftp-nyc.osuosl.org
--- Package information. ---
Depends (Version) | Installed
===-+-===
libc6 (= 2.4) | 2.13-36
libx11-6| 2:1.5.0-1
Package's Recommends field is empty.
Package's Suggests field is empty.
--- stterm-0.0~20120227+hg244.orig/config.def.h
+++ stterm-0.0~20120227+hg244/config.def.h
@@ -75,7 +75,7 @@ static Key key[] = {
};
/* Set TERM to this */
-#define TNAME st-256color
+#define TNAME stterm-256color
/* Line drawing characters (sometime specific to each font...) */
static char gfx[] = {
Bug#665668: xsensors chokes on unsupported sensor features
Hi Nanley, Thanks for taking the time to look into this. If you see any need for improvements in the patches, I will be interested to see what you have to say. My time at present is very limited, but I'll be glad to help as much as I'm able. Cheers, John On 05/10/2012 08:21 PM, Nanley Chery wrote: Hi John, Thank you very much for your patches! I have recently finished a semester of school and thus will have time to review your work in the coming weeks. I appreciate your patience on this issue. Thanks, Nanley -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667443: cxref dumps core with function def with function pointer
Package: cxref
Version: 1.6c-3
Severity: normal
Greetings,
When cxref encounters a function definition that contains a pointer to function
in the arguments, it segfaults. I have included a smal test file that
demonstrates what I'm seeing. The command line I'm using to reproduce this is:
cxref -xref -CPP -E -CC -dD -dI cxref-bomb.c
Trying to use cxref-cpp prevents the segfault, but output is empty except for
the default header from cxref. Switching the comment from the int (*f)(int,int)
to the int f is enough to get cxref through without segfaulting.
I've spent some time trying to get a handle on the fault, but I seems to lead
to the lexer or more likely the parser. If I get some time I'll try to dig
deeper on this. Maybe later this month.
Thanks for your time and efforts
-John
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'testing'), (500, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cxref depends on:
ii debconf [debconf-2.0] 1.5.42
ii gcc4:4.6.3-4
ii libc6 2.13-27
cxref recommends no packages.
Versions of packages cxref suggests:
ii cxref-doc1.6c-3
ii iceweasel [www-browser] 10.0.3esr-3
ii lynx-cur [www-browser] 2.8.8dev.12-2
ii texlive-binaries 2011.20120328-1
-- Configuration Files:
/etc/cxref/config changed [not included]
/etc/cxref/cxref-cpp.defines changed [not included]
/* cxref-bomb.c */
#include stdio.h
int
f1 (a, b)
int a, b;
{
return a + b;
}
int
f2 (a, b)
int a, b;
{
return a * b;
}
int
f3 (a, b, f)
int a, b;
int (*f)(int, int);
/*int f;*/
{
return f(a, b);
}
int
main (argc, argv)
int argc;
char *argv[];
{
int d = 1, e =2;
int g, h;
int (*fp)(int,int);
/* g = f3(d, e, f1);
h = f3(d, e, f2);*/
fp = f1;
g = fp(d, e);
fp = f2;
h = fp(d, e);
printf (d=%d e=%d d+e=g=%d d*e=h=%d\n, d, e, g, h);
return 0;
}
Bug#665504: xsensors chokes on command line optins
Package: xsensors
Version: 0.70-2
Severity: important
Tags: patch
Dear Maintainer,
On new hardware and fresh installation, xsensors failed to start. From the
command line, I got the error GUI failed!. Tried various options, but
nothing helped. After running it through gdb and seeing a problem with the
command line parsing, I came up with the patch that is attached to this
bug report. This fixes the command line problem.
Now that I could get xsensors to handle the command line, I found another
problem. When setting up the subfeatures for the chip, if it finds
something other than a temp, fan, or volt feature, it stops processing
sensors and displays what it has (including an empty tab for sensor it
choked on). Patch forthcoming.
Regards,
John Vogel jvog...@stny.rr.com
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xsensors depends on:
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-27
ii libcairo2 1.10.2-7
ii libfontconfig1 2.8.0-3.1
ii libfreetype62.4.8-1
ii libgdk-pixbuf2.0-0 2.24.1-1
ii libglib2.0-02.30.2-6
ii libgtk2.0-0 2.24.10-1
ii libpango1.0-0 1.29.4-3
ii libsensors4 1:3.3.1-2
Versions of packages xsensors recommends:
ii lm-sensors 1:3.3.1-2
xsensors suggests no packages.
-- no debconf information
From: John Vogel jvog...@stny.rr.com
Subject: Fix passing of command line to start_gui() from main()
* Add gtk_parse_args() in main() so gtk std args are stripped before getopt().
* Add nargc and nargv to update arg vector for start_gui().
* Adjust arg parsing in start_gui().
---
diff -uNr a/src/gui.c b/src/gui.c
--- a/src/gui.c 2012-03-24 08:38:28.247092369 -0400
+++ b/src/gui.c 2012-03-24 08:48:11.955097035 -0400
@@ -547,8 +547,8 @@
gtk_container_add( GTK_CONTAINER (mainwindow), notebook );
-if ( argc = 2 ) {
-for ( i = 1; i argc; i++ ) {
+if ( argc 0 ) {
+for ( i = 0; i argc; i++ ) {
head = add_sensor_chips( notebook, argv[i] );
if ( head == NULL )
return FAILURE;
diff -uNr a/src/main.c b/src/main.c
--- a/src/main.c 2012-03-24 08:38:28.247092368 -0400
+++ b/src/main.c 2012-03-24 08:45:23.539095688 -0400
@@ -61,6 +61,10 @@
char *sens_config = NULL;
FILE *sens_conf_file = NULL;
char *temp_str = NULL;
+int nargc;
+char **nargv;
+
+gtk_parse_args (argc, argv);
/* Process arguements. */
while ( ( c = getopt( argc, argv, fhc:i:t:v ) ) != EOF ) {
@@ -105,6 +109,9 @@
}
}
+nargc = argc - optind;
+nargv = (char **)argv+optind;
+
/* Open the config file if specified. */
if ( sens_config
( sens_conf_file = fopen( sens_config, r ) ) == NULL ) {
@@ -122,7 +129,7 @@
}
/* This will start the GUI. */
-if ( start_gui( argc, argv ) != SUCCESS ) {
+if ( start_gui( nargc, nargv ) != SUCCESS ) {
fprintf( stderr, GUI failed!\n );
}
Bug#665660: apcupsd crashes during normal system shutdown
Package: apcupsd Version: 3.14.10-1 Severity: normal Dear Maintainer, While catching up on some much needed log file checking, I noticed a segfault logged about apcupsd. For the last week or so, it has consistantly crashed on every normal shutdown. /var/log/messages: Mar 24 20:08:05 stygian shutdown[4550]: shutting down for system reboot Mar 24 20:08:09 stygian kernel: [ 1140.462351] apcupsd[1398]: segfault at 108 ip 00412cd9 sp 7fff3734aa00 error 4 in apcupsd[40+3a000] Mar 24 20:08:10 stygian kernel: Kernel logging (proc) stopped. /var/log/apcupsd.events: 2012-03-14 20:30:42 -0400 apcupsd 3.14.10 (13 September 2011) debian startup succeeded 2012-03-14 23:43:42 -0400 apcupsd exiting, signal 15 2012-03-14 23:43:44 -0400 apcupsd shutdown succeeded 2012-03-24 19:49:27 -0400 apcupsd 3.14.10 (13 September 2011) debian startup succeeded 2012-03-24 20:08:09 -0400 apcupsd exiting, signal 15 March 14, was the last time apcupsd didn't crash during normal shutdown. I shut apcupsd down manually, and it succeeded without error. I've tried to get a core dump, but so far, no such luck. Soft and hard limits are set to unlimited and I have a core dump directory set to 1777 that is enabled at every boot: $(echo /var/log/dumps/core.%e.%p /proc/sys/kernel/core_pattern). I don't know how to troubleshoot this more, but I'm open to suggestions. This hasn't affected actual usability. I've had two or three main power fails in the last couple days with no problems, all worked as expected. I haven't changed much in the main configuration file, other than to set my hostname and cable type. If you would like, I will send it or a diff from the original. Regards, John Vogel jvog...@stny.rr.com -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apcupsd depends on: ii libc6 2.13-27 ii libgcc1 1:4.7.0-1 ii libwrap0 7.6.q-23 Versions of packages apcupsd recommends: ii apcupsd-doc 3.14.10-1 Versions of packages apcupsd suggests: ii apcupsd-cgi 3.14.10-1 ii udev 175-3.1 -- Configuration Files: /etc/apcupsd/apcupsd.conf changed [not included] /etc/default/apcupsd changed [not included] -- 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#665668: xsensors chokes on unsupported sensor features
Package: xsensors
Version: 0.70-2
Severity: important
Tags: patch
Dear Maintainer,
Here is the other patch I mentioned in #665504 as forthcoming.
When add_sensor_tab() probes the sensor's subfeatures, if it finds one that is
upsupported by xsensors, it stops probing. If any supported senors have already
been set up, then these get displayed (as well as the empty tab for the
unsupported sensor). If no supported sensors are setup before this choke, then
all subsequent sensors are ignored and the console sees:
Couldn't parse chip name_of_chip! Exiting!
GUI failed!
Attached patch just does a quick loop through the sensor's features. If a
supported feature is found, it allows add_sensor_tab() to do it's thing. If
not, it forces the outer loop to skip to the next sensor, if there is one.
For your convience, I also attached a rolled patch that also covers #665504 and
this report.
Regards,
John Vogel jvog...@stny.rr.com
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xsensors depends on:
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-27
ii libcairo2 1.10.2-7
ii libfontconfig1 2.8.0-3.1
ii libfreetype62.4.8-1
ii libgdk-pixbuf2.0-0 2.24.1-1
ii libglib2.0-02.30.2-6
ii libgtk2.0-0 2.24.10-1
ii libpango1.0-0 1.29.4-3
ii libsensors4 1:3.3.1-2
Versions of packages xsensors recommends:
ii lm-sensors 1:3.3.1-2
xsensors suggests no packages.
From: John Vogel jvog...@stny.rr.com
Subject: Check for unsupported sensor features before chip tab creation
* Add feature check on current sensor before creating tab window for chip;
prevents add_sensor_tab() from choking on unsupported features.
---
diff -uNr a/src/gui.c b/src/gui.c
--- a/src/gui.c 2012-03-24 22:10:45.046471888 -0400
+++ b/src/gui.c 2012-03-24 22:13:14.406475648 -0400
@@ -455,6 +455,26 @@
}
while ( ( name = sensors_get_detected_chips( pquery, chipnum ) ) != NULL ) {
+/* This is a hack. what really needs to be done is to separate the gui code
+ from the chip feature parsing. Then this won't even be needed at window
+ creation time at all. */
+const sensors_feature *feature;
+int chipnum2 = 0;
+int use_chip = 0;
+while ((feature = sensors_get_features (name, chipnum2)) (!use_chip)) {
+switch (feature-type) {
+case SENSORS_FEATURE_TEMP:
+case SENSORS_FEATURE_IN:
+case SENSORS_FEATURE_FAN:
+use_chip++;
+break;
+default:
+break;
+}
+}
+if (!use_chip)
+continue;
+
#ifdef DEBUG_XSENSORS
printf( Adding tab for %s\n, name-prefix );
#endif
Binary files a/src/.gui.c.swp and b/src/.gui.c.swp differ
diff -uNr a/src/gui.c b/src/gui.c
--- a/src/gui.c 2012-03-24 22:22:54.206490260 -0400
+++ b/src/gui.c 2012-03-24 22:24:11.918491987 -0400
@@ -455,6 +455,26 @@
}
while ( ( name = sensors_get_detected_chips( pquery, chipnum ) ) != NULL ) {
+/* This is a hack. what really needs to be done is to separate the gui code
+ from the chip feature parsing. Then this won't even be needed at window
+ creation time at all. */
+const sensors_feature *feature;
+int chipnum2 = 0;
+int use_chip = 0;
+while ((feature = sensors_get_features (name, chipnum2)) (!use_chip)) {
+switch (feature-type) {
+case SENSORS_FEATURE_TEMP:
+case SENSORS_FEATURE_IN:
+case SENSORS_FEATURE_FAN:
+use_chip++;
+break;
+default:
+break;
+}
+}
+if (!use_chip)
+continue;
+
#ifdef DEBUG_XSENSORS
printf( Adding tab for %s\n, name-prefix );
#endif
@@ -547,8 +567,8 @@
gtk_container_add( GTK_CONTAINER (mainwindow), notebook );
-if ( argc = 2 ) {
-for ( i = 1; i argc; i++ ) {
+if ( argc 0 ) {
+for ( i = 0; i argc; i++ ) {
head = add_sensor_chips( notebook, argv[i] );
if ( head == NULL )
return FAILURE;
diff -uNr a/src/main.c b/src/main.c
--- a/src/main.c 2012-03-24 22:22:54.206490260 -0400
+++ b/src/main.c 2012-03-24 22:24:03.238491513 -0400
@@ -61,6 +61,10 @@
char *sens_config = NULL;
FILE *sens_conf_file = NULL;
char *temp_str = NULL;
+int nargc;
+char **nargv;
+
+gtk_parse_args (argc, argv);
/* Process arguements. */
while ( ( c = getopt( argc, argv, fhc:i:t:v ) ) != EOF ) {
@@ -105,6 +109,9 @@
}
}
+nargc = argc - optind
Bug#654395: additional patches for newer libav sources
On 01/22/2012 11:48 AM, Kevin Roy wrote: Hi John, -- First, this patch does not have anything related to this bug report so next time, you are more than welcome to open another bug report. Next, I don't know how your patch managed to negates the patch 0009 but if it does, it's not the good way to solve this. Instead, an update to the ffmpeg_compat.h is only needed (cf patch attached to #656502). Thanks for your concern in blender package, Cheers I apologize for posting to this bug improperly. In my haste to get blender working on my system again, I jumped at a chance to help. I realize now that my method and actions have actually led to disrupting the people doing work that is over my head. In the future, I will think more carefully before I post and to be more thorough in checking that I'm posting to the correct bug. I certainly didn't intend to step on toes, but it's clear to me now that I did. Thank you for your patience and forbearance. Cordially, John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654395: additional patches for newer libav sources
I had the same problem with blender 2.61-1 segfaulting on my wheezy/sid
box. So I went about trying to build from git. Right away had problems
with missing headers declarations for libavutil/mathematics.h. Then, had
problems with avformat_alloc_open_context2() in
intern/audaspace/ffmpeg/AUD_FFMPEGWriter.cpp. I found a fix in Gentoo's
ebuild for blender-2.60a which negates most of the current
debian/patches/0009-fix_FTBFS_ffmpeg_debian.patch. So I added the first
patch below and replaced the 0009 patch with the second patch below (the
one I found for the Gentoo ebuild).
Builds fine and blender seems to running fine on my system, using up to
date sid and strictly pure debian system other then my wacom driver
(upstream kernel module and xorg driver).
---
intern/ffmpeg/ffmpeg_compat.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/intern/ffmpeg/ffmpeg_compat.h b/intern/ffmpeg/ffmpeg_compat.h
index dfdad22..bf6e4a9 100644
--- a/intern/ffmpeg/ffmpeg_compat.h
+++ b/intern/ffmpeg/ffmpeg_compat.h
@@ -74,6 +74,10 @@
#define FFMPEG_SWSCALE_COLOR_SPACE_SUPPORT
#endif
+#if (LIBAVUTIL_VERSION_MAJOR 51) || ((LIBAVUTIL_VERSION_MAJOR == 51)
(LIBAVUTIL_VERSION_MINOR = 9))
+#include libavutil/mathematics.h
+#endif
+
#ifndef FFMPEG_HAVE_AVIO
#define AVIO_FLAG_WRITE URL_WRONLY
#define avio_open url_fopen
--
---
intern/audaspace/ffmpeg/AUD_FFMPEGWriter.cpp | 13 ++---
1 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/intern/audaspace/ffmpeg/AUD_FFMPEGWriter.cpp
b/intern/audaspace/ffmpeg/AUD_FFMPEGWriter.cpp
index 702c366..4fadbd1 100644
--- a/intern/audaspace/ffmpeg/AUD_FFMPEGWriter.cpp
+++ b/intern/audaspace/ffmpeg/AUD_FFMPEGWriter.cpp
@@ -38,6 +38,8 @@ extern C {
#include libavcodec/avcodec.h
#include libavformat/avformat.h
#include libavformat/avio.h
+#include libavutil/mathematics.h
+#include libavutil/avstring.h
#include ffmpeg_compat.h
}
@@ -55,10 +57,15 @@ AUD_FFMPEGWriter::AUD_FFMPEGWriter(std::string
filename, AUD_DeviceSpecs specs,
{
static const char* formats[] = { NULL, ac3, flac, matroska,
mp2, mp3, ogg, wav };
- if(avformat_alloc_output_context2(m_formatCtx, NULL, formats[format],
filename.c_str()))
- AUD_THROW(AUD_ERROR_FFMPEG, context_error);
+ m_formatCtx = avformat_alloc_context();
+if (!m_formatCtx) AUD_THROW(AUD_ERROR_FFMPEG, context_error);
- m_outputFmt = m_formatCtx-oformat;
+ av_strlcpy(m_formatCtx-filename, filename.c_str(),
sizeof(m_formatCtx-filename));
+ m_outputFmt = m_formatCtx-oformat = av_guess_format(formats[format],
filename.c_str(), NULL);
+ if (!m_outputFmt) {
+avformat_free_context(m_formatCtx);
+AUD_THROW(AUD_ERROR_FFMPEG, context_error);
+}
switch(codec)
{
--
Perhaps you have already solved these issues, but since I had trouble
building from anonscm.debian.org/pkg-multimedia/blender.git, I thought
perhaps this may help.
Regards,
John Vogel jvog...@stny.rr.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656563: [xserver-xorg-input-wacom] new upstream release 0.13.0
Package: xserver-xorg-input-wacom Version: 0.12.0-1 Severity: minor --- Please enter the report below this line. --- There is a new upstream release xf86-input-wacom-0.13.0. They have added support for the newest bamboo tablets (connect, capture, and create) and made many improvements. For kernel support, one still needs to build and install backported upstream module. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-1-amd64 Debian Release: wheezy/sid 990 unstabledebian.osuosl.org 1 experimentaldebian.osuosl.org --- Package information. --- Depends(Version) | Installed -+-=== xorg-input-abi-13| xserver-xorg-core (= 2:1.10.99.901) | 2:1.11.3.901-2 libc6 (= 2.3) | 2.13-24 libx11-6 | 2:1.4.4-4 libxi6 (= 2:1.2.0) | 2:1.4.5-1 libxinerama1 | 2:1.1.1-3 libxrandr2 (= 2:1.2.0) | 2:1.3.2-2 Package's Recommends field is empty. Suggests (Version) | Installed ===-+-=== xinput | 1.5.3-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630663: [approx] approx-import refuses to import arch-indep debs that are named as arch-dep debs
On 06/24/2011 11:23 AM, Eric Cooper wrote: Thanks for the report, but I'm a little unclear on what the problem is. What error message does approx-import --verbose print for the .debs it refuses to import, and what do you think it should do differently? Sorry for my lack of clarity. I'm not sure if it should do anything differently. What was happening was that I somehow had a bunch of .debs in my apt cache that were named as architecture dependent that should have been named as architecture independent .debs. Approx-import complained about this and refused to move them. I didn't pick up on the connection at first, and spent a bunch of time trying to figure out why they weren't being imported. When I finally made the connection, I manually deleted the problem .debs from the apt cache and everything seems fine now. I should have made notes about the error messages, but I didn't, so all I have to go on now is my memory. I remember approx-import throwing the error message about improperly named .debs. I also remember that I was trying to figure out why some 120 package files weren't being imported. Looking back on it now, I feel a bit silly that I didn't make the connection between the fact that 120 .debs weren't getting imported and the error message. I was grateful that approx-import had caught this glitch in my apt cache. So, to close it all out, closing the bug is probably the best course of action. If you need me to do anything in that regard, I will. Thank you for approx. I am very happy with it. John Vogel jvo...@stny.rr.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630921: [libmount1] tries to overwrite existing libmount
Package: libmount1 Version: 2.19.1-2 Severity: grave --- Please enter the report below this line. --- When upgrading from util-linux-2.19.1-1 et al, libmount1 install tries to overwrite previous util-linux libmount. Bypassed here by holding mount and libmount1 while upgrading the rest, then proceeded with mount and libmount1. I'm not a packaging guru, but would setting a Conflicts: or Breaks: line in the debian/control do the trick? --- System information. --- Architecture: amd64 Kernel: Linux 2.6.39-2-amd64 Debian Release: wheezy/sid 500 unstablelocalhost 500 testing localhost 500 experimentallocalhost 1 experimentallocalhost --- Package information. --- Depends (Version) | Installed ===-+- libblkid1 (= 2.17.2) | 2.19.1-2 libc6 (= 2.4) | 2.13-7 libselinux1 (= 1.32) | 2.0.98-1+b1 libsepol1 (= 1.14) | 2.0.42-1 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630663: [approx] approx-import refuses to import arch-indep debs that are named as arch-dep debs
Package: approx Version: 4.6-1 Severity: minor --- Please enter the report below this line. --- I've recently installed approx. Mostly, I have been very happy with its performance and usefulness. One thing troubled me: I was getting 120 +/- packages not imported from the existing apt cache. As I tracked down the problem, I noticed that theses same packages were also being flagged as improperly named (such as debian-reference-en_2.46_amd64.deb, but should be named debian-reference_2.46_all.deb).Two copies existed in the cache that were the same size and returned the same md5sum; this was true for most packages that were failing to be imported by approx-import. A few were older versions that should have purged with `apt-get autocleaned`, but perhaps the wrong naming prevented apt from seeing them. So, for each package failing to import, I removed the improperly named deb and then approx-import did it's job just fine. This problem was a bit frustrating, but all in all, I'm actually glad approx-import refused to import the problem packages. I realise this may seem like a non-issue to you, but I guess I think of approx as having helped me fix a small problem. I also thought that if this could happen to me, it might happen to others. So perhaps this bug report should just be closed at your own convenience. But, at least someone else might benefit from my troubles. Thanks for approx! It's great to have a program that does so much: caching proxy as well as a local repo maintainer. Good job. Respectfully, John Vogel --- System information. --- Architecture: amd64 Kernel: Linux 2.6.39-2-amd64 Debian Release: wheezy/sid 500 unstablelocalhost 500 testing localhost 500 experimentallocalhost 1 experimentallocalhost --- Package information. --- Depends (Version) | Installed ===-+-=== debconf (= 0.5) | 1.5.39 OR debconf-2.0 | libc6 (= 2.7) | 2.13-7 libpcre3 (= 8.10) | 8.12-3 adduser | 3.113 bzip2 | 1.0.5-6 curl| 7.21.6-1 openbsd-inetd | OR inet-superserver| update-inetd| 4.38+nmu1 Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== libconfig-model-approx-perl| 1.003-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629357: [clamav-docs] Add doc-base control file
Package: clamav-docs Version: 0.97+dfsg-2 Severity: wishlist Tags: patch --- Please enter the report below this line. --- I have included a short doc-base control file that works fine here: --- BEGIN clamav-docs.doc-base --- Document: clamav-docs Author: Tomasz Kojm Title: ClamAV Documentation Abstract: Documentation for the ClamAV suite Section: System/Security Format: PDF Files: /usr/share/doc/clamav-docs/clamdoc.pdf Format: HTML Index: /usr/share/doc/clamav-docs/html/index.html Files: /usr/share/doc/clamav-docs/html/*.html --- END clamav-docs.doc-base --- I hope this helps. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.39-1-amd64 Debian Release: wheezy/sid 500 unstableftp.us.debian.org 500 testing security.debian.org 500 testing ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576275: dxx-rebirth: Port of the classic game Descent
While my coding skills are subpar, I am willing to package this if there is a call for it. I have been playing around with a local copy of 0.56 on my home machine lately. But I want to know ahead of time if my deficiencies in programming will be an issue with sponsors. John Vogel jvog...@stny.rr.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606425: [debirf] trouble booting with grub2
Package: debirf
Version: 0.27-1
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
When attempting to boot from created grub iso,
boot fails. Poked around the main script and
found problems with build of grub.cfg. The issue
is with the odd ?loop? construct that is imported
as the head of the grub.cfg script. I have pasted
a small patch that works for me.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.36
Debian Release: squeeze/sid
500 unstablestygian.midgard.home
500 unstableftp.us.debian.org
500 unstablecdimage.debian.org
500 testing security.debian.org
500 testing ftp.us.debian.org
500 testing cdimage.debian.org
1 experimentalftp.us.debian.org
1 experimentalcdimage.debian.org
--- Package information. ---
Depends (Version) | Installed
===-+-=
debootstrap | 1.0.26
cpio| 2.11-5
apt | 0.8.10
fakeroot| 1.14.4-2
fakechroot | 2.13.1-1
busybox-static (= 1.14.2) |
OR busybox (= 1.14.2) | 1:1.17.1-8
klibc-utils | 1.5.20-1
Recommends(Version) | Installed
===-+-
genisoimage | 9:1.1.11-1
grub-common (= 1.98~20091114) | 1.99~20101126-1
OR syslinux-common | 2:4.03+dfsg-1
Package's Suggests field is empty.
--- /usr/bin/debirf 2010-02-17 01:40:04.0 -0500
+++ ./debirf/debirf 2010-12-08 19:07:25.850264510 -0500
@@ -587,21 +587,18 @@
# make grub.cfg
mkdir -p $ISODIR/boot/grub/
- cp /usr/share/debirf/grub2-terminal-chooser
$ISODIR/boot/grub/grub.cfg
cat $ISODIR/boot/grub/grub.cfg EOF
## MENU
-if test \$chosen_console == console ; then
- console=tty0
-fi
-if test \$chosen_console == serial ; then
- console=ttyS0,115200n8
-fi
set default=0
set timeout=4
-menuentry Debirf: $DEBIRF_LABEL, console=\$console (created $(date -R)) {
-linux /$KERNEL console=\$console
+menuentry Debirf: $DEBIRF_LABEL, console=tty0 (created $(date -R)) {
+linux /$KERNEL console=tty0
+initrd /$INITRAMFS
+}
+menuentry Debirf: $DEBIRF_LABEL, console=ttyS0,115200n8 (created
$(date -R)) {
+linux /$KERNEL console=ttyS0,115200n8
initrd /$INITRAMFS
}
EOF
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586274: ulogd: need reference to ipt and ebt ulog kernel modules
Package: ulogd Version: 1.24-2.1 Severity: normal think it would be a helpful addition to the docs to note that only one of the kernel modules for either iptables (ipt_ULOG) or ebtables (ebt_ulog) can be loaded at the same time. Attempts to load the other will result in insmod or modprobe insertion errors: Cannot allocate memory. I have been trying to track down why I couldn't load the ebt_ulog kernel module. I read on kernel.org's list archives that this is the intended behavior. On ulogd startup, ipt_ULOG module gets loaded, making ebt_ulog unavailable. While this will only be useful to those doing bridge firewalling, but it will save a lot of grief. Just having this info in the README.Debian file would seem to be enough: --- README.Debian.old 2010-06-17 21:52:31.0 -0400 +++ README.Debian.new 2010-06-17 21:51:00.0 -0400 @@ -7,4 +7,10 @@ Don't forget to adapt your /etc/ulogd.conf to those modules. Example configuration is included. +Only one of the kernel modules for either iptables (ipt_ULOG) or ebtables +(ebt_ulog) can be loaded at the same time. Attempts to load the other will +result in insmod or modprobe insertion errors: Cannot allocate memory. +To log ebtables to ulogd, ensure that ebt_ulog module is loaded before +ulogd is started. + Achille Hope this helps. Regards, John Vogel -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (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 ulogd depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ulogd recommends no packages. Versions of packages ulogd suggests: pn ulogd-mysql none (no description available) pn ulogd-pcapnone (no description available) pn ulogd-pgsql none (no description available) pn ulogd-sqlite3 none (no description available) -- debconf information: ulogd/config_syntax_changed: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
