Bug#851767: chromium: Line 21 in the startup script /usr/bin/chromium is missing a terminating quote.

2017-01-18 Thread Grigor Gatchev
Package: chromium Version: 55.0.2883.75-4 Severity: grave Justification: renders package unusable Dear Maintainer, I upgraded package chromium to 55.0.2883-75.4. After that, the Chromium browser would not run. I browsed the starting script /usr/bin/chromium and noticed that the string in line

Bug#656015: base: Monitor EDID not recognized by Linux kernel 3.x on AMD A6 CPU

2012-01-27 Thread Grigor Gatchev
Package: base Followup-For: Bug #656015 The bug is present also in kernel 3.2.0-1, package version 3.2.1-2. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#656015: base: Monitor EDID not recognized by Linux kernel 3.x on AMD A6 CPU

2012-01-15 Thread Grigor Gatchev
Package: base Severity: important -- System Information: CPU: AMD A6 MB: AsRock A55 Pro3 Debian release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) -- Bug Description: After upgrading kernel from 2.6.39 to 3.0.0, monitor

Bug#490218: network-manager-kde: does not see wireless device

2008-07-10 Thread Grigor Gatchev
Package: network-manager-kde Version: 1:0.2.2-1 Severity: normal (I'm not sure whether this bug is in network-manager-kde: could be in wpasupplicant, or elsewhere.) When started, KNetworkManager finds the wired device, but not the wireless device. (KWifiManager and command line find it and

Bug#490218: Bug solved :-(

2008-07-10 Thread Grigor Gatchev
Found the problem. For unknown reason, the wpa_supplicant executable was only several K long. Reinstalled the package, and things went smoothly. (Sorry for the trouble. I lost two days on experimenting before sending the report, but only after that got the idea to inspect the executables.)