Bug#960282: [Pkg-zsh-devel] Bug#960282: Bug#960282: zsh: completion error with non exsiting files since deca7c928520fba5a73383f1cac0b3ace8e0e45d

2020-05-11 Thread TS
Hello Daniel, Hello Axel, >> _arguments:comparguments:393: too many arguments > In version 5.8-4, line 393 of _arguments doesn't call > comparguments. >> after deleting $opt_args_use_NUL_separators from _arguments: > You seem to be using _arguments from git HEAD with zsh 5.8-4. > That is not a

Bug#960282: zsh: completion error with non exsiting files since deca7c928520fba5a73383f1cac0b3ace8e0e45d

2020-05-11 Thread TS
Package: zsh Version: 5.8-4 Severity: normal Hello Zsh devs, completion error with non existing files since upstream commit deca7c928520fba5a73383f1cac0b3ace8e0e45d % rm asdhg _arguments:comparguments:393: too many arguments _rm:72: line: attempt to assign array value to non-array

Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc

2020-04-01 Thread TS
Control: found -1 src:linux 5.5.13-2 thanks Hi, linux 5.5.13-2 still does not boot on this computer. Adding 'nomodeset i915.modeset=0' to boot options solves that. This time full Hardware overview attached. Thanks. kind regards, Thilo Package: src:linux Version: 5.5.13-2 Severity:

Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc

2020-02-24 Thread TS
time ago, can't remember if there were also those: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' lines. This 2nd machine is also amd64. regards TS

Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc

2020-02-21 Thread TS
Hi Ben, Ben Hutchings schrieb/wrote: > Control: reassign -1 src:linux 5.4.19-1 > Control: severity -1 important > Control: tag -1 moreinfo > > On Fri, 2020-02-21 at 15:39 +0100, TS wrote: >> Package: linux-source-5.4 >> Version: linux 5.4.0-4 >> Severity: ser

Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc

2020-02-21 Thread TS
Package: linux-source-5.4 Version: linux 5.4.0-4 Severity: serious Justification: 1 Hi did upgrade to sid. linux 5.4.0-4 does not boot on this pc. Booting 4.19.0-8-amd64 instead brings up running system. The boot prozess breaks after grub. Blank screen, nothing happens. With 4.19.0-8-amd64

Bug#903393: [initramfs-tools] update-initramfs -u warns: Unknown X keysym "dead_belowmacron"

2020-01-09 Thread TS
On Thu, 25 Apr 2019 15:55:48 +0200 at46 wrote: > Seems the warnings are gone. Neither with update-initramfs nor with > setupcon I get the "WARNING: Unknown X keysym "dead_belowmacron"" > messages anymore. > > Axel Hi, for me this message still is displayed: # command update-initramfs -u ||

Bug#922281: Fw: SD Card Format Bug

