Bug#1071372: [solved] emacs: it hangs saving .gpg files (without using cpu)

[Alex Andreotti]

gnupg2 (2.2.43-7) has arrived in unstable and gpg has started working
again, as far as I'm concerned this report can be closed, thanks.

Avoid breakage with epg.el (Closes: #1071552)

Bug#1071372: emacs: it hangs saving .gpg files (without using cpu)

[Alex Andreotti]

Package: emacs
Version: 1:29.3+1-3
Severity: normal
X-Debbugs-Cc: alex.andreo...@gmail.com

Dear Maintainer,

   * What led up to the situation?

For years I have normally used emacs (GUI) to create gpg files (.org.gpg or 
.md.gpg) where I save relatively sensitive information using a key installed in 
the system (with password). Last week when I created a file and saved it, emacs 
asked me to mark the key to use, and when I pressed OK to save the file it 
hung. Probably a "recent" apt upgrade broke it but I don't know exactly which 
one, before this problem I used to save .gpg files often

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I tried the cli version with emacsclient and tried launching the GUI version 
with -Q, but the problem persists. I tried stopping it with ^C and it break out 
but often the file isn't created, with an existing file it made it invalid.

   * What was the outcome of this action?

When saving .gpg files it hangs and I've to terminate emacs

   * What outcome did you expect instead?

I've been opening/editing/saving .gpg files for years without any problems and 
they save in a second.




-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs depends on:
ii  emacs-gtk  1:29.3+1-3

emacs recommends no packages.

emacs suggests no packages.

-- no debconf information

Bug#989828: minidlna: thread or subprocess segfault on select_del

[Alex Andreotti]

Package: minidlna
Version: 1.3.0+dfsg-2.2
Followup-For: Bug #989828
X-Debbugs-Cc: alex.andreo...@gmail.com

Dear Maintainer,

Attached a backtrace and a patch that fixes the segv, but I don't know if it's 
the right way, there might be some leak or other side effects.

The problem persists and I found some time to investigate.
I use a dlna application with Android that launches another player application, 
it may be that one of these two does not fully comply with the standard (even 
if I use the same apps with a Synology nas and they have no problems).

Looks like the select_fini is called, events (in select.c) is set to NULL, and 
then a select_del arrives. I'll try to investigate if this is the case.

At the moment I don't know if it's only a package problem or also an upstream 
problem, it seems to me that there is some patch applied to select.c but I 
haven't looked at what they change.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages minidlna depends on:
ii  adduser3.129
ii  init-system-helpers1.65.2
ii  libavformat59  7:5.1.2-1
ii  libavutil577:5.1.2-1
ii  libc6  2.36-6
ii  libexif12  0.6.24-1+b1
ii  libflac12  1.4.2+ds-2
ii  libid3tag0 0.15.1b-14
ii  libjpeg62-turbo1:2.1.2-1+b1
ii  libogg01.3.5-3
ii  libsqlite3-0   3.40.0-1
ii  libvorbis0a1.3.7-1
ii  lsb-base   11.5
ii  sysvinit-utils [lsb-base]  3.05-7

minidlna recommends no packages.

minidlna suggests no packages.

-- no debconf information
Core was generated by `/sbin/minidlnad -f ./minidlna.conf -R'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
(gdb) bt
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x7f94740b8d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x7f9474069ef2 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#3  0x7f9474054472 in __GI_abort () at ./stdlib/abort.c:79
#4  0x7f9474054395 in __assert_fail_base (fmt=0x7f94741c8a70 "%s%s%s:%u: 
%s%sAssertion `%s' failed.\n%n", assertion=0x5643b46bc302 "events != NULL", 
file=0x5643b46bc2d0 "select.c", line=135, function=)
at ./assert/assert.c:92
#5  0x7f9474062df2 in __GI___assert_fail (assertion=0x5643b46bc302 "events 
!= NULL", file=0x5643b46bc2d0 "select.c", line=135, function=0x5643b46bc358 
<__PRETTY_FUNCTION__.0> "select_del") at ./assert/assert.c:101
#6  0x5643b46abba8 in select_del (ev=0x5643b6381240, flags=1) at 
./select.c:135
#7  0x5643b46773af in CloseSocket_upnphttp (h=0x5643b6381240) at 
./upnphttp.c:126
#8  0x5643b467d8e6 in SendResp_dlnafile (h=0x5643b6381240, 
object=0x7ffcfd003f9c "40.mp4") at ./upnphttp.c:2099
#9  0x5643b4679f94 in ProcessHttpQuery_upnphttp (h=0x5643b6381240) at 
./upnphttp.c:1001
#10 0x5643b467a594 in Process_upnphttp (ev=0x5643b6381240) at 
./upnphttp.c:1131
#11 0x5643b46ac02f in select_process (msec=1755462) at ./select.c:185
#12 0x5643b4676d5f in main (argc=4, argv=0x7ffcfd004c78) at 
./minidlna.c:1287

--- minidlna-1.3.0+dfsg.orig/select.c
+++ minidlna-1.3.0+dfsg/select.c
@@ -132,9 +132,14 @@ select_del(struct event *ev, int flags)
if (ev->index < --nevents) {
struct event *ev0;
 
-   ev0 = events[nevents];
-   events[ev->index] = ev0;
-   ev0->index = ev->index;
+   // assert(events != NULL);
+   if (events != NULL) {
+   assert(nevents >= 0);
+   ev0 = events[nevents];
+   assert(ev->index >= 0);
+   events[ev->index] = ev0;
+   ev0->index = ev->index;
+   }
}
ev->index = -1;

Bug#1017414: firefox: it works but firefox.real segfault at every launch (vaapi related?)

[Alex Andreotti]

Package: firefox
Version: 103.0.2-2
Severity: normal
X-Debbugs-Cc: alex.andreo...@gmail.com

Dear Maintainer,

  * What led up to the situation?

I keep journalctl running in one of my terminals and noticed that (from some 
time now) every time I run FF it does segfault.
>From the output messages seems to be VAAPI related but I'm not sure, logs 
>attached.


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.7-0.3
ii  fontconfig   2.13.1-4.4
ii  libasound2   1.2.7.2-1
ii  libatk1.0-0  2.38.0-1
ii  libc62.34-3
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libdbus-1-3  1.14.0-2
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.2-4
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.1.0-8
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-2
ii  libglib2.0-0 2.72.3-1+b1
ii  libgtk-3-0   3.24.34-1
ii  libnspr4 2:4.34-1
ii  libnss3  2:3.81-2
ii  libpango-1.0-0   1.50.9+ds-1
ii  libstdc++6   12.1.0-8
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.1-2
ii  libx11-xcb1  2:1.8.1-2
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:6.0.0-1
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:3.3.17-7+b1
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages firefox recommends:
ii  libavcodec-extra57 7:3.4.3-1
ii  libavcodec-extra58 [libavcodec58]  7:4.4.2-1+b3
ii  libavcodec-extra59 [libavcodec59]  7:5.1-2+b1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.005-1
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20-1
ii  pulseaudio 15.0+dfsg1-4+b1

-- no debconf information
Application Basics
--

Name: Firefox
Version: 103.0.2
Build ID: 20220808125904
Distribution ID:
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 
Firefox/103.0
OS: Linux 5.18.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.16-1 (2022-08-10)
OS Theme: Adwaita / Adwaita
Multiprocess Windows: 1/1
Fission Windows: 1/1 Enabled by default
Remote Processes: 7
Enterprise Policies: Inactive
Google Location Service Key: Found
Google Safebrowsing Key: Found
Mozilla Location Service Key: Found
Safe Mode: false
Memory Size (RAM): 31.3 GB
Disk Space Available: 13.4 GB

Crash Reports for the Last 3 Days
-

Firefox Features


Name: DoH Roll-Out
Version: 2.0.0
ID: doh-roll...@mozilla.org

Name: Firefox Screenshots
Version: 39.0.1
ID: screensh...@mozilla.org

Name: Form Autofill
Version: 1.0.1
ID: formautof...@mozilla.org

Name: Picture-In-Picture
Version: 1.0.0
ID: pictureinpict...@mozilla.org

Name: Web Compatibility Interventions
Version: 103.0.0
ID: webcom...@mozilla.org

Name: WebCompat Reporter
Version: 1.5.0
ID: webcompat-repor...@mozilla.org

Remote Features
---

bug-1766618-rollout-disable-websocket-over-http2-release-91-100: active

Remote Processes


Type: Privileged About
Count: 1

Type: Extension
Count: 1

Type: Isolated Web Content
Count: 1

Type: Preallocated
Count: 3

Type: Socket
Count: 1

Add-ons
---

Name: Add-ons Search Detection
Type: extension
Version: 2.0.0
Enabled: true
ID: addons-search-detect...@mozilla.com

Name: Amazon.co.uk
Type: extension
Version: 1.9
Enabled: true
ID: ama...@search.mozilla.org

Name: Bing
Type: extension
Version: 1.3
Enabled: true
ID: b...@search.mozilla.org

Name: DuckDuckGo
Type: extension
Version: 1.1
Enabled: true
ID: d...@search.mozilla.org

Name: Ghostery – Privacy Ad Blocker
Type: extension
Version: 8.7.6
Enabled: true
ID: fire...@ghostery.com

Name: Google
Type: extension
Version: 1.2
Enabled: true
ID: goo...@search.mozilla.org

Name: uBlock Origin
Type: extension
Version: 1.43.0
Enabled: true
ID: ublo...@raymondhill.net

Name: Video DownloadHelper
Type: extension
Version: 7.6.0
Enabled: true
ID: {b9db16a4-6edc-47ec-a1f4-b86292ed211d}

Name: Wikipedia (en)
Type: extension
Version: 1.1
Enabled: true
ID: wikipe...@search.mozilla.org

Graphics


Features
Compositing: WebRender

Bug#996668: cinnamon-settings-daemon: cinnamon shutdown hang

[Alex Andreotti]

On Thu, Nov 18, 2021 at 11:16:25AM +0100, Fabio Fantoni wrote:

[cut]

