I have just recompiled 6.13.11~exp with statically compiled usbhid and
xhci_hcd and after few reboots same errors appeared. Probably it will be
the same with upstream 6.14.1 but i didn't do enough reboots to observe
this. It is weird because on cold boot these errors never occur but
later after
Hi,
full kernel log:
kernel: usbhid 1-13:1.0: can't add hid device: -71
kernel: usbhid 1-13:1.0: probe with driver usbhid failed with error -71
kernel: usbhid 1-13:1.1: can't add hid device: -71
kernel: usbhid 1-13:1.1: probe with driver usbhid failed with error -71
kernel: usbhid 1-13:1.2: can'
Package: linux-image-6.12.21-amd64
Version: 6.12.21
Dear Maintainer,
I have usbhid bugs in journal while bootig concern usbhid driver like:
can't add hid device: -71
probe with driver usbhid failed with error -71
These errors concern usb keyboard which works normally despite these
err
Package: foot
Version: 1.21.0-1
Dear Maintainer,
After updating from: 1.20.2-3 to 1.21.0-1 font rendering is very
different. Fonts looks more bold and not as readable as earlier looks
like more blurrier. Is this a consequence of "bump version constraint
fcft-dev to >= 3.3.1 and set version co
Package: virtualbox
Version: 7.0.18-dfsg-1+b1
Launching virtualbox manager causes host screen to blink black (like
disabling monitor for a sec.). This behavior was observed under
wayland/xwayland with kernel 6.7.12 with UHD Graphics 630 - i915 module.
Package: keepassxc
Version: 2.7.7+dfsg.1-3
Autofocus not working after unlocking database. Issue is resolved in
2.7.8. Update is needed.
Package: linux-image-5.17.0-1-amd64
Version: 5.17.3-1
After upgrading from kernel 5.16 to 5.17 there are *ACPI* errors like this :
kernel: ACPI Error: Aborting method \_PR.PR01._CPC due to previous error
(AE_NOT_FOUND) (20211217/psparse-529)
kernel: ACPI BIOS Error (bug): Could not resolve symb
Package: openrazer-driver-dkms
Version: 3.2.0+dfsg-1
Driver stop working after upgrade from 3.1 to 3.2 with Razer Basilisk v2.
** Error:
kernel: razermouse: system not supported, no HID or USB support
Tested with kernel 5.10 and 5.15.5. Dkms tree ok:
** dkms status:
openrazer-driver/3.2.0, 5.1
Package: linux-image-5.15.0-1-amd64
Version: 5.15.3-1
There are errors increased in smart after every boot in Samsung 970 evo
nvme disk.
*Error Information Log Entries: 41* <- increased after every boot
nvme error-log /dev/nvme0 :
status_field :*0x4004(INVALID_FIELD: A reserved code
Hi,
Can someone explain if this is a bug ? or maybe kernel try to talk to
nvme disk in non supported (by a disk) way ? or maybe there is a need
for some kind of exclude samsung disks from this kind of communication ?
Is anybody even working on this ?
Regards Edi
Package: linux-image-5.14.0-2-amd64
Version: 5.14.9-2
After upgrading from kernel 5.10 to 5.14 there are errors increased in
smart after every boot in Samsung 970 evo.
Error Information Log Entries: 41 <- increased after every boot
nvme error-log /dev/nvme0 :
status_field : 0x4004(I
Hi,
I have exactly the same error with Samsung 970 EVO and smart error
counter is incremented after every boot :
error_count : 38
status_field : 0x4004(INVALID_FIELD: A reserved coded value or an
unsupported value in a defined field)
Best regards
Edi
Why closed if package gnome-shell-extension-autohidetopbar is still in
version 20200921-1 in sid and bullseye so it is not working. When there
will be an updated version?
Also produced error like this:
No signal 'allocation-changed' on object 'StBoxLayout'
Package: gnome-shell-extension-dashtodock
Version: 68-1
Severity: normal
Extension not working after upgrade from gnome 3.36 to 3.38
Error:
No signal 'allocation-changed' on object
'Gjs_dash-to-dock_micxgx_gmail_com_dash_DashToDock_MyDashActor'
-- System Information:
Debian Release: bul
Package: gnome-shell-extension-autohidetopbar
Version: 20200921-1
Severity: normal
Top bar does not autohide on wayland window after upgrading from gnome
3.36 to 3.38
Autohiding is working as expected with X window
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT p
Seems problem is resolved probably after some package upgrades (maybe
gnome-shell 3.36.4)
Regards
EdiD
+0200, EdiD wrote:
Gnome-shell crashes and (systemd) restarts DE. All running applications are
killed. Errors from log:
gnome-shell[1119]: WL: error in client communication (pid 1119)
gnome-shell[1179]: (EE) failed to write to XWayland fd: Broken pipe
I suspect this is happening
Package: gnome-shell
Version: 3.36.3-1
Severity: grave
Justification: causes non-serious data loss
Gnome-shell crashes and (systemd) restarts DE. All running applications are
killed. Errors from log:
gnome-shell[1119]: WL: error in client communication (pid 1119)
gnome-shell[117
The same with mpv 0.32 playing flac stream from online radio
Config:
cache=no
demuxer-max-back-bytes=100KiB
demuxer-max-bytes=2MiB
Ram usage constantly growing (last seen as much as 700MB and cpu usage
is growing with memory). Memory leak ?
Hi,
Same problem here:
gnome-shell[1153]: segfault at 0 ip 7f989dac846a sp
7ffc28aef5a0 error 4 in libst-1.0.so[7f989daa9000+4a000]
Still no gnome-shell 3.36.2 update even in sid
Regards,
Edi D
Hi,
Still not working with systemd 245 and apparmor-utils 2.13.4-1+b1
It will be great to redirect like this:
aa-genprof -f <(journalctl -b)
Is there any chance to work with journald ?
Regards,
Edi D
Package: tilix
Version: 1.9.3-3
Followup-For: Bug #946629
I am wondering why such packages are not tested at all ?
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Kernel
Hi
Sorry for late response. Yes it was fixed after gnome upgrade.
Regards,
Edi D
Package: gnome-shell
Version: 3.34.0-2
Severity: normal
Numlock state is reversed after system boot
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-3
25 matches
Mail list logo
