Package: src:linux
Version: 6.1.85-1
Severity: important
Dear Maintainer,
After upgrading to linux-image-6.1.0-20-amd64 and rebooting my laptop, my
Bluetooth mouse failed to work after resuming from suspend (via closing and
reopening my laptop). Manually stopping and starting Bluetooth via the
Looks like I should have done a little more sleuthing before sending this bug
report. The problem has been fixed upstream with patch 12.
https://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-012
Package: bash
Version: 5.0-4
Severity: normal
Dear Maintainer,
Apologies in advance. I don't know the proper terminology, so this might be a
known issue. I'll just describe what I expect to happen and what actually
happens on Buster.
Let's say I have a .bash_history file containing the
Package: gnome-control-center
Version: 1:3.30.3-2~deb10u1
Severity: important
Dear Maintainer,
After upgrading from stretch to buster, I was checking out the new Gnome
Settings. I noticed that the `gnome-control-center datetime` panel seemed to
indicate that Automatic Date and Time was not on,
Package: firefox-esr
Version: 60.6.1esr-1~deb9u1
Severity: important
In Preferences/Privacy & Security there are a pair of preferences "Allow
Firefox to send technical and interaction data to Mozilla" and "Allow Firefox
to install and run studies". These are both unchecked and greyed out by
Is it possible to get an upgrade in severity to grave for this bug (or
the linked bug #851928)? The fix for this bug is blocked from entering
testing by another bug that is marked grave:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853170
Both of (#852612 / #851928) and #853170 cause
> I think this should be the same as #851928 addressed by
>
> - http://git.kernel.org/linus/20b1e22d01a4b0b11d3a1066e9feb04be38607ec
> - http://git.kernel.org/linus/0100a3e67a9cef64d72cd3a1da86f3ddbee50363
>
> and already pending for the next upload of src:linux to unstable
> (4.9.6-1).
>
This bug is almost certainly related to this patch, which I believe is
not in the currently packaged kernel:
https://git.kernel.org/cgit/linux/kernel/git/efi/efi.git/commit/?h=next=b2a91a35445229
The machine referenced in that patch is the Lenovo ThinkPad w541,
which is a minor hardware
Package: src:linux
Version: 4.9.2-2
Severity: important
Dear Maintainer,
I upgraded to kernel 4.9 which just migrated into testing. Upon reboot
the system failed to get past "loading initial ramdisk". I added
"debug ignore_loglevel earlyprintk=efi,keep" to the kernel command line
and was able to
It may be too late for this, but here goes:
In the source package's control file, if you replace the Build-Depends
on libssl-dev with:
libssl1.0-dev | libssl-dev (<< 1.1.0~)
the package builds and appears to work normally. This is what OpenSSH
(and maybe others) used to get past this
Debian stretch with chromium 55.0.2883.75-1 (and only chromium) pulled
in from unstable. With a brand new profile (i.e., by deleting
.cache/chromium and .config/chromium and starting Chromium) Chromium
aw-snaps on gfycat.com with very high probability. I occasionally also
see gmail aw-snap, but
I'm a concerned package user looking at this. According to tracker,
yubico-piv-tool is slated for auto-removal because it fails to build
with OpenSSL 1.1. However, the report shows that the version that fails
to build is 1.0.3-1, whereas the current version in Sid and Stretch is
1.4.2-1. What's up
system,
not this package.
On 2016-05-06 21:08, Axel Beckert wrote:
> Control: tag -1 + unreproducible moreinfo
>
> Hi Robert,
>
> Robert Lange wrote:
>> Package: sshuttle
>> Version: 0.78.0-1~bpo8+1
>> Severity: grave
> […]
>> I tried to make a backport of ss
package sshuttle
dpkg-buildpackage: source version 0.78.0-1~bpo8+1
dpkg-buildpackage: source distribution jessie-backports
dpkg-buildpackage: source changed by Robert Lange <rc...@drexel.edu>
dpkg-source --before-build sshuttle-0.78.0
dpkg-buildpackage: host architecture amd64
fakeroot debian
, but given the above, I would say that doing this in the official
backports repo would cause a lot of problems, especially with that special
breed of user who upgrades first and reads the notes later.
--Robert Lange
On 16-04-29, Daniel Pocock <dan...@pocock.pro> wrote:
> Packag
I had upgraded my kernel to 4.2.3-1 and the crackling issue had mostly
gone away (there was a single quiet pop during boot, rather than an
awful crackle). However, after a couple of weeks (and a bunch of
updates) the crackle is back and just as bad as ever.
Lenovo ThinkPad w540
Debian Testing
cheese depends on:
libclutter-gst-2.0-0
gstreamer1.0-clutter
totem (and totem-plugins) depends on:
libclutter-gst-3.0-0
gstreamer1.0-clutter-3.0
Debian allows both of these libraries to be installed at the same time.
However, if libclutter-gst-3.0-0 and gstreamer1.0-clutter-3.0 are
installed,
I am posting another set of journal entries. In this session, I logged
in via GDM3, got the Oh no! message, and was booted back to GDM3. I
logged in again, and was this time granted my desktop.
First, the GDM journal:
-
$ journalctl -b _UID=117
-- Logs begin at Wed 2015-08-05 10:13:49 EDT,
I also see this bug on stretch. It affects my main system, a new
installation on bare metal, and a new installation in a VM, so it's
nothing in my profile, settings, or hardware that is causing it.
I see it every time a user logs in from GDM3 to Gnome3. With a small
probability (maybe 1 in 10) I
Now that a 4.0.x kernel is in testing, I tried this again.
$ uname -a
Linux iset 4.0.0-2-amd64 #1 SMP Debian 4.0.8-1 (2015-07-11) x86_64 GNU/Linux
The bitrate is still incorrect. It appears to be constant at whatever
the first sampled value was since the system last booted. The link
quality and
Package: emacs24
Version: 24.4+1-5
Severity: important
I have a 15 inch 3K laptop monitor. As such, I must use HiDPI settings or my
applications will have unusably small text. Using gnome-tweak-tool I set the
Window HiDPI setting to 2. This causes GTK apps to have scaled fonts and
widgets and
Package: src:linux
Version: 4.0.5-1
Severity: normal
When using the kernel provided by linux-image-4.0.0-2-amd64, the WiFi bit rate
is misreported. The exact (incorrect) bit rate changes on each boot (possibly
on the first WiFi connection), but is constant until the computer is rebooted,
libefivar0 version 0.20-4 fixed the issue. I am now able to modify and
delete boot entries.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
The brightness is saved across reboots when using the kernel provided by
package linux-image-4.0.0-2-amd64, which is currently in unstable.
Unfortunately, due to other regressions, I was forced back to
linux-image-3.16.0-4-amd64, which is currently in testing, and now
brightness is not saved
# strace -o /tmp/efibootmgr.$RANDOM efibootmgr -b 0016 -B
The text file of strace output is attached.
execve(/bin/efibootmgr, [efibootmgr, -b, 0016, -B], [/* 21 vars */])
= 0
brk(0) = 0x215f000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
As of an update that occurred to testing in the last week, I no longer
see this issue. Screen brightness is once again saved across reboots.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: efibootmgr
Version: 0.12-1
Severity: important
Dear Maintainer,
Until about 1 month ago, efibootmgr was able to modify and delete boot menu
items. I do not know exactly when it started failing, but I just noticed it
today.
Running Debian Testing. Tested with kernel 3.16 from testing as
When I set the brightness manually, I run the following and see:
$ ls -1 /sys/class/backlight/*/*brightness | xargs -I % sh -c echo % ;
cat %
/sys/class/backlight/intel_backlight/actual_brightness
2219
/sys/class/backlight/intel_backlight/brightness
2219
Package: xorg
Version: 1:7.7+9
Severity: normal
Dear Maintainer,
I have a Thinkpad w540. I use the Intel graphics and have the Nvidia card off.
I usually leave the screen at 50% brightness to conserve battery, and because
the screen to very bright.
I use testing and run apt-get dist-upgrade
I agree with the original poster and argue for increasing the priority
of this bug, because under certain circumstances it may make a Debian
system appear to be unbootable.
As it stands, if something causes the computer's EFI NVRAM to get wiped
(e.g., user error, firmware bug, firmware
Package: bumblebee
Version: 3.2.1-5
Severity: important
Dear Maintainer,
I am running testing and Bumblebee was working properly to enable and disable
my Nvidia graphics chip when I was running kernel 3.14-X-amd64. Last night I
dist-upgraded and got kernel 3.16. This morning I noticed my laptop
I found a reference to the same issue from an Arch user:
https://github.com/Bumblebee-Project/Bumblebee/issues/592
The workaround given was to append acpi_osi=\!Windows 2013\ to the
GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub and run
update-grub.
After doing this, bumblebee is
Package: libchart-gnuplot-perl
Version: 0.20-2
Severity: minor
Dear Maintainer,
the following entry in the Chart::Gnuplot documentation is not correct,
Using the given statements results in an error (; expected):
6. Title in non-English characters (Thanks to WOLfgang Schricker)
I would like to, but according to the ChangeLog upstream has dropped
support for several old chips, e.g. GeForce 6150
So I will need to live with sporadic crashing until legacy-304xx becomes
available?
But if you have such an ancient card, have you tried the 173xx legacy
driver - they were
On second throught, lately I got the crash only when I blanked my
screen with the following command:
xlock -nolock -mode blank
Unfortunately that turned out to be not correct. Machine is also
freezing during normal operation from time to time.
From time to time (once a week maybe) the system
On second throught, lately I got the crash only when I blanked my screen
with the following command:
xlock -nolock -mode blank
Previously it also froze during operation, but it seems this issue has
been solved since my last update.
I will watch it further and submit an update in case it will
Is your bug still around in actual versions of debian and icedove? If
not this bug can be closed.
It seems to be solved in current version of icedove - so please close it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Michael,
thanks for your feedback.
Make keys known to kernel by adding to file /etc/rc.local :
# Get Brightness control keys working; map to XF86 Brightness keys
# up
setkeycodes 65 225
# down
setkeycodes 67 224
Doesn't remapping the key suffice to get it working via the standard way
Are there any plans to release an new debian package for python-twitter
with OAuth support?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: cryptsetup
Subject: cryptsetup: Would like to use decrypt_derived with a source
mapping other than that of the root filesystem
Package: cryptsetup
Version: 2:1.1.3-3
Severity: normal
I am encountering the same problem as already reported (and stated to be
closed 15 Oct 2009) in Bug
I now encountered the same problem with a standard desktop computer.
When /etc/initramfs-tools/conf.d/driver-policy is set to
MODULES=dep
then USB Keyboard drivers are NOT included in the Initramfs. As nowadays
most computers have USB keyboards I think this is quite inconvenient.
I would expect
Hi,
I applied the previously mentioned patches locally to anki 0.9.9.8.6-2
last week and anki became again usable:
http://github.com/dae/libanki/commit/a1d3f13f0a694e079be196bb2eb4ee6b67799f45
http://github.com/dae/libanki/commit/f69d946f8355af9ca19c5e90e1056c01a3722bf5
Found no other side
Damien Elmes wrote:
You installed a broken plugin. As the top of the error message says,
file a report with the plugin author.
Ah, Thanks for your your resolve. You are right.
It was the Plugin Left Hand Reps.
After removing the plugin the error was gone.
Can you please mark this bug as
Hi Yves-Alexis,
I think messing with xmodmap is not a good idea when using libxklavier
(which xfce uses).
Basically, you're messing with the keymap behind Xorg's back, which
triggers a refresh loop in xfce settings
I don't exactly know what you're trying to do, but there may be a really
Package: libc6-dev
Version: 2.3.6-3
Severity: normal
When compiling a program including argp.h with -Ox and -pedantic
option an error is issued.
gcc-4.0 -O -pedantic argp.cpp
/usr/include/argp.h: In function 'void argp_usage(const argp_state*)':
/usr/include/argp.h:564: error: declaration of
Alexander Sack wrote:
Sorry for the delay ... I somehow dropped the ball on this :). To answer your
The same for me. And also Sorry for the short reply - Thunderbird ate my
message. I will check this afterwards if it is reproducible.
question, you can try to install and set the japanese locale
Package: mozilla-thunderbird
Version: 1.0.2-3
mozilla-thunderbird-offline: 1.0.2-3
While working offline, when I save a message as draft and then move it
to an IMAP folder, it vanishs when I switch to online mode
Actions:
- go offline: File/Offline/Work Offline
- start composing a message for
So it's not a pure problem with Thunderbird/Modzilla, but rather some
interference with my system.
Because I cannot reply to your message, not even without adding any
characters.
But I have no idea what could cause the problem, can you help me in
locating the source?
So maybe you actually used a
Package: mozilla-thunderbird
Version: 1.0-3
Error Description
-
I am unable to send mails in ISO-2022-JP or Shift_JIS character encoding.
When trying to send a mail in this encodings I get the warning message
The message you composed contains characters not found in the selected
49 matches
Mail list logo
