Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy
On Thu, 6 Apr 2017 15:06:17 -0400 G. Branden Robinson wrote: > At 2017-04-06T13:33:58-0400, James McCoy wrote: > > On Thu, Apr 06, 2017 at 01:17:55PM -0400, G. Branden Robinson wrote: > > > The below is not a sufficient reproduction receipe for me. > > > > > > I'm running Debian Stretch (testing). > > > > > > Things do not go wrong at step #5, nor afterward. > > > > Make sure the terminal is sized small enough (80x24). That causes the > > syntax highlighting in Vim to get a little confused and enable some bold > > highlighting, which then causes the visual bell to turn everything bold. > > It was. Hello Branden! Thanks for trying to reproduce the bug. Does it help to know that I have: xset b off in my ~/.xsession script? -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpoCu1ylKyTZ.pgp Description: PGP signature
Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy
At 2017-04-06T13:33:58-0400, James McCoy wrote: > On Thu, Apr 06, 2017 at 01:17:55PM -0400, G. Branden Robinson wrote: > > The below is not a sufficient reproduction receipe for me. > > > > I'm running Debian Stretch (testing). > > > > Things do not go wrong at step #5, nor afterward. > > Make sure the terminal is sized small enough (80x24). That causes the > syntax highlighting in Vim to get a little confused and enable some bold > highlighting, which then causes the visual bell to turn everything bold. It was. Would it help for me to record a short video and add it to the bug? Regards, Branden signature.asc Description: PGP signature
Re: Comments regarding libglvnd_0.2.999+git20170201-2_amd64.changes
Hi Andreas, On Thu, 6 Apr 2017, Andreas Boll wrote: what's the status of getting libglvnd accepted? it is still stuck due to the missing dependencies. If there’s anything we can do to help, please let us know. Do you have any idea how to solve that? Thorsten
Re: Comments regarding libglvnd_0.2.999+git20170201-2_amd64.changes
On 06.04.2017 21:10, Thorsten Alteholz wrote: > Hi Andreas, > > On Thu, 6 Apr 2017, Andreas Boll wrote: >> what's the status of getting libglvnd accepted? > > it is still stuck due to the missing dependencies. > >> If there’s anything we can do to help, please let us know. > > Do you have any idea how to solve that? Not possible to solve the missing dependencies because glvnd'd mesa needs libglvnd to build. So libglvnd has to enter the archive first.
Re: Comments regarding libglvnd_0.2.999+git20170201-2_amd64.changes
On Thu, 6 Apr 2017, Timo Aaltonen wrote: On 06.04.2017 21:10, Thorsten Alteholz wrote: Hi Andreas, On Thu, 6 Apr 2017, Andreas Boll wrote: what's the status of getting libglvnd accepted? it is still stuck due to the missing dependencies. If there’s anything we can do to help, please let us know. Do you have any idea how to solve that? Not possible to solve the missing dependencies because glvnd'd mesa needs libglvnd to build. So libglvnd has to enter the archive first. Isn't that something what build-profiles are for? Thorsten
Bug#859725: x11-common: Each time my screen standby, system crash
Hi John Paul Adrian Glaubitz, > Nothing from your syslog excerpt indicates a problem with your X server. > Yep, but it was just a supposition. > Is there a reason why you are using Debian pre-release kernel? The official > kernel for Debian Stretch and Sid is still based on the 4.9 series. > Yep, i know, it's just for try. Even with 4.9 kernel i have the problem. > Did you actually verify that your machine crashed? What about logging in > through SSH over the network? Just because the screen is black doesn't > mean the machine actually crashed. > Ok i have SSH access with my black screen but keyboard don't work (CTRL + ALT > + MAJ + SYS + B) thank you Le jeudi 06 avril 2017 à 17:59 +0200, John Paul Adrian Glaubitz a écrit : > Control: tags -1 moreinfo > > Hi Alexandre! > > > In my syslog i have this lines : > > Nothing from your syslog excerpt indicates a problem with your X > server. > > > Kernel: Linux 4.10.0-trunk-amd64 (SMP w/4 CPU cores) > > Is there a reason why you are using Debian pre-release kernel? The > official > kernel for Debian Stretch and Sid is still based on the 4.9 series. > > Could you please reboot your machine with the latest 4.9 kernel. > > Did you actually verify that your machine crashed? What about logging > in > through SSH over the network? Just because the screen is black > doesn't > mean the machine actually crashed. > > Adrian > >
Processed: found 858304 in 327-2
Processing commands for cont...@bugs.debian.org: > found 858304 327-2 Bug #858304 [xterm] Terminal stays bold after visual bell with bold text displayed Marked as found in versions xterm/327-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 858304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy
On Thu, Apr 06, 2017 at 01:17:55PM -0400, G. Branden Robinson wrote: > The below is not a sufficient reproduction receipe for me. > > I'm running Debian Stretch (testing). > > Things do not go wrong at step #5, nor afterward. Make sure the terminal is sized small enough (80x24). That causes the syntax highlighting in Vim to get a little confused and enable some bold highlighting, which then causes the visual bell to turn everything bold. > At 2017-04-05T22:03:50-0400, James McCoy wrote: > > On Mon, Mar 20, 2017 at 10:29:20PM +0100, Francesco Poli (wintermute) wrote: > > > I finally found a reliable way to reproduce it. > > > > > > Steps to reproduce: > > > > > > 0) open the attached test.md file: > > > > > > $ vim -u NONE test.md > > > > > > 1) enable syntax highlighting: > > > > > > :set bg=dark > > > :syn on > > > > > > 2) go to the end of the file: > > > > > > [Shift+G] > > > > > > 3) go back to the beginning of the file (line by line): > > > > > > [k].[k] ← hold the key pressed until you reach the first line > > > > > > 4) visualize file info on the status line: > > > > > > [Ctrl+G] > > > > > > 5) the syntax highlighting has gone crazy (even the status line is > > > in boldface!): see the attached screenshot > > > wrong_vim_syntaxmarkdown.png > > > > > > 6) exit from vim: > > > > > > :q > > > > > > 7) the terminal (xterm), or rather the shell (bash), has also gone > > > crazy (it now prints everything in boldface by default): see > > > the attached screenshot > > > wrong_vim_syntaxmarkdown2.png > > > > > > 8) the terminal won't come back to normal behavior until I quit it; > > > another trick to regain the normal behavior of the terminal is > > > opening test.md again, enable syntax highlighting, and exit vim > > > (steps 0, 1, and 6 above) > > Regards, > Branden -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Re: Comments regarding libglvnd_0.2.999+git20170201-2_amd64.changes
2017-03-21 19:17 GMT+01:00 Andreas Boll : > 2017-03-16 23:10 GMT+01:00 Timo Aaltonen : >> On 16.03.2017 20:39, Thorsten Alteholz wrote: >>> Hi Timo, >>> >>> can you please tell me where I can find the dependency: libglx-mesa0 | >>> libglx-vendor >> >> Nowhere right now; libglx-mesa0 will be provided by mesa, libglx-vendor >> by nvidia for instance. There is a bootstrapping issue I know, and this >> is not meant to be useful by itself. > > Hi Thorsten, > > FYI there's a wip branch of mesa available at: > https://anonscm.debian.org/cgit/pkg-xorg/lib/mesa.git/log/?h=glvnd-wip > > Thanks, > Andreas Hi Thorsten, what's the status of getting libglvnd accepted? If there’s anything we can do to help, please let us know. Thanks, Andreas
Re: Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy
The below is not a sufficient reproduction receipe for me. I'm running Debian Stretch (testing). Things do not go wrong at step #5, nor afterward. At 2017-04-05T22:03:50-0400, James McCoy wrote: > On Mon, Mar 20, 2017 at 10:29:20PM +0100, Francesco Poli (wintermute) wrote: > > I finally found a reliable way to reproduce it. > > > > Steps to reproduce: > > > > 0) open the attached test.md file: > > > > $ vim -u NONE test.md > > > > 1) enable syntax highlighting: > > > > :set bg=dark > > :syn on > > > > 2) go to the end of the file: > > > > [Shift+G] > > > > 3) go back to the beginning of the file (line by line): > > > > [k].[k] ← hold the key pressed until you reach the first line > > > > 4) visualize file info on the status line: > > > > [Ctrl+G] > > > > 5) the syntax highlighting has gone crazy (even the status line is > > in boldface!): see the attached screenshot > > wrong_vim_syntaxmarkdown.png > > > > 6) exit from vim: > > > > :q > > > > 7) the terminal (xterm), or rather the shell (bash), has also gone > > crazy (it now prints everything in boldface by default): see > > the attached screenshot > > wrong_vim_syntaxmarkdown2.png > > > > 8) the terminal won't come back to normal behavior until I quit it; > > another trick to regain the normal behavior of the terminal is > > opening test.md again, enable syntax highlighting, and exit vim > > (steps 0, 1, and 6 above) Regards, Branden signature.asc Description: PGP signature
Processed: Re: x11-common: Each time my screen standby, system crash
Processing control commands: > tags -1 moreinfo Bug #859725 [x11-common] x11-common: Each time my screen standby, system crash Added tag(s) moreinfo. -- 859725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859725: x11-common: Each time my screen standby, system crash
Control: tags -1 moreinfo Hi Alexandre! > In my syslog i have this lines : Nothing from your syslog excerpt indicates a problem with your X server. > Kernel: Linux 4.10.0-trunk-amd64 (SMP w/4 CPU cores) Is there a reason why you are using Debian pre-release kernel? The official kernel for Debian Stretch and Sid is still based on the 4.9 series. Could you please reboot your machine with the latest 4.9 kernel. Did you actually verify that your machine crashed? What about logging in through SSH over the network? Just because the screen is black doesn't mean the machine actually crashed. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#859725: Acknowledgement (x11-common: Each time my screen standby, system crash)
In my syslog i have this lines : Apr 6 13:42:58 debian gvfsd-network[3909]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: L'emplacement indiqué n'est pas monté Apr 6 14:07:50 debian kernel: [15855.529860] usb 1-2: new full-speed USB device number 5 using xhci_hcd Apr 6 14:07:50 debian kernel: [15855.759454] usb 1-2: New USB device found, idVendor=054c, idProduct=0885 Apr 6 14:07:50 debian kernel: [15855.759461] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Apr 6 14:07:50 debian kernel: [15855.759465] usb 1-2: Product: MDR-ZX330BT Apr 6 14:07:50 debian mtp-probe: checking bus 1, device 5: "/sys/devices/pci:00/:00:14.0/usb1/1-2" Apr 6 14:07:50 debian mtp-probe: bus: 1, device: 5 was not an MTP device Apr 6 14:07:51 debian kernel: [15856.303846] hid-generic 0003:054C:0885.0003: hiddev0,hidraw2: USB HID v1.11 Device [MDR-ZX330BT] on usb-:00:14.0-2/input0 Apr 6 14:09:01 debian CRON[4517]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) Apr 6 14:16:00 debian wpa_supplicant[819]: wlp58s0: WPA: Group rekeying completed with a0:e0:af:22:31:0f [GTK=CCMP] Apr 6 14:17:01 debian CRON[4526]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 6 14:39:01 debian CRON[4549]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) Apr 6 15:09:01 debian CRON[4579]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ --- HERE : REBOOT --- Apr 6 15:17:19 debian systemd-modules-load[332]: Inserted module 'lp' Apr 6 15:17:19 debian systemd-modules-load[332]: Inserted module 'ppdev' Apr 6 15:17:19 debian systemd-modules-load[332]: Inserted module 'parport_pc' Apr 6 15:17:19 debian lvm[334]: 2 logical volume(s) in volume group "vg" monitored Apr 6 15:17:19 debian systemd[1]: Starting Flush Journal to Persistent Storage... Apr 6 15:17:19 debian systemd[1]: Started Flush Journal to Persistent Storage. Apr 6 15:17:19 debian systemd[1]: Started udev Coldplug all Devices. Apr 6 15:17:19 debian systemd[1]: Started udev Kernel Device Manager.
Bug#859725: x11-common: Each time my screen standby, system crash
Package: x11-common Version: 1:7.7+18 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Just when my screen go in standby (after 2minutes for examples) each time my system crash. If i want get back my computer i need to press power button to reboot. Thank you -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.10.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages x11-common depends on: ii lsb-base 9.20161125 x11-common recommends no packages. x11-common suggests no packages. -- no debconf information
