Bug#727047: gnome-session-flashback: Alt+Tab doesn't work anymore after upgrade
Olivier BERGER wrote: > > This can also be set in gnome-control-center, in Navigation, by > setting Alt+TAB for "Switch Applications". To clarify, in case others are confused like I was: first you choose "Keyboard" in gnome-control-center, and then look under "Shortcuts". That's where you'll find Navigation. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717813: Filed this bug upstream
Filed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=67353 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717813: xserver-xorg-video-openchrome: Flipped colors (blue/red) in some videos
On Thu, Jul 25, 2013 at 01:41:41PM +0200, Julien Viard de Galbert wrote: > > As you tested upstream version, can you please report the problem > upstream too. > > Currently my VIA PC is not working, but as soon as I can find time > for it, I'll probably try updating the package. > And when updating I'll take things directly from upstream. Sure, I'll report it to upstream too. However, I didn't actually "test" the upstream version because I couldn't get the upstream version to work at all. Inspired by http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706066 I built a debian package for it but that hung the machine --- no response to alt-sysrq-b. (It's probably an EXA problem but that's another issue...) Selim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696240: The ppd from Luca worked for me
Hi, I have an ML-2165 and I tried the ppd file that Luca attached to his message on the bug report page. I added the printer using the web interface for CUPS and only changed the default setting from Letter to A4. It seems to work okay. The only thing I noticed was this: I first chose the "Print Test Page" option on the CUPS webpage and the resulting printout was missing the right side of thin border line around the page. It looks like that edge got cut off. But all the "non-test" pages I printed afterwards seem okay. Thanks for the ppd! Selim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689872: libkmod2: module parameters on kernel command line parsed wrong
On Mon, Oct 08, 2012 at 06:56:05PM -0300, Lucas De Marchi wrote:
> On Mon, Oct 8, 2012 at 6:52 PM, Lucas De Marchi
> wrote:
> > On Sun, Oct 7, 2012 at 2:35 PM, Marco d'Itri wrote:
> >> Any objections?
> >>
> >> ----- Forwarded message from "Selim T. Erdogan"
> >> -
> >>
> >> From: "Selim T. Erdogan"
> >> To: Debian Bug Tracking System
> >> Subject: Bug#689872: libkmod2: module parameters on kernel command line
> >> parsed
> >> wrong
> >>
> >> Package: libkmod2
> >> Version: 9-2
> >> Severity: important
> >> Tags: d-i patch
> >>
> >> This problem only affects module parameters given on the kernel command
> >> line at boot time which include a '.' as part of their value. For
> >> example "libata.force=1.5Gbps". The bug causes such values to
> >> overwrite the parameter, so this would get interpreted as parameter
> >> "5Gbps" with no value. ("force" gets lost.)
> >>
> >> To reproduce this safely, add "testmodule.testparam=1.5G" to the end of
> >> the kernel command line at boot time. Then:
> >>
> >> $ /sbin/modprobe -c |grep 5G
> >> options testmodule 5G
> >>
> >> This problem prevented me from using the wheezy beta 2 debian-installer
> >> on a machine that needed libata.force=1.5Gbps to work properly with my
> >> new SSD. See https://lists.debian.org/debian-boot/2012/10/msg00049.html
> >>
> >> I'm including a very simple at the end of the report that fixes the
> >> problem. Feel free to modify/edit as necessary. With this patch:
> >>
> >> $ /sbin/modprobe -c |grep 5G
> >> options testmodule testparam=1.5G
> >>
> >>
> >> -- System Information:
> >> Debian Release: wheezy/sid
> >> APT prefers unstable
> >> APT policy: (500, 'unstable'), (1, 'experimental')
> >> Architecture: i386 (i686)
> >>
> >> Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
> >> Locale: LANG=tr_TR.UTF-8, LC_CTYPE=tr_TR.UTF-8 (charmap=UTF-8)
> >> Shell: /bin/sh linked to /bin/dash
> >>
> >> Versions of packages libkmod2 depends on:
> >> ii libc6 2.13-35
> >> ii multiarch-support 2.13-35
> >>
> >> libkmod2 recommends no packages.
> >>
> >> libkmod2 suggests no packages.
> >>
> >> -- no debconf information
> >>
> >> *** kcmdline-option-parsing
> >> Description: Fixes parsing of module parameters on the kernel command
> >> line. Before this patch, if the parameter value had a '.' in it, that
> >> would break things.
> >> Author: Selim T. Erdoğan
> >>
> >> --- kmod-9.orig/libkmod/libkmod-config.c
> >> +++ kmod-9/libkmod/libkmod-config.c
> >> @@ -542,6 +542,7 @@ static int kmod_config_parse_kcmdline(st
> >> char buf[KCMD_LINE_SIZE];
> >> int fd, err;
> >> char *p, *modname, *param = NULL, *value = NULL;
> >> + int in_value_text = 0;
> >>
> >> fd = open("/proc/cmdline", O_RDONLY|O_CLOEXEC);
> >> if (fd < 0) {
> >> @@ -564,15 +565,20 @@ static int kmod_config_parse_kcmdline(st
> >> *p = '\0';
> >> kcmdline_parse_result(config, modname, param,
> >> value);
> >> param = value = NULL;
> >> + in_value_text = 0;
> >> modname = p + 1;
> >> break;
> >> case '.':
> >> - *p = '\0';
> >> - param = p + 1;
> >> - break;
> >> + if (in_value_text == 0) {
> >> + *p = '\0';
> >> + param = p + 1;
> >> + break;
> >> + }
> >
> > this fall-through here doesn't seem intentional
You're correct.
> >
> >
> >> case '=':
> >> - if (param != NULL)
> >> + if (param != NULL) {
> >> value = p + 1;
> >> + in_value_text=1;
> >> +
Bug#689872: libkmod2: module parameters on kernel command line parsed wrong
Package: libkmod2
Version: 9-2
Severity: important
Tags: d-i patch
This problem only affects module parameters given on the kernel command
line at boot time which include a '.' as part of their value. For
example "libata.force=1.5Gbps". The bug causes such values to
overwrite the parameter, so this would get interpreted as parameter
"5Gbps" with no value. ("force" gets lost.)
To reproduce this safely, add "testmodule.testparam=1.5G" to the end of
the kernel command line at boot time. Then:
$ /sbin/modprobe -c |grep 5G
options testmodule 5G
This problem prevented me from using the wheezy beta 2 debian-installer
on a machine that needed libata.force=1.5Gbps to work properly with my
new SSD. See https://lists.debian.org/debian-boot/2012/10/msg00049.html
I'm including a very simple at the end of the report that fixes the
problem. Feel free to modify/edit as necessary. With this patch:
$ /sbin/modprobe -c |grep 5G
options testmodule testparam=1.5G
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=tr_TR.UTF-8, LC_CTYPE=tr_TR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libkmod2 depends on:
ii libc6 2.13-35
ii multiarch-support 2.13-35
libkmod2 recommends no packages.
libkmod2 suggests no packages.
-- no debconf information
*** kcmdline-option-parsing
Description: Fixes parsing of module parameters on the kernel command
line. Before this patch, if the parameter value had a '.' in it, that
would break things.
Author: Selim T. Erdoğan
--- kmod-9.orig/libkmod/libkmod-config.c
+++ kmod-9/libkmod/libkmod-config.c
@@ -542,6 +542,7 @@ static int kmod_config_parse_kcmdline(st
char buf[KCMD_LINE_SIZE];
int fd, err;
char *p, *modname, *param = NULL, *value = NULL;
+ int in_value_text = 0;
fd = open("/proc/cmdline", O_RDONLY|O_CLOEXEC);
if (fd < 0) {
@@ -564,15 +565,20 @@ static int kmod_config_parse_kcmdline(st
*p = '\0';
kcmdline_parse_result(config, modname, param, value);
param = value = NULL;
+ in_value_text = 0;
modname = p + 1;
break;
case '.':
- *p = '\0';
- param = p + 1;
- break;
+ if (in_value_text == 0) {
+ *p = '\0';
+ param = p + 1;
+ break;
+ }
case '=':
- if (param != NULL)
+ if (param != NULL) {
value = p + 1;
+ in_value_text=1;
+ }
break;
}
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680277: evince: segfault when printing certain pages (but okay when printing to ps file)
On Wed, Jul 04, 2012 at 09:52:06PM +0200, Michael Biebl wrote:
> On 04.07.2012 20:39, Selim T. Erdogan wrote:
> > Package: evince
> > Version: 3.4.0-2+b1
> > Severity: normal
> >
> > Evince segfaults when I try to print page 1 of file f1040sd.pdf (attached).
> > Page 2 prints okay. This also happens on some other files/pages, which
> > I can provide if needed.
> >
> > If I choose print to file and select pdf, it still segfaults. However,
> > if I select ps, it prints fine. Then I can open the ps file in evince
> > and send to the printer without any problem.
> >
>
> Might be another of those cairo 1.12 regressions.
> I myself noticed several issues with printing PDF files with evince and
> cairo 1.12.
> See
> https://bugs.freedesktop.org/show_bug.cgi?id=51443
> and specifically
> https://bugs.freedesktop.org/show_bug.cgi?id=51443#c24
>
> Would be nice if you install the evince-dbg and libcairo2-dbg debug
> package and get us a back trace.
> The steps are basically:
> - Install gdb
> - Run "gdb /usr/bin/evince"
> - type "set logging on"
> - type "run path/to/pdf"
> - print the document → leads to the crash
> - run "bt full" in gdb
>
> Attach gdb.txt to the bug report.
Yes, looks very similar to the backtrace in the bug report link you gave.
My gdb.txt is attached.
Selim
Starting program: /usr/bin/evince f1040sd.pdf
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[New Thread 0xb68ecb70 (LWP 24625)]
[New Thread 0xb60ebb70 (LWP 24626)]
[New Thread 0xb58eab70 (LWP 24627)]
[Thread 0xb58eab70 (LWP 24627) exited]
[New Thread 0xb58eab70 (LWP 24633)]
[New Thread 0xaf98bb70 (LWP 24634)]
[Thread 0xb60ebb70 (LWP 24626) exited]
[New Thread 0xb60ebb70 (LWP 24638)]
Program received signal SIGSEGV, Segmentation fault.
decode_integer (p=0x0, integer=integer@entry=0xbfffee00)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-cff-subset.c:241
241
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-cff-subset.c:
Böyle bir dosya ya da dizin yok.
#0 decode_integer (p=0x0, integer=integer@entry=0xbfffee00)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-cff-subset.c:241
No locals.
#1 0xb7757e60 in cairo_cff_font_read_top_dict (font=0x863c170)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-cff-subset.c:1185
index = {size = 1, num_elements = 1, element_size = 12,
elements = 0x861f8a8 ""}
element =
buf = "Q^U\b\364\357%\267\300\003&\267\000\000\000\000\364\357}\267"
operand =
status = CAIRO_INT_STATUS_SUCCESS
p = 0x8555fed "\213\213\371\211\213\006\373w\213\a\273\n\273\v"
size =
offset = 335
#2 0xb77595fb in cairo_cff_font_read_font (font=0x863c170)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-cff-subset.c:1321
i =
status =
#3 cairo_cff_font_generate (length=,
data=, font=0x863c170)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-cff-subset.c:2545
status =
#4 _cairo_cff_subset_init (cff_subset=cff_subset@entry=0xb040,
subset_name=subset_name@entry=0xb08c "CairoFont-4-0",
font_subset=font_subset@entry=0xb140)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-cff-subset.c:2928
font =
status =
data = 0x0
length = 0
i =
#5 0xb779cd6b in _cairo_pdf_surface_emit_cff_font_subset (
font_subset=0xb140, surface=0x86ea370)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-pdf-surface.c:4884
status =
subset = {family_name_utf8 = 0x0,
ps_name = 0x8359b50 "@;n\b\360\215b\blStd-NewswithCom ",
widths = 0x85dc208, x_min = -0.0070001,
y_min = -0.22701, x_max = 0.98899,
y_max = 0.76401, ascent = 0.76401,
descent = -0.22701,
data = 0x86d8000 "\370\317\\\b\240\250l\b", data_length = 568}
name =
"CairoFont-4-0\000#\267?\264u\267\370\063k\b\b\004\000\000\001\000\000\000\n\020p\267\364\357}\267\002\000\000\000\070\320_\b\275\027p\267\270\254c\b`\315z\267\350\360\377\277"
#6 _cairo_pdf_surface_emit_unscaled_font_subset (font_subset=0xb140,
closure=0x86ea370)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-pdf-surface.c:5596
surface = 0x86ea370
status = CAIRO_INT_STATUS_SUCCESS
#7 0xb775ad9a in _cairo_sub_font_collect (closure=0xb114, entry=0x85f6200)
at
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-sca
Bug#650012: ndiswrapper-source: Doesn't build. Complains: ‘struct net_device’ has no member named ‘priv’
Package: ndiswrapper-source Version: 1.56+r2729-1 Severity: important Trying to build it with "m-a build ndiswrapper" gave a whole raft of errors, starting with: - /usr/src/modules/ndiswrapper/iw_ndis.c: In function ‘iw_set_essid’: /usr/src/modules/ndiswrapper/iw_ndis.c:76:28: error: ‘struct net_device’ has no member named ‘priv’ (many more of the same sort) - Googling a bit, it seems this is due to a #define introduced a long time ago to be compatible with older kernels, which kept working until the the latest kernel finally broke it. It also looks like this issue has been fixed in the upstream ndiswrapper. The easy fix I applied was to comment out lines 278-280 in /usr/src/modules/ndiswrapper/ntoskernel.h while I was building it. (As suggested by http://aptosid.com/index.php?name=PNphpBB2&file=printview&t=1868&start=0) It might be a good time to package a newer upstream version... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=tr_TR.UTF-8, LC_CTYPE=tr_TR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ndiswrapper-source depends on: ii bzip2 1.0.5-7 ii debhelper 8.9.11 ii module-assistant 0.11.4 ndiswrapper-source recommends no packages. Versions of packages ndiswrapper-source suggests: pn kernel-package -- 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#610371: another work-around
I have the same issue, though my gnome-power-manager version is different (3.0.2-3). The work-around mentioned above doesn't work as is, because on my system (sid with gnome 3) there is no such field under "actions" in gconf-editor. Instead, I installed the "dconf-tools" package and ran dconf-editor. Here I went under "org->gnome->settings-daemon->plugins->power" and changed "lid-close-battery-action" from suspend to nothing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#614022: xserver-xorg-video-openchrome: gdm fails to start X
Package: xserver-xorg-video-openchrome
Version: 1:0.2.904+svn891-1
Severity: grave
Tags: upstream patch
Justification: renders package unusable
(Reportbug didn't tell me where exactly I should type my explanation/report.
I hope right here -- after the headers -- is correct.)
I did an update to sid today and after rebooting, my gdm/X didn't come up.
Just a black/black screen was shown. No fallback to VESA either.
(However, I realized later that if I uninstall the openchrome driver package,
then VESA works.)
At X failure, when I pressed tab at the black/blank screen, I was told that
X failed and given the choice to see the gdm log file, followed by the X log
file. The gdm log file, included below, showed a symbol lookup error, so I
got the source package and poked around. The patch below seems to solve
the problem. (Apologies if the format isn't great. I haven't made a patch
file before.) (I also am not sure if I should be attaching the patch instead
of including it inline. Is there a preference?)
As far as I could tell by browsing the upstream source repository, the same
bug is there too.
Diff of original and changed versions of file (via_panel.c):
-
---
openchrome-original/xserver-xorg-video-openchrome-0.2.904+svn891/src/via_panel.c
2010-12-21 17:12:42.0 +0200
+++
openchrome-changed/xserver-xorg-video-openchrome-0.2.904+svn891/src/via_panel.c
2011-02-19 01:46:25.0 +0200
@@ -307,7 +307,7 @@
int width, height;
Bool ret;
-ret = ViaPanelGetSizeFromDDC(pScrn, &width, &height);
+ret = ViaPanelGetSizeFromDDCv1(pScrn, &width, &height);
/*
if (!ret)
ret = ViaPanelGetSizeFromDDCv2(pScrn, &width);
@@ -411,7 +411,7 @@
}
Bool
-ViaPanelGetSizeFromDDC(ScrnInfoPtr pScrn, int *width, int *height)
+ViaPanelGetSizeFromDDCv1(ScrnInfoPtr pScrn, int *width, int *height)
{
VIAPtr pVia = VIAPTR(pScrn);
xf86MonPtr pMon;
Contents of gdm log file (/var/log/gdm/:0.log):
-
X.Org X Server 1.9.4
Release Date: 2011-02-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32.28-dsa-ia32 i686 Debian
Current Operating System: Linux bodrum 2.6.37-1-686 #1 SMP Tue Feb 15 18:21:50
UTC 2011 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-1-686
root=UUID=fd16510f-8930-4b27-808e-b9174369c2d4 ro quiet
Build Date: 17 February 2011 01:25:01AM
xorg-server 2:1.9.4-2 (Cyril Brulebois )
Current version of pixman: 0.21.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 19 02:06:57 2011
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) Failed to load module "fbdev" (module does not exist, 0)
/usr/bin/X: symbol lookup error:
/usr/lib/xorg/modules/drivers/openchrome_drv.so: undefined symbol:
ViaPanelGetSizeFromDDCv1
-- Package-specific info:
X server symlink status:
lrwxrwxrwx 1 root root 13 Aug 12 2009 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1771432 Feb 17 03:30 /usr/bin/Xorg
VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc.
KM400/KN400/P4M800 [S3 UniChrome] [1106:7205] (rev 01)
/etc/X11/xorg.conf does not exist.
/etc/X11/xorg.conf.d does not exist.
KMS configuration files:
/etc/modprobe.d/i915-kms.conf:
options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
options radeon modeset=1
Kernel version (/proc/version):
---
Linux version 2.6.37-1-686 (Debian 2.6.37-1) (b...@decadent.org.uk) (gcc
version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Tue Feb 15 18:21:50 UTC 2011
Xorg X server log files on system:
--
-rw-r--r-- 1 root root 12514 Feb 19 02:06 /var/log/Xorg.0.log
Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 5578.103]
X.Org X Server 1.9.4
Release Date: 2011-02-04
[ 5578.104] X Protocol Version 11, Revision 0
[ 5578.104] Build Operating System: Linux 2.6.32.28-dsa-ia32 i686 Debian
[ 5578.104] Current Operating System: Linux bodrum 2.6.37-1-686 #1 SMP Tue Feb
15 18:21:50 UTC 2011 i686
[ 5578.104] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-1-686
root=UUID=fd16510f-8930-4b27-808e-b9174369c2d4 ro quiet
[ 5578.105] Build Date: 17 February 2011 01:25:01AM
[ 5578.105] xorg-server 2:1.9.4-2 (Cyril Brulebois )
[ 5578.105] Current version of pixman: 0.21.4
[ 5578.105]Before reporting problems, check http://wiki.x.org
Bug#418813: locales still won't install. Dependency problem on i386
The last message I saw on the bug page mentioned that the glibc-2.5-1 virtual package is provided by libc6 2.5-2. But I've just done a system update (on unstable) and the available version of libc6 is 2.5-1. Furthermore, according to http://packages.debian.org/unstable/libs/libc6, 2.5-2 is the version on amd64 -- for i386, the version is 2.5-1. For this latter version the control info has "Provides: glibc-2.5.0-0exp1, glibc-2.5.0-0exp2" Could it be that the glibc-2.5-1 virtual package is only provided by the version of libc6 for amd64, but not by i386? Selim T. Erdoğan
