[Dx-packages] [Bug 465689] Re: Ubuntu Clock Won't Show Year

2013-10-12 Thread Bug Watch Updater
** Changed in: gnome-panel
   Status: Confirmed = In Progress

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

Title:
  Ubuntu Clock Won't Show Year

Status in Desktop panel for GNOME:
  In Progress
Status in The Date and Time Indicator:
  Triaged
Status in “gnome-panel” package in Ubuntu:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Triaged

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to show year.

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  https://wiki.ubuntu.com/TimeAndDate#settings: 'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked...

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/465689/+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 1238420] Re: window-stack-bridge crashed with SIGSEGV in QVariant::QVariant()

2013-10-12 Thread Tommy Aria Pradana
** Information type changed from Private 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/1238420

Title:
  window-stack-bridge crashed with SIGSEGV in QVariant::QVariant()

Status in “hud” package in Ubuntu:
  New

Bug description:
  happen on 32-bit Saucy Salamander

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: hud 13.10.1+13.10.20131010-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Fri Oct 11 12:19:16 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2013-10-07 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta i386 (20131005)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  SegvAnalysis:
   Segfault happened at: 0xb757a70a _ZN8QVariantC2ERKS_+26:   mov
(%edi),%eax
   PC (0xb757a70a) ok
   source (%edi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: hud
  StacktraceTop:
   QVariant::QVariant(QVariant const) () from 
/usr/lib/i386-linux-gnu/libQt5Core.so.5
   QDBusPendingReplyData::argumentAt(int) const () from 
/usr/lib/i386-linux-gnu/libQt5DBus.so.5
   BamfWindow::BamfWindow(QString const, QDBusConnection const) ()
   BamfWindowStack::addWindow(QString const) ()
   BamfWindowStack::ViewOpened(QString const, QString const) ()
  Title: window-stack-bridge crashed with SIGSEGV in QVariant::QVariant()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.hud.log: (process:1303): hudapplicationlist-WARNING **: Could not get 
window stack: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.canonical.Unity.WindowStack was not provided by any .service files
  upstart.window-stack-bridge.log: Window:  44040198 Desktop has no parents

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1238420/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch

2013-10-12 Thread Steve Langasek
I've also checked this memory usage with valgrind; valgrind doesn't
think there's a leak, at the end of a valgrind session there are only
211,206 bytes possibly lost - nowhere near the many MB that we're
seeing.

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

Title:
  uevent spam causes libdbus client code in session upstart to consume
  massive amounts of memory on Ubuntu Touch

Status in Upstart:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “systemd” source package in Saucy:
  New
Status in “unity” source package in Saucy:
  New
Status in “upstart” source package in Saucy:
  Fix Released

Bug description:
  using ubuntu touch image 82 i see the session init consume about 10MB per 
minute as long as the screen is on  with Mir.
  running the same session with surfaceflinger only consumes 1MB per minute.

  in both cases the system starts to swap heavily at some point, making
  the UI unresponsive.

  http://paste.ubuntu.com/6196223/ has the top output of a Mir session
  after 30min, the UI just got completely unresponsive when this
  snapshot was taken.

  http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
  session where the screen was off for about 10min

  apparently the leak only occurs while the screen is on, it seems to be
  permanently there but in the case of surfaceflinger it hits less hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch

2013-10-12 Thread Steve Langasek
I've tested on a mako device here, and the memory usage is not all due
to a misbehaved client.  I've tracked down all the clients of the
session init; unity8 is the only long-lived client other than the
bridges, and if I kill unity8 and let it respawn, upstart gains back
some of the memory, but *not all*: if I feed events into the session
init, bringing its memory usage up to 93.3MB, and then kill unity8 (and,
in fact,if I go through one-by-one and kill *all* the processes related
to the session), upstart frees *some* memory, but its total usage
remains at 88MB - compared to 5MB when it starts out.

Another thing I've found out, though, is that if I force a re-exec of
the session init with 'telinit u', the memory usage drops down... and
never rises again, even if I spam it with more events.  This suggests a
possible workaround of just re-execing the session init immediately
after startup.  But that probably requires landing a fix for bug
#1238078 first.

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

Title:
  uevent spam causes libdbus client code in session upstart to consume
  massive amounts of memory on Ubuntu Touch

Status in Upstart:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “systemd” source package in Saucy:
  New
Status in “unity” source package in Saucy:
  New
Status in “upstart” source package in Saucy:
  Fix Released

Bug description:
  using ubuntu touch image 82 i see the session init consume about 10MB per 
minute as long as the screen is on  with Mir.
  running the same session with surfaceflinger only consumes 1MB per minute.

  in both cases the system starts to swap heavily at some point, making
  the UI unresponsive.

  http://paste.ubuntu.com/6196223/ has the top output of a Mir session
  after 30min, the UI just got completely unresponsive when this
  snapshot was taken.

  http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
  session where the screen was off for about 10min

  apparently the leak only occurs while the screen is on, it seems to be
  permanently there but in the case of surfaceflinger it hits less hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235649/+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 1238420] Re: window-stack-bridge crashed with SIGSEGV in QVariant::QVariant()

