Bug#928342: libccid: ControlUSB Error

Package: libccid Version: 1.4.26-1 Severity: important I am trying to use pcscd for the smart card reader on a lenovo thinkpad T550. I keep seeing errors in the ControlUSB() function, citing LIBUSB_ERR (-7) in 'service status pcscd'. The reader is identified as Bus 001 Device 003: ID 058f:954

Bug#852398: chromium: Issue not resolved

Package: chromium Version: 56.0.2924.76-4 Followup-For: Bug #852398 Dear Maintainer, Problem is still present in stretch; launching /usr/bin/chromium doesn't bring up previously installed or enabled extensions. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500

Bug#852398: Chromium might as well be broken

I'll chime in and state that this was a terrible idea. I'm not sure what outcome was expected, but breaking normal behavior for no good reason is just insane. I'd go as far as suspecting sabotage! Why else would disabling extensions, without so much as a warning, have been done? Please revert b

Bug#833934: workaround

>From the other merged threads, setting javascript.options.baselinejit = false seems to be a useful workaround until the patch comes out.

Bug#833934: Same problems described by OP

After the update from 45.2.0 to +b1 I am experiencing the same behavior as Christoph. I am also running Baikal server and connecting too it via CalDAV. I can start icedove in safe-mode only. I did a debug with gdb, and I am also getting a segfault in the same area. The information is below.

Bug#831727: g++-5: Compiling with -Og does not generate debugging symbols readable by gdb

Package: g++-5 Version: 5.4.0-6 Severity: normal When I compile a short program with -Og, gdb claims that there is no debugging symbols. Ex: g++ -std=c++11 -o program -Og code.cpp, running gdb ./program produces the line "Reading symbols from ./program...(no debugging symbols found)...done."

Bug#827304: mousepad: Random crashing

Package: mousepad Version: 0.4.0-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, After the last few updates in testing, I've noticed that when editing a file with mousepad, that at seemingly random times, the color scheme will first change from Oblivion (which I'm

Bug#823468: xserver-xorg-input-synaptics: touchpad no longer accepting double-tap as input on Thinkpad T550

Package: xserver-xorg-input-synaptics Version: 1.8.3-1+b1 Severity: important Dear Maintainer, I'm using a Thinkpad T550. Up until a few days ago, everything was working normally with both the touchpad, \ and the trackpoint. Recently, the touchpad has ignored any double touch to act as a mous

Bug#815017: gdb info (thunar: Thunar segfaults when renaming a file)

kyle@minilith:~$ gdb thunar GNU gdb (Debian 7.10-1+b1) 7.10 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitte

Bug#815017: thunar: Thunar segfaults when renaming a file

Package: thunar Version: 1.6.10-2 Severity: normal Renaming a file from within Thunar seems to randomly segfault. I can reproduce this by renaming files until the segfault happens. Usually it takes no more than 5, but I cannot pin down what exactly is causing the problem. I ran Thunar in gdb

Bug#811013: Affects testing

I just updated a system from Jessie to testing, still having this bug. Shows nullptr dereference in dmesg. Have to remove all fglrx packages to boot to desktop. Sent from my HTC

Bug#811290: xfwm4: Visible line on screen that changes with window manager theme

After further research, it appears that the border I'm seeing is actually a "shadow that is under a dock", to a dock that isn't actually there. The shadow can be toggled (made to appear and disappear) under the xfwm4-tweaks-settings -> compositor -> check/uncheck "show shadows under dock windows".

Bug#811290: a screen grab of the border

Here is an image that is probably worth 1000 words. Excuse my lame GIMP abilities. http://ibin.co/2Tn8CFsmDU5O

Bug#811290: xfwm4: Visible line on screen that changes with window manager theme

Package: xfwm4 Version: 4.12.3-1 Severity: important Last night I upgraded my notebook from Jessie to testing, for testing purposes. \ It's hard to describe, but there is a grey border that runs across the screen, and it \ appears to be a window border of some kind. In the xfce settings, under

Bug#809624: Close Bug

I either didn't have enough data entered, or didn't understand what the chart was telling me. However, with 5 or more rides entered, it seems to displaying the correct results. Sorry for the confusion.

Bug#809624: goldencheetah: CP and Power charts under "Trends" is incorrect

Package: goldencheetah Version: 3.1.0-1+b3 Severity: normal I've just recently gotten a power meter, and I've been exploring some of the data analysis tools. I'm trying to understand the Power and CP plots under the "Trends" tab, but the Power plot is a single bar going to 1e-09 with the bin wi

Bug#599690: /usr/bin/nm-applet: Still an issue

Package: network-manager-gnome Version: 0.9.10.0-2 Followup-For: Bug #599690 After startup to ready desktop, the nm-applet appears to be trying to connect to a wireless network. As soon as I try to click on it, it crashes. It then has to be restarted. Afterwards it usually behaves fine, but t

Bug#788578: docky: Graphics corruption after resume from sleep

Package: docky Version: 2.2.0-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? The steps to reproduce are as follows. 1) Put PC into sleep. 2) Resume from sleep. * What was the outcom

Bug#772063: fglrx-driver: fails to build with -fstack-protector-strong error

Package: fglrx-driver Version: 1:14.9+ga14.201-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, * What led up to the situation? Trying to install fglrx-driver (and associated packages) from the non-free repository

Bug#741861: [Pkg-xfce-devel] [Pkg-systemd-maintainers] Bug#741861: libsystemd-login0: Cannot login, must first restart lightdm from tty1

On 03/17/2014 01:49 AM, Yves-Alexis Perez wrote: > Please keep the bug on CC, this is not a private support channel. > > Control: forcemerge 741236 741861 > On Sun, Mar 16, 2014 at 06:08:07PM -0500, Kyle Bentley wrote: >> Thanks for the advice. According to aptitude, libpam-syst

Bug#741698: lighdm shutdown/restart options in XFCE

I had just filed this bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741861 - which I believe now to either be related or a duplicate of this bug. I am using systemd with XFCE from Jessie. I am however using version 1.8.7-1, not the 1.8.8-1 in this report. Kyle B 0x06851F38.asc Desc

Bug#741861: libsystemd-login0: Cannot login, must first restart lightdm from tty1

Package: libsystemd-login0 Version: 204-7 Severity: normal Dear Maintainer, As of 2014/03/15 (+/- 1) I cannot login to Jessie normally. From a cold boot I get to lightdm, however, after entering credentials nothing happens. The screen isn't stuck, I can still move mouse, get to tty prompts, ec