> Thanks for logs, I only did a very fast look (sorry but I don't have much
> time) and I notice 2 things:
> 
> - "Nov 17 17:06:40 hellspawn cinnamon-session[1747]: WARNING: t+0.06097s:
> Failed to start app: Unable to start application: Failed to execute child
> process “gsettings-data-convert” (No such file or directory)" at start of
> session (that fail to terminate on shutdown until kill for timeout). On my
> testing system I have gconf2 installed (that contain
> gsettings-data-convert), if you want do a fast test do install it, reboot
> and after retry (as is started on session start) but I'm don't know is the
> cause of unexpected case on shutdown
> 
> - "Nov 17 17:07:11 hellspawn systemd[1]: nfs-blkmap.service: Failed with
> result 'exit-code'."   before "Nov 17 17:08:41 hellspawn systemd[1]:
> session-2.scope: Stopping timed out. Killing." I don't have have that
> service on my testing system (I don't use nfs), you use nfs for one or more
> remote filesystem? but also in that case I don't know if can be the cause of
> unexpected case on shutdown
> 

Thanks Fabio,

the problem seems to be gone, it's not clear to me why, I didn't see a
direct effect installing gconf2 and uninstalling nfs-kernel-sever, but
after a series of other operations and several reboots it is now gone.

- I tried to install gconf2 and reboot 2 times, the problem remained.
- I tried to remove nfs-kernel-server + autoremove and reboot 2 times,
  the problem remained.
- I tried to enable avahi-daemon.{socket,service} and reboot 2 times
  and the problem remained (later I stopped them, disabled + mask).
- I tried to use an alternate user that I created some time ago but that
  I rarely used and log in with Cinnamon and I noticed that the new user 
  did not have the problem, while the old user continued to have it.
- I installed lttng and eclipse-tracecompass to see if anything stood out 
  during a `systemctl stop session-2.scope`, but I didn't notice anything 
  special (for tracecompass I had to change alternatives for java
  oracle8 -> openjdk11).

Bug#996668: cinnamon-settings-daemon: cinnamon shutdown hang

[Alex Andreotti]

On Wed, Nov 17, 2021 at 05:52:07PM +0100, Fabio Fantoni wrote:
> Il 17/11/2021 17:19, Alex Andreotti ha scritto:
> > On Wed, Nov 17, 2021 at 04:20:53PM +0100, Fabio Fantoni wrote:
> > > Il 17/11/2021 16:01, Alex Andreotti ha scritto:
> > > > On Sun, Nov 07, 2021 at 12:28:12PM +0100, Fabio Fantoni wrote:
> > > > > Il 05/11/2021 17:40, Alex Andreotti ha scritto:
> > > > > > On Sun, Oct 31, 2021 at 12:28:03PM +0100, Fabio Fantoni wrote:
> > > > > > > Il 31/10/2021 10:02, Alex Andreotti ha scritto:
> > > > > > > Sorry if I don't replied before, I'm unable to reproduce the 
> > > > > > > issue on my Sid
> > > > > > > environment, unfortunately recently I am also very busy and I am 
> > > > > > > used the
> > > > > > > little time to the tests instead on the big muffin rebase they 
> > > > > > > are doing
> > > > > > > upstream for cinnamon 5.2.
> > > > > > > 
> > > > > > > As soon as I have time in these days I will try to prepare the 
> > > > > > > new build
> > > > > > > with latest upstream bugfixes to upload and doing more tests.
> > > > > > > 
> > > > > > > About your environments you had some applet,extension, desklet 
> > > > > > > added (not
> > > > > > > installed by default) and enabled? if yes can you try to disable 
> > > > > > > them, and
> > > > > > > after reboot the shutdown still have the same issue? without 
> > > > > > > being able to
> > > > > > > reproduce the problem unfortunately I can not try to debug to try 
> > > > > > > to see
> > > > > > > what it cause freeze/hang the cinnamon process on shutdown.
> > > > > > > 
> > > > > > Sorry for the late reply too, my gmail occasionally flags Debian
> > > > > > emails as spam ... I just happened to see it today.
> > > > > > 
> > > > > > I don't have custom applets, I just added a couple of auto starts, I
> > > > > > tried to disable them but nothing changes.
> > > > > > 
> > > > > > It's not a big deal, I don't reboot often, it's just a little 
> > > > > > annoying
> > > > > > because when I do it's because I need it.
> > > > > > 
> > > > > > It would be useful to have a more precise message, I can try to 
> > > > > > take a
> > > > > > look, if you have suggestions where to look are welcome.
> > > > > > 
> > > > > > Thanks for the work you do.
> > > > > Thanks for reply, yesterday I did other tests on Sid testing new 
> > > > > bugfix
> > > > > builds for future upload but I'm still unable to reproduce it. From a 
> > > > > fast
> > > > > search on upstream issues I don't found a similar reports.
> > > > I noticed by chance (this is the second time this has happened to me)
> > > > that the problem does not appear if I have just performed `apt
> > > > upgrade` and then reboot in the usual way (from the Cinnamon menu).
> > > Thanks for reply, so the latest update of one of these components 
> > > (cinnamon,
> > > nemo, cinnamon-screensaver, xapp, muffin and cinnamon-session) seems 
> > > solved
> > > it, can you confirm after other try if still unreproducible please?
> > > 
> > > If someone still reproduce it on updated Sid (or testing after migration 
> > > of
> > > updated components above) please reply or if nobody will reproduce it
> > > anymore I'll close this after 1-2 weeks
> > No, I'm sorry, I tried to summarize but obviously I was not clear.
> > 
> > The problem persists, even after the system upgrade I did today.
> > 
> > But the reboot of the session where I ran `apt upgrade` wasn't
> > affected, I don't know if the upgrade process ends or restart
> > cinnamon-launcher or what else.  In today's upgrade I noticed there
> > were cinnamon packagess, I don't remember if there were any the first
> > time I noticed it, I'll try to pay attention next time.
> 
> Sorry if I didn't understand right, since I'm unable to reproduce it is
> difficult found the cause of issue and try to solves it.
> 
> Can you try to check syslog and kern.log and see if there is any crash (for
> 

Bug#996668: cinnamon-settings-daemon: cinnamon shutdown hang

[Alex Andreotti]

On Wed, Nov 17, 2021 at 04:20:53PM +0100, Fabio Fantoni wrote:
> Il 17/11/2021 16:01, Alex Andreotti ha scritto:
> > On Sun, Nov 07, 2021 at 12:28:12PM +0100, Fabio Fantoni wrote:
> > > Il 05/11/2021 17:40, Alex Andreotti ha scritto:
> > > > On Sun, Oct 31, 2021 at 12:28:03PM +0100, Fabio Fantoni wrote:
> > > > > Il 31/10/2021 10:02, Alex Andreotti ha scritto:
> > > > > Sorry if I don't replied before, I'm unable to reproduce the issue on 
> > > > > my Sid
> > > > > environment, unfortunately recently I am also very busy and I am used 
> > > > > the
> > > > > little time to the tests instead on the big muffin rebase they are 
> > > > > doing
> > > > > upstream for cinnamon 5.2.
> > > > > 
> > > > > As soon as I have time in these days I will try to prepare the new 
> > > > > build
> > > > > with latest upstream bugfixes to upload and doing more tests.
> > > > > 
> > > > > About your environments you had some applet,extension, desklet added 
> > > > > (not
> > > > > installed by default) and enabled? if yes can you try to disable 
> > > > > them, and
> > > > > after reboot the shutdown still have the same issue? without being 
> > > > > able to
> > > > > reproduce the problem unfortunately I can not try to debug to try to 
> > > > > see
> > > > > what it cause freeze/hang the cinnamon process on shutdown.
> > > > > 
> > > > Sorry for the late reply too, my gmail occasionally flags Debian
> > > > emails as spam ... I just happened to see it today.
> > > > 
> > > > I don't have custom applets, I just added a couple of auto starts, I
> > > > tried to disable them but nothing changes.
> > > > 
> > > > It's not a big deal, I don't reboot often, it's just a little annoying
> > > > because when I do it's because I need it.
> > > > 
> > > > It would be useful to have a more precise message, I can try to take a
> > > > look, if you have suggestions where to look are welcome.
> > > > 
> > > > Thanks for the work you do.
> > > Thanks for reply, yesterday I did other tests on Sid testing new bugfix
> > > builds for future upload but I'm still unable to reproduce it. From a fast
> > > search on upstream issues I don't found a similar reports.
> > I noticed by chance (this is the second time this has happened to me)
> > that the problem does not appear if I have just performed `apt
> > upgrade` and then reboot in the usual way (from the Cinnamon menu).
> 
> Thanks for reply, so the latest update of one of these components (cinnamon,
> nemo, cinnamon-screensaver, xapp, muffin and cinnamon-session) seems solved
> it, can you confirm after other try if still unreproducible please?
> 
> If someone still reproduce it on updated Sid (or testing after migration of
> updated components above) please reply or if nobody will reproduce it
> anymore I'll close this after 1-2 weeks

No, I'm sorry, I tried to summarize but obviously I was not clear.

The problem persists, even after the system upgrade I did today.

But the reboot of the session where I ran `apt upgrade` wasn't
affected, I don't know if the upgrade process ends or restart
cinnamon-launcher or what else.  In today's upgrade I noticed there
were cinnamon packagess, I don't remember if there were any the first
time I noticed it, I'll try to pay attention next time.

> > 
> > > @Joshua: Have you reproduced it or saw others users report of it with more
> > > informations that can help to reproduce it or found the cause?
> 
> 

Bug#996668: cinnamon-settings-daemon: cinnamon shutdown hang

[Alex Andreotti]

On Sun, Nov 07, 2021 at 12:28:12PM +0100, Fabio Fantoni wrote:
> Il 05/11/2021 17:40, Alex Andreotti ha scritto:
> > On Sun, Oct 31, 2021 at 12:28:03PM +0100, Fabio Fantoni wrote:
> > > Il 31/10/2021 10:02, Alex Andreotti ha scritto:
> > > Sorry if I don't replied before, I'm unable to reproduce the issue on my 
> > > Sid
> > > environment, unfortunately recently I am also very busy and I am used the
> > > little time to the tests instead on the big muffin rebase they are doing
> > > upstream for cinnamon 5.2.
> > > 
> > > As soon as I have time in these days I will try to prepare the new build
> > > with latest upstream bugfixes to upload and doing more tests.
> > > 
> > > About your environments you had some applet,extension, desklet added (not
> > > installed by default) and enabled? if yes can you try to disable them, and
> > > after reboot the shutdown still have the same issue? without being able to
> > > reproduce the problem unfortunately I can not try to debug to try to see
> > > what it cause freeze/hang the cinnamon process on shutdown.
> > > 
> > Sorry for the late reply too, my gmail occasionally flags Debian
> > emails as spam ... I just happened to see it today.
> > 
> > I don't have custom applets, I just added a couple of auto starts, I
> > tried to disable them but nothing changes.
> > 
> > It's not a big deal, I don't reboot often, it's just a little annoying
> > because when I do it's because I need it.
> > 
> > It would be useful to have a more precise message, I can try to take a
> > look, if you have suggestions where to look are welcome.
> > 
> > Thanks for the work you do.
> 
> Thanks for reply, yesterday I did other tests on Sid testing new bugfix
> builds for future upload but I'm still unable to reproduce it. From a fast
> search on upstream issues I don't found a similar reports.

I noticed by chance (this is the second time this has happened to me)
that the problem does not appear if I have just performed `apt
upgrade` and then reboot in the usual way (from the Cinnamon menu).

> @Joshua: Have you reproduced it or saw others users report of it with more
> informations that can help to reproduce it or found the cause?

Bug#996668: cinnamon-settings-daemon: cinnamon shutdown hang

[Alex Andreotti]

On Sun, Oct 31, 2021 at 12:28:03PM +0100, Fabio Fantoni wrote:
> Il 31/10/2021 10:02, Alex Andreotti ha scritto:

> Sorry if I don't replied before, I'm unable to reproduce the issue on my Sid
> environment, unfortunately recently I am also very busy and I am used the
> little time to the tests instead on the big muffin rebase they are doing
> upstream for cinnamon 5.2.
> 
> As soon as I have time in these days I will try to prepare the new build
> with latest upstream bugfixes to upload and doing more tests.
> 
> About your environments you had some applet,extension, desklet added (not
> installed by default) and enabled? if yes can you try to disable them, and
> after reboot the shutdown still have the same issue? without being able to
> reproduce the problem unfortunately I can not try to debug to try to see
> what it cause freeze/hang the cinnamon process on shutdown.
> 

Sorry for the late reply too, my gmail occasionally flags Debian
emails as spam ... I just happened to see it today.

I don't have custom applets, I just added a couple of auto starts, I
tried to disable them but nothing changes.

It's not a big deal, I don't reboot often, it's just a little annoying
because when I do it's because I need it.

It would be useful to have a more precise message, I can try to take a
look, if you have suggestions where to look are welcome.

Thanks for the work you do.

Bug#996668: cinnamon-settings-daemon: cinnamon shutdown hang

[Alex Andreotti]

Package: cinnamon-settings-daemon
Version: 5.0.4-2
Followup-For: Bug #996668
X-Debbugs-Cc: alex.andreo...@gmail.com

Dear Maintainer,

I have the same problem, everytime I reboot or shut down session-2.scope it 
hangs for 1m30s, cinnamon-launcher seems to be the problem, killing it as 
suggested the system shuts down without hanging.


Oct 31 09:03:50 hellspawn systemd[1]: Stopped ACPI event daemon.
Oct 31 09:05:19 hellspawn systemd[1]: session-2.scope: Stopping timed out. 
Killing.
Oct 31 09:05:19 hellspawn systemd[1]: session-2.scope: Killing process 9852 
(cinnamon-launch) with signal SIGKILL.
Oct 31 09:05:19 hellspawn gpg-agent[2486]: SIGTERM received - shutting down ...
Oct 31 09:05:19 hellspawn gpg-agent[2486]: gpg-agent (GnuPG) 2.2.27 stopped
Oct 31 09:05:19 hellspawn systemd[1]: session-2.scope: Killing process 9971 
(gmain) with signal SIGKILL.
Oct 31 09:05:19 hellspawn systemd[1]: session-2.scope: Failed with result 
'timeout'.
Oct 31 09:05:19 hellspawn systemd[1]: Stopped Session 2 of User alex.
Oct 31 09:05:19 hellspawn systemd[1]: session-2.scope: Consumed 3min 17.513s 
CPU time.
Oct 31 09:05:19 hellspawn systemd[1]: Stopping User Login Management...
Oct 31 09:05:19 hellspawn systemd[1]: Stopping User Manager for UID 1000...
Oct 31 09:05:19 hellspawn systemd[1776]: Stopped target Main User Target.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cinnamon-settings-daemon depends on:
ii  cinnamon-desktop-data5.0.0-2
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-2
ii  gir1.2-cvc-1.0   5.0.0-2
ii  libc62.32-4
ii  libcairo21.16.0-5
ii  libcanberra-gtk3-0   0.30-8
ii  libcanberra0 0.30-8
ii  libcinnamon-desktop4 5.0.0-2
ii  libcolord2   1.4.5-3
ii  libcups2 2.3.3op2-7
ii  libcvc0  5.0.0-2
ii  libdbus-glib-1-2 0.112-2
ii  libfontconfig1   2.13.1-4.2
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.0-3
ii  libgnomekbd8 3.26.1-1+b1
ii  libgtk-3-0   3.24.30-3
ii  libgudev-1.0-0   237-2
ii  liblcms2-2   2.12~rc1-2
ii  libnotify4   0.7.9-3
ii  libnspr4 2:4.32-1
ii  libnss3  2:3.70-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libpolkit-gobject-1-00.105-31
ii  libpulse015.0+dfsg1-2
ii  librsvg2-2   2.50.7+dfsg-2
ii  libsystemd0  249.5-1
ii  libupower-glib3  0.99.13-1
ii  libwacom21.12-1
ii  libx11-6 2:1.7.2-2+b1
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxi6   2:1.8-1
ii  libxklavier165.4-4
ii  libxtst6 2:1.2.3-1
ii  python3-tinycss  0.4-3+b4

Versions of packages cinnamon-settings-daemon recommends:
ii  cinnamon-l10n  5.0.2-2
ii  pulseaudio 15.0+dfsg1-2

Versions of packages cinnamon-settings-daemon suggests:
ii  cinnamon [x-window-manager]5.0.5-2
ii  cinnamon-screensaver   5.0.6-2
ii  flwm [x-window-manager]1.02+git2015.10.03+7dbb30-7
pn  gnome-calculator | galculator | mate-calc  
ii  gnome-power-manager3.32.0-2
ii  gnome-screenshot   40.0-1
ii  muffin [x-window-manager]  5.0.1-2
ii  openbox [x-window-manager] 3.6.1-9+deb11u1
pn  tracker-gui | gnome-search-tool
ii  x11-xserver-utils  7.7+9

-- no debconf information

Bug#989828: minidlna: thread or subprocess segfault on select_del

[Alex Andreotti]

Package: minidlna
Version: 1.3.0+dfsg-2
Severity: normal
X-Debbugs-Cc: alex.andreo...@gmail.com

Dear Maintainer,

   * What led up to the situation?

Since there was a major update of minidlnad months ago, segfault/coredump 
started appearing in the journal log. For reference, the update in question 
changed minidlnad's cli options, I use it from the command line and used 
options for verbose debugging, and they stopped working with that update 
(minidlnad works, but there is no longer the debug output).
Sorry if I report the bug only now, but it seemed random, and by the way, the 
application continues to work, it would seem that it is just a thread or a 
subprocess that crashes. Now I believe the bug shows up when videos are closed.

   * 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 ***


-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages minidlna depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libavformat587:4.3.2-0+deb11u2
ii  libavutil56  7:4.3.2-0+deb11u2
ii  libc62.31-12
ii  libexif120.6.22-3
ii  libflac8 1.3.3-2
ii  libid3tag0   0.15.1b-14
ii  libjpeg62-turbo  1:2.0.6-4
ii  libogg0  1.3.4-0.1
ii  libsqlite3-0 3.34.1-3
ii  libvorbis0a  1.3.7-1
ii  lsb-base 11.1.0

minidlna recommends no packages.

minidlna suggests no packages.

-- no debconf information
#0  0x5652d9547697 in select_del (ev=0x5652d9acf320, flags=) 
at select.c:135
#1  0x5652d952200f in CloseSocket_upnphttp (h=h@entry=0x5652d9acf320) at 
upnphttp.c:126
#2  0x5652d95242d4 in SendResp_dlnafile (object=0x7ffccbb779bc "33.mp4", 
h=0x5652d9acf320) at upnphttp.c:2082
#3  ProcessHttpQuery_upnphttp (h=h@entry=0x5652d9acf320) at upnphttp.c:984
#4  0x5652d9525c0d in Process_upnphttp (ev=) at 
upnphttp.c:1114
#5  0x5652d954750e in select_process (msec=) at select.c:186
#6  0x5652d951e464 in main (argc=, argv=) at 
minidlna.c:1287

Bug#983242: wine-development recent upgrade (5.6-1?) broke levelator.exe

[Alex Andreotti]

On Mon, Feb 22, 2021 at 11:00:32AM +0100, Berillions wrote:
> Are you sure that it’s a Debian bug ?
> Check the output console to see if it’s not an upstream bug instead of.

I tagged the bug as upstream, perhaps it is.

Bug#983242: wine-development recent upgrade (5.6-1?) broke levelator.exe

[Alex Andreotti]

On Mon, Feb 22, 2021 at 02:28:12AM +0100, Antoine Le Gonidec wrote:
> On Sun, 21 Feb 2021 14:22:19 +0100 Alex Andreotti  
> wrote:
> > I been using a script to level wav files for more than a year without 
> > problems, until few day ago, I guess it was the upgrade to version 5.6-1 
> > but I'm not sure
> 
> In bug #983117 there is a series of commands showing how to downgrade to 
> wine-development 5.5-9:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983117#5
> 
> Following it would allow you to check is your issue happens with 5.5-9 too, 
> or if actually started happening with 5.6-1.
> 
> Here is a copy for convenience (all commands as root):
> 
> cat > /etc/apt/sources.list.d/snapshot-20201026T024334Z.list << EOF
> # wine-development 5.5-9
> # cf. https://snapshot.debian.org/package/wine-development/5.5-9/
> deb [check-valid-until=no] 
> https://snapshot.debian.org/archive/debian/20201026T024334Z/ sid main
> EOF
> apt update
> apt install 
> {libwine-development:{amd64,i386},wine32-development:i386,wine64-development,wine-development}=5.5-9
> 

Thanks, I confirm that downgrading to 5.5-9 the problem does not exist, I had 
already switched to the non -development version which does not have the issue.

Let me know if I can help.

Bug#983242: wine-development recent upgrade (5.6-1?) broke levelator.exe

[Alex Andreotti]

Package: wine-development
Version: 5.6-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: alex.andreo...@gmail.com

Dear Maintainer,

   * What led up to the situation?

I been using a script to level wav files for more than a year without problems, 
until few day ago, I guess it was the upgrade to version 5.6-1 but I'm not sure

WINEPATH="$(winepath-development --windows "$TMPWAV")"
wine64-development "$HOME/.wine/drive_c/progs/Levelator/levelator.exe" 
"$WINEPATH"

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

A system upgrade with `apt upgrade`

   * What was the outcome of this action?

When I run the script levelator shows a MessageBox with an error (can't open 
file...)

   * What outcome did you expect instead?

I expect levelator to process the audio file



-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wine-development depends on:
ii  wine32-development  5.6-1
ii  wine64-development  5.6-1

wine-development recommends no packages.

Versions of packages wine-development suggests:
pn  dosbox
pn  exe-thumbnailer | kio-extras  
pn  playonlinux   
pn  q4wine
pn  winbind   
pn  wine-binfmt   
ii  winetricks0.0+20210206-1

Versions of packages libwine-development depends on:
ii  libasound2   1.2.4-1.1
ii  libc62.31-9
ii  libfaudio0   21.02-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.1-6
ii  libglib2.0-0 2.66.7-1
ii  libgphoto2-6 2.5.26-2
ii  libgphoto2-port122.5.26-2
ii  libgstreamer-plugins-base1.0-0   1.18.3-1
ii  libgstreamer1.0-01.18.3-1
ii  liblcms2-2   2.12~rc1-2
ii  libldap-2.4-22.4.57+dfsg-2
ii  libmpg123-0  1.26.4-1
ii  libncurses6  6.2+20201114-2
ii  libopenal1   1:1.19.1-2
ii  libpcap0.8   1.10.0-2
ii  libpulse014.2-1
ii  libtinfo66.2+20201114-2
ii  libudev1 247.3-1
ii  libunwind8   1.3.2-2
ii  libvkd3d11.1-5
ii  libx11-6 2:1.7.0-2
ii  libxext6 2:1.3.3-1.1
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libz-mingw-w64   1.2.11+dfsg-2
ii  ocl-icd-libopencl1 [libopencl1]  2.2.14-2

Versions of packages libwine-development recommends:
ii  fonts-liberation   1:1.07.4-11
ii  fonts-wine 5.0.3-3
ii  gstreamer1.0-plugins-good  1.18.3-1
ii  libasound2-plugins 1.2.2-2
ii  libgl1-mesa-dri20.3.4-1

Versions of packages libwine-development suggests:
ii  cups-bsd   2.3.3op2-3
ii  gstreamer1.0-libav 1.18.3-1
ii  gstreamer1.0-plugins-bad   1.18.3-1+b1
ii  gstreamer1.0-plugins-ugly  1.18.3-1
ii  ttf-mscorefonts-installer  3.8

Versions of packages wine32-development depends on:
ii  libc62.31-9
ii  libwine-development  5.6-1

wine32-development recommends no packages.

Versions of packages wine32-development suggests:
pn  wine32-development-preloader  

Versions of packages wine64-development depends on:
ii  libc62.31-9
ii  libwine-development  5.6-1

Versions of packages wine64-development recommends:
ii  wine32-development  5.6-1

Versions of packages wine64-development suggests:
pn  wine64-development-preloader  

Versions of packages wine-development is related to:
pn  dxvk 
pn  dxvk-wine32-development  
pn  dxvk-wine64-development  
ii  fonts-wine   5.0.3-3

-- no debconf information

Bug#963975: blender: Blender crashes on launch (failed assert)

[Alex Andreotti]

Package: blender
Version: 2.83.1+dfsg-1
Followup-For: Bug #963975

Dear Maintainer,

I have updated to 2.83.1 + dfsg-1 and have the same problem (I don't remember 
if I used 2.81 or 2.82 previously but it worked)

In my case, however, the fonts in question are not installed by blender-data, 
the fonts directory is missing, if I create it and copy the fonts blender does 
not work anyway, I guess we should run font config, if I copy the fonts in the 
configuration directory of blender, in the user's home, blender works.


dpkg -L blender-data|grep '\.ttf$'
/usr/share/locale/fonts/bmonofont-i18n.ttf
/usr/share/locale/fonts/droidsans.ttf


ls -l /usr/share/locale/fonts/bmonofont-i18n.ttf 
/usr/share/locale/fonts/droidsans.ttf
ls: cannot access '/usr/share/locale/fonts/bmonofont-i18n.ttf': No such file or 
directory
ls: cannot access '/usr/share/locale/fonts/droidsans.ttf': No such file or 
directory


cp blender-2.83.1-linux64/2.83/datafiles/fonts/bmonofont-i18n.ttf 
blender-2.83.1-linux64/2.83/datafiles/fonts/droidsans.ttf 
/home/alex/.config/blender/2.83/datafiles/fonts

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages blender depends on:
ii  blender-data   2.83.1+dfsg-1
ii  fonts-dejavu   2.37-2
ii  libavcodec-extra58 [libavcodec58]  7:4.3-2
ii  libavdevice58  7:4.3-2
ii  libavformat58  7:4.3-2
ii  libavutil567:4.3-2
ii  libboost-locale1.71.0  1.71.0-6+b2
ii  libc6  2.30-8
ii  libfftw3-double3   3.3.8-2
ii  libfreetype6   2.10.1-2
ii  libgcc-s1  10.1.0-4
ii  libgl1 1.3.1-1
ii  libglew2.1 2.1.0-4+b1
ii  libgomp1   10.1.0-4
ii  libilmbase24   2.3.0-6
ii  libjack-jackd2-0 [libjack-0.125]   1.9.12~dfsg-2+b1
ii  libjemalloc2   5.2.1-1
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libopenal1 1:1.19.1-1+b1
ii  libopencolorio1v5  1.1.1~dfsg0-6+b1
ii  libopenexr24   2.3.0-6
ii  libopenimageio2.1  2.1.16.0~dfsg0-1
ii  libopenjp2-7   2.3.1-1
ii  libopenvdb7.0  7.0.0-3+b1
ii  libosdcpu3.4.3 3.4.3-3
ii  libosdgpu3.4.3 3.4.3-3
ii  libpcre3   2:8.39-13
ii  libpng16-161.6.37-2
ii  libpython3.8   3.8.3-1
ii  libsdl2-2.0-0  2.0.12+dfsg1-1
ii  libsndfile11.0.28-8
ii  libspnav0  0.2.3-1+b2
ii  libstdc++6 10.1.0-4
ii  libswscale57:4.3-2
ii  libtbb22020.2-2
ii  libtiff5   4.1.0+git191117-2
ii  libx11-6   2:1.6.9-2+b1
ii  libxfixes3 1:5.0.3-2
ii  libxi6 2:1.7.10-1
ii  libxml22.9.10+dfsg-5+b1
ii  libxrender11:0.9.10-1
ii  libxxf86vm11:1.1.4-1+b2
ii  zlib1g 1:1.2.11.dfsg-2

blender recommends no packages.

blender suggests no packages.

-- no debconf information

Bug#958104: system-config-printer-udev: ABRT: free(): invalid pointer

[Alex Andreotti]

Backtrace attachment with related dbgsym installed.

Regards
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7f3de0cb055b in __GI_abort () at abort.c:79
#2  0x7f3de0d09008 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x7f3de0e15f3e "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x7f3de0d103aa in malloc_printerr (str=str@entry=0x7f3de0e140e0 
"free(): invalid pointer") at malloc.c:5339
#4  0x7f3de0d11d9c in _int_free (av=, p=, 
have_lock=0) at malloc.c:4173
#5  0x55904b38916f in for_each_matching_queue (flags=1, fn=0x55904b387c00 
, usblpdev=0x7fffde6ef5c8 "", 
usblpdevlen=, device_uris=, 
device_uris=, context=0x0) at udev/udev-configure-printer.c:1515
#6  0x55904b389f89 in do_add (cmd=0x7fffde6f0efa 
"/lib/udev/udev-configure-printer", devaddr=)
at udev/udev-configure-printer.c:1663
#7  0x55904b387724 in main (argc=3, argv=0x7fffde6f0c38) at 
udev/udev-configure-printer.c:1871

