Bug#995927: Aw: Re: Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend
Dear Salvatore, thank your for your response! I'd gladly report the issue upstream, but I'm not sure on how to approach that. I'm aware of Bugzilla [1], but so far I have no account there. And the documentation [2] says, that Bugzilla is likely not the right address anyway: > Locate the driver or kernel subsystem that seems to be causing the issue. > Find out how and where its developers expect reports. Note: most of the time > this won’t be bugzilla.kernel.org, as issues typically need to be sent by mail > to a maintainer and a public mailing list. I have very little experience when it comes to the kernel. The maintainers list [3] and the code of e100 [4] suggest different e-mail addresses, according to the e1000 Sourceforge site [5], depending on whether the e100 module would be considered "in" or "out of tree". I'm also not sure which formal rules (e.g. tags) I need to follow to get through with the matter at a big company like Intel. Can you give me some advice please? [1] https://bugzilla.kernel.org/ [2] https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html#step-by-step-guide-how-to-report-issues-to-the-kernel-maintainers [3] https://www.kernel.org/doc/html/latest/process/maintainers.html#intel-ethernet-drivers [4] https://sources.debian.org/src/linux/5.14.9-2/Documentation/networking/device_drivers/ethernet/intel/e100.rst/ [5] https://sourceforge.net/projects/e1000/ regards hikaru
Bug#984585: gpicview: make zoom factor steps configurable
Package: gpicview
Version: 0.2.5-3+b1
Severity: wishlist
Tags: patch upstream
X-Debbugs-Cc: hikaru.deb...@web.de
Dear Gpicview Maintainers,
I found gpicview's default zoom factor steps to be too large for my liking, so I
wrote a small patch to make the steps configurable via the configuration file
(but not via GUI).
Please consider including this patch (or something similar) in future versions
of gpicview!
Thanks!
hikaru
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gpicview depends on:
ii libatk1.0-0 2.36.0-2
ii libc62.31-9
ii libcairo21.16.0-5
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgdk-pixbuf2.0-0 2.40.2-2
ii libglib2.0-0 2.66.7-1
ii libgtk2.0-0 2.24.33-1
ii libjpeg62-turbo 1:2.0.6-2
ii libpango-1.0-0 1.46.2-3
ii libpangocairo-1.0-0 1.46.2-3
ii libpangoft2-1.0-01.46.2-3
ii libx11-6 2:1.7.0-2
Versions of packages gpicview recommends:
ii xdg-utils 1.1.3-4
gpicview suggests no packages.
-- no debconf information
Description: Make zoom_factor configurable
.
gpicview (0.2.5-3.1) UNRELEASED; urgency=medium
.
* Non-maintainer upload.
* Add option 'zoom_factor=1.05' (old hard-coded default) in gpicview.conf
Author:
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update: 2021-03-05
--- /dev/null
+++ gpicview-0.2.5/.vimrc
@@ -0,0 +1,2 @@
+source /usr/share/vim/vim82/defaults.vim
+set mouse=
--- gpicview-0.2.5.orig/src/main-win.c
+++ gpicview-0.2.5/src/main-win.c
@@ -372,9 +372,6 @@ static void update_btns(MainWin* mw)
gboolean main_win_open( MainWin* mw, const char* file_path, ZoomMode zoom )
{
-if(!file_path)
-return FALSE;
-
if (g_file_test(file_path, G_FILE_TEST_IS_DIR))
{
image_list_open_dir( mw->img_list, file_path, NULL );
@@ -935,14 +932,14 @@ void on_open( GtkWidget* btn, MainWin* m
void on_zoom_in( GtkWidget* btn, MainWin* mw )
{
double scale = mw->scale;
-scale *= 1.05;
+scale *= pref.zoom_factor;
main_win_set_zoom_scale(mw, scale);
}
void on_zoom_out( GtkWidget* btn, MainWin* mw )
{
double scale = mw->scale;
-scale /= 1.05;
+scale /= pref.zoom_factor;
main_win_set_zoom_scale(mw, scale);
}
--- gpicview-0.2.5.orig/src/pref.c
+++ gpicview-0.2.5/src/pref.c
@@ -27,6 +27,7 @@
#include
#include
+#include
#include "pref.h"
#include "main-win.h"
@@ -63,6 +64,20 @@ static int kf_get_int(GKeyFile* kf, cons
return TRUE;
}
+static double kf_get_double(GKeyFile* kf, const char* grp, const char* name,
double* ret )
+{
+GError* err = NULL;
+double val = g_key_file_get_double(kf, grp, name, );
+if( G_UNLIKELY(err) )
+{
+g_error_free(err);
+return FALSE;
+}
+if(G_LIKELY(ret))
+*ret = val;
+return TRUE;
+}
+
void load_preferences()
{
/* FIXME: GKeyFile is not fast enough.
@@ -83,6 +98,8 @@ void load_preferences()
pref.jpg_quality = 90;
pref.png_compression = 9;
+pref.zoom_factor = 1.05;
+
pref.show_toolbar = TRUE;
kf = g_key_file_new();
@@ -99,6 +116,8 @@ void load_preferences()
kf_get_int( kf, "General", "jpg_quality", _quality);
kf_get_int( kf, "General", "png_compression", _compression );
+kf_get_double( kf, "General", "zoom_factor", _factor );
+
kf_get_bool( kf, "General", "show_toolbar", _toolbar );
color = g_key_file_get_string(kf, "General", "bg", NULL);
@@ -149,6 +168,10 @@ void save_preferences()
fprintf( f, "jpg_quality=%d\n", pref.jpg_quality );
fprintf( f, "png_compression=%d\n", pref.png_compression );
+ /* fprintf honors the locale setting for decimal delimiters and will
write a comma instead of a point in some locales (e.g. de_DE).
+ GLib doesn't seem to be able to cope with that and won't accept
doubles with a comma. So we need to make sure to always write a point: */
+fprintf( f, "zoom_factor=%d.%03d\n", (int)pref.zoom_factor, (int)
(round((pref.zoom_factor - (int) pref.zoom_factor ) * 1000)) );
+
fprintf( f, "show_toolbar=%d\n", pref.show_toolbar );
fclose( f );
--- gpicview-0.2.5.orig/src/pref.h
+++ gpicview-0.2.5/src/pref.h
@@ -40,6 +40,8 @@ typedef struct _Pref
int jpg_quality;
int png_compression;
+
Bug#919769: firefox-esr: OB Firefox 60.4 crashes immediately on amrhf (Raspberry Pi)
I can reproduce this with firefox-esr 60.5 on a Cubieboard 2 running Stretch/armhf. However, in a Buster/armhf chroot Firefox works fine. To make sure this is not a chroot effect I tried again in a Stretch/armhf chroot and it shows the same error as the Stetch/armhf host. For sake of completeness I repeated the same in Stretch and Buster/armel chroots and got the same results as in the respective armhf counterparts. So I'd conclude this problem is specific to the Stretch/arm* architectures.
Bug#832558: [Pkg-dkms-maint] Bug#832558: Fix dkms mkdeb / mkdsc / mkbmdeb
Hello,
I understand the exchange between upstream and Debian is a bit sluggish here,
but besides that, is there a reason why Pierre's patch has never been applied?
The current situation breaks mkdeb (in some cases?) (e.g. phc_intel [1]) and
this part of Pierre's patch would fix this:
> - fix mkdeb (1): mkdeb failed because a mv command was looking for a
> package filename with -${debian_build_arch} instead of -all.
This situation has been kind of annoying ever since the Stretch release, and I
(and some others) would really appreciate having this fixed for Buster.
[1] http://linux-phc.org/forum/viewtopic.php?f=7=267
(power saving module for older Intel CPUs)
Thanks, and kind regards
hikaru
Bug#851496: Aw: Bug#851496: x11vnc/armhf: "stack smashing detected" "__libc_do_syscall ()" on nonexisting file
I made some further testing, by replacing the current glibc and x11vnc packages with the ones from before my dist-upgrade (from snapshots) and found, that the combination new glibc 2.24-8 / old x11vnc 0.9.13-1.2 does not exhibit the problem, while the combination old glibc 2.24-5 / new x11vnc 0.9.13-2 does. I therefore reassigned this bug report.
Bug#827391: nvidia-driver: Add support to Nvidia GeForce 10xx GPUs w/ driver 367.27
It turned out, I had extra characters in my debian/rules file, most likely due to a mistake while copying the patch from the wiki. This crippled my tar command, but didn't make it completely useless. So much for "following instructions". ;-) Thanks for your patience! In the end I manually installed these packages: libegl1-nvidia_367.27-1_amd64.deb libegl-nvidia0_367.27-1_amd64.deb libgl1-nvidia-glx_367.27-1_amd64.deb libgles1-glvnd-nvidia_367.27-1_amd64.deb libgles2-glvnd-nvidia_367.27-1_amd64.deb libglvnd-nvidia_367.27-1_amd64.deb libglx0-nvidia_367.27-1_amd64.deb libglx-nvidia0_367.27-1_amd64.deb libnvidia-eglcore_367.27-1_amd64.deb libnvidia-ml1_367.27-1_amd64.deb nvidia-alternative_367.27-1_amd64.deb nvidia-driver_367.27-1_amd64.deb nvidia-driver-bin_367.27-1_amd64.deb nvidia-kernel-dkms_367.27-1_amd64.deb nvidia-kernel-support_367.27-1_amd64.deb nvidia-vdpau-driver_367.27-1_amd64.deb xserver-xorg-video-nvidia_367.27-1_amd64.deb I also needed these packages from jessie-backports: glx-alternative-nvidia libvdpau1 nvidia-kernel-common nvidia-modprobe It wasn't necessary, but I thought it wouldn't hurt, to install nvidia-installer-cleanup from the backports too. Now I have this list of packages installed: # dpkg -l | grep nvidia ii glx-alternative-nvidia0.7.3~bpo8+1 amd64allows the selection of NVIDIA as GLX provider ii libegl-nvidia0:amd64 367.27-1 amd64NVIDIA binary EGL libraries ii libegl1-nvidia:amd64 367.27-1 amd64NVIDIA binary EGL stub libraries ii libgl1-nvidia-glx:amd64 367.27-1 amd64NVIDIA binary OpenGL libraries ii libgles1-glvnd-nvidia:amd64 367.27-1 amd64NVIDIA binary OpenGL|ES 1.x stub libraries ic libgles1-nvidia:amd64 340.96-1 amd64NVIDIA binary OpenGL|ES 1.x libraries ii libgles2-glvnd-nvidia:amd64 367.27-1 amd64NVIDIA binary OpenGL|ES 2.x stub libraries ic libgles2-nvidia:amd64 340.96-1 amd64NVIDIA binary OpenGL|ES 2.x libraries ii libglvnd-nvidia:amd64 367.27-1 amd64NVIDIA binary GL vendor neutral libraries ii libglx-nvidia0:amd64 367.27-1 amd64NVIDIA binary GLX libraries ii libglx0-nvidia:amd64 367.27-1 amd64Vendor neutral GL dispatch library -- libGLX ii libnvidia-eglcore:amd64 367.27-1 amd64NVIDIA binary EGL core libraries ii libnvidia-ml1:amd64 367.27-1 amd64NVIDIA Management Library (NVML) runtime library ii nvidia-alternative367.27-1 amd64allows the selection of NVIDIA as GLX provider ii nvidia-driver 367.27-1 amd64NVIDIA metapackage ii nvidia-driver-bin 367.27-1 amd64NVIDIA driver support binaries ii nvidia-installer-cleanup 20151021+1~bpo8+1 amd64cleanup after driver installation with the nvidia-installer ii nvidia-kernel-common 20151021+1~bpo8+1 amd64NVIDIA binary kernel module support files ii nvidia-kernel-dkms367.27-1 amd64NVIDIA binary kernel module DKMS source ii nvidia-kernel-support 367.27-1 amd64NVIDIA binary kernel module support files ii nvidia-legacy-check 367.27-1 amd64check for NVIDIA GPUs requiring a legacy driver ii nvidia-modprobe 358.09-1~bpo8+1 amd64utility to load NVIDIA kernel modules and create device nodes rc nvidia-settings 340.46-2 amd64tool for configuring the NVIDIA graphics driver ii nvidia-support20151021+1~bpo8+1 amd64NVIDIA binary graphics driver support files ii nvidia-vdpau-driver:amd64 367.27-1 amd64Video Decode and Presentation API for Unix - NVIDIA driver ii xserver-xorg-video-nvidia 367.27-1 amd64NVIDIA binary Xorg driver I'm wondering about two things: 1. I still have libgles1-nvidia and libgles2-nvidia from 340 on my system, while there are only libgles1-glvnd-nvidia and libgles2-glvnd-nvidia for 367. Are the latter two packages equivalent to the former ones or should
Bug#827391: nvidia-driver: Add support to Nvidia GeForce 10xx GPUs w/ driver 367.27
> Yes it should be made clearer, if you are on amd64 and want the 32 bit > libraries, not all packages should be installed. > > Basically you'll want to install libgl1-nvidia-glx-i386 (or > nvidia-driver-libs-i386 depending on the branch) and their dependencies. > > I've updated the wiki. Thanks! But that isn't the problem. fyi, I've switched the test system from i386 to amd64, but the basic problem remains. Maybe I should also tell you some things about my system setup: The test system is Jessie/amd64 on a USB stick. It is currently plugged into a computer with a GT218 chip. I know this isn't supportd by 367 anymore, but I merely want to make sure the driver installation works fine, because later I want to plug the USB stick into a computer with a GTX 1070 card. I only have access to this actual target computer sporadically, hence the test system. What I did was to install Jessie's nvidia-driver and the X-Server works. I wanted to use this package list as a template for what I actually need from 367: # dpkg -l | grep nvidia ii glx-alternative-nvidia0.5.1 amd64allows the selection of NVIDIA as GLX provider ii libegl1-nvidia:amd64 340.96-1 amd64NVIDIA binary EGL libraries ii libgl1-nvidia-glx:amd64 340.96-1 amd64NVIDIA binary OpenGL libraries ii libgles1-nvidia:amd64 340.96-1 amd64NVIDIA binary OpenGL|ES 1.x libraries ii libgles2-nvidia:amd64 340.96-1 amd64NVIDIA binary OpenGL|ES 2.x libraries ii libnvidia-eglcore:amd64 340.96-1 amd64NVIDIA binary EGL core libraries ii libnvidia-ml1:amd64 340.96-1 amd64NVIDIA Management Library (NVML) runtime library ii nvidia-alternative340.96-1 amd64allows the selection of NVIDIA as GLX provider ii nvidia-driver 340.96-1 amd64NVIDIA metapackage ii nvidia-driver-bin 340.96-1 amd64NVIDIA driver support binaries ii nvidia-installer-cleanup 20141201+1 amd64cleanup after driver installation with the nvidia-installer ii nvidia-kernel-common 20141201+1 amd64NVIDIA binary kernel module support files ii nvidia-kernel-dkms340.96-1 amd64NVIDIA binary kernel module DKMS source ii nvidia-modprobe 340.46-1 amd64utility to load NVIDIA kernel modules and create device nodes ii nvidia-settings 340.46-2 amd64tool for configuring the NVIDIA graphics driver ii nvidia-support20141201+1 amd64NVIDIA binary graphics driver support files ii nvidia-vdpau-driver:amd64 340.96-1 amd64Video Decode and Presentation API for Unix - NVIDIA driver ii xserver-xorg-video-nvidia 340.96-1 amd64NVIDIA binary Xorg driver Since apt's dependency resolution isn't available with the self-made packages, I then wanted to replace all these packages at once via dpkg, which failed due to dependency problems. To track these down, I wanted to atomize the process. nvidia-driver seemed to be a good starting point, however it complains during the installation: # dpkg -i nvidia-driver_367.27-1_amd64.deb dpkg: regarding nvidia-driver_367.27-1_amd64.deb containing nvidia-driver, pre-dependency problem: nvidia-driver pre-depends on nvidia-legacy-check (>= 343) nvidia-legacy-check is not installed. dpkg: error processing archive nvidia-driver_367.27-1_amd64.deb (--install): pre-dependency problem - not installing nvidia-driver Errors were encountered while processing: nvidia-driver_367.27-1_amd64.deb So I successfully installed nvidia-legacy-check first: # dpkg -i nvidia-legacy-check_367.27-1_amd64.deb Selecting previously unselected package nvidia-legacy-check. (Reading database ... 131797 files and directories currently installed.) Preparing to unpack nvidia-legacy-check_367.27-1_amd64.deb ... *** The following unsupported devices are present in the machine: 03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [ION] [10de:0a64] (rev a2) Unpacking nvidia-legacy-check (367.27-1) ... Setting up nvidia-legacy-check (367.27-1) ... Then I tried to install nvidia-driver, which failed: # dpkg -i nvidia-driver_367.27-1_amd64.deb (Reading database ... 131811 files and directories currently installed.) Preparing to unpack
Bug#827391: nvidia-driver: Add support to Nvidia GeForce 10xx GPUs w/ driver 367.27
Dear Luca, > Meanwhile, you can build the package from our SVN repositories following > the instructions on the wiki: > > https://wiki.debian.org/NvidiaGraphicsDrivers#Building_newer_releases_from_SVN I followed the instructions to the letter on Jessie, with the tar patch and without it (but tar from Stretch), and successfully built a bunch of packages. However, when trying to install the packages, I get errors like this one: > dpkg: error processing archive nvidia-driver_367.27-1_i386.deb (--install): > trying to overwrite '/DEBIAN/control', which is also in package > nvidia-legacy-check 367.27-1 nvidia-legacy-check 367.27-1 was already installed at that time. I suspect this problem may have to do with the fact, that all the files in the packages seem to be present multiple times. For example (note the duplicates): # dpkg -c nvidia-driver-bin_367.27-1_i386.deb drwxr-xr-x root/root 0 2016-07-09 19:53 ./ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/nvidia/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/nvidia/current/ -rwxr-xr-x root/root 23697 2016-06-10 04:51 ./usr/lib/nvidia/current/nvidia-bug-report.sh -rwxr-xr-x root/root182172 2016-06-10 04:27 ./usr/lib/nvidia/current/nvidia-debugdump drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/lintian/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/lintian/overrides/ -rw-r--r-- root/root 301 2016-07-09 19:52 ./usr/share/lintian/overrides/nvidia-driver-bin drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/nvidia/ -rw-r--r-- root/root 5225 2016-06-10 03:28 ./usr/share/nvidia/nvidia-application-profiles-367.27-rc -rw-r--r-- root/root 6041 2016-06-10 03:28 ./usr/share/nvidia/nvidia-application-profiles-367.27-key-documentation drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/doc/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/doc/nvidia-driver-bin/ -rw-r--r-- root/root 67033 2016-06-10 03:23 ./usr/share/doc/nvidia-driver-bin/changelog.gz -rw-r--r-- root/root 10859 2016-02-01 19:58 ./usr/share/doc/nvidia-driver-bin/copyright -rw-r--r-- root/root 82986 2016-06-15 19:20 ./usr/share/doc/nvidia-driver-bin/changelog.Debian.gz drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/bug/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/bug/nvidia-driver-bin/ -rwxr-xr-x root/root 3100 2016-02-16 14:22 ./usr/share/bug/nvidia-driver-bin/script -rw-r--r-- root/root 785 2016-07-09 19:52 ./usr/share/bug/nvidia-driver-bin/control drwxr-xr-x root/root 0 2016-07-09 19:54 ./DEBIAN/ -rw-r--r-- root/root 864 2016-07-09 19:54 ./DEBIAN/control -rw-r--r-- root/root 813 2016-07-09 19:54 ./DEBIAN/md5sums drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/nvidia/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/nvidia/current/ -rwxr-xr-x root/root 23697 2016-06-10 04:51 ./usr/lib/nvidia/current/nvidia-bug-report.sh -rwxr-xr-x root/root182172 2016-06-10 04:27 ./usr/lib/nvidia/current/nvidia-debugdump drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/lintian/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/lintian/overrides/ -rw-r--r-- root/root 301 2016-07-09 19:52 ./usr/share/lintian/overrides/nvidia-driver-bin drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/nvidia/ -rw-r--r-- root/root 5225 2016-06-10 03:28 ./usr/share/nvidia/nvidia-application-profiles-367.27-rc -rw-r--r-- root/root 6041 2016-06-10 03:28 ./usr/share/nvidia/nvidia-application-profiles-367.27-key-documentation drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/doc/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/doc/nvidia-driver-bin/ -rw-r--r-- root/root 67033 2016-06-10 03:23 ./usr/share/doc/nvidia-driver-bin/changelog.gz -rw-r--r-- root/root 10859 2016-02-01 19:58 ./usr/share/doc/nvidia-driver-bin/copyright -rw-r--r-- root/root 82986 2016-06-15 19:20 ./usr/share/doc/nvidia-driver-bin/changelog.Debian.gz drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/bug/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/share/bug/nvidia-driver-bin/ -rwxr-xr-x root/root 3100 2016-02-16 14:22 ./usr/share/bug/nvidia-driver-bin/script -rw-r--r-- root/root 785 2016-07-09 19:52 ./usr/share/bug/nvidia-driver-bin/control drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/nvidia/ drwxr-xr-x root/root 0 2016-07-09 19:53 ./usr/lib/nvidia/current/ -rwxr-xr-x root/root 23697 2016-06-10 04:51
Bug#821958: Re: Bug#821958: moc: Please make track number format configurable
Thanks for the links! I stumbled upon #2 yesterday before patching the source, but somehow I missed #1. #2 doesn't seem all that relevant to me, except for signaling that there might or might not be some improvement coming from upstream in the long run. #1 looks pretty similar to my patch. But this thread is from 2010 and dead, so I don't expect that to be implemented anymore. bottom line: Could you please include my patch in the Debian package until upstream comes up with something similar?
Bug#783293: Aw: Re: Bug#783293: browsers crash with 'illegal instruction' on i586
From: Bernhard Übelacker bernha...@vr-web.de I tried as a workaround to build a libqtwebkit package with attached little modification (does disable JIT, like for other archs). With this the browser does not crash. confirmed on real hardware. From: Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com Hi Hikaru! Is there any chance for you to see if this also happens with arora? The difference here is that arora currently uses Qt5 and it would be useful to know if the bug is also reproducible there. I tried, but unfortunately my i586 machine only has 320MB RAM and I can't upgrade it. It's already swapping heavily to even start the browser. Getting any website loaded before the Stretch release might be difficult. From: Sune Vuorela s...@debian.org I agree that just disabling the JITter is not an option. If someone improves the jitter, or making jitting optional for these architectures, we can look into it again. Until a patch shows up that does that, I'm going to mark this wontfix from the qt side of things. I totally understand your reasoning and I have next to no knowledge about Debian bug report tags. But from my layman's point of view marking it as 'wontfix' seems a little unfortunate. It might be misinterpreted as: We don't care that our package is broken on half of the architecture (i386). Wouldn't 'moreinfo' be more appropriate as in?: We need more info on how to fix it in a way that works for i586 but doesn't put i686 on a disadvantage. After all i586 is the minimum requirement all 'i386' packages should work on, right? From: Bernhard Übelacker bernha...@vr-web.de On Tue, 28 Apr 2015 21:40:34 +0200 Emilio Pozuelo Monfort po...@debian.org wrote: If you can try webkitgtk, you should be able to set JavaScriptCoreUseJIT=0 in the environment as a workaround. I did a export JavaScriptCoreUseJIT=0. But still qupzilla/libQtWebKit and xombrero/libwebkitgtk-3.0/libjavascriptcoregtk-3.0 received the signal SIGILL as before (inside qemu VM, '-cpu pentium'). confirmed. kind regards hikaru -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783082: Aw: Re: Bug#783082: video players crash with 'illegal instruction' on i586
Sorry for the delay. I can confirm that both of Bernhard's patch variants work on real hardware, in mplayer2 and vlc. Thank you very much! kind regards hikaru -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783082: Aw: Re: linux-image-3.16.0-4-586: video players/browsers crash with 'illegal instruction' on i586
Also installing the -dbg packages for the shared objects shown in your backtraces would give even better results: libjavascriptcoregtk-1.0-0-dbg libqtwebkit4-dbg I installed these packages: libjavascriptcoregtk-1.0-0-dbg libqtwebkit4-dbg libc6-dbg:i386 libglib2.0-0-dbg:i386 libqt4-dbg:i386 and got this backtrace for midori: Program received signal SIGILL, Illegal instruction. 0xb4984144 in llint_op_jnless () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 (gdb) bt #0 0xb4984144 in llint_op_jnless () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #1 0xae5dcf50 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) display/i $pc 1: x/i $pc = 0xb4984144 llint_op_jnless+153:fucomip %st(1),%st and qupzilla: Program received signal SIGILL, Illegal instruction. 0xb688b51a in llint_op_jnless () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 (gdb) bt #0 0xb688b51a in llint_op_jnless () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #1 0xacc52070 in ?? () #2 0xb67fedb5 in JSC::Interpreter::executeCall (this=0xfffb, callFrame=0xbf8ab814, function=0x0, callType=CallTypeNone, callData=0x0, thisValue=..., args=0xbf8ab814) at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/jit/JITCode.h:134 #3 0xb69180cf in JSC::call (exec=0xaca0d5c0, functionObject=..., callType=CallTypeNone, callData=0x0, thisValue=..., args=0xb739d000) at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/runtime/CallData.cpp:39 #4 0xb69608fb in JSC::boundFunctionCall (exec=0x4274ce73) at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/runtime/JSBoundFunction.cpp:53 #5 0xb67fee3f in JSC::Interpreter::executeCall (this=0xfffb, callFrame=0xbf8ab9c4, function=0x0, callType=3213539656, callData=0xb697bfa2 JSC::JSLockHolder::JSLockHolder(JSC::JSGlobalData*)+50, thisValue=..., args=0xb73ad280 WebCore::JSMainThreadExecState::s_mainThreadState) at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/interpreter/Interpreter.cpp:1057 #6 0xb69180cf in JSC::call (exec=0xacb4ffe0, functionObject=..., callType=CallTypeNone, callData=0xbf8ab948, thisValue=..., args=0xb739d000) at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/runtime/CallData.cpp:39 #7 0xb527edda in WebCore::ScheduledAction::executeFunctionInContext(JSC::JSGlobalObject*, JSC::JSValue, WebCore::ScriptExecutionContext*) () at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/HashTable.h:1107 #8 0xb527f3f8 in WebCore::ScheduledAction::execute(WebCore::Document*) () at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/HashTable.h:1107 #9 0xb5901db0 in WebCore::DOMTimer::fired() () at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/WebCore/platform/ScrollAnimator.h:73 #10 0xb5a44c07 in WebCore::ThreadTimers::sharedTimerFiredInternal() [clone .part.5] () at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Functional.h:355 #11 0xb5d0a9f2 in WebCore::SharedTimerQt::timerEvent(QTimerEvent*) () at /build/qtwebkit-bZFpMD/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Vector.h:875 #12 0xb3e9effe in QObject::event (this=0x9693e18, e=0xbf8abdec) at kernel/qobject.cpp:1253 #13 0xb429850a in QApplicationPrivate::notify_helper (this=0x951b628, receiver=0x9693e18, e=0xbf8abdec) at kernel/qapplication.cpp:4570 #14 0xb429f420 in QApplication::notify (this=0xbf8ac0c4, receiver=0x9693e18, e=0xbf8abdec) at kernel/qapplication.cpp:4356 #15 0xb3e8442a in QCoreApplication::notifyInternal (this=0xbf8ac0c4, receiver=0x9693e18, event=0xbf8abdec) at kernel/qcoreapplication.cpp:955 #16 0xb3eb91ce in sendEvent (event=0xbf8abdec, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #17 QTimerInfoList::activateTimers (this=0x951c1a4) at kernel/qeventdispatcher_unix.cpp:621 #18 0xb3eb5e49 in timerSourceDispatch (source=0x951c170) at kernel/qeventdispatcher_glib.cpp:186 #19 0xb3278da4 in g_main_dispatch (context=optimized out) at /build/glib2.0-EvFudu/glib2.0-2.42.1/./glib/gmain.c:3111 #20 g_main_context_dispatch (context=0x1) at /build/glib2.0-EvFudu/glib2.0-2.42.1/./glib/gmain.c:3710 #21 0xb32790c9 in g_main_context_iterate (context=0x951c090, block=2147115008, block@entry=1, dispatch=1, self=optimized out) at /build/glib2.0-EvFudu/glib2.0-2.42.1/./glib/gmain.c:3781 #22 0xb3279196 in g_main_context_iteration (context=0x951c090, may_block=1) at /build/glib2.0-EvFudu/glib2.0-2.42.1/./glib/gmain.c:3842 #23 0xb3eb6839 in QEventDispatcherGlib::processEvents (this=0x951c000, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #24 0xb434c516 in QGuiEventDispatcherGlib::processEvents (this=0x951c000, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #25 0xb3e82d9f in QEventLoop::processEvents (this=0xbf8ac034, flags=...) at kernel/qeventloop.cpp:149 #26 0xb3e8312e in QEventLoop::exec (this=0xbf8ac034, flags=...) at kernel/qeventloop.cpp:204 #27 0xb3e892b6 in
Bug#783082: Aw: Re: linux-image-3.16.0-4-586: video players/browsers crash with 'illegal instruction' on i586
Hello Bernhard, thanks for your reply! I will try to reproduce your findings on real hardware tomorrow. Can you have a look at the qupzilla and/or xombrero issue as well please? I'm not sure anymore if it's the same problem, because meanwhile I installed a qemu vm myself (on Wheezy/amd64) using these settings: qemu-system-i386 -cpu pentium -m 512 -hda pentium.img -cdrom debian-jessie-DI-rc3-i386-netinst.iso Then I installed a standard LXDE desktop and could reproduce the browser crashes but not the video player crashes. So far I have no gdb results because I only have very basic knowledge about it and a simple run command alone wasn't helpful. Doesn't Jessie's libav configure script already check for a K6-2 and disable i686? [1] I don't know because I'm not sure what's actually stored in $cpu at that point. regards hikaru [1] http://sources.debian.net/src/libav/6:11.3-1/configure/#L3282 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783082: Aw: Re: linux-image-3.16.0-4-586: video players/browsers crash with 'illegal instruction' on i586
Hi Bernhard, I have run your gdb examples on the K6-2 now and came to the same result for vlc: Program received signal SIGILL, Illegal instruction. [Switching to Thread 0xb0fd4b40 (LWP 1001)] 0xaf19da49 in mid_pred (c=0, b=0, a=0) at /build/libav-H9AQHK/libav-11.3/libavcodec/x86/mathops.h:77 77 /build/libav-H9AQHK/libav-11.3/libavcodec/x86/mathops.h: No such file or directory. (gdb) bt #0 0xaf19da49 in mid_pred (c=0, b=0, a=0) at /build/libav-H9AQHK/libav-11.3/libavcodec/x86/mathops.h:77 #1 ff_h263_pred_motion (s=0xb25322c0, block=0, dir=0, px=0xb0fd3f84, py=0xb0fd3f88) at /build/libav-H9AQHK/libav-11.3/libavcodec/h263.c:365 #2 0xaf2a3f1c in ff_h263_decode_mb (s=0xb25322c0, block=0xb253ae60) at /build/libav-H9AQHK/libav-11.3/libavcodec/ituh263dec.c:654 #3 0xaf19e044 in decode_slice (s=0xb25322c0) at /build/libav-H9AQHK/libav-11.3/libavcodec/h263dec.c:234 #4 0xaf19ebc0 in ff_h263_decode_frame (avctx=0xb2592520, data=0xb25928a0, got_frame=0xb0fd41a8, avpkt=0xb0fd41d4) at /build/libav-H9AQHK/libav-11.3/libavcodec/h263dec.c:575 #5 0xaf418c9c in avcodec_decode_video2 (avctx=0xb2592520, picture=0xb25928a0, got_picture_ptr=0xb0fd41a8, avpkt=0xb0fd41d4) at /build/libav-H9AQHK/libav-11.3/libavcodec/utils.c:1600 #6 0xb1a79801 in DecodeVideo (p_dec=0xb258bd58, pp_block=0xb0fd41a8) at codec/avcodec/video.c:631 #7 0xb750828e in DecoderDecodeVideo (p_dec=0xb258bd58, p_block=0xb2594b10) at input/decoder.c:1385 #8 0xb7509e57 in DecoderProcessVideo (b_flush=optimized out, p_block=0xb2594b10, p_dec=optimized out) at input/decoder.c:1631 #9 DecoderProcess (p_block=optimized out, p_dec=optimized out) at input/decoder.c:1810 #10 DecoderThread (p_data=0xb258bd58) at input/decoder.c:909 #11 0xb776fd97 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0xb76c6dfe in clone () from /lib/i386-linux-gnu/libc.so.6 (gdb) display/i $pc 1: x/i $pc = 0xaf19da49 ff_h263_pred_motion+249:cmovg %ecx,%edx However, the browser issue seems to be a different one, although probably similar due to a non-i586 instruction: midori (from Wheezy, with debug symbols): Program received signal SIGILL, Illegal instruction. 0xb4930144 in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 (gdb) bt #0 0xb4930144 in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #1 0xb492d2a9 in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #2 0xb48c9786 in JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, JSC::Register*) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #3 0xb48a78bf in JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const, JSC::JSValue, JSC::ArgList const) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #4 0xb49eb0f4 in JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const, JSC::JSValue, JSC::ArgList const) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #5 0xb4a345e1 in JSC::boundFunctionCall(JSC::ExecState*) () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 #6 0xb492d39a in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0 Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) display/i $pc 1: x/i $pc = 0xb4930144: fucomip %st(1),%st qupzilla (no dbg package available): Program received signal SIGILL, Illegal instruction. 0xb689b51a in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 (gdb) bt #0 0xb689b51a in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #1 0xb680edb5 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #2 0xb69280cf in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #3 0xb69708fb in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb680ee3f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb69280cf in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #6 0xb528edda in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #7 0xb528f3f8 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #8 0xb5911db0 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #9 0xb5a54c07 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #10 0xb5d1a9f2 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #11 0xb3eaeffe in QObject::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #12 0xb42a850a in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #13 0xb42af420 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #14 0xb3e9442a in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #15 0xb3ec91ce in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #16 0xb3ec5e49 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #17 0xb3288da4 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #18 0xb32890c9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #19 0xb3289196
Bug#766114: Aw: Re: [pkg-fso-maint] Bug#766114: Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf
Hmm, it's a strange thing. If I recompile fso-deviced eveything works as expected. But you can reproduce the problem with the packages as they are in Debian right now? I just rebuild the Jessie package (armhf) and still get the same startup error (as I expected). It seems, the generated .c files from vala-sources are broken. Unfortunately this is above my skills. Please let me know if I can be of any further assistance in solving this! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766114: [pkg-fso-maint] Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf
That doesn't help: # apt-get install fso-deviced-n900 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libgcrypt11 libgee2 libgnutls26 libjpeg62 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: fso-deviced Recommended packages: fso-deviced-platform The following NEW packages will be installed: fso-deviced fso-deviced-n900 0 upgraded, 2 newly installed, 0 to remove and 114 not upgraded. Need to get 0 B/146 kB of archives. After this operation, 617 kB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package fso-deviced. (Reading database ... 42289 files and directories currently installed.) Preparing to unpack .../fso-deviced_0.12.0-2_armhf.deb ... Unpacking fso-deviced (0.12.0-2) ... Selecting previously unselected package fso-deviced-n900. Preparing to unpack .../fso-deviced-n900_0.12.0-2_armhf.deb ... Unpacking fso-deviced-n900 (0.12.0-2) ... Processing triggers for man-db (2.7.0.2-2) ... Processing triggers for dbus (1.8.8-2) ... Setting up fso-deviced (0.12.0-2) ... [FAIL] Starting freesmartphone.org device daemon : fso-deviced failed! invoke-rc.d: initscript fso-deviced, action start failed. dpkg: error processing package fso-deviced (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of fso-deviced-n900: fso-deviced-n900 depends on fso-deviced (= 0.12.0-2); however: Package fso-deviced is not configured yet. dpkg: error processing package fso-deviced-n900 (--configure): dependency problems - leaving unconfigured Processing triggers for dbus (1.8.8-2) ... Errors were encountered while processing: fso-deviced fso-deviced-n900 E: Sub-process /usr/bin/dpkg returned an error code (1) (that was on the N900, right after running apt-get update) btw, even if it were the solution this would mean that fso-deviced-platform should be a dependency of fso-deviced and not a recommendation. That in turn would mean that fso-deviced should only be available in armel and armhf because all the packages that provide fso-deviced-platform are only available here. That on the other hand would be unfortunate because phoneui-apps depends on phoneuid depends on phonefsod depends on fso-deviced, which means people like me who want to have a look at the UI first on their x86 machine before deciding whether they want to obtain some HW for actually running phoneui-apps can't get a preview anymore. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608361: snowballz developer homepage down
Package: snowballz Version: 0.9.5.1-2.1 Severity: minor Hi, the snowballz homepage [1] seems to be down. For the package description I'd suggest to link to the projects sourceforge site [2] instead. regards hikaru [1] http://www.joey101.net/ [2] http://sourceforge.net/projects/snowballz/ ___ WEB.DE DSL Doppel-Flat ab 19,99 euro;/mtl.! Jetzt auch mit gratis Notebook-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604056: Acknowledgement (pyracerz dies immediately with a stacktrace on launch)
Hi, I can confirm this bug on Squeeze amd64. Run this in a terminal in bash: for f in /usr/lib/pymodules/python2.6/misc/* ; do if [ -L $f ] ; then dpkg -S `readlink $f` ; fi ; done hik...@squeeze820qm:~$ for f in /usr/lib/pymodules/python2.6/misc/* ; do if [ -L $f ] ; then dpkg -S `readlink $f` ; fi ; done python-coherence: /usr/share/pyshared/misc/media_server_observer.py python-coherence: /usr/share/pyshared/misc/upnp-tester.py Could you also run python again and do this? import sys sys.path hik...@squeeze820qm:~$ python Python 2.6.6 (r266:84292, Oct 9 2010, 12:24:52) [GCC 4.4.5] on linux2 Type help, copyright, credits or license for more information. import sys sys.path ['', '/usr/lib/python2.6', '/usr/lib/python2.6/plat-linux2', '/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old', '/usr/lib/python2.6/lib-dynload', '/usr/local/lib/python2.6/dist-packages', '/usr/lib/python2.6/dist-packages' '/usr/lib/python2.6/dist-packages/gst-0.10', '/usr/lib/pymodules/python2.6', '/usr/lib/pymodules/python2.6/gtk-2.0'] I'm certainly no python expert but it seems to me like the whole misc object in /usr/games/pyracerz isn't initialized when this bug occures. The original error message complains about some zoom attribute. I had a look at the code and found the usage which says something about a resolution parameter. I applied this and got the following: hik...@squeeze820qm:~$ pyracerz --resolution 640x480 /usr/share/games/pyracerz/modules/menu.py:27: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha Traceback (most recent call last): File /usr/games/pyracerz, line 280, in module if __name__ == '__main__': main() File /usr/games/pyracerz, line 106, in main pygame.display.set_caption(pyRacerz v + misc.VERSION) AttributeError: 'module' object has no attribute 'VERSION' So I had a look for misc.VERSION, found it in line 106 which is just some caption, deactivated that line, tried again and got this: hik...@squeeze820qm:~$ pyracerz --resolution 640x480 /usr/share/games/pyracerz/modules/menu.py:27: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha Traceback (most recent call last): File /usr/games/pyracerz, line 280, in module if __name__ == '__main__': main() File /usr/games/pyracerz, line 109, in main if misc.music == 1: AttributeError: 'module' object has no attribute 'music' misc.music can be found in line 109 and I'm pretty sure this game could be played endlessly since these errors are all just consequences of some deeper problem. regards hikaru ___ NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://produkte.web.de/go/webdefreephone -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605405: openbox: some application windows placed incorrectly if top panel present
Hello Dana and Nico, thanks for replying! I have no idea and am using a top placed panel since quite a while without ever noticing such a problem. Ktorrent also does not give me a problem. It opens under Openbox's placement policy, not from a position specified in the app, and so doesn't go under the panel. Does that mean that none of you can reproduce my problem? On Debian I use: hik...@squeeze820qm:~$ ktorrent --version Qt: 4.6.3 KDE Development Platform: 4.4.5 (KDE 4.4.5) KTorrent: 4.0.2 hik...@squeeze820qm:~$ apt-cache showpkg torcs Package: torcs Versions: 1.3.1-5 (/var/lib/apt/lists/ftp2.de.debian.org_debian_dists_squeeze_main_binary-amd64_Packages) (/var/lib/dpkg/status) So it's simply the squeeze packages. In the other distributions it's also just what they have in their repositories. It should be pretty simple to reproduce my problem: 1. Set up a fresh virtual machine with Squeeze. 2. Install LXDE and Ktorrent. 3. Put lxpanel to the top edge of the screen. 4. Start Ktorrent and maximize the window. 5. Reboot the VM and start Ktorrent again. Now you should see what I described in my first e-mail. % ktorrent --version Qt: 4.6.2 KDE Development Platform: 4.4.2 (KDE 4.4.2) KTorrent: 3.3.4 Seems like Ktorrent 3 behaves differently than version 4. Actually I first tended to file this bug report for ktorrent instead of openbox. But finding that kolourpaint works fine, that torcs has the same problem and that the problem doesn't occur with metacity made me think it was an openbox issue. regards hikaru ___ GRATIS! Movie-FLAT mit über 300 Videos. Jetzt freischalten unter http://movieflat.web.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578546: linux-image-2.6.32-bpo.3-amd64: burning DVD+RW very slow with HL-DT-ST DVD+/-RW GSA-U20N
Update: I tried some Ubuntu kernels and while 2.6.27-7-generic and successors have the same problems like the kernels from lenny-backports, 2.6.24-27-generic burns DVD+RW at a reasonable speed. So I guess the critical change happened between 2.6.26 and 2.6.27. ___ NEU: WEB.DE DSL für 19,99 EUR/mtl. und ohne Mindest-Laufzeit! http://produkte.web.de/go/02/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
