On Debian/Stretch - lightdm 1.18.3 - this issue is still present.
The script mentioned in comment 9 has served us well for the past 3+
years and is "maintained" on https://github.com/cedric-dufour/custom-
conf/tree/master/generic/all/custom-conf-pam-krb5/usr/share/custom-conf-
pam-krb5/config/etc/
Hello again,
Thanks @Sergio for the krenew tip.
I'd rather not automatically renew a user ticket without having him
supply its password from time to time.
I came up with a *horrible* workaround which I believe does not break
the entire Kerberos security (please correct me if I'm wrong):
In /et
Hello,
Has any progress been made with this issue?
Is there any workaround to circumvent it?
Thanks for the feedback and best
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336663
Title:
lightdm use
Hello,
The problem comes from:
1. the pager does not use the 'wnck_workspace_get_{width,height}' to calculate
its aspect ratio
2. the pager does not recalculate its aspect ratio when Compiz
workspaces/viewports settings are changed
Please consider attached patch to fix this behavior.
Once applied
Public bug reported:
Hello,
When increasing compiz virtual horizontal size, xfce4-panel (4.11;
Ubuntu/Trusty) workspace swicther shows the additional "workspaces" but
without increasing the swicther width accordingly; the width remains as
if a single "workspace" is used, and compiz "workspaces" a
I've been able to circumvent this bug with 'cirrus.modeset=0' in kernel boot
options.
PS: My setup is a bit strange (Quantal with custom Trusty kernel rebased to
3.12.6; both KVM host and guest)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
Hello,
After updating from Ubuntu Quantla (12.10), my system (Dell XPS 12) would:
1. attempt to suspend when lid is clised (even though this behavior is disabled
in 'xfce4-power-manager' settings); see bug #1222021
2. fail to suspend altogether when called from XFCE's 'Log O
Hello again
I'm currently looking at plymouth source code and trying to find a
solution to elegantly solve the issue mentioned in this bug at the
plymouth level, as Steve Langasek suggests.
Unfortunately, I'm wondering whether this can be achieved.
Plymouth seems to be totally agnostic of where
My XPS 12 now works beautifully under Xubuntu 12.10 (quantal)
Thank you very very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103594
Title:
Cypress Trackpad wrongly (?) detected as "PS/2 Cy
Hello Steve,
Thanks for your comments.
As for "no case in which plymouth is not used": I'm afraid I grossly
misunderstand when plymouth is used.
I experimented the "command-line" behavior I described above when booting in
"recovery mode".
Is plymouth also used in "recovery mode" or when one rem
Hello,
In the case of this cryptsetup(passphrase)/mountall(prompt) concurrency,
I agree with you.
Note that this issue also presents itself when not using plymouth
(though the passphrase prompt would "hide" the mountall "boredom" until
the 'return' key is pressed). The mountall "boredom" message
ERRATA: 'i915.invert_brightness=1' is *not* the way to go. Brightness is
actually handled correclty... but when booting the XPS 12 with 3.8rc5,
brightness is by default set to its minimum value (iow. off). One just
needs to increase it with Fn+F5 to have the panel "wake up".
Note that this issue i
Hello again,
I eventually have the i915/Intel HD4000 work along the 3.8 kernel: one
must pass "i915.invert_brightness=1" kernel parameter
# lspci -vvv -nn -s 00:02.0
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core
processor Graphics Controller [8086:0166] (rev 09) (prog-
Hello,
After installing request kernel:
# dpkg --get-selections | fgrep 3.8.0
linux-headers-3.8.0-030800rc5 install
linux-headers-3.8.0-030800rc5-generic install
linux-image-3.8.0-030800rc5-generic install
linux-image-extra-3.8.0-030800rc5-generic ins
Reassign "Affects" to "linux-image-generic" base on Kyle's
recommendation (https://bugs.launchpad.net/dell-
sputnik/+bug/1103594/comments/3)
** Project changed: dell-sputnik => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks Chris for that pointer!
Applying the mentionned patch solves the pointer jerkiness issue when
applying the "Coordinates Transformation Matrix" to my Atmel maXTouch
touchscreen.
I attach the corrected patch which can be added to the current Quantal
'xserver-xorg-core' (1.13.0-0ubuntu6.1) so
> > Could it be that this 3-seconds timeout is also reached in this
(bug) case?
> I don't believe so.
Thanks for your answer. I filed a separate bug addressing the
passphrase/boredom issue specifically:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1104156
--
You received this bug not
Public bug reported:
Hello,
(On Quantal) When using passphrase-protected LUKS encryped partition,
'mountall' shows the "Continue to wait, or Press S to skip mounting or M
for manual recovery" after the (hardcoded) 3-second BOREDOM_TIMEOUT.
This is:
- inappropriate as long as a passphrase is bei
Hello,
On Quantal, I've been trying to get rid of this message on my system
when using LUKS (passphrase-protected) encrypted LVM partitions.
Looking at the source code of "mountall.c", it appears the "Continue to
wait [...] S to skip or M for recovery" (warning) message is triggered
by the (recur
A way to circumvemt this bug - at least for the login screen when using LightDM
- is to add:
display-setup-script=setxkbmap
In /etc/lightdm/lightdm.conf, add
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
When a RAID1 system is degraded (e.g. unplug /dev/sdb, leaving obnly
/dev/sda), grub-pc properly enters prompt but system is reset as soon as
one attemps to boot OR one enters the command-line and issue the 'ls'
command.
This bug is known (and presumably fixed) to Debian:
ht
Using Ubuntu in a academic research environment, we need to be able to
do both things: develop/compile software and encode/decode multimedia
content on the same host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Today's update solved the issue for me. Was is weird is that this update
included no package *directly* related to bluetooth (I tried to
correlate which packages were updated the time it failed and the time it
was fixed again and found nothing relevant).
--
You received this bug notification beca
Same problem. Since latest bluez packges update (to version
4.101~0ubuntu6), my bluetooth keyboard stopped to work. After unpairing
it, it is also impossible to pair it again (though the device appears in
the devices list).
--
You received this bug notification because you are a member of Ubuntu
Latest kernel update (3.5.0-15.23) solved the issue for me.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053641
Title:
[i915] Kernel mode setting broken since 3.5.0-15.22 (Intel HD3000)
To
PS: rc2-r6 all work (all tested)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053641
Title:
[i915] Kernel mode setting broken since 3.5.0-15.22 (Intel HD3000)
To manage notifications about this b
Hello,
First version without the bug is rc2.
rc1 is still crippled.
Cheers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053641
Title:
[i915] Kernel mode setting broken since 3.5.0-15.22 (Intel HD3
Hello,
Latest upstream kernel (http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.6-rc6-quantal/) *fixes* the issue. I double-checked by
booting each kernel twice.
Best regards
PS: Please tell me if you still want me to try the previous 3.5.0 kernel
(and where I should get it from; I had it clean
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053641
Title:
[i915] Kernel mode setting broken since 3.5.0-15.22 (Intel HD3000)
To manage notifications about this bug go to:
https://bugs.launchpad.n
Public bug reported:
Hello,
Since latest linux-image update (3.5.0-15.22), device is unusable -
black screen after grub and then nothing else - unless one boots with
'nomodeset' added to the kernel options.
"ubuntu-bug linux" data should be attached.
Let me know if I can help,
Best regards,
C
** Attachment added: "Qt4 Mutitouch/Gesture Test Case"
https://bugs.launchpad.net/bugs/1052076/+attachment/3320794/+files/qt4-utouch.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052076
Title
can't even access; e.g. the "close" button on
QStackWidget tabs)
I attach a simple test case that allows to reproduce the problem
systematically (see README for further details).
Let me know if I can help.
Best regards,
Cédric Dufour
libqt4-core: 4.8.2+dfsg-2ubuntu1
xserver-xorg-in
Hello,
Can someone clarify where we stand in regard with this issue and Ubuntu Quantal
12.10?
I've been following Qt doc to the letter and got QPinchGesture working in a
QWidget... but as soon as the "grabGesture" is issued on that widget all other
widgets (tabs, pushbuttons, lineedits, etc.) st
Hello Martin,
Yes indeed, it seems we're bumping is several different issues. Yours - and its
fix - helped improve the global picture. I have absolutely no understanding of
how all that X and multi-touch works, so I don't know where to start from (in
respect with where/how to report the other is
Hello,
Thanks Martin for your PPA and the precise packages; unfortunately, I
run amd64 :-/
I first applied only #19 patch (yes, it did require some adjustments) to
the latest precise X.org packages (1.11.4-0ubuntu10.3): behavior remains
the same (at least as far as Compiz plugins are concerned: "
Hello Chase,
Thank you for looking into this.
When not subscribed to the X.org mailing list, obtaining the patch is kind of a
hassle (I couldn't find a download option and I'd rather avoid copy/paste). Can
you post it here too, so we can download/test it? Or will it be included in the
next xserv
I applied the patches in #11 and #12 to the current precise xserver-xorg-core
source (1.11.4-0ubuntu10.2) and unfortunately, it does not solve the atmel
maXtouch "loss of single click" (I can reproduce that behavior systematically
by calling Compiz's Expo plugin and double-clicking one of the vi
Also affected: Atmel maXtouch (see
https://answers.launchpad.net/utouch/+question/183765)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse events for Acer T231H multit
Thanks for that change. Cheers. Cédric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016592
Title:
libnss-ldap should not depend on libpam-ldap
To manage notifications about this bug go to:
https:
This issue is present on 12.04.
Has the fix been applied to Precise's Xorg package?
(I can't find it in
http://changelogs.ubuntu.com/changelogs/pool/main/x/xorg/xorg_7.6+12ubuntu1/changelog)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Thanks for your answer.
We actually have "install-recommends" disabled in /etc/apt/apt.conf.d
If you look closely, you will see that libnss-lap depends on ldap-auth-
config, which in turn depends on ldap-auth-client, which in turn depends
on libpam-ldap (thus the indirect dependency).
Debian has
Public bug reported:
On Ubuntu 12.04, libnss-ldap (264-2.2ubuntu2) should not depend on
libpam-ldap (via ldap-auth-config and ldap-auth-client).
Currently, if one installs libnss-ldap, libpam-ldap also gets installed
through dependencies.
Installing LDAP name services does not - should not, actu
"nfs shares are usually local": this is completely counter-intuitive. NFS =
Network File System. I think most would agree than a "network" file system is
definitely not a local one (and would rightly so, when considering the
differences in terms of access latencies).
Even on a high-bandwidth LAN
Forget my previously-posted patch. It was a bit too aggressive on the
character substitution and led to other errors in similar situations.
The newly attached patch should solve this.
Sorry for the trouble and cheers
** Patch added: "non-utf-8.patch"
https://bugs.launchpad.net/ubuntu/+source
Personally, I have circumvented this bug by a just-a-little-less-dirty
workaround (see attached patch).
It will only affect fields/data that contain non-UTF-8 character(s) and just
strip those from the field rather than suppressing the entire field.
Hope this helps.
Cédric
** Patch added: "non-u
This bug is still present in Ubuntu 10.04 LTS (Long Time Support), to
which I stick for very good reasons and which makes me experience the
bug at hand daily. Any hope of seeing a patch backported to LTS? Thanx
in advance
--
You received this bug notification because you are a member of Ubuntu
Bu
Hello all,
The fix released to address this bug's issue unfortunately leads to problem for
those who use the Lustre filesystem (see http://www.lustre.org):
- kernel hangs when attempting to mount a Lustre filesystem with the wrong
"NID" (which fortunately should not happen in normal operating c
And I would add to #44, #45 and #46 that Canonical can not honestly
ignore the fact that LTS releases are certainly preferred by
enterprise/production environments, for obvious reasons (well, my
1-penny maybe mislead guess). Jumping to so much untested/unreliable
stuff in a LTS release just makes m
Sorry, previous patch contained a typo. New one attached (and should also be
more resilient to package updates).
I rebuilt the "nfs-common_1.2.0-4ubuntu4_amd64.deb" package and installed it
with the expected auto-magic modification.
** Patch added: "nfs-utils.bug525154.patch"
http://launchpad
Couldn't we imagine using the output of " df -P /var/lib/nfs/ | tail -n
1 | awk '{print $6}' " to adapt the "/etc/init/statd.conf" script auto-
magically during the 'nfs-common' package installation (iow. having the
package's "postinst" script add the 'mounted MOUNTPOINT=...' stanza when
appropriat
Thanks for the quick feedback.
So, for others who may be lost like me, the new 'udev' way is (in
/etc/udev/rules.d/99-my-rule.rules):
# Exclude my USB token (cf. pamusb) from automount
# NOTE: use 'udevadm test /sys/block/sdX' to find the ENV{ID_SERIAL} parameter
SUBSYSTEM=="block", ENV{ID_SERIAL
Public bug reported:
Binary package hint: nautilus
Hello,
Some use cases (e.g. using a USB key as an authentication token along
with 'pamusb') require automount to be disabled for specific drive(s)
(rather than globally for all drives, using for example 'gconf-editor ->
apps -> nautilus -> prefe
Thanx Steve for feedback.
Yes, I do have a separate /var partition (LVM). So I guess all I achieved with
the "networking" condition is to add enough delay so that /var is mounted when
statd starts. Actually, I can confirm the fsck for this /var partition always
comes after the "statd main proces
Public bug reported:
statd fails to start during upstart with following messages:
$ fgrep statd /var/log/boot.log
init: statd main process (937) terminated with status 1
[...]
init: statd main process ended, respawning
init: statd main process (1036) terminated with status 1
init: statd respawnin
Please don't drop the $OPTIONS (. /etc/default/autofs). These may really be
handy!
Besides - sorry for being slightly off-topic, but - the supplied
/etc/default/autofs file mentions options and variables (e.g. BROWSE_MODE,
APPEND_OPTIONS, etc.) that *seem* to be used nowhere in /etc/init.d or
/
In the mean time, I've been able to circumvent this bug and finish the
installation process normally (using the Alternate CD beta-1 amd64 ISO
image) by:
1. creating the physical partitions (fdisk) using the debian-installer's
partition manager
2. [CTRL+ALT+F2] creating the RAID array manually:
md
Could it be upstart related? I experience the same bug and temporarily
solved it by restarting GDM after a 15 seconds delay in /etc/rc.local.
--
user switch crashes with process termination (lucid alpha)
https://bugs.launchpad.net/bugs/529882
You received this bug notification because you are a m
Some valuable pointers:
http://lxc.sourceforge.net/lxc.html (to start with)
http://manpages.ubuntu.com/manpages/lucid/en/man7/lxc.7.html (the hyperlinked
version of the former)
http://manpages.ubuntu.com/manpages/lucid/en/man5/lxc.conf.5.html (in
particular)
http://www.mjmwired.net/kernel/Documen
"Me too"
Personally, I'd love something like
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf
Is there anywhere we can find something equivalent for LXC?
(what we need is a genuine *users guide*)
--
Lack of documentation
https://bugs.launchpad.net/bugs/514379
You received this bug notificat
I had the same problem and incompletely hacked a solution as in
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/511245/comments/5.
Maybe it can help.
--
autofs5-ldap doesn't work immediately after bootup
https://bugs.launchpad.net/bugs/533029
You received this bug notification because you a
I just found out that all the 'sudo -u gdm gconf-editor && etc.' hacks
were just wiped out by the latest GDM update (because the %gconf...
files in /var/lib/gdm got overwritten).
We need to find a way to allow customization of GDM in a way that
resists update, via a sensible '/etc/gdm/custom.conf'
After a few reboot, it seems I found the quick-'n-elegant fix for that
issue:
r...@lucid-golden:~ # cat /etc/init/autofs-ldap.conf
# Restart AutoFS-LDAP after everything has settled
start on (stopped networking and stopped rc RUNLEVEL=[2345])
exec /etc/init.d/autofs restart
Problem with dependin
The problem is the same for NIS:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/119660
I do agree that porting autofs to upstart would be ideal. Unfortunately,
it seems it requires a good knowledge of Ubuntu's upstart events chain
to do it properly. Maybe someone knowledgeable enough with t
"Me too"
@Matthias ("as a java developer one would develop against a specification, not
a product"): I'd agree with you if we all took the blue pill (and lived in that
fantasy world where everyone behaves sensibly). Unfortunately, most of us had
to choose the red pill and live in the real world
Public bug reported:
r...@lucid-golden:~ # lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
r...@lucid-golden:~ # apt-cache show libsyncml0
Package: libsyncml0
Priority: optional
Section: universe/libs
Installed-Size: 344
Maintainer: Ubuntu MOTU Developers
I'm experiencing the (same?) problem with Lucid (and autofs-ldap).
After rebooting, one time it works... another time not (until autofs is
manually restarted)
That does sound like an upstart race condition.
Unfortunately, this is quite important for enterprise environments :-(
I guess at the time
Scratch my previous comment.
The /etc/polkit-1/localauthority/*.d files ARE honored, provided the
files are named *.pkla
Sorry
--
Do not show suspend/hiberate related UI if suspend is disabled in polkit
https://bugs.launchpad.net/bugs/432598
You received this bug notification because you are a
On Lucid, it would seem the /etc/polkit-1/* folders are not used.
Puting a power.conf file:
[Disable suspend]
Identity=unix-user:*
Action=org.freedesktop.devicekit.power.suspend
ResultActive=no
ResultAny=no
[Disable hibernate]
Identity=unix-user:*
Action=org.freedesktop.devicekit.power.hibernate
@5tan: Strange, my 'target=...' in '/etc/initramfs/conf.d/cryptroot' IS
respected in my two LUKS setups, one on Karmic and the other one still
on Jaunty.
--
cryptsetup prompt is overriden by upstart and xsplash in Karmic
https://bugs.launchpad.net/bugs/434232
You received this bug notification be
Well, the EXACT (and USB-disk-proof) syntax is:
echo 'target=#TARGET#,source=/dev/disk/by-uuid/#UUID#' >
/etc/initramfs-tools/conf.d/cryptroot
(thus leading to a '/dev/mapper/#TARGET#' device; otherwise, you get a
'/dev/mapper/cryptroot' device)
Also, make sure to add the proper modules in '/e
** Bug watch added: OpenVZ Bugzilla #1300
http://bugzilla.openvz.org/show_bug.cgi?id=1300
** Also affects: openvz-tools via
http://bugzilla.openvz.org/show_bug.cgi?id=1300
Importance: Unknown
Status: Unknown
--
WISH: allow to specify VEs boot order for /etc/init.d/vz
https://bugs
71 matches
Mail list logo
