Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

ntion that authentication for Google & Microsoft now uses the web browser, but nothing about nextCloud etc.) It is not expected that everything will work if you try to share configuration between different operating system versions. Sorry. :( Ouch! This is so frustrating. -richy. --

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

Confirmed: Same problem here for nextCloud and for google accounts. Gnome files says "Unable to access usern...@googlemail.com Invalid credentials for usern...@googlemail.com". Same for nextCloud accounts. goa-daemon says "/org/gnome/OnlineAccounts/Accounts/account_1706819076_1: Setting Attent

Bug#1033847: closed by Debian FTP Masters (reply to gabr...@debian.org (Gabriel F. T. Gomes)) (Bug#1033847: fixed in bash-completion 1:2.11-7)

Gabriel, On 7/17/23 08:39, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the bash-completion package: #1033847: Please update to upstream sources It has been closed by Debian FTP Masters (reply to gabr...@debian.org (Gab

Bug#1033847: Please update to upstream sources

version of the function has the same effect, of course. In my humble opinion, this is a prime example that Debian (and Ubuntu) maintainers should be careful with their patches, especially in well-maintained packages. Best wishes, -richard. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1033847: Please update to upstream sources

lied. Are you sure it is necessary? If no: can it be removed? If yes: has it been reported upstream and what was the response? Best wishes, -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1033847: Please update to upstream sources

The reproducible hang on my system turns out to be caused by Debian's 00-fix_quote_readline_by_ref.patch. Without it, tab completion returns immediately. This patch is not there upstreams. Is it really needed? It hangs at the line comparing $1 to ~*. Not sure what it does.

Bug#1033847: Please update to upstream sources

e upstream version. I am not sure it's worth debugging this further, given the outdated state of this package in Debian. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1033624: obs-studio: Pipewire capture source not listed

unable to capture the screen under Wayland (specifically, sway). Do you have xdg-desktop-portal-gnome installed? (See bug #1031645.) -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/> OpenPGP_signature Description: OpenPGP digital signature

Bug#1031645: gnome-shell should depend on xdg-desktop-portal-gnome

On 2/19/23 20:31, Simon McVittie wrote: [...] * gnome-core, a GNOME system with essential utilities like a login prompt, preferences, a file manager and a text editor, which Depends on gnome-session, and also on xdg-desktop-portal-gnome specifically; Okay, you managed to convince me that

Bug#1031645: gnome-shell should depend on xdg-desktop-portal-gnome

lity to do screen captures (PipeWire) in OBS studio, etc. Related: https://bugzilla.redhat.com/show_bug.cgi?id=2074189 -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1027506: Status of mozillavpn in Debian

On Wed, 11 Jan 2023 09:43:31 +0100 Sylvestre Ledru wrote: go: could not create module cache: mkdir /sbuild-nonexistent: permission denied To make this go away, the package must Build-Depend on dh-golang. However, that does not seem to be enough. The way subpackages are fetched or not during b

Bug#1027506: Status of mozillavpn in Debian

On 1/9/23 23:26, Sylvestre Ledru wrote: Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit : 2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to debian/ directory:    a) -DBUILD_TESTING=OFF to dh_auto_configure argument in debian/rules (without it it FTBFS trying to run some

Bug#1027506: Status of mozillavpn in Debian

On 1/9/23 10:38, Sylvestre Ledru wrote: Or just push a fork on github. I can take it for there :) For work-related reasons this isn't going to happen the next few weeks. Can you, please, update to 1.12.0 and include the minor described fixes to debian/*? It should work, afaict. -richard.

Bug#1027506: Status of mozillavpn in Debian

On 1/8/23 12:36, Richard B. Kreckel wrote: I am unfamiliar with GitLab. Sorry. Well, then I thought that could give it a try... Is there a simple walk-through what to do to create salsa MRs in a case like this package? (I've spent the whole Sunday now and I'm giving up frustra

Bug#1027506: Status of mozillavpn in Debian

Szlvestre, On 1/8/23 00:54, Sylvestre Ledru wrote: Could you please submit a MR here ? https://salsa.debian.org/sylvestre/mozillavpn I will be happy to upload it then Is that really necessary? I am unfamiliar with GitLab. Sorry. -richard.

Bug#1027506: Status of mozillavpn in Debian

contacted because of the build failure on mipsel and mpis64el. It makes little sense to insist on these architectures if upstream doesn't care. Please decide how to proceed and let me know if I can help in any way. -richard. -- .''`. Richard B. Kreckel : :' : `. `' `-<http://in.terlu.de/~kreckel/>

Bug#1026072: Fix for the bug

I am having it too and downgrading to 107.0.1-1 fixes the problem. It seems like someone was seeing something similar before and reported it here <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024351> but the bug got closed? -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1020695: [Pkg-openssl-devel] Bug#1020695: failure to compute digest: md4 and rmd160

IMO, this bug can be closed. There's been the decision by the OpenSSL Managment Board to reinstate RIPEMD160 (and only that) to the default providers in release 3.0.7. The other algorithm, MD4 is unsafe and remains in the legacy provider. References: OMC decision:

Bug#1020695: [Pkg-openssl-devel] Bug#1020695: failure to compute digest: md4 and rmd160

On 9/27/22 08:15, Sebastian Andrzej Siewior wrote: It is not part of any standard. It could hardly be less standardized. See ISO/IEC 10118-3:2018. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1020695: failure to compute digest: md4 and rmd160

W.r.t. RIPEMD160, this seems to be a mistake: https://github.com/openssl/openssl/issues/16994 Also, Fedora seems to have worked around this.

Bug#1020695: failure to compute digest: md4 and rmd160

python3.10/hashlib.py", line 123, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type ripemd160 -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/> OpenPGP_signature Description: OpenPGP digital signature

Bug#1020695: failure to compute digest: md4 and rmd160

/evp_fetch.c:373:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 40A761FE947F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: All other digests seem to work fine. -richy. -- Richard B. Kreckel <ht

Bug#1016283: onetbb: FTBFS: _segment_table.h:63:63: error: member ‘tbb::detail::d1::segment_table, 128>, tbb::detail::d1::cache_aligned_alloc

I am unable to reproduce the above compile-time error.

Bug#1016363: libx11-6 1.8.1 also breaks glxinfo

g those fixed anytime soon, it's best to work around in Debian. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1016363: libx11-6 1.8.1 also breaks glxinfo

. thunderbird 102.) -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1005884: linux-image-5.16.0-1-amd64: Kernel oops (unable to handle page fault) during boot

e? Yes that patch fixes it. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1005884: linux-image-5.16.0-1-amd64: Kernel oops (unable to handle page fault) during boot

table/05b11936073c8d6b7a28c07cc...@stwm.de/, I just removed the iwlwifi.ko module and it boots just fine now. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#1001156: qemu-arm needs some help with finding libs

On 05.12.21 23:16, Aurelien Jarno wrote: >> I am asking because without it I am getting >> a.out: error while loading shared libraries: libstdc++.so.6: cannot open >> shared object file: No such file or directory >> >> when running qemu-arm a.out. (libstdc++6-armhf-cross is installed.) > > You nee

Bug#1001156: qemu-arm needs some help with finding libs

On 05.12.21 20:22, Aurelien Jarno wrote: > libc6:armhf does provide the /lib/ld-linux-armhf.so.3. Do you have it > installed? I see. Maybe I messed up that symlink while trying to find an error. Say, do users have to export LD_LIBRARY_PATH=/usr/arm-linux-gnueabihf/lib? I am asking because witho

Bug#1001156: qemu-arm needs some help with finding libs

On 05.12.21 17:33, Michael Tokarev wrote: > 05.12.2021 19:21, Richard B. Kreckel wrote: >> On 05.12.21 14:34, Michael Tokarev wrote: >>> If you want your foreign binary to run, enable this foreign architecture >>> in dpkg (--add-architecture), run apt update, and in

Bug#1001156: qemu-arm needs some help with finding libs

On 05.12.21 14:34, Michael Tokarev wrote: > If you want your foreign binary to run, enable this foreign architecture > in dpkg (--add-architecture), run apt update, and install the corresponding > libc - this one will install things into the right place. All this has already been done. (Otherwise,

Bug#1001156: qemu-arm needs some help with finding libs

these steps. -rbk. -- .''`. Richard B. Kreckel : :' : `. `' `-<http://in.terlu.de/~kreckel/>

Bug#971939: cln FTCBFS: missing #include for intptr_t

nd be happy. ;-) -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#998698: qtwayland5 should always be installed along with Qt

n this bug. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#971939: cln FTCBFS: missing #include for intptr_t

Could you, please, try checking out cln from https://www.ginac.de/CLN/cln.git/ and run $ ./autogen.sh $ ./configure --host=powerpc64le-linux-gnu --disable-shared The question I am trying to get an answer for is if this really still hangs in CL_FLOATPARAM_CROSS. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#971939: cln FTCBFS: missing #include for intptr_t

Hi Helmut, On 05.11.21 15:41, Helmut Grohne wrote: > On Fri, Nov 05, 2021 at 10:32:59AM +0100, Richard B. Kreckel wrote: > I vaguely suspect that you do have qemu-user-binfmt installed and that > it enables running foreign binaries and changes the way configure > behaves. Does that m

Bug#971939: cln FTCBFS: missing #include for intptr_t

On 05.11.21 10:32, Richard B. Kreckel wrote: > On my bullseye setup, this works: > $ ./configure --host=powerpc64le-linux-gnu --disable-shared > $ make > $ qemu-ppc64le -L /usr/powerpc64le-linux-gnu ./tests/exam > Tests passed. It was on a bookworm/unstable setup, actually. (I don

Bug#971939: cln FTCBFS: missing #include for intptr_t

ations. How can I reproduce this? On my bullseye setup, this works: $ ./configure --host=powerpc64le-linux-gnu --disable-shared $ make $ qemu-ppc64le -L /usr/powerpc64le-linux-gnu ./tests/exam Tests passed. It surely produces the expected floatparam.h file, with long_double_mant_bits se

Bug#793675: hplip-gui: No system tray detected

Hi, On 15.05.21 10:32, Fabrice Bauzac-Stehly wrote: > "Richard B. Kreckel" writes: > >> Running version 3.21.2+dfsg1-2 of package hplip-gui, the annoying >> message still pops up after each login. > > Version 3.21.2+dfsg1-2 does not contain the ch

Bug#793675: hplip-gui: No system tray detected

hplip-systray.desktop" I wonder if anybody has tried if this works? If so, please speak up. -rbk. -- .''`. Richard B. Kreckel : :' : `. `' `-<http://in.terlu.de/~kreckel/>

Bug#847271: mutter: Resizing window moves the whole window

This seems to be fixed in mutter 3.38.2-1. OpenPGP_signature Description: OpenPGP digital signature

Bug#847271: mutter: Resizing window moves the whole window

izing terminals interactively, don't offset the position" in the update to 3.38.1-33-g067af969c. However, the problem is still there both in 3.38.1-2 and in 3.38.1-3. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#969029: pitivi fresh install gives missing dependecies message: GSound plugin, libav

Hi! After installing gir1.2-gsound-1.0, this message goes away. Pitivi already suggests installing gir1.2-gsound-1.0. This is perfectly correct, according to the Debian policy, section 7.2. On the other hand, it wouldn't hurt making this dependency stronger, would it? -richy. --

Bug#971939: cln FTCBFS: missing #include for intptr_t

pass --host to sbuild or --host-arch to pbuilder. Nevertheless, I attempted applying your box and built for arm64 and ppc64el. With the patch, it passes the build for arm64, but ppc64el still hangs in configure. Okay, all that has just been fixed upstream now. -richy. -- Richard B. Kreckel

Bug#971939: cln FTCBFS: missing #include for intptr_t

check if it works? (It's a little bit a stab in the dark, just reverting the last changes made there. After all, it should've worked before.) -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/> diff --git a/m4/intparam.m4 b/m4/intparam.m4 index 3c990d7..7d81424

Bug#971939: cln FTCBFS: missing #include for intptr_t

s bug when doing so? I would love to know at which point configure gets stuck. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#971769: rakudo 2020.09 uninstallable

Package: rakudo Version: 2020.09+dfsg-1 Severity: normal # apt install rakudo Setting up rakudo (2020.09+dfsg-1) ... rakudo-helper.pl: Reinstalling all perl6 modules ... (1/3) reinstall: perl6-readline Unhandled exception: Missing or wrong version of dependency 'gen/moar/stage2/MASTNodes.n

Bug#971741: pitivi should depend on libgstreamer-plugins-bad1.0-dev

Package: pitivi Version: 2020.09-1 Severity: important Dear Maintainer, Pitivi reports "Could not import 'GstTranscoder'. Make sure you have it available." and exits immediately unless package gir1.2-gst-plugins-bad-1.0 is isntalled. -- System Information: Debian Release: bullseye/sid APT

Bug#947247: libcln-dev: move cln.pc to a multiarch location

anks. I'm going to dupload a thoroughly modernized CLN package now. If you could have a look at it, this would be appreciated. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#947247: libcln-dev: move cln.pc to a multiarch location

in /usr/lib/? -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#899154: Acknowledgement (console switching broken on Polaris11 hardware with amdgpu.dc=1)

On Fri, 1 Jun 2018 01:10:10 +0200 "Richard B. Kreckel" wrote: > On 05/24/2018 11:54 PM, Richard B. Kreckel wrote: > > Aha! The problem goes away when upgrading to Xorg 1.20. > > Oh, the problem has re-surfaced after a recent burst of debian/testing > upgrades. :( T

Bug#942003: libcln-dev: remove unneeded dependencies

On 08.10.19 23:35, Pino Toscano wrote: > libcln-dev depends on some packages which are not strictly needed as > such: > - g++: even though cln is a C++ library, usually -dev packages with > includes do not require a certain compiler, which is chosen by the > user In theory, it should depend on

Bug#865999: [exiv2] Please package exiv2 0.26

On Sun, 10 Mar 2019 00:26:43 +0100 "Richard B. Kreckel" wrote: > Raphaël, what makes you sure that these CVEs are not present in earlier > versions (e.g. in 0.25 currently in testing)? Never mind. I see now that they're allo triaged by security. -richy. -- Rich

Bug#865999: [exiv2] Please package exiv2 0.26

tly in testing)? They were reported against 0.26 because that version was fuzzed, that's all, AFICT. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#914006: exiv2: Please package version 0.27

It looks like I forgot one grave bug: #62 (CVE-2018-5772) <https://github.com/Exiv2/exiv2/issues/216> But that's also fixed in 0.27.0. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#914006: exiv2: Please package version 0.27

On Sun, 18 Nov 2018 06:47:43 -0500 Jeremy Bicha wrote: > There is a new exiv2 0.27 RC2 tarball release. Could you look into > whether it fixes the security issues from 0.26 and would be acceptable > for unstable? I just went through all Debian bug reports associated with CVEs. As far as I can see

Bug#218557: dies with "Cannot find node `Top'"

ce the problem or should we close > the issue instead? I've never ran across this again. Let's close it. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#906777: ginac: FTBFS in buster/sid (-I: command not found)

This is because makeinfo is missing in your build environment. Will add a build-depend on texinfo to fix this. -richy.

Bug#900511: libcurl4 Conflicts: libcurl3

On Sat, 2 Jun 2018 23:14:40 +0300 Adrian Bunk wrote: > libcurl3 is not part of buster, and using libraries from previous > releases that are no longer present in a new stable Debian release is > not strictly supported - it works most of the time, but when problems > are reported a Breaks/Conflic

Bug#899154: Acknowledgement (console switching broken on Polaris11 hardware with amdgpu.dc=1)

On 05/24/2018 11:54 PM, Richard B. Kreckel wrote: > Aha! The problem goes away when upgrading to Xorg 1.20. Oh, the problem has re-surfaced after a recent burst of debian/testing upgrades. :(

Bug#899154: Acknowledgement (console switching broken on Polaris11 hardware with amdgpu.dc=1)

Aha! The problem goes away when upgrading to Xorg 1.20.

Bug#899154: console switching broken on Polaris11 hardware with amdgpu.dc=1

Package: linux-image-4.16.0-1-amd64 Severity: normal Version: 4.16.5-1 With current Debian/testing, I cannot switch consoles once I'm in graphics mode: Pressing Ctrl-Alt-F1 produces some artifacts on a black screen, mouse pointer still there and movable but that's it. It is impossible to switch ba

Bug#897598: cln: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian)

On 05/03/2018 02:39 PM, Manuel A. Fernandez Montecelo wrote: > I am attaching a patch that adds support for the arquitecture. I don't know > if > you will send upstream yourself or if you prefer that we send it. Pushed patch upstream: https://www.ginac.de/CLN/cln.git/?p=cln.git;a=commit;h=26aaf3

Bug#894310: Please build the thunderbolt-net module

Package: linux Severity: wishlist File: /boot/config-4.15.0-2-amd64 X-Debbugs-CC: sin...@nefkom.net I'ld like to play-test the thunderbolt-net module. Please consider enabling CONFIG_THUNDERBOLT_NET. Thanks -richy.

Bug#890861: man(1) fails to display anything

on another machine.) -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>

Bug#890861: man(1) fails to display anything

Package: man-db Version: 2.8.1-1 Severity: important $ man ls man: command exited with status 159: /usr/lib/man-db/zsoelim | /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl | nroff -mandoc -rLL=175n -rLT=175n -Tutf8 It turns out that $ MAN_DISABLE_SECCOMP=1 m

Bug#865209: gnome-terminal: Resizing terminal window to one side (left or right) also makes the window expand up and down

This looks like a duplicate of bug#850024. And it appears to have been fixed.

Bug#850024: gnome-terminal moves, while it's being resized

This bug has disappeared by an upgrade about a week ago. Apparently, the problem was not caused by gnome-terminal: downgrading from version 3.26.2-2 to 3.22.2-1 does not re-introduce it. In any case, feel free to close this bug.

Bug#850024: gnome-terminal moves, while it's being resized

Not sure if this is related, but while a gnome terminal window is being resized, messages about "Allocating size to GtkScrollbar 0x555efdf44410 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?" keep appearing in /var/log/messages.

Bug#850149: shotwell: Freezes when trying to open an image in fullscreen mode

Looking back at the original description, it might be this upstream bug: .

Bug#854912: unblock: shotwell/0.25.4-0.1

one justification offered for 1) but none for 2) I opted for option 1). Did I miss anything? I'm kindly asking that we work together to get this package of the stable version in before the release, for the reasons pointed out in #849688 and #850149. All my best, -richard. -- Richard B. Kreckel <http://in.terlu.de/~kreckel/>