2013-10-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: hud (Ubuntu)
   Status: New = Confirmed

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

Title:
  window-stack-bridge crashed with SIGSEGV in QVariant::QVariant()

Status in “hud” package in Ubuntu:
  Confirmed

Bug description:
  happen on 32-bit Saucy Salamander

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: hud 13.10.1+13.10.20131010-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Fri Oct 11 12:19:16 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2013-10-07 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta i386 (20131005)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  SegvAnalysis:
   Segfault happened at: 0xb757a70a _ZN8QVariantC2ERKS_+26:   mov
(%edi),%eax
   PC (0xb757a70a) ok
   source (%edi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: hud
  StacktraceTop:
   QVariant::QVariant(QVariant const) () from 
/usr/lib/i386-linux-gnu/libQt5Core.so.5
   QDBusPendingReplyData::argumentAt(int) const () from 
/usr/lib/i386-linux-gnu/libQt5DBus.so.5
   BamfWindow::BamfWindow(QString const, QDBusConnection const) ()
   BamfWindowStack::addWindow(QString const) ()
   BamfWindowStack::ViewOpened(QString const, QString const) ()
  Title: window-stack-bridge crashed with SIGSEGV in QVariant::QVariant()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.hud.log: (process:1303): hudapplicationlist-WARNING **: Could not get 
window stack: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.canonical.Unity.WindowStack was not provided by any .service files
  upstart.window-stack-bridge.log: Window:  44040198 Desktop has no parents

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1238420/+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 1066374] Re: /etc/init.d/networking restart causes unity to crash (12.10 beta)

2013-10-12 Thread Ionut C.
Same here...

Can someone tell me how can i recover from this without rebooting the
system ?

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

Title:
  /etc/init.d/networking restart causes unity to crash (12.10 beta)

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I ran /etc/init.d/networking restart from the terminal and it
  appeared that Unity crashed as result. The launcher and the top panel
  disappeared. I was still able to right click on the desktop and get
  the context menu, the theme from my open chromium windows seems to
  have had resorted to a default theme of some sort and I wasn't able to
  type in the chromium window location bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1066374/+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 1239060] [NEW] Unity launcher does not remember icons position

2013-10-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Changes in launcher icon positions are not permanent, they will move
back after reboot or logout/login. I'm not sure when exactly this
behaviour started, previously it worked fine. Saucy Salamander 13.10.

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment unity
-- 
Unity launcher does not remember icons position
https://bugs.launchpad.net/bugs/1239060
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1239060] Re: Unity launcher does not remember icons position

2013-10-12 Thread Thaddäus Tintenfisch
** Package changed: ubuntu = unity (Ubuntu)

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

Title:
  Unity launcher does not remember icons position

Status in “unity” package in Ubuntu:
  New

Bug description:
  Changes in launcher icon positions are not permanent, they will move
  back after reboot or logout/login. I'm not sure when exactly this
  behaviour started, previously it worked fine. Saucy Salamander 13.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239060/+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 1229370] Re: Launcher is empty saying Sorry, there is nothing that matches your search

2013-10-12 Thread corrado venturini
unity-scope-home 6.8.2+13.10.20131003-0ubuntu1 is installed
ubuntu saucy 64-bit Gallium 0.4 on NV4B

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

Title:
  Launcher is empty saying Sorry, there is nothing that matches your
  search

Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Since an update on Sunday, 22nd my Unity launcher is empty. All the
  categories: Home, Apps, Files, ... except for the Social lens/scope.

  I tried removing the caches under ~/.cache, reset zeitgeist, etc.
  There is nothing I can do about it. When I switch to a guest session,
  it's the same: emptyness.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130920-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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 23 21:23:12 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-09-21 (2 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130921)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1229370/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch

2013-10-12 Thread Steve Langasek
So the reason the memory usage wasn't growing after re-exec was because
unity8 didn't automatically reconnect when the dbus connection dropped.
If I kill and restart unity8, the problem reappears.

So the memory usage is indeed associated with the dbus client, even
though disconnecting the client doesn't free the memory, and valgrind
doesn't consider the memory to have been lost.

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

Title:
  uevent spam causes libdbus client code in session upstart to consume
  massive amounts of memory on Ubuntu Touch

Status in Upstart:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “systemd” source package in Saucy:
  New
Status in “unity” source package in Saucy:
  New
Status in “upstart” source package in Saucy:
  Fix Released

Bug description:
  using ubuntu touch image 82 i see the session init consume about 10MB per 
