Yavor,
you really did it!
On 11/20/24 02:23, Yavor Doganov wrote:
Please test the attached patch (it solves the problem for me):
$ apt-get source addresses-for-gnustep && cd addresses-for-gnustep-*
(Make sure it's 0.4.8-5; the trixie/sid version)
$ cp /path/to/1087735.patch debian/patches
$ ech
Hi Riccardo,
now let's hope the VCF Inspector can be fixed somehow.
On 11/20/24 01:30, Riccardo Mottola wrote:
it is very likely that you nailed it to this VCF Inspector!
now.. many things could be. The source code has a bug or bitrotted.
It was not rebuilt properly, ecc,
I suppose this is th
Hi Riccardo,
thanks for your observations!
Looks like finally found the root cause for making GWorkspace
malfunction on i386!
On 11/19/24 11:29, Riccardo Mottola wrote:
I see something very strange. As information, do you have the Content
Inspector open? I suppose not.. in case don't.
I don't
On 11/18/24 22:24, Yavor Doganov wrote:
Paul Seelig wrote:
The screenshot provided is from a bookworm system with the
backported GNUstep packages from trixie.
Oh, I missed this. A "backport" means to rebuild the package for an
older distro release using the toolchain of the older re
On 11/18/24 22:02, Yavor Doganov wrote:
Continuing.
Thanks but this is not useful. When you hit the breakpoint, type
"bt" at the GDB prompt, not "c".
This time i set up a fresh system installation using a
debian-12.8.0-i386-netinst.iso which was subsequently dist-upgraded to
trixie.
This was to
On 11/18/24 07:55, Yavor Doganov wrote:
Control: severity -1 grave
Control: tags -1 + moreinfo
Paul Seelig wrote:
[ snip ]
A screenshot is available at
http://wmlive.rumbero.org/NSInvalidArgumentException.png for a
visual depiction of the error message.
This shows NSContstantString(instance
Package: debian-installer
Severity: grave
X-Debbugs-Cc: think...@rumbero.org
Hi all,
using the xfce4 based RC2 live ISO image[1], on a Thinkpad T480 (16GB RAM/256GB
NVME/INTEL GRAPHICS ONLY) installation of Debian in an luks encrypted LVM was
performed.
Apparently, the required cryptsetup-init
Hi,
i was bitten by the same issue.
Analyzing the various /tmp/fmtutil.* files created during installation
trials, i stumbled over the line stating:
! I can't find file `syst-tex.mkii'.
Checking with apt-file, syst-tex.mkii appeared to be contained in two
packages, namely 'context' and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Hugo,
this is already fixed 0.6.2 in unstable, so either just wait for it to
arrive in testing, or manually install it from unstable.
Me too messages are okay, but previous checking for a newer release
would defintely be recommendable. ;)
Cheer
Hello Jakub,
i am unable to reproduce this behavior, and i think you should
definitely abstain from manually editing this configuration file.
You are not supposed to touch any configuration file which is handled
via debconf.
Please try to purge the package from your system, and then reinstall and
On 12/10/2009 03:34 AM, Marco d'Itri wrote:
> But was bindv6only=1 set on the client or on the server?
>
Both server and client had this very same setting and, acting as both
server and client, none of both could see each other anymore. Once i
removed the file from one of them, and after a reboot,
On 12/10/2009 01:53 AM, Marco d'Itri wrote:
> XDMCP is a protocol, which package is actually broken and how?
>
It was not possible anymore to connect to a remote system via xdmcp both
via gdm and Xephyr. The remote X server appeared to have become
completely unvisible within the local network.
reopen 560238 !
# thanks
Hi,
just want to remark that i actualy had to move the newly created file
/etc/sysctl.d/bindv6only.conf out of the way in order to restore the
xdmcp functionality it completely broke.
If you introduce new configuration files containing untested settings
which might break
On 11/29/2009 09:10 PM, Felix Zielcke wrote:
> But if you only have ASCII chars in the menu entry names then it
> shouldn't at all make a difference.
>
Yes, the files are all ASCII only.
> This shows if debconf thinks if you saw that prompt already or not
> echo FGET grub-pc/install_devices see
On 11/29/2009 09:08 AM, Felix Zielcke wrote:
> In the 24-1 one there was a syntax error in it which completely broke
> our parser. But unfortunately nobody thought that the grub.cfg could be
> just wrong and not the C code in GRUB itself.
>
After having successfully rebooted today with 24-2, i too
Well, if upgrading to 25-1 does not by itself result in a working boot
configuration, it defintely shouldn't be the user who should be held
responsible to make sure that it works. As an end user, i do expect
that the upgrade does work without any further intervention. If 25-1
does not work althoug
Just for the record, my old ThinkPad T23 become unbootable with the very
same symptons after upgrading it to this 1.97+20091125-1 version.
Luckily i still had 1.97+20091124-2 in the apt cache, and manually
downgrading to it "solved" the issue for the time being.
To me it looks like something went
Hello Frank,
thanks a lot for your actions! Your NMU is very appreciated!
Since my move from Germany to Spain one year ago i have almost no time
to care for this package. I'm looking forward to be able to take better
care again starting end of next January, when the biggest burdens here
are f
Hi Gerfried!
On Mon, Jan 23, 2006 at 10:51:52PM +0100, Gerfried Fuchs wrote:
>
> I'm not sure if you just have forgotten about this bugreport,
>
Sorry, but i've no time to care about this. Since the bugs in question
don't render the functionality of the package unusable, i don't consider
this t
19 matches
Mail list logo