Bug#850149: shotwell: Freezes when trying to open an image in fullscreen mode

> > Thanks for this! Shotwell is finally usable again. > > However the original problem (as described in the first comment) is > still present, do you want me to file a separate bug for that, or what > do you prefer? Is there a reference to an upstream bug? -richy. -- Richard B. Kreckel <http://in.terlu.de/~kreckel/>

Bug#854912: unblock: shotwell/0.25.4-0.1

I've NMUed shotwell 0.25.4+really0.24.5-0.1, containing 0.24.5, the latest stable release. It's now three days old. How to proceed? -richy. -- Richard B. Kreckel <http://in.terlu.de/~kreckel/>

Bug#854912: unblock: shotwell/0.25.4-0.1

Subject: unblock: shotwell/0.25.4-0.1 Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock package shotwell. Upstream version 0.25.1 of shotwell was packaged for testing, but that version is unsuitable for release in stretch as

Bug#849688: package in debian/testing is development version, severely broken

severity 849688 important (This is "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone", so setting to important.) Please respond today with a proposal how to get this broken package in Debian fixed. I may help with an NMU unless the

Bug#849688: package in debian/testing is development version, severely broken

On Mon, 02 Jan 2017 11:19:47 +0100 Jörg Frings-Fürst wrote: > I set the severity to normal because > * there are only 2 open bugs[5] for release 0.25.x at shotwell >bugtracker > * the next release date is near enough to get it into >unstable/testing. Jörg, having the freeze in mind, may