Bug#958104: system-config-printer-udev: ABRT: free(): invalid pointer

[Alex Andreotti]

Package: system-config-printer-udev
Version: 1.5.12-1
Followup-For: Bug #958104

Dear Maintainer,

in my case it's a strange bug, when I physically turn on the printer I see the 
segv and coredump in the logs, but then the printer works, system log attached.
Note that for this printer I had to install proprietary drivers: 
samsung-uld_V1.00.39_01.17.tar.gz
unfortunately it is not clear what they are going to install it is not a 
package and I have not found a log.
Let me know if you need more information I can look at it.

Thanks


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages system-config-printer-udev depends on:
ii  libc62.30-4
ii  libcups2 2.3.1-11
ii  libglib2.0-0 2.64.2-1
ii  libudev1 245.5-1
ii  libusb-1.0-0 2:1.0.23-2
ii  python3  3.8.2-3
ii  python3-cups 1.9.73-3+b1
ii  python3-cupshelpers  1.5.12-1
ii  python3-dbus 1.2.16-2

system-config-printer-udev recommends no packages.

system-config-printer-udev suggests no packages.

-- no debconf information
Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI contains USB 
serial number
Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI match: 
usb://Samsung/M2020%20Series?serial=08HVB8GKCB019MM
Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: free(): invalid pointer
Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI of detected 
printer: usb://Samsung/M2020%20Series?serial=08HVB8GKCB019MM, normalized: 
samsung m2020 series serial 08hvb8gkcb019mm
Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI of print queue: 
usb://Samsung/M2020%20Series?serial=08HVB8GKCB019MM, normalized: samsung m2020 
series serial 08hvb8gkcb019mm
Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: Queue 
ipp://localhost/printers/samsung-m2026 has matching device URI
Apr 22 15:23:40 hellspawn systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
Apr 22 15:23:40 hellspawn systemd[1]: Started Process Core Dump (PID 74191/UID 
0).
Apr 22 15:23:40 hellspawn systemd[1]: configure-printer@usb-005-002.service: 
Main process exited, code=dumped, status=6/ABRT
Apr 22 15:23:40 hellspawn systemd[1]: configure-printer@usb-005-002.service: 
Failed with result 'core-dump'.
Apr 22 15:23:40 hellspawn systemd-coredump[74193]: Process 74160 
(udev-configure-) of user 0 dumped core.
   
   Stack trace of thread 74160:
   #0  0x7f3de0cc6761 
