[Bug 588624] Re: upstart fails to boot without initrd
@Clint thanks for taking over, I was pretty shocked to learn that Rolf is trying to triage this bug but does not even know what an initrd is unfortunately this will be difficult to debug because most of the progress information I was used to see scrolling over my screen for many years is gone. It seems that Ubuntu is now depending on the initrd to do the fsck of the root-filesystem. regarding your questions: 1.) there are many howtos on how to build a kernel and configure grub to boot it. basically you need to have the ide/sata and filesystem drivers compiled into the kernel to boot without initrd. 2.) I would expect it to show the same behaviour I was used to see since ~1995: run fsck on the filesystem and show the progress 3.) see my initial post 4.) there are many reasons one would not want to use a distribution supplied kernel and probably run without an initrd. the most important reason for me is that I can boot with init=/bin/bash and fix most things upgrades have broken so far (xorg, pam,...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588624 Title: upstart fails to boot without initrd -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 370607] Re: X applications won't run under sudo
same problem here when using sudo -H bash and trying to start a graphical application; ~root/.Xauthority does not get updated anymore. problem seems to be that pam_xauth does no longer get the correct id for the requesting user pam_xauth(sudo:session): requesting user 0/0, target user 0/0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/370607 Title: X applications won't run under sudo -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588624] [NEW] upstart fails to boot without initrd
Public bug reported: Binary package hint: upstart upstart is no longer capable of booting without initrd. it appears to work at first, but as soon as the root file system reaches its maximum mount count, upstart stops at "waiting for /dev/sda1". to make things worse, after rebooting with init=/bin/bash, it is not easily possible to manually fsck the root device because /dev/sda1 is missing (thanks to udev). for those who are not accustomed to mknod and how to fix this problem: mknod /dev/sda b 8 0 mknod /dev/sda1 b 8 1 mknod /dev/sda2 b 8 2 ... with every day I use lucid I am becoming more and more motivated to replace upstart and udev with a very simple but reliable bash script and static device nodes. there were very intelligent and considerate people who invented sysvinit and deliberately decided not to exploit parallelism in this process for reliability is much more important than performance. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- upstart fails to boot without initrd https://bugs.launchpad.net/bugs/588624 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 584936] Re: gpsd cannot open /dev/ttyUSB0
** Description changed: Binary package hint: gpsd from the man page: - > gpsd must start up as root in order to open the NTPD shared-memory segment, open its logfile, and create its local control - > socket. Before doing any processing of GPS data, it tries to drop root privileges by setting its UID to "nobody" (or another userid - > as set by configure) and its group ID to the group of the initial GPS passed on the command line — or, if that device doesn't + > gpsd must start up as root in order to open the NTPD shared-memory segment, open its logfile, and create its local control + > socket. Before doing any processing of GPS data, it tries to drop root privileges by setting its UID to "nobody" (or another userid + > as set by configure) and its group ID to the group of the initial GPS passed on the command line — or, if that device doesn't > exist, to the group of /dev/ttyS0. - > The assumption behind gpsd's particular behavior is that all the tty devices to which a GPS might be connected are owned by - > the same non-root group and allow group read/write, though the group may vary because of distribution-specific or local - > administrative practice. If this assumption is false, gpsd may not be able to open GPS devices in order to read them (such + > The assumption behind gpsd's particular behavior is that all the tty devices to which a GPS might be connected are owned by + > the same non-root group and allow group read/write, though the group may vary because of distribution-specific or local + > administrative practice. If this assumption is false, gpsd may not be able to open GPS devices in order to read them (such > failures will be logged)." since I have no /dev/ttyS0 and gpsd is configured for start up without - any devices / adding devices later via hotplug / control socket ist - switches it's user-id to 0 and can therefore not open /dev/ttyUSB0 which - is later created with group id dialout by udev. + any devices / adding devices later via hotplug / control socket it + switches it's user-/group-id to nobody(65535) / root(0) and can + therefore not open /dev/ttyUSB0 which is later created with group id + dialout by udev. -- gpsd cannot open /dev/ttyUSB0 https://bugs.launchpad.net/bugs/584936 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 583037] Re: arrow-left maps to ISO_Level3_Shift
** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/49155623/Xorg.0.log -- arrow-left maps to ISO_Level3_Shift https://bugs.launchpad.net/bugs/583037 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 583037] Re: arrow-left maps to ISO_Level3_Shift
** Attachment added: "lspci-vvn.txt" http://launchpadlibrarian.net/49155573/lspci-vvn.txt -- arrow-left maps to ISO_Level3_Shift https://bugs.launchpad.net/bugs/583037 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 584936] [NEW] gpsd cannot open /dev/ttyUSB0
Public bug reported: Binary package hint: gpsd from the man page: > gpsd must start up as root in order to open the NTPD shared-memory segment, > open its logfile, and create its local control > socket. Before doing any processing of GPS data, it tries to drop root > privileges by setting its UID to "nobody" (or another userid > as set by configure) and its group ID to the group of the initial GPS passed > on the command line — or, if that device doesn't > exist, to the group of /dev/ttyS0. > The assumption behind gpsd's particular behavior is that all the tty devices > to which a GPS might be connected are owned by > the same non-root group and allow group read/write, though the group may vary > because of distribution-specific or local > administrative practice. If this assumption is false, gpsd may not be able to > open GPS devices in order to read them (such > failures will be logged)." since I have no /dev/ttyS0 and gpsd is configured for start up without any devices / adding devices later via hotplug / control socket ist switches it's user-id to 0 and can therefore not open /dev/ttyUSB0 which is later created with group id dialout by udev. ** Affects: gpsd (Ubuntu) Importance: Undecided Status: New -- gpsd cannot open /dev/ttyUSB0 https://bugs.launchpad.net/bugs/584936 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 583236] [NEW] window decorations: inconsistent and bad usability
Public bug reported: Binary package hint: light-themes after upgrading to ubuntu lucid, the minimixe / maximize / close buttons moved from the right to the left of the title bar. this may be ok for new installations, but messing with the user's theme is not acceptable during an upgrade. especially since system -> preferences -> appearance does not allow the user to change the button layout without asking to keep the "everything left" layout. it is well known that iphone users must be suffering from the stockholm syndrome in order to advocate that thing: http://www.zdnet.com/blog/hardware/are-iphone-users-suffering-from-stockholm-syndrome/6420 now it appears that ubuntu's design team and has been working with apple computers and is suffering from the same condition. but there is one important difference between apple and linux users: apple users will actually believe and thank steve jobs for taking them on a leash and telling them what is good for them. linux users do have their own opinion. ** Affects: light-themes (Ubuntu) Importance: Undecided Status: New -- window decorations: inconsistent and bad usability https://bugs.launchpad.net/bugs/583236 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 583037] [NEW] arrow-left maps to ISO_Level3_Shift
Public bug reported: Binary package hint: xorg after upgrading to lucid I had to notice that the kbd driver has been removed so I had to change my /etc/X11/xorg.conf to use the evdev driver for the keyboard: Section "InputDevice" Identifier "Keyboard_evdev" Driver "evdev" Option "Device" "/dev/input/by-path/platform-i8042-serio-0-event-kbd" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" Option "CoreKeyboard" EndSection #Section "InputDevice" #Identifier "Keyboard_kbd" #Driver "kbd" #Option "XkbLayout" "de" #Option "XkbVariant" "nodeadkeys" #Option "CoreKeyboard" #EndSection after that my left arrow key stopped working. using xev and xmodmap I found that the key was generating keycode 113 events which were mapped to ISO_Level3_Shift. workaround: xmodmap -e 'keycode 113 = Left' it appears that I am not the only one affected by this: http://benfrantzdale.livejournal.com/262354.html mapped (xmodmap -pke) as ISO_Level3_Shift instead of "Left". as 113 is the standard keycode for "Left" I wonder who messed up with the keyboard mappings. I use the german nodeadkeys layout. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- arrow-left maps to ISO_Level3_Shift https://bugs.launchpad.net/bugs/583037 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 582799] [NEW] mount -o remount,norelatime is broken
Public bug reported: Binary package hint: util-linux from /proc/mounts: /dev/root / ext3 rw,relatime,errors=continue,data=ordered 0 0 > mount -o remount,strictatime / /dev/root / ext3 rw,errors=continue,data=ordered 0 0 > mount -o remount,norelatime / /dev/root / ext3 rw,relatime,errors=continue,data=ordered 0 0 mount -o norelatime turns on relatime?!? who failed to understand the meaning of "no" here? ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- mount -o remount,norelatime is broken https://bugs.launchpad.net/bugs/582799 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 571258] Re: plymouth main process (341) killed by SEGV signal
same problem here; I also use a custom kernel; after rebooting with lucid the plymouth SEGV messages were the last thing I could see. had to reboot with init=/bin/bash and notice that upstart must have failed to fsck and remount,rw my rootfs -- plymouth main process (341) killed by SEGV signal https://bugs.launchpad.net/bugs/571258 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 582767] [NEW] wrong system time after upgrade
Public bug reported: Binary package hint: util-linux after upgrading karmic to lucid and rebooting my system time was set 2h in the past. cause: upgrading util-linux silently installed hwclock and defaults to UTC=no in /etc/rcS question: how do I stop hwclock messing with time now? aptitude purge util-linux is not possible. should I rm /etc/init/hwclock* or will they be reinstalled when upgrading util-linux for the next time? ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- wrong system time after upgrade https://bugs.launchpad.net/bugs/582767 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 90434] Re: please enable dontzap by default
could you please make "dontzap" a accessability option for those who are unable to control their fingers? today I ended up having to pull the plug because I could not find another way to get out of xorg. my /home partition was not mounted so gnome would not come up and would also not load my "dontzap=no" config dontzap belongs to the xorg config. keep it there. users use linux because they do not want to find new ways to do common tasks with every release. ubuntu started and was successful as a better maintained debian. now it seems the focus has shifted to "change and break everything that has reliably worked for 30 years" -- please enable dontzap by default https://bugs.launchpad.net/bugs/90434 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 582684] [NEW] xorg: no keyboard after upgrade
Public bug reported: Binary package hint: xorg after upgrading to lucid I could not type my password on the login screen. also I could not do anything to get out of xorg (ctrl+alt+f1, ctrl+backspace did not work) this was caused by the kbd driver having beeing removed from lucid. question: what was the objective in removing the kbd driver and breaking user's old installations? ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- xorg: no keyboard after upgrade https://bugs.launchpad.net/bugs/582684 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 516684] Re: After upgrade from Karmic boot fails, mountall and udevd fail
dear scott, can you please explain to my xen hosting provider why they need to upgrade their stable dom0 in order to support ubuntu with new domu kernels? their e-mail is ad...@funkfeuer.at I have just replaced upstart, mountall, ureadahead, plymouth,... by a very simple script that does what they fail to do: initialize my server and start the required services. very basic functionality which has been reliably provided by sysv init for more than 20 years... what do you mean by plumbing layer? sysv init has reliably worked for >20 years with hundreds of different kernels without needing any layers. upstart introduces a plumbing layer and everything breaks -- After upgrade from Karmic boot fails, mountall and udevd fail https://bugs.launchpad.net/bugs/516684 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 462624] Re: trouble with stored passwords
same problem here; even though because I am using screen the error message does not appear until after I abort svn by pressing ctrl-c. solved problem by doing "chmod 000 /usr/lib/gnome-keyring/gnome-keyring- ask". unfortunately it seems to be the current spirit of ubuntu to break things that used to work for many years just for the sake of implementing a feature (gnome-keyring) that brings no advantages to the user. the list of files having mode 000 on my system is growing: hwclock, nautilus, console-kit-daemon, pulseaudio -- trouble with stored passwords https://bugs.launchpad.net/bugs/462624 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 473139] Re: gnome-keyring demands unspecified password, breaking svn commits
same problem here echo - "[auth]\npassword-stores = \n" >~/.svn/config did not work solved problem by rm ~/.gnome2/keyring/* after breaking ssh-agent, gnome-keyring just earned itself a second scoring point on my "useless daemons creating problems" list. is it really necessary that so many packages depend on gnome-keyring? I would love to be able to purge it from my systems. -- gnome-keyring demands unspecified password, breaking svn commits https://bugs.launchpad.net/bugs/473139 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 557177] Re: init: support mandatory arguments, or prevent starting of tasks without any arguments
dear scott, as you failed to see the problem in having a script in upstart that recursively wipes all file systems when called according to the man page I would rather not have upstart on my systems. please make upstart an optional feature and let people stick with the robust sysv init where a script wiping your server definitely *is* a bug. upstart has no advantages for me but comes with lots of problems (for me at least bugs #62751, #416056, and #447747). -- init: support mandatory arguments, or prevent starting of tasks without any arguments https://bugs.launchpad.net/bugs/557177 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 391129] Re: [9.10] dontzap false does not work anymore
how to enable zap / disable dontzap for the gdm login screen? -- [9.10] dontzap false does not work anymore https://bugs.launchpad.net/bugs/391129 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 447747] Re: karmic - mountall fails to mount filesystem on boot
I recently upgraded my xen instance from jaunty to karmic and - surprise - it does not come up any more. How can I fix this problem? As the dom0 is not under my control, upgrading the kernel is not an option. Downgrading mountall? Replacing mountall by a shell script to only mount /proc? Why is karmic so dependent on kernel >= 2.6.26? What is the advantage in using /proc/$pid/mountinfo? -- karmic - mountall fails to mount filesystem on boot https://bugs.launchpad.net/bugs/447747 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 387086] Re: udevadm settle hangs
mv /sbin/udevadm /sbin/udevadm.real cat >/sbin/udevadm
[Bug 387086] Re: udevadm settle hangs
I now wrote a wrapper to call "udevadm settle --timeout 30" instead of udevadm. It still hangs in rt_sigsuspend(~[TRAP KILL SEGV STOP RTMIN RT_1]) -- udevadm settle hangs https://bugs.launchpad.net/bugs/387086 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 387086] [NEW] udevadm settle hangs
Public bug reported: Binary package hint: udev I am trying to automatically mount a LUKS volume when I log in: /etc/security/pam_mount.conf: /etc/fstab: /dev/sda3 /media/sda3 crypt defaults,noauto,nodev,nosuid 0 0 Instead of mounting the volume this causes the login process to get stuck: mount -p0 -o defaults,noauto,nodev,nosuid -t auto /dev/sda3 /media/sda3 /sbin/mount.crypto_LUKS /dev/sda3 /media/sda3 -o rw,nosuid,nodev cryptsetup luksOpen /dev/sda3 _dev_sda3 sh -c /sbin/udevadm settle /sbin/udevadm settle I am currently using chmod 644 /sbin/udevadm as a workaround. ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- udevadm settle hangs https://bugs.launchpad.net/bugs/387086 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 146938] gsasl-0.2.12 is outdated
Public bug reported: Binary package hint: gsasl gsasl-0.2.12 is more than one and a half years old. Jabberd2 versions > 2.1.9 (current is 2.1.16) require at least gsasl-0.2.14 to compile. Current version of gsasl is 0.2.21. Current upstream package version is 0.2.21. ** Affects: gsasl (Ubuntu) Importance: Undecided Status: New -- gsasl-0.2.12 is outdated https://bugs.launchpad.net/bugs/146938 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144954] sshfp records do not work
Public bug reported: Binary package hint: pdns According to the documentation pdns 2.9.21 is supposed to support sshfp records. However they do currently cause the following error when doing an axfr: > Exception: invalid unknown record > TCP Connection Thread died because of STL error: invalid unknown record ** Affects: pdns (Ubuntu) Importance: Undecided Status: New -- sshfp records do not work https://bugs.launchpad.net/bugs/144954 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144944] SPF records: broken syntax
Public bug reported: Binary package hint: pdns SPF used to use TXT records. Recently SPF has been assigned it's own record type which is supposed to be supported in pdns 2.9.21. Unfortunately there appears to be a bug in the parser so that TXT records cannot be easily duplicated as required by the RFC: name='hostmaster.org' type='TXT' content='v=spf1 a -all' should be duplicated as name='hostmaster.org' type='SPF' content='v=spf1 a -all' however pdns currently requires the following format (note the "): name='hostmaster.org' type='SPF' content='"v=spf1 a -all"' ** Affects: pdns (Ubuntu) Importance: Undecided Status: New -- SPF records: broken syntax https://bugs.launchpad.net/bugs/144944 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144933] REGRESSION: axfr fails when SOA does not contain serial
Public bug reported: Binary package hint: pdns SOA records containing just the authorative nameserver used to work in pdns 2.9.20. Now with 2.9.21-2 these cause axfr requests to fail: record: name="hostmaster.org" type="SOA" content="a.ns.hostmaster.org" test: host -t axfr hostmaster.org $ip error: TCP nameserver had error, cycling backend: Reading data: Connection reset by peer workaround: name="hostmaster.org" type="SOA" content="a.ns.hostmaster.org hostmaster.hostmaster.org 1190704103" ** Affects: pdns (Ubuntu) Importance: Undecided Status: New -- REGRESSION: axfr fails when SOA does not contain serial https://bugs.launchpad.net/bugs/144933 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144484] ekiga aborts due to missing symbol in libopal-2.2.0
Public bug reported: Binary package hint: ekiga ekiga: symbol lookup error: /usr/lib/libopal.so.2.2: undefined symbol: _ZN11PSafeObjectC2Ev ** Affects: ekiga (Ubuntu) Importance: Undecided Status: New -- ekiga aborts due to missing symbol in libopal-2.2.0 https://bugs.launchpad.net/bugs/144484 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139985] Call to undefined method Repository::getDisplayName() in /usr/share/websvn/filedetails.php on line 130
Public bug reported: Binary package hint: websvn Upgraded Feisty to Gutsy; websvn now shows the following error when trying to view details about a file: Fatal error: Call to undefined method Repository::getDisplayName() in /usr/share/websvn/filedetails.php on line 130 ** Affects: websvn (Ubuntu) Importance: Undecided Status: New -- Call to undefined method Repository::getDisplayName() in /usr/share/websvn/filedetails.php on line 130 https://bugs.launchpad.net/bugs/139985 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60515] Re: Get 500 Internal server error while trying to start asp test script.
Same problem. Here is my patch:
--- /usr/share/perl5/Apache/ASP.pm.ubuntu 2007-09-04 12:47:15.0
+0200
+++ /usr/share/perl5/Apache/ASP.pm 2007-09-04 12:59:21.0 +0200
@@ -62,12 +62,9 @@
eval "use $module ();";
}
-if($ENV{MOD_PERL}) {
- $ModPerl2 = ($mod_perl::VERSION >= 1.99);
- if($ModPerl2) {
+if($ENV{'MOD_PERL'} && ($mod_perl::VERSION ||
$ENV{'MOD_PERL_API_VERSION'}) >= 1.99) {
eval "use Apache::ASP::ApacheCommon ();";
die($@) if $@;
- }
}
}
Apache::ASP does not appear to be maintained anymore, so I would prefer
to use Apache2::ASP instead.
--
Get 500 Internal server error while trying to start asp test script.
https://bugs.launchpad.net/bugs/60515
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134056] Re: [Gutsy] Distributed.net client (dnetc) crashes with exception
Same problem here. Purged libnss-mdns and everything suddenly started working. What is libnss-mdns good for anyway? -- [Gutsy] Distributed.net client (dnetc) crashes with exception https://bugs.launchpad.net/bugs/134056 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