Bug#851061: Collections don't work at all, do they?

is silent about what to do with it. If there is some use, then it should be documented, so people can find out. -- Richard B. Kreckel <http://in.terlu.de/~kreckel/>

Bug#850548: gegl: please update to 0.3.10

Package: gegl Version: 0.3.8 Severity: normal A lot has happened upstream in gegl during the last half year. Please update gegl to version 0.3.10.

Bug#849883: inconsistency while processing conflicts

On 01/02/2017 12:22 AM, Richard B. Kreckel wrote: > [Status: Package emacs25 is marked for removal, emacs25-lucid and > emacs25-nox are both marked for *complete* removal.] That was incorrect: the two packages emacs25-lucid and emacs25-nox are not marked for complete removal. They are both

Bug#850024: gnome-terminal moves, while it's being resized

Package: gnome-terminal Version: 3.22.1-1 When grabbing one of the four corners of a window in order to resize it, one invariant is that the opposite corner should stay in its position. Gnome-terminal somehow manages to violate this invariant. Grab the top left or top right corner, whirl it aroun

Bug#849688: package in debian/testing is development version, severely broken

On 01/02/2017 11:19 AM, Jörg Frings-Fürst wrote: > * the next release date is near enough to get it into unstable/testing. That is great news! In the meanwhile, I suggest to upload a prerelease version with decent quality off from git into unstable/testing so it can receive fair testing. No bug