__GI_raise (libc.so.6 + 0x3b761)
   #1  0x7f3de0cb055b 
__GI_abort (libc.so.6 + 0x2555b)
   #2  0x7f3de0d09008 
__libc_message (libc.so.6 + 0x7e008)
   #3  0x7f3de0d103aa 
malloc_printerr (libc.so.6 + 0x853aa)
   #4  0x7f3de0d11d9c 
_int_free (libc.so.6 + 0x86d9c)
   #5  0x55904b38916f n/a 
(udev-configure-printer + 0x416f)
   #6  0x55904b389f89 n/a 
(udev-configure-printer + 0x4f89)
   #7  0x55904b387724 n/a 
(udev-configure-printer + 0x2724)
   #8  0x7f3de0cb1e0b 
__libc_start_main (libc.so.6 + 0x26e0b)
   #9  0x55904b3879ea n/a 
(udev-configure-printer + 0x29ea)
Apr 22 15:23:40 hellspawn systemd[1]: systemd-coredump@0-74191-0.service: 
Succeeded.
Apr 22 15:23:56 hellspawn lightdm[74105]: pam_unix(lightdm:auth): Couldn't open 
/etc/securetty: No such file or directory
Apr 22 15:23:56 hellspawn lightdm[74105]: gkr-pam: unable to locate daemon 
control file
Apr 22 15:23:56 hellspawn lightdm[74105]: gkr-pam: stashed password to try 
later in open session
Apr 22 15:23:56 hellspawn lightdm[74105]: Error getting user list from 
org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
Apr 22 15:23:57 hellspawn systemd[1]: Stopping Session c8 of user lightdm.
Apr 22 15:23:57 hellspawn lightdm[74036]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
Apr 22 15:23:57 hellspawn systemd[1]: 

Bug#953816: nvidia-settings: query status of attached displays + query monitoring/daemon mode

[Alex Andreotti]

Package: nvidia-settings
Version: 440.64-1
Severity: wishlist
Tags: upstream

Dear Maintainer,

   * What led up to the situation?

1) I have a second monitor (DVI) which is always connected to the video card, 
but it is not always on, I have not found a way with nvidia-settings to detect 
if the second monitor is physically on or off.

2) I run nvidia-settings -t -q ... every few seconds to monitor the status of 
the card, I thought it would be useful to have a command line option for 
nvidia-settings that does not end it immediately, but that continues to re- run 
the query every n seconds.

   * 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?

Thanks
Regards

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nvidia-settings depends on:
ii  libc6 2.29-10
ii  libcairo2 1.16.0-4
ii  libgdk-pixbuf2.0-02.40.0+dfsg-3
ii  libglib2.0-0  2.64.0-2
ii  libgtk-3-03.24.14-1
ii  libgtk2.0-0   2.24.32-4
ii  libjansson4   2.12-1
ii  libpango-1.0-01.42.4-8
ii  libpangocairo-1.0-0   1.42.4-8
ii  libx11-6  2:1.6.9-2
ii  libxnvctrl0   440.64-1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  nvidia-alternative440.64-1
ii  nvidia-installer-cleanup  20151021+11

Versions of packages nvidia-settings recommends:
ii  libgl1-nvidia-glvnd-glx  440.64-1
ii  libnvidia-ml1440.64-1
ii  nvidia-vdpau-driver  440.64-1

nvidia-settings suggests no packages.

-- no debconf information

Bug#942365: libgtk2-perl: Package uninstallable

[Alex Andreotti]

Source: libgtk2-perl
Version: 2:1.24993-1
Followup-For: Bug #942365

Dear Maintainer,

   * What led up to the situation?

I'm trying to run obmenu-generator (for openbox) that requires libgtk2-perl

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt install libgtk2-perl

   * What was the outcome of this action?

libgtk2-perl : Depends: perlapi-5.28.1 but it is not installable
apt search perlapi
Sorting... Done
Full Text Search... Done

   * What outcome did you expect instead?

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#945920: Chromium randomly crashes in the latest version.

[Alex Andreotti]

Package: chromium
Version: 79.0.3945.79-1
Followup-For: Bug #945920

Dear Maintainer,

I'm experiencing the same random crashes after upgrading from 78.0.3904.108-1 
to 79.0.3945.79-1

Backtrace attached.

Regards

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common79.0.3945.79-1
ii  libasound2 1.1.9-1
ii  libatk-bridge2.0-0 2.34.1-2
ii  libatk1.0-02.34.1-1
ii  libatomic1 9.2.1-21
ii  libatspi2.0-0  2.34.0-3
ii  libavcodec-extra58 [libavcodec58]  7:4.2.1-2
ii  libavformat58  7:4.2.1-2
ii  libavutil567:4.2.1-2
ii  libc6  2.29-6
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libcups2   2.3.0-7
ii  libdbus-1-31.12.16-2
ii  libdrm22.4.100-4
ii  libevent-2.1-7 2.1.11-stable-1
ii  libexpat1  2.2.9-1
ii  libflac8   1.3.3-1
ii  libfontconfig1 2.13.1-2+b1
ii  libfreetype6   2.10.1-2
ii  libgcc11:9.2.1-21
ii  libgdk-pixbuf2.0-0 2.40.0+dfsg-1
ii  libglib2.0-0   2.62.3-2
ii  libgtk-3-0 3.24.13-1
ii  libharfbuzz0b  2.6.4-1
ii  libicu63   63.2-2
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libjsoncpp11.7.4-3+b1
ii  liblcms2-2 2.9-4
ii  libminizip11.1-8+b1
ii  libnspr4   2:4.23-1
ii  libnss32:3.47.1-1
ii  libopenjp2-7   2.3.1-1
ii  libopus0   1.3-1+b1
ii  libpango-1.0-0 1.42.4-7
ii  libpangocairo-1.0-01.42.4-7
ii  libpci31:3.6.2-6
ii  libpng16-161.6.37-1
ii  libpulse0  13.0-3
ii  libre2-5   20191101+dfsg-1
ii  libsnappy1v5   1.1.7-2
ii  libstdc++6 9.2.1-21
ii  libva2 2.5.0-2
ii  libvpx61.8.1-2
ii  libwebp6   0.6.1-2+b1
ii  libwebpdemux2  0.6.1-2+b1
ii  libwebpmux30.6.1-2+b1
ii  libx11-6   2:1.6.8-1
ii  libx11-xcb12:1.6.8-1
ii  libxcb11.13.1-2
ii  libxcomposite1 1:0.4.4-2
ii  libxcursor11:1.2.0-2
ii  libxdamage11:1.1.5-1
ii  libxext6   2:1.3.3-1+b2
ii  libxfixes3 1:5.0.3-1
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-8
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  libxslt1.1 1.1.32-2.2
ii  libxss11:1.2.3-1
ii  libxtst6   2:1.2.3-1
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages chromium recommends:
ii  chromium-sandbox  79.0.3945.79-1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox 79.0.3945.79-1
ii  dunst [notification-daemon]  1.4.1-1
ii  fonts-liberation 1:1.07.4-10
ii  libgl1-mesa-dri  19.2.6-1
ii  libu2f-udev  1.1.10-1
ii  notification-daemon  3.20.0-4
ii  system-config-printer1.5.12-1
ii  upower   0.99.11-1

Versions of packages chromium-sandbox depends on:
ii  libatomic1  9.2.1-21
ii  libc6   2.29-6
ii  libgcc1 1:9.2.1-21
ii  libstdc++6  9.2.1-21

-- no debconf information

#0  0x5a77cee7 in 
memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vector, std::allocator >, 
std::allocator, 
std::allocator > > > const&, base::OnceCallback >)>)
()
#1  0x58f8ddb0 in 

Bug#941129: fetchmail: pidfile behavior changed

[Alex Andreotti]

On Sat, Sep 28, 2019 at 03:22:51AM +0200, Matthias Andree wrote:

[cut]

> fetchmail behaved inconsistently between daemon and non-detaching modes
> in the upstream version without Debian patches already until 6.4.0-rc4,
> and that needed fixing, and is what I've fixed.
> 
> If there are additional issues, I hope the package maintainer (Laszlo)
> can see to them.

I assume that for some reason with the old versions the script I am
using was not affected, it worked with relative path, I hadn't
modified it for years before finding the problem a few days ago.

On Sat, Sep 28, 2019 at 09:15:42AM +0200, László Böszörményi (GCS) wrote:

[cut]

> Can you revert to 6.4.0~rc3-1 and check it? But I'm going to update
> the packaging to the fixed upstream release. Please test that anyway.

I tried, 6.4.0~rc3-1 worked, from 6.4.0~rc4-1 it doesn't work anymore.


As far as I'm concerned you can close the bug, I'm also happy with
--pidfile, I opened it for your information.


Many thanks to you both for your time and support

Bug#941129: fetchmail: pidfile behavior changed

[Alex Andreotti]

Attention, I was using it with a relative path and it worked, the
behavior change is that it stopped working, I believe with one of the
two updates below:

September 4

