Bug#982195: obs-studio: Menus are messed up. highdpi related?
On Sun, 07 Feb 2021 11:44:42 +0100 Alberto Fuentes wrote: Package: obs-studio Version: 26.1.2+dfsg1-1+b1 Severity: normal X-Debbugs-Cc: paj...@gmail.com Dear Maintainer, All menus are cut and messed up in general. I attach start log and snapshot I have a very similar look in anki. And i have to start it with ANKI_NOHIGHDPI=1 Maybe is related? does it help if you start obs with the '--disable-high-dpi-scaling' flag? gfamdsr IOhannes OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1079045: pd-unauthorized: mp3-objects fail to create
some additional info: /usr/lib/pd/extra/unauthorized/mp3streamin~.pd_linux:/usr/lib/pd/extra/unauthorized/mp3streamin~.pd_linux: undefined symbol: InitMP3 mp3streamin~ ... couldn't create /usr/lib/pd/extra/unauthorized/mp3streamout~.pd_linux:/usr/lib/pd/extra/unauthorized/mp3streamout~.pd_linux: undefined symbol: head_check mp3streamout~ ... couldn't create /usr/lib/pd/extra/unauthorized/mp3fileout~.pd_linux:/usr/lib/pd/extra/unauthorized/mp3fileout~.pd_linux: undefined symbol: head_check mp3fileout~ ... couldn't create /usr/lib/pd/extra/unauthorized/mp3amp~.pd_linux:/usr/lib/pd/extra/unauthorized/mp3amp~.pd_linux: undefined symbol: freqs mp3amp~ ... couldn't create OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#988248: chiaki: No audio because of missing `libqt5multimedia5-plugins` package dependency
Control: tags 988248 + patch Control: tags 988248 + pending Dear maintainer, I've prepared an NMU for chiaki (versioned as 2.1.0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. mgdfsrt IOhannes OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#985507: v4l2loopback-utils: Unable to use dynamic device management due to old version
hi, On 3/19/21 11:43 AM, JCGoran wrote: Dear Maintainer, The current version of v4l2loopback-ctl in Unstable (currently 0.6) is a bit behind compared to upstream, and, as a result, I am unable to use dynamic device management to create new loopback devices on-the-fly since the option does not exist, see: https://github.com/umlaeute/v4l2loopback#dynamic-device-management As a workaround, I built v4l2loopback-ctl directly from upstream, but it would be great if the new version was included in Debian. ah no. in order for dynamic device management to work, you need support in the loopback module itself. just updating the utilities doesn't help. there has not been a *release* of v4l2loopback that has dynamic device management. the reasons are explained in https://github.com/umlaeute/v4l2loopback/issues/398 as soon as upstream releases a new version of `v4l2loopback`, the Debian packages will be updated accordingly. not sooner. gmsdrtf IOhannes
Bug#971737: lightning: all calendars disappeared (and throws errors when double-clicked)
On 10/6/20 2:10 PM, Carsten Schoenert wrote: lightning is since version 1:76.0_b1-1 a transitional package so there aren't any files within this package except the default Debian specific files. yes, i'm aware of that (hence i only mentioned the upgrade of thunderbird to the new version) Any Add-ons installed locally within the copied profile? Any Add-on not disabled while working on the profile? turns out the "lightning" add-on was still active. once i disabled it (and restarted thunderbird), the calendars are back to normal. i'm *pretty sure* that i didn't install the lightning add-on outside of Debian (that is: as a *local* add-on). so i guess there's a problem with the upgrade path from the Debian-packaged lightning (1:68.12.0-1) to the transitional package. gmdsr IOhannes PS: i'm leaving this open, in case you want to verify whether this is indeed an upgrade problem; for me, the problem is fixed now.
Bug#968416: lintian: Gives ridiculous warning about spelling in overrides file
On Fri, 14 Aug 2020 19:27:46 -0700 Felix Lechner wrote: > And BTW. are you going > to check spelling of comments in source code files as well? I'm pretty > sure you can find a lot of spelling typos there... > I am sorry but we do not plan to implement your suggestion. You may be > correct that there are lots of typos in code comments but that task is > too complicated for us. i think this was a tongue-in-cheek comment: lintian doesn't do spell-checking in comments, and i think that's fine. i (guess i) agree with robert, that lintian shouldn't do spell-checking in comments of lintian-override files either. > > > what's the point of checking spelling there? > > Like most of our tags, this one is based on user suggestions. could you please point to the relevant bug-report? i think it is great that lintian does spell-checking. inevitably it will find false-positives (that's to be expected). in this case, i think the sensible thing for maintainers is to override the false-positive it's good practice to document the context why this is not a spelling error in the first place. in many cases, this will re-produce the false-positive in the comment. which makes it all a bit tautological. (if i override the "spelling-in-override-comment" tag, will it trigger another warning?) i therefore propose to ignore spelling errors in lintian-override files if they appear in comments directly before any "spelling-in-*" tag in the overrides file. fgmndasr IOhannes
Bug#1004415: libassimp-dev: assimpTargets.cmake generates an invalid INTERFACE_INCLUDE_DIRECTORIES
On 1/27/22 05:14, David Fries wrote: It would be great if the Debian stable version of assimpTargets.cmake be released with the fix. in general, the "Debian stable version" is releasED. the release date for the current Debian/stable version was 2021-08-14, that is: in the past. i cannot really do anything about the past. i'm not fully decided whether i would want to provide a package for "bullseye-update" for this issue (i'm leaning towards "no", but haven't actually assessed the amount of work that needs to be done for that), gfmasd IOhannes OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1004633: gmerlin-avdecoder: FTBFS with ffmpeg 5.0
On Sun, 30 Jan 2022 23:04:11 +0100 Sebastian Ramacher wrote: Source: gmerlin-avdecoder Version: 1.2.0~dfsg-11 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm ftbfs Usertags: ffmpeg5.0 urgh. i have done a quick search, but haven't found any upgrading guide to migrate code-bases from ffmpeg4 to ffmpeg5. am i missing something? gfamsdf IOhannes OpenPGP_signature Description: OpenPGP digital signature
Bug#1009854: ITS: opusfile
On 4/19/22 10:59, IOhannes m zmölnig (Debian/GNU) wrote: Source: opusfile Version: 0.9+20170913-1.1 Severity: important [...] it would be great to hear something from the current maintainer of "opusfile". given that i have not had any feedback from ron for 29 days (with 21 days being the grace period as outlined in [1]), nor any objection from anyone else, i'm going to proceed with salvaging "opusfile". thanks for your attentions. gfdmasr IOhannes cheers [1] Debian Developer's Reference §5.12 <https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging> OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1016685: v4l2loopback: CVE-2022-2652 - leaking kernel memory via crafted card labels
On Fri, 05 Aug 2022 09:41:46 +0100 Neil Williams wrote: The following vulnerability was published for v4l2loopback (and is not included in the recent v0.12.7 git tag). how so? For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-2652 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2652 Please adjust the affected versions in the BTS as needed. as upstream, i strongly believe that the v0.12.7 release includes the relevant fix. is it enough t to just change the affected version or do I have to do something else as well? mgfads IOhannes OpenPGP_signature Description: OpenPGP digital signature
Bug#1084222: elpa-org: can no longer export to beamer
On 10/7/24 01:10, David Bremner wrote: IOhannes m zmölnig (Debian/GNU) writes: Package: elpa-org Version: 9.7.11+dfsg-1 Severity: normal Dear Maintainer, since i've upgraded elpa-org to 9.7.11+dfsg-1, I can no longer export my presentations to LaTeX/beamer. With the current version, when I try to export my slides (C-c C-e), I'm presented with the following options (only the LaTeX section shown): [l] Export to LaTeX [L] As LaTeX buffer [l] As LaTeX file [p] As PDF file [o] As PDF file and open I'm running 9.7.11 and can export to beamer fine. I do have (require 'ox-beamer) in my configuration. I suspect this is an upstream change. in the meantime i noticed that this might be related to my setup sharing configurations between multiple org documents. i'm basically doing: slides.org ```org #+TITLE: Some Title #+AUTHOR:Me and the others #+EMAIL: m...@example.com #+LANGUAGE: de #+INCLUDE: "config.org" # ... ``` and config.org: ``` #+STARTUP: beamer # ... ``` this used to work fine. now it seems that emacs/org no longer evaluates the `#+INCLUDE` directives, and therefore does not automatically switch to org-beamer-mode. if I manually run `M-x org-beamer-mode` the "export to PDF (Beamer)" option shows up and I can export as I used to. (well I *could*, but now I'm getting errors about 'pdflatex' being used rather than 'luatex', but that is a separate problem) so I guess it is more a problem of (upstream?) org-mode than a problem of elpa-org. (I'm not sure now that the downgrade of elpa-org did help; sometimes it worked and othertimes it did not) i'm not entirely sure how to proceed. gfmadsr IOhannes OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#331385: removal of pd-externals from unstable
Package: ftp.debian.org Severity: normal Please remove pd-externals from unstable. Justification: The package is not widely used, it is out of date and buggy (#323986). It is built from a CVS snapshot, which makes proper maintainance very difficult if not impossible. Thanks, Guenter -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-386 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#743209: gramps: l10n not working anymore
hi, bit of background: my system is setup to use C/en as default (there are few things i hate more than localized compiler errors). however some desktop applications (most noteably: gramps) i'd like to run in german. On 04/03/2014 02:31 PM, Ross Gammon wrote: > > I have come across similar problems before. I believe that Gramps does > not support non-UTF-8 locales. i sincerely hope that i got rid of all non-utf8 locales a long time ago. however,... > If you start with "LANG=de", gramps > will default to the "C" locale. > > Could you try?: > $ LANG=de_DE.UTF-8 gramps > did that (and also tried `LANG=de_AT.UTF-8 gramps` which is the actual locale i'm trying to use) to no avail. however, while doing so, i noticed that (after a recent re-installation of the entire system) the only locale i had configured on my system was en_US.UTF-8. building de_AT.UTF-8 did not help. then i dug into gramps a little bit, and noticed that "-v" should print out (among other things) the currently used locale: $ locale LANG=en_US.utf8 LANGUAGE=en_US:en ... LC_ALL= $ LANG=de_AT.UTF-8 /usr/bin/gramps -v ... Environment settings: - LANG : en_US.UTF-8 LANGUAGE : en:en GRAMPSI18N: not set GRAMPSHOME: not set GRAMPSDIR : not set ... # so i tried using LANGUAGE instead: $ LANGUAGE=de /usr/bin/gramps -v ... Environment settings: - LANG : de_DE.UTF-8 LANGUAGE : de GRAMPSI18N: not set GRAMPSHOME: not set GRAMPSDIR : not set PYTHONPATH: ... # that looked promising! $ LANGUAGE=de /usr/bin/gramps # gives me a german gramps! i'm sure it did work wit LANG previously. anyhow, i'll adapt my scripts to use LANGUAGE now. mdar IOhannes signature.asc Description: OpenPGP digital signature
Bug#748293: O: frei0r
Control: retitle -1 ITA: frei0r thanks pkg-multimedia has promised to adopt frei0r a long time ago. let's do it! (and move the package from experimental to unstable) fgmards IOhannes signature.asc Description: OpenPGP digital signature
Bug#583787: src:frei0r: Some files are LGPL 2.1
Control: tags -1 pending,fixed-in-experimental Control: owner -1 umlae...@debian.org thanks for the report. while packaging frei0r-1.4 we have updated debian/copyright to DEP5 and have now a (hopefully) accurate picture of the various licenses and copyrights used. frei0r_1.4-1 is now in experimental, and will hopefully be uploaded to unstable soon. gfmdsr IOhannes signature.asc Description: OpenPGP digital signature
Bug#750168: puredata: Conflicting declarations of function glist_scalar to cause undefined behaviour
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: tags -1 pending upstream Control: forwarded -1 https://sourceforge.net/p/pure-data/bugs/1145/ thanks for the bug-report. we have a fix at hand, which will part of the next upload (unless it is fixed by upstream first). fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTjE8lAAoJELZQGcR/ejb4l9sP/3pNOo2vEUpL1ug3Jlcuzyrp P0aN16AEtl+1nZivivmAbaRe+pNmHufe/tMxz2zg1ZPvlnRDzxo0fanhGMidxDDw WjU6nZdZ0J/KYHp6xnRJyMw8FAnY7cjscScuwi69YTME/Qz2Ki8EyrceIYU120N0 QPo6s5OHXZHnBetwF2+xj/Zy1o1/DV3xpapB69IhYFqKi37D01VPUxObZiS+/5OD 8iDh2Ix1JL7CYsoa/JsRax7ARXGvv7hphQv9nv+oB0ZBFCvxhS0dEZaBAYTzT+Q7 DwMMo0vie5B+w8Bo07sXnU/IRq2UdGkNfv4kBaCCvNaJfJGsHQ0Qzm0jYLC+RGKE mD0uSAzS4z+jrOs1aSkD08FztrjYdEyNFI+AhyqYpfV4AFJr6SYWwDeyyazBj434 932oAOOXyHuyUmWzXlo+SXrgh9Vwh9M74dJlU3BKONZqrT9gIjIUJa+EZW8/GPU/ fjRXbhZFvVB48Gz9sgPQhuQeK2mZXyhJ8Ql6TxLYoPvVkfUfWdyotx1hwtZu92M6 jtVAcysZRKbZfeqCJmvDXP0mTGeDXtJqWlQJ5flDPY77n04f7Z0pXwedd1MNu5mI F6y5sshx4LJsI/tEcsS+nx2HFCTHgzwmIAtQDRpa2jWq5hGFB/5ZKn+lhU9vrDFR A4BZtEJMWKuDjhVDsog5 =BMlh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751061: puredata: Conflicting declarations of function canvas_properties
On 06/09/2014 11:00 PM, Michael Tautschnig wrote: > Thank you very much for the previous bugfix. Yet during another rebuild of all > Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the > build thanks for the additional info. as there might be more of these conflicting declarations hidden in the current code-base, i would prefer if we could find a way to find all occurences at once, rather than incrementally (one fix per upload). any ideas how to proceed? fgsmdr IOhannes signature.asc Description: OpenPGP digital signature
Bug#729203: [FFmpeg-devel] Reintroducing FFmpeg to Debian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 (resending, to keep debian-devel and the bug-report in the loop) personally i would welcome if both libav and ffmpeg could co-exist within Debian¹. as i see it, libav and ffmpeg have diverged, and as such i would like to have the choice which one to use. On 2014-07-28 11:55, Marco d'Itri wrote: > On Jul 28, Alessio Treglia wrote: > >> Personally I don't feel like dropping libav in favor of ffmpeg >> now at this stage. + 1 i don't think that dropping libav is appropriate at all. > Except that, for a lot of the depending packages, there would be > an immediate benefit in the number of bugs fixed. at least in theory. > Personally I feel that we have inflicted libav on our users for > way more time than it was sensible to do. i would appreciate it, if you (and anybody else) used a less flammable &| touchy language. fgmadr IOhannes ¹ but then i'm not a member of the security team :-) -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJT1jRXAAoJELZQGcR/ejb45GYP/2a06m3B6PRGyjV6oGS1xwDg 0if/Lssn500F8yjrYFKnexKGZg6xncKVKJ+NJncX3pIWMKu/fOXKJusC5Z5eMdvg Ecruo7sXBojUnUxtaibGExkjdCWHv4wC/xwx/gQVUg3ijQGr5CQgZKXRPzf6dAG5 Sc4KS7w1SBtgLWaKvsOVhljSB39lye1cUk8vgkPkvSytJPiFMo1QSCDlbNz5JGbf 4c8viga5W9KCH5zMLzZTRQOkiPQpZMPsd/l220YX6ADwlBhnG/yRFBx7SBOnVDYb BIWb4MFrsCikzC5gJrJZdVAkB96AWOWR6J8N0s8LI2Y1ZwOIM4nJB1FNeQvFRaJI xe5p3dTI5DS7Kvc6i4LjKcO5m1EdZXeS1vV/OMDrLtgpfDC7pfhn3lImaYMPGCpA 60GNGo/PnbUMWGT3Z5JCeX/Q59X53d8DrW7gTcrQoSr6y0DN8AFEpcuDCYbd2ubt /A+0MeocRPNKGiNB7lEfvpSD3x3e4pGlSFB1AMgnwCGmpXzHeA51LzbDJGtfdWon x8L7OD5QD/LwRqQtAncRpf9jB56oJvktmznluSuCcJeY9ADSYH2YDPC1g3CCnuKG SOJpSClZrPjlc2511emDcnOaMJhkyjeQ8R+I67+I05r0jBdk2FDnFASsNVVcRV5o lzO+UTdVUs0nWsiDa+CX =PGZV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775890: assimp: Unresolved symbols in the debian version
Control: tags -1 confirmed pending thanks On 01/21/2015 08:38 AM, Leopold Palomo-Avellaneda wrote: > Package: assimp > Version: 3.0~dfsg-3 > Severity: important > > Dear Maintainer, > > * What exactly did you do (or not do) that was effective (or ineffective)? > > The debian version of the package shipped in sid or jessie has some symbols > dropped. > > * What was the outcome of this action? > > A simple program cannot be linked with the library. > > * What outcome did you expect instead? > > A linkeable lib. well, the library *can* be used (as long as you don't use the dropped symbols) [...] > > I guess that the file libassimp3.ver doesn't contain all the needed stuff, > for instante aiMaterial and then it's not exported. But, I'm not sure. yes, thanks for the hint. while ordinary (C-style) "ai*" symbols are exported, the C++ name-mangling prevents classes starting with "ai" to be exported (including aiMaterial). the fix is simple (adding another "ai*" line within the C++-scope). so we only need to get a freeze-exception from ftp-masters. msd IOhannes signature.asc Description: OpenPGP digital signature
Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist
On 10/07/2014 11:59 AM, IOhannes m zmoelnig wrote: > i am hit by the same problem. > as a temporary fix, i added the 'vgchange -ay' to > /usr/share/initramfs-tools/scripts/local-top/lvm2 > as adding it to > /etc/initramfs-tools/scripts/local-top/vgscan > somehow did not work (most likely due wrong order of execution, but i did not > investigate further) i turned out that i had forgotten to set +x permissions for /etc/initramfs-tools/scripts/local-top/vgscan gfmrdsa IOhannes signature.asc Description: OpenPGP digital signature
Bug#781095: pd-unauthorized: format list of contents and other small fixes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: tags -1 confirmed pending thanks On 2015-03-24 13:58, Daniele Forsi wrote: > Package: pd-unauthorized Severity: minor Tags: patch > > Dear Maintainer, > > the list of objects contained in this package is reflown (as per > the policy) and it's not easily readable in places like this > https://packages.debian.org/sid/pd-unauthorized > > The attached patch adds a leading space so that lines aren't > reflown, changes some words to upper case (MP3, Icecast/SHOUTcast), > adds a colon where it was missing, removes full-stops where > present, removes a double space and makes the list more consistent > removing "is" and adding "a". -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVGnGpAAoJELZQGcR/ejb475gP/ihhfBUlQPQsLMen5texMkk/ xsJK2Iw+echPEAFLieSOAryfZk96RV/tzHHZcPgwETS9t39G4lkObHOC7k12XAGy A/D47RcrD7a2xiGwlvNXIb2rR1WTjU5wSkLXlNC7oRXDRlMlsBGXlgMcqYc9lXOL pUEj4X04LTHMENYsRl1m8dc/+PREMoKDaeppIpE/BIHHke207vAXnjxw49rFy1eg NARcoIZb+7omjmiBHXi1hDhdg1pxiaHLPU6AKbsByPJjMtJ555QfpgmGmeC/c1Mh YLsNdYBdNKrdb/wVdyMFNgLsWdcwRvtlTD7NlAnMn4Jb9Sc1Or248sowyxcaxwhJ /H9dIocI9m27rA8Ihd/TCKq9p5sWWnDNGvubGfoYt+BFO/LlJXA/io1C8fDb3ZgQ NnF7xiKK3swdYBvZgGLKhW9g9Gjr5WxDvzGosRdelv/D/64peFqZPhEcVieq0fTI obn0hIjMgNbqQam3qMW566GmNIh1cOWzfmBBYm00yWvP11UgqSRcFwUS05z8WxYs eoexGad290Xs3KD8GGCG1oXvoGlq5I2Qevg4aRvHW2HZVJqxBoqcN8H0qI7SZT0L RAU31iEqu4SJtDooPIbYLIRWtAZX7E8kexEuy5pQc81WWpei/9lGqAE1YEXpQQ3/ uuNlJi2QAA6575dJKdRw =VT+g -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#788325: easytag: Don't register as default handler for directories
On 06/16/2015 01:01 PM, James Cowgill wrote: > The more I read about this situation affecting other projects, the more > I think David is right. All easytag is doing is following the > freedesktop spec and since easytag can handle directories, it should > have the directory mime type registered to it. This should either be > fixed in gnome-open or the spec should be updated to allow apps to > specify priorities. i can follow david's arguing and agree that it is not a bug in easytag (upstream). however, i don't think that the problem is with gnome-open or the freedesktop specs. installing the easytag package adds an entry to my /etc/mailcap file, that registers easytag as a program to "display non-text [directories] at the local site" (from mailcap(5), with a clarification by me in brackets). now i think that this is the main problem: easytag's desktop files declares that it *can* handle directories. (i guess the use case is that in your favourite filesystem browser you ought to be able to right-click on a directory and be presented with a list of applications that could handle that directory; having easytag in that list makes total sense to me). however, this declaration somehow makes the package installation process believe that it *should* handle directories (which is plain wrong), by adding an entry to /etc/mailcap. most likely the problem is with the packaging (not necessarily the easytag package per se, but maybe the tools used). according to update-mime(8), it *is* possible to add priorities to mime-types (for exactly the kind of problem we are facing). right now, easytag does not do anything special to register the mime-type handler, so it seems that the packaging should actively lower the priority. gfmadr IOhannes signature.asc Description: OpenPGP digital signature
Bug#788325: easytag: Don't register as default handler for directories
On 06/19/2015 09:38 PM, James Cowgill wrote: > I think you could reorder the easytag entries in /etc/mailcap by doing > some stuff with update-mime. i have added a fix in the master branch to use low-priorities mimetype associations in /etc/mailcap. > However it won't fix this problem because > desktop environments (including xdg-open and gnome-open) don't read > /etc/mailcap, they read the mimeapps.list files. I can't see any way to > set priorities for those (only user and desktop environment overrides). > http://standards.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.1.html > DoH!! [1] is quite explicit: there are no priorities... anyhow, your answer gave me two clues: - the good thing about that is, that i can now easily fix the problem for me, by adding the following to ~/.local/share/applications/mimeapps.list: [Removed Associations] inode/directory=easytag.desktop; - the bad thing is that this is on a per-user basis, and cannot be handled by the package. most likely the proper way would be to ensure that easytag does not appear in the [Default Applications] section (and that at least one proper filebrowser does appear in this section). but it also seems that Debian does not really maintain a mimeapps.list, which makes it rather hard to use :-( fgmadsr IOhannes [1] https://wiki.debian.org/MIME#Application_association signature.asc Description: OpenPGP digital signature
Bug#672352: gmerlin doesn't start with segfault
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 hi, thanks for the additional info. > > Versions of packages gmerlin recommends: pn gmerlin-encoders > pn gmerlin-plugins-avdecoder pn > gmerlin-plugins-base does the problem go away if you install any (or all) of these recommended packages? fgasdmr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUFr9EAAoJELZQGcR/ejb4r20P/RpHLMbhkdSLgsLSBjnlmj+L B6c0QvgMIXWjCGoK4R55lWiA9CkFKT210Kj3oYaiySLTQAH7OTv6SbNeUI7q8Vrf JwoDtHQcfiHQgiWYmYV36l6L3B0qaKEoKO4/J7xYl8J76wmruRKnrfm4dHvdnPyd jTvbsCAboWtX2rnvy2R/KvSdB3cwHwUrTh+Oxv9dmfR00Dx48/F0GInQxBE9+EIw X3cKrTj5oVuQtgRrK334/SKxHLAFhuqD96o6rZCFMoClQo0Wi9NqpaJ40ilvGUwK DWBZVaj4R8GOcZ85zh3Rr0EXWsf/eUjOFdv+CfbxV3z7fhz4F1Vkp3TvGqrJhTC0 WvfqnAxcCJBftrK+DYSzwzCA30tpph5ObIFyV/Akir67Eg1AZnkWcrIn95eWE3fm MlbKI7Jp4a1pd3stf0ncsI54Vfn9NwwXtQobpJTNRKCLlWa8xqDxIaZlr8fQxoZg cW2k/tL+uv9co0FZyQBkLNNR/byEiYUSHDl0iyDrHl87FGF2sQhj8ttYJlyEswnN ji8RFkluw8VNMeiCOuv3x4+s81XeF/DQKIUatQ6AlPFyJBpr5SDWHUIGE8Ugn+aT 8Tk6SAfXbsZYL4XT/LGaoUVR/8BsYt9m/Ky1Yw3gtenVlo8Wj8+Bl/2sD3XQEeEn xvHAsa8NFNWHy/pyVVr7 =/rom -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672352: gmerlin doesn't start with segfault
On 2014-09-15 12:28, IOhannes m zmölnig (Debian/GNU) wrote: > hi, > > thanks for the additional info. > > >> Versions of packages gmerlin recommends: pn gmerlin-encoders >> pn gmerlin-plugins-avdecoder pn >> gmerlin-plugins-base > > does the problem go away if you install any (or all) of these > recommended packages? and to reply to myself: uninstalling 'gmerlin-plugins-base' will make 'gmerlin' (as found in Debian/sid) segfault as well. i will upload a fixed version asap. fgamsdr IOhannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768295: pd-osc-1.0-2 is outdated and buggy
Control: retitle -1 bug with depth > 1 OSC address
Control: tags -1 confirmed
thanks
On 11/06/2014 11:28 AM, Antoine Villeret wrote:
> When parsing OSC path with more than one slash ('/'), the float is not
> understood by a number box.
to be precise, [routeOSC] will output a message with the remaining
OSC-path as the selector followed by the data.
when sending a message [/foo/bar 23( to [routeOSC /foo/bar], the
remaining OSC-path is empty, resulting in an empty symbol '' as the
selector; followed by the data (23).
the expected behaviour (which has been fixed in the upstream repository)
is to output with the selector "list".
signature.asc
Description: OpenPGP digital signature
Bug#765876: gramps: Import of utf-8 GEDCOM file without utf-8 BOM fails
i can confirm this problem. attached is a tiny gedcom export that exhibits the problem when being imported... mgdsar IOhannes umlauts.ged Description: application/gedcom signature.asc Description: OpenPGP digital signature
Bug#765876: gramps: Import of utf-8 GEDCOM file without utf-8 BOM fails
On 10/19/2014 09:46 AM, IOhannes m zmölnig (Debian/GNU) wrote: > i can confirm this problem. > this seems to be issue#8014 in gramps check [1] for a possible fix. gfmdsar IOhannes [1] https://sourceforge.net/p/gramps/source/ci/ed0ff156eec743136db0e9f2bdc9aa4e5a13110b/ signature.asc Description: OpenPGP digital signature
Bug#833917: open-iscsi: LVM fails to see iSCSI targets for non-mounted devices with systemd.
Package: open-iscsi Version: 2.0.873+git0.3b4b4500-8+deb8u1 Severity: normal Dear Maintainer, i'm expecting boot problems with a virtual machine using a disk(partition) that is an LVM-volume with the physical volumes on an iSCSI target. ## so here's my setup: - HOST was setup as a squeeze system, but has been upgraded to jessie+backports and system!! - HOST runs libvirtd/qemu to run a number of virtual machines - HOST's system resides on a normal built-in disk - additionally, HOST is connected to a SAN via iSCSI - HOST has a volumegroup 'virthosts' to manage the disks for the virtual machines. originally the volumegroup only contained local physical devices. - HOST hosts a virtual machine FOO, which has a system-disk /dev/virthosts/foo - later on an iSCSI LUN has been added to the VG - HOST also hosts a virtual machine BAR which has a system-disk /dev/virthosts/bar (which happens to be allocated on the local physical devices) and a data-disk /dev/virthosts/bardata, which has been forced to be allocated on the iSCSI LUN ## and here's the problem when i reboot the HOST machine LVM gets initialized, obviously *before* the iSCSI LUN comes up. this results in /dev/virthosts/bardata to be missing from the VG. in turn, this results in the virtual machine BAR not starting up. (the virtual machine FOO that has all its LVs on local PV comes up without a problem). afaict, the "solution" to this problem would be to add the VG 'virthosts' to the LVMGROUPS variable in /etc/default/open-scsi. unfortunately (as you can see from my conf-snippets) this is already the case, and did not help. i suspect this is because the VG is not used (e.g. "mounted") by HOST, but instead its LVs are passed on as raw devices to the virtual machines. here's some relevant (i hope) output from `journalctl`: > Aug 08 12:01:30 HOST systemd[1]: lvm2-activation-early.service: main process > exited, code=exited, status=5/NOTINSSTALLED > Aug 08 12:01:30 HOST systemd[1]: Failed to start Activation of LVM2 logical > volumes. > Aug 08 12:01:30 HOST systemd[1]: Unit lvm2-activation-early.service entered > failed state. > Aug 08 12:01:30 HOST lvm[856]: Couldn't find device with uuid > aLUEMH-r0mE-JubT-GB13-H6Hr-4ECS-wcHCBp. > Aug 08 12:01:30 HOST lvm[856]: Refusing activation of partial LV > virthosts/bardata. Use '--activationmode partial' to ov > Aug 08 12:01:30 HOST lvm[856]: 2 logical volume(s) in volume group > "virthosts" now active > Aug 08 12:01:30 HOST systemd[1]: lvm2-activation.service: main process > exited, code=exited, status=5/NOTINSSTALLED > Aug 08 12:01:30 HOST systemd[1]: Failed to start Activation of LVM2 logical > volumes. > Aug 08 12:01:30 HOST systemd[1]: Unit lvm2-activation.service entered failed > state. > Aug 08 12:01:30 HOST lvm[858]: Couldn't find device with uuid > aLUEMH-r0mE-JubT-GB13-H6Hr-4ECS-wcHCBp. > Aug 08 12:01:30 HOST lvm[858]: 2 logical volume(s) in volume group > "virthosts" monitored > Aug 08 12:01:31 HOST kernel: igb :02:00.0: changing MTU from 1500 to 9000 > Aug 08 12:01:31 HOST kernel: Bridge firewalling registered > Aug 08 12:01:31 HOST kernel: device eth0 entered promiscuous mode > Aug 08 12:01:31 HOST kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not > ready > Aug 08 12:01:31 HOST kernel: IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready > Aug 08 12:01:33 HOST kernel: igb :02:00.0 eth0: igb: eth0 NIC Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Aug 08 12:01:33 HOST kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link > becomes ready > Aug 08 12:01:33 HOST kernel: br0: port 1(eth0) entered forwarding state > Aug 08 12:01:33 HOST kernel: br0: port 1(eth0) entered forwarding state > Aug 08 12:01:33 HOST kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes > ready > Aug 08 12:01:42 HOST kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not > ready > Aug 08 12:01:44 HOST kernel: igb :02:00.1 eth1: igb: eth1 NIC Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Aug 08 12:01:44 HOST kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link > becomes ready > Aug 08 12:01:52 HOST networking[862]: Configuring network interfaces...done. > Aug 08 12:01:52 HOST ifup[1077]: /sbin/ifup: interface eth0 already configured > Aug 08 12:01:52 HOST kernel: Loading iSCSI transport class v2.0-870. > Aug 08 12:01:52 HOST kernel: iscsi: registered transport (tcp) after that, LVM does not attempt any activation anymore. instead i must re-activate the VG manually: # vgchange -a y 3 logical volume(s) in volume group "virthosts" now active after that, i can start the FOO virtual machine. given that open-iscsi already has the LVMGROUPS directive, I suspect that the problem is (solveable) in open-iscsi. please re-assign if this is not the case. -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LA
Bug#796241: lightdm-gtk-greeter: confusing placeholder text when greeter-hide-users=true
Package: lightdm-gtk-greeter Version: 2.0.2-1 Followup-For: Bug #796241 Control: Severity -1 important Dear Maintainer, confirmed on a brand new buster system. while seemingly a minor issue, this can easily lead to exposing the password of a user. please fix this..
Bug#874356: open-iscsi: (non-fatal) error during install
Package: open-iscsi Version: 2.0.874-4 Severity: minor Dear Maintainer, while installing 'open-iscsi' on a pristine machine, i got an error: > update-initramfs: Generating /boot/initrd.img-4.12.0-1-amd64 > cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory > > Setting up open-iscsi (2.0.874-4) ... the error was non-fatal and installation succeeded, nevertheless it was a bit disturbing to see the missing file unhandled. i'd suggest to test for the existence of that file before copying it around. (i casually checked the maintainer-scripts and it seems that these never use 'cp', and always check the existence of the initiatorname.iscsi file before doing anything to it). -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968), LANGUAGE=de_AT.utf8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages open-iscsi depends on: ii debconf 1.5.63 ii init-system-helpers 1.49 ii libc62.24-17 ii libisns0 0.97-2 ii libmount12.29.2-4 ii lsb-base 9.20170808 ii udev 234-3 Versions of packages open-iscsi recommends: ii busybox 1:1.22.0-19+b3 open-iscsi suggests no packages. -- Configuration Files: /etc/iscsi/iscsid.conf [Errno 13] Permission denied: '/etc/iscsi/iscsid.conf' -- debconf information excluded
Bug#874358: open-iscsi: iscsi_discovery spelling errors
Package: open-iscsi Version: 2.0.874-4 Severity: minor Dear Maintainer, running 'iscsi_discovery' without arguments i get the "help" screen which uses "defualt" (instead of "default") two times and has a somewhat hard to parse explanation on the '-f' flag.
Bug#874452: bonnie++: manpage has faulty 'multiple processes' eaxmple
Package: bonnie++ Version: 1.97.3 Severity: minor Dear Maintainer, 'man bonnie++' has a "MULTIPLE PROCESSES" section that explains how to use semaphores to run 3 copies of Bonnie++ simulatenously. Unfortunately, the commands shown are wrong as the '-y' option requires a synchronisation mode, so the example fails to run. The section about the '-p' option explicitly states that the parallel processes must be started with '-ys'. So please fix the "MULTIPLE PROCESSES" example: -bonnie++ -y > out1 & +bonnie++ -ys > out1 &
Bug#1070793: security.debian.org: Hibernate does not work from KDE Plasma menu. System does not power off.
2024-05-09
Thread
Hibernation does not work after update to Debian GNU/Linux, with Linux 5.10.0-29-amd64
Package: security.debian.org Severity: normal X-Debbugs-Cc: martin@rod.cz Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines ***
