[Bug 1020303] [NEW] nslcd drops supplemental groups when dropping privileges
Public bug reported: When nslcd drops privileges at startup, it calls setgroups(0, NULL) rather than the expected initgroups(username, gid). This causes nslcd not to be able to read files (such as TLS certificates) if they are owned by one of the supplemental groups specified in the /etc/group file. If it matters, nscd works as expected by calling getgrouplist() and then the appropriate setgroups() with the group list when it drops privileges. The debug output from nslcd shows this happening: nslcd: DEBUG: setgroups(0,NULL) done nslcd: DEBUG: setgid(112) done nslcd: DEBUG: setuid(106) done and it appears to do this intentionally in nslcd.c: /* drop all supplemental groups */ if (setgroups(0,NULL)0) ** Affects: nss-pam-ldapd (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/1020303 Title: nslcd drops supplemental groups when dropping privileges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1020303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82853] Re: Add support for the smbk5pwd overlay
I think the best thing to do for this bug is to unassign it and have it get re-triaged. It was triaged and assigned almost 5 years ago well before upstream fixed the problem. I'm hoping this doesn't upset anyone. ** Changed in: openldap (Ubuntu) Status: Triaged = New ** Changed in: openldap (Ubuntu) Assignee: Rick Clark (dendrobates) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/82853 Title: Add support for the smbk5pwd overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/82853/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 82853] Re: Add support for the smbk5pwd overlay
I think the best thing to do for this bug is to unassign it and have it get re-triaged. It was triaged and assigned almost 5 years ago well before upstream fixed the problem. I'm hoping this doesn't upset anyone. ** Changed in: openldap (Ubuntu) Status: Triaged = New ** Changed in: openldap (Ubuntu) Assignee: Rick Clark (dendrobates) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/82853 Title: Add support for the smbk5pwd overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/82853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82853] Re: Add support for the smbk5pwd overlay
This bug was fixed in Debian over two years ago. Is there any way this can get reprioritized somewhere higher than wishlist? Having to use George Rath's PPA is a bad workaround (but thanks George for your effort, it certainly helped!) and pulling the Debian slapd packages into our own apt server isn't much better. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/82853 Title: Add support for the smbk5pwd overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/82853/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 82853] Re: Add support for the smbk5pwd overlay
This bug was fixed in Debian over two years ago. Is there any way this can get reprioritized somewhere higher than wishlist? Having to use George Rath's PPA is a bad workaround (but thanks George for your effort, it certainly helped!) and pulling the Debian slapd packages into our own apt server isn't much better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/82853 Title: Add support for the smbk5pwd overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/82853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701717] Re: 'Mangler' unable to receive mouse input.
The xinput package is for the xinput binary program. The reported problem is not releated to the xinput binary, but is possibly within Xorg. However, it's more likely that it's a problem with Mangler. Marking the xinput version of this bug as invalid and I will triage within Mangler report first. ** Changed in: xinput (Ubuntu) Status: New = Invalid ** Changed in: mangler Assignee: (unassigned) = ekilfoil (ekilfoil) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701717 Title: 'Mangler' unable to receive mouse input. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701717] Re: 'Mangler' unable to receive mouse input.
I assume the Logitech mouse worked fine? Have you tried setting your PTT key to all of the available mouse buttons (such as middle button or right button) as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701717 Title: 'Mangler' unable to receive mouse input. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: [Needs SRU] unable to use mouse buttons to trigger events in mangler
** Description changed: [Impact] Hardware-specific issue which results in certain mouse models to get detected as keyboard, which can cause problems in various applications, depending on how they interact with the mouse. [Development Solution] Patch is already present in the xserver in natty as fixed by upstream. [Release Solution] Patch linked in comment #11 applies to maverick and was tested to solve the issue. [Test Case] - With affected hardware, run mangler and set the Enable Mouse Button Push to Talk option. Set mouse to Virtual core XTest, then click the Set button and press middle mouse button. Without the fix, there will be no effect, with the fix the program will trigger an event as appropriate. + With affected hardware, run mangler and set the Enable Mouse Button Push to Talk option. If the problem is resolved, the affected mouse's hardware description will be available in the drop down list. [Regression Potential] Mild. The patch was taken into the stable release branch, and we've been carrying this change in Natty without any complaints as far as I know. The patch itself just tweaks the ordering of device detection a smidge; there's essentially no chance of crashes or other serious problems. Worst case would be behavioral change in oddball input devices. [Original Report] inside mangler I have the Enable Mouse Button Push to Talk checked Select Mouse is set to Virtual core XTEST pointer I then clicked the Set button and pressed my middle mouser (Wheel) button When I try to use my middle mouse button it does not transmit. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xinput 1.5.0-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue May 4 19:18:23 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xinput -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/575465 Title: [Needs SRU] unable to use mouse buttons to trigger events in mangler -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: unable to use mouse buttons to trigger events in mangler
I spoke with the Xorg devs on IRC and this patch has been set for pull request in upstream's master git. However, Ubuntu needs to backport this to 10.10 and update. I do not plan on maintaining a PPA for this fix now that upstream has corrected the problem. This bugfix consists of moving two lines of code. The patch attached above is identical for the current version of Xorg. -- unable to use mouse buttons to trigger events in mangler https://bugs.launchpad.net/bugs/575465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: unable to use mouse buttons to trigger events in mangler
I've put this bugfix in a PPA in case anyone wants to test it and confirm: https://launchpad.net/~ekilfoil/+archive/xserver-xorg -- unable to use mouse buttons to trigger events in mangler https://bugs.launchpad.net/bugs/575465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: unable to use mouse buttons to trigger events in mangler
The way Mangler detects mouse button presses is by polling the state of the
mouse. With most mouses, polling the master pointer will return the state of
the slave device. This problem seems to be limited to Logitech wireless mice.
Basically we're doing this:
dev = XOpenDevice(GDK_WINDOW_XDISPLAY(rootwin), xdev[ctr].id);
xds = (XDeviceState *)XQueryDeviceState(GDK_WINDOW_XDISPLAY(rootwin), dev);
xbs = (XButtonState*) xds-data;
state = state bit;
if ((xbs-buttons[byte] state) bit) { // byte and bit are the mouse
button flags
// button is pressed
}
I have tried other wireless mouse devices at my disposal and they seem
to work fine. It is ONLY the logitech wireless mice (at least... that
have been reported)
--
unable to use mouse buttons to trigger events in mangler
https://bugs.launchpad.net/bugs/575465
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: unable to use mouse buttons to trigger events in mangler
I was incorrect. It seems that querying the master pointer does not give the button state of the slave pointer even for normal mice. I did some more digging on this today, and I found that an HP branded wireless USB mouse has the same issue. With this mouse (as well as the logitech wireless mouse), the return from: xdev = XListInputDevices(GDK_WINDOW_XDISPLAY(rootwin), ndevices_return); lists the USB device twice, but both have xdev[num].use == 3 (IsXExtensionKeyboard as defined in X11/XI.h). I think the problem is that one of those devices should have the use member set to 4. The attached xinput list provided by Locke above shows this correctly with one device as a pointer and one as a keyboard, but I'm assuming the xinput program is using the XI2 API. With a simple little program to list the devices and print the use member: 13 devices found Virtual core pointer: use is 0 Virtual core keyboard: use is 1 Virtual core XTEST pointer: is a pointer Virtual core XTEST keyboard: use is 3 Power Button: use is 3 Power Button: use is 3 G15 Gaming Keyboard: use is 3 G15 Gaming Keyboard: use is 3 Logitech USB-PS/2 Optical Mouse: is a pointer Macintosh mouse button emulation: is a pointer G15 Extra Keys: use is 3 BTC USB Multimedia Cordless Kit: use is 3 BTC USB Multimedia Cordless Kit: use is 3 While xinput prints: BTC USB Multimedia Cordless Kit id=14 [slave pointer (2)] BTC USB Multimedia Cordless Kit id=13 [slave keyboard (3)] -- unable to use mouse buttons to trigger events in mangler https://bugs.launchpad.net/bugs/575465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: unable to use mouse buttons to trigger events in mangler
I'm almost positive this is a problem in xorg-server. I'm working on a patch for this. ** Package changed: xinput (Ubuntu) = xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New = In Progress ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) = ekilfoil (ekilfoil) -- unable to use mouse buttons to trigger events in mangler https://bugs.launchpad.net/bugs/575465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: unable to use mouse buttons to trigger events in mangler
Swapping the order of the test in Xi/listdev.c that determines whether a device is a pointer or a keyboard properly detects my devices (OEM USB wireless mouse/kb combo) -- one as a keyboard and one as a pointer. I have confirmed that querying the device shows the button state for the pointer device and the X server responds with b-down as expected for various button states. libXi receives the button state information properly as well -- however it doesn't seem to be passed through to the end application's call to XQueryDeviceState. I have not finished investigating the cause of that problem, but I have confirmed that this is either a problem in my code or within libXi. This simple patch, fixes the detection device type problem and that is all I could find wrong in Xorg. ** Patch added: xorg-xi-usb-wireless-mouse-kb.patch http://launchpadlibrarian.net/48092586/xorg-xi-usb-wireless-mouse-kb.patch -- unable to use mouse buttons to trigger events in mangler https://bugs.launchpad.net/bugs/575465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575465] Re: unable to use mouse buttons to trigger events in mangler
I think that's as far as I can go with this. ** Changed in: xorg-server (Ubuntu) Status: In Progress = Confirmed ** Changed in: xorg-server (Ubuntu) Assignee: ekilfoil (ekilfoil) = (unassigned) -- unable to use mouse buttons to trigger events in mangler https://bugs.launchpad.net/bugs/575465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538818] Re: gtkmm 2.19.4 has a bug with Gtk::TextBuffer
Confirmed fixed after latest update. -- gtkmm 2.19.4 has a bug with Gtk::TextBuffer https://bugs.launchpad.net/bugs/538818 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 522372] Re: gnote crashed with SIGSEGV in gtk_text_iter_get_offset()
This bug is in gtkmm (libgtkmm-2.4-1c2a) 2.19.4. According to
https://bugs.launchpad.net/ubuntu/+source/regexxer/+bug/521412 this has
been fixed in 2.19.5.
This is a critical bug and gtkmm needs to a version bump for Lucid since
any gtkmm app that uses Gtk::TextBuffer will probably have the same
problem (including my project).
Code to reproduce:
#include gtkmm.h
int main(int argc, char *argv[]) {
Gtk::Main kit(argc, argv);
Glib::RefPtrGtk::TextBuffer buf = Gtk::TextBuffer::create();
}
Command to compile above program:
gcc `pkg-config --cflags --libs gtkmm-2.4` bug.cpp
--
gnote crashed with SIGSEGV in gtk_text_iter_get_offset()
https://bugs.launchpad.net/bugs/522372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538818] [NEW] gtkmm 2.19.4 has a bug with Gtk::TextBuffer
Public bug reported:
gtkmm 2.19.4 contains a bug which prevents TextBuffers from working in
some cases.
The bug is fixed upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=609852
Code to reproduce:
#include gtkmm.h
int main(int argc, char *argv[]) {
Gtk::Main kit(argc, argv);
}
Expected Output: None
Actual Output:
$ ./a.out
(a.out:12876): GLib-GObject-WARNING **: cannot register existing type
`gtkmm__GtkTextBuffer'
** Affects: gtkmm2.4 (Ubuntu)
Importance: Undecided
Status: New
--
gtkmm 2.19.4 has a bug with Gtk::TextBuffer
https://bugs.launchpad.net/bugs/538818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538818] Re: gtkmm 2.19.4 has a bug with Gtk::TextBuffer
** Description changed:
gtkmm 2.19.4 contains a bug which prevents TextBuffers from working in
some cases.
The bug is fixed upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=609852
Code to reproduce:
#include gtkmm.h
int main(int argc, char *argv[]) {
- Gtk::Main kit(argc, argv);
+ Gtk::Main kit(argc, argv);
}
+
+ Expected Output: None
+
+ Actual Output:
+ $ ./a.out
+
+ (a.out:12876): GLib-GObject-WARNING **: cannot register existing type
+ `gtkmm__GtkTextBuffer'
--
gtkmm 2.19.4 has a bug with Gtk::TextBuffer
https://bugs.launchpad.net/bugs/538818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538818] Re: gtkmm 2.19.4 has a bug with Gtk::TextBuffer
Thanks. https://launchpad.net/ubuntu/+source/gtkmm2.4 shows the latest upload still as 2.19.4, but if it's already known/on schedule to be fixed, go ahead and close this bug out. -- gtkmm 2.19.4 has a bug with Gtk::TextBuffer https://bugs.launchpad.net/bugs/538818 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485488] Re: Applications routed through the pulse pcm alsa-plugin crackle/die quickly
I'm the Mangler developer that first noticed the problem in the original ticket. FWIW, something definitely changed between 9.04 and 9.10. The PA ALSA plugin used to deliver audio at a fairly low latency (low enough that the default worked for our needs). The newer version of PulseAudio increased this latency significantly (from about 0.1 seconds to about 2 seconds or so) in the simple API. I don't know if it was intentional or not... it could very easily be a power saving measure to reduce CPU wakeups by the pulse daemon, but the result is horrible for ALSA apps that are expecting low latency. I think there's two separate problems being described in this bug though. One is latency problems and the other is sound dropping (buffer problems). They're probably related, but are two different issues. -- Applications routed through the pulse pcm alsa-plugin crackle/die quickly https://bugs.launchpad.net/bugs/485488 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485488] Re: Applications routed through the pulse pcm alsa-plugin crackle/die quickly
Two other things: 1) PulseAudio's alsa plugin should honor the requested latency from the call to snd_pcm_set_params() by setting pa_buffer_attr.fragsize accordingly. 2) PulseAudio's alsa plugin should honor ALSA calls to snd_pcm_drain() -- which I think are most likely the cause of the audio cutoff when combined with the high latency. -- Applications routed through the pulse pcm alsa-plugin crackle/die quickly https://bugs.launchpad.net/bugs/485488 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
