[Dx-packages] [Bug 1013386] Re: unity 2d dash doesn't open office files
*** This bug is a duplicate of bug 1002710 *** https://bugs.launchpad.net/bugs/1002710 ** Changed in: unity-2d (Ubuntu) Status: Confirmed => Fix Released -- 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/1013386 Title: unity 2d dash doesn't open office files Status in unity-2d package in Ubuntu: Fix Released Bug description: When i click within the dash - either on the home lens, or on the files lens on a LibreOffice type of file (.doc file, in this case) - the file doesn't open. Opening the file from within Nautilus works fine. Within Unity-3d this does NOT occur. Everything works flawlessly in this matter. cheers ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu8 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: Thu Jun 14 23:25:34 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) 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-2d/+bug/1013386/+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 992717] Re: Opening files from the Dash randomly doesn't work
*** This bug is a duplicate of bug 1002710 *** https://bugs.launchpad.net/bugs/1002710 ** Changed in: unity-2d (Ubuntu) Status: Confirmed => Fix Released -- 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/992717 Title: Opening files from the Dash randomly doesn't work Status in unity-2d package in Ubuntu: Fix Released Bug description: My problem is really simple: if I click on a file in the dash (either an exact search result or a recent file), sometimes nothing happens. But in some cases, it works. I can't say that it has a problem with file types - for example, I can open a .jpeg file that's on my desktop, but neither can I open a .JPG that's in my pictures folder, nor one that's on an external HDD, nor one that's _also_ on the desktop. This problem doesn't come up when using 3D unity. If needed, I can try a live cd/fresh install, but my network connection is really slow so I would only do that if that's the only solution. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 5.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Tue May 1 18:34:14 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120112) PackageArchitecture: all SourcePackage: unity-2d UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/992717/+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 1665471] Re: unknown, auto pop-up ????
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1665471/+attachment/4820457/+files/CoreDump.gz -- 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/1665471 Title: unknown, auto pop-up Status in hud package in Ubuntu: New Bug description: The message states problem with 17.04, we're not even there yet. This 16.10 version loaded corrupt from the beginning, can't find how to get around it. The initial download came up with a green screen, blew out all OS capability. Found a server version from the UK, it loaded OK. I'm not real savay with terminal applications, however, I got it to work. I would simply like to have a 'stable' OS, like it's always been until this time. Any suggestion would be appreciated. I have desktop on my other machine, but CD writer is missing, and I can't install one. Seems that any download OS I try won't install properly, and I don't know why. I'm waiting for 17.04, but in the meantime, it's very frustrating..and your help 'forums' don'tActually this is even the first time the 'send report' thing has actually worked...I've not had any problems with any version until this. I'm considering downloading 16.04 and starting over, but I'd rather not have to do all that work, as I'm just a 'casual user, and 'basic' OS works just fine for me. Any information, suggestions, etc., would be greatly appreciated...Thank you.. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic i686 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Feb 16 13:27:43 2017 ExecutablePath: /usr/lib/i386-linux-gnu/hud/hud-service InstallationDate: Installed on 2016-12-22 (55 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) ProcCmdline: /usr/lib/i386-linux-gnu/hud/hud-service ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0xb7730a74:mov$0xa7,%ah PC (0xb7730a74) in non-executable VMA region: 0xb773-0xb7731000 rw-p /lib/i386-linux-gnu/ld-2.24.so source "$0xa7" ok destination "%ah" ok SegvReason: executing writable VMA /lib/i386-linux-gnu/ld-2.24.so Signal: 11 SourcePackage: hud Stacktrace: #0 0xb7730a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceTop: ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: Upgraded to zesty on 2016-12-23 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1665471/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Branch linked: lp:~ci-train-bot/sni-qt/sni-qt-ubuntu-xenial-2488.1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Branch linked: lp:~ci-train-bot/sni-qt/sni-qt-ubuntu-zesty-2488 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Description changed: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml - in any folder you want + in any folder you want * Run: - - snapcraft prime - - sudo snap try prime - - snap run qt5-systray + - snapcraft prime + - sudo snap try prime + - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible + + + + SRU bug for sni-qt: + + [Impact] + + Indicator icons pointing to a position inside the snap aren't properly + found by unity, that shows a "missing icon" emblem + + [Test case] + + * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml + in any folder you want + * Run: + - snapcraft prime + - sudo snap try prime + - snap run qt4-systray + + An indicator should open, with the proper icon showin. From the window + you can change the icon type, and all the types should work. + + When snaps are generated in non updated systems, the icons (except the + Themed one) will be still missing. + + [Regression potential] + + If $SNAP env variable is defined for an app not running in snap + confinement the icons couldn't be properly visible -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this
[Dx-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Branch linked: lp:~3v1n0/sni-qt/xenial-sru1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Description changed: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible + + + + SRU bug for appmenu-qt5: + + [Impact] + + Indicator icons pointing to a position inside the snap aren't properly + found by unity, that shows a "missing icon" emblem + + [Test case] + + * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml + in any folder you want + * Run: + - snapcraft prime + - sudo snap try prime + - snap run qt5-systray + + An indicator should open, with the proper icon showin. From the window + you can change the icon type, and all the types should work. + + When snaps are generated in non updated systems, the icons (except the + Themed one) will be still missing. + + [Regression potential] + + If $SNAP env variable is defined for an app not running in snap + confinement the icons couldn't be properly visible -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: -
[Dx-packages] [Bug 1665471] Re: unknown, auto pop-up ????
** Information type changed from Private Security to Public -- 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/1665471 Title: unknown, auto pop-up Status in hud package in Ubuntu: New Bug description: The message states problem with 17.04, we're not even there yet. This 16.10 version loaded corrupt from the beginning, can't find how to get around it. The initial download came up with a green screen, blew out all OS capability. Found a server version from the UK, it loaded OK. I'm not real savay with terminal applications, however, I got it to work. I would simply like to have a 'stable' OS, like it's always been until this time. Any suggestion would be appreciated. I have desktop on my other machine, but CD writer is missing, and I can't install one. Seems that any download OS I try won't install properly, and I don't know why. I'm waiting for 17.04, but in the meantime, it's very frustrating..and your help 'forums' don'tActually this is even the first time the 'send report' thing has actually worked...I've not had any problems with any version until this. I'm considering downloading 16.04 and starting over, but I'd rather not have to do all that work, as I'm just a 'casual user, and 'basic' OS works just fine for me. Any information, suggestions, etc., would be greatly appreciated...Thank you.. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic i686 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Feb 16 13:27:43 2017 ExecutablePath: /usr/lib/i386-linux-gnu/hud/hud-service InstallationDate: Installed on 2016-12-22 (55 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) ProcCmdline: /usr/lib/i386-linux-gnu/hud/hud-service ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0xb7730a74:mov$0xa7,%ah PC (0xb7730a74) in non-executable VMA region: 0xb773-0xb7731000 rw-p /lib/i386-linux-gnu/ld-2.24.so source "$0xa7" ok destination "%ah" ok SegvReason: executing writable VMA /lib/i386-linux-gnu/ld-2.24.so Signal: 11 SourcePackage: hud Stacktrace: #0 0xb7730a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceTop: ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: Upgraded to zesty on 2016-12-23 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1665471/+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 1665422] Re: unity-scope-loader crashed with SIGSEGV in malloc_consolidate()
*** This bug is a duplicate of bug 1624683 *** https://bugs.launchpad.net/bugs/1624683 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 #1624683, 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/1665422/+attachment/4820358/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1665422/+attachment/4820360/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1665422/+attachment/4820363/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1665422/+attachment/4820364/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1665422/+attachment/4820365/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1665422/+attachment/4820366/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1665422/+attachment/4820367/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1624683 ** 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 libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1665422 Title: unity-scope-loader crashed with SIGSEGV in malloc_consolidate() Status in libunity package in Ubuntu: New Bug description: Install winehq and have come this issue ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: libunity9 7.1.4+16.10.20160516-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 16 20:05:53 2017 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2017-02-16 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170216) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope SegvAnalysis: Segfault happened at: 0x7f7e00d83ea1 <malloc_consolidate+321>: mov 0x10(%rbx),%r10 PC (0x7f7e00d83ea1) ok source "0x10(%rbx)" (0x96a0ee8c2105e95e) not located in a known VMA region (needed readable region)! destination "%r10" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: malloc_consolidate (av=av@entry=0x7f7e010c4b00 ) at malloc.c:4210 _int_malloc (av=av@entry=0x7f7e010c4b00 , bytes=bytes@entry=4096) at malloc.c:3485 __GI___libc_malloc (bytes=4096) at malloc.c:2925 g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 Title: unity-scope-loader crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1665422/+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 1575655] Re: the network indicator shows the wrong status
Hi, After testing some more, restarting the networkmanager does fix the issue for me too. However, it doesn't make sense, to me, to restart the whole service to fix this issue. Restarting the applet makes more sense to me. I have found a way to automatically restart nm-applet each time the machine resumes from a suspend. Disclaimer!! ((This is only a (hack/temporary-fix/work-around) as it doesn't address the cause of the issue.)) Short description of solution: I created a script that kills nm-applet at suspend|hibernate, then starts another nm-applet on resume|thaw. Then I placed it in (etc/pm/sleed.d) and named it "90_Restart_nm-applet" and made it executable. Specific steps taken: 1- Download attached script (90_Restart_nm-applet) 2- Open a terminal (Ctrl+Alt+T) 5- type in "sudo nautilus" without the quotations and enter your password. **PLEASE DO NOT DO ANYTHING, OTHER THAN THE FOLLOWING STEPS , IN THIS FILE MANAGER WINDOW (NAUTILUS), INCLUDING DELETING, RENAMING, AND MOVING FILES. IT WILL MESS WITH THE OWNERSHIP OF AND ACCESS TO FILES** <-- headache to track fix. 6- navigate to the downloaded script (90_Restart_nm-applet) and copy it. It is probably in your downloads folder in /Home//Downloads. 7- navigate to /etc/pm/sleep.d 8- paste (90_Restart_nm-applet) there, then right click it, and select properties. 9- go to (Permissions) tab and check (Allow executing file as program). 10- close properties menu and file manager (Nautilus) done. Someone might be able to write terminal commands to do this, I don't know how to. Now the nm-applet should restart whenever the system resumes from a suspend. Few things to note: a- I'm running UBUNTU 16.10 with a UNITY 7.5.0. Kernel... I posted my info in a precious comment... b- Because of (a), the address at which your script to be placed might be different than mine. Do some research. I found mine in an answer by (fader) here: "http://askubuntu.com/questions/92218/how-to-execute-a-command-after-resume-from-suspend; <--- a good place to start. Please keep in mind that this doesn't fix the underlying issue, it is only a work-around. As such, it may create more issues than the one it fixes. Let me know if anymore information is needed, Basem. P.S I have a feeling that I put comment in the wrong format for this website. Let me know how to fix it, Thanks. ** Attachment added: "Kills nm-applet on suspend and starts it on resume" https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+attachment/4820369/+files/90_Restart_nm-applet -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status Status in indicator-applet package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 indicator-applet: Installed: (none) Candidate: 12.10.2+15.04.20141127.2-0ubuntu1 Version table: 12.10.2+15.04.20141127.2-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages The network indicator sometimes shows the icon for wired connections and sometimes claims wifi without connection even though I'm consistently connected over wifi. I don't mean to say that it switches between these two or that always is wrong. But sometimes my connected to wifi symbol changes to wired. Other times it will change to the no connection wifi. The info is correct on boot, but switches over time, possibly after suspension. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-applet (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 27 14:54:42 2016 InstallationDate: Installed on 2016-04-08 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: indicator-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+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 1295267] Re: Windows change Monitor/Desktop after screen lock
Also have this bug, all my windows (except for terminal windows) move to left-most monitor after screen lock and monitors enter stand-by. This however only happens while leaving them longer in stand-by (overnight), during the day, when it may be locked for an hour at most, it doesn't happen. -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+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 1231550] Re: battery status indicator shows 'estimating'
** Branch linked: lp:~unity-api-team/indicator-power/16.04-lp1559731 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1231550 Title: battery status indicator shows 'estimating' Status in indicator-power: New Status in indicator-power package in Ubuntu: Confirmed Bug description: Sometime in saucy my battery icon started showing '(estimating...)' for the 'time' in the menu bar. This could be because I: a.) am plugged into power b.) have used the thinkpad 'tp-smapi-dkms' packages to control my battery, telling it to not charge even though its plugged in I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Thu Sep 26 12:09:50 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (708 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-05-20 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1231550/+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
