FWIW - I found that editing /etc/initramfs-tools/initramfs.conf and setting
COMPRESS=lzma and COMPRESSLEVEL=9 was enough to get initrd to fit in my /boot.
Using lzma instead of zstd for this particular release changed the size of the
ram disk from 229,092,670 bytes to 86,150,862 bytes. Of course
For the link provided, the crash occurs because of the presence of the unicode
middot character. The wchar_to_utf8() function in libobs utils checks for any
char that is less than 0 and returns zero. This results in dstr_to_lower() not
updating name_lower in xcompcap_props(). The empty name_lowe
Sending in plain text so it is readable:
I'm seeing the same bug in the latest Debian testing updated this
morning. Specifically, if I have the following github page open in my
browser clicking the xcomposite window source cases a seg fault as
reported.
https://github.com/pjreddie/darknet/i
I'm seeing the same bug in the latest Debian testing updated this morning.
Specifically, if I have the following github page open in my browser clicking
the xcomposite window source cases a seg fault as reported.
https://github.com/pjreddie/darknet/issues/553
This results in a window name of "Er
Package: qt6-base-examples
Version: 6.4.2+dfsg-18
Severity: normal
Dear Maintainer,
Qt Creator does not show examples for Qt6. Only for Qt5.
Looking at the corresponding packages reveals that only the Qt5 examples
packages contain actual source code.
Qt5 installs the source:
I was finally able to track this down to a missing xorg.conf file. I copied
the xorg.conf from a external drive with a working debian and now I can login
using xorg again.
On Tuesday, November 20, 2018, 8:51:05 PM PST, Debian Bug Tracking System
wrote:
Thank you for the additional in
I can see from gdb that Vinagre receives a window event via
vinagre_window_state_event_cb that tells it the window is no longer in
fullscreen mode. There was no preceding call to
vinagre_window_toggle_fullscreen and I don’t see any other calls to
gtk_window_fullscreen/unfullscreen.
Setting GTK
Sorry, to much haste I guess. My intent was to file against the nouveau
driver not drm. It can be moved to libgl1-mesa-dri I think.
On Thu, Jul 28, 2016 at 10:36 AM, Julien Cristau
wrote:
> On Wed, Jul 27, 2016 at 10:57:35 -0700, Mike Neilly wrote:
>
> > Package: libdrm-nouveau2
> > Version: 2
I’m attaching an image of the corrupted part of the screen. The black boxes are
added by me but everything behind them was not corrupted.
> On Jul 27, 2016, at 10:57 AM, Mike Neilly wrote:
>
> Package: libdrm-nouveau2
> Version: 2.4.68-1
> Severity: critical
> Tags: upstream
> Justification: b
9 matches
Mail list logo
