[Bug 2019247] Re: perf should be compiled with libtraceevent
This still appears to be an issue. Events are listed in `perf list` but not available for use by `perf record` e.g. $ sudo /usr/lib/linux-tools/6.2.0-39-generic/perf record -e syscalls:sys_enter_fsync -ag event syntax error: 'syscalls:sys_enter_fsync' \___ unsupported tracepoint libtraceevent is necessary for tracepoint support Run 'perf list' for a list of valid events Usage: perf record [] [] or: perf record [] -- [] -e, --eventevent selector. use 'perf list' to list available events ➜ test git:(UPM-29742) ✗ /usr/lib/linux-tools/6.2.0-39-generic/perf version perf version 6.2.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2019247 Title: perf should be compiled with libtraceevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042556] [NEW] Critical data loss bug in postgresql-common initscript
Public bug reported: Hi The Debian packages for PostgreSQL (and thus the Ubuntu packages because of the shared use of pg_wrapper) are subject to a potentially critical data loss bug because of an unsafe procedure for restarting PostgreSQL. This issue has been recognised and patched in Debian: http://anonscm.debian.org/loggerhead/pkg-postgresql/postgresql-common/trunk/revision/1181 http://archives.postgresql.org/pgsql-general/2012-07/msg00501.php but should be urgently included in Ubuntu and backported. I quote Tom Lane (key PostgreSQL dev): [The] forced unlink on the postmaster.pid file [...] (a) is entirely unnecessary, and (b) defeats the safety interlock against starting a new postmaster before all the old backends have flushed out. It is VITAL that pg_wrapper NEVER unlink the postmaster.pid file. The postmaster will do that its self if it finds the pid to be stale, but only after performing some checks to make sure there are no backends still running and to ensure that there's no other postmaster running against the database. See: http://archives.postgresql.org/pgsql-general/2012-07/msg00475.php Context here: http://archives.postgresql.org/pgsql-general/2012-07/msg00350.php http://dba.stackexchange.com/questions/20959/recover-postgresql-database-from-wal-errors-on-startup/20961 ** Affects: postgresql-common (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: postgresql-common (Debian) Importance: Unknown Status: Unknown ** Tags: patch-accepted-debian ** Bug watch added: Debian Bug tracker #686060 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686060 ** Also affects: postgresql-common (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686060 Importance: Unknown Status: Unknown ** Changed in: postgresql-common (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042556 Title: Critical data loss bug in postgresql-common initscript To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1042556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042556] Re: Critical data loss bug in postgresql-common initscript
Debian patch: http://anonscm.debian.org/loggerhead/pkg-postgresql /postgresql-common/trunk/revision/1181 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042556 Title: Critical data loss bug in postgresql-common initscript To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1042556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042556] Re: Critical data loss bug in postgresql-common initscript
BTW, while the Debian patch says potentially dangerous, Tom Lane (core Pg developer Red Hat package maintainer) says horridly, horridly dangerous and stupid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042556 Title: Critical data loss bug in postgresql-common initscript To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1042556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042556] Re: Critical data loss bug in postgresql-common initscript
Thanks. I wanted to make sure this didn't slip under the radar in terms of merging with Debian etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042556 Title: Critical data loss bug in postgresql-common initscript To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1042556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567268] Re: NetworkManager leaves garbage in essid after disconnect
NFI, I haven't used Ubuntu for a good year now. The fact that there haven't been any recent affects me too additions and there's been no comment activity suggests it's probably gone into the mists of wherever unloved bugs go to die. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/567268 Title: NetworkManager leaves garbage in essid after disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/567268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 267100] Re: Kernel memory disable overcommitment - java and other things dysfunctional
Still present on 12.04 LTS with 3.0.0-14-generic-pae i686. Memory fragmentation / contiguous allocation issues? I can't imagine why Java would demand contiguous memory, but it's a bit weird sometimes. craig@wallace:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04 LTS Release:12.04 Codename: precise craig@wallace:~$ uname -a Linux wallace 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 i686 i386 GNU/Linux craig@wallace:~$ free -m total used free sharedbuffers cached Mem: 3902 3669232 0129 2583 -/+ buffers/cache:957 2945 Swap: 1553 5 1547 craig@wallace:~$ cat /proc/meminfo MemTotal:3996268 kB MemFree: 212484 kB Buffers: 132820 kB Cached: 2669820 kB SwapCached: 2468 kB Active: 1514732 kB Inactive:2094660 kB Active(anon): 651976 kB Inactive(anon): 167824 kB Active(file): 862756 kB Inactive(file): 1926836 kB Unevictable: 80 kB Mlocked: 80 kB HighTotal: 3213600 kB HighFree: 40688 kB LowTotal: 782668 kB LowFree: 171796 kB SwapTotal: 1590420 kB SwapFree:1584292 kB Dirty: 2584 kB Writeback: 9920 kB AnonPages:805564 kB Mapped: 148452 kB Shmem: 12992 kB Slab: 81328 kB SReclaimable: 58140 kB SUnreclaim:23188 kB KernelStack:4320 kB PageTables:14600 kB NFS_Unstable: 11508 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit: 3588552 kB Committed_AS:3199664 kB VmallocTotal: 122880 kB VmallocUsed: 36856 kB VmallocChunk: 81828 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB DirectMap4k: 47096 kB DirectMap2M: 866304 kB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/267100 Title: Kernel memory disable overcommitment - java and other things dysfunctional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/267100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752542] Re: ACPI DSDT info
On the Dell Vostro 3550, for which info is already attached, the ACPI call \_SB.PCI0.PEG0.PEGP._OFF successfully disables the onboard radeon card, or at least claims to and reduces power use dramatically. After this acpi call is made, there's about a 10 second delay during resume from sleep as the radeon driver hunts around for the card. It looks like the intel video bios doesn't like the card disappearing either, complaining: [ 238.692874] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 238.692878] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CCB4 (len 62, WS 0, PS 0) @ 0xCCD0 [ 238.692881] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing B9C8 (len 1036, WS 4, PS 0) @ 0xBAC5 [ 238.692884] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing B95E (len 76, WS 0, PS 8) @ 0xB966 then repeatedly [ 244.058077] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 244.058080] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CCB4 (len 62, WS 0, PS 0) @ 0xCCD0 so be careful when turning off secondary video hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752542 Title: ACPI DSDT info To manage notifications about this bug go to: https://bugs.launchpad.net/lpbugreporter/+bug/752542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752542] Re: ACPI DSDT info
On the Dell Vostro 3550, for which info is already attached, the ACPI call \_SB.PCI0.PEG0.PEGP._OFF successfully disables the onboard radeon card, or at least claims to and reduces power use dramatically. After this acpi call is made, there's about a 10 second delay during resume from sleep as the radeon driver hunts around for the card. It looks like the intel video bios doesn't like the card disappearing either, complaining: [ 238.692874] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 238.692878] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CCB4 (len 62, WS 0, PS 0) @ 0xCCD0 [ 238.692881] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing B9C8 (len 1036, WS 4, PS 0) @ 0xBAC5 [ 238.692884] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing B95E (len 76, WS 0, PS 8) @ 0xB966 then repeatedly [ 244.058077] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 244.058080] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CCB4 (len 62, WS 0, PS 0) @ 0xCCD0 so be careful when turning off secondary video hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752542 Title: ACPI DSDT info To manage notifications about this bug go to: https://bugs.launchpad.net/lpbugreporter/+bug/752542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294648] Re: svn over https with client certificates broken (regression in intrepid)
Daniel: Check `ldd svn' and the ldd output for neon to see if you're actually linked to OpenSSL or to gnutls. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/294648 Title: svn over https with client certificates broken (regression in intrepid) To manage notifications about this bug go to: https://bugs.launchpad.net/neon/+bug/294648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794841] Re: fsck prompt for missing device doesn't time out, hangs unattended/headless server boot indefinitely
*** This bug is a duplicate of bug 571444 *** https://bugs.launchpad.net/bugs/571444 Inevitably I only found a report on this _after_ I filed this one.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794841 Title: fsck prompt for missing device doesn't time out, hangs unattended/headless server boot indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/794841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794841] [NEW] fsck prompt for missing device doesn't time out, hangs unattended/headless server boot indefinitely
*** This bug is a duplicate of bug 571444 *** https://bugs.launchpad.net/bugs/571444 Public bug reported: Binary package hint: mountall During boot, an Ubuntu machine installed as a server from the alternate CD will pause indefinitely waiting for console input if an fstab line points to a device that is not present and fsck would normally be run on that device. It prints The disk drive for / is not ready yet or not present. Continue to wait; or press s to skip mounting or M for manual recovery then waits for input. This halt occurs before sshd comes up and is only on the console, so a headless server has to be physically accessed to resolve the problem. This is not a crash. Pressing S allows the server to continue booting, but you have to have a keyboard plugged in and a display to see what you need to do, or at least need a serial console in place. This is far from ideal for a remote headless machine. Encountered on: craig@backup:/etc$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 11.04 Release:11.04 Codename: natty with: craig@backup:/etc$ apt-cache policy mountall upstart mdadm mountall: Installed: 2.25ubuntu1 Candidate: 2.25ubuntu1 Version table: *** 2.25ubuntu1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status upstart: Installed: 0.9.7-1 Candidate: 0.9.7-1 Version table: *** 0.9.7-1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status upstart: Installed: 0.9.7-1 Candidate: 0.9.7-1 Version table: *** 0.9.7-1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status mdadm: Installed: 3.1.4-1+8efb9d1ubuntu4.1 Candidate: 3.1.4-1+8efb9d1ubuntu4.1 Version table: *** 3.1.4-1+8efb9d1ubuntu4.1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.1.4-1+8efb9d1ubuntu4 0 500 http://ftp.iinet.net.au/pub/ubuntu/ natty/main i386 Packages This is particularly problematic because mdadm doesn't auto-assemble and start degraded RAID arrays that are not the boot device, so a server with a degraded RAID array will fail to boot if that array is not the boot device. I encountered this on a big RAID backup server where the device containing root,boot,usr,var etc is is a little low-power SSD and all the real storage lives on a RAID array. When a disk dropped out of the array and we lost power, the server failed to come back up because it was sitting at this fsck prompt. Recommended fix: Time out on the prompt after 60 seconds, defaulting to S for skip. Do not wait for input on subsequent prompts if more than one is displayed, automatically skip if the first prompt timed out. The latter is important because many servers will have 10 or more file systems and you don't want a 60-second timeout on each. ** Affects: upstart Importance: Undecided Status: New ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Also affects: upstart Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 571444 Boot hangs and unable to continue when automount disk in fstab is not available (Off or Disconnected) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794841 Title: fsck prompt for missing device doesn't time out, hangs unattended/headless server boot indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/794841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750994] [NEW] NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display
Public bug reported: Launching NetBeans7 RC1 from http://netbeans.org/ fails with a SIGSEGV on a freshly installed Ubuntu 11.04 system with OpenJDK 1.6.0_22. The segfault is in libGL.so.1 at glXChooseVisual+0x106eb . Running glxinfo reports: Xlib: extension GLX missing on display :0.0. Error: couldn't find RGB GLX visual or fbconfig ... so I suspect the issue is that OpenJDK isn't coping cleanly when GLX isn't available. It appears that the JDK has been restructured to try to merge the -headless and regular jdks, given that `dpkg -S /usr/lib/jvm/java-6-openjdk/bin/java' reports `openjdk-6-jre-headless'. Attempting to 'apt-get --purge remove openjdk-6-jre-headless' shows that openjdk-6-jre now depends on openjdk-6-jre-headless. This may be related to the problem. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xb0d99e7b, pid=392, tid=3001133936 # # JRE version: 6.0_22-b22 # Java VM: OpenJDK Client VM (20.0-b11 mixed mode, sharing linux-x86 ) # Derivative: IcedTea6 1.10.1pre # Distribution: Ubuntu Natty (development branch), package 6b22-1.10.1~pre1-0ubuntu1 # Problematic frame: # C [libGL.so.1+0x61e7b] glXChooseVisual+0x106eb # # An error report file with more information is saved as: # /home/craig/hs_err_pid392.log # # If you would like to submit a bug report, please include # instructions how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ # ** Affects: openjdk-6 (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/750994 Title: NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750994] Re: NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display
** Attachment added: OpenJDK crash report https://bugs.launchpad.net/bugs/750994/+attachment/1981016/+files/hs_err_pid392.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750994 Title: NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750994] Re: NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display
Possibly related: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/745271 Some more system details: craig@wallace:~$ lsb_release -rd Description:Ubuntu Natty (development branch) Release:11.04 xdpyinfo attached. craig@wallace:~$ apt-cache policy openjdk-6-jdk openjdk-6-jdk: Installed: 6b22-1.10.1~pre1-0ubuntu1 Candidate: 6b22-1.10.1~pre1-0ubuntu1 Version table: *** 6b22-1.10.1~pre1-0ubuntu1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ natty/main i386 Packages 500 http://au.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status ** Attachment added: output from xdpyinfo https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/750994/+attachment/1981037/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750994 Title: NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750994] Re: NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display
When I switched to the `nouveau' display driver, thus enabling glx, NetBeans was able to launch successfully. Given that NetBeans was failing during the 'enabling modules' stage, I'd say it was crashing when it tried to launch a module that used GL visualization features. Looks like openjdk needs more tests run on displays lacking glx extensions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750994 Title: NetBeans 7 crashes OpenJDK with SIGSEGV in glXChooseVisual when GLX not available on display -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58307] Re: --append-to-version breaks make-kpkg kernel build
Brian Rogers' PPA addresses this in Mavrick. Please push into -updates ! -- --append-to-version breaks make-kpkg kernel build https://bugs.launchpad.net/bugs/58307 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 578108] Re: pppd persistent mode is not working
It looks like /etc/init/network-interface.conf from ifupdown should probably exclude ppp interfaces. It appears to be intended for hotplug, and ppp interfaces look like they're hotplugged, but in fact they're typically created as a result of an ifup invoking pppd. They need a way to be protected from automatic ifdown if they're persistent. Adding ifupdown to the bug. ** Also affects: ifupdown Importance: Undecided Status: New -- pppd persistent mode is not working https://bugs.launchpad.net/bugs/578108 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 585208] Re: slapd becomes non-responsive after several weeks runtime
Did you consider giving me more than a few hours to respond? Or collect more debug info? Did either of you even bother looking at the attached details? Did you notice the several weeks part, where it's not particularly easy to reproduce this issue on demand? This bug should not be closed. -- slapd becomes non-responsive after several weeks runtime https://bugs.launchpad.net/bugs/585208 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- 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 585208] Re: slapd becomes non-responsive after several weeks runtime
Sorry, that was unnecessarily grumpy. It's been a long day of fighting bugs in innumerable different things, etc. -- slapd becomes non-responsive after several weeks runtime https://bugs.launchpad.net/bugs/585208 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- 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 585208] Re: slapd becomes non-responsive after several weeks runtime
Did you consider giving me more than a few hours to respond? Or collect more debug info? Did either of you even bother looking at the attached details? Did you notice the several weeks part, where it's not particularly easy to reproduce this issue on demand? This bug should not be closed. -- slapd becomes non-responsive after several weeks runtime https://bugs.launchpad.net/bugs/585208 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 585208] Re: slapd becomes non-responsive after several weeks runtime
Sorry, that was unnecessarily grumpy. It's been a long day of fighting bugs in innumerable different things, etc. -- slapd becomes non-responsive after several weeks runtime https://bugs.launchpad.net/bugs/585208 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 572105] Re: update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update
This issue is closely related to issue 356256. -- update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update https://bugs.launchpad.net/bugs/572105 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-ldap in ubuntu. -- 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 572105] Re: update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update
... which is https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/356256, since LP didn't feel like auto-linking it. -- update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update https://bugs.launchpad.net/bugs/572105 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-ldap in ubuntu. -- 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 585208] [NEW] slapd becomes non-responsive after several weeks runtime
Public bug reported: I use an Ubuntu 10.04 (lucid) server for, among other things, LDAP authentication. slapd: Installed: 2.4.21-0ubuntu5 Candidate: 2.4.21-0ubuntu5 Version table: *** 2.4.21-0ubuntu5 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Distributor ID: Ubuntu Description:Ubuntu 10.04 LTS Release:10.04 Codename: lucid With Ubuntu 9.10 it was stable and well-behaved. Since upgrading to 10.04, however, I've been seeing issues where slapd stops responding to ldap queries after several weeks of uptime. slapd has to be killed and re-launched to get it working again. I haven't found any way to reproduce this except waiting. The delay before it happens is variable, from a few days to a few weeks. All other daemons on the server are stable and well behaved. The issue appears to be restricted to slapd. After the second time this happened, I tried to dump a core from slapd so I could debug it after I'd restarted it to restore services. However, gcore reported the following error: /root/slapd.core.gMMj3g:1: Error in sourced command file: Cannot access memory at address 0x1fe8513 gcore: failed to create slapd.core.25525 and when I attached gdb directly to attempt to just get a backtrace, it failed in a similar manner: Attaching to process 25525 Reading symbols from /usr/sbin/slapd...Reading symbols from /usr/lib/debug/usr/sbin/slapd...done. done. Cannot access memory at address 0x1fe8513 ... making it rather hard to collect debug information. A backtrace requested after that error is essentially useless, as it contains no symbols, only '???' and addresses. This time when it happened I collected some information from slapd's /proc entry before re-starting the process. It's all I could come up with, and it didn't tell me much. I'll attach the files from /proc here. Ideas? Can this be caused by a slapd bug? Or should I be looking for a kernel bug? ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- slapd becomes non-responsive after several weeks runtime https://bugs.launchpad.net/bugs/585208 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- 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 585208] Re: slapd becomes non-responsive after several weeks runtime
The attachment contains /proc/$pid/{environ,maps,pagemap,smaps,status}
from a failed slapd instance.
I couldn't read /proc/$pid/mem; it reported no such process.
** Attachment added: Select files from /proc of failed slapd instance
http://launchpadlibrarian.net/49050824/slapd_procfiles.zip
--
slapd becomes non-responsive after several weeks runtime
https://bugs.launchpad.net/bugs/585208
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
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 572105] Re: update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update
This issue is closely related to issue 356256. -- update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update https://bugs.launchpad.net/bugs/572105 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 572105] Re: update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update
... which is https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/356256, since LP didn't feel like auto-linking it. -- update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update https://bugs.launchpad.net/bugs/572105 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 585208] [NEW] slapd becomes non-responsive after several weeks runtime
Public bug reported: I use an Ubuntu 10.04 (lucid) server for, among other things, LDAP authentication. slapd: Installed: 2.4.21-0ubuntu5 Candidate: 2.4.21-0ubuntu5 Version table: *** 2.4.21-0ubuntu5 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Distributor ID: Ubuntu Description:Ubuntu 10.04 LTS Release:10.04 Codename: lucid With Ubuntu 9.10 it was stable and well-behaved. Since upgrading to 10.04, however, I've been seeing issues where slapd stops responding to ldap queries after several weeks of uptime. slapd has to be killed and re-launched to get it working again. I haven't found any way to reproduce this except waiting. The delay before it happens is variable, from a few days to a few weeks. All other daemons on the server are stable and well behaved. The issue appears to be restricted to slapd. After the second time this happened, I tried to dump a core from slapd so I could debug it after I'd restarted it to restore services. However, gcore reported the following error: /root/slapd.core.gMMj3g:1: Error in sourced command file: Cannot access memory at address 0x1fe8513 gcore: failed to create slapd.core.25525 and when I attached gdb directly to attempt to just get a backtrace, it failed in a similar manner: Attaching to process 25525 Reading symbols from /usr/sbin/slapd...Reading symbols from /usr/lib/debug/usr/sbin/slapd...done. done. Cannot access memory at address 0x1fe8513 ... making it rather hard to collect debug information. A backtrace requested after that error is essentially useless, as it contains no symbols, only '???' and addresses. This time when it happened I collected some information from slapd's /proc entry before re-starting the process. It's all I could come up with, and it didn't tell me much. I'll attach the files from /proc here. Ideas? Can this be caused by a slapd bug? Or should I be looking for a kernel bug? ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- slapd becomes non-responsive after several weeks runtime https://bugs.launchpad.net/bugs/585208 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 585208] Re: slapd becomes non-responsive after several weeks runtime
The attachment contains /proc/$pid/{environ,maps,pagemap,smaps,status}
from a failed slapd instance.
I couldn't read /proc/$pid/mem; it reported no such process.
** Attachment added: Select files from /proc of failed slapd instance
http://launchpadlibrarian.net/49050824/slapd_procfiles.zip
--
slapd becomes non-responsive after several weeks runtime
https://bugs.launchpad.net/bugs/585208
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 574239] [NEW] ltsp-client should depend on or suggest cpufrequtils
Public bug reported: Thin clients installed by ltsp-build-client don't use their power management capabilities by default, because scaling_min_speed is set the same as scaling_max_speed in /sys/devices/system/cpu/cpu?/cpufreq . The cpufrequtils package provides init scripts that automatically enable the ondemand governor and set scaling_min_speed appropriately for the hardware, and offers additional configuration via /etc/default/cpufrequtils. This provides an immediate power use improvement on thin clients, also reducing heat and (for fan models) noise. It improves stability on hot Australian days, too! As it's harmless on machines that don't support CPU frequency scaling and offers big improvements on those that do, it'd be nice to see it included. ** Affects: ltsp (Ubuntu) Importance: Undecided Status: New -- ltsp-client should depend on or suggest cpufrequtils https://bugs.launchpad.net/bugs/574239 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 574239] Re: ltsp-client should depend on or suggest cpufrequtils
Oh: both client and server are now on lucid (10.04) but this report isn't really version specific. Please set importance wishlist. I can't. -- ltsp-client should depend on or suggest cpufrequtils https://bugs.launchpad.net/bugs/574239 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 572105] [NEW] update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update
Public bug reported: Binary package hint: update-manager The following version info is from AFTER the upgrade: r...@access:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04 LTS Release:10.04 Codename: lucid At several points during an upgrade from Ubuntu karmic to lucid, many services are restarted. Unfortunately, update-manager appears to make no effort to protect services currently required for core system functionality from being stopped, and it can hang at these points until those services are manually restarted by the admin. In my case, the problem service is slapd, because the system being upgraded is the LDAP master and it uses libpam-ldap and libnss-ldap (via the ldap-auth-client package) to do local authentication. If slapd is stopped, things tend to go very pear-shaped very fast with long timeouts and/or failures on system calls involving the nss subsystem. The same issue probably arises with other authentication mechanisms that rely on daemons that may be running locally. I noticed the upgrade hang after udev was updated and after libstdc++ was upgraded. In both cases ssh became non-responsive as did most other things. I had a local root console already open for just this situation, so I was able to restart slapd and get on with the install, but if I hand't been things could've been rather problematic I'm sure there are other packages that may restart things at inopportune times, or stop them and expect something else to start them well down the track rather than restarting them on the spot. One possible solution to this is to give the nss-ldap and nss-pam packages a way to protect slapd from being stopped during package installation, so it's only restarted momentarily at the end of the upgrade and when it its self is upgraded. Alternately, disabling ldap etc auth via nssswitch.conf during the upgrade would work. update-manager would need to make sure that the core system users and groups were still in /etc/passwd and /etc/group though, as if the admin's moved them to the external auth source then disabling that auth source would not go well. More package info: r...@access:~# apt-cache policy libpam-ldap libnss-ldap slapd ldap-auth-config ldap-auth-client update-manager update-manager-core libpam-ldap: Installed: 184-8ubuntu1 Candidate: 184-8.2ubuntu1 Version table: 184-8.2ubuntu1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages *** 184-8ubuntu1 0 100 /var/lib/dpkg/status libnss-ldap: Installed: 261-2.1ubuntu4 Candidate: 264-2ubuntu2 Version table: 264-2ubuntu2 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages *** 261-2.1ubuntu4 0 100 /var/lib/dpkg/status slapd: Installed: 2.4.21-0ubuntu5 Candidate: 2.4.21-0ubuntu5 Version table: *** 2.4.21-0ubuntu5 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status ldap-auth-config: Installed: 0.5.2 Candidate: 0.5.2 Version table: *** 0.5.2 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status ldap-auth-client: Installed: 0.5.2 Candidate: 0.5.2 Version table: *** 0.5.2 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status update-manager: Installed: (none) Candidate: 1:0.134.7 Version table: 1:0.134.7 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages update-manager-core: Installed: 1:0.126.9 Candidate: 1:0.134.7 Version table: 1:0.134.7 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages *** 1:0.126.9 0 100 /var/lib/dpkg/status ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- update-manager doesn't prevent restart of slapd on system using ldap auth, resulting in hung update https://bugs.launchpad.net/bugs/572105 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 572109] [NEW] failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg'
Public bug reported: Binary package hint: update-manager During a do-release-upgrade from a Karmic system to lucid (release), do- release-upgrade aborted with the following error: A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade is now aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. Traceback (most recent call last): File /tmp/tmp6njyKc/lucid, line 7, in module File /tmp/tmp6njyKc/DistUpgradeMain.py, line 158, in main File /tmp/tmp6njyKc/DistUpgradeController.py, line 1649, in run File /tmp/tmp6njyKc/DistUpgradeController.py, line 1636, in fullUpgrade File /tmp/tmp6njyKc/DistUpgradeController.py, line 1107, in doPostUpgrade File /tmp/tmp6njyKc/DistUpgradeController.py, line 172, in openCache File /tmp/tmp6njyKc/DistUpgradeCache.py, line 106, in __init__ File /tmp/tmp6njyKc/DistUpgradeConfigParser.py, line 51, in getListFromFile IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg' I've attached the full scrollback from my terminal as well as the requested files and the output of a dpkg --get-selections. Despite the Python exception, the upgrade appears to have completed fine (at least as far as apt is concerned). ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg' https://bugs.launchpad.net/bugs/572109 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 572109] Re: failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg'
** Attachment added: apt.log http://launchpadlibrarian.net/46521095/apt.log -- failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg' https://bugs.launchpad.net/bugs/572109 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 572109] Re: failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg'
** Attachment added: main.log http://launchpadlibrarian.net/46521118/main.log -- failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg' https://bugs.launchpad.net/bugs/572109 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 572109] Re: failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg'
** Attachment added: dpkg-selections.txt http://launchpadlibrarian.net/46521143/dpkg-selections.txt -- failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg' https://bugs.launchpad.net/bugs/572109 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 572109] Re: failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg'
** Attachment added: scrollback.txt http://launchpadlibrarian.net/46521177/scrollback.txt -- failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg' https://bugs.launchpad.net/bugs/572109 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 572109] Re: failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg'
/tmp/tmp6njyKc doesn't exist, as per the error message. Otherwise I would've attached it ;-) I do not run any aggressive temp-cleaning code. It's a really bog- standard Ubuntu install (recently clean-installed with Karmic on brand new disks, yesterday upgraded to Lucid), which is why this is so surprising. It's just running Bacula and PostgreSQL so it has no particularly interesting configuration or services. cr...@backup:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 15G 4.7G 9.3G 34% / none 1003M 344K 1002M 1% /dev none 1007M 0 1007M 0% /dev/shm none 1007M 76K 1007M 1% /var/run none 1007M 0 1007M 0% /var/lock none 1007M 0 1007M 0% /lib/init/rw none 15G 4.7G 9.3G 34% /var/lib/ureadahead/debugfs /dev/mapper/backup-bacula--main 1.6T 501G 1.1T 31% /srv/bacula-main /dev/mapper/backup-bacula--archives 4.0T 1.1T 3.0T 26% /srv/bacula-archives /dev/mapper/backup-bacula--wrk 1.0T 4.3M 1.0T 1% /srv/bacula-wrk /dev/mapper/backup-bacula--catalog 5.0G 138M 4.6G 3% /srv/bacula-catalog /dev/mapper/backup-bacula--bootstrap 249M 17M 220M 7% /srv/bacula-bootstrap /dev/mapper/backup-nonbacula 197G 15G 173G 8% /srv/nonbacula cr...@backup:~$ mount /dev/sda1 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw) none on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) none on /dev type devtmpfs (rw,mode=0755) none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) none on /dev/shm type tmpfs (rw,nosuid,nodev) none on /var/run type tmpfs (rw,nosuid,mode=0755) none on /var/lock type tmpfs (rw,noexec,nosuid,nodev) none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) none on /var/lib/ureadahead/debugfs type debugfs (rw,relatime) /dev/mapper/backup-bacula--main on /srv/bacula-main type xfs (rw,noatime,nodiratime) /dev/mapper/backup-bacula--archives on /srv/bacula-archives type xfs (rw,noatime,nodiratime,allocsize=512k,inode64) /dev/mapper/backup-bacula--wrk on /srv/bacula-wrk type xfs (rw,noatime,nodiratime) /dev/mapper/backup-bacula--catalog on /srv/bacula-catalog type ext4 (rw,noatime,nodiratime) /dev/mapper/backup-bacula--bootstrap on /srv/bacula-bootstrap type ext4 (rw,noatime,nodiratime) /dev/mapper/backup-nonbacula on /srv/nonbacula type ext4 (rw,noatime,nodiratime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) -- failed karmic-lucid do-release-upgrade: IOError: [Errno 2] No such file or directory: '/tmp/tmp6njyKc/removal_blacklist.cfg' https://bugs.launchpad.net/bugs/572109 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 566832] Re: kvm expect PXE rom to be in /usr/share/qemu
This is arguably a kvm bug, in that kvm should check /usr/share/kvm instead of or as well as /usr/share/qemu , so I've added kvm to the affects list. I can confirm this issue in Lucid as of five minutes ago: $ apt-cache policy kvm kvm-pxe kvm: Installed: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 Candidate: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 Version table: *** 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status kvm-pxe: Installed: 5.4.4-1ubuntu1 Candidate: 5.4.4-1ubuntu1 Version table: *** 5.4.4-1ubuntu1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/universe Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04 LTS Release:10.04 Codename: lucid ** Also affects: kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- kvm expect PXE rom to be in /usr/share/qemu https://bugs.launchpad.net/bugs/566832 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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 566832] Re: kvm expect PXE rom to be in /usr/share/qemu
This is arguably a kvm bug, in that kvm should check /usr/share/kvm instead of or as well as /usr/share/qemu , so I've added kvm to the affects list. I can confirm this issue in Lucid as of five minutes ago: $ apt-cache policy kvm kvm-pxe kvm: Installed: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 Candidate: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 Version table: *** 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status kvm-pxe: Installed: 5.4.4-1ubuntu1 Candidate: 5.4.4-1ubuntu1 Version table: *** 5.4.4-1ubuntu1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/universe Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04 LTS Release:10.04 Codename: lucid ** Also affects: kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- kvm expect PXE rom to be in /usr/share/qemu https://bugs.launchpad.net/bugs/566832 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 366101] Re: Evolution slows down and nearly freezes when bringing up a new compose window
A patch to gtk to address this issue was merged upstream quite some time ago, so it should be resolved by now. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- Evolution slows down and nearly freezes when bringing up a new compose window https://bugs.launchpad.net/bugs/366101 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 570870] Re: pxe boot doesn't work with kvm
A safer way to tackle this that will avoid breaking things and permit software that's come to expect things to live where kvm-pxe used to put them is to just install some suitable symlinks. See attached patch. ** Patch added: etherboot-pxe-firmware-paths.diff http://launchpadlibrarian.net/45909355/etherboot-pxe-firmware-paths.diff -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 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 567268] Re: NetworkManager leaves garbage in essid after disconnect
Re-tested with current (as of five minutes ago) lucid, post-alpha-2. Problem still exists. cr...@ayaki:~$ iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:aloe Mode:Managed Frequency:2.437 GHz Access Point: 00:13:46:27:6B:41 Bit Rate=1 Mb/s Tx-Power=14 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=64/70 Signal level=-46 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 cr...@ayaki:~$ iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:g\xC6isQ\xFFJ\xEC)\xCD\xBA\xAB\xF2\xFB\xE3F|\xC2T\xF8\x1B\xE8\xE7\x8DvZ.c3\x9F\xC9\x9A Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Tx-Power=14 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off Linux ayaki 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 i686 GNU/Linux cr...@ayaki:~$ apt-cache policy network-manager network-manager: Installed: 0.8-0ubuntu3 Candidate: 0.8-0ubuntu3 Version table: *** 0.8-0ubuntu3 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status -- NetworkManager leaves garbage in essid after disconnect https://bugs.launchpad.net/bugs/567268 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 567268] Re: NetworkManager leaves garbage in essid after disconnect
Note that this bug doesn't seem to actually cause any kind of breakage. It's just ugly, and may indicate useof unitialized/freed memory or an improperly terminated string somewhere in the nm code, which may become a problem later. -- NetworkManager leaves garbage in essid after disconnect https://bugs.launchpad.net/bugs/567268 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 567268] [NEW] NetworkManager leaves garbage in essid after disconnect
Public bug reported: Binary package hint: network-manager NetworkManager appears to fill the essid with garbage when it disconnects from a network as part of disabling networking (ie: right click on nm applet, uncheck enable networking). cr...@ayaki:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu lucid (development branch) Release:10.04 Codename: lucid cr...@ayaki:~$ apt-cache policy network-manager network-manager: Installed: 0.8-0ubuntu3 Candidate: 0.8-0ubuntu3 Version table: *** 0.8-0ubuntu3 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status cr...@ayaki:~$ uname -a Linux ayaki 2.6.32-20-generic #29-Ubuntu SMP Fri Apr 9 20:35:55 UTC 2010 i686 GNU/Linux While connected to wifi, as normal: r...@ayaki:~# iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:madradish Mode:Managed Frequency:2.437 GHz Access Point: 00:12:BF:09:E1:76 Bit Rate=1 Mb/s Tx-Power=14 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:3132-3334-35 Power Management:off Link Quality=42/70 Signal level=-68 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 After disconnection, note the garbage essid: r...@ayaki:~# iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:p\xE9\xA1A\xE1\xFCg\x01~\x97\xEA\xDCk\x96\x8F8\*\xEC\xB0;\xFB2\xAFT\xEC\x18\xDB\ Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Tx-Power=14 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off I never noticed this before upgrading to lucid (pre) and therefore from NM 0.7 to NM 0.8 . While that doesn't mean it wasn't happening, I tend to use iwconfig and would expect to have noticed. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager leaves garbage in essid after disconnect https://bugs.launchpad.net/bugs/567268 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 567268] Re: NetworkManager leaves garbage in essid after disconnect
It also happens if I disconnect from the wireless using the Enable
Wireless check box.
cr...@ayaki:~$ iwconfig wlan0
wlan0 IEEE 802.11abgn
ESSID:\x02\x1A\xFEC\xFB\xFA\xAA:\xFB)\xD1\xE6\x05|\x94u\xD8\xBEa\x89\xF9\\xBB\xA8\x99\x0F\x95\xB1\xEB\xF1\xB3
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=14 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
or even leaving wireless enabled and using the Disconnect menu option:
cr...@ayaki:~$ iwconfig wlan0
wlan0 IEEE 802.11abgn
ESSID:\x05\xEF\xF7\x00\xE9\xA1:\xE5\xCA\x0B\xCB\xD0HGd\xBD\x1F#\x1E\xA8\x1C{d\xC5\x14sZ\xC5^Kyc
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=14 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
I smell a string null termination bug...
--
NetworkManager leaves garbage in essid after disconnect
https://bugs.launchpad.net/bugs/567268
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 567268] Re: NetworkManager leaves garbage in essid after disconnect
Wifi card info: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) Subsystem: Intel Corporation Device 1120 0c:00.0 0280: 8086:4229 (rev 61) Subsystem: 8086:1120 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 30 Region 0: Memory at f1ffe000 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlagn Kernel modules: iwlagn cr...@ayaki:~$ modinfo iwlagn filename: /lib/modules/2.6.32-20-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko alias: iwl4965 license:GPL author: Copyright(c) 2003-2009 Intel Corporation i...@linux.intel.com version:1.3.27k description:Intel(R) Wireless WiFi Link AGN driver for Linux firmware: iwlwifi-4965-2.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-2.ucode firmware: iwlwifi-6050-4.ucode firmware: iwlwifi-6000-4.ucode srcversion: 9B8B8B62434B92B6793FD7A -- NetworkManager leaves garbage in essid after disconnect https://bugs.launchpad.net/bugs/567268 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 562278] [NEW] plymouth check for splash in cmdline incorrectly matches nosplash too
Public bug reported: Binary package hint: plymouth Distributor ID: Ubuntu Description:Ubuntu lucid (development branch) Release:10.04 Codename: lucid plymouth: Installed: 0.8.1-4ubuntu1 Candidate: 0.8.1-4ubuntu1 Version table: *** 0.8.1-4ubuntu1 0 500 http://ftp.iinet.net.au/pub/ubuntu/ lucid/main Packages 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Plymouth sees a kernel command line containing the text 'splash' anywhere in it as a request to show a splash screen. This includes a kernel command line containing nosplash or any other text with splash in it. As nosplash used to be a way to get rid of the accursed splash screen back in the day, it's not unheard of to see it on kernel command lines. The test in main.c:615 in the function plymouth_should_show_default_splash(state_t * state) reveals why. return strstr (state-kernel_command_line, rhgb) != NULL || (strstr (state-kernel_command_line, splash) != NULL strstr(state-kernel_command_line, splash=verbose) == NULL); the test for splash will match any substring. It should be checking for splash with a trailing space or end-of-string. Removing nosplash from my kernel command line got rid of the splash screen :S ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New -- plymouth check for splash in cmdline incorrectly matches nosplash too https://bugs.launchpad.net/bugs/562278 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 562278] Re: plymouth check for splash in cmdline incorrectly matches nosplash too
The attached patch adds a simple function that does a more robust check for a keyword in the kernel command line, and converts the problem function to use it. Plymouth makes ... iffy ... keyword checks in many other places, and these should probably use the function as well. Pretty much anywhere state-kernel_command_line is referenced. ** Patch added: Proposed fix http://launchpadlibrarian.net/44038361/plymouth-fix-state.diff -- plymouth check for splash in cmdline incorrectly matches nosplash too https://bugs.launchpad.net/bugs/562278 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 560491] Re: [lucid beta2] Plymouth does not honor nosplash
This bug is caused by a bug in Plymouth's kernel command line parsing, causing it to see splash on the kernel command line and thus think it's been asked to show a splash screen when nosplash or any other string containing splash as a substring appears on the command line. I've attached a patch that fixes the way plymouth looks for keywords in the kernel command line. ** Patch added: Fix plymouth's keyword check in kernel command line http://launchpadlibrarian.net/44091238/plymouth-fix-state.diff -- [lucid beta2] Plymouth does not honor nosplash https://bugs.launchpad.net/bugs/560491 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 546723] [NEW] no useful errors if tls certs missing or unreadable
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 9.10 Release:9.10 Codename: karmic # libvirtd --version libvirtd (libvirt) 0.7.0 ii libvirt0 0.7.0-1ubuntu13.1 if listen_tls = 1 is set in libvirtd.conf, but the certs required aren't present in /etc/pki, libvirtd silently fails to launch, returning with error code 0 (success) and so confusing start-stop-daemon into thinking it launched. libvirtd SHOULD: - print an error mesage like libvirtd: listen_tls set but /etc/pki/CA/cacert.pem not found, cannot launch - return a non-zero error code - if listen_tls or listen_tcp are set but --listen is not specified on the command line, log/print a warning like WARNING: listen_tls or listen_tcp enabled but --listen not specified on the command line. libvirtd will not listen on the network. This probably qualifies as an upstream bug more than anything, BUT ubuntu's config file for libvirtd needs to at least mention the certificate paths in the comments for listen_tls. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- no useful errors if tls certs missing or unreadable https://bugs.launchpad.net/bugs/546723 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 546723] Re: no useful errors if tls certs missing or unreadable
Also, Ubuntu's libvirt packages should probably provide a skeleton /etc/pki which has symlinks to the default certs generated by snakeoil . -- no useful errors if tls certs missing or unreadable https://bugs.launchpad.net/bugs/546723 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 546745] [NEW] libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs
Public bug reported: Description:Ubuntu 9.10 Release:9.10 Codename: karmic libvirtd (libvirt) 0.7.0 /etc/libvirt/libvirtd.conf contains the comment: # - sasl: use SASL infrastructure. The actual auth scheme is then # controlled from /etc/sasl2/libvirt.conf. For the TCP # socket only GSSAPI DIGEST-MD5 mechanisms will be used. # For non-TCP or TLS sockets, any scheme is allowed. # yet strace'ing libvirtd startup reveals that it's actually looking for /etc/sasl/libvirt.conf, which is why sasl authentication is not working . It should be reading /etc/sasl2/libvirt.conf. Once /etc/sasl2 is symlinked to /etc/sasl, it still fails, but that's another bug. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs https://bugs.launchpad.net/bugs/546745 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 546723] [NEW] no useful errors if tls certs missing or unreadable
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 9.10 Release:9.10 Codename: karmic # libvirtd --version libvirtd (libvirt) 0.7.0 ii libvirt0 0.7.0-1ubuntu13.1 if listen_tls = 1 is set in libvirtd.conf, but the certs required aren't present in /etc/pki, libvirtd silently fails to launch, returning with error code 0 (success) and so confusing start-stop-daemon into thinking it launched. libvirtd SHOULD: - print an error mesage like libvirtd: listen_tls set but /etc/pki/CA/cacert.pem not found, cannot launch - return a non-zero error code - if listen_tls or listen_tcp are set but --listen is not specified on the command line, log/print a warning like WARNING: listen_tls or listen_tcp enabled but --listen not specified on the command line. libvirtd will not listen on the network. This probably qualifies as an upstream bug more than anything, BUT ubuntu's config file for libvirtd needs to at least mention the certificate paths in the comments for listen_tls. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- no useful errors if tls certs missing or unreadable https://bugs.launchpad.net/bugs/546723 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 546723] Re: no useful errors if tls certs missing or unreadable
Also, Ubuntu's libvirt packages should probably provide a skeleton /etc/pki which has symlinks to the default certs generated by snakeoil . -- no useful errors if tls certs missing or unreadable https://bugs.launchpad.net/bugs/546723 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 546745] [NEW] libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs
Public bug reported: Description:Ubuntu 9.10 Release:9.10 Codename: karmic libvirtd (libvirt) 0.7.0 /etc/libvirt/libvirtd.conf contains the comment: # - sasl: use SASL infrastructure. The actual auth scheme is then # controlled from /etc/sasl2/libvirt.conf. For the TCP # socket only GSSAPI DIGEST-MD5 mechanisms will be used. # For non-TCP or TLS sockets, any scheme is allowed. # yet strace'ing libvirtd startup reveals that it's actually looking for /etc/sasl/libvirt.conf, which is why sasl authentication is not working . It should be reading /etc/sasl2/libvirt.conf. Once /etc/sasl2 is symlinked to /etc/sasl, it still fails, but that's another bug. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs https://bugs.launchpad.net/bugs/546745 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 491236] Re: aptitude does not respect /etc/apt/preferences
Ouch. This just upgraded my netatalk package, replacing my openssl- enabled version and knocking all the Mac OS 9 clients used for running critical legacy apps off the network. Yes, I should've noticed it in the (huge) list of packages affected, but then aptitude shouldn't have upgraded it either. $ cat /etc/apt/preferences.d/netatalk Package: netatalk Pin: origin Pin-Priority: 1001 Prefer aptitude over apt-get, indeed. -- aptitude does not respect /etc/apt/preferences https://bugs.launchpad.net/bugs/491236 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 491236] Re: aptitude does not respect /etc/apt/preferences
Correction. My issue is, more strictly, https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/508545 on aptitude 0.4.11.11 (ubuntu 10.04) -- aptitude does not respect /etc/apt/preferences https://bugs.launchpad.net/bugs/491236 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 508545] Re: Aptitude ignores preferences.d/*
Still affects aptitude 0.4.11.11 on Ubuntu 10.04 as of 24 Mar 2010. It just merrily munched my custom-rebuilt netatalk package, knocking all the Mac OS 9 systems required for critical legacy apps off the network. Ouch! $ cat /etc/apt/preferences.d/netatalk Package: netatalk Pin: origin Pin-Priority: 1001 $ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: netatalk 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. $ sudo aptitude safe-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Writing extended state information... Done The following packages will be upgraded: netatalk The following packages are RECOMMENDED but will NOT be installed: libpam-cracklib rc 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/831kB of archives. After unpacking 81.9kB will be freed. Do you want to continue? [Y/n/?] -- Aptitude ignores preferences.d/* https://bugs.launchpad.net/bugs/508545 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 508545] Re: Aptitude ignores preferences.d/*
Closely related to https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/491236 -- Aptitude ignores preferences.d/* https://bugs.launchpad.net/bugs/508545 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 26452] Re: netatalk not built with encrypted auth support
... however, dhx2 doesn't work with Mac OS 9 clients. 'cleartext' auth doesn't support password lengths 8 chars, so if you have a users with longer passwords they'll be locked out. Those of us unfortunate enough to be supporting such dinosaurs can get NetATalk to build against OpenSSL quite easily thanks to the thoughtful package maintainers. Just: $ cd debtmp $ mkdir debtmp $ apt-get source netatalk $ apt-get install libcups2-dev $ apt-get build-dep netatalk $ cd netatalk-2.0.4~beta2 $ DEB_BUILD_OPTIONS=openssl fakeroot debian/rules binary $ sudo dpkg -i ../netatalk_2.0.4~beta2-5ubuntu2_i386.deb (Versions may need adapting as appropriate). This rebuilds NetATalk against OpenSSL, restoring the uams_dhx_pam and uams_dhx_randnum modules. -- netatalk not built with encrypted auth support https://bugs.launchpad.net/bugs/26452 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 535517] [NEW] netatalk fails to generate unique server signatures
Public bug reported: Binary package hint: netatalk Description:Ubuntu 9.10 Release:9.10 ii netatalk 2.0.4~beta2-5ubuntu2 AppleTalk user binaries NetATalk fails to generate a unique server signature. Analysis of client/server communication reveals that both NetATalk servers here report the signature 01017F0001017F0001017F0001017F00 . This confuses Mac clients, resulting in them apparently randomly directing AFP requests to one server or the other. Users will connect to SERVER1 and get a volume list from SERVER2 or vice versa. The netatalk code for generating server signatures (etc/afpd/status.c:191) uses the libc gethostid() call to obtain a 32-bit unique identifier for the host. GNU Libc's man page for gethostid(3) notes that: In the glibc implementation, the hostid is stored in the file /etc/hostid. (In glibc versions before 2.2, the file /var/adm/hostid was used.) In the glibc implementation, if gethostid() cannot open the file containing the host ID, then it obtains the hostname using gethostname(2), passes that hostname to gethostbyname_r(3) in order to obtain the host's IPv4 address, and returns a value obtained by bit-twiddling the IPv4 address. (This value may not be unique.) Ubuntu systems do not have any /etc/hostid by default, so glibc falls back on gethostbyname_r(3). However, Ubuntu systems' /etc/hosts files map the hostname to 127.0.0.1: 127.0.0.1 localhost 127.0.1.1 HOSTNAME.localnetHOSTNAME so gethostbyname_r for the hostname in /etc/hostname will always return 127.0.0.1 . gethostid(3) will therefore always return the same value, and NetATalk's system id will always be the same on different Ubuntu hosts. ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: netatalk (Ubuntu) Importance: Undecided Status: New -- netatalk fails to generate unique server signatures https://bugs.launchpad.net/bugs/535517 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 535517] Re: netatalk fails to generate unique server signatures
** Attachment added: libpcap format dump showing identical signatures from different hosts http://launchpadlibrarian.net/40668887/packettrace.pcap -- netatalk fails to generate unique server signatures https://bugs.launchpad.net/bugs/535517 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 535517] Re: netatalk fails to generate unique server signatures
** Attachment added: Text export of client/server chat with identical signatures http://launchpadlibrarian.net/40668914/packettrace.txt ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu) Importance: Undecided Status: New -- netatalk fails to generate unique server signatures https://bugs.launchpad.net/bugs/535517 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 535517] Re: netatalk fails to generate unique server signatures
Filed upstream bug: https://sourceforge.net/tracker/index.php?func=detailaid=2967179group_id=8642atid=108642 (Couldn't see how to link it to this bug in Launchpad) ** Bug watch added: SourceForge.net Tracker #2967179 http://sourceforge.net/support/tracker.php?aid=2967179 -- netatalk fails to generate unique server signatures https://bugs.launchpad.net/bugs/535517 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 535517] Re: netatalk fails to generate unique server signatures
A workaround for admins: to each line in your afpd.conf, append an explicit: -signature user:SERVERNAME (if you have more than one line in afpd.conf, make sure the signature is unique for each one). -- netatalk fails to generate unique server signatures https://bugs.launchpad.net/bugs/535517 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 535517] Re: netatalk fails to generate unique server signatures
** Also affects: coreutils (Ubuntu) Importance: Undecided Status: New -- netatalk fails to generate unique server signatures https://bugs.launchpad.net/bugs/535517 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 242842] Re: Thunar overrides the user's umask
Michael: That test is invalid, and shows nothing. You've misunderstood how the umask works. In a UNIX system, things like environment variables, ulimit settings and the umask are inherited from the parent process during process creation. Your test has a process tree like this: Thunar terminal bash and you're changing the umask in the 'bash' process that you then terminate by closing the terminal. Nothing else has changed. (Technically the terminal process is probably a peer of Thunar rather than a child, despite having been created by Thunar, because Thunar detaches from it to avoid killing it if Thunar dies or is restarted - but that doesn't really matter for the purposes of this discussion). Additionally, you're trying to test by setting the umask then checking it again later. This fails to detect the case where Thunar isn't changing the umask, but rather overriding it in individual mkdir(...) etc system calls. Which is what it was doing, by the way, before this bug was fixed - it wasn't setting the umask, but rather was ignoring it and specifying its own mask for file and directory operations. A valid test would be to launch a terminal, kill Thunar, set your umask, then re-launch Thunar from within that terminal session, then create a directory using that Thunar process and see if it's permissions (shown using 'ls -l') are appropriate for the umask you set. Better, set your umask globally using PAM options, /etc/profile, or (preferably) a new file in /etc/X11/XSession.d for the purpose. Be aware that if you set your umask in /etc/profile or by PAM it might get overridden by your X session startup scripts in some distros. That's *NOT* to do with Thunar. ** Changed in: thunar (Ubuntu) Status: Confirmed = Fix Released ** Changed in: thunar (Ubuntu) Status: Fix Released = Fix Committed -- Thunar overrides the user's umask https://bugs.launchpad.net/bugs/242842 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 242842] Re: Thunar overrides the user's umask
Michael: Yep, that's ugly. It actually is properly associated with this bug, too, as the patch Debian and Ubuntu have for Thunar is completely borked. The umask patch: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/jaunty/thunar/jaunty/revision/58 is at fault for this. It calls: umask(0) thus changing the user's umask (wtf?!?). It does so in a really bizarre way: + if (!_thunar_vfs_io_ops_mkdir (lp-data, 0777 ~umask(0), THUNAR_VFS_IO_OPS_NONE, error)) ... that makes me think that whoever wrote that completely fails to understand how the umask works and what it does. People seem to be unable to understand that *they* *don't* *have* *to* *mess* *with* *the* *umask*. It's a *mask* and is applied automatically by libc to mask out disallowed permissions bits, so the app just asks for the most general permissions that make sense (0666 for files, 0777 for dirs) unless it has a really good reason (like creating a file to contain a private key) not to. My original patch for this issue works fine and gets this right. I have no idea why the above was used instead. Karmic carries a correct patch; the same patch just needs to be applied to Jaunty. ** Changed in: thunar (Ubuntu Jaunty) Status: Incomplete = Confirmed -- Thunar overrides the user's umask https://bugs.launchpad.net/bugs/242842 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 242842] Re: Thunar overrides the user's umask
... however, Jaunty isn't a LTS release and has been superceded by Karmic, so I don't know if anyone with the power to do so will/can actually merge the patch that corrects this: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/karmic/thunar/karmic/revision/61/debian/patches/04_fix- umask-handling.patch If upgrading isn't an option, you can apt-get source thunar, apply the patch, and then `fakeroot debian/rules binary' to build new patches. (Oversimplified - see Google for instructions on manually patching Debian packages). -- Thunar overrides the user's umask https://bugs.launchpad.net/bugs/242842 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 417695] Re: ALSA/PulseAudio output connector identification wrong on Dell XPS M1330 (Karmic A3)
** Attachment added: lspci -vvnn http://launchpadlibrarian.net/30692914/lspci.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/30692915/Dependencies.txt -- ALSA/PulseAudio output connector identification wrong on Dell XPS M1330 (Karmic A3) https://bugs.launchpad.net/bugs/417695 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 417695] [NEW] ALSA/PulseAudio output connector identification wrong on Dell XPS M1330 (Karmic A3)
Public bug reported: Binary package hint: gnome-media gnome-volume-control or the underlying PulseAudio / ALSA system(s) misidentify the output channels on this Dell XPS M1330 laptop. The Analog Output connector, which is selected by default, is the 2ndary headphone / line out port. The Analog Headphones connector, which is not the default selection, is the main headphone connector and (if no headphones are connected) drives the built-in speakers. ProblemType: Bug Architecture: i386 Date: Sun Aug 23 20:38:01 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-media 2.27.90-0ubuntu1 [modified: usr/bin/gnome-audio-profiles-properties usr/bin/gnome-sound-recorder usr/bin/gnome-volume-control usr/bin/gnome-volume-control-applet usr/bin/gstreamer-properties] ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-6.25-generic SourcePackage: gnome-media Uname: Linux 2.6.31-6-generic i686 ** Affects: gnome-media (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- ALSA/PulseAudio output connector identification wrong on Dell XPS M1330 (Karmic A3) https://bugs.launchpad.net/bugs/417695 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 417695] Re: ALSA/PulseAudio output connector identification wrong on Dell XPS M1330 (Karmic A3)
$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu karmic (development branch) Release:9.10 Codename: karmic $ uname -a Linux ayaki 2.6.31-6-generic #25-Ubuntu SMP Fri Aug 14 16:25:04 UTC 2009 i686 GNU/Linux ** Attachment added: dmesg.txt http://launchpadlibrarian.net/30692938/dmesg.txt -- ALSA/PulseAudio output connector identification wrong on Dell XPS M1330 (Karmic A3) https://bugs.launchpad.net/bugs/417695 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 401442] [NEW] Upstream evolution patch rel 2.26.2 fixes messages marked read in junk folder
Public bug reported: Binary package hint: evolution I'm being bitten by an issue where Evolution is helpfully marking messages it filters into the user's junk folder as read. This makes it much harder for the user to occasionally check the junk folder to see if legit messages have been trapped. This isssue has been fixed in Evolution upstream patch release on the 2.26 series (2.26.2). Updating the Hardy packages to that patch release in hardy-updates would be rather handy, as it's not the only significant fix in the release. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- Upstream evolution patch rel 2.26.2 fixes messages marked read in junk folder https://bugs.launchpad.net/bugs/401442 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 401442] Re: Upstream evolution patch rel 2.26.2 fixes messages marked read in junk folder
hardy-updates? Sorry, brain fart. jaunty-updates is a lot saner, given that the package in question is 2.26.1-0ubuntu2 in Jaunty. -- Upstream evolution patch rel 2.26.2 fixes messages marked read in junk folder https://bugs.launchpad.net/bugs/401442 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 181576] Re: Can't disable junk filtering
It's a bug alright, though the original reporter may not have been as clear about it as they should. Junk filtering is DISABLED in evolution (edit - preferences - junk, ensure check incoming messages for junk is unchecked and to be safe uncheck check custom headers for junk). Despite that, messages are shown in the junk vfolder on my users' Evolution IMAP accounts (backed by Cyrus IMAPd). As junk filtering was _never_ _enabled_ on the account, there is no way the junk folder could/should contain messages. The immediate cause of the messages appearing in Junk is that they have the Junk IMAP flag set. At least, that's how it looks from digging through CAMEL_DEBUG=all CAMEL_DEBUG_VERBOSE=all output: sexp is : [(match-all (system-flag Junk))] Equivalent sql SELECT uid FROM 'Inbox' WHERE (junk = 1) So - we know why they're appearing in Junk, but not how they got the Junk IMAP flag set. None of the messages it's hiding as junk have X -Spam-Flag or X-Spam-Level headers. Bogofilter shouldn't be being run as junk filtering is disabled. So how are they getting flagged? One of the journalists at work missed a story because of this bug/feature after we moved from Thunderbird to Evolution on the thin clients. Evo decided that half her mail was junk and quietly ate it. I'm encountering this on a Jaunty system with evolution 2.26.1-0ubuntu2. The account is an IMAP account talking to a Cyrus IMAPd server. ** Changed in: evolution (Ubuntu) Status: Invalid = New ** Summary changed: - Can't disable junk filtering + Messages flagged as Junk even when junk filtering off (IMAP) -- Messages flagged as Junk even when junk filtering off (IMAP) https://bugs.launchpad.net/bugs/181576 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 181576] Re: Messages flagged as Junk even when junk filtering off (IMAP)
Further investigation reveals that the issue is mostly (entirely?) confined to one user account. While many accounts have messages with the IMAP Junk flag set, most are older messages that could well have been manually set by the user with Thunderbird. However, they could also have been set by Evolution when first loading the mailbox, and there's not really any way to tell. I do have one user account which had junk filtering enabled but LOTS of mail landing up in the Junk vfolder folder. Another account has had a few recent messsages leak into the Junk vfolder (ie flagged as Junk in INBOX). In both cases it is EXTREMELY unlikely that the user would've intentionally flagged the email as Junk. One case could be explained as mis-clicks, but in the other case about 1/3 of mail was flagged as Junk with no discernable pattern. -- Messages flagged as Junk even when junk filtering off (IMAP) https://bugs.launchpad.net/bugs/181576 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 311982] Re: Array too big when printing large image
Please disregard my previous report. The CUPS server was finding printers exported by a Debian Lenny box. Lenny's poppler source package lacks debian/patches/63_do-not-make-ps-arrays-bigger-than-64k-from-big- images-in-patterns.patch . ** Changed in: eog (Ubuntu) Status: New = Invalid ** Changed in: eog (Ubuntu Intrepid) Status: New = Invalid -- Array too big when printing large image https://bugs.launchpad.net/bugs/311982 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 311982] Re: Array too big when printing large image
eog also appears to produce oversize arrays when printing large images, resulting in errors like: D [25/Jun/2009:16:53:00 +0800] [Job 172688] Error: /limitcheck in --array-- D [25/Jun/2009:16:53:00 +0800] [Job 172688] Operand stack: D [25/Jun/2009:16:53:00 +0800] [Job 172688] 90223 D [25/Jun/2009:16:53:00 +0800] [Job 172688] Execution stack: D [25/Jun/2009:16:53:00 +0800] [Job 172688] %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- D [25/Jun/2009:16:53:00 +0800] [Job 172688] Dictionary stack: D [25/Jun/2009:16:53:00 +0800] [Job 172688] --dict:1152/1684(ro)(G)-- --dict:0/20(G)-- --dict:93/200(L)-- --dict:66/75(L)-- D [25/Jun/2009:16:53:00 +0800] [Job 172688] Current allocation mode is local D [25/Jun/2009:16:53:00 +0800] [Job 172688] Last OS error: 2 D [25/Jun/2009:16:53:00 +0800] [Job 172688] GPL Ghostscript 8.62: Unrecoverable error, exit code 1 E [25/Jun/2009:16:53:01 +0800] PID 21114 (/usr/lib/cups/filter/pstoraster) stopped with status 1! ** Also affects: eog (Ubuntu) Importance: Undecided Status: New -- Array too big when printing large image https://bugs.launchpad.net/bugs/311982 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 311982] Re: Array too big when printing large image
Ah - I only just noticed that this bug had been targeted specifically at poppler. The issue is on eog 2.26.1 on Jaunty with all updates. I'll file a new bug. -- Array too big when printing large image https://bugs.launchpad.net/bugs/311982 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 386199] Re: Long delay before new/compose window appears
Matthias Clasen from Red Hat tackled the underlying gtk+ bug ( http://bugzilla.gnome.org/show_bug.cgi?id=585626 ) and has committed a patch to gtk+ head that dramatically improves things. See the gtk+ bug I've linked to for his patch, and some instructions I've written on easily applying the fix to your Ubuntu system without having to change anything else if you suffer from the same issue. ** Changed in: evolution (Ubuntu) Status: Triaged = In Progress ** Changed in: gtkhtml Importance: Unknown = Undecided ** Changed in: gtkhtml Remote watch: GNOME Bug Tracker #585626 = None ** Changed in: gtkhtml Status: New = Invalid ** Also affects: libgtk via http://bugzilla.gnome.org/show_bug.cgi?id=585626 Importance: Unknown Status: Unknown ** Changed in: evolution Importance: Unknown = Undecided ** Changed in: evolution Remote watch: GNOME Bug Tracker #585624 = None ** Changed in: evolution Status: New = Invalid -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 366101] Re: Evolution slows down and nearly freezes when bringing up a new compose window
Looks like a tracker issue. Ick. Bugs of interest: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/190918 https://bugs.launchpad.net/ubuntu/+bug/218230 ** Also affects: linux Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #575821 http://bugzilla.gnome.org/show_bug.cgi?id=575821 ** Also affects: tracker via http://bugzilla.gnome.org/show_bug.cgi?id=575821 Importance: Unknown Status: Unknown -- Evolution slows down and nearly freezes when bringing up a new compose window https://bugs.launchpad.net/bugs/366101 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 386199] Re: Long delay before new/compose window appears
** Bug watch added: GNOME Bug Tracker #585624 http://bugzilla.gnome.org/show_bug.cgi?id=585624 ** Also affects: evolution via http://bugzilla.gnome.org/show_bug.cgi?id=585624 Importance: Unknown Status: Unknown -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
Cloning my comment from the GNOME bug, since I've identified pretty much exactly what factor controls whether or not this issue happens: If you enable your local X server to listen on TCP/IP (on most GNOME desktops, edit /etc/gdm/gdm.conf (may be /etc/X11/gdm/gdm.conf depending on distro/version) and change DisallowTCP=true to DisallowTCP=false then restart GDM, you can reproduce this running directly on your normal X server. If you run with DISPLAY=:0.0 (assuming you're on DISPLAY 0) the compose window appears in about a second. If you run with DISPLAY=127.0.0.1:0.0 it takes 15 or more seconds to appear. Here's an interesting example. I have two terminals, with prompts T1$ and T2$ . In T1 I'll launch Evolution, talking on a UNIX domain socket. On T2 I'll then time how long it takes to open a compose window by using the command time evolution mailto:t...@nowhere.org;. The remote invocation only terminates when the mail window has displayed, so we can time how long it takes to display quite accurately. Once I've timed that, I'll exit evolution on T1, reopen it with a TCP/IP connection, and repeat the test on T2. Observe the difference: T1$ DISPLAY=:0.0 evolution ** (evolution:26183): DEBUG: EI: SHELL STARTUP ** (evolution:26183): DEBUG: EI: mail_read_notify ** (evolution:26183): DEBUG: MAIL SERVER: Count changed: 0 T2$ time evolution mailto:t...@nowhere.org real0m0.830s user0m0.160s sys 0m0.030s T1$ DISPLAY=127.0.0.1:0 evolution ** (evolution:26236): DEBUG: EI: SHELL STARTUP ** (evolution:26236): DEBUG: EI: mail_read_notify ** (evolution:26236): DEBUG: MAIL SERVER: Count changed: 0 T2$ time evolution mailto:t...@nowhere.org real0m16.742s user0m0.180s sys 0m0.030s 0.8 seconds vs 16.7 seconds. The only difference is TCP/IP vs UNIX domain socket comms. -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
** Bug watch added: GNOME Bug Tracker #585626 http://bugzilla.gnome.org/show_bug.cgi?id=585626 ** Also affects: gtkhtml via http://bugzilla.gnome.org/show_bug.cgi?id=585626 Importance: Unknown Status: Unknown -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
** Attachment added: Quick gtkhtml hack/workaround http://launchpadlibrarian.net/27859768/bug585626.diff -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
It's a gtkhtml bug, or possibly a libgtk+ bug. A workaround is to patch libgtkhtml and rebuild it. Instructions: $ sudo apt-get install fakeroot build-essential wget $ sudo apt-get build-dep gtkhtml3.14 $ mkdir $HOME/gtkhtml $ cd $HOME/gtkhtml $ apt-get source gtkhtml3.14 $ wget http://launchpadlibrarian.net/27859768/bug585626.diff $ patch -p0 bug585626.diff $ ( cd gtkhtml3.14-* fakeroot debian/rules binary ) $ sudo dpkg -i *.deb Your changes WILL BE AUTOMATICALLY REPLACED next time gtkhtml is updated, so this is only a quick-and-dirty fix. (Yes, you can use pinning or the like to retain them, but if you need to know how to unpin later, remember to , etc, or things may go pear-shaped, so I won't explain that here). -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 220005] Re: xrdp package doesn't work out of box
xrdp is _severely_ bugged when using vnc4server as a backend. gnome- panel tends to launch, then crash out with a BadWindow xlib error, resulting in a flickering gnome-panel and otherwise a default stippled x server background. If you remove vnc4server and install xtightvnc, login should work. However, at least on the systems I've tried, the gnome theme seems to be constantly reset to a flat generic theme and the keyboard mapping is completely insane (dvorak? something similarly mad). At present, xrfb seems pretty broken. -- xrdp package doesn't work out of box https://bugs.launchpad.net/bugs/220005 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 220005] Re: xrdp package doesn't work out of box
Sorry - install tightvncserver, not xtightvnc. And I meant xrdp not xrfb at the end there. -- xrdp package doesn't work out of box https://bugs.launchpad.net/bugs/220005 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 386199] Re: Long delay before new/compose window appears
** Attachment added: libpcap format protocol trace of X11 network comms during compose window open. http://launchpadlibrarian.net/27805425/trace.pcap -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] [NEW] Long delay before new/compose window appears
Public bug reported: On my remote X11 clients, Evolution takes 20 - 30 seconds to display the compose / reply window. This happens on all clients, including a PXE- booted KVM virtual machine and a Xephyr X server. The problem occurs whether the X11 connection is ssh-tunneled or is a direct connection in the clear (using XDMCP). Performance is otherwise normal, in Evolution and elsewhere. Tracker has been removed. libtrackerclient is still installed as it's required by Totem, but Evolution does not link to it according to `ldd'. IPv6 has been disabled, as previous bug reports have indicated that IPv6 may be the issue. `ip -6 r s' shows no routes, there are no inet6 addresses in `ip addr show', and the disable_ipv6 flag has been set in sysctl for all system interfaces. Probably related bugs: bug #366101, bug #159153 . I've filed this separately because of the involvement of networked sessions. (though, as I haven't been able to test a physical console yet, there's no guarantee it's network only). I'll attach a trace of the X11 traffic taken while Evolution is opening the compose window after clicking on the new button in the toolbar. System details: $ lsb_release -rd Description:Ubuntu 9.04 Release:9.04 evolution: Installed: 2.26.1-0ubuntu2 tracker: Installed: (none) evolution-data-server: Installed: 2.26.1-0ubuntu2 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
To examine the libpcap trace, open it with Wireshark, right-click on the first packet, and choose Decode as. In the window that appears select the Transport tab, then the X11 protocol in the list. Hit apply, then close. You'll now see the decoded X11 traffic. (Note that this traffic is for the WHOLE SERVER, not just Evolution). It's also informative to use the I/O graph. From the main menu, hit Statistics-I/O graphs. The first hump is moving the pointer to the new button and clicking on it, then moving the pointer out of the Xephyr window to wait for the compose window to appear. There's then a long period of steady low-rate traffic corresponding to the period when Evolution is non-responsive (from around seconds 6-18 in this particular trace), followed by a spike as it sets up and draws the window. (I've attached a PNG of the graph, but if you actually fire up Wireshark and generate it yourself you'll be able to click on parts of it to move the main window's selection to that part of the timeline.) The long flat period, when examined, appears to be a continuous loop of the following X11 operations: (C: X11 client; S: X11 server): C-S: Requests: Grabserver, QueryPointer S-C: Reply: QueryPointer C-S: Requests: QueryPointer S-C: Reply: QueryPointer C-S: UngrabServer There are over 400 such repetitions in the particular sample I'm examining right now. Most are looping one after the other, but some are intermixed with other operations before or after the long slow period. However, at this point I'm not 100% sure they're even from Evolution. ** Attachment added: io_graph.png http://launchpadlibrarian.net/27805743/io_graph.png -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
** Attachment added: tcpdump of x11 traffic for whole X session during compose window open http://launchpadlibrarian.net/27805934/trace.pcap -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
** Attachment added: Repeated grab/pointer query messages http://launchpadlibrarian.net/27805937/trace_repeated_section.txt -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
I've attached a better trace now. It contains a full Evolution session from start to finish, and excludes X11 traffic from the rest of the desktop. I used `netstat' to see which clients were connected to the Xephyr server before starting evo, fired up a tcpdump, started evo, did the testing, used 'netstat' to see what clients were connected now, and exited evo. I then diffed the two netstat results, found the new client source ports, and filtered the dump to include only those (sport: 37625, 37627). The compose window display took 17 seconds from clicking on the new button to the finish of the window drawing. The time range was 11:37:30- 11:37:47 When filtered for evo traffic only things look a fair bit different; see the I/O graph I'll attach shortly. There are several distinct phases apparent in window creation, each of which take several seconds. I'm not sure what's going on yet, and it's far from clear that network round trips / throughput are even the issue. ** Attachment added: Trace of evo startup, new btn click, compose window open, and exit. http://launchpadlibrarian.net/27805953/trace_evo_only_full_lifetime.pcap.bz2 -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
In the trace attached to the last comment, the new button click is packet 3664 at 11:37:30.98 . The window appears, as noted, around 11:37:47. The attached graph and the one in the next comment show I/O in packets/second and bytes/second during this period. ** Attachment added: I/O, bytes per second, during session (evo traffic only) http://launchpadlibrarian.net/27806272/iograph_evoonly_bytes.png -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
** Attachment added: I/O, packets per second, during session (evo traffic only) http://launchpadlibrarian.net/27806288/iograph_evoonly_packets.png -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
As you can see the packets per second graph is rather more interesting. When we look at what the traffic actually is (note: using view - time display format - time of day is useful), it's possible to see the same sequence of packets repeated during the long delay: (C: client; S: server) C - S: Req: TranslateCoordinates S - C: Rep: TranslateCoordinates C - S: Req: GrabServer, QueryPointer S - C: Rep: QueryPointer (* now, repeated seven times *): * C - S: Req: QueryPointer * S - C: Rep: QueryPointer (* end repeated segment *) C - S: Req: UngrabServer The whole segment above repeats hundreds of times during the long delay before the compose window appears. I've attached a pcap trace containing one of these repeated segments so you can examine it easily without having to dig through the whole trace. Also attached is a text version. ** Attachment added: Repeated section, evo only traffic, one repeat http://launchpadlibrarian.net/27806563/trace_repeated_section.txt -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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 386199] Re: Long delay before new/compose window appears
** Attachment added: Repeated section, evo only traffic, one repeat (pcap) http://launchpadlibrarian.net/27806581/trace_repeated_section.pcap -- Long delay before new/compose window appears https://bugs.launchpad.net/bugs/386199 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
