Package: libopenhmd0
Version: 0.3.0-1
Severity: normal
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
It's not possible to coinstall libopenhmd0 for two different architectures.
I would like to install the package for both amd64 and i386, but this
doesn't work. apt produces a conflict if I try
Package: libkscreenlocker5
Version: 5.20.5-1
Severity: important
Forwarded: https://bugs.kde.org/show_bug.cgi?id=439814
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
This issue has started happening some time ago, but I don't know when exactly
kscreenlocker sometimes activates too slowly, and
AWS has now locked the discussion on their bug report:
https://github.com/aws/aws-cli/issues/4947#issuecomment-793192340
Sadly, they will not change their stance towards publishing proper
source packages of awscli and botocore on PyPI. On the positive side,
they promised to bundle the source code
Package: arduino-core-avr
Version: 1.8.3+dfsg1-1
Severity: important
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
The Arduino bootloader binaries shipped in Debian cannot be flashed to Arduino
devices, because they are too big. I tested only with the Arduino Uno, but
others may be affected as
Package: arduino-core-avr
Version: 1.8.3+dfsg1-1
Severity: important
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
It's not possible to update the fuse/lock bits with the included boards.txt and
recent avrdude versions.
avrdude used to mask unused bits for some microcontrollers, but this was
Package: cura
Version: 4.8-3
Severity: normal
Tags: upstream
Forwarded: https://github.com/Ultimaker/Cura/issues/9049
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
When starting a print or saving a material, Cura crashes with the following
error:
File "/usr/lib/cura/plugins/XmlMaterialProfi
The patch fixed the issue for me.
I pushed it to Salsa right away.
Can you upload 4.8-4, please?
There's also a little extra included:
The missing metadata license for cura.appdata.xml
> you hit some more issue we currently have with these files.
> A lot of them we can't currently rebuild at all and due this we can't
> ship them.
>
> We have written some notes about the known problems to
> /usr/share/doc/arduino-core-avr/README.Debian and it seems this should
> get extended abou
> Hmmm, when I connect gdb to the process, I get an immediate
>
> 0x7f9480ca33ff in __GI___poll (fds=0x55943c327d50, nfds=2, timeout=-1) at
> ../sysdeps/unix/sysv/linux/poll.c:29
> 29../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
gdb automatically breaks on all signals, an
Can you still reproduce this issue with the current Cura version
(including all dependencies) from sid? Does it also happen with Snap
package provided by upstream?
If yes, please report the bug on the upstream bug tracker and
cross-reference it.
Thank you very much.
If you are unable to do so, p
Hi Bernhard,
> I am not sure if my last mail reached you. [1]
> There I did not notice a line for libboost_nowide in ldd output.
>
> Also I tested by the last two modifications which
> made XS.so to be linked to libboost_nowide and made
> slic3r not fail with the unknown symbol error.
I got it n
know how
to fix it so signatures are imported as well.
Then, after importing the newer upstream releases, the other patches can
be applied.
I haven't tested the resulting xpi yet.
From 028146af85f65766d92af20088b8644630880fd7 Mon Sep 17 00:00:00 2001
From: Gregor Riepl
Date: Sun, 13 Sep
Package: awscli
Version: 1.18.135-1
Severity: wishlist
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
Please consider packaging version 2.0.x of the AWS CLI.
It contains a few crucial new features that aren't available in version 1.x.
Note that v2 is maintained in a separate branch: https://g
> cc1plus: out of memory allocating 9048820 bytes after a total of 77602816
> bytes
How about increasing the memory on the build machine or preventing a
parallel make?
90MB memory usage doesn't sound dramatic to me.
> I've looked at this a little more. From what I can tell, the dependency
> on botocore v2 is really going to make this hard to package. We can't
> simply update the botocore packages to version 2, since it is not
> backwards compatible with v1. Existing packages that depend on botocore
> would
I believe this bug has already been reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931930
Duplicate?
Note: The issue was *not* fixed upstream.
It was simply closed because of a lack of activity in two years.
> does the current version 4.8 still exhibit this problem?
For me at least, the UI is still broken in 4.8.
If the issue was in fact fixed by
https://github.com/Ultimaker/Cura/pull/7139 , it's not in 4.8 yet. That
PR was only merged 19 days ago and 4.8 was released on Nov 27.
> any idea when Enigmail 2.2.x will finds it's way into unstable? Ubuntu
> already is using this version in Groovy Gorilla.
>
> Thunderbrid 78.2.2 will get released within the next hours and I like to
> do a first upload of this version into unstable. But this isn't helpful
> as Thunderbird wil
Thunderbird 78.3.1 is now in unstable, and without Enigmail 2.2,
existing users may lose their existing configuration.
Please consider uploading the migration wizard (i.e. Enigmail 2.2) as
soon as possible.
> cura should require python3-uranium >= 4.7.0
> (Maybe cura should also depend on python3-savitar >= 4.7.0 to avoid further
> incompatibilities)
We did this so far, but it was probably missed during the last package
upgrade.
Funny though that you didn't get an upgrade on both packages. Perhaps
> A native build of cura-engine on unstable amd64 ends with:
>
> | In file included from /usr/include/gtest/gtest.h:387,
> | from /<>/tests/utils/SparseGridTest.cpp:4:
> | /<>/tests/utils/SparseGridTest.cpp: In member function
> ‘virtual void cura::GetNearbyTest_GetNearby_Test::T
Package: systemsettings
Version: 4:5.17.5-2
Severity: normal
Dear Maintainer,
When I enable or disable the "Force font DPI" setting in the "Fonts" -> "Fonts"
section, systemsettings5 crashes with the attached backtrace.
The most relevant part seems to be:
Thread 1 (Thread 0x7eff36317800 (LWP 981
> File "/usr/lib/python3/dist-packages/UM/Trust.py", line 9, in
> from cryptography.hazmat.backends import default_backend
> ModuleNotFoundError: No module named 'cryptography'
Missing dependency in python3-uranium, should be easy to fix.
diff --git a/debian/control b/debian/control
index
> I do confirm that the bug is present now in the cura package (v.
> 3.3.1) and makes the software unusable.
Are you sure about that version?
We're at 4.8 now...
> This has been reported to Cura developers:
> https://github.com/Ultimaker/Cura/issues/6841
As mentioned earlier, the fix from
https
> The stable debian Buster is shipping a very old version...
> https://packages.debian.org/buster/cura
Well... I'm sorry to say, but it's very, very unlikely that buster will
receive an updated Cura version. New package versions usually land in
sid and testing, and a new Debian stable release will
> Should we backport that change?
>
> +# WORKAROUND: Cura#5488
> +# When using the KDE qqc2-desktop-style, the UI layout is completely broken,
> and
> +# even worse, it crashes when switching to the "Preview" pane.
> +if Platform.isLinux():
> +os.environ["QT_QUICK_CONTROLS_STYLE"] = "default"
> Thank you Gregor, I'm using Appimage (which works fine). I plan to
> switch to Bullseye very soon: I will definitely try the package and
> post the results here.
>
> However, I find these reports interesting: at least it is known that
> there is a problem with this package. I've been using De
Package: thunderbird
Version: 1:78.5.1-1
Severity: minor
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
The Thunderbird startup script /usr/bin/thunderbird has a quoting error that
makes debug mode unusable.
When executing
/usr/bin/thunderbird -g
the following is printed:
INFO -> Starting
Package: wxmaxima
Version: 19.07.0-1.1
Severity: normal
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
When using the built-in help in wxMaxima, keywords are anchored to wrong
positions in the help text.
For example, if open the help for "simp", it (roughly) jumps to the help for
"commutative"
Package: python3-pynest2d
Version: 4.8.0-1
Severity: important
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
Please consider building pynest2d for all supported Python interpreters in
unstable, not just the latest (3.9 at this point).
When running Python software in a different interpreter, e
Package: platformio
Version: 4.3.4-1
Severity: wishlist
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
There is a new upstream version of PlatformIO available: 5.0.3
Please consider packaging it.
Thank you.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT pol
Package: yubikey-manager
Version: 3.1.1-3
Severity: wishlist
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
Please consider packaging the GUI version of YubiKey Manager in addition to the
command line tool.
The source code is available here: https://developers.yubico.com/yubikey-
manager-qt/Rel
Looks like removing --enable-locking isn't enough - an explicit
--disable-locking is needed.
Discovered here:
https://gitlab.com/sane-project/backends/-/issues/363#note_451303024
Please add the build flag and push a new version.
Thank you!
Package: tiled
Version: 1.4.3-1
Severity: normal
Forwarded: https://github.com/mapeditor/tiled/issues/2939
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
When starting Tiled for the first time on a new system, the two options
"Display news in status bar" and "Highlight new version in status bar
> https://salsa.debian.org/games-team/renpy/commit/fc29ebfe106238b590a7896450a5d1ad1f94f84e
>
>
> Switch to python3.
>
> Closes: #938351
>
I'm confuse
>> I've pushed my work to https://salsa.debian.org/biebl/enigmail and
>> uploaded to DELAYED/14.
>>
> In the interest of getting thunderbird updated in bullseye, I've just
> gone ahead and rescheduled the NMU from 5-day to 0-day.
Thanks!
I just tested the published package from the perspective of
> I do not have much experience debugging OpenGL stuff either, but
> from the description I would say that this could be a bug in Cura, or
> it could be a bug in the OpenGL implementation for AMD VEGAM, whatever
> that is. Perhaps it is an idea to identify the package being used
> by X.org for thi
8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From ba169d7446c5713b34471ecd6a8ccba43a31ad9d Mon Sep 17 00:00:00 2001
From: Gregor Riepl
Date: Sat, 31 Oct 2020 11:29:46 +0100
Subject: [P
Package: libsane
Version: 1.0.31-2
Severity: important
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
sane seems to have trouble interacting with certain USB scanners.
In particular: A Canon LiDE30 scanner, which is fully supported by the plustek
driver.
USB device permissions don't seem to be
After tracing sane-plustek in gdb, I found that it tries to create the
lock file /var/lock/sane/LCK..auto - but without creating
/var/lock/sane/ first.
I assume that at some point, this directory was created when installing
the package, but this is no longer valid with /var/lock pointing to
/run/l
> Any progress? If not, I'm willing to package this.
Looks like progress is being made:
https://salsa.debian.org/debian/scantailor-advanced
I was able to build + run the resulting package after adding the
attached quilt patch. It avoids errors due to a missing QPainterPath
include:
src/core/fil
Thanks for reporting, I'll add/mark those symbols ASAP.
Hi Chris,
> I just ACCEPTed fdm-materials from NEW but noticed it had:
Thanks!
Looks like this bug (and the one for the license issues in libsavitar) was not
sent to the 3dprinter list, so I missed it until now. Sorry.
> 9 The original release lacked a license. This was acknowledged by
> 10
Hi,
> I just ACCEPTed libsavitar from NEW but noticed it was missing
> attribution in debian/copyright for at least Kristen Wegner
> for pugixml.
>
> (This is not exhaustive so please check over the entire package
> carefully and address these on your next upload.)
Thanks.
I will look into th
Good morning.
> I just ACCEPTed libsavitar from NEW but noticed it was missing
> attribution in debian/copyright for at least Kristen Wegner
> for pugixml.
So, I rechecked that part.
The reason why there was no attribution to Kristen Wegner was because of the
wording "Based on". I assumed this
There is an ancient entry in the "Unsuitable" package list that mentions AGS.
This no longer applies, as the Linux port is fully open sourced.
The upstream project even offers Debian build scripts.
A little bit of work may still be required.
> W: libboost1.65-doc: privacy-breach-generic
> usr/share/doc/libboost1.65-doc/HTML/libs/assert/doc/html/assert.html
> (https://fonts.googleapis.com/css?family=open+sans:300,300italic,400,400italic,600,600italic%7cnoto+serif:400,400italic,700,700italic%7cdroid+sans+mono:400,700)
Both Open Sans a
The bug was incorrectly stated as fixed with the libArcus release.
I reopened it; it will be fixed for good when Cura appears in Debian.
Package: src:libarcus
Version: 3.0.3-1
Severity: important
buildd reports that the package fails to build on architectures other than
amd64:
--- new_symbol_file (libarcus3_3.0.3-1_arm64)
+++ dpkg-gensymbolsG2tD1l 2017-11-23 11:18:12.246629570 +
@@ -63,6 +63,7 @@
(c++)"Arcus::SocketLis
Package: cura
Version: 3.1.0-1
Severity: important
fdm-materials is currently a Recommended dependency of Cura.
If the package is missing and a previous printer definition is loaded, Cura
will immediately crash instead of handling the error gracefully.
This is an upstream bug, but until it gets f
Package: plasma-workspace
Version: 4:5.12.4-1
Severity: normal
Dear Maintainer,
The Plasma lockscreen displays start/stop/forward/backward controls when an
media player application like VLC, Amarok or SMPlayer is active.
It was previously impossible to disable these controls.
In Plasma 5.12.2, a
Package: p7zip
Version: 16.02+dfsg-4
Severity: grave
Tags: upstream newcomer security
Justification: user security hole
Dear Maintainer,
p7zip, p7zip-full and the non-free component p7zip-rar are affected by two
vulnerabilities:
https://landave.io/2018/01/7-zip-multiple-memory-corruptions-via-rar
> Since they are in two different source packages let's actually create
> two bugs.
Ah, I hadn't noticed that.
Thanks for splitting and retagging.
> Package: cura
> Version: 3.0.3-2
> Severity: wishlist
>
> Cura 3.1 is the latest available stable release.
Cura 3.1 is already packaged and currently going through the build queue.
It should be available soon.
Hi Graham
> Since the upload of 1:3.1.0-1, cura-engine's autopkgtests have been
> failing [1] with the following error:
>
> [ERROR] Trying to retrieve unregistered setting with no value given:
> 'slicing_tolerance'
> info: test exiting
> autopkgtest [23:15:10]: test test-command-line: ---
Hi,
is this bug still relevant for protobuf 3.0?
If not, please report the bug as fixed.
Thank you.
Also: It looks like the upstream PR URL is wrong.
It refers to an entirely different patch.
Hi,
is this bug still relevant for protobuf 3.0?
If not, please report the bug as fixed.
Thank you.
Also: It looks like the upstream PR URL is wrong.
It refers to an entirely different patch.
It looks like Ultimaker dropped official 32 bit support:
https://github.com/Ultimaker/CuraEngine/issues/547
@pere fixed a few obvious bugs, but testing and more patches (if required) are
welcome.
cura-engine 2.5.0 is available in sid.
Note that it's currently missing libArcus for integration into
Package: kubernetes-client
Version: 1.7.7+dfsg-2
Severity: important
Dear Maintainer,
The current version of kubernetes-client in Debian seems to have a bug in
option handling.
Any server or user flags specified on the command line or in ~/.kube/config are
ignored.
Instead, kubectl always tries
According to https://bugzilla.mozilla.org/show_bug.cgi?id=1357323 ,
this bug should no longer affect Firefox 55 and 56, as the gonk code was
removed from the tree.
Please confirm.
Package: virtualbox-dkms
Version: 5.2.4-dfsg-2
Severity: important
Dear Maintainer,
After upgrading linux-image-amd64 and linux-headers-amd64, virtualbox-dkms
fails to build the vbox modules with DKMS. libelf-dev is installed, so this is
not https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88647
>> In Plasma 5.12.2, a system setting was introduced that allows enabling and
>> disabling the feature.
>> In the Debian version of lockscreen however, these settings aren't shown, for
>> an unknown reason.
>
> I can't reproduce the issue here. I see the Show media controls option in the
> Screen
It's a bit hard to see from the stack trace what exactly is causing the
crash. There is a mention of
/home/karl/.local/share/cura/3.1/machine_instances/AnetA8WithInit.json
however, have you tried moving /home/karl/.local/share/cura away and starting
from scratch?
I suspect this is a bug in Cura o
Package: python3-pyqt5
Version: 5.10.1+dfsg-1
Severity: important
Tags: patch
Dear Maintainer,
Upstream introduced a bug into PyQt5 5.10.1 that broke Cura:
https://github.com/Ultimaker/Cura/issues/3438
Maintainers in ArchLinux and Ubuntu have already applied a backported patch
that fixes the bug
> This is a bug in pyqt5 5.10.1.
>
> https://github.com/Ultimaker/Cura/issues/3438#issuecomment-383494598
Thanks for pointing this out.
And now I see why I wasn't affected by this: My system is still at PyQt 5.9.2.
> Here's a patch:
>
> https://git.archlinux.org/svntogit/packages.git/tree/trun
> Well, following the code, it seems that the option is only shown if you have
> org.kde.breeze.desktop or org.kde.breezedark.desktop set as your
> lookandfeelpackage configuration (~/.config/kdeglobals [KDE]
> LookAndFeelPackage)
>
> Can you please check if your configuration is says so?
It see
Hi,
as expected, Cura is working again.
Thanks for applying the patch.
Package: libqt5webkit5
Version: 5.9.1+dfsg-5
Severity: important
Tags: patch upstream
Dear Maintainer,
When running a Python3 application that uses QtWebKit5, I'm getting the
following segfault:
Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
0x7fffefc5592f in JSC::JSRopeStri
Hi Petter,
sorry about the delay. I was waiting for a review from Bas (or another DD).
The package is also currently stuck at version 2.5.0, due to a lack of time on
my side, but I'll try to prepare and push an update ASAP.
The package is on mentors.debian.net, but you also need to get all the
de
>> The package is on mentors.debian.net, but you also need to get all the
>> dependencies if you want to build it yourself:
>> https://mentors.debian.net/packages/uploader/onitake%40gmail.com
>
> Is this the same code as on git.debian.org?
Yes. The source packages I pushed to Debian Mentors corre
> Do you plan to maintain these packages as part of the 3dprinter group?
> If so, the maintainer should be changed from your name to the mailing
> list, to make sure the packages show up on
> https://qa.debian.org/developer.php?login=3dprinter-gene...@lists.alioth.debian.org
> >.
Ok.
> The pack
Hi Petter
> So, libarcus is uploaded and in NEW, and cura-engine is ready to be
> uploaded but held off until its build dependency libarcus is in
> unstable (what about uploading without arcus support for now?)
CuraEngine is not of much use without libArcus, I'm afraid...
I'm not sure if it even
> So, libarcus is uploaded and in NEW, and cura-engine is ready to be
> uploaded but held off until its build dependency libarcus is in
> unstable (what about uploading without arcus support for now?)
Before you upload cura-engine, please pull again.
I forgot to change the Maintainer to the list.
Hi,
the Debian 3dprinter team is preparing a release of the new CuraEngine and the
rest of the Cura packages:
https://anonscm.debian.org/cgit/3dprinter/packages/cura-engine.git/
https://anonscm.debian.org/cgit/3dprinter/packages/cura.git/
We're still working on 2.5, but 2.7 or 3.0 will be release
A little update on the StringTest failures on 32-bit systems.
This was already reported upstream by thopiekar:
https://github.com/Ultimaker/CuraEngine/issues/619
I linked the sid build results there.
For some very strange reason, I don't see this SEGFAULT when I run the build
process in a 32-bit
> I've just uploaded libsavitar to NEW, after giving the d/copyright file a
> close
> look. I am aware of the several proposals for improvements, but concluded
> that those can be uploaded next time, and decided it was more important
> to get a slot in the NEW queue for now.
>
> The only package
>> Uranium and Cura are both ready for review.
>
> Very good. I'll have a look, and hope we can coordinate any fixes on
> IRC.
>
> Btw, are you aware of http://dep.debian.net/deps/dep3/ >?
Partially. I know the guidelines for patches, but wasn't aware of this DEP.
I'll look at it.
This lack of ports mirrors in choose-mirror is still an issue.
Just ran into the problem on the sparc64 port.
I submitted a merge request for your patch here:
https://salsa.debian.org/installer-team/choose-mirror/merge_requests/1
> Bug #928230 in mariadb-10.3 reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
Are you going to do an upload for buster, or is this postponed until after
buster becomes stable?
If pos
Dear maintainer,
With the latest upload of MariaDB 10.3, --libmysqld-libs is now supported by
mysql_config/mariadb_config:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928230#46
Can you please trigger a rebuild of amarok once mariadb-10.3_1:10.3.15-1 has
hit unstable?
Please also consider u
Package: initramfs-tools
Version: 0.133
Severity: normal
Dear Maintainer,
On systems with a small /boot volume, update-initramfs will frequently fail
with
pigz: abort: write error on (No space left on device)
This hasn't been an issue so far, with a 200MB boot volume and a maximum of 2
kernels
Package: thunderbird
Version: 1:68.5.0-1+b1
Severity: normal
Dear Maintainer,
After upgrading Thunderbird to version 68.5, the new mail dialogue wraps lines
after 54 characters instead of the commonly used 72.
Changing the value of mailnews.wraplength has no effect.
This was not the case with F
> We have collected some steps you should mind within the Wiki.
>
> https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues
I disabled all addons and also tried safe mode: Doesn't make a
difference. I didn't try to create a fresh profile.
And I couldn't find any bugs on the Debian tracker o
>> I do workaround around this temporally by adjusting the DPI scaling
>> using the key combination 'Crtl +' or using the 'Crtl' key and the
>> scroll wheel on the mouse.
>
> That's a... very interesting workaround.
> Even more interestingly, the text size doesn't even change when I "zoom"
> using
Package: libdpkg-perl
Version: 1.19.7
Severity: wishlist
Dear Maintainer,
Currently, dpkg-source supports unpacking multiple orig tarballs into the
source directory.
Aside from the main archive, additional tarballs are marked by a 'component'
name that is appended to the base tarball name, as do
> gcr builds fine now on sparc64, thanks for the patch
Cool stuff, thanks for pushing the update!
This should finally allow most of Gnome to build again on sparc64.
It looks there are a few unit test crashes/aborts now, though.
amd64:
42/43 gcr:gcr-base / system-promptFAIL 0.52 s
> Hello, your package build depends on a cruft package, I'm uploading a fix in
> deferred/5
>
> patch is here: (I'll close the bug before uploading)
> - pylint3, python3-pytest,
> + pylint, python3-pytest,
> python3-pyqt5,
Thanks a lot for this!
I tested locally and pushed 3.3.0-2 that inclu
> When running Cura under a scaled KDE desktop (1.3x scale), the font and
> positioning of text makes Cura unusable. I have attached a screenshot of
> what it looks like.
The bug is known, but I'm not sure if it is in python3-qt or in Cura itself.
I intend to package a recent Cura version very
> > The bug is known, but I'm not sure if it is in python3-qt or in Cura itself.
>
> Do you know if it was already reported to upstream? I couldn't find it
> on github, but there's 967 issues open...
Sorry, my message was referring to the original bug, where all text was
completely empty.
May I
> please mark some more symbols as optional, seen when building with -O3 on
> ppc64el and s390x.
>
> patch at
> http://launchpadlibrarian.net/462915998/libsavitar_4.4.1-1_4.4.1-1ubuntu1.diff.gz
These look good to me, please apply the patch.
I still don't get why so many STL symbols are exported
Package: cura
Version: 4.4.1-1
Severity: wishlist
Dear Maintainer,
Please consider packaging the Python module trimesh and making it a dependency
of cura or uranium-plugins.
Without this module, the AMFReader plugin will not work:
2020-02-08 11:49:09,224 - ERROR - [MainThread] UM.Logger.logExce
Package: wnpp
Severity: wishlist
* Package name: trimesh
Version : 3.5.19
* URL : https://github.com/mikedh/trimesh
* License : MIT
Programming Lang: Python
Description : Trimesh is a Python library for loading and using
triangular meshes
Trimesh is a pur
> After upgrading to 4.4.1 the UI is not usable. See screenshot. The dialog is
> all messed up.
> Appimage version works as expected.
>
> Deleting the config folder is even worse. I can't get past the settings
> wizard.
Thank you for the bug report.
The issue is known and reproducible, but a sol
Package: plasma-workspace
Version: 4:5.14.5.1-3
Severity: normal
Dear Maintainer,
The keyboard indicator plasmoid (i.e. the tray indicator) from plasma-widgets-
addons and the KDE lock screen stopped showing lock key status for me.
This is a crucial feature when using a keyboard that doesn't have
> I reported this problem some time ago, it depends on the 5.62.0 framework.
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872
I'm positive this is not the same bug, as I don't have problems with keyboard
lock state per se.
#942429 only concerns the propagation of lock state to notif
Hi Dmitry,
> That happens because I did not bump the build-dependency on Qt, so the
> buildds picked up Qt from unstable (and not from experimental) when building
> PyQt5.
>
> My plan is to upload PyQt 5.12 to unstable in the next few days, and upload
> Qt 5.12 to unstable after 5.12.5 is release
> A transition is in progress right now. Some packages will be uninstallable
> until the release team rebuilds them. Hopefully that will happen later this
> week.
>
> Please follow the transition bug (https://bugs.debian.org/941093) to track
> its state.
Thanks for the info!
signature.asc
Descr
Looks like the dependency chain is fixed, python3-pyqt5 is installable again.
Thanks.
Thanks for the bug report.
Building the package used to work fine, so I'm suspecting the pthread
detection scripts have started failing with glibc 2.28, which was updated
recently.
I will look into the issue.
If you have any idea why it might be occurring, please share.
201 - 300 of 433 matches
Mail list logo
