[Desktop-packages] [Bug 1498274] Re: init.d script doesn't respect `version` argument
Wow, works like a treat!!
I'd definitely expect there to be only one way to do it, and for
`service postgresql start 9.3` to have the effect that `service
postgresql pgstart 9.3` has in your patch.
With much thanks,
Eoghan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1498274
Title:
init.d script doesn't respect `version` argument
Status in postgresql-common package in Ubuntu:
Confirmed
Bug description:
Release: Ubuntu 15.04
It seems that the current version of the /etc/init.d/postgresql script
doesn't respect the `version` flag. Help text states:
Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
reload|status} [version ..]
But with 2 installations and called as follows:
/etc/init.d/postgresql start 9.4
or
service postgresql start 9.4
Both 9.4 and 9.3 are started, I expected just 9.4 to start.
Package info:
# apt-cache policy postgresql-common
postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
169.pgdg70+1 0
500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64
Packages
*** 169.pgdg14.04+1 0
100 /var/lib/dpkg/status
166bzr2 0
500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64
Packages
500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1498274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1498274] Re: init.d script doesn't respect `version` argument
Hi jeroen,
Thanks for your reply.
Running `ps -elf |grep postg` shows both:
0 S postgres 30213 1 1 80 0 - 331047 poll_s 14:49 ? 00:00:00
/usr/lib/postgresql/9.3/bin/postgres -D /var/lib/postgresql/9.3/main -c
config_file=/etc/postgresql/9.3/main/postgresql.conf
0 S postgres 30214 1 4 80 0 - 4088839 poll_s 14:49 ? 00:00:00
/usr/lib/postgresql/9.4/bin/postgres -D /var/lib/postgresql/9.4/main -c
config_file=/etc/postgresql/9.4/main/postgresql.conf
(neither are shown after `service postgresql stop`)
I can also connect to both databases.
My notes tell me I did something along the lines of the following:
deb http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg main
sudo apt-get update
sudo apt-get install postgresql-9.4 postgresql-server-dev-9.4
postgresql-contrib-9.4
# ... later
sudo apt-get install postgresql-9.3 postgresql-server-dev-9.3
postgresql-contrib-9.3
(Note discrepency between viviid (my installation) and wheezy in the apt line —
I didn't think that was significant?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1498274
Title:
init.d script doesn't respect `version` argument
Status in postgresql-common package in Ubuntu:
New
Bug description:
Release: Ubuntu 15.04
It seems that the current version of the /etc/init.d/postgresql script
doesn't respect the `version` flag. Help text states:
Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
reload|status} [version ..]
But with 2 installations and called as follows:
/etc/init.d/postgresql start 9.4
or
service postgresql start 9.4
Both 9.4 and 9.3 are started, I expected just 9.4 to start.
Package info:
# apt-cache policy postgresql-common
postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
169.pgdg70+1 0
500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64
Packages
*** 169.pgdg14.04+1 0
100 /var/lib/dpkg/status
166bzr2 0
500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64
Packages
500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1498274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1498274] [NEW] init.d script doesn't respect `version` argument
Public bug reported:
Release: Ubuntu 15.04
It seems that the current version of the /etc/init.d/postgresql script
doesn't respect the `version` flag. Help text states:
Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
reload|status} [version ..]
But with 2 installations and called as follows:
/etc/init.d/postgresql start 9.4
or
service postgresql start 9.4
Both 9.4 and 9.3 are started, I expected just 9.4 to start.
Package info:
# apt-cache policy postgresql-common
postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
169.pgdg70+1 0
500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64
Packages
*** 169.pgdg14.04+1 0
100 /var/lib/dpkg/status
166bzr2 0
500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
** Affects: postgresql-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1498274
Title:
init.d script doesn't respect `version` argument
Status in postgresql-common package in Ubuntu:
New
Bug description:
Release: Ubuntu 15.04
It seems that the current version of the /etc/init.d/postgresql script
doesn't respect the `version` flag. Help text states:
Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
reload|status} [version ..]
But with 2 installations and called as follows:
/etc/init.d/postgresql start 9.4
or
service postgresql start 9.4
Both 9.4 and 9.3 are started, I expected just 9.4 to start.
Package info:
# apt-cache policy postgresql-common
postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
169.pgdg70+1 0
500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64
Packages
*** 169.pgdg14.04+1 0
100 /var/lib/dpkg/status
166bzr2 0
500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64
Packages
500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1498274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319] Re: xrandr --scale restricts area in which mouse moves
This is affecting me with a hDPI primary display (Dell m3800) when adding an external monitor which has to be scaled 2x2 with xrandr in order for the extra display to not appear massive. Is there any way of getting the patch that fixes this without compiling xorg? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Precise: Fix Released Status in xorg-server source package in Quantal: Fix Released Status in xorg-server source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
