[Dx-packages] [Bug 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop
Also had the problem, using Gnome 3 and Ubuntu 14.04. Removing appmenu-qt5 solved the problem. -- 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/1307619 Title: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop Status in LyX - The Document Processor: New Status in appmenu-qt5 package in Ubuntu: Confirmed Bug description: 1. Open Qt Creator Version 3.0.1 at the Gnome3 Desktop 2. Menu bar is missing. workaround -- After Deinstall appmenu-qt5 is the Menu bar working again. Open Terminal: sudo apt-get remove appmenu-qt5 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Mon Apr 14 18:52:18 2014 InstallationDate: Installed on 2014-02-14 (58 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214) SourcePackage: appmenu-qt5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lyx/+bug/1307619/+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 1389336] Re: Use geoclue-2.0
Any progress on this? It's better to finish all porting before 15.10 is released. ** Tags added: wily -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: New Status in qtlocation-opensource-src package in Ubuntu: New Status in ubuntu-geoip package in Ubuntu: New Status in webkitgtk package in Ubuntu: New Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1427566] Re: [Clock] Add timers functionality
** Changed in: ubuntu-ux Assignee: Magdalena Mirowicz (magdalena-mirowicz) = James Mulholland (jamesjosephmulholland) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1427566 Title: [Clock] Add timers functionality Status in The Date and Time Indicator: New Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: Triaged Status in indicator-datetime package in Ubuntu: New Bug description: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1472622] [NEW] Unity doesn't update or freezes contents within application window
Public bug reported: When switching between different application windows there is a chance that the contents of a window just freeze. For me this happens with Firefox quite often, and extremely often when using QtCreator. Once such a window is frozen, scrolling or keyboard input seems to work, but you won't see any effect because the window contents are not updated anymore. You can re-animate such a frozen window again by just resizing it a bit, but it will get stuck again some time later after switching between windows. This bug doesn't happen with openbox or gnome as window manager / compositor. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.76 Thu Jan 22 12:11:08 PST 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jul 8 15:23:19 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8343] InstallationDate: Installed on 2014-03-19 (475 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140319) MachineType: Tarox Prof. Workstation P7Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=403365c1-32ea-4fc9-b389-6a61e48dec7c ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0080 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7Q57-M DO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0080:bd08/02/2011:svnTarox:pnProf.WorkstationP7Q:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7Q57-MDO:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: Prof. Workstation P7Q dmi.product.version: System Version dmi.sys.vendor: Tarox version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Jul 8 12:50:05 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- 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/1472622 Title: Unity doesn't update or freezes contents within application window Status in unity package in Ubuntu: New Bug description: When switching between different application windows there is a chance that the contents of a window just freeze. For me this happens with Firefox quite often, and extremely often when using QtCreator. Once such a window is frozen, scrolling or keyboard input seems to work, but you won't see any effect because the window contents are not updated anymore. You can re-animate such a frozen window again by just resizing it a bit, but it will get stuck again some time later after switching between windows. This bug doesn't happen with openbox or gnome as window manager / compositor. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic
[Dx-packages] [Bug 1390625] Re: mouse cursor gets corrupted
Happens to me in Elementary Freya 0.3. My fix is to lock the screen (SUPER + L) - then unlock.. -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] 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 Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 381416] Re: notify-osd should have a close button
I agree. I know this bug is already closed as Won't Fix because it's working as designed, but I think it's a faulty design. Making the notifications light-weight by giving the user no way to interact with them, even to dismiss them, isn't really light-weight at all. It's more intrusive and difficult to work with. I have no way of getting the notifications out of my way once I've seen them, so they stay there taking up I don't think it helps things at all to simply hold notifications of different priorities or lengths for different lengths of time. A notification should stay visible until a user has had a chance to see it. How long it takes the user to see it depends on else they're doing, and there's no way for either the system nor the application to know what else the user is doing -- are they currently reading something and waiting until they get to the end of a paragraph to glance at the notification, or did they look at it right away? You don't know, and you can't, so err on the side of longer notifications and give them a dismiss button. To point: when I first installed Ubuntu 14.04, one of the first pieces of advice I got was to install a patched version of NotifyOSD that would let you customize notifications (including dismissing them). When that's the advice that people are giving to new users, I think you have a design problem -- 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/381416 Title: notify-osd should have a close button Status in notify-osd package in Ubuntu: Won't Fix Bug description: Binary package hint: notify-osd As simple as that. The new notification system works fine, but it really bugs me that I'm forced to wait for those little messages to fade away by themselves. Should I suggest this somewhere else? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/381416/+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 1471311] Re: Calendar event dates are in wrong time format for other languages in indicator
** Changed in: indicator-datetime (Ubuntu) Assignee: Alejandro J. Cura (alecu) = Charles Kerr (charlesk) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1471311 Title: Calendar event dates are in wrong time format for other languages in indicator Status in the base for Ubuntu mobile products: New Status in indicator-datetime package in Ubuntu: New Bug description: The calendar event dates aren't in the right format. See the attached screenshot, the date should be júl. 11., szo 08.00 instead of this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471311/+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 1437944] Re: brightness resets after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1437944 Title: brightness resets after reboot Status in indicator-datetime package in Ubuntu: Confirmed Bug description: with ubuntu-15.04 beta, the brightness always resets after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1437944/+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 1466760] Re: /usr/lib/arm-linux-gnueabihf/url-dispatcher/url-dispatcher:ubuntu-app-launch-invalid-appid
*** This bug is a duplicate of bug 1352656 *** https://bugs.launchpad.net/bugs/1352656 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: url-dispatcher (Ubuntu) Status: New = Confirmed -- 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/1466760 Title: /usr/lib/arm-linux-gnueabihf/url-dispatcher/url-dispatcher:ubuntu-app- launch-invalid-appid Status in url-dispatcher package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding url-dispatcher. This problem was most recently seen with version 0.1+15.10.20150612-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a436921274341898964fed1c53aab684f0921592 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1466760/+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 1412709] Re: Error: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme'
** Branch linked: lp:~boiko/telephony-service/sync_ota5_fixes -- 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, dx-packages https://bugs.launchpad.net/bugs/1412709 Title: Error: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme' Status in notify-osd package in Ubuntu: Fix Released Status in notify-osd-icons package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: In Progress Status in telephony-service source package in Vivid: New Bug description: I am seeing the following warning with notify-osd when changing the volume: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme' This happens also when running it manually (as in src/send-test- notification.sh): notify-send Volume -i notification-audio-volume-medium -h int:value:75 -h string:x-canonical-private-synchronous: When leaving out the notification- prefix there's no error: notify-send Volume -i audio-volume-medium -h int:value:75 -h string:x-canonical-private-synchronous: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.10.20140819-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 20 10:41:03 2015 DesktopSession: 'ubuntu' GtkTheme: 'Numix' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2012-05-28 (966 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 42992PG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.3-0ubuntu0.2 libdrm2 2.4.56-1~ubuntu1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 SourcePackage: notify-osd UpgradeStatus: Upgraded to trusty on 2015-01-17 (2 days ago) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42992PG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42992PG dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1412709/+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 1455520] Re: systemd-shim executes 'poweroff' after resuming from suspend-to-memory(S3)
I have same behavior on debian jessie
it's occurs only where resume from ram..but not if resume from disk (hibernate)
i try to insolae the problem. i start with mate-power-manager (from
mate-desktop):
https://github.com/mate-desktop/mate-power-manager/issues/140
But seems that it's not their fault
i think that when resume pressing the powerbutton , its wakeup the
machine but also send the poweroff event that poweroff the machine after
20 or 30 seconds.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1455520
Title:
systemd-shim executes 'poweroff' after resuming from suspend-to-
memory(S3)
Status in systemd-shim package in Ubuntu:
New
Bug description:
Hi,all
I'm using latest kernel 4.1-rc3 on ubuntu 14.04.2 LTS X86_64,
and I found that, after resuming from suspend-to-memory,
the systemd-shim deamon will execute a 'poweroff', which
shuts the system down.
here's my step to reproduce the bug:
1.echo mem /sys/power/state //ok
2.wait for 30 seconds//ok
3.push power button //ok
4.system resumes automatically //ok
5.after a few seconds, system shutdown //oh no...
I replace /sbin/shutdown with a script that prints the current process
backtrace by pstree, then the system will not halt after resumming
from suspend-to-memory. Here's my script:
# cat /sbin/shutdown
#!/bin/sh
pstree -a /home/chenyu/shutdown_trace.log
and here's the backtrace when system is executing my 'shutdown', after
resumming, we can see that, systemd-shim invokes 'sh -c
/sbin/poweroff':
init
|-ModemManager
| `-2*[{ModemManager}]
|-NetworkManager
| `-3*[{NetworkManager}]
|-acpid -c /etc/acpi/events -s /var/run/acpid.socket
| `-sh -c /etc/acpi/powerbtn.sh
|-anacron -s
|-avahi-daemon
| `-avahi-daemon
|-bluetoothd
|-cron
|-cups-browsed
|-cupsd -f
| `-dbus dbus://
|-dbus-daemon --system --fork
|-getty -8 38400 tty4
|-getty -8 38400 tty5
|-getty -8 38400 tty2
|-getty -8 38400 tty3
|-getty -8 38400 tty6
|-irqbalance
|-kerneloops
|-login --
| `-bash
| `-sudo -s
| `-bash
|-ondemand /etc/init.d/ondemand background
| `-sleep 60
|-polkitd --no-debug
| `-2*[{polkitd}]
|-rsyslogd
| `-3*[{rsyslogd}]
|-sshd -D
|-systemd-logind
|-systemd-shim
| |-sh -c /sbin/poweroff
| | `-shutdown /sbin/shutdown -h -P now
| | `-pstree -a
| `-2*[{systemd-shim}]
|-systemd-udevd --daemon
| |-systemd-udevd --daemon
| |-systemd-udevd --daemon
| |-systemd-udevd --daemon
| |-systemd-udevd --daemon
| |-systemd-udevd --daemon
| |-systemd-udevd --daemon
| |-systemd-udevd --daemon
| |-systemd-udevd --daemon
| `-systemd-udevd --daemon
|-upstart-file-br --daemon
|-upstart-socket- --daemon
|-upstart-udev-br --daemon
`-whoopsie
`-2*[{whoopsie}]
Since I'm not sure why systemd-shim act like this, I would be
happy to debug with your suggestion, and give feedback to you.
Best Regards,
Yu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1455520/+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 1461682] Re: [MX4] LED does not notify for incoming notifications
will release on next update. ** Changed in: canonical-devices-system-image Status: In Progress = Fix Committed -- 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/1461682 Title: [MX4] LED does not notify for incoming notifications Status in the base for Ubuntu mobile products: Fix Committed Status in indicator-messages package in Ubuntu: Invalid Status in qtubuntu package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Image r12 The notification LED on the device does not blink when a new SMS arrives. Its always static off. It however does lighten up when the button physical button is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461682/+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 1472826] [NEW] Motif library v4.0.4 causes segfault in legacy app
Public bug reported: Our group develops an X application that uses the Motif Library (package libxm4 v2.3.4-5). It appears that in the latest version of libXm.4.0.4 on Trusty (14.04), on certain types of X events, it causes a segfault. I've isolated this to a particular version of the library and OS rev. Our application works fine for OS older than 14.04, ie 12.04 etc. I also confirmed the version issue by copying libXm.4.0.3 from a 12.04 machine onto a 14.04 machine and it allows the program to work normally. I basically copied libXm.4.0.3 from a 12.04 machine to the 14.04 machine and created a symlink to it: ln -s /usr/lib/x86_64-linux-gnu/libXm.4.0.3 /usr/lib/x86_64-linux-gnu/libXm.4.0.4 So, whatever has changed between 4.0.3 and 4.0.4 has broken some API calls. It's hard for us to debug this from the application side b/c it generates a segfault, which causes the application to crash. Example of what causes the crash. When our application generates a child window which has text field widgets like a text field or textarea, typing into the field causes this crash. Any ideas on why the new version would cause these crashes? Looking at the release notes (/usr/share/doc/libmotif-dev/RELNOTES.gz), I see there were a number of bug fixes. Is it possible one of these fixes caused another bug? Thanks in advance. Quang ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1472826 Title: Motif library v4.0.4 causes segfault in legacy app Status in unity package in Ubuntu: New Bug description: Our group develops an X application that uses the Motif Library (package libxm4 v2.3.4-5). It appears that in the latest version of libXm.4.0.4 on Trusty (14.04), on certain types of X events, it causes a segfault. I've isolated this to a particular version of the library and OS rev. Our application works fine for OS older than 14.04, ie 12.04 etc. I also confirmed the version issue by copying libXm.4.0.3 from a 12.04 machine onto a 14.04 machine and it allows the program to work normally. I basically copied libXm.4.0.3 from a 12.04 machine to the 14.04 machine and created a symlink to it: ln -s /usr/lib/x86_64-linux-gnu/libXm.4.0.3 /usr/lib/x86_64-linux-gnu/libXm.4.0.4 So, whatever has changed between 4.0.3 and 4.0.4 has broken some API calls. It's hard for us to debug this from the application side b/c it generates a segfault, which causes the application to crash. Example of what causes the crash. When our application generates a child window which has text field widgets like a text field or textarea, typing into the field causes this crash. Any ideas on why the new version would cause these crashes? Looking at the release notes (/usr/share/doc/libmotif-dev/RELNOTES.gz), I see there were a number of bug fixes. Is it possible one of these fixes caused another bug? Thanks in advance. Quang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1472826/+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 160311] Re: Resizing windows by grabbing window borders is difficult
Alt + F8 on MATE will activate resize for the currently selected window. ** Changed in: ubuntu-mate Status: New = Opinion -- 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/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in Decorator for compiz-fusion: New Status in One Hundred Papercuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Ubuntu MATE: Opinion Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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
