Bug#964906: Same problem here, but not systematic

2021-04-27 Thread Raphaël Plasson
I have the same problem on two of my servers (both with similar 
configuration, debian buster with backports), both with a btrfs raid-1 
on /root.


In my case, initramfs indeed fails to mount /root, but performing a 
'btrfs device scan' followed by a manual mount to /root directly on the 
initramfs prompts solves the problem.


However, this problem is not systematically met. Even on the same 
server, the root may be correctly mounted after a reboot.


Maybe there is a race condition, so that the 
'/usr/share/initramfs-tools/scripts/local-premount/btrfs' may not be 
launched at the right moment?


Hoping this information can help.



Bug#970694: numba: FTBFS: unsat-dependency: python3-llvmlite:amd64 (< 0.34)

2020-09-29 Thread Raphaël Plasson
Note that this problem does hit the python3-numba package (and not only 
the src:numba) as it requires python3-llvmlite (<< 0.34). An `apt 
upgrade` doesn't touch the python3-llvmlite on my machines, and an `apt 
full-upgrade` would update python3-llvmlite and remove python3-numba. I 
thus assume than python3-numba is now uninstallable on sid.


Shouldn't this bug be opened also for python3-numba, as this package is 
likely to appear as uninstallable in the present state?


Raphaël


> Source: numba
> Version: 0.50.1-2
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in 
the past)

>
> numba has unsatisfiable build dependencies:
> | report:
> | -
> | package: sbuild-build-depends-main-dummy
> | version: 0.invalid.0
> | architecture: amd64
> | status: broken
> | reasons:
> | -
> | missing:
> | pkg:
> | package: sbuild-build-depends-main-dummy
> | version: 0.invalid.0
> | architecture: amd64
> | unsat-dependency: python3-llvmlite:amd64 (< 0.34)
>
> python3-llvmlite is now at version 0.34.0-1.
>
> Cheers
> --
> Sebastian Ramacher



Bug#949657: Linked to sqlite3 upgrade?

2020-01-23 Thread Raphaël Plasson
I just happened to have the same bug (well, I think it is the same one), 
impossible to start firefox, but the same problem was met with 
firefox-esr and thunderbird (none can start). Downgrading each of these 
ackages didn't solve the problem, thus leading to a problem from a 
common library.


By chance, I know that everything was working fine yesterday, and that 
only few package upgrades had been done meanwhile. Long story short, I 
downgraded back all possibly related packages until finding back the 
culprit.


Both firefox and thunderbird are working again when downgrading sqlite3, 
libsqlite3-0 and libsqlite3-dev from 3.31.0-1 back to the testing 
version 3.30.1+fossil191229-1


Raphaël



Bug#936076: Related(?) bug with python 3.8

2020-01-22 Thread Raphaël Plasson

It can be noticed that numba cannot be loaded at all with python 3.8:

Python 3.8.1 (default, Jan 19 2020, 22:34:33)
[GCC 9.2.1 20200117] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numba
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/numba/__init__.py", line 25, in 

    from .decorators import autojit, cfunc, generated_jit, jit, njit, 
stencil
  File "/usr/lib/python3/dist-packages/numba/decorators.py", line 12, 
in 

    from .targets import registry
  File "/usr/lib/python3/dist-packages/numba/targets/registry.py", line 
5, in 

    from . import cpu
  File "/usr/lib/python3/dist-packages/numba/targets/cpu.py", line 9, 
in 

    from numba import _dynfunc, config
ImportError: 
/usr/lib/python3/dist-packages/numba/_dynfunc.cpython-38-x86_64-linux-gnu.so: 
undefined symbol: _PyObject_GC_UNTRACK



This bug is linked to this issue https://bugs.python.org/issue35081

I didn't open a new bug as this bug is also referring to 
_PyObject_GC_UNTRACK as an issue.


Raphaël



Bug#926310: Working again since 2.6.2 version... for some time

2020-01-14 Thread Raphaël Plasson
I actually experienced again (once) the freeze after som use, linked to 
the same load of GLib-GIO-CRITICAL errors after some time. No specific 
activities were linked to this event (only one .ods file was being 
worked on during the event).


So same problem as before, but seems now more random rather than 
systematic as before.


Raphaël



Bug#926310: Working again since 2.6.2 version

2020-01-14 Thread Raphaël Plasson
I upgraded to the last 2.6.2 version of the client and, up to now, it 
seems again functional. It stills implies higher CPU usage than with the 
older clients, but I do not observe again the minutes-long freezes as 
observed in 2.6.0 and 2.6.1 versions (only CPU spikes for a couple of 
seconds when synchronizing files).


Raphaël



Bug#926310: No change with 2.6 version

2019-10-10 Thread Raphaël Plasson
The package is still unusable on my desktop. Am I the only one concerned
by the bug?

What happens is that the synchronisation seems to wrok correctly, it
scans the files, start to perform the update, but then the app freezes
with 100% CPU on one core for several minutes (can be tens of minutes
actually). It sometimes unfreezes for few minutes, but then the freeze
occur again, endlessly (probably each time it starts again).

This happens with kde. Launched from the terminal, the freeze is linked
to a huge load of "(process:7566): GLib-GIO-CRITICAL **: 07:06:51.918:
g_menu_insert_item: assertion 'G_IS_MENU (menu)' failed" errors.

Raphaël



Bug#926310: No problem with command line

2019-04-03 Thread Raphaël Plasson
For more information: I tried with the command line (time nextcloudcmd
--non-interactive -u user -p password -s nextcloud-directory
https://nextcloud-server), the sync takes only a couple of seconds...

The problems seems to come from the GUI, rather than from the sync
framework itself!

Raphaël



Bug#846255: Rebuild with apt-src

2016-12-01 Thread Raphaël Plasson
If this can be useful, I tried to enable this option by recompiling with 
apt-src:


apt-src  install jdupes
cd jdupes-1.6
***edit Makefile: uncomment "CFLAGS += -DENABLE_BTRFS"
cd ..
apt-src build jdupes
dpkg -i jdupes_1.6-1_amd64.deb

This _seems_ to work, as I can pass the -B option to jdupes, jdupes 
reports that some deduplication could be done ("finish with a 
Deduplication done (xxx files processed)"), but I obtain this kind of 
warnings (seems to be as many warnings as the number of files processed...):
warning: dedupe only did 0 byes: ***file_x*** => ***file_y***: Invalid 
argument [-22]


I do not know how harmful may be these warnings, nor if the 
deduplication indeed worked at all... So probably a "test on your own 
risk" functionality for the moment.


Hoping that this report may help a correct btrfs deduplication by more 
knowledgeable people.


Raphaël


--
Raphaël Plasson, PhD
Maître de Conférences (Assistant Professor)

UMR 408 Université d'Avignon - INRA
Sécurité & Qualité des Produits d'Origine Végétale
Équipe 'Chimie des Antioxydants'

Université d'Avignon - UFR-ip STS
Campus Jean-Henri Fabre
301 rue Baruch de Spinoza BP 21239
84916 Avignon Cedex 9

Phone: +33(0)4 9014 4441
Cell phone: +33(0)6 8855 4223
email: raphael.plas...@univ-avignon.fr