[Bug 1909605] [NEW] regex "look behind" not working
Public bug reported: I absolutely needed look behind functionality, and it would not work in kate and kwrite. I finally solved the problem by opening the text file in libreoffice writer -- look behind is working there. ** Affects: kate (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/1909605 Title: regex "look behind" not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1909605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1038522] Re: manual partitioning in installer crashes
I found the crash could be avoided if I reboot between creating the partitions (using sudo fdisk) and using the installer. That is, first boot off the CD and create the partitions (including write, of course), then reboot (boot again off the CD) and use the installer. Voila! No crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038522 Title: manual partitioning in installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1038522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990464] [NEW] kubuntu install crashed after manually specifying partitions (root, home, tmp swap)
Public bug reported: kubuntu install crashed after manually specifying partitions (root, home, tmp swap) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.16 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 CasperVersion: 1.315 Date: Sat Apr 28 12:12:19 2012 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash -- LiveMediaBuild: Kubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=linux LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubiquity-2.10.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990464 Title: kubuntu install crashed after manually specifying partitions (root, home, tmp swap) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/990464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990464] Re: kubuntu install crashed after manually specifying partitions (root, home, tmp swap)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990464 Title: kubuntu install crashed after manually specifying partitions (root, home, tmp swap) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/990464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990464] Re: kubuntu install crashed after manually specifying partitions (root, home, tmp swap)
By specifying the root and swap partitions only, kubuntu is now installing (I avoided the crash). Partitions for home and tmp are already on the hard drive. So under Plan B, after kubuntu is installed successfully using the simplified partitioning scheme, I will move home and tmp to the separate partitions, and modify fstab to make it permanent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990464 Title: kubuntu install crashed after manually specifying partitions (root, home, tmp swap) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/990464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254650] Re: knetworkmanager kills firefox
I checked this within the last month, and it was no longer a problem -- Firefox worked OK when interfaces is blank and knetworkmanager handles the connection. (When I checked 6 months ago or so, at that time, it was still a problem.) Maybe one of the numerous Firefox updates solved the problem. -- knetworkmanager kills firefox https://bugs.launchpad.net/bugs/254650 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 253289] Re: firefox not working (extremely slow)
Alexander, I cannot imagine how a graphics card issue would be a problem or not a problem depending on how the internet was configured. Can you explain that for me? Thanks, Rick --- On Sun, 11/2/08, Alexander Sack [EMAIL PROTECTED] wrote: From: Alexander Sack [EMAIL PROTECTED] Subject: [Bug 253289] Re: firefox not working (extremely slow) To: [EMAIL PROTECTED] Date: Sunday, November 2, 2008, 4:22 PM most likely graphics driver issue. otherwise a places performance issue for which there are enough bugs open already. ** Changed in: firefox (Ubuntu) Status: New = Invalid -- firefox not working (extremely slow) https://bugs.launchpad.net/bugs/253289 You received this bug notification because you are a direct subscriber of the bug. -- firefox not working (extremely slow) https://bugs.launchpad.net/bugs/253289 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 254650] [NEW] knetworkmanager kills firefox
Public bug reported: Binary package hint: knetworkmanager I discovered this problem connecting to a encrypted wireless network with my laptop. If I blank out the interfaces file in /etc/network, so that knetworkmanager connects to the wireless network after I log into an X session, firefox is EXTREMELY SLOW to the point of not working. I timed it once, and from launch to displaying my home page (www.yahoo.com) took 21 minutes Clicking on a menu item (like File, Edit, View, etc.) seems to lock up firefox (but really I think it takes forever for firefox to respond). I had this problem when I launched firefox after the network was up and working, and after konq was working normally. Everything worked normally EXCEPT firefox. If I specify the wireless network settings in interfaces (so that the laptop connects to the network while booting up), firefox works normally. I had been letting knetworkmanager connect to the wireless network, and I had given up on firefox. I decided to experiment with specifying the wireless network settings in interfaces without thinking about the firefox problem. After I got the internet connection working that way, I decided to try firefox, and discovered it was working again. Before I discovered that specifying the wireless network settings in interfaces solved the firefox problem, I posted queries in ubuntuforums.org and on the firefox mailing list, and did not get a single helpful responce. (On ubuntuforums.org, I got firefox tweak tips. On the firefox mailing list, I was basically told I was the only person having this problem.) ** Affects: knetworkmanager (Ubuntu) Importance: Undecided Status: New -- knetworkmanager kills firefox https://bugs.launchpad.net/bugs/254650 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 253289] [NEW] firefox not working (extremely slow)
Public bug reported: Binary package hint: mozilla-firefox Firefox used to work OK, but suddenly it is unbearably slow. Like after launching firefox just now, it took 8 minutes for the window to come up. But the window that came up was blank and unresponsive. (Before the window came up, I did get a dialog asking whether to restore the prior session or do a new session -- I chose new session.) It did not present my home page, www.yahoo.com, until 21 minutes after launch!!! I am using firefox 3.0. ( I cannot be more specific than that, because clicking on Help locks up the browser.) I am on kubuntu 8.04.1. I uninstalled firefox, deleted everything under .mozilla/firefox, then reinstalled firefox. This surely gave me the most recent version, but firefox has been unusable since before wiping it. I am using an IBM Thinkpad Pentium 4 laptop. Konqueror works OK (I am typing this message using Konqueror), and everything else works OK -- firefox is the only problem. (Of course, Konqueror is javascript challenged, which is why I would like firefox to be working.) While typing www.ubuntuforums.org into the address field, it gets stuck on the first w, pauses there for a couple of minutes, then goes to the page. I posted a query on ubuntuforums.org and got tweaking tips. I joined the foxfire mailing list and sent a query, but I did not receive a helpful response. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- firefox not working (extremely slow) https://bugs.launchpad.net/bugs/253289 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
Re: [Bug 181221] Re: The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV)
nasrullah, Install 7.04 instead of 7.10 -- worked for me. Rick --- nasrullah [EMAIL PROTECTED] wrote: I DO GET THIS BUG MOST OF THE TIME, CAN SOMEONE HELP TO GET RID OF IT. THANK YOU -- The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV) https://bugs.launchpad.net/bugs/181221 You received this bug notification because you are a direct subscriber of the bug. -- The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV) https://bugs.launchpad.net/bugs/181221 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 181221] Re: The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV)
I just installed kubuntu 7.04 on this desktop, and no more crashes. So the problem seems to be in 7.10. Unless this problem gets fixed suddenly, I will move my other desktop to 7.04 ASAP. (I am going on a trip, so ASAP will be in a couple of weeks.) -- The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV) https://bugs.launchpad.net/bugs/181221 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
Re: [Bug 172840] Re: postgresql server cannot shut down and cannot restart
Thanks, --- Martin Pitt [EMAIL PROTECTED] wrote: This is fixed in the more recent postgresql-common versions: postgresql-common (80) unstable; urgency=low [...] * PgCommon.pm: Fix cluster_data_directory() to consider the data_directory setting in postgresql.conf, which should trump the /pgdata symbolic link. [...] For your case, just either change the pgdata symbolic link, or remove it entirely, so that the data_directory setting in postgresql.conf becomes active. Non-default locations work fine, and postgresql-common has test cases to ensure that this feature does not regress. ** Changed in: postgresql (Ubuntu) Status: New = Fix Released -- postgresql server cannot shut down and cannot restart https://bugs.launchpad.net/bugs/172840 You received this bug notification because you are a direct subscriber of the bug. -- postgresql server cannot shut down and cannot restart https://bugs.launchpad.net/bugs/172840 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 181221] Re: The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV)
I just fired up my laptop, which has kubuntu 7.04. Surfing ebay is no problem using that machine. I am thinking of going back to 7.04 on one of my desktops (home and day job) to see whether the problem goes away. I think the problem will go away, as it only came up after I upgraded to 7.10 on both desktops. But it just happens frequently and is very annoying. I agree. -- The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV) https://bugs.launchpad.net/bugs/181221 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 181221] Re: The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV)
This bug is easy to reproduce -- just surf for auctions on ebay. Within one minute, you will crash. Here is one backtrace: (no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232714048 (LWP 10512)] [New Thread -1277318256 (LWP 10520)] [New Thread -1268114544 (LWP 10519)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb7be0fd7 in XtRemoveTimeOut () from /usr/lib/libXt.so.6 #7 0xb5e0edb1 in ?? () from /home/rick/.mozilla/plugins/libflashplayer.so #8 0xb5e04338 in ?? () from /home/rick/.mozilla/plugins/libflashplayer.so #9 0xb5dfd181 in ?? () from /home/rick/.mozilla/plugins/libflashplayer.so #10 0xb5e01937 in ?? () from /home/rick/.mozilla/plugins/libflashplayer.so #11 0x080c0468 in ?? () #12 0xbfab4188 in ?? () #13 0xbfab4158 in ?? () #14 0xb7b7fd81 in operator delete () from /usr/lib/libstdc++.so.6 #15 0x0805b62f in NSPluginInstance::destroy () #16 0x0805d78d in NSPluginInstance::~NSPluginInstance () #17 0xb7109890 in QGList::remove () from /usr/lib/libqt-mt.so.3 #18 0x0805652f in NSPluginClass::timer () #19 0x080565c1 in NSPluginInstance::shutdown () #20 0x080593b9 in NSPluginInstanceIface::process () #21 0xb73000d7 in DCOPClient::receive () from /usr/lib/libDCOP.so.4 #22 0xb7301434 in ?? () from /usr/lib/libDCOP.so.4 #23 0x080850f0 in ?? () #24 0xbfab44e4 in ?? () #25 0xbfab44dc in ?? () #26 0xbfab44d4 in ?? () #27 0xbfab44cc in ?? () #28 0xbfab44c4 in ?? () #29 0xbfab44bc in ?? () #30 0xbfab447c in ?? () #31 0xbfab44ec in ?? () #32 0xbfab44e4 in ?? () #33 0xbfab44dc in ?? () #34 0xbfab44d4 in ?? () #35 0xbfab44cc in ?? () #36 0xbfab44c4 in ?? () #37 0xbfab44bc in ?? () #38 0x0010 in ?? () #39 0xbfab4494 in ?? () #40 0x08062da8 in vtable for QMemArraychar () #41 0x007e in ?? () #42 0x00108e10 in ?? () #43 0x01ab4401 in ?? () #44 0x004f in ?? () #45 0x0002 in ?? () #46 0x080b08c0 in ?? () #47 0x080a6400 in ?? () #48 0x080850f0 in ?? () #49 0xb7a7913c in ?? () from /lib/tls/i686/cmov/libc.so.6 #50 0x0001 in ?? () #51 0x0047 in ?? () #52 0xb72d58d0 in ?? () from /usr/lib/libqt-mt.so.3 #53 0xb7a941d0 in ?? () from /lib/tls/i686/cmov/libc.so.6 #54 0xb7a75fd5 in ?? () from /lib/tls/i686/cmov/libc.so.6 #55 0x080c15e8 in ?? () #56 0xbfab44b8 in ?? () #57 0x004c in ?? () #58 0x080e55f8 in ?? () #59 0xbfab44b8 in ?? () #60 0xb7a10c84 in read () from /lib/tls/i686/cmov/libc.so.6 #61 0xb7fb7e38 in read () from /usr/lib/libartsdsp.so.0 #62 0xb7301f55 in ?? () from /usr/lib/libDCOP.so.4 #63 0xbfab4598 in ?? () #64 0x0001 in ?? () #65 0x080e55f8 in ?? () #66 0x080ad158 in ?? () #67 0xbfab4568 in ?? () #68 0xb7a10c84 in read () from /lib/tls/i686/cmov/libc.so.6 #69 0xb7fb7e38 in read () from /usr/lib/libartsdsp.so.0 #70 0xb7312280 in KDE_IceProcessMessages () from /usr/lib/libDCOP.so.4 #71 0xb72f85c3 in DCOPClient::processSocketData () from /usr/lib/libDCOP.so.4 #72 0xb7301b59 in DCOPClient::qt_invoke () from /usr/lib/libDCOP.so.4 #73 0xb6e0d893 in QObject::activate_signal () from
[Bug 16502] Re: nspluginviewer crashes badly on flashplayer
This is a fresh install of kubuntu 7.10, and I'm getting lots of these crashes. They do not crash the whole system, but I get lots of crash handler windows that I have to close. -- nspluginviewer crashes badly on flashplayer https://bugs.launchpad.net/bugs/16502 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 177800] k3b No CD/DVD writer found
Public bug reported: Binary package hint: k3b On exactly this same hardware, running kubuntu 6.10, k3b burned CD's fine. I am now running gutsy, and k3b cannot find the CD drive. Bug #114471, No CD/DVD writer found (No detect CD/DVD writer), is closed and I do not know how to reopen it. kinfoCenter can find the CD drive and says it can write CD-R, CD-R/W, DVD-R, DVD-RAM, MRW and RAM. (kinfoCenter does not seem to support text copy/paste.) Do you need any additional info? Luckily, I still have the drive on which kubuntu 6.10 is installed, so I will put that back in the box to burn this CD. Thanks, ** Affects: k3b (Ubuntu) Importance: Undecided Status: New -- k3b No CD/DVD writer found https://bugs.launchpad.net/bugs/177800 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 176518] Administrator Mode does not work
Public bug reported: I just installed Gutsy on two different systems, and I cannot get into Administrator Mode in System Settings on either install. I will continue using one (at my residence), but at my workshop, I am back to 6.10. ** Affects: kde-systemsettings (Ubuntu) Importance: Undecided Status: New -- Administrator Mode does not work https://bugs.launchpad.net/bugs/176518 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
Re: [Bug 172840] postgresql server cannot shut down and cannot restart
Actually, I discovered that the problem (postgresql server cannot shut down and cannot restart) is only a problem with a non-default data location. The postgresql.conf file has a data_directory value, and if you set that to a non-default location, some but not all of the data goes to that location. There is also a pgdata soft link in the same directory as the conf file, and some of the data follows that soft link, no matter the value of data_directory in postgresql.conf. I would call the feature of using a non-default data location as broken, unless there is documentation somewhere that I have overlooked. I have given up on trying to use /srv/postgresql for the data directory, and instead I am going with the default, /var/lib/postgresql, as use of a non-default location is not currently supported as far as I know. Thanks, --- Rick Graves [EMAIL PROTECTED] wrote: Public bug reported: Binary package hint: postgresql If you shut down the computer, you see a message error PID file is invalid, please manually kill the stale server process (maybe not an exact quote), along with Fail in red. You get exactly the same message if you try shutting down the database server or restarting the database server. I have this problem both in ubuntu 6.06 LTS and 7.10. ** Affects: postgresql (Ubuntu) Importance: Undecided Status: New -- postgresql server cannot shut down and cannot restart https://bugs.launchpad.net/bugs/172840 You received this bug notification because you are a direct subscriber of the bug. -- postgresql server cannot shut down and cannot restart https://bugs.launchpad.net/bugs/172840 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 172840] postgresql server cannot shut down and cannot restart
Public bug reported: Binary package hint: postgresql If you shut down the computer, you see a message error PID file is invalid, please manually kill the stale server process (maybe not an exact quote), along with Fail in red. You get exactly the same message if you try shutting down the database server or restarting the database server. I have this problem both in ubuntu 6.06 LTS and 7.10. ** Affects: postgresql (Ubuntu) Importance: Undecided Status: New -- postgresql server cannot shut down and cannot restart https://bugs.launchpad.net/bugs/172840 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
Re: [Bug 138793] Re: no warning about decoy conf files
Martin, Please see /usr/share/postgresql-common/README.Debian.gz for an intro. I find a file named README.Debian.gz here: /usr/share/doc/postgresql-8.2/ I had to unzip it to a tmp directory to read it. It mentions pg_createcluster, but in no way makes clear that pg_createcluster should be used to set up a new database, and gives no step-by-step instructions. Pertaining to the instructions that I found and followed, anyone can find those by googling install postgresql without the quotes and hit I'm feeling lucky (at least the I'm feeling lucky part is working for me right now). That would be these: http://www.postgresql.org/docs/8.0/interactive/installation.html From there, one can also easily find these by filling in the version number of your choice: http://www.postgresql.org/docs/8.1/interactive/installation.html http://www.postgresql.org/docs/8.2/interactive/install-short.html So it seems the installation instructions one can easily find don't work, and the installation instructions one should follow are unclear and lost somewhere in the directory structure anyway. Should I file another bug on inadequate installation instructions? It seems adequate instructions are lacking, and if that is the case, I would be willing to pitch in and write better ones if arrangements could be made to get the instructions in front of people actually when they install postgresql on ubuntu and/or Debian. Thanks, Rick --- Martin Pitt [EMAIL PROTECTED] wrote: Rick Graves [2007-10-31 13:27 -]: What installation instructions should I be following? I do not recall ever hearing of pg_createcluster. Please see /usr/share/postgresql-common/README.Debian.gz for an intro. -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 You received this bug notification because you are a direct subscriber of the bug. -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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
Re: [Bug 138793] Re: no warning about decoy conf files
Martin, I would like to run my history by you. I was using postgresql-7.4 before I switched to ubuntu (I am a refugee from RedHat). After I upgraded my workstation to the latest and greatest from ubuntu and installed the postgresql client, I got messages that the version 8 client does not work right with the version 7 server. So when the data drive on my postgresql-7.4 server died, it seemed like an ideal time to set up a new postgresql-8 server and migrate the data over (yes, I was fully backed up, and you have to migrate the data anyway when you upgrade postgresql). As of Wednesday, my new postgresql-8 server is now working. (My almost three week gap with no working database server was mostly the fault of factors other than less than ideal installation instructions.) So it seems the installation instructions one can easily find don't work Well, they do work. I disagree. If you follow the instructions on the postgresql.org site, the server cannot start. I had to figure out from error messages to find server.crt, server.key and root.crt, and that I had to copy them to the data directory, etc. For my money, the instructions on postgresql.org site do not work on an install from the ubuntu 6.06 server CD. You are assuming that one must set up a new cluster, but (according to the pg_createcluster man page), The default cluster that is created on installation of a server package is main. I want to use main -- I do not want to set up a different cluster (such as testing and the other examples on the man page do not register for me). I am not aware of any problem with using main (other than there are no working installation instructions). My new postgresql-8 server is using main and it seems to be working OK. So if there is no problem with using the main cluster, there should be installation instructions for doing that. That would be the simple server installation. Setting up additional clusters is a more advanced installation, and those instructions could be separate from the simple install. So far I deliberately don't put the initdb programs into the $PATH, but pg_* tools are in the path. Would it have helped you if there was an initdb in the path which told you about the distro tools? The postgresql.org instructions put the full path on initdb, so I do not think that putting pg_* tools in the path will be a clue to most administrators. (Because the postgresql.org instructions put the full path on initdb, it never occurred to me to examine what was in the path.) Perhaps the objective should be make the postgresql.org instructions work using the main cluster without having to figure out how to get the server started. I think the vast majority of administrators will know to ignore the part about compiling the source, but I think the rest of the instructions here should work: http://www.postgresql.org/docs/8.0/interactive/installation.html What do you think? Thanks, Rick --- Martin Pitt [EMAIL PROTECTED] wrote: Hi Rick, Rick Graves [2007-11-01 21:28 -]: So it seems the installation instructions one can easily find don't work Well, they do work. If you stay on upstream's path, then things will work, but then of course you cannot expect the distro integration bits to work (like automatic startup in the init scripts, upgrading, logging into the proper places, default configuration for log rotation, etc.). Should I file another bug on inadequate installation instructions? You can do, or we just retitle this one (which is preferable, I think). It seems adequate instructions are lacking, and if that is the case, I would be willing to pitch in and write better ones if arrangements could be made to get the instructions in front of people actually when they install postgresql on ubuntu and/or Debian. I'd be absolutely happy to improve this. The question is, where to do it? So far I deliberately don't put the initdb programs into the $PATH, but pg_* tools are in the path. Would it have helped you if there was an initdb in the path which told you about the distro tools? We could also patch the upstream initdb itself to point out pg_createcluster maybe. Pitti -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 You received this bug notification because you are a direct subscriber of the bug. -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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
Re: [Bug 138793] Re: no warning about decoy conf files
Martin, Having just run this again, I can report that the conf files are deposited in the data directory when you run initdb. Also, for the postgresql server to start, I must copy server.crt, server.key and root.crt from /var/lib/postgresql/8.1/main to the data directory, and change the owner of those files to postgres. Otherwise, no go. dpkg -l 'postgres*' | grep ^ii I get postgresql-8.1, postgresql-client-8.1, postgresql-common, and postgresql-client-common. The first two are version 8.1.9-0ubuntu0.6.06. lsb_release -d Ubuntu 6.06.1 LTS It does not happen on Ubuntu Feisty/Gutsy and Debian Etch/unstable. For a database sever, I think most real database administrators would choose a long term support version over unstable! Rick --- Martin Pitt [EMAIL PROTECTED] wrote: Hi Rick, Rick Graves [2007-10-24 3:34 -]: Part of my problem was the conf files were not just in /etc/postgresql, but in /etc/postgresql/8.1/main This is because we support multiple versions in parallel, and also multiple clusters (instances) of one version in parallel. Please see /usr/share/doc/postgresql-common/README.gz. deep, I found the conf files in the data directory instead). This would be one major part of the bug. It does not happen on Ubuntu Feisty/Gutsy and Debian Etch/unstable. Please give me the output of dpkg -l 'postgres*' | grep ^ii lsb_release -d Thanks, Martin -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 You received this bug notification because you are a direct subscriber of the bug. -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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
Re: [Bug 138793] Re: no warning about decoy conf files
Martin, The prefered way is to use pg_createcluster What installation instructions should I be following? I do not recall ever hearing of pg_createcluster. Thanks, Rick --- Martin Pitt [EMAIL PROTECTED] wrote: Hi, Rick Graves [2007-10-31 9:11 -]: Having just run this again, I can report that the conf files are deposited in the data directory when you run initdb. Ah, of course. If you run initdb manually, then you cannot expect the postgresql-common integration scripts to work magically. The prefered way is to use pg_createcluster, which will do all this shuffling for you and register the cluster in the postgresql-common structure, init scripts, enable the possibility to upgrade it painlessly with pg_upgradecluster, etc. But then I wonder how you managed to get the files in /etc/? It seems that you once had the default 8.1/main cluster, deleted the data directory in /var/lib, but not the configuration directory in /etc/, and then used initdb to re-create the data dir in /var/? Also, for the postgresql server to start, I must copy server.crt, server.key and root.crt from /var/lib/postgresql/8.1/main to the data directory, and change the owner of those files to postgres. Otherwise, no go. pg_createcluster does all this. For a database sever, I think most real database administrators would choose a long term support version over unstable! Absolutely! -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 You received this bug notification because you are a direct subscriber of the bug. -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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
Re: [Bug 138793] Re: no warning about decoy conf files
Martin, Please give me the output of dpkg -l 'postgres*' | grep ^ii lsb_release -d I am traveling now (out of the office). I will get back next week, and I can send the info then. I did the installs from the 6.06 LTS server CD. What installation instructions should I follow when I set up a postgresql server using the 6.06 LTS server CD? Rick --- Martin Pitt [EMAIL PROTECTED] wrote: Hi Rick, Rick Graves [2007-10-24 3:34 -]: Part of my problem was the conf files were not just in /etc/postgresql, but in /etc/postgresql/8.1/main This is because we support multiple versions in parallel, and also multiple clusters (instances) of one version in parallel. Please see /usr/share/doc/postgresql-common/README.gz. deep, I found the conf files in the data directory instead). This would be one major part of the bug. It does not happen on Ubuntu Feisty/Gutsy and Debian Etch/unstable. Please give me the output of dpkg -l 'postgres*' | grep ^ii lsb_release -d Thanks, Martin -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 You received this bug notification because you are a direct subscriber of the bug. -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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
Re: [Bug 138793] Re: no warning about decoy conf files
Martin, I am happy to add a small README.configuration to the data directory which points to the configuration files in /etc/. Part of my problem was the conf files were not just in /etc/postgresql, but in /etc/postgresql/8.1/main (so deep, I found the conf files in the data directory instead). What installation instructions should I be following? Thanks, Rick --- Martin Pitt [EMAIL PROTECTED] wrote: What do you mean by 'decoy files'? There are no fake postgresql.conf etc. files in the data directory. I am happy to add a small README.configuration to the data directory which points to the configuration files in /etc/. Do you mean that? ** Changed in: postgresql-common (Ubuntu) Sourcepackagename: postgresql-8.1 = postgresql-common Importance: Undecided = Low Status: New = Incomplete -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 You received this bug notification because you are a direct subscriber of the bug. -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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 138793] Re: no warning about decoy conf files
Martin, I installed postgresql 8.1, and there were duplicate copies of all the conf files (postgresql.conf, etc.) in the data directory. They are decoys in the sense that I found those first, but editing them had no effect. I am happy to add a small README.configuration to the data directory which points to the configuration files in /etc/. Do you mean that? That would solve the problem that I encountered. Thanks, Rick -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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 138793] no warning about decoy conf files
Public bug reported: Binary package hint: postgresql-8.1 The ubuntu install puts copies of the conf files in the data directory, and buries the real conf files in /etc/postgresql/8.1/main. As an administrator, I found the conf files in the data directory, but I did not find the real conf files in /etc/postgresql/8.1/main -- too deep. Editing the conf files in the data directory does not work; see: http://ubuntuforums.org/showthread.php?p=3344958#post3344958 In an ideal world, if you are going to plant decoy copies of the configuration files in a location an administrator is likely to find, with the decoy copies should be a README that tells were the real conf files are located. Thanks, ** Affects: postgresql-8.1 (Ubuntu) Importance: Undecided Status: New -- no warning about decoy conf files https://bugs.launchpad.net/bugs/138793 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
