[Bug 1315021] [NEW] Service restart fails because process has not exited
Public bug reported: When restarting the puppetmaster process (via the service command, or calling the initscript directly), the restart can fail if the original process does not exit immediately. This is because the initscript is not written to wait for the original process to exit. In my testing under Trusty, adding -R n to the start-stop-daemon command in the initscript fixed the problem. It's difficult to determine an appropriate value for n, but it could be tunable via /etc/default/puppetmaster. It's definitely a problem not to wait at all for the process to exit. ** Affects: puppetmaster (Ubuntu) Importance: Undecided Status: New ** Description changed: - When the puppetmaster process (via the service command, or calling the - initscript directly), the restart can fail if the original process does - not exit immediately. This is because the initscript is not written to - wait for the original process to exit. + When restarting the puppetmaster process (via the service command, or + calling the initscript directly), the restart can fail if the original + process does not exit immediately. This is because the initscript is not + written to wait for the original process to exit. In my testing, adding -R n to the start-stop-daemon command in the initscript fixed the problem. It's difficult to determine an appropriate value for n, but it could be tunable via /etc/default/puppetmaster. It's definitely a problem not to wait at all for the process to exit. ** Description changed: When restarting the puppetmaster process (via the service command, or calling the initscript directly), the restart can fail if the original process does not exit immediately. This is because the initscript is not written to wait for the original process to exit. - In my testing, adding -R n to the start-stop-daemon command in the - initscript fixed the problem. It's difficult to determine an appropriate - value for n, but it could be tunable via /etc/default/puppetmaster. It's - definitely a problem not to wait at all for the process to exit. + In my testing under Trusty, adding -R n to the start-stop-daemon + command in the initscript fixed the problem. It's difficult to determine + an appropriate value for n, but it could be tunable via + /etc/default/puppetmaster. It's definitely a problem not to wait at all + for the process to exit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315021 Title: Service restart fails because process has not exited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetmaster/+bug/1315021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276766] Re: puppet incorrectly enumerates upstart jobs when called with puppet resource service
Fixed in upstream: https://tickets.puppetlabs.com/browse/PUP-1332 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1276766 Title: puppet incorrectly enumerates upstart jobs when called with puppet resource service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- 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 1276766] Re: puppet incorrectly enumerates upstart jobs when called with puppet resource service
Fixed in upstream: https://tickets.puppetlabs.com/browse/PUP-1332 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276766 Title: puppet incorrectly enumerates upstart jobs when called with puppet resource service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235147] Re: Unknown parameter
Fixed in upstream: https://tickets.puppetlabs.com/browse/PUP-1332 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235147 Title: Unknown parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158107] [NEW] launcher does not hide when auto-hide is enabled
Public bug reported: After upgrading to raring, the launcher never auto-hides, even with the Auto-hide the Launcher setting is enabled. When the setting is toggled, maximized windows resize to fit the full as if the launcher were hidden, but it never disappears. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.13.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed Mar 20 22:49:59 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-17 (184 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-03-19 (1 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158107 Title: launcher does not hide when auto-hide is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1158107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090383] [NEW] Dash does not display unless other windows are open
Public bug reported: When no windows are open on the screen, as when I've first logged in, the Dash refuses to open. The launcher bar works (hiding/showing, as expected), but clicking the Dash Home button or pressing the Super key does nothing. As soon as I open any window (usually I drop down Tilda using a key shortcut), the on-screen button and Super key both work again. This problem started after an upgrade from Precise to Quantal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,put,regex,move,vpswitch,imgpng,gnomecompat,animation,workarounds,unitymtgrabhandles,place,mousepoll,snap,expo,resize,wall,fade,grid,ezoom,session,scale,unityshell] CompositorRunning: compiz Date: Fri Dec 14 08:19:19 2012 DistUpgraded: 2012-09-06 09:55:41,509 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: fglrx, 9.000, 3.5.0-19-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-18-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-19-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Redwood PRO [Radeon HD 5500 Series] [1002:68d9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3051] InstallationDate: Installed on 2012-08-11 (124 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) JockeyStatus: kmod:fglrx - ATI Fire GL (Proprietary, Enabled, In use) kmod:fglrx_updates - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=c296c803-7748-4fc1-8921-173f75886ec5 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-09-06 (98 days ago) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785T-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0603:bd09/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785T-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.8.6-0ubuntu1~test1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090383 Title: Dash does not display unless other windows are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1090383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053669] Re: Relation not found when running relation-list
After talking this through with a few folks, it looks like this may be fixed in some version of juju. Adding juju-origin: ppa to environments.yaml makes the problem go away. The issue remains in the stock version of juju for precise. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1053669 Title: Relation not found when running relation-list To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1053669/+subscriptions -- 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 1053669] Re: Relation not found when running relation-list
After talking this through with a few folks, it looks like this may be fixed in some version of juju. Adding juju-origin: ppa to environments.yaml makes the problem go away. The issue remains in the stock version of juju for precise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053669 Title: Relation not found when running relation-list To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1053669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046910] [NEW] Custom keyboard shortcuts for maximize and restore are broken after upgrade
Public bug reported: After upgrading 12.10 beta, I found that my custom maximize (ctrl-super- up) and minimize (ctrl-super-down) shortcuts weren't working. The default shortcuts (super-up, super-down) did work, and were reported in the shortcuts screen (hold super). Re-applying the shortcuts in the keyboard shortcuts panel didn't fix them, but disabling them and re-setting them did. ** Affects: 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/1046910 Title: Custom keyboard shortcuts for maximize and restore are broken after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1046910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660588] Re: Path is included in TerminalServerClient item name
** Also affects: gnome-do-plugins (Ubuntu) Importance: Undecided Status: New -- Path is included in TerminalServerClient item name https://bugs.launchpad.net/bugs/660588 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