minute as long as the screen is on  with Mir.
  running the same session with surfaceflinger only consumes 1MB per minute.

  in both cases the system starts to swap heavily at some point, making
  the UI unresponsive.

  http://paste.ubuntu.com/6196223/ has the top output of a Mir session
  after 30min, the UI just got completely unresponsive when this
  snapshot was taken.

  http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
  session where the screen was off for about 10min

  apparently the leak only occurs while the screen is on, it seems to be
  permanently there but in the case of surfaceflinger it hits less hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235649/+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 1226105] Re: [Saucy] Empty Unity dashboard after upgrade Raring - Saucy Beta 1

2013-10-12 Thread corrado venturini
*** This bug is a duplicate of bug 1220572 ***
https://bugs.launchpad.net/bugs/1220572

i have 7 icons. if i click filesfolders i see some files.  if i click
the 3rd icon i see recent, download, folders. if i click the 'search
applications' icon i see NOTHING.

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

Title:
  [Saucy] Empty Unity dashboard after upgrade Raring - Saucy Beta 1

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Raring to Saucy Beta 1, the Unity dashboard has
  become completely empty except for a search social networks icon at
  the bottom.

  No more Apps, no more Files, etc, everything  and her brother is gone
  :-/

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  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,dbus]
  Date: Mon Sep 16 17:49:14 2013
  EcryptfsInUse: Yes
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-09-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1226105/+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 1233199] Re: lock to launcher / unlock from launcher not working...

2013-10-12 Thread Jakob Mühldorfer
Same for me.
@Brian: which files do I need permission for?

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

Title:
  lock to launcher / unlock from launcher not working...

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I either click on Lock to Launcher or Unlock from Launcher
  nothing happens.

  Ubuntu Version: 13.10
  Unity Version: 7

  Steps Taken:

  - reinstall unity / ubuntu-desktop
  - reset unity icons

  Other Info:

  The only way I'm able to change the icons currently is manually
  through gconf which often requires me to logout and login to take
  effect.

  -Peter

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu1
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg: [   48.845411] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
  Date: Mon Sep 30 07:16:12 2013
  DistUpgraded: 2013-09-02 00:45:43,852 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-20 (40 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Gigabyte Technology Co., Ltd. H61N-USB3
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic 
root=UUID=227939ab-2f00-4536-87e2-e2c048aac315 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-09-02 (28 days ago)
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: H61N-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd05/15/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61N-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61N-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H61N-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.2-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep 30 00:36:18 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputDell Dell USB Keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 723 
   vendor ACR
  xserver.version: 2:1.14.2.901-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1233199/+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 1239234] [NEW] Type your command dialog displayed when resuming from suspend

2013-10-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When the computer wakes from suspend (and, if locking is enabled, the
screen is unlocked), the Type your command dialog is displayed in the
top left corner, as if the user had pressed Alt. This occurs even if the
user suspends and then wakes up the computer with no keypresses.

This does not occur by simply engaging and then unlocking the
screensaver without a suspend.

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment saucy
-- 
Type your command dialog displayed when resuming from suspend
https://bugs.launchpad.net/bugs/1239234
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1239060] Re: Unity launcher does not remember icons position

2013-10-12 Thread Brian Murray
** Tags added: saucy

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

Title:
  Unity launcher does not remember icons position

Status in “unity” package in Ubuntu:
  New

Bug description:
  Changes in launcher icon positions are not permanent, they will move
  back after reboot or logout/login. I'm not sure when exactly this
  behaviour started, previously it worked fine. Saucy Salamander 13.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239060/+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 1239060] Re: Unity launcher does not remember icons position

2013-10-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity (Ubuntu)
   Status: New = Confirmed

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

Title:
  Unity launcher does not remember icons position

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Changes in launcher icon positions are not permanent, they will move
  back after reboot or logout/login. I'm not sure when exactly this
  behaviour started, previously it worked fine. Saucy Salamander 13.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239060/+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 1239234] Re: Type your command dialog displayed when resuming from suspend

2013-10-12 Thread Stephen M. Webb
*** This bug is a duplicate of bug 1227920 ***
https://bugs.launchpad.net/bugs/1227920

** This bug has been marked a duplicate of bug 1227920
   after suspend/resume, the Unity HUD is always open when I unlock the screen

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

Title:
  Type your command dialog displayed when resuming from suspend

Status in “unity” package in Ubuntu:
  New

Bug description:
  When the computer wakes from suspend (and, if locking is enabled, the
  screen is unlocked), the Type your command dialog is displayed in
  the top left corner, as if the user had pressed Alt. This occurs even
  if the user suspends and then wakes up the computer with no
  keypresses.

  This does not occur by simply engaging and then unlocking the
  screensaver without a suspend.

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