fetchmail (6.4.0~rc4-1) unstable; urgency=medium

  * New major upstream RC release.
  * Remove outdated and Python 2 only fetchmailconf package (closes: 
#936512).
  * Drop merged in patches.
  * Update remaining patches.
  * Remove old upgrade code from postinst.

September 6

fetchmail (6.4.0~rc4-2) unstable; urgency=medium

  * Remove all parts of fetchmailconf (closes: #939522).

Bug#941129: fetchmail: pidfile behavior changed

[Alex Andreotti]

Package: fetchmail
Version: 6.4.0~rc4-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I have been using fetchmail for several years to download mail from multiple
 accounts, one instance for each account using the FETCHMAILHOME variable.

I realized only today that it was a few days since it was no longer downloading
 mail.

The script that I use enters the directories of the various accounts,
 sets the variable FETCHMAILHOME and uses the default values

Looking at the log file I saw this message (ACCOUNT is the email):

./ACCOUNT/fetchmail.pid: No such file or directory
fetchmail: lock creation failed.

If I create the file, before launching fetchmail, is correctly removed:

fetchmail: removing stale lockfile

but later the lock fails (ACCOUNT is the email):

7426  openat(AT_FDCWD, "./ACCOUNT/fetchmail.pid", O_WRONLY|O_CREAT|O_EXCL, 
0666) = -1 ENOENT (No such file or directory)
7426  dup(2)= 4
7426  fcntl(4, F_GETFL) = 0x8401 (flags 
O_WRONLY|O_APPEND|O_LARGEFILE)
7426  close(4)  = 0
7426  write(2, "./ACCOUNT/fetch"..., 68) = 68
7426  write(2, "fetchmail: lock creation failed."..., 33) = 33
7426  exit_group(8) = ?
7426  +++ exited with 8 +++

To make fetchmail work again I had to specify the pidfile as argument
 (FETCHMAILHOME is relative, not an absolute path)

--pidfile "$FETCHMAILHOME/fetchmail.pid"

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fetchmail depends on:
ii  adduser   3.118
ii  debianutils   4.9
ii  libc6 2.29-2
ii  libcom-err2   1.45.3-4
ii  libgssapi-krb5-2  1.17-6
ii  libkrb5-3 1.17-6
ii  libssl1.1 1.1.1d-1
ii  lsb-base  11.1.0

Versions of packages fetchmail recommends:
ii  ca-certificates  20190110

Versions of packages fetchmail suggests:
pn  fetchmailconf   
ii  postfix [mail-transport-agent]  3.4.7-1
ii  resolvconf  1.79

-- no debconf information

Bug#874176: wrk: Fails to run with 'PANIC: unprotected error in call to Lua API'

[Alex Andreotti]

Package: wrk
Version: 4.0.2-2
Followup-For: Bug #874176

Dear Maintainer,

  * What led up to the situation?

I needed to use wrk for some benchmark.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt install wrk && wrk -c 800 -d 10 -t 24 http://127.0.0.1:8080/

   * What was the outcome of this action?

PANIC: unprotected error in call to Lua API (attempt to index a nil value)

   * What outcome did you expect instead?

the benchmark to run.

Currently luajit-2.1 is installed but the sources are looking for luajit-2.0, 
also luajit-2.1 is missing a define (luaL_reg luaL_Reg) and src/script.c fail 
to compile.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wrk depends on:
ii  libc62.28-10
ii  libluajit-5.1-2  2.1.0~beta3+dfsg-5.1
ii  libssl1.11.1.1c-1

wrk recommends no packages.

wrk suggests no packages.

-- no debconf information
Index: wrk-4.0.2/src/script.h
===
--- wrk-4.0.2.orig/src/script.h
+++ wrk-4.0.2/src/script.h
@@ -2,9 +2,9 @@
 #define SCRIPT_H
 
 #include 
-#include 
-#include 
-#include 
+#include 
+#include 
+#include 
 #include 
 #include "stats.h"
 #include "wrk.h"
Index: wrk-4.0.2/src/wrk.h
===
--- wrk-4.0.2.orig/src/wrk.h
+++ wrk-4.0.2/src/wrk.h
@@ -10,7 +10,7 @@
 
 #include 
 #include 
-#include 
+#include 
 
 #include "stats.h"
 #include "ae.h"
Index: wrk-4.0.2/src/script.c
===
--- wrk-4.0.2.orig/src/script.c
+++ wrk-4.0.2/src/script.c
@@ -26,6 +26,8 @@ static void set_fields(lua_State *, int,
 static void set_field(lua_State *, int, char *, int);
 static int push_url_part(lua_State *, char *, struct http_parser_url *, enum 
http_parser_url_fields);
 
+#define luaL_reg  luaL_Reg
+
 static const struct luaL_reg addrlib[] = {
 { "__tostring", script_addr_tostring   },
 { "__gc",   script_addr_gc },

Bug#914494: sysvinit-utils: pidof behavior changed with omit option -o

[Alex Andreotti]

Package: sysvinit-utils
Version: 2.92~beta-1
Severity: normal

Dear Maintainer,

  * What led up to the situation?

I'm using a script that when start kills all the script with the same name but 
itself,
the syntax was:

pidof -o $$ -x script.sh

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I did an apt upgrade today that installed sysvinit-utils_2.92~beta-1_amd64, my 
older version
in /var/cache/apt/archives was sysvinit-utils_2.88dsf-59.11_amd64 (Oct 14), the 
behavior
change should be in between.

If I use a shell `sh script.sh` or `zsh script.sh` it works, but `./script.sh` 
directly doesn't,
my /bin/sh link to dash, I don't think is relevant...

As a work around I use a for loop and compare with $$.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sysvinit-utils depends on:
ii  init-system-helpers  1.56
ii  libc62.27-8
ii  util-linux   2.32.1-0.2

sysvinit-utils recommends no packages.

sysvinit-utils suggests no packages.

-- no debconf information

Bug#914484: blender: segv on OpenColorIO -> YAML::detail::node_data::get

[Alex Andreotti]

Package: blender
Version: 2.79.b+dfsg0-4+b1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

trying to run blender

   * What was the outcome of this action?

systemd-coredump[7871]: Process 7864 (blender) of user 1000 dumped core.

note: I upgraded the nvidia driver from experimental some day ago (in order to
  get cuda working with ffmpeg) but blender was still working, and I did
  few system upgrade recently.

A coredump gdb backtrace log attached.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages blender depends on:
ii  blender-data  2.79.b+dfsg0-4
ii  fonts-dejavu  2.37-1
pn  libavcodec58  
ii  libavdevice58 7:4.0.3-1
ii  libavformat58 7:4.0.3-1
ii  libavutil56   7:4.0.3-1
ii  libboost-atomic1.67.0 1.67.0-10
ii  libboost-chrono1.67.0 1.67.0-10
ii  libboost-date-time1.67.0  1.67.0-10
ii  libboost-filesystem1.67.0 1.67.0-10
ii  libboost-iostreams1.67.0  1.67.0-10
ii  libboost-locale1.67.0 1.67.0-10
ii  libboost-regex1.67.0  1.67.0-10
ii  libboost-system1.67.0 1.67.0-10
ii  libboost-thread1.67.0 1.67.0-10
ii  libc6 2.27-8
ii  libfftw3-double3  3.3.8-2
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-9
ii  libgl11.1.0-1
ii  libglew2.12.1.0-2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgomp1  8.2.0-9
ii  libilmbase23  2.2.1-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2
ii  libjemalloc1  3.6.0-11
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  libopenal11:1.19.1-1
ii  libopencolorio1v5 1.1.0~dfsg0-2
ii  libopenexr23  2.2.1-4
ii  libopenimageio1.8 1.8.15~dfsg0-1+b1
ii  libopenjp2-7  2.3.0-1
ii  libopenvdb5.0 5.0.0-2
ii  libpcre3  2:8.39-11
ii  libpng16-16   1.6.34-2
ii  libpython3.6  3.6.7-1
ii  libsndfile1   1.0.28-4
ii  libspnav0 0.2.3-1
ii  libstdc++68.2.0-9
ii  libswscale5   7:4.0.3-1
ii  libtbb2   2017~U7-8
ii  libtiff5  4.0.10-3
ii  libx11-6  2:1.6.7-1
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxml2   2.9.4+dfsg1-7+b2
ii  libxxf86vm1   1:1.1.4-1+b2
ii  python3   3.6.7-1
ii  zlib1g1:1.2.11.dfsg-1

blender recommends no packages.

blender suggests no packages.

-- no debconf information
   PID: 7864 (blender)
   UID: 1000 (alex)
   GID: 1000 (alex)
Signal: 11 (SEGV)
 Timestamp: Fri 2018-11-23 20:08:42 CET (19s ago)
  Command Line: blender
Executable: /usr/bin/blender
 Control Group: /user.slice/user-1000.slice/session-2.scope
  Unit: session-2.scope
 Slice: user-1000.slice
   Session: 2
 Owner UID: 1000 (alex)
   Boot ID: 69c5b102150f4313a80b0a25e798c7f3
Machine ID: 6cbd0c550e6a4ab981e041a13ba68e48
  Hostname: hellspawn
   Storage: 
/var/lib/systemd/coredump/core.blender.1000.69c5b102150f4313a80b0a25e798c7f3.7864.154300012200.lz4
   Message: Process 7864 (blender) of user 1000 dumped core.

Stack trace of thread 7864:
#0  0x7f54886495e2 
_ZNK4YAML6detail9node_data3getINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEPNS0_4nodeERKT_N5boost10shared_ptrINS0_13memory_holderEEE
 (libOpenColorIO.so.1)
#1  0x7f5488642b1d load (libOpenColorIO.so.1)
#2  0x7f548864669d 
_ZNK11OpenColorIO2v18OCIOYaml4openERSiRNSt3tr110shared_ptrINS0_6ConfigEEEPKc 
(libOpenColorIO.so.1)
#3  0x7f54885bfa63 
_ZN11OpenColorIO2v16Config14CreateFromFileEPKc (libOpenColorIO.so.1)
#4  0x55c9fac5837f _ZN8OCIOImpl20configCreateFromFileEPKc 
(blender)
#5  0x55c9f9bfcd3a colormanagement_init (blender)
#6  0x55c9f91dcfe2 main (blender)
#7  

Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)

[Alex Andreotti]

Hello Bernhard,
  
thanks for replying and the hints, see the attachment, sorry about the
grave flag, feel free to change it (looking at the stack may be
something related to the atspi upgrade, I'll try a downgrade, perhaps
not a lightdm bug), currently I can login booting at level 3 and then
startx manually.

Kind regards
Alex

GNU gdb (Debian 8.1-4+b1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/lightdm-gtk-greeter...Reading symbols from 
/usr/lib/debug/.build-id/c0/e5308b5094bd6e1bd8fc5473e690244ebf3ec6.debug...done.
done.

warning: core file may not match specified executable file.
[New LWP 1562]
[New LWP 1563]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/lightdm-gtk-greeter'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:93
93  ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
[Current thread is 1 (Thread 0x7f1b938c1a80 (LWP 1562))]
(gdb) q
   PID: 1562 (lightdm-gtk-gre)
   UID: 110 (lightdm)
   GID: 116 (lightdm)
Signal: 11 (SEGV)
 Timestamp: Thu 2018-10-25 16:12:05 CEST (4min 22s ago)
  Command Line: /usr/sbin/lightdm-gtk-greeter
Executable: /usr/sbin/lightdm-gtk-greeter
 Control Group: /user.slice/user-110.slice/session-c1.scope
  Unit: session-c1.scope
 Slice: user-110.slice
   Session: c1
 Owner UID: 110 (lightdm)
   Boot ID: fe8320c4f1fa48389152f7b8a23c1ba8
Machine ID: 6cbd0c550e6a4ab981e041a13ba68e48
  Hostname: hellspawn
   Storage: 
/var/lib/systemd/coredump/core.lightdm-gtk-gre.110.fe8320c4f1fa48389152f7b8a23c1ba8.1562.154047672500.lz4
   Message: Process 1562 (lightdm-gtk-gre) of user 110 dumped core.

Stack trace of thread 1562:
#0  0x7f1b99a64907 __strlen_avx2 (libc.so.6)
#1  0x7f1b99cee3f8 g_string_insert_len (libglib-2.0.so.0)
#2  0x7f1b99cd32a5 g_log_writer_format_fields 
(libglib-2.0.so.0)
#3  0x7f1b99cd41ae g_log_writer_standard_streams 
(libglib-2.0.so.0)
#4  0x7f1b99cd42b2 g_log_writer_default (libglib-2.0.so.0)
#5  0x7f1b99cd2657 g_log_structured_array (libglib-2.0.so.0)
#6  0x7f1b99cd2a9d g_log_default_handler (libglib-2.0.so.0)
#7  0x7f1b99cd2cef g_logv (libglib-2.0.so.0)
#8  0x7f1b99cd2edf g_log (libglib-2.0.so.0)
#9  0x7f1b96b79342 atspi_get_a11y_bus (libatspi.so.0)
#10 0x7f1b98de860a atk_bridge_adaptor_init 
(libatk-bridge-2.0.so.0)
#11 0x7f1b9a265664 n/a (libgtk-3.so.0)
#12 0x7f1b9a40fd39 n/a (libgtk-3.so.0)
#13 0x7f1b99dabb6d g_closure_invoke (libgobject-2.0.so.0)
#14 0x7f1b99dbe8f3 n/a (libgobject-2.0.so.0)
#15 0x7f1b99dc7882 g_signal_emit_valist 
(libgobject-2.0.so.0)
#16 0x7f1b99dc7ecf g_signal_emit (libgobject-2.0.so.0)
#17 0x7f1b99db01d4 n/a (libgobject-2.0.so.0)
#18 0x7f1b99db2651 g_object_notify (libgobject-2.0.so.0)
#19 0x7f1b9a1119b8 n/a (libgdk-3.so.0)
#20 0x7f1b99dabb6d g_closure_invoke (libgobject-2.0.so.0)
#21 0x7f1b99dbe124 n/a (libgobject-2.0.so.0)
#22 0x7f1b99dc7882 g_signal_emit_valist 
(libgobject-2.0.so.0)
#23 0x7f1b99dc83a4 g_signal_emit_by_name 
(libgobject-2.0.so.0)
#24 0x7f1b9a13cf5a n/a (libgdk-3.so.0)
#25 0x7f1b9a11182d gdk_display_manager_open_display 
(libgdk-3.so.0)
#26 0x7f1b9a410f1a gtk_init_check (libgtk-3.so.0)
#27 0x7f1b9a410f49 gtk_init (libgtk-3.so.0)
#28 0x55d6e0bc2e86 main (lightdm-gtk-greeter)
#29 0x7f1b9992cb17 __libc_start_main (libc.so.6)
#30 0x55d6e0bc555a _start (lightdm-gtk-greeter)

Stack trace of thread 1563:
#0  0x7f1b999f7739 __GI___poll (libc.so.6)
#1  

Bug#911760: lightdm: more info

[Alex Andreotti]

Package: lightdm
Version: 1.26.0-3
Followup-For: Bug #911760

Could have something to do with the systemd/libpam upgrade? 
I have another issue with a password prompter (see attachment)
Oct 24 15:42:45 hellspawn gpg-agent[1931]: failed to unprotect the secret key: 
Inappropriate ioctl for device
Oct 24 15:42:45 hellspawn gpg-agent[1931]: failed to read the secret key
Oct 24 15:42:45 hellspawn gpg-agent[1931]: command 'PKDECRYPT' failed: 
Inappropriate ioctl for device 
Oct 24 15:42:45 hellspawn dbus-daemon[1485]: [session uid=1000 pid=1485] 
Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.22' 
(uid=1000 pid=1986 comm="pinentry --display :0 ")
Oct 24 15:42:45 hellspawn dbus-daemon[1485]: [session uid=1000 pid=1485] 
Activated service 'org.gnome.keyring.SystemPrompter' failed: Process 
org.gnome.keyring.SystemPrompter received signal 11
Oct 24 15:42:45 hellspawn gpg-agent[1931]: No Gcr System Prompter available, 
falling back to curses
Oct 24 15:42:45 hellspawn kernel: gcr-prompter[1991]: segfault at 696e6420 ip 
7ff4696c5907 sp 7fff5a80b198 error 4 in 
libc-2.27.so[7ff46958d000+146000]
Oct 24 15:42:45 hellspawn kernel: Code: f9 20 77 1f c5 fd 74 0f c5 fd d7 c1 85 
c0 0f 85 df 00 00 00 48 83 c7 20 83 e1 1f 48 83 e7 e0 eb 36 66 90 83 e1 1f 48 
83 e7 e0  fd 74 0f c5 fd d7 c1 d3 f8 85 c0 74 1b f3 0f bc c0 48 01 f8 48 

Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop

[Alex Andreotti]

Package: lightdm
Version: 1.26.0-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

A system upgrade, a list of the packages upgraded should be attached, I don't 
see any relation with lightdm but I could be missing something

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt update
apt upgrade
reboot

   * What was the outcome of this action?

lightdm doesn't start, segfault and restart until systemd stop it

   * What outcome did you expect instead?

the usual login dialog

Attached there should be the `journal -xe` segfault, the list of the packages 
installed by the upgrade, the backtrace of a `gdb lighdm --debug` session.
Please let me know how/if I can help with more logs.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.10-1
ii  debconf [debconf-2.0]  1.5.69
ii  libaudit1  1:2.8.4-2
ii  libc6  2.27-6
ii  libgcrypt201.8.3-1
ii  libglib2.0-0   2.58.1-2
ii  libpam-systemd 239-10
ii  libpam0g   1.1.8-3.8
ii  libxcb11.13.1-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.5-1
ii  lsb-base   9.20170808

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.8-2
ii  xserver-xephyr   2:1.20.1-5

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
[XDMCPServer]
[VNCServer]


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm
Starting program: /usr/sbin/lightdm --debug --test-mode
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.03s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=2132
[+0.05s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
[+0.07s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.10s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
[+0.12s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.14s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.16s] DEBUG: Registered seat module local
[+0.19s] DEBUG: Registered seat module xremote
[+0.21s] DEBUG: Registered seat module unity
[+0.23s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[New Thread 0x76714700 (LWP 2136)]
[New Thread 0x75f13700 (LWP 2137)]
[New Thread 0x756cc700 (LWP 2138)]
[+0.36s] DEBUG: Monitoring logind for seats
[+0.38s] DEBUG: New seat added from logind: seat0
[+0.40s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.42s] DEBUG: Seat seat0: Starting
[+0.44s] DEBUG: Seat seat0: Creating greeter session
[+0.46s] DEBUG: Seat seat0: Creating display server of type x
[+0.48s] DEBUG: posix_spawn avoided (fd close requested)
[+0.49s] DEBUG: Could not run plymouth --ping: Failed to execute child process 
?plymouth? (No such file or directory)
[+0.51s] DEBUG: Using VT 7
[+0.53s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.55s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.57s] DEBUG: XServer 0: Writing X server authority to 
/var/run/lightdm/root/:0
[+0.59s] DEBUG: XServer 0: Launching X Server
[+0.61s] DEBUG: Launching process 2140: /usr/bin/X :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.63s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.65s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.67s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+0.69s] WARNING: Error getting user list from org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
[+0.73s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.76s] WARNING: Failed to read password database: No such file or directory
[+0.78s] DEBUG: User alex added
[+0.80s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close 
requested)
[+0.91s] DEBUG: Seat seat0 

Bug#903580: aegisub still can't be installed on unstable

[Alex Andreotti]

Package: aegisub
Version: 3.2.2+dfsg-3+b6
Followup-For: Bug #903580

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I'm trying to install aegisub on a sid machine

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt install aegisub

   * What was the outcome of this action?

The following packages have unmet dependencies:
 aegisub : Depends: libboost-regex1.62.0 but it is not going to be installed


apt install libboost-regex1.62.0
libboost-regex1.62.0 is already the newest version (1.62.0+dfsg-10).

   * What outcome did you expect instead?

to install and run? :-)

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aegisub depends on:
ii  libasound2 1.1.6-1
ii  libass91:0.14.0-2
ii  libboost-filesystem1.62.0  1.62.0+dfsg-10
ii  libboost-locale1.62.0  1.62.0+dfsg-10
ii  libboost-regex1.62.0   1.62.0+dfsg-10
ii  libboost-system1.62.0  1.62.0+dfsg-10
ii  libboost-thread1.62.0  1.62.0+dfsg-10
ii  libc6  2.27-6
ii  libffms2-4 2.23-3+b1
ii  libfftw3-double3   3.3.8-2
ii  libfontconfig1 2.13.0-5
ii  libgcc11:8.2.0-6
ii  libgl1 1.1.0-1
ii  libgl1-mesa-glx18.1.8-1
ii  libhunspell-1.6-0  1.6.2-1+b1
ii  libicu57   57.1-9
ii  libluajit-5.1-22.1.0~beta3+dfsg-5.1
ii  libpulse0  12.2-2
ii  libstdc++6 8.2.0-6
ii  libwxbase3.0-0v5   3.0.4+dfsg-4
ii  libwxgtk3.0-0v53.0.4+dfsg-4
ii  zlib1g 1:1.2.11.dfsg-1

aegisub recommends no packages.

Versions of packages aegisub suggests:
pn  aegisub-l10n  

Bug#818597: libcpprest2.7: libcpprest.so.2.7 not installed

[Alex Andreotti]

Package: libcpprest2.7
Version: 2.8.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

I'm trying to use poedit

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

run poedit from the shell

   * What was the outcome of this action?

poedit: error while loading shared libraries: libcpprest.so.2.7: cannot open 
shared object file: No such file or directory

   * What outcome did you expect instead?

poedit to run, I used it yesterday or the day before, so must been a recent 
upgrade.

$ dpkg -S libcpprest.so.2.7
dpkg-query: no path found matching pattern *libcpprest.so.2.7*

$ sudo apt-file search libcpprest.so.2.7
libcpprest2.7: /usr/lib/x86_64-linux-gnu/libcpprest.so.2.7

$ dpkg -l "*libcpprest*"
ii  libcpprest2.7:amd64 2.8.0-1  amd64
Shared library for Casablanca

$ dpkg -L libcpprest2.7
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libcpprest2.7
/usr/share/doc/libcpprest2.7/changelog.Debian.gz
/usr/share/doc/libcpprest2.7/copyright

# apt-get install --reinstall doesn't solve, the lib seems missing.


Regards


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#810781: nvidia-cuda-toolkit : Depends: nvidia-cuda-dev (= 6.5.19-2) but it is not going to be installed

[Alex Andreotti]

Recent upgrades fixed the dependencies, may be closed.

Bug#810781: nvidia-cuda-toolkit : Depends: nvidia-cuda-dev (= 6.5.19-2) but it is not going to be installed

[Alex Andreotti]

Source: nvidia-cuda-toolkit
Severity: normal

Dear Maintainer,

  * What led up to the situation?

I'm trying to enable GPU rendering for blender, I had it working few weeks ago
on a very similar, almost equal, system environment (Debian/unstable),
but it was on x86 arch and I had to switch to amd64, now can't get it working 
anymore.

   * 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?

Being able to install nvidia-cuda-toolkit, it should enable GPU option in 
blender
(User settings -> system -> Compute device)

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Below the current installation error log, this morning I just upgraded because 
have seen
there was some *nvidia* upgrade, before the upgrade I had a different error,
but always related to unmet dependencies for nvidia-cuda-dev

% sudo apt-get install nvidia-cuda-toolkit
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-cuda-toolkit : Depends: nvidia-cuda-dev (= 6.5.19-2) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

% sudo apt-get install nvidia-cuda-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-cuda-dev : Depends: libcuinj64-6.5 (= 6.5.19-2) but it is not going 
to be installed
   Recommends: libnvcuvid1 but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

% sudo apt-get install libcuinj64-6.5
Reading package lists... Done
Building dependency tree   
Reading state information... Done
libcuinj64-6.5 is already the newest version (6.5.19-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Bug#806487: syslinux: FTBFS: ldlinux.raw: write error

[Alex Andreotti]

I've the same error with buildroot's syslinux, the problem is in
the file prepcore.c, in particular:

if (fwrite(infile + start, 1, offset - start, f) != offset - start ||
fwrite(out, 1, outfile_len, f) != outfile_len || fclose(f))
error("write error");

given the code seems obvious an offset > start is expected, but a
printf show otherwise:

infile=0x1cf0240 start=31744 out=0x7f3db1d6e010 offset=0
outfile_len=57639

offset is initialized with pfx_compressed:

offset = get_32(>pfx_compressed);

something changed in some file format or some header?
or something about the arch being 64bit?
(objcopy doesn't fail)

-rw-r--r-- 1 alex alex 250589 Dec 15 13:05 ldlinux.lsr
-rw-r--r-- 1 alex alex 250589 Dec 15 13:05 ldlinux.lst
-rw-r--r-- 1 alex alex   4136 Dec 15 13:05 ldlinux.sec
-rwxr-xr-x 1 alex alex 687828 Dec 15 13:05 ldlinux.elf
-rw-r--r-- 1 alex alex 127464 Dec 15 13:05 ldlinux.raw
-rw-r--r-- 1 alex alex  0 Dec 15 13:05 ldlinux.bin

Bug#792089: gnome-screenshot: GNOME Screenshot flash doesn't go away until the app exits

[Alex Andreotti]

Package: gnome-screenshot
Version: 3.16.2-1
Followup-For: Bug #792089

I had the same problem, been using gnome-screenshot a lot, but
in the past few weeks with this bug was impossible to use.
The modal gray window cover the whole captured area and is sticky
over all the other windows, it doesn't capture mouse/keyboard
events, so eventually you blindly type/click on windows behind.

Weird downgrading to stable/3.14.0-1 doesn't change anything.

Commented out the cheese_flash stuff in screenshot_fallback_fire_flash()
in screenshot-utils.c and it solved (I don't care about being notified
by a flash, always use it in interactive mode)

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-screenshot depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  libc62.19-19
ii  libcairo21.14.2-2
ii  libcanberra-gtk3-0   0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libgdk-pixbuf2.0-0   2.31.5-1
ii  libglib2.0-0 2.44.1-1.1
ii  libgtk-3-0   3.16.5-1
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1

gnome-screenshot recommends no packages.

gnome-screenshot suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765589: lightdm: greeter-hide-users=true in 01_debian.conf

[Alex Andreotti]

Package: lightdm
Version: 1.10.3-1
Severity: wishlist

Hello dear Maintainer,

I would like to know if is really necessary to declare greeter-hide-users=true
in /usr/share/lightdm/lightdm.conf.d/01_debian.conf

I like to set it to false and have to do it on every lightdm upgrade,
/usr/share/lightdm/lightdm.conf.d/01_debian.conf override 
/etc/lightdm/lightdm.conf,
is this wanted/expected?

On upgrades with edits in /etc/lightdm/lightdm.conf I've to edit both.

Please let me know.

Cheers

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lightdm depends on:
ii  adduser3.113+nmu3
ii  consolekit 0.4.6-5
ii  dbus   1.8.8-2
ii  debconf [debconf-2.0]  1.5.53
ii  libc6  2.19-11
ii  libgcrypt201.6.2-4
ii  libglib2.0-0   2.42.0-2
ii  libpam-systemd 215-5+b1
ii  libpam0g   1.1.8-3.1
ii  libxcb11.10-3
ii  libxdmcp6  1:1.1.1-1
ii  lightdm-gtk-greeter [lightdm-greeter]  1.8.5-1

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+7

Versions of packages lightdm suggests:
pn  accountsservice  none
ii  upower   0.99.1-3

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
greeter-session=lightdm-gtk-greeter
greeter-hide-users=false
greeter-allow-guest=false
[SeatDefaults]
[XDMCPServer]
[VNCServer]


-- debconf information excluded

-- debsums errors found:
debsums: changed file /usr/share/lightdm/lightdm.conf.d/01_debian.conf (from 
lightdm package)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765589: [Pkg-xfce-devel] Bug#765589: lightdm: greeter-hide-users=true in 01_debian.conf

[Alex Andreotti]

On Thu, Oct 16, 2014 at 03:23:28PM +0200, Yves-Alexis Perez wrote:
 control: tag -1 unreproducible moreinfo
 On jeu., 2014-10-16 at 15:02 +0200, Alex Andreotti wrote:
  Package: lightdm
  Version: 1.10.3-1
  Severity: wishlist
  
  Hello dear Maintainer,
  
  I would like to know if is really necessary to declare 
  greeter-hide-users=true
  in /usr/share/lightdm/lightdm.conf.d/01_debian.conf
 
 Yes, I don't want to expose each and every users of each and every
 Debian box running LightDM.

Ok, but isn't already set by default to true on /etc/lightdm/lightdm.conf?

  I like to set it to false and have to do it on every lightdm upgrade,
  /usr/share/lightdm/lightdm.conf.d/01_debian.conf override 
  /etc/lightdm/lightdm.conf,
  is this wanted/expected?
 
 Here editing /etc/lightdm/lightdm.conf works just fine, it overrides
 correctly settings from /usr/share.

So, how do I check why on my system /usr/share win?

Thanks
Regards


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765589: [Pkg-xfce-devel] Bug#765589: lightdm: greeter-hide-users=true in 01_debian.conf

[Alex Andreotti]

On Thu, Oct 16, 2014 at 03:34:38PM +0200, Yves-Alexis Perez wrote:
 On jeu., 2014-10-16 at 15:31 +0200, Alex Andreotti wrote:
  On Thu, Oct 16, 2014 at 03:23:28PM +0200, Yves-Alexis Perez wrote:
   control: tag -1 unreproducible moreinfo
   On jeu., 2014-10-16 at 15:02 +0200, Alex Andreotti wrote:
Package: lightdm
Version: 1.10.3-1
Severity: wishlist

Hello dear Maintainer,

I would like to know if is really necessary to declare 
greeter-hide-users=true
in /usr/share/lightdm/lightdm.conf.d/01_debian.conf
   
   Yes, I don't want to expose each and every users of each and every
   Debian box running LightDM.
  
  Ok, but isn't already set by default to true on /etc/lightdm/lightdm.conf?
 
 No, default is false.

Isn't this a countersense? Why not setting it true here by default and
leave from 01_debian.conf?

  
I like to set it to false and have to do it on every lightdm upgrade,
/usr/share/lightdm/lightdm.conf.d/01_debian.conf override 
/etc/lightdm/lightdm.conf,
is this wanted/expected?
   
   Here editing /etc/lightdm/lightdm.conf works just fine, it overrides
   correctly settings from /usr/share.
  
  So, how do I check why on my system /usr/share win?
 
 Check lightdm --show-config which will show you from where the variables
 are set (to a different value than the default):
 
 root@scapa:~# lightdm --show-config
[SeatDefaults]
 A  greeter-session=lightdm-greeter
 B  greeter-hide-users=false
 A  session-wrapper=/etc/X11/Xsession
 
 Sources:
 A  /usr/share/lightdm/lightdm.conf.d/01_debian.conf
 B  /etc/lightdm/lightdm.conf
 

So, I tried setting it to true on 01_debian.conf:

lightdm --show-config
~
[sudo] password for alex: 
   [SeatDefaults]
A  greeter-session=lightdm-greeter
A  greeter-hide-users=true
A  session-wrapper=/etc/X11/Xsession

   [LightDM]
B  greeter-session=lightdm-gtk-greeter
B  greeter-hide-users=false
B  greeter-allow-guest=false

Sources:
A  /usr/share/lightdm/lightdm.conf.d/01_debian.conf
B  /etc/lightdm/lightdm.conf

It show correct order but on boot it ask for username...

Suggestions?

Thanks


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765589: [Pkg-xfce-devel] Bug#765589: lightdm: greeter-hide-users=true in 01_debian.conf

[Alex Andreotti]

On Thu, Oct 16, 2014 at 04:04:20PM +0200, Yves-Alexis Perez wrote:
 On jeu., 2014-10-16 at 15:42 +0200, Alex Andreotti wrote:
  On Thu, Oct 16, 2014 at 03:34:38PM +0200, Yves-Alexis Perez wrote:
   On jeu., 2014-10-16 at 15:31 +0200, Alex Andreotti wrote:
On Thu, Oct 16, 2014 at 03:23:28PM +0200, Yves-Alexis Perez wrote:
 control: tag -1 unreproducible moreinfo
 On jeu., 2014-10-16 at 15:02 +0200, Alex Andreotti wrote:
  Package: lightdm
  Version: 1.10.3-1
  Severity: wishlist
  
  Hello dear Maintainer,
  
  I would like to know if is really necessary to declare 
  greeter-hide-users=true
  in /usr/share/lightdm/lightdm.conf.d/01_debian.conf
 
 Yes, I don't want to expose each and every users of each and every
 Debian box running LightDM.

Ok, but isn't already set by default to true on 
/etc/lightdm/lightdm.conf?
   
   No, default is false.
  
  Isn't this a countersense? Why not setting it true here by default and
  leave from 01_debian.conf?
 
 Because lightdm.conf comes from upstream (so we don't need to patch it
 manually) and is usually modified (with tracking) by the box
 administrator.
  

  I like to set it to false and have to do it on every lightdm 
  upgrade,
  /usr/share/lightdm/lightdm.conf.d/01_debian.conf override 
  /etc/lightdm/lightdm.conf,
  is this wanted/expected?
 
 Here editing /etc/lightdm/lightdm.conf works just fine, it overrides
 correctly settings from /usr/share.

So, how do I check why on my system /usr/share win?
   
   Check lightdm --show-config which will show you from where the variables
   are set (to a different value than the default):
   
   root@scapa:~# lightdm --show-config
  [SeatDefaults]
   A  greeter-session=lightdm-greeter
   B  greeter-hide-users=false
   A  session-wrapper=/etc/X11/Xsession
   
   Sources:
   A  /usr/share/lightdm/lightdm.conf.d/01_debian.conf
   B  /etc/lightdm/lightdm.conf
   
  
  So, I tried setting it to true on 01_debian.conf:
  
  lightdm --show-config
  ~
  [sudo] password for alex: 
 [SeatDefaults]
  A  greeter-session=lightdm-greeter
  A  greeter-hide-users=true
  A  session-wrapper=/etc/X11/Xsession
  
 [LightDM]
  B  greeter-session=lightdm-gtk-greeter
  B  greeter-hide-users=false
  B  greeter-allow-guest=false
  
  Sources:
  A  /usr/share/lightdm/lightdm.conf.d/01_debian.conf
  B  /etc/lightdm/lightdm.conf
  
  It show correct order but on boot it ask for username...
 
 Well, that looks obvious to me… Compare with my output, and look at the
 session ([]) names… You're defining greeter-hide-users in the wrong
 section.
  
 

Oops, thank you the section did the trick.

Regards


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#694879: blender 2.71 still missing Collada import/export support

[alex . andreotti]

Thank you
that's a good news, I look forward to it.
Keep up the good work!

Cheers

On Mon, Sep 22, 2014 at 09:16:45AM +0200, Rene Engelhard wrote:
 On Mon, Sep 22, 2014 at 08:47:43AM +0200, Matteo F. Vescovi wrote:
 [2]https://bugs.debian.org/694932
 Don't hold your breath waiting for it, though ;-)
 We (Rene and I) are working on it: him for LO, me for Blender.
 
 Indeed, though notthing happened much since some time:
 http://anonscm.debian.org/cgit/pkg-multimedia/opencollada.git/
 
 I think we (you? I got fed up with NEW...) should upload it asap.
 (colada2gltf is an other story but only my problem :))
 Updates can then still happen :)
 
 Anyway, don't expect to see it in the archives any time soon.
 It probably won't be part of Jessie freeze/release, I guess.
 
 Indeed, especially as it's a NEW packge and needs to go through NEW
 and *then* blender neeeds to enable it with the waiting time of 10 days.
 And the freeze is on Nov 5
 
 Regards,
 
 Rene
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#694879: blender 2.71 still missing Collada import/export support

[Alex Andreotti]

Package: blender
Version: 2.71+dfsg1-1
Followup-For: Bug #694879

Dear Maintainer,

I was trying to export from blender to three.js (webgl).
three.js have a native (py) blender exporter but this create a generic json,
the generic JSONloader is then used from three.js to load the exports,
but it seem to have some problem (may be still in development).

Looking around seem the standard way to export from blender to three.js is 
using Collada.

Any hope to get it enabled?

Thanks
Cheers

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.14-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages blender depends on:
ii  blender-data  2.71+dfsg1-1
ii  fonts-droid   1:4.4.3r1.1-1
ii  libavcodec56  6:11-1
ii  libavdevice55 6:11-1
ii  libavformat56 6:11-1
ii  libavutil54   6:11-1
ii  libboost-date-time1.55.0  1.55.0+dfsg-3
ii  libboost-filesystem1.55.0 1.55.0+dfsg-3
ii  libboost-locale1.55.0 1.55.0+dfsg-3
ii  libboost-regex1.55.0  1.55.0+dfsg-3
ii  libboost-system1.55.0 1.55.0+dfsg-3
ii  libboost-thread1.55.0 1.55.0+dfsg-3
ii  libc6 2.19-11
ii  libfftw3-double3  3.3.4-1
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.1-14
ii  libgl1-mesa-glx [libgl1]  10.2.6-1
ii  libglew1.10   1.10.0-3
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libgomp1  4.9.1-14
ii  libilmbase6   1.0.1-6.1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20140719git3eb0ae6a~dfsg-1
ii  libjpeg8  8d1-1
ii  libjs-jquery  1.7.2+dfsg-3.2
ii  libjs-jquery-ui   1.10.1+dfsg-1
ii  libopenal11:1.15.1-5
ii  libopencolorio1   1.0.9~dfsg0-3
ii  libopenexr6   1.6.1-8
ii  libopenimageio1.4 1.4.13~dfsg0-1
ii  libopenjpeg5  1.5.2-2
ii  libpng12-01.2.50-2
ii  libpython3.4  3.4.1-11
ii  libsdl1.2debian   1.2.15-10
ii  libsndfile1   1.0.25-9
ii  libspnav0 0.2.2-1
ii  libstdc++64.9.1-14
ii  libswscale3   6:11-1
ii  libtiff5  4.0.3-10
ii  libx11-6  2:1.6.2-3
ii  libxi62:1.7.4-1
ii  libxxf86vm1   1:1.1.3-1
ii  zlib1g1:1.2.8.dfsg-2

blender recommends no packages.

blender suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761423: busybox: using find in pipe with dd produce semi-random output

[Alex Andreotti]

Package: busybox
Version: 1:1.22.0-8
Severity: normal

Dear Maintainer,

probably the problem is in the mainstream but it affect also Debian.

   * What led up to the situation?

I was trying to find a shell way to check if a directory is empty

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I created a chroot with only busybox and the libs needed (as shown by ldd) to 
be sure it is using only busybox commands.

 sudo chroot chrootdir /bin/busybox sh

created a shell function:

isempty() { [ $(find $1 -name ?* | dd bs=$((${#1}+3)) count=1 
2/dev/null) = $1 ] ; }
mkdir /test  /test/.x
while [ 1 ] ; do if ! isempty /test ; then echo error ; break ; else echo not 
empty ; fi ; done

run it few times
run 1 to 3 exit immediatly with error
run 4 show a non emtpy then error
run 5 show 9 non empty then error
(nobody removed or added files in /test)

also running manually the command below show different results from time to time

find /test -name ?* | dd count=1 2/dev/null

   * What was the outcome of this action?

output truncated randomically, seem by line ending, when is wrong show only the 
first line.

   * What outcome did you expect instead?

always the same predictable full output of find.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.14-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages busybox depends on:
ii  libc6  2.19-10

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761423: busybox: using find in pipe with dd produce semi-random output

[Alex Andreotti]

Sorry I see I've missed a `touch /test/.x` in the bugreport.

The test case is really simple:

% busybox sh

BusyBox v1.22.1 (Debian 1:1.22.0-8) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ mkdir /tmp/emptytest
~ $ touch /tmp/emptytest/.x
~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null
/tmp/emptytest/
~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null 
/tmp/emptytest/
~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null 
/tmp/emptytest/
/tmp/emptytest/.x
~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null 
/tmp/emptytest/
~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null 
/tmp/emptytest/
/tmp/emptytest/.x
~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null 
/tmp/emptytest/
~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null 
/tmp/emptytest/
/tmp/emptytest/.x

The output should be always:

/tmp/emptytest/
/tmp/emptytest/.x

Assuming dd block size default to 512.

Notice that omitting count or in pipe with cat it work properly.

I guess something wrong on how dd close the pipe or find handle
broken pipes.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#739054: fglrx-driver: fglrx segfault

[Alex Andreotti]

On Fri, Apr 25, 2014 at 05:14:54PM +0200, Andrey Gursky wrote:
 Hi,
 
 with fglrx 14.4~rc1.0.apr17-1 and Xorg 1.15.1 just starting chromium
 (and for sure skype also) still crashes the X:

I'm using skype as untrusted user and have no problems (but I'm also
on i386), still chromium make X segfault because a safe configuration
for the user is missing, I'm trying to fix that but currently the only
way I found is to edit /usr/bin/chromium and add
--disable-accelerated-compositing --disable-threaded-compositing
arguments, using chrome://flags I'm unable to get the same result.


ii  skype  4.2.0.13-1 i386

/usr/bin/xhost +local:trustno1
/usr/bin/sudo -H -u trustno1 -g trustno1 /usr/bin/skype 

sudo -u trustno1 id
uid=1001(trustno1) gid=1001(trustno1)
gruppi=1001(trustno1),20(dialout),29(audio),44(video),46(plugdev),102(messagebus)

[cut...]


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#739054: fglrx-driver: fglrx segfault

[Alex Andreotti]

Launching chromium on a fresh install (without ~/.config/chromium) or
with the default config give me this segfault:

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7750c0f]
1: /usr/bin/X (0xb75a9000+0x1ab9e4) [0xb77549e4]
2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb758740c]
3: /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb70e+0x39b13)
   [0xb7119b13]
4: /lib/i386-linux-gnu/i686/cmov/libc.so.6 (__strtod_internal+0x38)
   [0xb7115e88]
5: /usr/lib/xorg/modules/linux/libglx.so (0xb6cdb000+0x3fd97)
   [0xb6d1ad97]
6: /usr/lib/xorg/modules/linux/libglx.so (0xb6cdb000+0x3fe9c)
   [0xb6d1ae9c]
7: /usr/lib/xorg/modules/linux/libglx.so (0xb6cdb000+0x12866)
   [0xb6ced866]
8: /usr/bin/X (0xb75a9000+0x3cb0d) [0xb75e5b0d]

/usr/lib/xorg/modules/linux/libglx.so -
/etc/alternatives/glx--linux-libglx.so

/etc/alternatives/glx--linux-libglx.so -
/usr/lib/fglrx/fglrx-libglx.so

fglrx-driver: /usr/lib/fglrx/fglrx-libglx.so

ii  fglrx-driver   1:14.3~beta1.0-1 i386 non-free ATI/AMD
RadeonHD display driver

To get chromium working I've to use --disable-accelerated-compositing
--disable-threaded-compositing or disable them in chrome://flags


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#739054: fglrx-driver: fglrx segfault

[alex . andreotti]

My apologies for such a generic subject for a bug.

The bug I had when this was opened was something preventing me from
loading the desktop and has been fixed, gone.

The bug with chromium is something different.

I've debootstrapped a jessie today on a ssd, then dist-upgraded to
sid, now I've two installation with (almost) same version of debs, the
new one segfault, the old one doesn't.

So far I've only seen the problem with chromium, using --incognito
doesn't segfault.

I'm investigating the difference between the two installation, if
someone have some suggestion for comparison let me know.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#739054: Xserver 1.15 crash with fglrx 14.1 beta 1.3

[Alex Andreotti]

I've downgraded *xserver*xorg* and *fglrx* to /testing and set
fglrx-driver fglrx-modules-dkms fglrx-source on hold (not sure which
is really needed to be downgraded and hold), got the desktop working
but now not sure where to look to know when I can unhold and upgrade
fglrx again, currently just keeping an eye on this bug page, any
suggestion? Thanks


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#739054: fglrx-driver: fglrx segfault

[Alex Andreotti]

Package: fglrx-driver
Version: 1:14.1~beta1.3-1
Severity: important

Dear Maintainer,


   * What led up to the situation?

   dist-upgrade

   * What was the outcome of this action?

   no desktop (Xorg exit), vt still working

   * What outcome did you expect instead?

   working desktop...

-- Package-specific info:
Full fglrx package list:
ii  fglrx-atieventsd   1:14.1~beta1.3-1   i386  
 events daemon for the non-free ATI/AMD RadeonHD display driver
ii  fglrx-control  1:14.1~beta1.3-1   i386  
 control panel for the non-free ATI/AMD RadeonHD display driver
ii  fglrx-driver   1:14.1~beta1.3-1   i386  
 non-free ATI/AMD RadeonHD display driver
rc  fglrx-kernel-3.10-3-686-pae1:13.4-3+3.10.11-1 i386  
 FGLRX binary kernel module for Linux 3.10-3-686-pae
rc  fglrx-kernel-3.10-3-rt-686-pae 1:13.4-3+3.10.11-1 i386  
 FGLRX binary kernel module for Linux 3.10-3-rt-686-pae
ii  fglrx-kernel-3.11-2-686-pae1:14.1~beta1.3-1+3.11. i386  
 FGLRX binary kernel module for Linux 3.11-2-686-pae
rc  fglrx-kernel-3.2.0-4-686-pae   1:13.4-2+3.2.41-2  i386  
 FGLRX binary kernel module for Linux 3.2.0-4-686-pae
ii  fglrx-modules-dkms 1:14.1~beta1.3-1   i386  
 dkms module source for the non-free ATI/AMD RadeonHD display driver
ii  fglrx-source   1:14.1~beta1.3-1   i386  
 kernel module source for the non-free ATI/AMD RadeonHD display driver
ii  glx-alternative-fglrx  0.4.1  i386  
 allows the selection of FGLRX as GLX provider
ii  libfglrx:i386  1:14.1~beta1.3-1   i386  
 non-free ATI/AMD RadeonHD display driver (runtime libraries)
ii  libfglrx-amdxvba1:i386 1:14.1~beta1.3-1   i386  
 AMD XvBA (X-Video Bitstream Acceleration) runtime libraries
ii  libgl1-fglrx-glx:i386  1:14.1~beta1.3-1   i386  
 proprietary libGL for the non-free ATI/AMD RadeonHD display driver

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 
00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e199]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 46
Region 0: Memory at e000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at fe9c (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at c000 [size=256]
Expansion ROM at fe9a [disabled] [size=128K]
Capabilities: access denied
Kernel driver in use: fglrx_pci


DRM and fglrx Informations from dmesg:
[0.850073] Linux agpgart interface v0.103
[5.938579] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, 
Starnberg, GERMANY' taints kernel.
[5.953314] 6[fglrx] Maximum main memory to use for locked dma buffers: 
3887 MBytes.
[5.953524] 6[fglrx]   vendor: 1002 device: 6779 count: 1
[5.953950] 6[fglrx] ioport: bar 4, base 0xc000, size: 0x100
[5.954280] 6[fglrx] Kernel PAT support is enabled
[5.954302] 6[fglrx] module loaded - fglrx 13.35.5 [Jan 29 2014] with 1 
minors
[   18.197144] fglrx_pci :01:00.0: irq 46 for MSI/MSI-X
[   18.198641] 6[fglrx] Firegl kernel thread PID: 2271
[   18.198770] 6[fglrx] Firegl kernel thread PID: 2272
[   18.198898] 6[fglrx] Firegl kernel thread PID: 2273
[   18.199063] 6[fglrx] IRQ 46 Enabled
[   18.248258] 6[fglrx] Reserved FB block: Shared offset:0, size:100 
[   18.248261] 6[fglrx] Reserved FB block: Unshared offset:f884000, size:4000 
[   18.248263] 6[fglrx] Reserved FB block: Unshared offset:f888000, 
size:478000 
[   18.248265] 6[fglrx] Reserved FB block: Unshared offset:7fff4000, 
size:c000 

Xorg X server configuration file status:
-rw-r--r-- 1 root root 669 Aug 24 12:57 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
#Section ServerLayout
#   Identifier  Default Layout
#   Screen  0 Default Screen 0 0
#EndSection

#Section Monitor
#   Identifier   0-CRT1
#   Option  PreferredMode 1920x1080
#EndSection

Section Monitor
Identifier   0-DFP2
Option  PreferredMode 1680x1050
EndSection

Section Device
Identifier  aticonfig-Device[0]-0
Driver  fglrx
Option  Monitor-CRT1 0-CRT1
#   Option  Monitor-DFP2 0-DFP2
#   BusID   PCI:1:0:0
EndSection

Section Screen
Identifier Default Screen
Device 

Bug#729765: fglrx-modules-dkms: fglrx module does not compile on recent x86 kernels

[Alex Andreotti]

As a workaround (suggested somewhere) just patched
modules/fglrx/kcl_iommu.c:KCL_IOMMU_CheckInfo() to return 0.
It build and seem to work (desktop's windows seem to refresh correctly
and acceleration is enabled).


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#729765: fglrx-modules-dkms: fglrx module does not compile on recent x86 kernels

[Alex Andreotti]

Package: fglrx-driver
Version: 1:13.8~beta1-3
Followup-For: Bug #729765

Dear Maintainer,

today I've upgraded fglrx-driver and got this same problem (iommu while 
building the module).
A binary version of the driver seem to be loaded (from Xorg log) but it is very 
slow refreshing desktop's windows, so as usual I've tried to build fglrx-driver 
with module assistant.
I've tried both 3.10-3-686-pae and 3.11-2-686-pae kernels but got same result.


-- Package-specific info:
Full fglrx package list:
ii  fglrx-atieventsd  1:13.8~beta1-3i386  events daemon 
for the non-free ATI/AMD RadeonHD display 
ii  fglrx-control 1:13.8~beta1-3i386  control panel 
for the non-free ATI/AMD RadeonHD display 
ii  fglrx-driver  1:13.8~beta1-3i386  non-free 
ATI/AMD RadeonHD display driver
ii  fglrx-kernel-3.10-3-686-p 1:13.4-3+3.10.11- i386  FGLRX binary 
kernel module for Linux 3.10-3-686-pae
rc  fglrx-kernel-3.10-3-rt-68 1:13.4-3+3.10.11- i386  FGLRX binary 
kernel module for Linux 3.10-3-rt-686-pae
rc  fglrx-kernel-3.2.0-4-686- 1:13.4-2+3.2.41-2 i386  FGLRX binary 
kernel module for Linux 3.2.0-4-686-pae
ii  fglrx-modules-dkms1:13.8~beta1-3i386  dkms module 
source for the non-free ATI/AMD RadeonHD dis
ii  fglrx-source  1:13.8~beta1-3i386  kernel module 
source for the non-free ATI/AMD RadeonHD d
ii  glx-alternative-fglrx 0.4.1 i386  allows the 
selection of FGLRX as GLX provider
ii  libfglrx:i386 1:13.8~beta1-3i386  non-free 
ATI/AMD RadeonHD display driver (runtime librar
ii  libfglrx-amdxvba1:i3861:13.8~beta1-3i386  AMD XvBA 
(X-Video Bitstream Acceleration) runtime librar
ii  libgl1-fglrx-glx:i386 1:13.8~beta1-3i386  proprietary 
libGL for the non-free ATI/AMD RadeonHD disp

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos [Radeon HD 6450/7450/8450]

DRM and fglrx Informations from dmesg:
[0.849396] Linux agpgart interface v0.103

Xorg X server configuration file status:
-rw-r--r-- 1 root root 669 Aug 24 12:57 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
#Section ServerLayout
#   Identifier  Default Layout
#   Screen  0 Default Screen 0 0
#EndSection

#Section Monitor
#   Identifier   0-CRT1
#   Option  PreferredMode 1920x1080
#EndSection

Section Monitor
Identifier   0-DFP2
Option  PreferredMode 1680x1050
EndSection

Section Device
Identifier  aticonfig-Device[0]-0
Driver  fglrx
Option  Monitor-CRT1 0-CRT1
#   Option  Monitor-DFP2 0-DFP2
#   BusID   PCI:1:0:0
EndSection

Section Screen
Identifier Default Screen
Device aticonfig-Device[0]-0
DefaultDepth 24
SubSection Display
Virtual   3600 1920
Depth 24
EndSubSection
EndSection



Xorg X server log files on system:
-rw-r--r-- 1 root root 38143 Dec  3 09:20 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:
[14.508] 
X.Org X Server 1.12.4
Release Date: 2012-08-27
[14.508] X Protocol Version 11, Revision 0
[14.508] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
[14.508] Current Operating System: Linux hellspawn 3.11-2-686-pae #1 SMP 
Debian 3.11.8-1 (2013-11-13) i686
[14.508] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11-2-686-pae 
root=UUID=29feb66c-8e75-493f-86d0-c5f0df9f3765 ro noresume gfxpayload=true quiet
[14.508] Build Date: 22 August 2013  05:27:51PM
[14.508] xorg-server 2:1.12.4-6.2 (Michael Stapelberg 
stapelb...@debian.org) 
[14.508] Current version of pixman: 0.30.2
[14.508]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[14.508] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[14.508] (==) Log file: /var/log/Xorg.0.log, Time: Tue Dec  3 09:00:14 
2013
[14.531] (==) Using config file: /etc/X11/xorg.conf
[14.531] (==) Using system config directory /usr/share/X11/xorg.conf.d
[14.637] (==) No Layout section.  Using the first Screen section.
[14.637] (**) |--Screen Default Screen (0)
[14.637] (**) |   |--Monitor default monitor
[14.638] (**) |   |--Device aticonfig-Device[0]-0
[14.638] (==) No monitor specified for screen Default Screen.
Using a default monitor configuration.
[14.638] (==) Automatically adding devices
[14.638] (==) Automatically enabling devices
[14.665] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[14.665]Entry deleted from font path.
[14.665] (WW) The 

Bug#653110: z88dk-bin: workaround

[Alex Andreotti]

Package: z88dk-bin
Version: 1.8.ds1-9
Followup-For: Bug #653110

..lnx DESTDIR are translated to a wrong temporary full path in z88dk-data's 
.cfg files
as temporary workaround just remove the wrong prefix:
dpkg -L z88dk-data | grep '\.cfg$' | xargs sudo sed -i 
's?/tmp/buildd/z88dk-1.8.ds1/debian/tmp??'

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages z88dk-bin depends on:
ii  libc6   2.13-30
ii  z88dk-data  1.8.ds1-9

z88dk-bin recommends no packages.

z88dk-bin suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#484164: sdlgfx: out of date, mainstream reached 2.0.17. please, need arcColor function here

[Alex Andreotti]

Package: sdlgfx
Severity: wishlist

The mainstream version 2.0.17 added circle/arc functions, would be nice to have 
in the debian package too.
Thanks
Regards


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/4 CPU cores)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]