[Dx-packages] [Bug 1575655] Re: the network indicator shows the wrong status

[Morten Frisch]

Yeah, I'd like to add that this definitely happens after suspend for me

-- 
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 603415] Re: Unity should have a screen magnifier

[Billy]

** Changed in: unity (Ubuntu Xenial)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/603415

Title:
  Unity should have a screen magnifier

Status in Compiz:
  In Progress
Status in Nux:
  Triaged
Status in Unity:
  Triaged
Status in compiz package in Ubuntu:
  In Progress
Status in nux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in compiz source package in Xenial:
  In Progress
Status in nux source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Fix Released

Bug description:
  Binary package hint: gnome-control-center

  In gnome-keybindings-properties, in the Accessibility section, there
  are three entries by default: toggle magnifier, toggle screen reader,
  and toggle on-screen keyboard. None of these work, whether or not
  Assistive Technologies is currently running and whether or not orca is
  currently running.

  WHAT I EXPECT TO HAPPEN: I should be able to configure a shortcut to
  any of these actions, such as Ctrl-Alt-A to the Toggle magnifier
  action. Then, pressing, Ctrl-Alt-A will start the magnifier.

  WHAT ACTUALLY HAPPENS: I am able to modify the entry in the gnome-
  keybindings-properties window, but pressing the designated key does
  not perform any action. That is, the magnifier does not open. Changing
  the hotkeys for other actions works okay.

  WHY THIS IS BAD: This is confusing and misleading behavior, and can be
  especially damaging for people who need the accessibility features.
  Ideally, the keybindings should be fixed, but otherwise they should be
  removed from the dialog.

  This is true under up-to-date Lucid 10.04 tested on several systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/603415/+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 1573639] Re: ownCloud Client system tray icon integration broken

[Launchpad Bug Tracker]

This bug was fixed in the package owncloud-client - 2.1.1+dfsg-
1ubuntu1.1

---
owncloud-client (2.1.1+dfsg-1ubuntu1.1) xenial; urgency=medium

  * workaround-systemtray-bug.diff: Don't call isSystemTrayAvailable, it
hides the systemtray. (LP: #1573639)

 -- Timo Aaltonen   Thu, 28 Apr 2016 20:30:38 +0300

** Changed in: owncloud-client (Ubuntu Xenial)
   Status: Fix Committed => 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/1573639

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Released
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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 1573639] Update Released

[Chris J Arges]

The verification of the Stable Release Update for owncloud-client has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1573639

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Released
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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 1573639] Re: ownCloud Client system tray icon integration broken

[Launchpad Bug Tracker]

** Branch linked: lp:~mitya57/appmenu-qt5/lp1574699

-- 
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/1573639

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Committed
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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 1573639] Re: ownCloud Client system tray icon integration broken

[Timo Aaltonen]

don't close bugs manually, the package hasn't transitioned to -updates
yet

** Changed in: owncloud-client (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

-- 
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/1573639

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Committed
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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

[Sebastien Bacher]

Did compiz/unity change there, or is there some video driver issue when
makes the screen config change when monitors go to suspend mode which
was not the case before?

-- 
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:
  Confirmed
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 1573115] Re: No Speakers Sound in Ubuntu 16.04

[Ferruccio]

Same bug affects Asus EeePC 1015px

-- 
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/1573115

Title:
  No Speakers Sound in Ubuntu 16.04

Status in compiz-plugins-main package in Ubuntu:
  Confirmed

Bug description:
  I recently installed Ubuntu 16.04 and I'm having a problem with my audio 
device.
  *The internal mic is working properly
  *The external output (headphones) is working properly too.
  *But the internal speakers doesn't work.

  I tried on the live version of 16.04 and I had the same issue.

  Information of my laptop:

  lspci  -v:

  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Dell 6 Series/C200 Series Chipset Family High Definition 
Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 39
Memory at f7f0 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  aplay -l:

   Lista de PLAYBACK dispositivos hardware 
  tarjeta 0: PCH [HDA Intel PCH], dispositivo 0: Generic Analog [Generic Analog]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
  tarjeta 0: PCH [HDA Intel PCH], dispositivo 3: Generic Digital [Generic 
Digital]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0

  Attached you can see the alsamixer configuration which shows the
  speaker volume. In capture view the audio is also in 100%

  I have no idea how to solve it. I used the same laptop with 14.04LTS
  without this problem.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1573115/+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

[Manthis]

I'm encountering the same issue and this is clearly driving me nuts as I
can't figure out why all my windows are systematically moved to my left
screen when unlocking my computer. As others, I confirm that it seems to
happen when screens go in sleep mode and wake up.

-- 
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:
  Confirmed
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 1579837] Re: Issue after wizard with policykit

[Jean-Baptiste Lallement]

removed the blocker tags and retarget to OTA12. The package has been
unseeded which temporarily fixes the issue for OTA11

** Tags removed: lt-blocker regression-proposed

** Changed in: canonical-devices-system-image
Milestone: 11 => 12

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1579837

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579837/+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