Bug#849883: inconsistency while processing conflicts

acs25-nox. This is, of course, where the nonsense begins. Confirm by clicking the 'Mark' button. [Status: Package emacs25 is marked for removal, emacs25-lucid and emacs25-nox are both marked for *complete* removal.] -richy. -- Richard B. Kreckel <http://in.terlu.de/~kreckel/>

Bug#849688: Acknowledgement (package in debian/testing is development version, severely broken)

On 12/29/2016 08:59 PM, Richard B. Kreckel asked: > Can a user downgrade to 0.24 once he has started using 0.25.1? On 12/29/2016 09:22 PM, Jens Georg replied: > Yes, that's perfectly fine as long as you go for shotwell-0.24.3, > otherwise you re-introduce an db index issue.

Bug#849688: package in debian/testing is development version, severely broken

0.24.2) or 2) move along with the version from git and hope for the best. I don't know which option is more feasible. This is a question for Jens Georg: Can a user downgrade to 0.24 once he has started using 0.25.1? -richy. -- Richard B. Kreckel <http://in.terlu.de/~kreckel/>

Bug#849208: Nvidia driver does not use DPMS

After upgrading to version 375.26-1, DPMS works even without setting it in xorg.conf, indeed even without an xorg.conf file. I was unable to find this issue in Nvidia's release notes for this driver version, though. Anyway, this bug can be closed. -rbk. --

