<?xml version="1.0" encoding="utf-8" ?>

<?xml-stylesheet type="text/xsl" href="/templates/2k11/rss.xsl" media="screen" ?>
<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>Daniel Lange's blog (Entries tagged as trixie)</title>
    <link>https://daniel-lange.com/</link>
    <description>agrep -pB IT /dev/life</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 2.6.0 - http://www.s9y.org/</generator>
    <pubDate>Wed, 06 May 2026 06:32:29 GMT</pubDate>

    <image>
    <url>//daniel-lange.com/uploads/Avatar_Blog_144_234.png</url>
    <title>RSS: Daniel Lange's blog - agrep -pB IT /dev/life</title>
    <link>https://daniel-lange.com/</link>
    <width>144</width>
    <height>234</height>
</image>

<item>
    <title>Getting scanning to work with Gimp on Trixie</title>
    <link>https://daniel-lange.com/archives/195-Getting-scanning-to-work-with-Gimp-on-Trixie.html</link>
            <category>Debian</category>
    
    <comments>https://daniel-lange.com/archives/195-Getting-scanning-to-work-with-Gimp-on-Trixie.html#comments</comments>
    <wfw:comment>https://daniel-lange.com/wfwcomment.php?cid=195</wfw:comment>

    <slash:comments>9</slash:comments>
    <wfw:commentRss>https://daniel-lange.com/rss.php?version=2.0&amp;type=comments&amp;cid=195</wfw:commentRss>
    

    <author>nospam@example.com (Daniel Lange)</author>
    <content:encoded>
    &lt;p&gt;Trixie ships &lt;a href=&quot;https://www.gimp.org/&quot; title=&quot;Gimp Homepage&quot;&gt;Gimp&lt;/a&gt; 3.0.4 and the 3.x series has gotten incompatible to &lt;a href=&quot;http://www.sane-project.org/sane-frontends.html&quot;&gt;XSane&lt;/a&gt;, the common frontend for scanners on Linux.&lt;/p&gt;

&lt;p&gt;Hence the maintainer, Jörg Frings-Fürst, has &lt;a href=&quot;https://git.jff.email/cgit/xsane.git/commit/?id=e94358be7216ead86f500f2f19420a61435eceec&quot;&gt;disabled the Gimp integration temporarily&lt;/a&gt; in response to a Debian bug &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088080&quot;&gt;#1088080&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;There seems to be no tracking bug for getting the functionality back but people have been commenting on Debian bug &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993293&quot;&gt;#993293&lt;/a&gt; as that is ... loosely related &lt;img src=&quot;https://daniel-lange.com/plugins/serendipity_event_emoticate/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; class=&quot;emoticon&quot; /&gt;.&lt;/p&gt;

&lt;p&gt;There are two options to get the Scanning functionality back in Trixie until this is properly resolved by an updated XSane in Debian (e.g. via trixie-backports):&lt;/p&gt;

&lt;p&gt;Lee Yingtong Li (RunasSudo) has created a Python script that calls XSane as a cli application and published it at &lt;a href=&quot;https://yingtongli.me/git/gimp-xsanecli/&quot;&gt;https://yingtongli.me/git/gimp-xsanecli/&lt;/a&gt;. This worked okish for me but needed me to find the scan in &lt;code&gt;/tmp/&lt;/code&gt; a number of times. This is a good stop-gap script if you need to scan from Gimp $now and look for a quick solution.&lt;/p&gt;

&lt;p&gt;Upstream has completed the necessary steps to get XSane working as a Gimp 3.x plugin at &lt;a href=&quot;https://gitlab.com/sane-project/frontend/xsane&quot;&gt;https://gitlab.com/sane-project/frontend/xsane&lt;/a&gt;. Unfortunately compiling this is a bit involved but I made a version that can be dropped into &lt;code&gt;/usr/local/bin&lt;/code&gt; or &lt;code&gt;$HOME/bin&lt;/code&gt; and works alongside Gimp and the system-installed XSane.&lt;/p&gt;

&lt;p&gt;So:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;code&gt;sudo apt install gimp xsane&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Download &lt;a href=&quot;https://daniel-lange.com/software/xsane-1.0.0-fit-003&quot;&gt;xsane-1.0.0-fit-003 (752kB, AMD64 executable for Trixie)&lt;/a&gt; and place it in &lt;code&gt;/usr/local/bin&lt;/code&gt; (as root)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;sha256sum /usr/local/bin/xsane-1.0.0-fit-003&lt;/code&gt;&lt;br /&gt;
# result needs to be af04c1a83c41cd2e48e82d04b6017ee0b29d555390ca706e4603378b401e91b2&lt;/li&gt;
&lt;li&gt;&lt;code&gt;sudo chmod +x /usr/local/bin/xsane-1.0.0-fit-003&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;# Link the executable into the Gimp plugin directory as the user running Gimp:&lt;br /&gt;
&lt;code&gt;mkdir -p $HOME/.config/GIMP/3.0/plug-ins/xsane/&lt;/code&gt;&lt;br /&gt;
&lt;code&gt;ln -s /usr/local/bin/xsane-1.0.0-fit-003 $HOME/.config/GIMP/3.0/plug-ins/xsane/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart Gimp&lt;/li&gt;
&lt;li&gt;Scan from Gimp via File → Create → Acquire → XSane &lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The source code for the &lt;code&gt;xsane&lt;/code&gt; executable above is available under GPL-2 at &lt;a href=&quot;https://gitlab.com/sane-project/frontend/xsane/-/tree/c5ac0d921606309169067041931e3b0c73436f00&quot;&gt;https://gitlab.com/sane-project/frontend/xsane/-/tree/c5ac0d921606309169067041931e3b0c73436f00&lt;/a&gt;. This points to the last upstream commit from 27. September 2025 at the time of writing this blog article.&lt;/p&gt;

