[Bug 2079039] [NEW] Signature link changed

2024-09-05 Thread Georg Pelz
Public bug reported: We work in workspace with changing pcs. (home folders are in the network) We migrated from Ubuntu 22.04 LTS Desktop to Ubuntu 24.04.1 LTS Desktop. We use thunderbird 128.1.0esr-1 through snap. Our signature all lie on an nfs mount (/var/nfs/oeffentlich/emailsignaturen/) (fstab

[Bug 2061981] Re: chromium fails to start with non-standard home directory

2024-07-22 Thread Georg Pelz
Thanks for the suggestion, but the workaround: > snap disconnect chromium:dot-local-share-applications > snap disconnect chromium:dot-local-share-icons does not work here. Starting chromium I get: Jul 22 12:18:28 pc063 chromium_chromium.desktop[4469]: [4469:4469:0722/121828.188355:ERROR:process_s

[Bug 2061981] Re: chromium fails to start with non-standard home directory

2024-06-13 Thread Georg Pelz
Just noticed: starting Chromium through /snap/chromium/current/usr/lib/chromium-browser/chrome works, but I'm not sure whether any of the restrictions still work when doing this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://

[Bug 2061981] Re: chromium fails to start with non-standard home directory

2024-06-12 Thread Georg Pelz
using Ubuntu 22.04 with snapd 2.63 21759 (stable) and also with latest edge 'latest/edge: 2.63+git266.g20cde6b 2024-06-11 (22109)', I still get: Jun 13 06:18:38 pc063 chromium_chromium.desktop[3970]: cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-sna

[Bug 1932297] Re: 8:6.9.7.4+dfsg-16ubuntu6.11 break pcx 1bit creation

2021-06-22 Thread Georg Pelz
I found a workaround by using an intermediate file which works with 20.04 and on my 18.04 system. first crop&co, but output to .gif using: convert -crop 1200x800+1+1 +repage -rotate 180 -crop +2+1 +repage -rotate -90 -bordercolor white -border 1x1 -resize 1200 upsversandauftrag_etikett_1848655-1

[Bug 1932297] Re: 8:6.9.7.4+dfsg-16ubuntu6.11 break pcx 1bit creation

2021-06-21 Thread Georg Pelz
Okay, I tried it on another 18.04 system and there the calls work properly. When running the calls on my desktop system (20.04) I get: $ dpkg -l | grep imagemagick ii imagemagick 8:6.9.10.23+dfsg-2.1ubuntu11.4 amd64image manipulation progra

[Bug 1932297] Re: 8:6.9.7.4+dfsg-16ubuntu6.11 break pcx 1bit creation

2021-06-18 Thread Georg Pelz
send you an email with the gif I used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932297 Title: 8:6.9.7.4+dfsg-16ubuntu6.11 break pcx 1bit creation To manage notifications about this bug go to:

[Bug 1932297] Re: 8:6.9.7.4+dfsg-16ubuntu6.11 break pcx 1bit creation

2021-06-17 Thread Georg Pelz
this also happen on Ubuntu 20.04.2, so my guess is that this is something that was introduced after ubuntu6.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932297 Title: 8:6.9.7.4+dfsg-16ubuntu6.11

[Bug 1932297] Re: 8:6.9.7.4+dfsg-16ubuntu6.11 break pcx 1bit creation

2021-06-17 Thread Georg Pelz
** Attachment added: "identify againt output created with 6.11" https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1932297/+attachment/5505258/+files/identify_6.11.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https:/

[Bug 1932297] [NEW] 8:6.9.7.4+dfsg-16ubuntu6.11 break pcx 1bit creation

2021-06-17 Thread Georg Pelz
Public bug reported: Today 8:6.9.7.4+dfsg-16ubuntu6.11 got installed on my server 18.04 server. --- Start-Date: 2021-06-17 06:26:11 Commandline: /usr/bin/unattended-upgrade Upgrade: imagemagick:amd64 (8:6.9.7.4+dfsg-16ubuntu6.9, 8:6.9.7.4+dfsg-16ubuntu6.11) End-Date: 2021-06-17 06:26:14 Star