Bug#926212: gnome-shell crashed (segfault)

2019-04-06 Thread Gunter Grodotzki
Thanks Bernhard for the help. I am only realising now that even though I am 
running “testing” that the bug is most likely due to upstream.

> On 05 Apr 2019, at 22:01, Bernhard Übelacker  wrote:
> 
> Hello Guenter Grodotzki,
> I just tried to help triage that issue.
> 
> For some reason you just added the segfault line.
> I assume there was one line following starting with "Code:".
> Please add that line too when submitting bugs.
> 
> As this information is still kind of small, you might consider
> to install a coredump collector like systemd-coredump.
> That way you could list crashes of the current boot by:
>coredumpctl list
> And some more information is entered into journal that would
> help a lot to triage such crashes ("Stack trace of thread...".
>journalctl --no-pager
> 
> Even better would be if you could install the debug symbol
> packages e.g. gnome-shell-dbgsym like described in [1].
> Then following commands should print a backtrace
> with source line information.
> 
> 
> Nevertheless, I tried if that little information brings
> us somewhere and I think it leads into function
> shell_app_dispose. There, I assume, we reach line 1485,
> unfortunately dereferencing a null pointer
> in app->running_state->windows.
> 
> 
> There are some upstream bugs [2], which point to that line.
> Unfortunately it looks like there is no fix yet commited.
> 
> 
> But, if I am right, something like this could
> help already (untested)?
> 
>   while (app->running_state)
> -_shell_app_remove_window (app, app->running_state->windows->data);
> +if (app->running_state->windows) _shell_app_remove_window (app, 
> app->running_state->windows->data);
> 
>   /* We should have been transitioned when we removed all of our windows 
> */
> 
> 
> Kind regards,
> Bernhard
> 
> 
> [1] 
> https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
> [2] https://gitlab.gnome.org/GNOME/gnome-shell/issues/590
>https://gitlab.gnome.org/GNOME/gnome-shell/issues/766
>https://gitlab.gnome.org/GNOME/gnome-shell/issues/750
>https://gitlab.gnome.org/GNOME/gnome-shell/issues/918
>https://gitlab.gnome.org/GNOME/gnome-shell/issues/822
>https://bugzilla.redhat.com/show_bug.cgi?id=1654420#c22
> 
> 
> (gdb) list shell-app.c:1477,1492
> 1477static void
> 1478shell_app_dispose (GObject *object)
> 1479{
> 1480  ShellApp *app = SHELL_APP (object);
> 1481
> 1482  g_clear_object (&app->info);
> 1483
> 1484  while (app->running_state)
> 1485_shell_app_remove_window (app, app->running_state->windows->data);
> 1486
> 1487  /* We should have been transitioned when we removed all of our 
> windows */
> 1488  g_assert (app->state == SHELL_APP_STATE_STOPPED);
> 1489  g_assert (app->running_state == NULL);
> 1490
> 1491  G_OBJECT_CLASS(shell_app_parent_class)->dispose (object);
> 1492}
> 



Bug#926120: mirror submission for openmirror.fi

2019-03-31 Thread Gunter Grodotzki
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: openmirror.fi
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Maintainer: Gunter Grodotzki 
Country: FI Finland
Location: Helsinki
Comment: Hi,
 
 I would like to "officially" add my mirror: http://openmirror.fi/ to your 
list. The setup of the server is completely open source: 
https://github.com/openmirror/openmirror and also completely automated via 
travis-ci. This is to keep the whole setup transparent and will also give a 
sense of "activity" towards the user.
 
 My main reasons to run this mirror:
 
 - I wanted to have a "zero compromise" mirror when it comes to offering (e.g. 
I offer cd-images, archive and main - would even like to go further and mirror 
testing cd-images and bpo, but have not found any proper documentation on that 
yet)
 - I would like to give back to the community - being a happy Debian user 
(desktop and server) for more than 10 years
 - I would like to use this as a test project for an automated mirror server 
and gain experience on running a (hopefully) high traffic website
 
 It is currently funded from my personal projects, but the costs are kept at a 
minimum. so I am not seeing any issues funding this for a longterm. The "cost 
of my personal time" would deplete rather quicker than the actual server costs 
- which is why I am hoping by hosting it on github might attract other 
volunteers.
 
 Looking forward to some feedback :)
 
 Cheers,
 Gunter




Trace Url: http://openmirror.fi/debian/project/trace/
Trace Url: http://openmirror.fi/debian/project/trace/ftp-master.debian.org
Trace Url: http://openmirror.fi/debian/project/trace/openmirror.fi



Bug#925483: tilda: does not start (segfault)

2019-03-25 Thread Gunter Grodotzki
Thanks Bernhard for the help!

You are right, I am running Gnome/Wayland, and this seems to be
unsupported.



Bug#774195: libnss3: libpkix incorrect prefers older, weaker certs over stronger, newer certs

2015-06-17 Thread Gunter Grodotzki

Hi all,

It would be great if we could get this released on Jessie as quick as 
possible - other Bugtrackers even suggest updating nss on Wheezy as well.


The security point asside, this currently causes chrome to show a "red 
padlock", thus making the user believe that the website is not 
trustworthy anymore.


Is there any reason why this can not be released?

Regards,
Gunter


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



Bug#781942: dovecot-antispam: crashes dovecot imap

2015-04-05 Thread Gunter Grodotzki
Package: dovecot-antispam
Version: 2.0+20130912-1~bpo70+1
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

dovecot-antispam just does not work anymore with dovecot 2.2
The error line reads:
Apr  5 10:10:54 hXXX dovecot: imap(XXX): Fatal: master: service(imap): child 
9207 returned error 3

When I deactivate the plugin it works again.
Using the following config:
plugin {
antispam_backend = mailtrain
antispam_spam   = Spam
antispam_trash  = Trash
antispam_mail_spam = learn_spam
antispam_mail_notspam = learn_ham
antispam_mail_sendmail = /usr/bin/rspamc
antispam_mail_sendmail_args = -h;127.0.0.1:11334
}


-- System Information:
Debian Release: 7.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.41-042stab092.3 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dovecot-antispam depends on:
ii  dovecot-core [dovecot-abi-2.2.abiv13]  1:2.2.13-11~bpo70+1
ii  dovecot-imapd  1:2.2.13-11~bpo70+1
ii  libc6  2.13-38+deb7u8

dovecot-antispam recommends no packages.

Versions of packages dovecot-antispam suggests:
pn  crm114 | dspam  

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