** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643566
Title:
I've switched to sssd and that also seemed to do the trick. If you need
a workaround, this way you won't have to modify any system files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314095
Title:
This problem also exists on the gdm in trusty. And kdm is also broken.
There is no way for me to deploy 14.04 with this bug in my computer lab.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068605
Ti
After the latest ifenslave update, my bonding configuration appears to
be working as intended. The bug has been fixed for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title:
Bonding mod
*** This bug is a duplicate of bug 1041790 ***
https://bugs.launchpad.net/bugs/1041790
Looking at the other comments, my case might be a different one, since
my system doesn't hang/crash. I experience slow downs after the crash.
So it might indeed be a different bug in my case. For some reason
My most recent crash happened while using Google Earth.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129679
Title:
Server hangs preceded by "EQ overflowing."
To manage notifications about this bu
I'm also experiencing this bug on Intel Sandy Bridge graphics.
I'm attaching my log files for Xorg,dmesg,i915.
** Attachment added: "i915_error_state"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129679/+attachment/3668879/+files/i915_error_state
--
You received t
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129679/+attachment/3668881/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129679/+attachment/3668880/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I'm nut sure if I'm looking at exactly the same bug, since in my case the
displays stay black, no output what so ever.
The displays are all connected to the digital output.
I'm including the dmesg of one of my machines with drm debug.
** Attachment added: "dmesg.log"
https://bugs.launchpad.ne
I can confirm this on multiple desktop machines, fully updated raring
installs. All have Intel Graphics. I will grab a dmesg in a minute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156310
Title:
Kernel Crashdump
** Attachment added: "linux-image-3.5.0-17-generic.201529.crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1067642/+attachment/3418545/+files/linux-image-3.5.0-17-generic.201529.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "kernel log of bug"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1067642/+attachment/3418472/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
Titl
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418469/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
Ti
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418468/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418467/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
Title:
ge
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418466/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418465/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418464/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418463/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418462/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
Title:
gene
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418461/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
Title:
gene
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418460/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1067642/+attachment/3418459/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067642
Titl
apport information
** Tags added: apport-collected
** Description changed:
I can reproduce this bug on 4 different machines, all runing updated Quantal
versions.
Might be related to BUG#1042213 .
This Bug does not appear when using nfs3 monted homes, only with nfs4 mounted
homes.
A 3.6
Oct 29 16:10:17 wslab03 kernel: [ 3171.068714] BUG: unable to handle kernel
NULL pointer dereference at (null)
Oct 29 16:10:17 wslab03 kernel: [ 3171.068775] IP: []
filemap_fault+0x3e/0x450
Oct 29 16:10:17 wslab03 kernel: [ 3171.068818] PGD 230050067 PUD 22dcac067 PMD
0
Oct 29 16:10:1
I still experience crashes using nfs4 and an up to date quantal.
Changing to confirmed.
** Changed in: linux (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The upstream kernel release is running without issues, so what would I report
to them?
The panic occurs on the current quantal kernel, not the mainline one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
I can reproduce this bug on 4 different machines, all runing updated Quantal
versions.
Might be related to BUG#1042213 .
This Bug does not appear when using nfs3 monted homes, only with nfs4 mounted
homes.
A 3.6.2 mainline kernel also hasn't exhibited this behavior so far.
I'm also seeing bug on an up to date qunatal with kernel 3.5.0-17.
What can I provide to help get this fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1042213
Title:
[quantal] Kernel oops with
*** This bug is a duplicate of bug 945450 ***
https://bugs.launchpad.net/bugs/945450
** This bug has been marked a duplicate of bug 945450
Responsiveness: LightDM in ubuntu 12.04 very slow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I'm running precise in a computer lab, so maybe I can shed some light on your
theory:
We have roughly 10 different desktop environments installed
current statistics:
host 1: gnome-session --session=buntu, no user in w
host 2: gnome-session --session=ubuntu, no user in w
host 3: gnome-session --se
I believe, since unity-greeter's configuration was moved from
unity-greeter.conf to gsettings, you will have to change the settings in
gsettings.
the lightdm user has a home directory in /var/lib/lightdm
To change the settings, you will have to run dconf-editor as the lightdm user.
I don't know w
Th slow down I'm experiencing is only on the lightdm screen.
We have pretty much all desktop environments installed (openbox, fluxbox,
enlightenment, kde, gnome, lxde, xfce, unity, twm, evilwm, ...), which might be
a contributing factor, with the list being quite large. With GDM, there are no
su
** Tags added: regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897212
Title:
lightdm ignores session selection of ldap users
To manage notifications about this bug go to:
https:/
Whitelisting 'all' did the trick for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761587
Title:
Unity makes Gajim unusable
To manage notifications about this bug go to:
https://bugs.launchpad.
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/250909
Title:
Apt-get does not support packages of 2.5 gig...
To manage notifications about this bug go to:
https://bugs.launchp
I can confirm this bug also exists on precise!
The following packages will be upgraded:
android-sdk
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/2,789 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Here's my config.
I can still reproduce this with all current updates installed.
** Attachment added: "lighdtm config"
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/962932/+attachment/2948263/+files/lightdm.conf
--
You received this bug notification because you are a member o
Public bug reported:
If the Login field is used instead of the listed accounts, the default session
stored in AccountsService is ignored, instead the greeters default session (in
this case ubuntu) is used.
The default session is stored correctly in accountsservice and .dmrc after
logging in.
u
Mounting the /var/lib/AccountsService directory through nfs from an
external server might help get around this issue. I will see if this
works.
** Bug watch added: Red Hat Bugzilla #617465
https://bugzilla.redhat.com/show_bug.cgi?id=617465
** Also affects: accountsservice (Fedora) via
https
I can still reproduce this on my lab machines with all updates
installed.
Mar 26 12:05:28 $HOSTNAME lightdm: pam_unix(lightdm:session): session opened
for user $USER by (uid=0)
Mar 26 12:05:28 $HOSTNAME lightdm: pam_ck_connector(lightdm:session): nox11
mode, ignoring PAM_TTY :0
Mar 26 12:05:32 $
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962932
Title:
Pressing escape key on lightdm greeter restarts xserver
To manage notifica
** Description changed:
Pressing the escape key on the lightdm greeter screen with an up to date
ubuntu precise results in the xserver restarting.
I assume, this is not intended behavior.
+
+ I'm only able to reproduce this bug with
+ "greeter-hide-users=true" set in lighdm.conf
--
You
I'm not quite convinced this is a duplicate of those bugs. I have the
same problem on all of my machines with:
---# lspci |grep VGA
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
Sandy bridge GPUs on the other hand are smooth as but
** Attachment added: "strace"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/962932/+attachment/2921237/+files/lighdtm_strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962932
Title:
** Attachment added: "lighdm log, showing restart"
https://bugs.launchpad.net/bugs/962932/+attachment/2921207/+files/lightdm.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962932
Title:
Pressi
Public bug reported:
Pressing the escape key on the lightdm greeter screen with an up to date
ubuntu precise results in the xserver restarting.
I assume, this is not intended behavior.
** Affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notific
I believe I have narrowed down the bug to a race condition with the 10.04 sever
and its exported nfs4 shares. The nfs client tries to mount the nfs4 shares and
get caught in a loop. The workaround for this is forcing nfs3 in the
auto.master using:
"/home /etc/autofs/auto.home vers=3,--
This bug might actually be related to nfs-common, but I'm not sure yet.
I'm debugging the situation right now.
A workaround that might be working is setting the MOUNT_WAIT variable in
/etc/default/autofs
nfs debugging didn't give me anything usefel yet, I will see what I can
pick up with wiresha
nfs3+ heimdal Kerberos for authentication + ldap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962001
Title:
Nfs mount hangs while automounting home
To manage notifications about this bug go to:
ht
Public bug reported:
On my Ubuntu Precise nfs clients with autofs, the mount.nfs process hangs for
hours until the autofs service is restarted.
I haven't been able to get an strace from this, since it doesn't happen all the
time.
I do have a kernel log trace, since sshd was being blocked which r
** Attachment added: "kern.log showing hug task"
https://bugs.launchpad.net/bugs/962001/+attachment/2915174/+files/kern.log
** Description changed:
- On my nfs clients with autofs, the mount.nfs process hangs for hours until
the autofs service is restarted.
+ On my Ubuntu Precise nfs clients
I've created a PPA with Gajim 0.15 under
https://launchpad.net/~cebalrai/+archive/misc, if this helps the
maintainer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959365
Title:
[new-upstream]Gajim
*** This bug is a duplicate of bug 959365 ***
https://bugs.launchpad.net/bugs/959365
** This bug has been marked a duplicate of bug 959365
[new-upstream]Gajim 0.15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
The current version of Gajim in Ubuntu Precise is 0.14.1, while version
0.15 was released on March 18th 2012.
** Affects: gajim (Ubuntu)
Importance: Undecided
Status: New
** Tags: gajim update xmpp
--
You received this bug notification because you are a memb
This bug ist also present under precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761587
Title:
Unity makes Gajim unusable
To manage notifications about this bug go to:
https://bugs.launchpad.
I can confirm this bug for precise with nfs+ldap+kerberos.
The default session for users isn't saved in either lightdm or gdm, as both use
accountsservice for session saving.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I was able to get around this bug be setting:
BLUETOOTH_ENABLED=1
in /etc/default/bluetooth
until the package is installed.
There is probably a bug in the post-installation script which doesn't
work when "BLUETOOTH_ENABLED=0" is set.
--
You received this bug notification because you are a mem
tracked it down to one of my own config files...marking invalid.
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869917
Title:
ttyS0/t
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/869917/+attachment/2522437/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869917
Title:
ttyS0
** Attachment added: "strace ttyS1"
https://bugs.launchpad.net/bugs/869917/+attachment/2522434/+files/ttyS1_strace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869917
Title:
ttyS0/ttyS1 res
Public bug reported:
On a system with a fully updated oneiric installation, syslog is full
of:
Oct 7 11:32:05 $hostname kernel: [ 7332.859460] init: ttyS1 main process
(17271) terminated with status 1
Oct 7 11:32:05 $hostname kernel: [ 7332.859485] init: ttyS1 main process
ended, respawning
Libdrm from proposed fixes the bug on a Intel G35.
No adverse effects so far.
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Your PPA fixes the bug for me.
Lets hope they include it in the release.
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
*** This bug is a duplicate of bug 619663 ***
https://bugs.launchpad.net/bugs/619663
** This bug is no longer a duplicate of bug 654619
[945gme] Failed to allocate framebuffer with width >2048 with intel 2.12
drivers.
** This bug has been marked a duplicate of bug 619663
[maverick] Non-
*** This bug is a duplicate of bug 619663 ***
https://bugs.launchpad.net/bugs/619663
** This bug has been marked a duplicate of bug 619663
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
* You can subscribe to bug 619663 by following this link:
https://bugs.e
This really needs more attention, only 11 days from release. And the
number of affected users is probably going to be relatively large. Xorg-
Edgers isn't what one wants on production systems.
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.
I never had the PPA installed and I'm also getting this bug.
--
Docky freezes when launching application
https://bugs.launchpad.net/bugs/628372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I can confirm this bug on Lucid amd64.
I also have the "mail user agent extension" installed.
--
No signature detected in emails signed using pgp/mime
https://bugs.launchpad.net/bugs/565014
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, it appears to be fixed now: "unconfirm"
** Changed in: cl-asdf (Ubuntu)
Status: Confirmed => New
--
cl-asdf postinstall script hangs: SYSTEM-SOURCE-FILE is undefined
https://bugs.launchpad.net/bugs/529219
You received this bug notification because you are a member of Ubuntu
Bugs
I can confirm this as well.
** Changed in: cl-asdf (Ubuntu)
Status: New => Confirmed
--
cl-asdf postinstall script hangs: SYSTEM-SOURCE-FILE is undefined
https://bugs.launchpad.net/bugs/529219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: pam (Ubuntu)
Status: New => Confirmed
--
pam_motd patch to show /etc/legal fails to set flag
https://bugs.launchpad.net/bugs/481854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
*** This bug is a duplicate of bug 526556 ***
https://bugs.launchpad.net/bugs/526556
According to upstream it is actually a bug in gnome-keyring, not gajim.
** Bug watch added: Gajim Trac #5633
http://trac.gajim.org/ticket/5633
** Also affects: gajim via
http://trac.gajim.org/ticket/56
Public bug reported:
Postinstall script fails to update initramfs if running kernel is not installed
in system, for example chroot environment.
relevant section of nvidia-current.postinst
-
CURRENT_KERNEL=$(uname -r)
NEWEST_KERNEL=$(get_newest_kernel "$KERNELS")
** Changed in: casper (Ubuntu)
Assignee: (unassigned) => Ubuntu Development Team (ubuntu-dev)
--
nfs-boot with unionfs doesn't work
https://bugs.launchpad.net/bugs/460781
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
It is quite emberassing that this confirmed bug hasn't been fixed after
a month. Jaunty is getting close to the first Beta release and this
should get fixed before that.
--
[regression] Acrobat Reader hangs when presenting a (any) PDF
https://bugs.launchpad.net/bugs/325098
You received this bug n
This bug still appears for me under 9.04.
'evolution --force-shutdown' does not work in my case. Killing the gnome panel
does.
--
Clicking on clock applet hangs gnome-panel
https://bugs.launchpad.net/bugs/203527
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Bug confirmed:
9.04-amd64,2.6.28-7-generic #20-Ubuntu SMP, nvidia 180.27-0ubuntu1.
Nvidia Quadro 140NVS (Thinkpad T61)
metacity ver. 2.25.144-0ubuntu1
--
Window decorations in title bar missing with compiz enabled
https://bugs.launchpad.net/bugs/327793
You received this bug notification because y
79 matches
Mail list logo