Bug#859059: keyboard-configuration: many mac keymap in keyboard-configuration are faulty
Hi, I'm currently trying the pc keyboard layout with intl variant Seems everything is ok Thanks again Raphael 2017-03-31 11:42 GMT+02:00 raphael truc : > Hi, > > Indeed your solution seems better. > If I remember well, I selected manually the mac keyboard. > I'll try this evening to reconfigure with the pc model > Thanks > > 2017-03-31 10:35 GMT+02:00 Anton Zinoviev : > >> On Thu, Mar 30, 2017 at 10:37:03PM +0200, raphael truc wrote: >> > >> > I understand it may not be easy. Maybe a solution would to be to have >> more >> > atomic keyboard description file that could be combined together, but it >> > may add some strange results, though. >> >> In my opinion, one solution is to move all mac specific layouts to the >> respective pc file. Then we can get rid of the files in macintosh_vndr. >> I don't see a problem if we allow mac users to use non-mac layouts and >> pc users to use mac layouts. >> >> By the way, did you select Mac keyboard model manually? As far as I can >> remember, by default, keyboard-configuration (hence the installer too) >> use pc keyboard model on Macs (and not macintosh, ibook, powerbook, >> macbook78 or macbook79). >> >> Are there some problems if you reconfigure keyboard-configuration to use >> pc keyboard model? In this case there will be no need to copy the altgr >> part of the pc keyboard to the macintosh one. >> >> Anton Zinoviev >> > >
Bug#859059: keyboard-configuration: many mac keymap in keyboard-configuration are faulty
Hi, Indeed your solution seems better. If I remember well, I selected manually the mac keyboard. I'll try this evening to reconfigure with the pc model Thanks 2017-03-31 10:35 GMT+02:00 Anton Zinoviev : > On Thu, Mar 30, 2017 at 10:37:03PM +0200, raphael truc wrote: > > > > I understand it may not be easy. Maybe a solution would to be to have > more > > atomic keyboard description file that could be combined together, but it > > may add some strange results, though. > > In my opinion, one solution is to move all mac specific layouts to the > respective pc file. Then we can get rid of the files in macintosh_vndr. > I don't see a problem if we allow mac users to use non-mac layouts and > pc users to use mac layouts. > > By the way, did you select Mac keyboard model manually? As far as I can > remember, by default, keyboard-configuration (hence the installer too) > use pc keyboard model on Macs (and not macintosh, ibook, powerbook, > macbook78 or macbook79). > > Are there some problems if you reconfigure keyboard-configuration to use > pc keyboard model? In this case there will be no need to copy the altgr > part of the pc keyboard to the macintosh one. > > Anton Zinoviev >
Bug#859059: keyboard-configuration: many mac keymap in keyboard-configuration are faulty
Hi, Thanks for your quick reply I understand it may not be easy. Maybe a solution would to be to have more atomic keyboard description file that could be combined together, but it may add some strange results, though. The problem, for now, is that nothing raises a warning or an error saying it could not work, which is very confusing and frustrating, and painful for non experienced users and even experienced ones. And also it could make people think that it's a specifically bad designed package from Debian which is not. Have a nice day Raphael 2017-03-30 20:43 GMT+02:00 Anton Zinoviev : > forcemerge 535834 859059 > thanks > > On Wed, Mar 29, 2017 at 10:28:42PM +0200, raphael wrote: > > > > I have a macbook pro with us keymap, I tried different layouts > > available in keyboard-configuration to get accents, but ended with Can > > not find "mac" in "macintosh_vndr/us". or Can not find "altgr-intl" in > > "macintosh_vndr/us". and No Symbols named "altgr-intl" in the include > > file "macintosh_vndr/us" or No Symbols named "mac" in the include file > > "macintosh_vndr/us" > > > > I ended up copying the altgr part of the pc keyboard (found in > > /usr/share/X11/xkb/symbols) to the macintosh one. I already had the > > same kind of problem with mac french azerty keyboard. I think either > > the /usr/share/X11/xkb/symbols/macintosh_vndr files should be > > corrected or choices in the keyboard-configuration setup reduced to > > what's really available (it took me quite a long time to understand > > why I couldn't get the accents though everything looked fine). > > Yes, this is an unfortunate bug which is reported from time to time. > Unfortunately, it can not be fixed because of > > https://bugs.freedesktop.org/show_bug.cgi?id=33670 > > Anton Zinoviev > >
Bug#842994: [Pkg-zsh-devel] Bug#842994: Bug#842994: zsh-syntax-highlighting: shell flooded with error messages
removing the alias solved the problem Thanks for helping 2016-11-03 15:21 GMT+01:00 raphael truc : > Thanks for the explanations > I'll use autoload -U and remove the alias, which was not a good idea at > the beginning > Have a nice day > > Raphael > > > 2016-11-03 14:23 GMT+01:00 Daniel Shahaf : > >> Control: severity -1 normal >> Control: forwarded -1 https://github.com/zsh-users/z >> sh-syntax-highlighting/issues/252 >> >> raphael truc wrote on Thu, Nov 03, 2016 at 10:27:35 +0100: >> > Indeed, I noticed I had aliased long time ago ! to sudo (which I forgot) >> >> This is an artifact of using `source zsh-syntax-highlighting.zsh` to >> load zsh-syntax-highlighting; using `autoload -U` would avoid aliases >> in the calling scope being applied. There already is an upstream issue >> for that: https://github.com/zsh-users/zsh-syntax-highlighting/issues/252 >> >> Given that your alias changes the meaning of a shell syntax construct, >> it would break _any_ plugin that's run by `source` [which is most of >> them], not just z-sy-h. Hence I'm demoting the severity. >> >> I'm afraid the upstream fix is not entirely trivial, it is not scheduled >> yet. In the meantime, the workarounds available to you are either to >> move the «!» inside the parentheses, or to define the alias _after_ >> loading z-sy-h. >> >> Cheers, >> >> Daniel >> > >
Bug#842994: [Pkg-zsh-devel] Bug#842994: Bug#842994: zsh-syntax-highlighting: shell flooded with error messages
Thanks for the explanations I'll use autoload -U and remove the alias, which was not a good idea at the beginning Have a nice day Raphael 2016-11-03 14:23 GMT+01:00 Daniel Shahaf : > Control: severity -1 normal > Control: forwarded -1 https://github.com/zsh-users/ > zsh-syntax-highlighting/issues/252 > > raphael truc wrote on Thu, Nov 03, 2016 at 10:27:35 +0100: > > Indeed, I noticed I had aliased long time ago ! to sudo (which I forgot) > > This is an artifact of using `source zsh-syntax-highlighting.zsh` to > load zsh-syntax-highlighting; using `autoload -U` would avoid aliases > in the calling scope being applied. There already is an upstream issue > for that: https://github.com/zsh-users/zsh-syntax-highlighting/issues/252 > > Given that your alias changes the meaning of a shell syntax construct, > it would break _any_ plugin that's run by `source` [which is most of > them], not just z-sy-h. Hence I'm demoting the severity. > > I'm afraid the upstream fix is not entirely trivial, it is not scheduled > yet. In the meantime, the workarounds available to you are either to > move the «!» inside the parentheses, or to define the alias _after_ > loading z-sy-h. > > Cheers, > > Daniel >
Bug#842994: [Pkg-zsh-devel] Bug#842994: zsh-syntax-highlighting: shell flooded with error messages
Hi, Thanks for your reply Indeed, I noticed I had aliased long time ago ! to sudo (which I forgot) setopt gives : autocd autopushd chaselinks correct correctall extendedglob globdots histignoredups histnofunctions histreduceblanks histverify interactive interactivecomments markdirs menucomplete monitor nullglob pushdsilent pushdtohome sharehistory shinstdin zle Raphael 2016-11-03 2:34 GMT+01:00 Daniel Shahaf : > raphael wrote on Wed, Nov 02, 2016 at 23:02:43 +0100: > > Package: zsh-syntax-highlighting > > Version: 0.5.0-1 > > Severity: important > > > > Hi, > > > > Since last upgrade, after a few commands I get for every commands : > > _zsh_highlight_main__type:35: no matches found: (( 1 )) > > _zsh_highlight_highlighter_main_paint:490: no matches found: (( > already_added )) > > > > These lines are: > > if ! (( already_added )); then > if ! (( $+REPLY )); then > > Have you aliased «!» to anything? Can you share the output of `setopt` > (without arguments)? > > Or — instead of these two — could you provide a minimal zshrc that > reproduces the problem? > > Thanks, > > Daniel >
Bug#841949: Acknowledgement (minidlna: Minidlna fails to display AVI files)
Finally, installing libavifile did the trick, it was probably removed when doing apt autoremove. Maybe it should be a dependance Sorry for the noise Raphael 2016-10-24 20:51 GMT+02:00 Debian Bug Tracking System : > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Alexander GQ Gerasiov > > If you wish to submit further information on this problem, please > send it to 841...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 841949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841949 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#832551: Acknowledgement (xserver-xorg-core: Various X tools stop working with new xserver-xorg-core)
Indeed, downgrading from 2:1.18.4-1 to 2:1.18.3-1 for xserver-common/xorg-xserver-core/xwayland/xserver-xephyr resolved the problem 2016-07-26 21:09 GMT+02:00 Debian Bug Tracking System : > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian X Strike Force > > If you wish to submit further information on this problem, please > send it to 832...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 832551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832551 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#823355: xserver-xorg-video-intel: Black screen on TTY's ctrl-alt-F* and black screen when going back to X
Hi Indeed, using kernel 4.4.0 gets back to normal. Sorry for the noise Raphael 2016-05-05 17:35 GMT+02:00 Julien Cristau : > Control: tag -1 moreinfo > > On Tue, May 3, 2016 at 23:22:19 +0200, raphael wrote: > > > Package: xserver-xorg-video-intel > > Version: 2:2.99.917+git20160325-1 > > Severity: important > > > > Hi, > > > > Since last upgrade, I noticed that switching to TTY's with ^-alt-F* > gives a black screen, and trying to go back to the X session gives also a > black screen. > > (I have a dual card though no bumblebee installed, only intel driver is > used). > > What did you upgrade, when, and does reverting that upgrade fix things? > This is more likely to be a kernel issue than an X driver issue, so you > could try rebooting with an earlier or newer kernel. > > Cheers, > Julien >
Bug#819823: gnome-terminal: Fails to start with "message bus" warning
Indeed, I had something called "vte-ng" used by termite in /usr/local. I uninstalled it, and gnome-terminal works again. Sorry for the noise and thanks again. Raphaël 2016-04-04 11:33 GMT+02:00 Simon McVittie : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Control: retitle 819823 gnome-terminal-server: undefined symbol: > vte_terminal_set_color_cursor_foreground > > On Mon, 04 Apr 2016 at 11:20:59 +0200, raphael truc wrote: > > On the first term, the one with terminal-server, I get > "/usr/lib/gnome-terminal > > /gnome-terminal-server: symbol lookup error: /usr/lib/gnome-terminal/ > > gnome-terminal-server: undefined symbol: > > vte_terminal_set_color_cursor_foreground" > > Thanks, that points us to the real bug here. > > According to the packaging metadata, that symbol was new in vte 0.44: > > vte_terminal_set_color_cursor_foreground@Base 0.44.0 > > and you correctly have vte 0.44 installed: > > ii libvte-2.91-00.44.0-1 > > If you run "ldd /usr/lib/gnome-terminal/gnome-terminal-server" in the > same terminal, what do you get? > > Do you perhaps have an older version of vte somewhere like /usr/local/lib? > > Thanks, > S > -BEGIN PGP SIGNATURE- > > iQIcBAEBCAAGBQJXAjUGAAoJEE3o/ypjx8yQiGIP/0CTdDtvdbL2fjG5yGUwX2ob > AKaLhqWISUN2FDWb/MTX2P15gpW5azH9UmXVgVzL/bV8u5LLHZEE/g8DhRG/yZrU > hA8L/VnP1EsFAz+XvGpia6frdqtjJDIhtWrvqvPY3dR7/xe9DtUmsDvORzDPhFbR > exI5WU6Tqfino3scAqhvhN8T5LtAuj4dUXiYNXf6qB2hHvWgcI+OcWeYWiUS2ONu > VVU+hvLt9lmucNe4jjFgjmbP2sHcCPKwTQnNO2q1VWXrSKtpWZlzsMOJjvNrP/Ue > EWicVRV91/4gC6CvbGUWB9R/qWEqm/NZHe8hJyq8kyNhD5nHI5u3BD7Vu2tb+auF > 14Mfkzr96s+OYgIk1EpTHRz2I2Ud6anMp9aK/o4N+DNWnn2Kaf+WEYC+TI43V1sL > +moTOWZnOyhlPDGp64i94WlCsI0x/OcFYXkdeSQW2yMZD585OaVlGupMGdIBBntc > QajWGXj8WNG4LyBj6w6ykyDpqj1cMSWpXUVLjdTXgC98WYX6cG4YIhqYrKIHyC8e > l/wwWsbIBdFQYO0TXYooqMwBzfW/7FB5KKLi9NGfSRjv+cwnX1Ec1pWYZfN5vohr > pCF1B01aZdjsUGIqVfoU7eGzTkteb2fmC6ygu1KqFJop7ClTJ6vlDheFq05oz16X > Xgj9u/vQgZQREb0hdvdb > =Anxg > -END PGP SIGNATURE- >
Bug#819823: gnome-terminal: Fails to start with "message bus" warning
Hi, Thanks for your reply. Indeed, I do not use systemd (though it is installed, but not used as primary init) nor dbus-user-session I launched /usr/lib/gnome-terminal/gnome-terminal-server on one term and try to launch gnome-terminal with another, it fails. On the first term, the one with terminal-server, I get "/usr/lib/gnome-terminal/gnome-terminal-server: symbol lookup error: /usr/lib/gnome-terminal/gnome-terminal-server: undefined symbol: vte_terminal_set_color_cursor_foreground" and on the second "Error creating terminal: Message recipient disconnected from message bus without replying" Regards Raphaël 2016-04-04 10:13 GMT+02:00 Simon McVittie : > Control: tags 819823 + moreinfo > > On Sat, 02 Apr 2016 at 21:16:58 +0200, raphael wrote: > > Since last update, gnome-terminal (on non-gnome session ie awesome and > lightdm) fails to lauchn with error : "Error creating terminal: Message > recipient disconnected from message bus without replying" > > I see you aren't using systemd, so I can't ask you to look for warnings > in the Journal. I assume you don't have dbus-user-session installed either. > > Please try running > > /usr/lib/gnome-terminal/gnome-terminal-server > > in some other X terminal (an xterm or something); then try to start > gnome-terminal from a second xterm. If that fails with similar symptoms, > report any warning or error messages that come from gnome-terminal-server. > > If that *doesn't* fail with similar symptoms, the next thing to try is > editing /usr/share/dbus-1/services/org.gnome.Terminal.service so that the > Exec line reads > > Exec=/bin/sh -c '/usr/lib/gnome-terminal/gnome-terminal-server | logger -t > gnome-terminal-server' > > Again, try starting gnome-terminal from an xterm, but this time please > look in > /var/log/syslog for messages tagged "gnome-terminal-server", and report > those. > > Regards, > S >
Bug#815497: crosshurd: Hurd deb package fails to install
Hi, It's totally up to date In fact, I tried on another box, just using a temporary folder, and it worked without problems, maybe I have a glitch in my shell environnement... 2016-02-22 22:16 GMT+01:00 Samuel Thibault : > raphael truc, on Mon 22 Feb 2016 22:13:50 +0100, wrote: > > It's a stretch host > > Ok, same here. I guess it's completely up to date? > > > Maybe there is a conf file somewhere I missed ! > > The default values provided in /etc/crosshurd should just work fine, and > what is not there is asked interactively by crosshurd. > > Samuel >
Bug#815497: crosshurd: Hurd deb package fails to install
It's a stretch host Maybe there is a conf file somewhere I missed ! 2016-02-22 19:58 GMT+01:00 Samuel Thibault : > raphael truc, on Mon 22 Feb 2016 19:50:49 +0100, wrote: > > Well, I mount the partition on /mnt and run crosshurd > > Well, that works for me :) > > Are you using a jessie, stretch or sid host? > > Samuel >
Bug#815497: crosshurd: Hurd deb package fails to install
Well, I mount the partition on /mnt and run crosshurd Nothing special 2016-02-22 0:41 GMT+01:00 Samuel Thibault : > raphael truc, on Mon 22 Feb 2016 00:39:50 +0100, wrote: > > The downloads seems complete. > > It's not a hiccup, I've encountered the same bugs two or three times > these few > > weeks > > Then we need to determine what's getting wrong. How do you run this, > precisely? > > Samuel >
Bug#815497: crosshurd: Hurd deb package fails to install
The downloads seems complete. It's not a hiccup, I've encountered the same bugs two or three times these few weeks 2016-02-22 0:11 GMT+01:00 Samuel Thibault : > raphael truc, on Mon 22 Feb 2016 00:06:54 +0100, wrote: > > In fact the packages are downloaded > > Are the downloads really complete? > > > doing a ln -s /var/cache/apt /mnt/var/cache erases any previous errors > when > > doing a crosshurd after > > Ok, but still there's something that went wrong, and we should > determine what: either a mirror hiccup, which we don't care about, or > another issue. > > Samuel >
Bug#815497: crosshurd: Hurd deb package fails to install
Hi, Thanks for your quick reply. In fact the packages are downloaded doing a ln -s /var/cache/apt /mnt/var/cache erases any previous errors when doing a crosshurd after Raphael 2016-02-21 23:58 GMT+01:00 Samuel Thibault : > Control: tags -1 + unreproducible > > Mmm, I have no issue with crosshurd at the moment. Wondering what is > different in your setup and in mine. > > I typically test by pointing crosshurd at non-yet-existing /tmp/crosshurd > > raphael, on Sun 21 Feb 2016 23:12:53 +0100, wrote: > > When trying to install hurd with crosshurd, it fails to install the hurd > package with the error : > > "I: Extracting > /var/cache/apt/archives/libbz2-1.0_1.0.6-8_hurd-i386.deb... > > /usr/share/crosshurd/makehurddir.sh: ligne 51 : [: trop d'arguments > (translation : too many arguments) > > This is weird, for a start. This is about libparted2, did it somehow not > get downloaded? Perhaps a mirror hiccup? > > > dpkg-deb : erreur : impossible de lire l'archive > « /mnt//var/cache/apt/archives/dpkg_1.18.3_hurd-i386.deb > > /var/cache/apt/archives/dpkg_1.18.4_hurd-i386.deb »: Aucun fichier ou > dossier de ce type (no such file or directory) > > There's an /mnt/ path and a non-/mnt/ path here. > > Samuel >
Bug#802127: crosshurd: GNU/Hurd fails to install with crosshurd
Thanks Indeed, I wondered how to put messages in english ! Raphaël Le 18 octobre 2015 13:12, Samuel Thibault a écrit : > raphael, le Sat 17 Oct 2015 18:40:23 +0200, a écrit : > > Les paquets suivants contiennent des dépendances non satisfaites : > > initscripts : Dépend: sysvinit-utils (>= 2.88dsf-50) mais ne sera pas > installé > > Casse: util-linux (< 2.26.2-4~) mais 2.25.2-4.1+hurd.1 > devra être installé > > I guess this is due to outdated packages on debian-ports, I have asked > for their removal. > > PS: remember to run commands with no locale when reporting bugs ;) > -- > Samuel >
Bug#746603: crosshurd: Does not install hurd nor kfreebsd
Hi, Not sure about multiarch, but I think it is. Also, the strange thing about the kfreebsd install is I wanted a x86_64 install, and it fails on a 486 kernel. But maybe it's normal in the crosshurd process. Thanks Raphael 2014-05-01 23:13 GMT+02:00 Samuel Thibault : > raphael, le Thu 01 May 2014 22:57:17 +0200, a écrit : > > I tried to use crosshurd to install hurd, it finished in : > > Err http://ftp.debian-ports.org unreleased/main i386 Packages > > 404 Not Found [IP : 206.12.19.127 80] > > Do you perhaps have a multiarched host? It seems this is a new problem > for crosshurd indeed. > > > So, I tried to install kfreebsd, using as target cpu x86_64, though it > failed with : > > E: Impossible de trouver le paquet kfreebsd-image-8-486 > > Right, I've bumped the kernel to -10 for next upload. > > Samuel >
