On Fri 21 Dec 2018 at 18:14:56 +, Brian Potkin wrote:
> On Fri 21 Dec 2018 at 16:52:24 +, Brian Potkin wrote:
>
> > On Fri 21 Dec 2018 at 03:40:56 +0100, Bernhard Übelacker wrote:
> >
> > > Maybe you still can test my proposed changes in message [#36-#3] ?
> >
> > I dusted off everythin
Hello Brian Potkin,
you might have a look at following commands to build a
complete local cups-browsed package with the upstream
patch included.
That may work better, as a plain make built shared lib
might be not enough compatible with the executable from
the debian package.
Just if you do not wa
On Fri 21 Dec 2018 at 20:39:55 +0100, Till Kamppeter wrote:
> Bernhard, thank you for your patches. I have applied them (slightly changed)
> to cups-browsed upstream. They actually do not do any functional changes, so
> if the BrowseFilter facility does not work as expected, this is another bug
>
Bernhard, thank you for your patches. I have applied them (slightly
changed) to cups-browsed upstream. They actually do not do any
functional changes, so if the BrowseFilter facility does not work as
expected, this is another bug and this bug was probably there before.
Till
On Fri 21 Dec 2018 at 16:52:24 +, Brian Potkin wrote:
> On Fri 21 Dec 2018 at 03:40:56 +0100, Bernhard Übelacker wrote:
>
> > Maybe you still can test my proposed changes in message [#36-#3] ?
>
> I dusted off everything I know about patching and compiling (which can
> be written on the back
On Fri 21 Dec 2018 at 03:40:56 +0100, Bernhard Übelacker wrote:
> Hello Brian Potkin,
>
> > You got exactly what I was shown.
>
> You are right, and I just wanted to make a point how someone
> who want to help can start right away with all the needed information.
>
> > Do you really think repor
Hello Brian Potkin,
> You got exactly what I was shown.
You are right, and I just wanted to make a point how someone
who want to help can start right away with all the needed information.
> Do you really think reportbug would have added an imortant clue? It
> was clear that my original report wa
On Thu 20 Dec 2018 at 20:28:08 +0100, Bernhard Übelacker wrote:
> Hello Brian Potkin,
>
> > Does the efficient and correct operation of a program depend on whether
> > the system is amd64 or i386? Most of my machines are i386 only and, to
> > my knowledge, Debian has not abandoned this architectu
Control: found cups-browsed 1.11.6-3
And probably I was not clear in my message #36:
- I may have found something that could lead to your sitation,
and attached a change that might avoid it.
- I could not reproduce the crash because I do not have such printers.
- Maintainer or Upstream are need
Hello Brian Potkin,
> Does the efficient and correct operation of a program depend on whether
> the system is amd64 or i386? Most of my machines are i386 only and, to
> my knowledge, Debian has not abandoned this architecture.
>
> I was probably incorrect in thinking I had tested the offending di
On Thu 20 Dec 2018 at 19:05:16 +0100, Bernhard Übelacker wrote:
> Dear Maintainer, hello Brian Potkin,
>
> > Thanks. All this is very new to me. I hope it is what is needed and
> >
> > someone can interpret it!
>
> Thanks for the information,
Dear Maintainer, hello Brian Potkin,
> Thanks. All this is very new to me. I hope it is what is needed and
>
> someone can interpret it!
Thanks for the information, in my first attempts I was under the impression
you are on a amd64 system becau
On Thu 20 Dec 2018 at 14:36:03 +0100, Bernhard Übelacker wrote:
> Hello Brian Potkin,
> I tried to have a look in a unstable VM, but unfortunately
> I get different offsets ...
>
> You might add the output of this command:
> dpkg -l | grep -E "cups-browsed|libc6|libglib|libavahi|libdbus" | sort
Hello Brian Potkin,
I tried to have a look in a unstable VM, but unfortunately
I get different offsets ...
You might add the output of this command:
dpkg -l | grep -E "cups-browsed|libc6|libglib|libavahi|libdbus" | sort
And what output did you receive from this command
coredumpctl list
and f
On Tue 18 Dec 2018 at 19:15:27 +0100, Bernhard Übelacker wrote:
> Hello Brian Potkin,
> you might want to install a core dump collector like systemd-coredump.
>
> With that in place you might get a more verbose message in journalctl.
It is more verbose:
Dec 20 11:15:14 test systemd[1]: Reloadin
Hello Brian Potkin,
you might want to install a core dump collector like systemd-coredump.
With that in place you might get a more verbose message in journalctl.
Also a later inspection of the coredump might be possible:
coredumpctl list
coredumpctl gdb [PID]
bt
quit
And even better when hav
Package: cups-browsed
Version: 1.21.6-2
Severity: normal
Tags: upstream
cups-browsed.conf and a log are attached.
Whilst taking another look at #908573 the service fails to restart
when the only uncommented line for BrowseFilter has "pdl postscript".
journalctl shows
Dec 18 11:21:22 test syste
17 matches
Mail list logo
