[Bug 1234400] Re: Cannot log in users if their Xauthority file is corrupt.
thanks. Regarding lightdm itself, do you intend to also release a newer package for the 1.6 "stable" branch as well ? The current bug is in fact a 1.6 regression there as well (and this is how I noticed it). It's a bit counter-intuitive that the fix for a regression found in the "stable" branch is to be found an a package upgrade picked from the "unstable" branch... Unless you've just decided to EOL 1.6. E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234400 Title: Cannot log in users if their Xauthority file is corrupt. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1234400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020770] Re: gdm install prompts about dm when debconf value set
Hi, Pardon me if I'm misunderstanding, but it very much seems to me that the gdm/lightdm configuration scripts are unconditionally setting the default value of the debconf choice to gdm, irrespective of the previous value of the setting. Is that normal behaviour ? In the transcript below I would have found more logical to see a GET just after the two METAGET's. Best, E. root@magret:/var/cache/debconf# debconf-set-selections < gdm shared/default-x-display-managerselect lightdm > lightdm shared/default-x-display-managerselect lightdm > EOF root@magret:/var/cache/debconf# debconf-get-selections | grep display # Default display manager: gdm shared/default-x-display-managerselect lightdm lightdm shared/default-x-display-managerselect lightdm root@magret:/var/cache/debconf# DEBCONF_DEBUG=developer dpkg-reconfigure -fnoninteractive lightdm debconf (developer): starting /var/lib/dpkg/info/lightdm.prerm upgrade 1.4.0-0ubuntu2 debconf (developer): starting /var/lib/dpkg/info/lightdm.config reconfigure 1.4.0-0ubuntu2 debconf (developer): <-- METAGET shared/default-x-display-manager owners debconf (developer): --> 0 gdm, lightdm debconf (developer): <-- METAGET shared/default-x-display-manager choices debconf (developer): --> 0 gdm, lightdm debconf (developer): <-- SET shared/default-x-display-manager gdm debconf (developer): --> 0 value set debconf (developer): <-- INPUT high shared/default-x-display-manager debconf (developer): --> 30 question skipped debconf (developer): <-- GO debconf (developer): --> 0 ok debconf (developer): <-- GET shared/default-x-display-manager debconf (developer): --> 0 gdm debconf (developer): starting /var/lib/dpkg/info/lightdm.postinst configure 1.4.0-0ubuntu2 debconf (developer): <-- STOP root@magret:/var/cache/debconf# debconf-get-selections | grep display # Default display manager: gdm shared/default-x-display-managerselect gdm lightdm shared/default-x-display-managerselect gdm root@magret:/var/cache/debconf# debconf-get-selections | grep priority # Ignore questions with a priority less than: debconf debconf/priorityselect critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020770 Title: gdm install prompts about dm when debconf value set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1020770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Fine by me. Thanks all for tidying this up. Nice work. E. On Mon, Feb 11, 2013 at 6:41 PM, Dave Turvene wrote: > I need to work on several projects so will not have time to look at this > again this week. I rebased our work on Kevin Cernekee's 14-part > submission to linux-input. His patchset cleaned-up/refactored a lot of > the messier code along with a more comprehensive init sequence for the > Dell E6XXX series. Ben's V5 init sequence is no longer necessary. The > new dlkm is at [1]. > > The one final step that needs to be taken is to reconcile florin9doi's > init sequence for my Dell N5110 and a Fujitsu a512. The systems have > the same E7/EC signatures but appear to have different init sequences. > When I use the Fujitsu a512 init sequence, my system is stuck in PS/2 > 3-byte format and, apparently, the converse is true for the Fujitsu. > > I have re-added the alps_debug sysfs interface to toggle packet debug > and switch between the new V5 (was V6) init sequences for the N5110 and > a512. This can only be done by setting the alps_debug bit and > rebuilding; I couldn't get it to work on-the-fly. > > We are almost to the point of a submitting a final patchset to resolve a > LOT of ALPS touchpad bugs. > > [1]: http://dahetral.com/public-download > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/606238 > > Title: > synaptic touchpad not recognized on dell latitude e6510 and others > > Status in The Linux Kernel: > Fix Released > Status in “linux” package in Ubuntu: > In Progress > Status in “linux” source package in Precise: > Fix Released > Status in “linux” source package in Quantal: > In Progress > Status in “linux” package in Arch Linux: > Fix Released > Status in openSUSE: > New > > Bug description: > It wrongly recognized as PS/2 Generic Mouse. And then scrolling does > not work, but tapping does. > > ProblemType: Bug > AplayDevices: > List of PLAYBACK Hardware Devices >card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > Architecture: i386 > ArecordDevices: > List of CAPTURE Hardware Devices >card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] > Subdevices: 2/2 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: karol 2618 F pulseaudio > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'Intel'/'HDA Intel at 0xe966 irq 22' > Mixer name : 'IDT 92HD81B1C5' > Components : 'HDA:111d76d5,1028040b,00100104' > Controls : 26 > Simple ctrls : 16 > Date: Fri Jul 16 13:36:04 2010 > DistroRelease: Ubuntu 9.10 > HibernationDevice: RESUME=UUID=cdf10c13-029f-401b-afed-f651ca0e2cbe > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2) > MachineType: Dell Inc. Latitude E6510 > NonfreeKernelModules: nvidia > Package: linux-image-2.6.31-22-generic-pae 2.6.31-22.60 > PccardctlIdent: >Socket 0: > no product info available > PccardctlStatus: >Socket 0: > no card > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-generic-pae > root=UUID=2f511d08-c4e9-44e6-a1d2-5be6172b18c6 ro quiet splash > ProcEnviron: >PATH=(custom, user) >LANG=pl_PL.UTF-8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-22.60-generic-pae > RelatedPackageVersions: >linux-backports-modules-2.6.31-22-generic-pae 2.6.31-22.24 >linux-firmware 1.26 > SourcePackage: linux > Uname: Linux 2.6.31-22-generic-pae i686 > dmi.bios.date: 05/28/2010 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A03 > dmi.board.name: 0N5KHN > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA03:bd05/28/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.name: Latitude E6510 > dmi.product.version: 0001 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@Kevin (#305) > Are you seeing incorrect readings when using MT, or is your comment just based on the code? It would not be too surprising if > different initialization sequences altered the data format (ala Dolphin's 8-byte vs. 9-byte setting). Just inspecting the packets traveling through. Some MT reports, with one of the finger close to the edges, were not working. This was most visible when enabling 2-finger scrolling, since this would prevent scrolling if one of the fingers happens to be in the dead zones. Looking at the packets, it seems clear that there's one extra MT slot in each direction (and 16 and 12 are nicer numbers than 15 and 11). > Along similar lines, it would be nice if we could adjust the Rushmore > trackstick sensitivity so that it used the existing V3 > trackstick report code as-is, with no special divisor. My code at https://github.com/emmanuelthome/psmouse-alps does work with the V3 trackstick report code as-is (report by Malte Skoruppa who tested it). I think that the key is probably the weird thing which I called alps_e6_sort_of_setmode there. > E6230 has: > > - touchpad (80mm x 40mm) > - 2 lower buttons > - no middle button :( > > E6430 has: > > - touchpad (80mm x 45mm) > - trackstick > - 3 upper buttons > - 2 lower buttons ok, I stand corrected then. I should have made my point clearer, though. At some point it was thought that E6230/E6430 needed two entirely different init sequences, and needed to be detected based on some yet- to-be-determined magic going beyong E6/E7/EC reports. Not. It's only that trying to talk to the missing trackstick on the E6230 freezes the device, but that can be encompassed by a unified init. > "My reverse-engineering work and merge with bgamari's patches show this. > These are differentiated by querying the 0xc2c8 > register, which is not queried in Kevin's patch." > > Do you feel comfortable making the statement that checking the 0xc2c8 > register on Rushmore will unambiguously indicate > whether the configuration has a trackstick present (even if we're dealing > with a completely new, unknown PC)? Hell, if someone knew for sure, situation would be easier ;-) No, I'm not sure. What I observe is that based on the observation of E6230/E6430, bit 7 (0x80) of register c2c8 is used to choose between two code paths, one of which probably talks to the trackstick. The code structure here is almost in one-to-one mapping with the v3 code, and goes as follows: - check for presence of trackstick (bit 7 of register 0x8 on alps_v3, bit 7 of register 0xc2c8 on ``rushmore''). - if trackstrick: - enable trackstick passthrough mode by setting bit 0 of that same register - get an E7 report directly from the trackstick, although nothing is done with it. - send a magic command which sets something to the value 0x94. Might be your desired ``divisor''. - set bit 1 of register above (activate trackstick ???) - leave trackstick passthrough mode. > I did not see the ALPS driver checking this register, so if we don't know for > certain that this is the purpose > of the 0xc2c8 register, it might just be safer to always create the virtual > trackstick device on a > Rushmore-equipped PC (even if we never send it any reports). Yes. However, if the 0x94 thing above has any use, we'd better send it only conditionally, and the windows driver seems to do so only if it finds bit 0x80 in register 0xc2c8. Also, consistency with plain v3 code sort of increases the slim confidence we may have. > "Briefly put, I think we should work making all this stuff cleaner." > One thing that would probably make sense is to store the appropriate function > pointers + constants > in the alps_data struct, so we do not need case statements all over the code. The current alps_get_model logic seems hairy, too. Maybe it can be streamlined a bit, but that's just aesthetics. We could probably fetch the E6/E7/EC reports at once, and decide later. Do you have an idea of how many models will match any of the rushmore/pinnacle/pinnacle_agx rules ? Anyway. Whatever people find best doing for a patch to mainline is fine with me. I think we all have more important things to work with than silly touchpads... Best, E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Hi all,
In reply to #302:
> Where did you get the device names ("Dolphin", "Pinnacle", "Mercury",
etc.) and how did you figure out the protocols?
Seconded.
> Can people test Kevin's patch?
I tried it on my dell e6230, it works.
Kevin's patch do not properly take into account the fact that the e6230
has 16 and 12 bits for the MT slots, and not 15 and 11 (this is the
ALPS_BITMAP_X_BITS and ALPS_BITMAP_Y_BITS setting).
> If it works, then I'll layer the Dell I15R, I17R, 13z on top of it and
submit a patch to linux-input.
I'm a bit lost here. Has anybody kept track of the different models
encountered, and on which laptops ? I think that would help a lot (most
of the info is probably in here, but very poorly organized ; In
particular it's difficult to keep track of which laptop models, among
the ones listed, seemingly have different touchpad hardware).
Dave, what's your decision on your ACPI patch ? I haven't understood
what was the rationale behind using it, as it seemed to me that we had
enough material to drive our decision by talking to hardware directly.
If I understand correctly, you are about to forget this patch, is that
right ?
Merging all existing code (yours, mine, kevin's) is in fact easier than
the recollection of what happens where, and possibly requesting some
testing hardware (posters in this thread can be solicited).
Slightly different is the situation for the short v6 init sequence in
#280, which diverges from the usual pattern, to say the least. Not
having RESET_BAT and ENABLE in there makes the sequence functionally
different from what happens with other hardware.
In the ``seemingly different hardware category'', one could be mistaken
into listing the Dell E6230/E6430. These do have identical hardware,
except for the absence of the trackstick on the smaller E6230. My
reverse-engineering work and merge with bgamari's patches show this.
These are differentiated by querying the 0xc2c8 register, which is not
queried in Kevin's patch.
Briefly put, I think we should work making all this stuff cleaner.
E.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606238
Title:
synaptic touchpad not recognized on dell latitude e6510 and others
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/606238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1089413] Re: Touchpad not recognised on Dell Latitude E6230
You are well right posting a new bug. Bug 606238 was really too crowded. As far as I am aware, no, there is nothing in the current ubuntu kernel for having this issue fixed. I hacked a dklm replacement, building on top of Dave Turvene's and Ben Gamari's work. Code is here. git://github.com/emmanuelthome/psmouse-alps.git Real place for this fix is upstream, though. I haven't contacted upstream yet, being busy at other things. E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1089413 Title: Touchpad not recognised on Dell Latitude E6230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
In reply to #276-#277. I was mistaken on this one. Apparently the driver does nothing regarding enabling or disabling multitouch features on the trackpad. It's only a matter of the software down the line which interprets the packet data. Nothing, in fact, recognizes more than two finger in the alps driver. Presently, as far as I am aware, the only multitouch sequences which are interpreted are two-finger scrolling and two fingers for right click. The former works. The latter maybe works, although I must admit that for me, it is such an unusual gesture that I miss it most often. Could be me, could be incomplete code as well. In reply to #282: Cool. Would you be so kind to send me the output of dmesg|grep psmouse please ? Thanks. E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Cool. I suspected there was some clutter in there, but not to that point. I am a bit surprised though that there is no ENABLE command in your short init sequence. Looks quite odd. I factored the e6x30 init sequences into a common sequence (tested, works), and later ambitiously tested a merge of the v3 and v5 init sequences (untested beyond my own hardware). Code is there. git://github.com/emmanuelthome/psmouse-alps.git E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Sure. Not today, though. All these features are configurable with the windows touchpad software. Assuming they map to visible config orders sent to the device upon init, I can reverse-engineer them and enable them from the driver. I wonder, though, what is the usual choice done for touchpad hardware on linux. Are we _always_ enabling all features, or is there a mechanism to enable them just on demand ? I have seen no such thing in the sources (haven't searched much either). This sort of touchpad includes features which can be an annoyance for people not used to them, so the choice of enabling everything is not necessarily the right one. E.g. my touchpad seems to have pinch-to-zoom functionality (not even tried). I don't exactly know to what this would map under linux, nor whether this stands a chance of working in the first place, but I presume not everyone would love this feature. Best, E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Hi, I succeeded in reproducing the reverse engineering steps for the Dell E6230 touchpad. Here is an updated version of Dave's dkms module which is **ONLY** for the E6230. Starting from the init sequenced captured via qemu, I have tried to make some sense out of the commands. It seems that this init sequence is in fact quite different from that on the E6430 (which reports 73 03 0a on E7 report as well). At some point I thought that difference was related to the presence of a touchstick on 6430/6530 and not on 6230, but it seems to be more than that. Do not use this if you do not have the same hardware as me. I do not, at the moment, know how to distinguish between the dell E6430 and dell E6230 models. Using the newly built psmouse module, I can use the rightmost area of the pad to scroll, which is all I need. I don't know about other useful features, probably I would need to enable them from my windows VM before being able to see how they get initialized. This is something I can do, if deemed useful. It would be nice to tidy up this set of patches, in particular: (1) make the v5 and v6 init sequences more readable (2) differentiate between the various models (this applies to the models whose E7 report says 0x73 0x03 00x0a). Doing (1) is easy, but a test host is needed. Doing (2) requires some interaction with a user of such a platform. Volunteers ? Best, E. ** Attachment added: "updated dkms module for Dell E6230 ONLY" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+attachment/3450457/+files/psmouse-alps-dst-1.1.dell-e6230.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992928] Re: Alt-Backtick Keyboard Shortcut is Hardcoded
Misbehaviour still present in quantal I'm using gnome-fallback session. Seems that keybooard settings are under gsettings now. The magic to get this annoyance fixed is now: gsettings set org.gnome.desktop.wm.keybindings switch-group "['disabled']" (dconf-editor to the same spot works as well) (the default setting for this is "['Above_Tab']". A very unusual keysym indeed. I now understand which it wasn't easy grepping for `, backtick, grave, backquote etc...) E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992928 Title: Alt-Backtick Keyboard Shortcut is Hardcoded To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/992928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778796] Re: ‘info gcc’ broke. The package gcc-doc should be rebuilt with new debhelper to get trigger support
up. Problem still occurs in quantal, fresh install. info gcc directs me to the gccgo info page. E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778796 Title: ‘info gcc’ broke. The package gcc-doc should be rebuilt with new debhelper to get trigger support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/778796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082211] [NEW] restart impossible when a remote ssh session is running
Public bug reported: (assigning to lightdm, although it's broader than that. Not clear which component is to blame exactly). Let X be a laptop running ubuntu 12.10. It's an x86-64 cpu for that matter, but no one cares. Assume an ssh server is running on X, and someone is logged in via ssh from another machine Y to machine X. Now if X is showing a lightdm login screen, there is no way the ``restart'' button (from the top-right menu) can work. It is simply ignored. There is no message either. If some user is logged on X, and he opens up the top-right menu and goes to ``restart'', one of two things may happen. - If the remote session is under this very user, then the session is killed, and the computer restarts. - If the remote session is under another user (root, for the situation I tried), then the user's session is nuked, but the computer does not restart, and returns back to the lightdm login screen. I find this quite irritating. Ssh sessions to my laptop may happen. When I have physical access to it, I would like to be able to restart/shut down the machine without having to either do a dirty shutdown (5s press) or hunt manually for ssh session and kill -9 them, or ctrl-alt-f1, root login, and reboot. I would conceive it if someone considers it's ''dangerous'' to kill incoming ssh sessions. Not that I share this opinion, but I imagine it may exist. If so, would it be possible, please, to have a dialog box like ``yes, I mean it'' if the system decides it's perhaps unwise to proceed to reboot ? Best, E. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082211 Title: restart impossible when a remote ssh session is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1082211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027289] [NEW] openmpi1.5-doc no longer contains man pages
Public bug reported: By comparing this: http://packages.ubuntu.com/quantal/all/openmpi-doc/filelist and that: http://packages.ubuntu.com/quantal/all/openmpi1.5-doc/filelist it is pretty obvious that the MPI_* man pages have been dropped from openmpi1.5-doc (same deal for precise, for that matter) I see no mention of this in the README of the openmpi1.5-doc package, nor in its Changelog (I have not spent long searchnig though). Was this an intentional change, or an accident ? Having the MPI_* man pages is something one does count on when installing the -doc package. Best, E. ** Affects: openmpi1.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027289 Title: openmpi1.5-doc no longer contains man pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmpi1.5/+bug/1027289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778796] Re: ‘info gcc’ broke. The package gcc-doc should be rebuilt with new debhelper to get trigger support
Just re-tested this one. It's still broken. /usr/share/info/gcc.info.gz points to gcc-4.6.info.gz (don't know whether that was the case before), but that is of no use for providing correct `info gcc', because: (1) update-info-dir does not look at symlinks. (2) the info-dir section in gcc-4.6.info.gz is not meant to provide a match for (gcc) anyway. Best, E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778796 Title: ‘info gcc’ broke. The package gcc-doc should be rebuilt with new debhelper to get trigger support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/778796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778796] Re: ‘info gcc’ broke. The package gcc-doc should be rebuilt with new debhelper to get trigger support
Quite annoying indeed. Still observed in oneiric beta2. I never installed, nor cared or heard about gccgo, yet I'm served with the gccgo info page in lieu of the gcc one. I'll go for manual removing of /usr/share/info/gccgo.info.gz and redo update-info-dir in the meantime. Is the comment to be trusted in that a mere rebuild of the gcc-doc pacakge would cure this ? If so, shall we expect a fix for the 11.10 final ? Best, E. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778796 Title: ‘info gcc’ broke. The package gcc-doc should be rebuilt with new debhelper to get trigger support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/778796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754470] Re: syndaemon consumes 100% CPU
It's not really a fix. Merely a paper wrap. The bug seems to reside elsewhere, and might possibly affect other apps. IMO it's important to do more work. I will not personally have time to devote to this, however (despite the fact that I can reproduce the bug). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754470 Title: syndaemon consumes 100% CPU -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754470] Re: syndaemon consumes 100% CPU
There still seems to be something quite fishy going on with XRecord and async events. I don't know much of it underneath, so my understanding might be quite bad. Here are some random thoughts. The problem is that there is an event queue which fills up and is never drained by the application. Here, the culprit event has code 34, which is X_UngrabKey. Despite the hint, this is not related to the screen saver, since ``echo mem > /sys/power/state'' reaches the same situation. Once this event is on top of the queue, it is _never_ processed by the application. Probably because the XRecord context doesn't want it (there's an event range passed to the async context constructor). I don't know why this event shows up here. Here's a dump of the event which reaches the end of handle_response in xcb_io.c (libX11), just before _XEnq: : 22 20 0b 00 01 08 f8 00 90 94 c6 a9 ff 7f 00 00 0010: f3 00 00 00 00 00 00 00 4d 44 50 00 00 00 00 00 This is never eaten by the application. The xcb_io.c source file is in sync with the git HEAD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754470 Title: syndaemon consumes 100% CPU -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754470] Re: syndaemon consumes 100% CPU
No it's not, unfortunately. The current xcb_io.c matches the one in the git repository, which has the relevant patch applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754470 Title: syndaemon consumes 100% CPU -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754470] Re: syndaemon consumes 100% CPU
This bug annoys me greatly.
Tried your package as well. It remains silent. No debug output at all.
I don't know which changes you tried, but I've tried putting some
printf() hooks within xrecord_callback(), e.g.:
cbres = (struct xrecord_callback_results *)closure;
int check = recorded_data->category != XRecordFromServer;
static int i=0;
printf("event %d [%d]!\n", i++, check);
if (recorded_data->category != XRecordFromServer) {
This code path, under normal operation, is supposed to be called. When
the process is spinning, it seems to not enter xrecord_callback() at
all. The events received are not key events, as is visible from this gdb
extract (I compiled the package with -g):
(gdb) fin
Run till exit from #0 0x7f187e3ab123 in __select_nocancel ()
at ../sysdeps/unix/syscall-template.S:82
0x00401fb2 in record_main_loop (display=0x140b010, idle_time=0.5)
at ../../tools/syndaemon.c:413
413 ret = select(fd+1 /* =(max descriptor in read_fds) + 1 */,
(gdb) n
417 if (FD_ISSET(fd, &read_fds)) {
(gdb)
419 cbres.key_event = 0;
(gdb)
420 cbres.non_modifier_event = 0;
(gdb)
422 XRecordProcessReplies(dpy_data);
(gdb)
424 if (!ignore_modifier_keys && cbres.key_event) {
(gdb) p cbres
$1 = {modifiers = 0x1418ae0, key_event = 0, non_modifier_event = 0,
pressed_modifiers = '\000' }
(gdb) n
428 if (cbres.non_modifier_event &&
(gdb)
434 if (disable_event) {
(gdb) p disable_event
$2 = 0
(gdb) p pad_disabled
$3 = 0
I'll keep hunting a bit.
E.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754470
Title:
syndaemon consumes 100% CPU
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
