[Dx-packages] [Bug 1370069] Re: Unlock does not work
I am using 14.04 LTS. Is there a fix available for LTS I could test? -- 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/1370069 Title: Unlock does not work Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: After screen lock the login does not display a field where a password can be typed and thus there seems to be no way to login to machine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Sep 16 16:53:05 2014 DistUpgraded: 2014-04-11 11:51:55,755 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Subsystem: Hewlett-Packard Company Device [103c:18e4] Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1002:6771] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:90b8] InstallationDate: Installed on 2013-11-05 (315 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=ef4f067e-192b-4f3f-873d-bfb295641eec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to trusty on 2014-04-11 (158 days ago) dmi.bios.date: 09/09/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.18 dmi.board.asset.tag: CZC3427KBP dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3427KBP dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP EliteDesk 800 G1 TWR dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 4 10:17:39 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1370069/+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 1349281] Re: The exposed open windows are displayed in the correct order
** Changed in: unity Assignee: (unassigned) = Eleni Maria Stea (hikiko) ** Changed in: unity Status: New = Confirmed -- 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/1349281 Title: The exposed open windows are displayed in the correct order Status in Unity: Confirmed Status in “unity” package in Ubuntu: New Bug description: When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in the wrong order: windows that are in the top-left corner can be shown in the right bottom position or on the top bottom corner. This makes very hard to switch between similarly looking windows like terminals. How to reproduce: * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. The thing that is more strange is that you have to move the mouse pointer to a certain point (let's say right-top), then you see the window has appeared far away (let's say bottom-left) so you have to move your mouse again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+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 1374301] [NEW] osd notifications blurry
You have been subscribed to a public bug: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- osd notifications blurry https://bugs.launchpad.net/bugs/1374301 You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. -- 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 1374350] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()
*** This bug is a duplicate of bug 1199571 *** https://bugs.launchpad.net/bugs/1199571 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1199571, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1374350/+attachment/4215788/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1374350/+attachment/4215790/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1374350/+attachment/4215792/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1374350/+attachment/4215793/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1374350/+attachment/4215794/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1374350/+attachment/4215795/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1374350/+attachment/4215796/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1199571 Huge multi-threading violations in cairo ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1374350 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: Started to happen randomly at 14.04 and continued to 14.10 ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 26 11:45:50 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-18 (160 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7fe6a9a59540:mov%rdx,0x10(%rax) PC (0x7fe6a9a59540) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: Upgraded to utopic on 2014-09-25 (0 days ago) UserGroups: sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374350/+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 1374301] Re: osd notifications blurry
** Package changed: ubuntu = notify-osd (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: New Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+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 1374301] Re: osd notifications blurry
Can you provide a screenshot of the encountered issue, Andrew? Futhermore what type of session (desktop-environment) are you running? -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: New Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+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 1374383] [NEW] Clicking on Files opens new window, rather than switch to already open one
Public bug reported: Although I can currently recreate the bug with Files (Nautilius, is it?), I remember having seen such a thing before with other windows, although only with previous Ubuntu versions. The bug is as follows. In the current desktop, I open Files (and I see the arrows on the left saying how many of such windows are open). It only happens if Files is open once. I click on a partition that is not automatically mounted on startup (e.g. a Windows partition) (I haven't tested with one that automatically mounts but is not a part of /), regardless of whether it was previously mounted or not. When I switch away from that window (e.g. click on Firefox), then I click back on its icon, I get a new Files window, rather than the old one I had open, which was viewing the windows partition. If you can't replicate this, try CTRL+L (leave the cursor on the path box) on that window and then switch away and back. Note that with ALT+TAB and ALT+` I can see the window alright. Also, if there is more than one Files window, whether all looking at windows partitions or not, there is no problem, even if the first such window was the last to be viewed, clicking on the Files icon correctly returns to that window. In summary, when Files is opened once and viewing a windows partition, clicking on a different application and back on its icon opens a new Files window rather than switch to the old one. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CurrentDesktop: Unity Date: Fri Sep 26 12:01:15 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-07-04 (83 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) --- P.S. regarding info collected by `ubuntu-bug`: - This is NOT a fresh install. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Description changed: Although I can currently recreate the bug with Files (Nautilius, is it?), I remember having seen such a thing before with other windows, although only with previous Ubuntu versions. The bug is as follows. In the current desktop, I open Files (and I see the arrows on the left saying how many of such windows are open). It only happens if Files is open once. I click on a partition that is not automatically mounted on startup (e.g. a Windows partition) (I haven't tested with one that automatically mounts but is not a part of /), regardless of whether it was previously mounted or not. When I switch away from that window (e.g. click on Firefox), then I click back on its icon, I get a new Files window, rather than the old one I had open, which was viewing the windows partition. If you can't replicate this, try CTRL+L (leave the cursor on the path box) on that window and then switch away and back. Note that with ALT+TAB and ALT+` I can see the window alright. Also, if there is more than one Files window, whether all looking at windows partitions or not, there is no problem, even if the first such window was the last to be viewed, clicking on the Files icon correctly returns to that window. In summary, when Files is opened once and viewing a windows partition, clicking on a different application and back on its icon opens a new Files window rather than switch to the old one. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CurrentDesktop: Unity Date: Fri Sep 26 12:01:15 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-07-04 (83 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) + + --- + + P.S. regarding info collected by `ubuntu-bug`: + + - This is NOT a fresh install. -- 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/1374383 Title:
[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:ubuntu/utopic-proposed/ubuntu-app-launch -- 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 Unity: Fix Released 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: Fix Released 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: Fix Released 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/unity/+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 1367817] Re: Revert icon to previous 'envelope' design
This bug was fixed in the package ubuntu-themes - 14.04+14.10.20140925-0ubuntu1 --- ubuntu-themes (14.04+14.10.20140925-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Revert the suru theme's message indicators back to the earlier 'envelope' look. (LP: #1367817) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 25 Sep 2014 13:30:08 + ** Changed in: ubuntu-themes (Ubuntu) Status: New = Fix Released -- 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/1367817 Title: Revert icon to previous 'envelope' design Status in Themes for Ubuntu: In Progress Status in “indicator-messages” package in Ubuntu: In Progress Status in “ubuntu-themes” package in Ubuntu: Fix Released Bug description: The previous 'envelope' icon worked better. UX Testing Finding: All participants associated the icon with an alarm or reminder. They all failed to interact with it when looking for missed calls and unread messages. They had to go to the dialer and messages separately to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1367817/+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 1370735] Re: Failing ServiceTest.ApplicationTest test in PPA
This bug was fixed in the package url-dispatcher - 0.1+14.10.20140925-0ubuntu1 --- url-dispatcher (0.1+14.10.20140925-0ubuntu1) utopic; urgency=low [ Ted Gould ] * Drop file based URLs for Music and Video (LP: #1340952) * Update tests to work with new UAL requirements (LP: #1370735) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 25 Sep 2014 13:29:40 + ** Changed in: url-dispatcher (Ubuntu) Status: New = Fix Released -- 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/1370735 Title: Failing ServiceTest.ApplicationTest test in PPA Status in URL Dispatcher: Confirmed Status in “url-dispatcher” package in Ubuntu: Fix Released Bug description: Chatting with ted, this test failure unexpected, locally reproducible, and possibly related to the new UAL. https://launchpadlibrarian.net/185144786/buildlog_ubuntu-utopic-i386 .url- dispatcher_0.1%2B14.10.20140905.1%2Balesage01-0ubuntu2_FAILEDTOBUILD.txt.gz I'll let ted set importance, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/url-dispatcher/+bug/1370735/+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 1365408] Re: Should ship a PNG icon instead of using the theme
This bug was fixed in the package indicator-messages - 13.10.1+14.10.20140925-0ubuntu1 --- indicator-messages (13.10.1+14.10.20140925-0ubuntu1) utopic; urgency=low [ Lars Uebernickel ] * Support X-Ubuntu-SymbolicIcon in desktop files (LP: #1365408) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 25 Sep 2014 14:41:04 + ** Changed in: indicator-messages (Ubuntu) Status: New = Fix Released -- 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/1365408 Title: Should ship a PNG icon instead of using the theme Status in Ubuntu Application Launcher: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “address-book-app” package in Ubuntu: Fix Released Status in “dialer-app” package in Ubuntu: Confirmed Status in “indicator-messages” package in Ubuntu: Fix Released Status in “mediaplayer-app” package in Ubuntu: In Progress Status in “messaging-app” package in Ubuntu: Confirmed Status in “sync-monitor” package in Ubuntu: Invalid Status in “ubuntu-app-launch” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: In Progress Bug description: By design request, all apps, click or not, should ship their own icon as PNG instead of using icons from the theme. Please download the respective icon from http://bazaar.launchpad.net /~ubuntu-art-pkg/ubuntu-themes/trunk/files/head:/suru-icons/apps/256/ and include in your packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1365408/+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
This bug was fixed in the package url-dispatcher - 0.1+14.10.20140925-0ubuntu1 --- url-dispatcher (0.1+14.10.20140925-0ubuntu1) utopic; urgency=low [ Ted Gould ] * Drop file based URLs for Music and Video (LP: #1340952) * Update tests to work with new UAL requirements (LP: #1370735) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 25 Sep 2014 13:29:40 + ** Changed in: url-dispatcher (Ubuntu) Status: In Progress = Fix Released -- 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: Fix Released Status in Unity Media Scanner Scope: Confirmed Status in QML plugin for Scopes: Invalid Status in “url-dispatcher” package in Ubuntu: Fix Released 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 1374390] [NEW] when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen
Public bug reported: When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?) screen appears to unlock. I tried to reinstall unity, unity-services, lightdm, unity-greeter, but nothing has changed. Remark: I have two other machines, one of them works correctly, but on the other the locking (Ctrl+Alt+l) doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 26 12:35:49 2014 DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-10-15 (345 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007) MachineType: ASUSTeK COMPUTER INC. X202E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (161 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 26 12:10:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12380 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 package-from-proposed trusty ubuntu -- 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/1374390 Title: when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen Status in “unity” package in Ubuntu: New Bug description: When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?) screen appears to unlock. I tried to reinstall unity, unity-services, lightdm, unity-greeter, but nothing has changed. Remark: I have two other machines, one of them works correctly, but on the other the locking (Ctrl+Alt+l) doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 26 12:35:49 2014 DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-10-15 (345 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007)
[Dx-packages] [Bug 1367817] Re: Revert icon to previous 'envelope' design
** Branch linked: lp:ubuntu/ubuntu-themes -- 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/1367817 Title: Revert icon to previous 'envelope' design Status in Themes for Ubuntu: In Progress Status in “indicator-messages” package in Ubuntu: In Progress Status in “ubuntu-themes” package in Ubuntu: Fix Released Bug description: The previous 'envelope' icon worked better. UX Testing Finding: All participants associated the icon with an alarm or reminder. They all failed to interact with it when looking for missed calls and unread messages. They had to go to the dialer and messages separately to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1367817/+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 1370735] Re: Failing ServiceTest.ApplicationTest test in PPA
** Branch linked: lp:ubuntu/utopic-proposed/url-dispatcher -- 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/1370735 Title: Failing ServiceTest.ApplicationTest test in PPA Status in URL Dispatcher: Confirmed Status in “url-dispatcher” package in Ubuntu: Fix Released Bug description: Chatting with ted, this test failure unexpected, locally reproducible, and possibly related to the new UAL. https://launchpadlibrarian.net/185144786/buildlog_ubuntu-utopic-i386 .url- dispatcher_0.1%2B14.10.20140905.1%2Balesage01-0ubuntu2_FAILEDTOBUILD.txt.gz I'll let ted set importance, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/url-dispatcher/+bug/1370735/+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
** Branch linked: lp:ubuntu/utopic-proposed/url-dispatcher -- 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: Fix Released Status in Unity Media Scanner Scope: Confirmed Status in QML plugin for Scopes: Invalid Status in “url-dispatcher” package in Ubuntu: Fix Released 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 1362104] Re: Hides the app menu even when the global menu is not available
** Branch linked: lp:ubuntu/utopic-proposed/appmenu-qt5 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1362104 Title: Hides the app menu even when the global menu is not available Status in Ubuntu GNOME Flashback: New Status in “appmenu-qt5” package in Ubuntu: In Progress Bug description: Steps to reproduce: - Install gnome-session-flashback and retext. - Log into the GNOME Flashback (Metacity) session. - Launch ReText. Expected result: ReText window has a menu bar. Got: ReText does not have a menu bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1362104/+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 1365408] Re: Should ship a PNG icon instead of using the theme
This bug was fixed in the package ubuntu-app-launch - 0.4+14.10.20140925-0ubuntu1 --- ubuntu-app-launch (0.4+14.10.20140925-0ubuntu1) utopic; urgency=low [ Martin Pitt ] * Upstart dep updated to trunk [ Ted Gould ] * Upstart dep updated to trunk * Add handling for X-Ubuntu-SymbolicIcon in desktop hook (LP: #1365408) [ CI bot ] * Adjust upstart recommends to upstart-bin (LP: #1351306) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 25 Sep 2014 14:43:28 + ** Changed in: ubuntu-app-launch (Ubuntu) Status: New = Fix Released -- 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/1365408 Title: Should ship a PNG icon instead of using the theme Status in Ubuntu Application Launcher: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “address-book-app” package in Ubuntu: Fix Released Status in “dialer-app” package in Ubuntu: Confirmed Status in “indicator-messages” package in Ubuntu: Fix Released Status in “mediaplayer-app” package in Ubuntu: In Progress Status in “messaging-app” package in Ubuntu: Confirmed Status in “sync-monitor” package in Ubuntu: Invalid Status in “ubuntu-app-launch” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: In Progress Bug description: By design request, all apps, click or not, should ship their own icon as PNG instead of using icons from the theme. Please download the respective icon from http://bazaar.launchpad.net /~ubuntu-art-pkg/ubuntu-themes/trunk/files/head:/suru-icons/apps/256/ and include in your packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1365408/+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 ubuntu-app-launch - 0.4+14.10.20140925-0ubuntu1 --- ubuntu-app-launch (0.4+14.10.20140925-0ubuntu1) utopic; urgency=low [ Martin Pitt ] * Upstart dep updated to trunk [ Ted Gould ] * Upstart dep updated to trunk * Add handling for X-Ubuntu-SymbolicIcon in desktop hook (LP: #1365408) [ CI bot ] * Adjust upstart recommends to upstart-bin (LP: #1351306) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 25 Sep 2014 14:43:28 + ** Changed in: ubuntu-app-launch (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 Unity: Fix Released 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: Fix Released Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Released Status in “ubuntu-app-launch” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released 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/unity/+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 1362104] Re: Hides the app menu even when the global menu is not available
This bug was fixed in the package appmenu-qt5 - 0.3.0+14.10.20140926-0ubuntu1 --- appmenu-qt5 (0.3.0+14.10.20140926-0ubuntu1) utopic; urgency=low [ Dmitry Shachnev ] * Do nothing if AppMenu is not available, or UBUNTU_MENUPROXY is set to 0 or empty string. (LP: #1362104) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 26 Sep 2014 09:04:23 + ** Changed in: appmenu-qt5 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1362104 Title: Hides the app menu even when the global menu is not available Status in Ubuntu GNOME Flashback: New Status in “appmenu-qt5” package in Ubuntu: Fix Released Bug description: Steps to reproduce: - Install gnome-session-flashback and retext. - Log into the GNOME Flashback (Metacity) session. - Launch ReText. Expected result: ReText window has a menu bar. Got: ReText does not have a menu bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1362104/+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 1367920] Re: dialer not brought to foreground when launched from messaging-menu
This seems to be a gerenal issue with the indicators, it can be reproduce with the settings app. -- 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/1367920 Title: dialer not brought to foreground when launched from messaging-menu Status in Dialer app for Ubuntu Touch: Confirmed Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: How to reproduce === 1 - Make sure that you have a missing call/voice mail message on messaging menu 2 - Open dialer app 3 - Open the messaging menu 4 - Click to expand the message 5 - Click on the phone app icon in the top right Expected The messaging menu disappear and the dialer app appears Current == The message is removed but the messaging menu still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1367920/+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 1367916] Re: Phone freezes when trying to active the dialer app from the messaging menu
actually the messaging menu goes away if you lock the phone using the power button. but not ideal... -- 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/1367916 Title: Phone freezes when trying to active the dialer app from the messaging menu Status in The Messaging Menu: New Status in “indicator-messages” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: How to reproduce == 1 - Make sure that you have a missing call/voice message in your messaging indicator 2 - Launch the dialer app 3 - Lock your phone 4 - From the lock screen open the messaging menu 5 - Click to expand the message 6 - Click on the icon in the top right Expected == The dialer app appears with the phone pre-populated Current === The phone freezes and stop to accept any input. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1367916/+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 1367920] Re: dialer not brought to foreground when launched from messaging-menu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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/1367920 Title: dialer not brought to foreground when launched from messaging-menu Status in Dialer app for Ubuntu Touch: Confirmed Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: How to reproduce === 1 - Make sure that you have a missing call/voice mail message on messaging menu 2 - Open dialer app 3 - Open the messaging menu 4 - Click to expand the message 5 - Click on the phone app icon in the top right Expected The messaging menu disappear and the dialer app appears Current == The message is removed but the messaging menu still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1367920/+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 1362307] Re: Tapping on an SMS does not open the messaging app
*** This bug is a duplicate of bug 1367920 *** https://bugs.launchpad.net/bugs/1367920 ** This bug has been marked a duplicate of bug 1367920 dialer not brought to foreground when launched from messaging-menu -- 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/1362307 Title: Tapping on an SMS does not open the messaging app Status in “indicator-messages” package in Ubuntu: New Bug description: Steps: 1. Receive an SMS 2. Pull down the indicator 3. Click on the message in the indicator Effect: Nothing happens Expected: The messaging app opens to the message this is krillin r9 (on rtm branch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1362307/+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 1367920] Re: dialer not brought to foreground when launched from messaging-menu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-messages (Ubuntu) Status: New = Confirmed -- 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/1367920 Title: dialer not brought to foreground when launched from messaging-menu Status in Dialer app for Ubuntu Touch: Confirmed Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: How to reproduce === 1 - Make sure that you have a missing call/voice mail message on messaging menu 2 - Open dialer app 3 - Open the messaging menu 4 - Click to expand the message 5 - Click on the phone app icon in the top right Expected The messaging menu disappear and the dialer app appears Current == The message is removed but the messaging menu still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1367920/+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 1363630] Re: Since revision 446.1.3, Zenity backend is broken
** Changed in: ubuntu-gnome-flashback Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to exit_status != 0. Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** Also affects: dbus (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: hud (Ubuntu) Status: Confirmed = Fix Released ** Also affects: ubuntu-touch-session (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: New = Confirmed ** Changed in: dbus (Ubuntu RTM) Status: New = Confirmed ** Changed in: dbus (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: ubuntu-touch-session (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “dbus” package in Ubuntu RTM: Confirmed Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1374451] [NEW] Unintended slow keys looks like bug
Public bug reported: This is more of a feature than a bug... If slow keys gets turned on somehow and the user is not aware of this, it can look like the keyboard is not working. I spent days (10?) with the consultation of my local Ubuntu folks before someone finally thought of slow keys. One suggestion was to reinstall Ubuntu, fortunately I resisted this long enough to learn of slow keys. This has been my most frustrating problem with Ubuntu (since 6.06) It appears that in normal use, the chance of holding down a key long enough that it is accepted when one is not aware of slow keys is very small so it just looks like the keyboard input is not being accepted. There are a few other instances of this problem on the web but not enough to become a prime suspect easily. I dont know how slow keys got turned on. I suggest having a box appear at bootup that reminds the user: Universal Access Typing Slow Keys is active. Hold keys down to get input accepted. Fred 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 x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Sep 26 08:05:58 2014 InstallationDate: Installed on 2014-08-19 (37 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1374451 Title: Unintended slow keys looks like bug Status in “unity” package in Ubuntu: New Bug description: This is more of a feature than a bug... If slow keys gets turned on somehow and the user is not aware of this, it can look like the keyboard is not working. I spent days (10?) with the consultation of my local Ubuntu folks before someone finally thought of slow keys. One suggestion was to reinstall Ubuntu, fortunately I resisted this long enough to learn of slow keys. This has been my most frustrating problem with Ubuntu (since 6.06) It appears that in normal use, the chance of holding down a key long enough that it is accepted when one is not aware of slow keys is very small so it just looks like the keyboard input is not being accepted. There are a few other instances of this problem on the web but not enough to become a prime suspect easily. I dont know how slow keys got turned on. I suggest having a box appear at bootup that reminds the user: Universal Access Typing Slow Keys is active. Hold keys down to get input accepted. Fred 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 x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Sep 26 08:05:58 2014 InstallationDate: Installed on 2014-08-19 (37 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash 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/1374451/+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 1358745] Re: Screen lock has no place to type in a password
I have the same issue, i did a 1314 upgrade then did a fresh install of 14, still getting it. -- 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/1358745 Title: Screen lock has no place to type in a password Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1358745/+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 1358745] Re: Screen lock has no place to type in a password
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1374466 -- 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/1358745 Title: Screen lock has no place to type in a password Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1358745/+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 1374301] Re: osd notifications blurry
** Tags added: trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: New Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+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 1374502] [NEW] Files scope gone in utopic?!
Public bug reported: I am not able to search for files using the dash anymore. This is the only thing I use the dash for frequently... ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: utopic -- 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/1374502 Title: Files scope gone in utopic?! Status in “unity” package in Ubuntu: New Bug description: I am not able to search for files using the dash anymore. This is the only thing I use the dash for frequently... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374502/+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 1363421] Re: Unity Doesn't Start on 14.10 System
Rebuild the 14.10 Unity system using the Final Beta and continue to have the problem of a desktop with no Unity launch bar or Ubuntu banner (top line). The Gnome boot problem has been resolved, the correction did not effect the Unity boot problem. -- 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/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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 1374517] [NEW] Back Forward buttons don't rewind or fast-forward, respectively, the track for however long they are pushed
Public bug reported: According to specifications https://wiki.ubuntu.com/Sound#Playback_item: - If a track is currently playing, the Back button should rewind the track for however long it is pushed. - If a track is currently playing, the Forward button should fast-forward the track for however long it is pushed. That doesn't happen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 26 17:44:39 2014 InstallationDate: Installed on 2014-06-07 (111 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.indicator.sound.desktop: 2014-06-07T15:18:04.803967 ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1374517 Title: Back Forward buttons don't rewind or fast-forward, respectively, the track for however long they are pushed Status in “indicator-sound” package in Ubuntu: New Bug description: According to specifications https://wiki.ubuntu.com/Sound#Playback_item: - If a track is currently playing, the Back button should rewind the track for however long it is pushed. - If a track is currently playing, the Forward button should fast-forward the track for however long it is pushed. That doesn't happen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 26 17:44:39 2014 InstallationDate: Installed on 2014-06-07 (111 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.indicator.sound.desktop: 2014-06-07T15:18:04.803967 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1374517/+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 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled
** Tags added: touch-2014-10-02 ** Changed in: urfkill (Ubuntu) Importance: High = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1296114 Title: Bluetooth is always enabled after reboot even if it was disabled Status in Bluetooth Menu: Invalid Status in “indicator-bluetooth” package in Ubuntu: Invalid Status in “rfkill” package in Ubuntu: Triaged Status in “urfkill” package in Ubuntu: In Progress Bug description: If bluetooth was disabled using the switcher in the bluetooth indicator, after reboot it becomes enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 22 22:34:52 2014 InstallationDate: Installed on 2014-01-27 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: Connecting to session manager To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled
** Changed in: urfkill (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1296114 Title: Bluetooth is always enabled after reboot even if it was disabled Status in Bluetooth Menu: Invalid Status in “indicator-bluetooth” package in Ubuntu: Invalid Status in “rfkill” package in Ubuntu: Triaged Status in “urfkill” package in Ubuntu: In Progress Bug description: If bluetooth was disabled using the switcher in the bluetooth indicator, after reboot it becomes enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 22 22:34:52 2014 InstallationDate: Installed on 2014-01-27 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: Connecting to session manager To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
This bug was fixed in the package ubuntu-touch-session - 0.108+14.10.20140926.1-0ubuntu1 --- ubuntu-touch-session (0.108+14.10.20140926.1-0ubuntu1) utopic; urgency=low [ Oliver Grawert ] * 'move to new dbus-session address handling in XDG_RUNTIME_DIR (LP: #1316978) (LP: #1316978) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 26 Sep 2014 14:45:01 + -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “dbus” package in Ubuntu RTM: Fix Released Status in “ubuntu-touch-session” package in Ubuntu RTM: Fix Released Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
This bug was fixed in the package dbus - 1.6.18-0ubuntu11 --- dbus (1.6.18-0ubuntu11) 14.09; urgency=medium * write to $XDG_RUNTIME_DIR instead of the users home when creating the dbus-session file, so we can start our session even with 100% filled or readonly home dir (LP: #1316978) -- Oliver Grawert o...@ubuntu.com Fri, 26 Sep 2014 14:18:38 +0200 ** Changed in: dbus (Ubuntu RTM) Status: Confirmed = Fix Released ** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “dbus” package in Ubuntu RTM: Fix Released Status in “ubuntu-touch-session” package in Ubuntu RTM: Fix Released Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1358830] Re: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings
** Tags added: qa-daily-testing rtm-14 ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Confirmed ** Changed in: indicator-bluetooth (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1358830 Title: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: Summary: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings steps: 1. Open system settings 2. Go to bluetooth page 3. Disable and enable bluetooth 4. Pull down bluetooth indicator Expected results: Bluetooth indicator has widgets on it Actual results: Indicator is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1358830/+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 1374301] Re: osd notifications blurry
Here's a picture of the issue while this notification from Spotify, the issue occurs on all notifications, including system ones ** Attachment added: Workspace 1_004.png https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+attachment/4216306/+files/Workspace%201_004.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: New Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+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 1358830] Re: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings
*** This bug is a duplicate of bug 1369866 *** https://bugs.launchpad.net/bugs/1369866 ** This bug has been marked a duplicate of private bug 1369866 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1358830 Title: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: Summary: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings steps: 1. Open system settings 2. Go to bluetooth page 3. Disable and enable bluetooth 4. Pull down bluetooth indicator Expected results: Bluetooth indicator has widgets on it Actual results: Indicator is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1358830/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** Branch linked: lp:ubuntu/utopic-proposed/ubuntu-touch-session -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “dbus” package in Ubuntu RTM: Fix Released Status in “ubuntu-touch-session” package in Ubuntu RTM: Fix Released Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
This bug was fixed in the package ubuntu-touch-session - 0.108+14.10.20140926.1-0ubuntu1 --- ubuntu-touch-session (0.108+14.10.20140926.1-0ubuntu1) utopic; urgency=low [ Oliver Grawert ] * 'move to new dbus-session address handling in XDG_RUNTIME_DIR (LP: #1316978) (LP: #1316978) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 26 Sep 2014 14:45:01 + ** Changed in: ubuntu-touch-session (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu RTM: Fix Released Status in “ubuntu-touch-session” package in Ubuntu RTM: Fix Released Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1374566] [NEW] The new bash patch causes lxc-clone and tar to create huge copy of var/log/lastlog
Public bug reported: The new bash patch causes lxc-clone to create a huge copy. Same thing happens with tar. To resolve, I have to remove /var/log/lastlog before copying or cloning. ** Affects: unity-2d (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/1374566 Title: The new bash patch causes lxc-clone and tar to create huge copy of var/log/lastlog Status in “unity-2d” package in Ubuntu: New Bug description: The new bash patch causes lxc-clone to create a huge copy. Same thing happens with tar. To resolve, I have to remove /var/log/lastlog before copying or cloning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/1374566/+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 1363421] Re: Unity Doesn't Start on 14.10 System
The symptom you're describing is of Compiz not running. There isn't enough additional information reported to tell us why, though. Let's start with this: try running '/usr/lib/nux/unity_support_test --print --display :0' and attach the output to this bug. That program determines if there is appropriate hardware support for running Unity (and some driver updates have been known to cause problems by misreporting their capabilities recently). Another thing is to look for the Unity log file. If the file ~/.cache/upstart/unity7.log exists, could you please also attach that to this bug. ** Changed in: unity (Ubuntu) Status: New = Incomplete ** Changed in: unity Status: New = Incomplete -- 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/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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 1358340] Re: [Indicators] Complete greeter profiles
** Branch linked: lp:~ted/indicator-sound/lp1358340-greeter-data -- 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, dx-packages https://bugs.launchpad.net/bugs/1358340 Title: [Indicators] Complete greeter profiles Status in The Date and Time Indicator: Confirmed Status in The Messaging Menu: In Progress Status in Sound Menu: Confirmed Status in Transfer Indicator: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Fix Released Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: A recent change in the interest of security removed access to the indicators when the phone is locked and the greeter is showing. This was an accentual change based on a misunderstanding There had been a plan to support media playback control via the sound indicator. Without this the user must unlock the phone in order to simply pause the music or change songs, etc. Desired resolution: - Revert the change that caused this issue - Add a switch to System Settings to enable security conscious user to switch off Launcher and Greeter access while the phone is locked. This setting should *always* be off by default. https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1363421] Re: Unity Doesn't Start on 14.10 System
Booted the Unity load, desktop opened with no Unity Launch bar and no Ubuntu banner. Opened an xterm and ran the unity_support_test, output below. Attaching the unity7.log associated with this boot. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) G41 OpenGL version string: 2.1 Mesa 10.2.6 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: yes ** Attachment added: Unity7.log https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1363421/+attachment/4216500/+files/unity7.log -- 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/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
This bug was fixed in the package dbus - 1.8.8-1ubuntu2 --- dbus (1.8.8-1ubuntu2) utopic; urgency=medium * write to $XDG_RUNTIME_DIR instead of the users home when creating the dbus-session file, so we can start our session even with 100% filled or readonly home dir (LP: #1316978) -- Oliver Grawert o...@ubuntu.com Fri, 26 Sep 2014 15:07:05 +0200 ** Changed in: dbus (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Fix Released Status in “hud” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu RTM: Fix Released Status in “ubuntu-touch-session” package in Ubuntu RTM: Fix Released Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1363421] Re: Unity Doesn't Start on 14.10 System
This is looking like a duplicate of bug #1357746. Could you please attach a copy of your /var/log/dmesg to this bug? -- 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/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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 1374652] [NEW] unity-schemas fail to install, missinng declaration replaces libunity-core
Public bug reported: dpkg: error processing archive /var/cache/apt/archives/unity-schemas_7.3.1+14.10.20140915-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml', which is also in package libunity-core-6.0-9 7.3.0+14.10.20140711-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-schemas (not installed) 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Sep 27 00:29:31 2014 InstallationDate: Installed on 2013-08-29 (393 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829) SourcePackage: unity SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug utopic ** Changed in: unity (Ubuntu) Importance: Undecided = High -- 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/1374652 Title: unity-schemas fail to install, missinng declaration replaces libunity- core Status in “unity” package in Ubuntu: New Bug description: dpkg: error processing archive /var/cache/apt/archives/unity-schemas_7.3.1+14.10.20140915-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml', which is also in package libunity-core-6.0-9 7.3.0+14.10.20140711-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-schemas (not installed) 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Sep 27 00:29:31 2014 InstallationDate: Installed on 2013-08-29 (393 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829) SourcePackage: unity SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374652/+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
** Branch linked: lp:ubuntu/utopic-proposed/unity8 -- 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 “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress 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/ubuntu/+source/indicator-messages/+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 1363421] Re: Unity Doesn't Start on 14.10 System
** Attachment added: /var/log/dmsg.log https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1363421/+attachment/4216715/+files/dmesg -- 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/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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
This bug was fixed in the package unity8 - 8.00+14.10.20140926-0ubuntu1 --- unity8 (8.00+14.10.20140926-0ubuntu1) utopic; urgency=low [ CI bot ] * Resync trunk [ Nick Dedekind ] * Visual changes for indicator RTM polishing (LP: #1329289) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 26 Sep 2014 19:12:39 + ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- 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 “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released 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/ubuntu/+source/indicator-messages/+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 1363421] Re: Unity Doesn't Start on 14.10 System
Looked at the description of 1357746 which indicates problem caused by the latest level of xserver-xorg-video-intel. The boot hang on black screen forum entry (see Ubuntu Development Version) I had with Gnome also involved the same component. In trying to debug the Gnome failure it was recommended to go to an earlier level of xserver-xorg-video- intel. The only way I knew to do this was to copy the executable files (/usr/lib/xorg/modules/drivers/intel_drv.so, /usr/lib/libI810XvMC.so.1.0.0, and /usr/lib/libIntelXvMC.so.1.0.0) from my working 14.04 system to the failing 14.10 Gnome system. When I booded the modified 14.10 system it came up and ran with only a minor screen refresh slowness. Since this fixed the Gnome system I tried it on the Unity system but unless I did something wrong it made no difference. The interesting thing was when I backed off the changes in the Gnome system (replaced the 3 original modules) the system continued to boot OK without any screen refresh slowness. -- 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/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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 814833] Re: Opening the dash is very slow and laggy
+1 for what Guillaume F said in comment #45. Sometimes the dash takes so long to populate that it tells me Sorry, there is nothing that matches your search, even though I know there are matches. And at random times it resets the search filters to include Files and Folders - I turn this off as soon as it happens, as it is too slow to complete searching when this is turned on. Is that relevant to this bug, though, or is this bug only about the intial delay in drawing the dash? I only find it is very slow to draw the dash if the system runs out of RAM and starts swapping to disk. -- 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/814833 Title: Opening the dash is very slow and laggy Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When I was running off a usb drive at least, opening of the app/files dash lagged a second or two behind the actual clicking of the logo button. Just a minor thing, but was hard to ignore it To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/814833/+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 1374681] [NEW] Nemo freezes under root account when open dirs with a lot of subdirs and files.
Public bug reported: Nemo freezes under root account when open dirs with a lot of subdirs and files. For example, /usr/share/. ProblemType: Crash Architecture: x86_64 Description: Ubuntu 14.04.1 LTS Release: 14.04 nemo: Installed: 2.2.4-3~webupd8~trusty0 Candidate: 2.2.4-3~webupd8~trusty0 Version table: *** 2.2.4-3~webupd8~trusty0 0 500 http://ppa.launchpad.net/webupd8team/nemo/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 2.2.2-b~trusty~NoobsLab.com 0 500 http://ppa.launchpad.net/noobslab/mint/ubuntu/ trusty/main amd64 Packages 1.8.4-1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 1.8.4-1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages ** Affects: libcompizconfig (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libcompizconfig in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374681 Title: Nemo freezes under root account when open dirs with a lot of subdirs and files. Status in “libcompizconfig” package in Ubuntu: New Bug description: Nemo freezes under root account when open dirs with a lot of subdirs and files. For example, /usr/share/. ProblemType: Crash Architecture: x86_64 Description: Ubuntu 14.04.1 LTS Release: 14.04 nemo: Installed: 2.2.4-3~webupd8~trusty0 Candidate: 2.2.4-3~webupd8~trusty0 Version table: *** 2.2.4-3~webupd8~trusty0 0 500 http://ppa.launchpad.net/webupd8team/nemo/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 2.2.2-b~trusty~NoobsLab.com 0 500 http://ppa.launchpad.net/noobslab/mint/ubuntu/ trusty/main amd64 Packages 1.8.4-1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 1.8.4-1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcompizconfig/+bug/1374681/+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 1306608] Re: Unity global menu delays actions in a gtk2 app
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- 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/1306608 Title: Unity global menu delays actions in a gtk2 app Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: There is a problem with this global menu from Unity, it delays actions/things i do in the menu. It seems that the information from menu is not send to the app. Using vba-m gtk, i can not load saved games until I move the emulator window. Take a look at the video. Step to reproduce: - Opens the vba-m emulator - Load a ROM - Save State in some time - Try to Load State (Emulation Load State Most Recent), you will notice that it will not work - Move the emulator window to other place, you will that after you drop the window, the emulator will load the saved state Or: - Opens the vba-m emulator - Load a ROM - Save State in some time - Try to Load State, you will notice that it will not work - Click in global menu, the menu drops down, and click again to close it, the emulator will load the saved state after this action Or: - Opens the vba-m emulator - Load a ROM - Save State in some time - Try to Load State, you will notice that it will not work - Change to other window (lost focus from vbam), and returns to the emulator window,it will load the saved state after this action http://youtu.be/Pwq_7_7oLPk If i disable the global menu, to use the old gtk2 menu, it works fine (env UBUNTU_MENUPROXY=0 gvbam). This emulator works fine in others desktops, like xfce, mate and kde. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CasperVersion: 1.340 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Apr 11 15:11:04 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140411) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1306608/+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 1306608] Re: Unity global menu delays actions in a gtk2 app
On running VisualBoyAdvance-M's GTK frontend (vbam-gtk) on Ubuntu 14.04LTS, the menu doesn't respond if a ROM is already loaded and being emulated. I tried with both global menu and LIM, both had the same problem. However, like @sergio-br2 mentioned, menu work with legacy GTK2 menus. Surprisingly, Ubuntu 12.04's Unity 5 has no problem with vbam-gtk's global menu! So, this seems to be a bug that creeped in somewhere between Unity 6 (Ubuntu 12.10) and Unity 7.2 (Ubuntu 14.04LTS). 'vbam' will be replacing 'visualboyadvance' in the Debian repo (See bug #378561 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541157), coz the former is the most actively maintained fork of the latter which is now inactive. Ubuntu 14.04 being an LTS release need to address such usability issues and fix this bug. ** Bug watch added: Debian Bug tracker #541157 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541157 -- 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/1306608 Title: Unity global menu delays actions in a gtk2 app Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: There is a problem with this global menu from Unity, it delays actions/things i do in the menu. It seems that the information from menu is not send to the app. Using vba-m gtk, i can not load saved games until I move the emulator window. Take a look at the video. Step to reproduce: - Opens the vba-m emulator - Load a ROM - Save State in some time - Try to Load State (Emulation Load State Most Recent), you will notice that it will not work - Move the emulator window to other place, you will that after you drop the window, the emulator will load the saved state Or: - Opens the vba-m emulator - Load a ROM - Save State in some time - Try to Load State, you will notice that it will not work - Click in global menu, the menu drops down, and click again to close it, the emulator will load the saved state after this action Or: - Opens the vba-m emulator - Load a ROM - Save State in some time - Try to Load State, you will notice that it will not work - Change to other window (lost focus from vbam), and returns to the emulator window,it will load the saved state after this action http://youtu.be/Pwq_7_7oLPk If i disable the global menu, to use the old gtk2 menu, it works fine (env UBUNTU_MENUPROXY=0 gvbam). This emulator works fine in others desktops, like xfce, mate and kde. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CasperVersion: 1.340 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Apr 11 15:11:04 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140411) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1306608/+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