2019-02-13 Thread TS Brownie
Package: base Version: all 1) I have repeated this on 3 different SD cards (16 GB), using windows 7 and 10 and 3 different computers and 2 SD card readers. Both Pi 2 and 3. 2) I used to be a software engineer 3) Happens on Jessie and Stretch Summary: Load Debian (usually NOOB or package with

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

2018-12-04 Thread TS
TS schrieb/wrote: -- -- > For completeness: > % lspci | grep -i vga > 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset > Integrated Graphics Controller (rev 07) Two machines with: # unameALL Linux desk 4.18.0-3-amd64 #1 SMP Debian 4.18.20-2 (2018-1

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

2018-12-04 Thread TS
Bjørn Mork schrieb/wrote: -- -- > Given this, there is an extremely suspicious commit added in v4.18.20: > > 06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for > gen4/gen5") -- -- > Still, I do think that there is good reason to simply try a revert of that > commit. In

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

2018-12-03 Thread TS
Ben Hutchings schrieb/wrote: -- -- >> Since the issue happens very early in boot process debugging is quit >> difficult. >> Assistance with further debugging is required if you need additional >> informations. > > You can use a serial console or netconsole to send the kernel log to > another

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

2018-11-25 Thread TS
Amy Kos schrieb/wrote: > Could be graphics related, boot stops at: > > fb: switching to inteldrmfb from EFI VGA > > Disabling kernel mode setting with parameter nomodeset boots to tty. > confirming, adding 'nomodeset' to linux boot options lets linux-image-4.18.0-3-amd64 boot. Thanks Amy for

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

2018-11-23 Thread TS
Package: src:linux Version: 4.18.20-1 Severity: critical Justification: breaks the whole system Dear Maintainers, linux-image-4.18.0-3-amd64 does not boot on this computer. After grub shortly cursor is blinking upper left (when usually the initrd is deflating and systemd starts). After that

Bug#886389: Bug#912144: grub2-common: marks kernel update scripts falsely as obsolete conffiles

2018-10-29 Thread TS
TS schrieb/wrote: > Hello, > % dpkg-query -W -f='${Conffiles}\n' | grep -E '(grub|archive).*obsolete$' > /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg > 64d549adf06d734bb947d742898d9a19 obsolete > /etc/apt/trusted.gpg.d/debian-archive-wheez

Bug#886389: Bug#912144: grub2-common: marks kernel update scripts falsely as obsolete conffiles

2018-10-29 Thread TS
Hello, >>> since fix for #910959 grub2-common marks kernel update scripts falsely as >>> obsolete conffiles. >>> >>> % dpkg-query -W -f='${Conffiles}\n' | grep 'grub.*obsolete$' >>> /etc/kernel/postrm.d/zz-update-grub 536d9d45e3e547638db3c5d58a925b6c >>> obsolete >>>

Bug#912144: grub2-common: marks kernel update scripts falsely as obsolete conffiles

2018-10-28 Thread TS
Package: grub2-common Version: 2.02+dfsg1-7 Severity: normal Hello, since fix for #910959 grub2-common marks kernel update scripts falsely as obsolete conffiles. % dpkg-query -W -f='${Conffiles}\n' | grep 'grub.*obsolete$' /etc/kernel/postrm.d/zz-update-grub 536d9d45e3e547638db3c5d58a925b6c

Bug#909841: fc-cache: failed to write cache

2018-09-29 Thread TS
Hello, Holger Schröder schrieb/wrote: > There's something wrong with the last update to 2.13.1-1 anyway. I > currently have 14350 files under /var/cache/fontconfig = 7.5 GB. And it > is getting more and more.  Deleting the files doesn't help either, the > propagation starts all over again. i

Bug#909841: fc-cache: failed to write cache

2018-09-29 Thread TS
Hello, for sake of completeness, the pattern "${(u)$(fc-list ':' file 2> /dev/null):h}" resolvs to this directories on my system: # p ${(u)$(fc-list ':' file 2> /dev/null):h} /usr/share/fonts/truetype/noto /usr/share/texmf/fonts/opentype/public/tex-gyre /usr/share/fonts/truetype/liberation

Bug#909841: fc-cache: failed to write cache

2018-09-29 Thread TS
Package: fontconfig Version: 2.13.1-1 Severity: normal Dear Maintainer, not sure when this started, but when running 'fc-cache -frv' it now reports: 'failed to write cache'. e.g.: # /usr/bin/fc-cache -frv | /bin/grep fail /usr/share/fonts/X11/cyrillic: failed to write cache

Bug#908818: [Pkg-zsh-devel] Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-17 Thread TS
Daniel Shahaf schrieb/wrote: -- -- > For the time being I did a quick build with that commit backported and > uploaded it to https://home.apache.org/~danielsh/zsh/debian/ . Hello, Just to be sure i again tried stock debian zsh 5.6.2 which still fails for me. The version you uploaded fixes it

Bug#908818: [Pkg-zsh-devel] Bug#908818: Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-17 Thread TS
Hello, Daniel Shahaf schrieb/wrote: > Upstream has committed 551ff842721d6ca83727dbe6cd40178f46cc8201 (43464: > Another attachtty() fix). I haven't been able to reproduce the issue so > I can't confirm that commit fixes it. Thank your for your support. Really i mean this. But There are FAQs

Bug#908818: [Pkg-zsh-devel] Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-15 Thread TS
-- -- > Could you please send a bug report upstream (zsh-work...@zsh.org)? > Ideally, the bug report would include a reproduction script that sets up > a new temporary directory, creates a minimal zshrc in it, and runs > 'ZDOTDIR=/path/to/dir zsh -d' and provokes the bug. > > Thanks! > >

Bug#908818: [Pkg-zsh-devel] Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-15 Thread TS
-- -- > I can't reproduce the bug with a zshrc that contains nothing but an > (unconditional) zmodload zsh/zprof. I'm using a self-compiled > static build from upstream git, not a package build. > > Could you please send a bug report upstream (zsh-work...@zsh.org)? > Ideally, the bug report

Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-15 Thread TS
-- -- > up to 5.5.1-1 seem fine, problem starts with 5.6 for the record what zprofile does... zprofile() { ZSH_PROFILE_RC=1 zsh "$@" } ...is it activates this code snipped in my .zshrc: # # zprofile # (( ${+ZSH_PROFILE_RC} )) && builtin zmodload zsh/zprof in case you want test

Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-15 Thread TS
-- -- > After downgrading Zsh to 5.4.2-3... -- -- Tested with 5.5.1-1 % asi zsh izsh | 5.5.1-1 | 5.6.2-1 izsh-common | 5.5.1-1 | 5.6.2-1 izsh-doc | 5.5.1-1 | 5.6.2-1 > > > ...i am not able to reproduce the "[7] + 10408 suspended (tty output)" thing.

Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-15 Thread TS
TS schrieb/wrote: > Hello Axel, > > thanks for uploading 5.6.2, but no luck. > > I still get reliable: > > % zprofile > [7] + 10408 suspended (tty output) > > % pZSH_VERSION > scalar-readonly ZSH_VERSION='5.6.2' After downgrading Zsh to 5.4.2-3... % asi

Bug#908818: Reopen: #908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-15 Thread TS
Hello Axel, thanks for uploading 5.6.2, but no luck. I still get reliable: % zprofile [7] + 10408 suspended (tty output) % pZSH_VERSION scalar-readonly ZSH_VERSION='5.6.2' Debian Bug Tracking System schrieb/wrote: > This is an automatic notification regarding your Bug report > which was

Bug#908818: [Pkg-zsh-devel] Bug#908818: Bug#908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-14 Thread TS
Hello, Daniel Shahaf schrieb/wrote: -- -- > If you'd like to build it yourself, then first of all thank you for the > willingness. The procedure is documented on > http://ircbots.debian.net/factoids/factoid.php?key=package+recompile ; > between step 4 and step 5 you should apply the patch,

Bug#908818: [Pkg-zsh-devel] Bug#908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-14 Thread TS
Hi Daniel, Daniel Shahaf schrieb/wrote: -- -- > It will be included in upstream 5.6.2 which is due to be released soon. > It would be great if you could test the issue with this patch and > report back. > > Cheers, > > Daniel I am not familar with building from source. Need to dig through

Bug#908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-14 Thread TS
Package: zsh Version: 5.6.1-1 Severity: important Hello, sorry for the bad bug description, not sure how to tell it better. running the function zprofile() { ZSH_PROFILE_RC=1 zsh "$@" } for profiling Zsh startup performance i now get: % zprofile [7] + 23074 suspended (tty output) then

Bug#622933: [Pkg-zsh-devel] Bug#622933: Bug#622933: zsh: Enable completions by default, unless skip_global_compinit is set

2018-09-10 Thread TS
Hello Frank, Hello Daniel, nice to see Zsh is actively maintained in Debian. ;) Merely i was referring that the intention of the original patch as i understand was to make the whole pattern case-insensitive, not only the first part of it. Just documented public in the bug report for other