&lt;h2&gt;Debugging help&lt;/h2&gt;

&lt;p&gt;(added 06.05.2026)&lt;br /&gt;
As some people in the comments seem to have issues with getting the plugin to work on their systems:&lt;/p&gt;

&lt;p&gt;Run &lt;code&gt;$HOME/.config/GIMP/3.0/plug-ins/xsane/xsane-1.0.0-fit-003 --version&lt;/code&gt; as a shell command line.&lt;/p&gt;

&lt;p&gt;This should output:&lt;/p&gt;

&lt;pre&gt;
xsane-1.0.0 (c) 1998-2022 Oliver Rauch
  E-mail: Oliver.Rauch@xsane.org
  package xsane-1.0.0-fit-003
  compiled with GTK-3.24.49
  with color management function
  with GIMP support, compiled with GIMP-3.0.4
  XSane output formats: jpeg, pdf(compr.), png, pnm, ps(compr.), tiff, txt
&lt;/pre&gt;

&lt;p&gt;If it doesn&#039;t, the shell may tell you what step of the instructions you missed (e.g. the +x attribute) or the loader shows what library you are missing on your system.&lt;/p&gt;
 
    </content:encoded>

    <pubDate>Wed, 24 Dec 2025 09:00:00 +0000</pubDate>
    <guid isPermaLink="false">https://daniel-lange.com/archives/195-guid.html</guid>
    <category>debian</category>
<category>scanner</category>
<category>trixie</category>
<category>updated</category>
<category>xsane</category>

</item>
<item>
    <title>Make `apt` shut up about &quot;modernize-sources&quot; in Trixie</title>
    <link>https://daniel-lange.com/archives/192-Make-apt-shut-up-about-modernize-sources-in-Trixie.html</link>
            <category>Debian</category>
    
    <comments>https://daniel-lange.com/archives/192-Make-apt-shut-up-about-modernize-sources-in-Trixie.html#comments</comments>
    <wfw:comment>https://daniel-lange.com/wfwcomment.php?cid=192</wfw:comment>

    <slash:comments>5</slash:comments>
    <wfw:commentRss>https://daniel-lange.com/rss.php?version=2.0&amp;type=comments&amp;cid=192</wfw:commentRss>
    

    <author>nospam@example.com (Daniel Lange)</author>
    <content:encoded>
    &lt;p&gt;Apt in Trixie (Debian 13) has the annoying function to tell you
&lt;em&gt;&quot;&lt;strong&gt;Notice&lt;/strong&gt;: Some sources can be modernized. Run &#039;apt modernize-sources&#039; to do so.&quot;&lt;/em&gt; ... every single time you run &lt;code&gt;apt update&lt;/code&gt;. Not cool for logs and log monitoring.&lt;/p&gt;

&lt;p&gt;And - of course - if you had the option to do this, you ... would have run the indicated &lt;code&gt;apt modernize-sources&lt;/code&gt; command to convert your &lt;code&gt;sources.list&lt;/code&gt; to &quot;deb822 .sources format&quot; files already. So an information message once or twice would have done.&lt;/p&gt;

&lt;p&gt;Well, luckily you can help yourself:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;apt -o APT::Get::Update::SourceListWarnings=false&lt;/code&gt; will keep &lt;code&gt;apt&lt;/code&gt; shut up. This could go into an &lt;code&gt;alias&lt;/code&gt; or your systems management tool / update script.&lt;/p&gt;

&lt;p&gt;Alternatively add&lt;/p&gt;

&lt;pre&gt;
# Keep apt shut about preferring the &quot;deb822&quot; sources file format
APT::Get::Update::SourceListWarnings &quot;false&quot;;
&lt;/pre&gt;

&lt;p&gt;to &lt;code&gt;/etc/apt/apt.conf.d/10quellsourceformatwarnings&lt;/code&gt; .&lt;/p&gt;

&lt;p&gt;This silences the notices about sources file formats (not only the deb822 one) system-wide.
That way you can decide when you can / want to migrate to the new, more verbose, apt sources format yourself.&lt;/p&gt;

&lt;h3&gt;Update 06.06.2025&lt;/h3&gt;

&lt;p&gt;I looks like the powers that are have had mercy, apt 3.0.2 has &lt;a href=&quot;https://tracker.debian.org/news/1648026/apt-302-migrated-to-testing/&quot;&gt;migrated to Trixie two days ago&lt;/a&gt; and the &lt;a href=&quot;https://tracker.debian.org/news/1647058/accepted-apt-302-source-into-unstable/&quot;&gt;Changelog&lt;/a&gt; contains:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;Downgrade &quot;modernize-sources&quot; notice to audit&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;!-- s9ymdb:729 --&gt;&lt;img class=&quot;plain-images&quot; width=&quot;128&quot; height=&quot;128&quot;  src=&quot;https://daniel-lange.com/uploads/icons/emoji/hug.png&quot;  loading=&quot;lazy&quot; alt=&quot;Hug&quot; border=&quot;0&quot;&gt;&lt;/p&gt;
 
    </content:encoded>

    <pubDate>Sat, 03 May 2025 12:22:00 +0000</pubDate>
    <guid isPermaLink="false">https://daniel-lange.com/archives/192-guid.html</guid>
    <category>annoying</category>
<category>apt</category>
<category>debian</category>
<category>trixie</category>
<category>ubuntu</category>
<category>updated</category>

</item>

</channel>
</rss>