Bug#776800: X server crashes when switching to another user

As of stretch, with the nvidia-driver 375.20 and Xorg 1.19 this problem has disappeared.

Bug#849208: Acknowledgement (Nvidia driver does not use DPMS)

It turns out that installing nvidia-xconfig and creating an xorg.conf file with Option "DPMS" "true" in the "Monitor" section makes the screen turn off as desired. The nvidia-xconfig package description says that "This tool is deprecated. The NVIDIA drivers now automatically integrate with the Xor

Bug#849208: Nvidia driver does not use DPMS

Package: nvidia-driver Version: 375.20-4 The screen blanks, but the backlight is never turned off. It seems like DPMS is not enabled? $ xset -q [...] DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Disabled This is the card: $ nvidia-detect Detected NVIDIA GPUs: 01:00.0 VGA co

Bug#838602: glibc should provide LSB-style symlinks /lib*/ld-lsb*.so.*

Package: libc6 Version: 2.23-5 Quite some 3rd party packages expect symbolic links ld-lsb*.so.* to the dynamic linker/loader. (E.g., on amd64, google-earth won't start on stretch unless /lib64/ld-lsb-x86-64.so.3 is a symlink to /ld-linux-x86-64.so.2). These symlinks used to be installed by package

Bug#830532: package should be re-built with gcc-6

Package: ginac Version: 1.7.0-1 Severity: serious The uploaded amd64 package was built with gcc-6. But on other architectures, it was built with gcc-5 -std=c++11. To avoid any ABI breakage or yet anther soname bump, this package should not migrate to testing. A new package should be uploaded as s

Bug#810851: Please upload version in testing to backports

propose to uplad a ersion to Debian backports [3]? -richy. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804505 [2] https://extensions.gnome.org/extension/750/openweather/ [3] http://backports.debian.org/Contribute/ -- .''`. Richard B. Kreckel : :' : `. `

Bug#791048: ginac: library transition may be needed when GCC 5 is the default

On 09/21/2015 09:29 AM, Simon McVittie wrote: > I have uploaded this revised diff. Well, that diff should resolve this issue. Thanks, Simon.

Bug#791048: ginac: library transition may be needed when GCC 5 is the default

On 09/21/2015 08:54 AM, Niels Thykier wrote: > Is anything blocking the upload (beyond someone doing it)? I'm not aware of anythin blocking. I've been away for a couple of weeks and will care for this later today.

Bug#791048: ginac: library transition may be needed when GCC 5 is the default

On 08/21/2015 10:12 AM, Simon McVittie wrote: > The broken situation would be that you have programs (or libraries) foo > and bar installed, both linked to libginac.so.5, with foo expecting the > g++-4.x ABI and bar expecting the g++-5 ABI. Depending which version of > libginac.so.5 you had install

Bug#791048: ginac: library transition may be needed when GCC 5 is the default

On 08/19/2015 10:56 AM, Simon McVittie wrote: > On Mon, 03 Aug 2015 at 10:01:51 +0200, Richard B. Kreckel wrote: >> But there is going to be libginac5 in Debian 9 >> anyway and this will be compiled with the new ABI. So, there is no need >> for a libginac2v5 package. > >

Bug#769960: gdm3: upgrade from 3.14.0 to 3.14.1 results in blank screen

Some more fiddling has revealed: It does not seem to be the nvidia driver's fault: with the nouveau driver the screen remains blank, too. It does not seem to be systemd's fault either: it also happens when starting gdm3 manually. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.

Bug#769960: gdm3: upgrade from 3.14.0 to 3.14.1 results in blank screen

Suddenly, a few hours ago, the same symptoms started on a machine that had been running Debian jessie fine for many months. Also, 'systemctl' reports that gdm runs as expected, but there's no screen content. Also, 'startx' works and launches a Gnome session. 'journalctl' reports nothing unusual (th

Bug#781222: mpmath.polyroots fails with "NameError: global name 'orig' is not defined"

6,6 +156,7 @@ # Constant polynomial with no roots return [] +orig = ctx.prec tol = +ctx.eps with ctx.extraprec(extraprec): deg = len(coeffs) - 1 -richy. -- Richard B. Kreckel <http://in.terlu.de/~kreckel/> -- To UNSUBSCRIBE, email to debia

Bug#776800: X server crashes when switching to another user

ed-source nvidia_drv.so does in #11 and #12. But in #10 I applied the appended brute-force patch to see what happens and, lo and behold, no crashes after a hundred times switching user and two days of doing normal work! This patch may introduce a small memory leak - I don't know. But the mach

Bug#779177: Make pdnsd installed by default

Package: pdnsd Running a web browser on a clean Debian/jessie install is dog slow because it tries to resolve common hostnames over and over again and there is no DNS cache. Such a system is simply not competitive. Feel free to reassign to tasksel or something more appropriate. -- Richard B

  1   2   >