[Dx-packages] [Bug 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Hm, to clarity: "The indicator-session opens, and often the menu stays stuck open for a while."...as the panel crashes. That's how I first know the crash has happened again What I wanted to convey was that the rightmost indicator menu opens, and then the crash freezes it; my continued right-arrow inpuds. Not every time. Whether that means that particular indicator is involved, or the next one, date/time, that never opens--or whether that means anything--I am not knowledgeable enough to say. Thank you. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze & crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
I have continued to get this crash, periodically. I think the circumstance that triggers it is, generally at least: 1. opening the app menus in the panel via keyboard shortcuts, then 2. hitting left-arrow to wrap around and access the indicator menus Doing the above does not reproduce the crash every time. I have not seen it happen, I think, when I hit right-arrow, to start on the leftmost indicator applet. Just the left-to-wrap-right move. The indicator-session opens, and often the menu stays stuck open for a while. Incidentally, this behavior is a workaround for the loss of HUD access to indicator menus. (I suppose it may be what I did before the HUD arrived; I don't remember clearly.) Thanks, Marco! -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze & crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1332551] Re: Setting off high contrast changes icon to the default theme
** Package changed: unity (Ubuntu) => unity-control-center (Ubuntu) ** Project changed: unity => hundredpapercuts ** Changed in: hundredpapercuts Importance: Undecided => Low ** Changed in: unity-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332551 Title: Setting off high contrast changes icon to the default theme Status in One Hundred Papercuts: New Status in “unity-control-center” package in Ubuntu: New Bug description: If I set ON to the high contrast option, and then OFF, the icon theme that is set is the default one, but I think should be the one I chose before turning on high contrast. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1332551/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze & crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality
** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-clock-app Assignee: (unassigned) => Nekhelesh Ramananthan (nik90) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons "Ok" and "Show" which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the "Snooze" functionality and replace the "Show" button with "Snooze". However "Snooze" was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the "Ok" button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed "Snooze", then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1163041] Re: Inconsistent behaviour with minimized Trash windows
Care should be taken what happens when user goes somewhere else from trash in the window opened from the trash launcher. And also what happens when one goes to trash from a normal nautilus window. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1163041 Title: Inconsistent behaviour with minimized Trash windows Status in Ayatana Design: Invalid Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.2 series: Confirmed Status in “unity” package in Ubuntu: Triaged Bug description: Now with a fix for LP: #753938 being merged into raring, this presents a new usability challenge to users. The issue: When you open a trash window from the launcher and minimize it, it gets minimized into the Nautilus icon. However, a user would then expect to get the window back by clicking the icon where the window minimized into in the first place, in this case, the Nautilus icon in the launcher. Instead, it opens a new Nautilus window. The issue here is that trash windows and every other Nautilus window are only seperated logically from each other, but not visually. The fix: When minimizing the trash window, instead of minimizing into the Nautilus icon, it should minimize the window into the trash icon in the launcher. I'm purely talking about the minimize animation and triangle next to the trash icon here. Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 unity: Installiert: 6.12.0daily13.04.01-0ubuntu1 Installationskandidat: 6.12.0daily13.04.01-0ubuntu1 Versionstabelle: *** 6.12.0daily13.04.01-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.04.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Apr 2 00:23:51 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1163041/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1329289] Re: Messaging indicator sometimes fails to send a reply
Ok, managed to reproduce before finishing my monthly SMS allowance :-D -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329289 Title: Messaging indicator sometimes fails to send a reply Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: STEPS: 1. Open the messaging app 2. Send a message to your own phone 3. Close the messaging app 4. Hit the power button 5. Drag down the indicator 6. Reply to the message 7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead saves it. See attached screenshot note the greyed send button WORKAROUND: Remove all messages from the indicator and use the messaging app once to reply, you will then be good till your indicator locks up again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 12:01:29 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1329289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1329289] Re: Messaging indicator sometimes fails to send a reply
Cannot reproduce this... reproduced steps 5-6 like 15 times... -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329289 Title: Messaging indicator sometimes fails to send a reply Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: STEPS: 1. Open the messaging app 2. Send a message to your own phone 3. Close the messaging app 4. Hit the power button 5. Drag down the indicator 6. Reply to the message 7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead saves it. See attached screenshot note the greyed send button WORKAROUND: Remove all messages from the indicator and use the messaging app once to reply, you will then be good till your indicator locks up again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 12:01:29 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1329289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1329289] Re: Messaging indicator sometimes fails to send a reply
** Changed in: unity8 (Ubuntu) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu) Assignee: Nick Dedekind (nick-dedekind) => Andrea Cimitan (cimi) ** Tags added: touch-2014-09-11 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329289 Title: Messaging indicator sometimes fails to send a reply Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: STEPS: 1. Open the messaging app 2. Send a message to your own phone 3. Close the messaging app 4. Hit the power button 5. Drag down the indicator 6. Reply to the message 7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead saves it. See attached screenshot note the greyed send button WORKAROUND: Remove all messages from the indicator and use the messaging app once to reply, you will then be good till your indicator locks up again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 12:01:29 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1329289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365039] Re: Could not get session id for session
Please attach /var/log/lightdm/lightdm.log after a failed boot. ** Changed in: lightdm Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1365039 Title: Could not get session id for session Status in Light Display Manager: Incomplete Status in “systemd-shim” package in Ubuntu: New Bug description: A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1). On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting. Here are the troubles met at the next cold boot (verbosy mode): - the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??) - second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again. - third try: same issue, but was able to open tty when it did a pause at swap partition loading: so i reconfigured lightdm and choose gdm as default that time. Startx was ran and after some hard hdd scanning, it finally loaded a degraded login screen: no mouse but the keyboard was working. After login validation, gnome-shell appeared as expected, but again no mouse; a ctrl+alt+T opened a terminal, where i'm right now, to report that issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-2 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic i686 ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Sep 3 17:15:43 2014 SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1365039/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
@dave-eorbit Thank you anyway! -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1329289] Re: Messaging indicator sometimes fails to send a reply
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329289 Title: Messaging indicator sometimes fails to send a reply Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: STEPS: 1. Open the messaging app 2. Send a message to your own phone 3. Close the messaging app 4. Hit the power button 5. Drag down the indicator 6. Reply to the message 7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead saves it. See attached screenshot note the greyed send button WORKAROUND: Remove all messages from the indicator and use the messaging app once to reply, you will then be good till your indicator locks up again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 12:01:29 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1329289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
For what it's worth, I added the command "pkill -f wpa_supplicant" after "nmcli nm sleep false" in my /etc/pm/sleep.d/ thaw or resume script, based on another similar bug that was reported elsewhere (I've lost the link; sorry). Now the wireless interface comes back up pretty consistently after a return from suspend... however, from time to time, after coming back from suspend once, it returns to suspend a few seconds later. It's never done this repeatedly after an initial suspend. Not sure if this amounts to forward progress or just sideways wiggling, but I thought I'd report it in case it rang any bells... -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1260728] Re: Indicators should send timestamps, not pre-formatted strings
** Changed in: unity8 (Ubuntu) Importance: Undecided => Medium ** Changed in: unity8 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1260728 Title: Indicators should send timestamps, not pre-formatted strings Status in The Unity 8 shell: Triaged Status in “indicator-datetime” package in Ubuntu: Triaged Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Triaged Bug description: Some indicators send pre-formatted strings, when they should be sending unix timestamps, to be formatted by the UI according to locale / timezone / user preferences. See https://wiki.ubuntu.com/TimeAndDate for the design spec. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1260728/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1350952] Re: [Indicators] replace the text "Empty!" with something more useful
** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Status: Confirmed => Triaged ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350952 Title: [Indicators] replace the text "Empty!" with something more useful Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Triaged Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Bug description: when clearing the menu on this indicator (and others), the text "Empty!" is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350952/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1255180] Re: Reading scope models sometimes produces lots of criticals
** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255180 Title: Reading scope models sometimes produces lots of criticals Status in Dee: New Status in Unity: New Status in The Unity 8 shell: Triaged Status in “unity” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: In some cases shell gets into a situation where the results in the dee model are not properly synchronized with the qt model, which can cause the qt wrapper to try reading (now) invalid rows. This was identified to be caused because of the way the scope results model works and how its qt wrapper deals with changesets. Basically we have a single DeeSharedModel that contains all the results for a particular search, that model gets split up by category id into multiple DeeFilterModels, which contain results for a specific category. Now the problem is that when there's a transaction (ie multiple row additions/removals) on the master shared model, the transaction is mirrored in the per-category filter models, but it introduces a problem cause we don't serialize the changes, which means that multiple filter models can have an active transaction at the same time, and when one the filter models synchronizes with the qt wrapper, a visibility change can cause a different model to be shown, and since that model is still processing the transaction, the qt wrapper won't be properly synchronized, and can ask for rows that are about to be removed. A solution to this problem is making sure that there's always just one active transaction on the filter models. To manage notifications about this bug go to: https://bugs.launchpad.net/dee/+bug/1255180/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1289981] Re: Sound indicator : play icon for gmusicbrower always busy (only if big songs collection in gmbrowser)
Thanks for your quick reply. I guess we should leave this report open until it auto-expires. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1289981 Title: Sound indicator : play icon for gmusicbrower always busy (only if big songs collection in gmbrowser) Status in “indicator-sound” package in Ubuntu: Incomplete Status in “xfce4-indicator-plugin” package in Ubuntu: Incomplete Bug description: To reproduce the bug : 1-Having lot of songs in gmusicmbrower (I have 1668 song). This bug doesn't occurs for other users of the same PC having small collections 2-click on sound indicator 3-I expect that gmusicbrowser play icon is avalaible 4- What happens : play icon is indefinitely busy. Forward and backward icons are not working either Xubuntu Trusty (beta1) 32 bits ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-indicator-plugin 2.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Sun Mar 9 10:42:17 2014 SourcePackage: xfce4-indicator-plugin UpgradeStatus: Upgraded to trusty on 2014-01-26 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1289981/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Also experiencing this on Ubuntu 14.04. It's much easier to reproduce the longer you leave the computer in hibernation. I usually can't reproduce if I hibernate for a few minutes and then resume, but if I hibernate overnight and resume the next morning, this bug almost always occurs. Doing a sudo service network-manager restart works around it, but is annoying. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1355966] Re: [FFE] Implement AbandonScope (etc)
** Summary changed: - Implement AbandonScope (etc) + [FFE] Implement AbandonScope (etc) -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1355966 Title: [FFE] Implement AbandonScope (etc) Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: New Bug description: Currently, logout produces the following error in upstart systems: systemd-logind[15351]: Failed to abandon scope session-c7.scope systemd-logind[15351]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc7_2escope Whlie the cgroup is being autoremoved when empty, the more important bug is that StopSession won't forcibly kill the cgroup. These methods should be added at some point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1355966/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1340952] Re: Video and Music scopes should provide non-file:/// based URIs
** Changed in: mediaplayer-app Status: New => In Progress ** Changed in: mediaplayer-app Importance: Undecided => High ** Changed in: mediaplayer-app Assignee: (unassigned) => Ted Gould (ted) -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1340952 Title: Video and Music scopes should provide non-file:/// based URIs Status in Media Player App: In Progress Status in Unity Media Scanner Scope: Confirmed Status in QML plugin for Scopes: Confirmed Status in “url-dispatcher” package in Ubuntu: In Progress Bug description: There are some mp4 videos found/indexed by mediascanner-service-2.0 from ~/Pictures. The thumbnails of those are shown in the Video scope but can not be played. If the video is moved over to ~/Videos, the videos are played just fine. mako utopic r119 To manage notifications about this bug go to: https://bugs.launchpad.net/mediaplayer-app/+bug/1340952/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310788] Re: Thunar exists with segfault when accessing the context menu a second time
Yes, I can only replicate the first warning, but not the second one which crashes. Alexander, if you're willing, you can try the first four steps of: https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages sudo apt-get install unity-gtk2-module-dbgsym gdb thunar Right-click twice to reproduce the crash. gdb should stop, and then you can provide us the output of 'bt'. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1310788 Title: Thunar exists with segfault when accessing the context menu a second time Status in “thunar” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Under ubuntu 14.04. Thunar 1.6.3-1ubuntu5 crashes if I try to access the context menu twice (via right click). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1310788/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04)
Still happening in 13.10 after updating system on 9/1/2014. Reboot does NOT fix problem, but 'killall unity-panel-service' does. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04) Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1244285/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365039] Re: Could not get session id for session
** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1365039 Title: Could not get session id for session Status in Light Display Manager: New Status in “systemd-shim” package in Ubuntu: New Bug description: A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1). On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting. Here are the troubles met at the next cold boot (verbosy mode): - the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??) - second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again. - third try: same issue, but was able to open tty when it did a pause at swap partition loading: so i reconfigured lightdm and choose gdm as default that time. Startx was ran and after some hard hdd scanning, it finally loaded a degraded login screen: no mouse but the keyboard was working. After login validation, gnome-shell appeared as expected, but again no mouse; a ctrl+alt+T opened a terminal, where i'm right now, to report that issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-2 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic i686 ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Sep 3 17:15:43 2014 SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1365039/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310788] Re: Thunar exists with segfault when accessing the context menu a second time
What we'd like to know is how you set this machine up - is it a xubuntu install with ubuntu added, ubuntu with xubuntu installed, ubuntu with thunar installed. I've not been able to confirm this issue - more detail of how you got to where you are will help. Thanks. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1310788 Title: Thunar exists with segfault when accessing the context menu a second time Status in “thunar” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Under ubuntu 14.04. Thunar 1.6.3-1ubuntu5 crashes if I try to access the context menu twice (via right click). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1310788/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365039] Re: Could not get session id for session
from /var/log/upstart/cups.log : cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration auth.log give some more details: Sep 3 16:59:41 u32 gdm-password][2215]: pam_succeed_if(gdm-password:auth): requirement "user ingroup nopasswdlogin" not met by user "oem" Sep 3 16:59:49 u32 gdm-password][2215]: pam_unix(gdm-password:session): session opened for user oem by (unknown)(uid=0) Sep 3 16:59:49 u32 kernel: [ 202.752699] systemd-logind[1125]: Failed to start unit user@1000.service: Unknown unit: user@1000.service Sep 3 16:59:49 u32 kernel: [ 202.752707] systemd-logind[1125]: Failed to start user service: Unknown unit: user@1000.service Sep 3 16:59:49 u32 kernel: [ 202.758288] systemd-logind[1125]: New session c2 of user oem. Sep 3 16:59:49 u32 kernel: [ 202.758310] systemd-logind[1125]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. Sep 3 16:59:49 u32 gdm-launch-environment][1680]: pam_unix(gdm-launch-environment:session): session closed for user gdm Sep 3 16:59:49 u32 kernel: [ 202.985699] systemd-logind[1125]: Failed to abandon scope session-c1.scope Sep 3 16:59:49 u32 kernel: [ 202.985709] systemd-logind[1125]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope Sep 3 16:59:49 u32 polkitd(authority=local): Unregistered Authentication Agent for unix-session:c1 (system bus name :1.45, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ) (disconnected from bus) Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: Gkm: using old keyring directory: /home/oem/.gnome2/keyrings Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: Gkm: using old keyring directory: /home/oem/.gnome2/keyrings Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: message repeated 2 times: [ couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files] Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The Secret Service was already initialized Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The PKCS#11 component was already initialized Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The SSH agent was already initialized Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The GPG agent was already initialized Sep 3 16:59:56 u32 polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.80 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Sep 3 17:01:00 u32 sudo: oem : TTY=pts/7 ; PWD=/home/oem ; USER=root ; COMMAND=/usr/sbin/synaptic Sep 3 17:01:00 u32 sudo: pam_unix(sudo:session): session opened for user root by oem(uid=0) Sep 3 17:03:59 u32 pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Sep 3 17:03:59 u32 pkexec[2739]: oem: Executing command [USER=root] [TTY=unknown] [CWD=/home/oem] [COMMAND=/usr/lib/update-notifier/package-system-locked] Sep 3 17:04:21 u32 gnome-keyring-daemon[2231]: keyring alias directory: /home/oem/.gnome2/keyrings Sep 3 17:16:35 u32 gnome-keyring-daemon[2231]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk Sep 3 17:17:01 u32 CRON[4597]: pam_unix(cron:session): session opened for user root by (uid=0) Sep 3 17:17:01 u32 CRON[4597]: pam_unix(cron:session): session closed for user root -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1365039 Title: Could not get session id for session Status in “systemd-shim” package in Ubuntu: New Bug description: A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1). On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting. Here are the troubles met at the next cold boot (verbosy mode): - the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??) - second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again. - third try: same issue, but was able to open
[Dx-packages] [Bug 1310788] Re: Thunar exists with segfault when accessing the context menu a second time
At the moment I am using Unity and it happens while I am doing a right click on a file or directory. Yes, my machine is up to date. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1310788 Title: Thunar exists with segfault when accessing the context menu a second time Status in “thunar” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Under ubuntu 14.04. Thunar 1.6.3-1ubuntu5 crashes if I try to access the context menu twice (via right click). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1310788/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365039] Re: Could not get session id for session
'nouveau' driver is not cleanly loaded, as it usually is ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1365039/+attachment/4194458/+files/Xorg.0.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1365039 Title: Could not get session id for session Status in “systemd-shim” package in Ubuntu: New Bug description: A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1). On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting. Here are the troubles met at the next cold boot (verbosy mode): - the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??) - second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again. - third try: same issue, but was able to open tty when it did a pause at swap partition loading: so i reconfigured lightdm and choose gdm as default that time. Startx was ran and after some hard hdd scanning, it finally loaded a degraded login screen: no mouse but the keyboard was working. After login validation, gnome-shell appeared as expected, but again no mouse; a ctrl+alt+T opened a terminal, where i'm right now, to report that issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-2 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic i686 ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Sep 3 17:15:43 2014 SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1365039/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365039] [NEW] Could not get session id for session
Public bug reported: A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1). On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting. Here are the troubles met at the next cold boot (verbosy mode): - the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??) - second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again. - third try: same issue, but was able to open tty when it did a pause at swap partition loading: so i reconfigured lightdm and choose gdm as default that time. Startx was ran and after some hard hdd scanning, it finally loaded a degraded login screen: no mouse but the keyboard was working. After login validation, gnome-shell appeared as expected, but again no mouse; a ctrl+alt+T opened a terminal, where i'm right now, to report that issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-2 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic i686 ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Sep 3 17:15:43 2014 SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 package-from-proposed utopic ** Attachment added: ".xsession-errors" https://bugs.launchpad.net/bugs/1365039/+attachment/4194452/+files/.xsession-errors -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1365039 Title: Could not get session id for session Status in “systemd-shim” package in Ubuntu: New Bug description: A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1). On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting. Here are the troubles met at the next cold boot (verbosy mode): - the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??) - second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again. - third try: same issue, but was able to open tty when it did a pause at swap partition loading: so i reconfigured lightdm and choose gdm as default that time. Startx was ran and after some hard hdd scanning, it finally loaded a degraded login screen: no mouse but the keyboard was working. After login validation, gnome-shell appeared as expected, but again no mouse; a ctrl+alt+T opened a terminal, where i'm right now, to report that issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-2 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic i686 ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Sep 3 17:15:43 2014 SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1365039/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310788] Re: Thunar exists with segfault when accessing the context menu a second time
** Changed in: unity-gtk-module (Ubuntu) Assignee: (unassigned) => William Hua (attente) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1310788 Title: Thunar exists with segfault when accessing the context menu a second time Status in “thunar” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Under ubuntu 14.04. Thunar 1.6.3-1ubuntu5 crashes if I try to access the context menu twice (via right click). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1310788/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1289981] Re: Sound indicator : play icon for gmusicbrower always busy (only if big songs collection in gmbrowser)
No more in 14.04.1. (I have also removed about a third of my songs from my collection) Karim 2014-09-03 14:44 GMT+01:00 Thaddäus Tintenfisch : > Is this bug still present in the final release of Xubuntu 14.04? > > ** Changed in: indicator-sound (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1289981 > > Title: > Sound indicator : play icon for gmusicbrower always busy (only if big > songs collection in gmbrowser) > > Status in "indicator-sound" package in Ubuntu: > Incomplete > Status in "xfce4-indicator-plugin" package in Ubuntu: > Incomplete > > Bug description: > To reproduce the bug : > 1-Having lot of songs in gmusicmbrower (I have 1668 song). This bug > doesn't occurs for other users of the same PC having small collections > 2-click on sound indicator > 3-I expect that gmusicbrowser play icon is avalaible > 4- What happens : play icon is indefinitely busy. Forward and backward > icons are not working either > > Xubuntu Trusty (beta1) 32 bits > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: xfce4-indicator-plugin 2.3.0-0ubuntu1 > ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 > Uname: Linux 3.13.0-16-generic i686 > ApportVersion: 2.13.3-0ubuntu1 > Architecture: i386 > CurrentDesktop: XFCE > Date: Sun Mar 9 10:42:17 2014 > SourcePackage: xfce4-indicator-plugin > UpgradeStatus: Upgraded to trusty on 2014-01-26 (41 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1289981/+subscriptions > -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1289981 Title: Sound indicator : play icon for gmusicbrower always busy (only if big songs collection in gmbrowser) Status in “indicator-sound” package in Ubuntu: Incomplete Status in “xfce4-indicator-plugin” package in Ubuntu: Incomplete Bug description: To reproduce the bug : 1-Having lot of songs in gmusicmbrower (I have 1668 song). This bug doesn't occurs for other users of the same PC having small collections 2-click on sound indicator 3-I expect that gmusicbrowser play icon is avalaible 4- What happens : play icon is indefinitely busy. Forward and backward icons are not working either Xubuntu Trusty (beta1) 32 bits ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-indicator-plugin 2.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Sun Mar 9 10:42:17 2014 SourcePackage: xfce4-indicator-plugin UpgradeStatus: Upgraded to trusty on 2014-01-26 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1289981/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1364999] [NEW] Blocked password prompt in Unity lock screen
Public bug reported: Sometimes when I lock the screen, I can't get in again. I have to press Ctrl+Alt+F1 and kill X or reboot to get in again. The problem is actually that I can't type in the password because the text input field is no longer there. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Sep 3 14:25:34 2014 InstallationDate: Installed on 2014-07-10 (55 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty ** Attachment added: "Locked & Blocked" https://bugs.launchpad.net/bugs/1364999/+attachment/4194406/+files/lockNblock.jpg -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1364999 Title: Blocked password prompt in Unity lock screen Status in “unity” package in Ubuntu: New Bug description: Sometimes when I lock the screen, I can't get in again. I have to press Ctrl+Alt+F1 and kill X or reboot to get in again. The problem is actually that I can't type in the password because the text input field is no longer there. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Sep 3 14:25:34 2014 InstallationDate: Installed on 2014-07-10 (55 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1364999/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Happens for me on Lenovo T420 frequently. At work, I hook it up to the second monitor. Yesterday I rebooted, it came up in dual monitor mode, and it was fine all day, including closing the lid, and the password box is there. At the EOD, I close the lid, unplug the monitor. Came back in, plug it back in, initial log in is ok. And then when the screen times out, both screens doesn't have the password dialog. End up doing a unity --replace on VT1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1341562] Re: indicator-printers not working on Ubuntu 14.04
I installed 14.04.1 (fresh, not an update) a week ago, and have kept it up-to-date. I have only installed a couple of packages from the standard repositories: vim, java, no fancy stuff. I configured a couple of network printers (via SMB print server), and noticed that when I print, no indicator appears. Also, the jobs won't start printing until I open the corresponding print queue in the "Printers" configuration application. This may be related to the fact that these printers require user authentication. Anyway, this is an inconvenience that would probably be solved if the indicator-printers applet were running properly. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1289981] Re: Sound indicator : play icon for gmusicbrower always busy (only if big songs collection in gmbrowser)
Is this bug still present in the final release of Xubuntu 14.04? ** Changed in: indicator-sound (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1289981 Title: Sound indicator : play icon for gmusicbrower always busy (only if big songs collection in gmbrowser) Status in “indicator-sound” package in Ubuntu: Incomplete Status in “xfce4-indicator-plugin” package in Ubuntu: Incomplete Bug description: To reproduce the bug : 1-Having lot of songs in gmusicmbrower (I have 1668 song). This bug doesn't occurs for other users of the same PC having small collections 2-click on sound indicator 3-I expect that gmusicbrowser play icon is avalaible 4- What happens : play icon is indefinitely busy. Forward and backward icons are not working either Xubuntu Trusty (beta1) 32 bits ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-indicator-plugin 2.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Sun Mar 9 10:42:17 2014 SourcePackage: xfce4-indicator-plugin UpgradeStatus: Upgraded to trusty on 2014-01-26 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1289981/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1352072] Re: notification-daemon crashed with signal 5 in g_source_remove()
*** This bug is a duplicate of bug 1273014 *** https://bugs.launchpad.net/bugs/1273014 ** This bug has been marked a duplicate of bug 1273014 notification-daemon crashed with signal 5 in g_source_remove() -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1352072 Title: notification-daemon crashed with signal 5 in g_source_remove() Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: I'm working with openbox. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 Date: Sun Aug 3 21:57:20 2014 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-04-27 (98 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /usr/lib/notification-daemon/notification-daemon Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_source_remove() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1352072/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310788] Re: Thunar exists with segfault when accessing the context menu a second time
** Changed in: thunar (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity-gtk-module (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1310788 Title: Thunar exists with segfault when accessing the context menu a second time Status in “thunar” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Under ubuntu 14.04. Thunar 1.6.3-1ubuntu5 crashes if I try to access the context menu twice (via right click). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1310788/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310788] Re: Thunar exists with segfault when accessing the context menu a second time
Could you please tell us which desktop you are using? Xfce or Unity? Also where exactly do you right click to make it crash? And do you have all available updates installed? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1310788 Title: Thunar exists with segfault when accessing the context menu a second time Status in “thunar” package in Ubuntu: Confirmed Status in “unity-gtk-module” package in Ubuntu: Confirmed Bug description: Under ubuntu 14.04. Thunar 1.6.3-1ubuntu5 crashes if I try to access the context menu twice (via right click). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1310788/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351815] Re: StartTransientUnit signature has changed in systemd 214
** Branch linked: lp:ubuntu/utopic-proposed/systemd-shim -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1351815 Title: StartTransientUnit signature has changed in systemd 214 Status in “systemd-shim” package in Ubuntu: Fix Committed Bug description: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351815] Re: StartTransientUnit signature has changed in systemd 214
** Branch linked: lp:debian/systemd-shim -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1351815 Title: StartTransientUnit signature has changed in systemd 214 Status in “systemd-shim” package in Ubuntu: Fix Committed Bug description: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
This bug was fixed in the package dovecot - 1:2.2.9-1ubuntu5 --- dovecot (1:2.2.9-1ubuntu5) utopic; urgency=medium * No-change rebuild against current debhelper to drop unnecessary upstart dependency. (LP: #1351306) -- Martin PittWed, 03 Sep 2014 09:50:41 +0200 ** Changed in: dovecot (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Released Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
This bug was fixed in the package hockeypuck - 1.0~rel20140413+7a1892a~trusty.1 --- hockeypuck (1.0~rel20140413+7a1892a~trusty.1) utopic; urgency=medium * Drop unnecessary upstart recommends, the package has an init.d script as well which is supported by all init systems. (LP: #1351306) -- Martin PittWed, 03 Sep 2014 09:44:14 +0200 ** Changed in: hockeypuck (Ubuntu) Status: Fix Committed => Fix Released ** Branch linked: lp:ubuntu/utopic-proposed/dovecot -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: In Progress Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Released Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Changed in: ubuntu-app-launch (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: In Progress Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Released Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:~pitti/ubuntu-app-launch/upstart-dep -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: In Progress Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Also affects: ubuntu-app-launch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: In Progress Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Also affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Changed in: dovecot (Ubuntu) Status: New => In Progress ** Changed in: dovecot (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: In Progress Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/hockeypuck/utopic- proposed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: In Progress Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Changed in: pay-service (Ubuntu) Status: New => In Progress ** Also affects: hockeypuck (Ubuntu) Importance: Undecided Status: New ** Changed in: hockeypuck (Ubuntu) Status: New => Fix Committed ** Changed in: hockeypuck (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “dovecot” package in Ubuntu: In Progress Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:~pitti/pay-service/upstart-dep -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:~pitti/unity/upstart-dep -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
Sorry, this doesn't actually affect unity-lens-applications, this is just a transitive dep. ** Changed in: unity-lens-applications (Ubuntu) Status: New => Invalid ** Changed in: unity (Ubuntu) Status: New => In Progress ** Also affects: pay-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “hockeypuck” package in Ubuntu: Fix Committed Status in “pay-service” package in Ubuntu: In Progress Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-lens-applications (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “pay-service” package in Ubuntu: New Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “unity-lens-applications” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (>= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (>= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (>= 1.11-0ubuntu3). dbus depends on upstart (>= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
