I have the same issue. Also caused by upgrade. Causes almost any
program that attempts to play sound to freeze. I twigged that it was
pulseaudio when a non-pulseaudio using video player was the only
sound-playing thing on my system that DIDN'T freeze.
And I found a workaround.
When you
package: gucharmap
version:1:14.0.3
While preparing this bug report for the white-on-white characters, I
checked the versions of everything gucharmap depends on and I think I
found a packaging error. Gucharmap wants libc6 version 2.4, but
installed without complaint even though I have libc6 versi
package: gimp
Version: 2.10.30-1+b1
Severity: Normal
The 'rotate' tool in GIMP is now ignoring selection area and layer
restrictions, making it impossible to rotate any part of the image
relative to other parts.
Note, there is a workaround. Cut to the last paragraph if that's all
you're interest
On Sun, 28 Nov 2021 09:48:22 +0100 Niels Thykier wrote:
> This is a consequence of the currently incomplete "/usr-merge"
> transition, where /bin has been merged into /usr/bin without dpkg's back.
>
> As such, dpkg knows those paths only by their "officially declared"
> paths in /bin. It is obvio
Package: dpkg
Version: 1.20.9
Distribution: Bookworm
Architecture: AMD64
Relevant because this could have something to do with which utilities
are statically linked to bash or exactly which coreutils we're talking
about:
bash is version 5.1-3.1 and coreutils is version 8.32-4.1
At the command l
On 5/26/21 8:01 PM, Bernhard Übelacker wrote:
> Testing in a VM with a more reasonable 6GB apparently does not provoke
>> the crash.
>
> I fear the issue might also be specific to the graphics library
> because the crash happens in nouveau_dri.so.
> Therefore a VM might not show this issue.
>
I d
On Wed, 14 Apr 2021 14:04:33 + Ray Dillinger wrote:
>
> Warning, a coredump from this system would be immense. Or, well anyway
> pretty darn large. The machine has over 64G of RAM memory installed and
> openuniverse seems to expand to fill available space. I could make
On Wed, 14 Apr 2021 11:59:43 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
> Hello Ray,
> from the "Code:" line you supplied I think the segfault happens
> in create_cache_trans at ../src/mesa/state_tracker/st_cb_bitmap.c:402.
>
>
https://sources.debian.org/src/mesa/20.3.5-1/src/mesa/state_trac
Package: openuniverse
version: 1.0beta3.1+dfsg-6.1
When I started openuniverse, it put up a window with no menu items and
no other control elements. It responded to '?' or 'H' keystrokes by
putting up a short list of keystroke shortcuts - presumably
corresponding to nonexistent menu options. Th
As expected the problem is something about the interaction with the
debian nvidia software, gdm, and my laptop. I have found a workaround.
I did
# apt-get remove *nvidia*
And the configuration went back to the nouveau drivers, and the problem
went away.
The laptop isn't a gaming machine so I
X-Debbugs-Cc: b...@sonic.net
Package: gnome
Version: 1:3.20+2
Followup-For: Bug #730224
I installed "Stretch" on my laptop using ISO install snapshot CDs
(specifically the image downloaded 6 January 2017).
The laptop was working fine with "Jessie" before the (re)install.
I did a clean insta
There is no reason to have multiple sources in your
/etc/apt/sources.list file, if apt-get update/upgrade only cares about
the first one!
I use multiple sources in the hopes that
(a) The load should be distributed among those mirrors.
(b) Multiple downloads should be happening at once. At leas
Hmm.
On further inspection, it appears that you're right.
So I suppose my "bug" is that debian appears not to give
a crap about people monitoring who is downloading which
packages and isn't providing their repositories via
https. Or ftps. Or, really, via *any* confidential
mechanism.
Signatur
I'm getting a message that the certificate for
"debian.org" is not applicable to "security.debian.org"
and therefore none of these packages can be verified.
On the one hand, of course that's just a configuration
error where the certificate should be for *.debian.org
instead of for debian.org.
On
Package: gdm3
Version: 3.18.0-2
Followup-For: Bug #794316
Dear Maintainer,
I had an issue where login didn't work. The login screen would appear,
I'd enter username and password, and then I'd wind up back at the login
screen. It may be this bug or one closely related.
For a while I thought I
I had the proprietary nvidia drivers installed in my Jessie machine
when I decided to move to Stretch.
During the upgrade process, there was a message that the open-source
driver was compatible with my hardware now, and did I want to switch
to the nouveau system. I always prefer open-source when
Package: keyboard-configuration
Version: 1.88
Severity: wishlist
* What led up to the situation?
I purchased a Corsair Vengeance K90 Keyboard, expecting to be able to
configure a keyboard model/layout for it. So far I have been
frustrated.
* What exactly did you do (or not do) that was e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/12/2012 10:13 AM, Matthias Klose wrote:
> On 11.07.2012 19:21, Ray Dillinger wrote:
>> This is the standard library. It's totally fundamental. We
>> can't allow Debian systems for programmers to NOT have man pages
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This bug also affects subsequent versions of this package,
libstdc++6-4.6-doc and libstdc++6-4.7-doc
Today I typed "man std::mutex" and my system told me there was no man
page for something that I know is part of the c++ standard library. So
I went
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, some further information. After I start gnome-terminal from a
command line with 'gnome-terminal -x /bin/sh' I can issue a 'w' command
(in another terminal) and see that an instance of 'sh' for my account
has been started. This has to be the sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
During a recent upgrade, a checkbox marked "use colors from system
theme" got checked. I was using a black-on-yellow color scheme.
The "colors from the system theme" apparently caused gnome-terminal
to switch to a black background, but did not change
t seeing this bug; if
they were, there would be a furor over it by now because the
package in the presence of this bug is completely unusable
('grave'). I am experiencing it as a 'grave' bug, but since
it apparently affects relatively few users,maybe it should be
'normal&#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, that was a spectacularly unhelpful answer. I'll try to do
better.
The reason all these things went away is because they are, by
default, disabled in the version of Gnome you've just upgraded to.
The "bug" can't be fixed, because evidently it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just by the way, this bug is annoying as hell. xscreensaver allowed
setting individual options for different screensavers. Replacing it
with gnome-screensaver when gnome-screensaver does not, AND
gnome-screensaver still had bugs in power management on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/18/2011 02:31 AM, Kalle Olavi Niemitalo wrote:
> Ray Dillinger writes:
>
>> display.c starts with the lines:
>>
>>
>> #define _X_OPEN_SOURCE_EXTENDED
>
> There is an extra underscore after the X.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> bear@janus:~/src/xxh$ make display.o
>> gcc -D_XOPEN_SOURCE_EXTENDED -Wall -Werror -lncursesw -c -o display.o \
>> display.c
>> bear@janus:~/src/xxh$
>
> should't the ncursesw headers be used?
Sorry, don't understand your message. The ncursesw head
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2011 05:10 PM, Thomas Dickey wrote:
> You're seeing implicit for get_wch, since there's no _XOPEN_SOURCE_EXTENDED
> in the compile line.
Okay, after checking:
bear@janus:~/src/xxh$ make display.o
gcc -D_XOPEN_SOURCE_EXTENDED -Wall -Werror
On 07/17/2011 05:10 PM, Thomas Dickey wrote:
> fwiw, I routinely build with warnings enabled (and don't have a use for
> -Werror).
>
> For the rest - I'm typically seeing only extra warnings that
> you wouldn't see with -Wall (such as const mismatches, which are
> problematic).
>
> That's for ncu
Package: gcc
Version: 4:4.4.5-1
Severity: normal
Tags: l10n
In reply to your
Fwd: Message with no Package: tag cannot be processed!(...)
(reportbug fails on my system due to sendmail not being installed.
Like most sane people I use Qmail. should I file a bug against
reportbug?)
original me
C4 or DES by default, and should
print a warning to stderr when weak ciphers are enabled explicitly.
Do we have any idea how much trouble it would cause for these
deprecated insecure ciphers to be completely disabled?
Ray Dillinger
--
To UNSUBSCRIBE,
A clarification: This laptop has no numlock key as such - not even
in its overlay keyset. The only way to toggle the numlock is to plug
in an external (USB) keyboard and press the key on that - or to have
the numlock setting inherited from my standard X settings, which is
what was happening h
Yes, in fact it turns out to be that simple. X regards the num-lock
behavior as implying the 'function key' behavior, even for keys that
don't have anything to do with the numeric keypad overlay.
So the workaround is, turn the numlock off.
And the 'fix' that demotes this from regular to nea
On Thu, 2008-02-28 at 03:23 +0100, Mohammed Adnène Trojette wrote:
> You're contributing to a solution. I just did not have the time to check
> the issue. If you want, you can report the bug directly to upstream
> (http://bugs.freedesktop.org/ - xkeyboard-config component).
That is indeed a good
I've spent several days reading man pages, configuration directory
README's, configuration files, ISO standards to figure out what the
README's were saying, etc
And aside from there being no useful mention whatsoever of laptop
function keys, as far as I can tell keyboard configuration has b
please let me know how.
If anyone knows what file to twiddle and how, I'll have a go at
seeing if the solution works.
Ray Dillinger
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
35 matches
Mail list logo