Bug#622933: zsh: Enable completions by default, unless skip_global_compinit is set

2018-09-09 Thread TS
Hello Frank, again i learned sth. useful. THANKS! Replying here because i think the patch that never got applied should look like: - ((#i)on|yes|enable|1) ;; + ((#i)(on|yes|enable|1)) ;; best regards, Thilo

Bug#906914: etckeeper: do not commit in the middle of an upgrade run

2018-08-23 Thread TS
Hello, given the commit message "daily autocommit" there seem to be only one possible source for this. /etc/etckeeper/daily via etckeeper.timer But this is disabled here. See attached txt file for easier reading, w/o line wrapping. Prior to any apt run, locally here 'anacron -s -n -d' is run.

Bug#906914: etckeeper: do not commit in the middle of an upgrade run

2018-08-22 Thread TS
Package: etckeeper Version: 1.18.8-1 Severity: normal Dear Maintainer, during today's upgrade run etckeeper were upgraded and it did an commit in the middle of that upgrade process. I think etckeeper should not commit unconditionally in the middle of an upgrade. In contrast, when first

Bug#286456: The superficial emptiness

2008-03-20 Thread cullie chuen-ts
DickBiggishWill http://www.Plaserable.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#154613: Join the team of winners!

2008-01-09 Thread delmar chang-ts
Welcome to cooperation! My name is Kirstin Griffin, and I work as general staff manager in the company Iberis. I would like to offer you a position of Transfer Manager in the company Iberis. Our company Iberis Capital Group is one of the leaders on the financial services market One of the

Bug#162917: Don't pursue the money - just meet them!

2008-01-09 Thread brooke chuen-ts
Welcome to cooperation! My name is Kirstin Griffin, and I work as general staff manager in the company Iberis. I would like to offer you a position of Transfer Manager in the company Iberis. Our company Iberis Capital Group is one of the leaders on the financial services market One of the

Bug#117436: Talented employees wanted. No investment is required in order to reach the financial success.

2007-09-18 Thread devy chuen-ts
Big international commercial organization is seeking of talented, honest, reliable representatives in different regions. Because of developing of our business the organization is proposing to you to become its part. You can work part time or full time. Requirements: Internet Connection Basic