date:20141120

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/546056

Title:
  gdb crashed with AttributeError in __repr__()

Status in “apport” package in Ubuntu:
  Invalid
Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  No idea what caused this unfortunately, but after starting up Kubuntu
  Lucid (up-to-date as of 24-Mar-2010 15:25 UTC) I received the apport
  notification.

  ProblemType: Crash
  Architecture: amd64
  Date: Wed Mar 24 00:10:11 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gdb
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  Package: gdb 7.1-1ubuntu1
  ProcCmdline: /usr/bin/gdb -nw -n -batch -x 
/tmp/kde-username/drkonqiyJ9575.tmp -p 9573 /usr/bin/python2.6
  ProcEnviron:
   SHELL=/bin/zsh
   LANGUAGE=
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  SourcePackage: gdb
  Title: gdb crashed with AttributeError in __repr__()
  Uname: Linux 2.6.32-17-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/546056/+subscriptions

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

[Touch-packages] [Bug 490170] Re: GDB cannot continue after stopping at a breakpoint

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/490170

Title:
  GDB cannot continue after stopping at a breakpoint

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  I'm trying to debug Amarok. I set a few breakpoints:
  (gdb) b xinestream.cpp:666

   
  Breakpoint 1 at 0x7fffe304a186: file ../../xine/xinestream.cpp, line 666. 

   
  (gdb) b xinestream.cpp:196
  Breakpoint 2 at 0x7fffe30482cd: file ../../xine/xinestream.cpp, line 196. (3 
locations)
  (gdb) b xinestream.cpp:1433
  Breakpoint 3 at 0x7fffe30507d6: file ../../xine/xinestream.cpp, line 1433.

  But, once a breakpoint gets hit, gdb refuses to continue, or do anything at 
all:
  (gdb) c   
  Continuing.   
  Cannot get thread event message: debugger service failed  
  (gdb) bt
  Target is executing.
  (gdb) info frame
  No stack.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Nov 29 17:30:19 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: gdb 7.0-0ubuntu1
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  SourcePackage: gdb
  Uname: Linux 2.6.31-15-generic x86_64
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:2439): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (pidgin:2195): Pango-WARNING **: pango_layout_set_markup_with_accel: Error 
on line 4: Entity did not end with a semicolon; most likely you used an 
ampersand character without intending to start an entity - escape ampersand as 
&
   (:3149): Gdk-CRITICAL **: gdk_window_get_origin: assertion 
`GDK_IS_WINDOW (window)' failed
   (pidgin:2195): Pango-WARNING **: pango_layout_set_markup_with_accel: Error 
on line 4: Entity did not end with a semicolon; most likely you used an 
ampersand character without intending to start an entity - escape ampersand as 
&

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/490170/+subscriptions

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

[Touch-packages] [Bug 495115] Re: gdb segfaults after a program it is debugging segfaults, restarts, and reaches a break point

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/495115

Title:
  gdb segfaults after a program it is debugging segfaults, restarts, and
  reaches a break point

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  gdb is crashing when i restart a segfaulted program and reach a
  breakpoint. I'm debugging some simple data transforms via a test
  program (i'll try to attach), which fails when run on itself(not the
  bug i'm reporting). I set a breakpoint before the first run at line
  data_transforms.c:156(middle of a for loop). When it reaches the break
  for the first time in the new run, it segfaults.

  I'm running 9.10 karmic, with uname -a:

  Linux schrodingers-grue-box 2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3
  22:00:22 UTC 2009 i686 GNU/Linux

  apt-cache reports gdb as: Architecture: i386 Version: 7.0-0ubuntu1

  I attached gdb to gdb, caused the segfault again, and recieved the
  following backtrace:

  Program received signal SIGSEGV, Segmentation fault.
  0x08181de9 in check_typedef ()
  (gdb) bt
  #0  0x08181de9 in check_typedef ()
  #1  0x08129be2 in allocate_value_lazy ()
  #2  0x08129ca2 in allocate_value ()
  #3  0x08129e73 in value_from_longest ()
  #4  0x0812e10d in evaluate_subexp_standard ()
  #5  0x081cb73e in ?? ()
  #6  0x0812c1d7 in evaluate_subexp_standard ()
  #7  0x081cb73e in ?? ()
  #8  0x0812ad1e in evaluate_subexp_with_coercion ()
  #9  0x0812cbc9 in evaluate_subexp_standard ()
  #10 0x081cb73e in ?? ()
  #11 0x0812aaff in evaluate_expression ()
  #12 0x08141681 in ?? ()
  #13 0x0814182f in do_displays ()
  #14 0x0815e826 in normal_stop ()
  #15 0x0815a9e7 in ?? ()
  #16 0x080928e2 in execute_command ()
  #17 0x0817094b in ?? ()
  #18 0x081716a2 in ?? ()
  #19 0x007fba32 in rl_callback_read_char () from /lib/libreadline.so.6
  #20 0x08170a8b in ?? ()
  #21 0x0816ff79 in ?? ()
  #22 0x0816f7bb in ?? ()
  ---Type  to continue, or q  to quit---
  #23 0x08170646 in gdb_do_one_event ()
  #24 0x0816a983 in catch_errors ()
  #25 0x080f4ab4 in ?? ()
  #26 0x0816b053 in current_interp_command_loop ()
  #27 0x080891bb in ?? ()
  #28 0x0816a983 in catch_errors ()
  #29 0x08089d84 in ?? ()
  #30 0x0816a983 in catch_errors ()
  #31 0x080890e2 in gdb_main ()
  #32 0x080890a3 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/495115/+subscriptions

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

[Touch-packages] [Bug 360595] Re: gdb crashed with SIGSEGV in value_fn_field()

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/360595

Title:
  gdb crashed with SIGSEGV in value_fn_field()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  Was debugging some of my software using Eclipse when this happened.

  ProblemType: Crash
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gdb
  NonfreeKernelModules: nvidia
  Package: gdb 6.8-3ubuntu2
  ProcCmdline: gdb -q -nw -i mi -tty /dev/pts/0 
--cd=/home/username/workspace/EciDataAccess --command=.gdbinit 
/home/username/workspace/EciDataAccess/debug/EciDatabase
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: gdb
  StacktraceTop:
   value_fn_field ()
   ?? ()
   ?? ()
   value_struct_elt ()
   evaluate_subexp_standard ()
  Title: gdb crashed with SIGSEGV in value_fn_field()
  Uname: Linux 2.6.28-11-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/360595/+subscriptions

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

[Touch-packages] [Bug 368335] Re: gdb doesn't work

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/368335

Title:
  gdb  doesn't work

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  At the prompt, I type in:  
  gdb 
  and get the following:
  [21:35:02 dvz] $ gdb find: cannot search `': No such file or directory
  find: `/usr/scripts': No such file or directory

  The  seems to automatically execute instead of populate options.
  completion works no problem with other tools/commands.

  I don't know if this is my issue or gdb, or if anyone else has had
  this.

  =
  Description:  Ubuntu 9.04
  Release:  9.04

  gdb:
Installed: 6.8-3ubuntu2
Candidate: 6.8-3ubuntu2
Version table:
   *** 6.8-3ubuntu2 0
  500 http://us.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/368335/+subscriptions

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

[Touch-packages] [Bug 434168] Re: spawned a gdb spinning at 100%CPU

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/434168

Title:
  spawned a gdb spinning at 100%CPU

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  I discovered a gdb process that was consuming all CPU time and killed it.
  At that time, a new apport window opened to report a bug.
  I am guessing the gdb process was started by apport.
  If it happens again, I will check in pstree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/434168/+subscriptions

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

[Touch-packages] [Bug 385454] Re: gdb froze after the program exited

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/385454

Title:
  gdb froze after the program exited

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  When the program I was debugging exited, gdb froze. The program is now
  in a "zombie" state. Here's the backtrace for gdb:

  #0  0x7f0264fc88f5 in __libc_waitpid (pid=4589, stat_loc=0x7fff6dfe0864, 
options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
  #1  0x00464d95 in my_waitpid (pid=4589, status=0x7fff6dfe0864, 
flags=0) at /build/buildd/gdb-6.8/gdb/linux-nat.c:194
  #2  0x00466bd0 in wait_lwp (lp=0x2773c10) at 
/build/buildd/gdb-6.8/gdb/linux-nat.c:1371
  #3  0x004670e3 in stop_wait_callback (lp=0x2773c10, 
data=0x7fff6dfe0960) at /build/buildd/gdb-6.8/gdb/linux-nat.c:1493
  #4  0x00463f98 in iterate_over_lwps (callback=0x4670c0 
, data=0x7fff6dfe0960) at 
/build/buildd/gdb-6.8/gdb/linux-nat.c:757
  #5  0x004683ab in linux_nat_wait (ptid={pid = -1, lwp = 0, tid = 0}, 
ourstatus=0x7fff6dfe0b80) at /build/buildd/gdb-6.8/gdb/linux-nat.c:2284
  #6  0x0046d126 in thread_db_wait (ptid={pid = -1, lwp = 0, tid = 0}, 
ourstatus=0x7fff6dfe0b80)
  at /build/buildd/gdb-6.8/gdb/linux-thread-db.c:904
  #7  0x004eabb9 in wait_for_inferior (treat_exec_as_sigtrap=0) at 
/build/buildd/gdb-6.8/gdb/infrun.c:1032
  #8  0x004eaeb7 in proceed (addr=, 
siggnal=TARGET_SIGNAL_DEFAULT, step=0) at /build/buildd/gdb-6.8/gdb/infrun.c:844
  #9  0x004e49d7 in continue_command (proc_count_exp=0x0, from_tty=1) 
at /build/buildd/gdb-6.8/gdb/infcmd.c:653
  #10 0x0044e28a in execute_command (p=0x271d1a1 "", from_tty=1) at 
/build/buildd/gdb-6.8/gdb/top.c:449
  #11 0x004f650b in command_handler (command=0x271d1a0 "c") at 
/build/buildd/gdb-6.8/gdb/event-top.c:518
  #12 0x004f73dc in command_line_handler (rl=) at 
/build/buildd/gdb-6.8/gdb/event-top.c:804
  #13 0x7f0265ba9c8e in rl_callback_read_char () from /lib/libreadline.so.5
  #14 0x004f6829 in rl_callback_read_char_wrapper (client_data=0x11ed) 
at /build/buildd/gdb-6.8/gdb/event-top.c:177
  #15 0x004f512d in process_event () at 
/build/buildd/gdb-6.8/gdb/event-loop.c:341
  #16 0x004f5ae6 in gdb_do_one_event (data=) at 
/build/buildd/gdb-6.8/gdb/event-loop.c:378
  #17 0x004f2634 in catch_errors (func=0x4f58e0 , 
func_args=0x0, errstring=0x64a577 "", mask=)
  at /build/buildd/gdb-6.8/gdb/exceptions.c:513
  #18 0x00497940 in tui_command_loop (data=) at 
/build/buildd/gdb-6.8/gdb/tui/tui-interp.c:153
  #19 0x00446169 in captured_command_loop (data=0x11ed) at 
/build/buildd/gdb-6.8/gdb/main.c:99
  #20 0x004f2634 in catch_errors (func=0x446160 
, func_args=0x0, errstring=0x64a577 "", mask=)
  at /build/buildd/gdb-6.8/gdb/exceptions.c:513
  #21 0x00446c7e in captured_main (data=) at 
/build/buildd/gdb-6.8/gdb/main.c:883
  #22 0x004f2634 in catch_errors (func=0x4461a0 , 
func_args=0x7fff6dfe12b0, errstring=0x64a577 "", mask=)
  at /build/buildd/gdb-6.8/gdb/exceptions.c:513
  #23 0x00446154 in gdb_main (args=) at 
/build/buildd/gdb-6.8/gdb/main.c:892
  #24 0x00446126 in main (argc=, 
argv=0x7fff6dfe0864) at /build/buildd/gdb-6.8/gdb/gdb.c:33

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/385454/+subscriptions

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

[Touch-packages] [Bug 450571] Re: DWARF-2 expression error

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/450571

Title:
  DWARF-2 expression error

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  compiled dvswitch from trunk:
  git clone https://alioth.debian.org/anonscm/git/dvswitch

  juser@dhcp227:~/vga2usb/dvs/dvswitch/dvswitch-trunk$ git show
  commit 20a5cd7eb17baca7181225901c03519d46d5ad41
  Author: Ben Hutchings 
  Date:   Wed Sep 30 04:24:43 2009 +0100

  running the app resulted in segfault, Ben says: "You seem to have
  found a compiler bug - gdb 7.0 is a major new release so the bug may
  well be there"

  Description:  Ubuntu karmic (development branch)
  Release:  9.10

Installed: 7.0-0ubuntu1

  Linux dhcp227 2.6.31-13-generic #45-Ubuntu SMP Tue Oct 13 02:07:24 UTC
  2009 x86_64 GNU/Linux

  ProblemType: Bug
  Architecture: amd64
  Date: Tue Oct 13 12:51:32 2009
  DistroRelease: Ubuntu 9.10
  Package: gdb 7.0-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
  SourcePackage: gdb
  Uname: Linux 2.6.31-13-generic x86_64
  XsessionErrors:
   (gnome-settings-daemon:1652): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:1652): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (nautilus:1713): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (polkit-gnome-authentication-agent-1:1737): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-panel:1712): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to 
allocate widget with width -3 and height 24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/450571/+subscriptions

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

[Touch-packages] [Bug 438081] Re: gdb eats 100% of CPU when taking info about npviewer's crash

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/438081

Title:
  gdb eats 100% of CPU when taking info about npviewer's crash

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  nspluginwrapper: 1.2.2-0ubuntu6

  Npviewer crashed when gnome started.
  Apport is collecting info about the crash and gdb is still on 100% of CPU 
(even after 30 minutes)

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Sep 28 13:10:05 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gdb
  NonfreeKernelModules: fglrx
  Package: gdb 6.8.90.20090918-0ubuntu2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
  SourcePackage: gdb
  Uname: Linux 2.6.31-10-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/438081/+subscriptions

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

[Touch-packages] [Bug 348638] Re: gdb crash when evaluating an expression with several function calls

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/348638

Title:
  gdb crash when evaluating an expression with several function calls

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  When evaluating an expression, I get the following crash:

  Program received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f1f5f2366e0 (LWP 28406)]
  d_name (di=0x7fff66a5b740) at 
/build/buildd/gdb-6.8/libiberty/cp-demangle.c:1193
in /build/buildd/gdb-6.8/libiberty/cp-demangle.c
  (gdb) bt
  #0  d_name (di=0x7fff66a5b740) at 
/build/buildd/gdb-6.8/libiberty/cp-demangle.c:1193
  #1  0x00629b04 in d_encoding (di=0x7fff66a5b740, top_level=1) at 
/build/buildd/gdb-6.8/libiberty/cp-demangle.c:1053
  #2  0x0062a1a6 in is_ctor_or_dtor (mangled=0x7f1f578be9e3 
"_ZNK7piclens6PLSize3fitERKS0_fb", ctor_kind=0x7fff66a5b7e4, 
  dtor_kind=0x7fff66a5b7e0) at 
/build/buildd/gdb-6.8/libiberty/cp-demangle.c:4416
  #3  0x0062a293 in is_gnu_v3_mangled_ctor (name=0x7fff66a5b740 
"��\213W\037\177") at /build/buildd/gdb-6.8/libiberty/cp-demangle.c:4466
  #4  0x00573410 in gnuv3_pass_by_reference (type=0xaca2350) at 
/build/buildd/gdb-6.8/gdb/gnu-v3-abi.c:776
  #5  0x005734b5 in gnuv3_pass_by_reference (type=0xaca2350) at 
/build/buildd/gdb-6.8/gdb/gnu-v3-abi.c:795

  [ skip a hundred thousand lines ]

  #130888 0x005734b5 in gnuv3_pass_by_reference (type=0xaca2350) at 
/build/buildd/gdb-6.8/gdb/gnu-v3-abi.c:795
  #130889 0x005734b5 in gnuv3_pass_by_reference (type=0xaca22b0) at 
/build/buildd/gdb-6.8/gdb/gnu-v3-abi.c:795
  #130890 0x005734b5 in gnuv3_pass_by_reference (type=0xaca4240) at 
/build/buildd/gdb-6.8/gdb/gnu-v3-abi.c:795
  #130891 0x004e1058 in call_function_by_hand (function=0x515b340, 
nargs=2, args=0x7fff67258bb8) at /build/buildd/gdb-6.8/gdb/infcall.c:480
  #130892 0x004bda34 in evaluate_subexp_standard (expect_type=, exp=0xa003320, pos=0x7fff67258f04, noside=EVAL_NORMAL)
  at /build/buildd/gdb-6.8/gdb/eval.c:1265
  #130893 0x004bbb52 in evaluate_expression (exp=) 
at /build/buildd/gdb-6.8/gdb/eval.c:75
  #130894 0x004ceb77 in print_command_1 (exp=0xa231a2 
"UIController::shared()->mainLayer()->hud()->GetWallSafeContentRect(true)", 
inspect=0,
  voidprint=1) at /build/buildd/gdb-6.8/gdb/printcmd.c:872
  #130895 0x0044e28a in execute_command (p=0xa231e9 ")", from_tty=1) at 
/build/buildd/gdb-6.8/gdb/top.c:449
  #130896 0x004f650b in command_handler (command=0xa231a0 "p 
UIController::shared()->mainLayer()->hud()->GetWallSafeContentRect(true)")
  at /build/buildd/gdb-6.8/gdb/event-top.c:518
  #130897 0x004f73dc in command_line_handler (rl=) 
at /build/buildd/gdb-6.8/gdb/event-top.c:804
  #130898 0x7f1f5ee22ea7 in rl_callback_read_char () from 
/lib/libreadline.so.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/348638/+subscriptions

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

[Touch-packages] [Bug 436440] Re: gdb high CPU usage

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/436440

Title:
  gdb high CPU usage

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  When Totem 2.28.0 crash there is no option to send report via apport,
  as a result gdb activates in process and uses 80-90 % of CPU

  ProblemType: Bug
  Architecture: i386
  Date: Fri Sep 25 10:04:37 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gdb
  NonfreeKernelModules: nvidia
  Package: gdb 6.8.90.20090918-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
  SourcePackage: gdb
  Uname: Linux 2.6.31-10-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/436440/+subscriptions

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

[Touch-packages] [Bug 362652] Re: asin produces wrong values

p asin(1.0)

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/362652

Title:
  asin produces wrong values

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Calls to asin from inside gdb produce incorrect values.

  Testcase:
  #include 
  #include 

  int main() {
printf("asin(1.0) = %f\n", asin(1.0));
return 0;
  } 

  Test program correctly prints 1.570796, but "p asin(1.0)" from within
  gdb prints 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/362652/+subscriptions

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

[Touch-packages] [Bug 1302196] Re: gdb crashed with SIGSEGV in PyDict_GetItem()

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1302196

Title:
  gdb crashed with SIGSEGV in PyDict_GetItem()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  It pops up after the login

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gdb 7.7-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 18:20:13 2014
  ExecutablePath: /usr/bin/gdb
  InstallationDate: Installed on 2013-09-10 (205 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130910)
  ProcCmdline: gdb --ex file\ "/usr/bin/apt-get" --ex core-file\ 
/tmp/apport_core_hky1muf3 --batch --ex set\ backtrace\ limit\ 2000 --ex p\ -99 
--ex x/16i\ $pc --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ 
bt\ full --ex p\ -99 --ex print\ (char*)\ __nih_abort_msg --ex p\ -99 --ex 
info\ registers --ex p\ -99 --ex print\ __glib_assert_msg --ex p\ -99 --ex 
print\ __abort_msg->msg
  SegvAnalysis:
   Segfault happened at: 0xb7432ce1:cmpb   $0x0,0x10(%esi)
   PC (0xb7432ce1) ok
   source "$0x0" ok
   destination "0x10(%esi)" (0xb600bb10) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gdb
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
   PyDict_GetItem () from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
   PyUnicode_InternInPlace () from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
   ?? () from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
   ?? () from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
  Title: gdb crashed with SIGSEGV in PyDict_GetItem()
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (3 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1302196/+subscriptions

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

[Touch-packages] [Bug 342588] Re: gdb freezes too often, making debugging difficult

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/342588

Title:
  gdb freezes too often, making debugging difficult

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  I set a breakpoint and run the program... But gdb just freezes. Here's
  the stack trace:

  #0  0x7fa7df69a3aa in sigsuspend () from /lib/libc.so.6
  #1  0x00467f77 in ?? ()
  #2  0x0046d126 in ?? ()
  #3  0x004eabb9 in wait_for_inferior () 
  #4  0x004eaeb7 in proceed ()   
  #5  0x004e49d7 in continue_command ()  
  #6  0x0044e28a in execute_command ()   
  #7  0x004f650b in ?? ()
  #8  0x004f73dc in ?? ()
  #9  0x7fa7e02eeea7 in rl_callback_read_char () from /lib/libreadline.so.5
  #10 0x004f6829 in ?? ()  
  #11 0x004f512d in ?? ()  
  #12 0x004f5ae6 in gdb_do_one_event ()
  #13 0x004f2634 in catch_errors ()
  #14 0x00497940 in ?? ()  
  #15 0x00446169 in ?? ()  
  #16 0x004f2634 in catch_errors ()
  #17 0x00446c7e in ?? ()  
  #18 0x004f2634 in catch_errors ()
  #19 0x00446154 in gdb_main ()
  #20 0x00446126 in main ()

  (Sorry, I don't know how to get symbols for gdb.)

  It ignores Ctrl-C, Ctrl-Z, Ctrl-\.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/342588/+subscriptions

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

[Touch-packages] [Bug 319418] Re: gdb crashes when debugging firefox after an exec

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/319418

Title:
  gdb crashes when debugging firefox after an exec

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  Create a simple program, gdbcrash.c, that runs firefox:

  #include 

  int main(int argc, char* argv[]) {
  execl("/usr/bin/firefox", "firefox", NULL);
  return 1;
  }

  Compile it, and run it in gdb. Make sure firefox is not already
  running, or change the program so it starts firefox with a different
  profile.

  Here's what I get:

  $ gdb ./gdbcrash 
  GNU gdb 6.8-debian
  Copyright (C) 2008 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "i486-linux-gnu"...
  (gdb) run
  Starting program: /home/dima/gdbcrash 
  Executing new program: /bin/dash
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  Executing new program: /usr/lib/firefox-3.0.5/firefox
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  [Thread debugging using libthread_db enabled]
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  [New Thread 0xb7c646c0 (LWP 24972)]
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  ---Type  to continue, or q  to quit---
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  [New Thread 0xb5c5cb90 (LWP 24975)]
  [New Thread 0xb5319b90 (LWP 24976)]
  [New Thread 0xb4b18b90 (LWP 24977)]
  [Thread 0xb5c5cb90 (LWP 24975) exited]
  [Thread 0xb4b18b90 (LWP 24977) exited]
  [Thread 0xb5319b90 (LWP 24976) exited]
  [New process 24972]
  Executing new program: /usr/lib/firefox-3.0.5/firefox
  warning: Cannot initialize thread debugging library: generic error
  warning: Cannot initialize thread debugging library: generic error
  (no debugging symbols found)
  [New process 24972]
  (no debugging symbols found)
  [Thread debugging using libthread_db enabled]
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  Segmentation fault

  
  This happens in Ubuntu 8.04 and 8.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/319418/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post

[Touch-packages] [Bug 338440] Re: gdb constantly stops with a message "debugger service failed"

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/338440

Title:
  gdb constantly stops with a message "debugger service failed"

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  I'm trying to debug a Firefox plugin. GDB makes it very difficult: it 
constantly stops debugging, and displays an error message:
  [Thread 0x46f2a950 (LWP 25316) exited]
  Cannot get thread event message: debugger service failed

  If I type "continue", it resumes - only to stop a few seconds later.

  (I had gdb attached while filing this bug report; it stopped seven
  times.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/338440/+subscriptions

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

[Touch-packages] [Bug 1332484] Re: GDB Demangler crashes in 14.10 and 14.04

there is no upstream patch yet

** Changed in: gdb (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gdb (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1332484

Title:
  GDB Demangler crashes in 14.10 and 14.04

Status in GNU Debugger:
  Unknown
Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  (gdb crashed with SIGSEGV in _IO_vfprintf_internal())

  This is to duplicate an upstream bug report that affects users on both
  14.10 and 14.04 LTS.

  Test case:

  echo 'void
  
_ZN5Utils9transformIPN15ProjectExplorer13BuildStepListEZNKS1_18BuildConfiguration14knownStepListsEvEUlS3_E_EEN4Myns5QListIDTclfp0_cvT__ERKNS7_IS8_EET0_()
  { } int main() {}' | gcc -xc - && gdb ./a.out

  Upstream has a patch, and it'd be nice to also SRU the fix to 14.04
  LTS because users are seeing it (as reported on IRC).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1332484/+subscriptions

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

[Touch-packages] [Bug 1155981] Re: gdb crashing

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1155981

Title:
  gdb crashing

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  When I continue using gdb via Eclipse, netbeans or Emacs gdb crashes

  
  lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  used gdb in built version:
  gdb --version
  GNU gdb (GDB) 7.5-ubuntu
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  

  
  09:26 PM =>$emacs --version
  GNU Emacs 23.4.1
  Copyright (C) 2012 Free Software Foundation, Inc.
  GNU Emacs comes with ABSOLUTELY NO WARRANTY.
  You may redistribute copies of Emacs
  under the terms of the GNU General Public License.
  For more information about these matters, see the file named COPYING.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1155981/+subscriptions

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

[Touch-packages] [Bug 1394380] Re: [TOPBLOCKER] QML cache not regenerated correctly on image update

2014-11-20 Thread Oliver Grawert

added top blocker status since it is considered to go in before the
golden milestone

** Summary changed:

- QML cache not regenerated correctly on image update
+ [TOPBLOCKER] QML cache not regenerated correctly on image update

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1394380

Title:
  [TOPBLOCKER] QML cache not regenerated correctly on image update

Status in “android” package in Ubuntu:
  Invalid
Status in “lxc-android-config” package in Ubuntu:
  Confirmed
Status in “lxc-android-config” package in Ubuntu RTM:
  Confirmed

Bug description:
  image rtm-proposed 166

  Multiple problems here, due to the fact that oxide was updated (a new
  release) and webrowser-app was updated

  1) webbrowser-app cache was not updated on the image upgrade in 
.cache/QML/Apps/webbrowser-app and 
  desktop versions of web pages are displayed until the cache is destroyed or 
regenerated. Try cnn.com or nytimes.com

  2) no webbapps cache is regenerated, so launching of the webapps
  displays wrong pages (.cache/QML/Apps/*webapps*) due to stale cache.
  You can try Google Maps for an example. Deleting the cache makes them
  work again properly.

  Expected Results:
  - after image upgrade, either all of the apps should be regenerated smartly, 
or we should blow away all of the caches to prevent an issue when a library 
(like oxide) is upgraded and causes an invalid cache.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions

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

[Touch-packages] [Bug 1265662] Re: Bluetooth Magic Mouse Lags and disconnect

can't make any connection to gdb

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1265662

Title:
  Bluetooth Magic Mouse Lags and disconnect

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  This issue is also referred here:

  http://askubuntu.com/questions/368236/bluetooth-mouse-lags-and-
  eventually-disconnects

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1265662/+subscriptions

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

[Touch-packages] [Bug 1390905] Re: gdb list not from the first line

test case is missing. this usually works me.

** Changed in: gdb (Ubuntu)
   Status: New => Incomplete

** Changed in: gdb (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1390905

Title:
  gdb list not from the first line

Status in “gdb” package in Ubuntu:
  Incomplete

Bug description:
  when I use gdb list command, it does not list source code from the
  first line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1390905/+subscriptions

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

[Touch-packages] [Bug 1275210] Re: gdbtui does not give input and show cyrillic symbols

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1275210

Title:
  gdbtui does not give input and show cyrillic symbols

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  
┌──main.c┐
     │1   #include 
   │
     │2 
   │
     │3   int main()
   │
     │4   { 
   │
     │5   printf("M-P~_M-Q~@M-PM-8M-PM-2M-PM-5M-Q~B 
M-P~\M-PM-8M-Q~@\n");  │
     │6   return 0; 
   │
     │7   } 
   │
     │8 


   │
     
└─┘
  exec No process In:   
  Line: ??   PC: ??
  GNU gdb (GDB) 7.6.1-ubuntu
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /home/eldar/hello...done.
  (gdb) M-Q~GM-Q~BM-PM-> M-Q~BM-PM-0M-PM-:M-PM->M-PM-5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1275210/+subscriptions

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

[Touch-packages] [Bug 1348666] Re: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error:value_of_register_lazy

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1348666

Title:
  
/usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error:value_of_register_lazy

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gdb.  This problem was most recently seen with version
  7.7.91.20140723-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/41e25033b9aad2967c2c55bc3b1279ef06a35625
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1348666/+subscriptions

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

[Touch-packages] [Bug 1202220] Re: step function does not work with gdb-mutiarch

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1202220

Title:
  step function does not work with gdb-mutiarch

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  In cross mode, running gdbserver from 12.04 armhf in the target and
  using gdb-multiarch in the host 12.04 x86 ubuntu, we can connect to
  the target using suitable gdbinit file but we cannot use step command
  in gdb-mutliarch shell. Using once starts the program to be run in the
  gdbserver, using it once more the program completion in the target.

  Steps to repro:
  Test C file: test.c

  #include 

  void printest()
  {
  printf("printest function.\n");
  printf("printest function.\n");
  printf("printest function.\n");
  printf("printest function.\n");
  }

  int main(int argc, char *argv[])
  {

  printf("Hello World!\n");
  printf("Hello World!\n");
  printest();
  printest();
  printf("Hello World!\n");
  printf("Hello World!\n");
  return 0;
  }

  Build:
  arm-linux-gnueabihf-gcc -g test.c -o test

  In target:
  gdbserver :1234 ./test

  In host:
  gdb-multiarch ./test

  gdbinit file used has:
  set solib-absolute-prefix  
  set sysroot  
  set solib-search-path  /lib: /usr/lib
  set architecture arm

  In the gdb shell:
  (gdb)target remote :1234 
  (gdb) step
  (gdb) step

  Output:
  The program terminates in the target and the debugging is stopped.

  Also, I verified that using just the latest 12.04-armhf gdb (not the
  client/server combination) in the target itself that the same issue
  does not reproduce.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1202220/+subscriptions

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

[Touch-packages] [Bug 1379384] Re: Notifications anchored to the left instead of right on manta

** Also affects: unity8 (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1379384

Title:
  Notifications anchored to the left instead of right on manta

Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  See the attached image. They should also be pushed further down to get
  separated from the indicators at the top.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141008-0ubuntu1
  Uname: Linux 3.4.0-6-manta armv7l
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: armhf
  Date: Thu Oct  9 14:45:16 2014
  InstallationDate: Installed on 2014-10-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141009-020205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379384/+subscriptions

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

[Touch-packages] [Bug 1082460] Re: [regression] string not display when using UTF-8 characters

this works for me in 14.04 LTS

** Changed in: gdb (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1082460

Title:
  [regression] string not display when using UTF-8 characters

Status in “gdb” package in Ubuntu:
  Fix Released

Bug description:
  $ uname -a
  Linux black 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:27:31 UTC 2012 i686 
i686 i686 GNU/Linux
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 12.10
  Release:  12.10
  Codename: quantal
  -
  exp.cpp:
  ---
  #include 
  using namespace std;
  const char *s  = "ф";//ф
  const char *s2 = "\ud45c";//표
  int main() {
cout << s << endl;
cout << s2 << endl;
return 0;
  }
  ---
  $ g++ -O0 -g -o "exp" exp.cpp
  $ ./exp
  ф
  표
  -

  gdb_7.5-0ubuntu2_i386.deb:
  -
  $ gdb ./exp
  GNU gdb (GDB) 7.5-ubuntu
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "i686-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /home/sneg/work/edu_cpp/exp...done.
  (gdb) print s
  $1 = 0x80487f8 
  (gdb) print s2
  $2 = 0x80487fb 
  (gdb) show charset
  The host character set is "auto; currently UTF-8".
  The target character set is "auto; currently UTF-8".
  The target wide character set is "auto; currently UTF-32".

  --

  gdb_7.4-2012.04-0ubuntu2.1_i386.deb:
  -
  $ gdb ./exp
  GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "i686-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /home/sneg/work/edu_cpp/exp...done.
  (gdb) print s
  $1 = 0x80487f8 "ф"
  (gdb) print s2
  $2 = 0x80487fb "표"
  (gdb) show charset
  The host character set is "auto; currently UTF-8".
  The target character set is "auto; currently UTF-8".
  The target wide character set is "auto; currently UTF-32".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1082460/+subscriptions

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

[Touch-packages] [Bug 1336665] Re: [Launcher] Weird bounce back effect when organising items

** Also affects: unity8 (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1336665

Title:
  [Launcher] Weird bounce back effect when organising items

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Steps to repro:

  1) Long press an item in the Launcher (Quicklist appear)
  2) While long pressing start moving the item (drag&drop mode entered). Item 
detaches from its previous place
  3) Drop the item at the top of the icon column to be the topmost.

  Expected behaviour:
  Item animates nice in to its place without any additional movement.

  Actual behaviour:
  Item animates in to its place ok but also whole column of items moves 
downwards and bounces back.

  --
  Desired solution:
  Expected behaviour above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1336665/+subscriptions

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

[Touch-packages] [Bug 1378938] Re: App switcher can be put in a bad state by grabbing the app before it comes into focus

** Also affects: unity8 (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1378938

Title:
  App switcher can be put in a bad state by grabbing the app before it
  comes into focus

Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  It seems it is possible to put the app switcher in an odd 'in-between'
  state through the right combination of taps. To reproduce this, open a
  few apps and:

  1. Swipe from the right to open the app switcher
  2. Tap on an app to focus it and immediately tap on it again and hold down - 
before it comes into focus - don't take your finger off yet
  3. Now swiping up or down will dismiss the app
  4. After that the switcher will be open but all of the previews will appear 
closer to the screen. Tapping the screen won't do anything. Interaction can 
only be restored by swiping from the right again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141006-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: armhf
  Date: Wed Oct  8 16:03:25 2014
  InstallationDate: Installed on 2014-10-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141008-090632)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378938/+subscriptions

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

[Touch-packages] [Bug 1095990] Re: gdb -x uses quadratic time

please could you recheck with 14.10?


** Changed in: gdb (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1095990

Title:
  gdb -x uses quadratic time

Status in “gdb” package in Ubuntu:
  Incomplete

Bug description:
  I have a script, which uses gdb -x to evaluate a large number of
  expressions on a running program. As gdb is processing those
  expressions, it takes longer and longer time to process each line of
  input. This results in the overall time consumption being quadratic in
  the number of input lines.

  I tested the same script on a Fedora install. On Fedora gdb runs
  several orders of magnitude faster.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gdb 7.1-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21
  Uname: Linux 2.6.32-37-generic i686
  Architecture: i386
  Date: Fri Jan  4 10:42:11 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1095990/+subscriptions

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

[Touch-packages] [Bug 1350803] Re: [Spread] Threashold in spread for closing apps should be increased

** Also affects: unity8 (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1350803

Title:
  [Spread] Threashold in spread for closing apps should be increased

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Currently, the close threshold is too small (you can close app with a
  fast swipe even for short distance movement), should be increased

  
  Desired solution:

  Increase the initial threshold (the one that activates closing action)
  by ~50%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1350803/+subscriptions

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

[Touch-packages] [Bug 1230253] Re: Not-so-smart autocomplete

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1230253

Title:
  Not-so-smart autocomplete

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  gdb seems to have several bugs in command line autocomplete.

  Whenever I want to insert a breakpoint and I start typing the file
  name, if the filename contains a dash '-' instead of an underscore
  '_', gdb doesn't autocomplete correctly. It seems that it only
  considers the string after the dash. Example:

  (gdb) break hmi-con
  connection_ptr
hmi-connection.hpp
  construction vtable for std::istream-in-boost::process::pistream  
hmi-connection-state.cpp
  construction vtable for std::ostream-in-boost::process::postream  
hmi-connection-state.h
  hmi-connection.cpp
  (gdb) break hmi-conn
  connection_ptrhmi-connection.cpphmi-connection.hpp
hmi-connection-state.cpp  hmi-connection-state.h
  (gdb) break hmi-conn

  and so on.

  If I just write "break hmi-"[TAB][TAB], gdb will output the whole list of 
symbols for the executable (and ctrl+c is the only way out).
  If I reach the "." ("break hmi-connection."[TAB][TAB]), gdb will again output 
the whole list of symbols for the executable.

  This happens quite often, whenever a filename with dash '-' is
  involved.

  This is a quite severe bug: gdb should (almost) never output the whole
  list of symbols because this simply makes no sense in most of real-
  life situations. It may make sense in a one-file project where the
  list of symbols is just one or two pages long, but for sure it
  shouldn't be printed out with the [TAB][TAB] sequence.

  The sum of these two bugs is devastating: trying to autocomplete a
  filename with a dash often result in a very long wait possibly
  followed by wrong autocomplete suggestions. If the autocomplete is
  successful, however, it may happen that one has pressed [TAB] more
  than two times (due to the latency), and then the full symbol list
  printout kicks in. This is really frustrating and makes gdb
  autocomplete quite unusable.

  Finally, gdb autocomplete is mostly context-free. Whenever I break in
  a function, I'll probably want to inspect some local variable, but gdb
  prints out every possible match, also including library symbols from
  STL, boost, etc.. Some priority to local symbols should be added
  (maybe expanding the search context according to the number of times
  [TAB] is pressed?).

  I'm using GNU gdb (GDB) 7.6-ubuntu under Ubuntu 13.04 Raring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1230253/+subscriptions

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

[Touch-packages] [Bug 1352842] Re: [Spread] Item jumps when drag/swipe to close is activated

** Also affects: unity8 (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1352842

Title:
  [Spread] Item jumps when drag/swipe to close is activated

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  By design there is an initial threshold defined after which swipe to
  close is activated and the application starts to follow users finger.
  This threshold has been defined to prevent accidental closing actions
  when user's intention was to scroll through currently running apps.
  This is working fine and as designed.

  The problem arises in that exact time when the threshold value is
  exceeded. When item starts following the finger movement there is an
  unwanted jump happening. Which I suspect being as much as the
  threshold value is. It's a small jump but still distracting.

  --- 
  Desired solution:
  When threshold exceeded and item starts following the finger it happens 
smoothly without a jump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1352842/+subscriptions

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

[Touch-packages] [Bug 1197027] Re: gdb shows 'inf' when printing long doubles on x86_64

please recheck with 14.10 and gdb-7.8

** Changed in: gdb (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1197027

Title:
  gdb shows 'inf' when printing long doubles on x86_64

Status in “gdb” package in Ubuntu:
  Incomplete

Bug description:
  A test file:
  ---

  #include 
  int main()
  {
long double a = 0x1.29aeffefc8ec645p+12557L;
printf("%Lf\n", a);
  }


  Whilst in gdb (on 32bit):
  ---
  (gdb) p 0x1.29aeffefc8ec645p+12557L
  $1 = 12558.16282653431
  (gdb) p a
  $2 = 1.2565231254743496882989195724989633e+3780
  ---

  Do the same but on gdb 64bit:
  ---
  (gdb) p 0x1.29aeffefc8ec645p+12557L
  $1 = 12558.16282653431
  (gdb) p a
  $2 = inf
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gdb 7.6~20130417-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Jul  2 17:07:07 2013
  InstallationDate: Installed on 2013-06-05 (27 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1197027/+subscriptions

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

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

According to loghtdm.conf it is the unity greeter.

I added the etc/lightdm configs


This is the content of var/lib/AccountService/users/


[com.ubuntu.touch.AccountsService.Sound]
SilentMode=false
IncomingCallSound='/usr/share/sounds/ubuntu/ringtones/Ubuntu.ogg'
IncomingMessageSound='/usr/share/sounds/ubuntu/notifications/Xylo.ogg'

[com.canonical.indicator.sound.AccountsService]
PlayerName='Rhythmbox'
Timestamp=291479336095
Title=''
Artist=''
Album=''
ArtUrl=''
PlayerIcon=<('themed', <['rhythmbox']>)>
Running=true
State='Stopped'

[com.ubuntu.AccountsService.Sound]
Volume=0.1817449951171875
Muted=true

[InputSource0]
xkb=de

[InputSource1]
xkb=us

[InputSource2]
xkb=fr

[User]
XSession=ubuntu
XKeyboardLayouts=
Background=/usr/share/xfce4/backdrops/xubuntu-wallpaper.png
SystemAccount=false

** Attachment added: "lightdm.conf"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+attachment/4264333/+files/lightdm.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393846

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+subscriptions

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

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

** Attachment added: "lightdm-gtk-greeter.conf"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+attachment/4264334/+files/lightdm-gtk-greeter.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393846

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+subscriptions

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

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

** Attachment added: "lightdm-gtk-greeter-ubuntu.conf"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+attachment/4264335/+files/lightdm-gtk-greeter-ubuntu.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393846

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+subscriptions

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

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

** Attachment added: "users.conf"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+attachment/4264336/+files/users.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393846

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+subscriptions

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

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

In lightdm.conf.d I found this file. I assume the file in this directory
represents the selected greeter?

** Attachment added: "10-xubuntu.conf"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+attachment/4264337/+files/10-xubuntu.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393846

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+subscriptions

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

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

I selected the color black as a background recently.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393846

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+subscriptions

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

[Touch-packages] [Bug 1393487] Re: swiping word ribbon to right causes words to be repeated

** Changed in: ubuntu-keyboard
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1393487

Title:
  swiping word ribbon to right causes words to be repeated

Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  rtm build 162 on krillin

  Steps to reproduce:
  - open messaging app
  - type "Hello" in the message field
  - see the word "Hello" show up by itself in the list
  - swipe word ribbon to the right and release
  - now there are 2 "Hello" words in the ribbon
  - continue to swipe and release the word ribbon and you get a repeated word 
each time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1393487/+subscriptions

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

[Touch-packages] [Bug 1372948] Re: Keyboard doesn't auto-capitalize 'I'

** Changed in: ubuntu-keyboard
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1372948

Title:
  Keyboard doesn't auto-capitalize 'I'

Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  In English 'I' is not auto-capitalized.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20140910~rtm-0ubuntu1 
[origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Tue Sep 23 15:44:57 2014
  InstallationDate: Installed on 2014-09-16 (7 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-030205)
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1372948/+subscriptions

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

[Touch-packages] [Bug 1315634] Re: gdb does not show heap arrays in fortran

confirmed. looks like this is an upstream issue, and Suse is carrying a
local patch?


** Changed in: gdb (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gdb (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1315634

Title:
  gdb does not show  heap arrays in fortran

Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  The problem description can be found in many places over the internet, e.g. 
here:
  
http://numericalnoob.blogspot.fi/2012/08/fortran-allocatable-arrays-and-pointers.html
  When debugging simple program

  program test
  integer, parameter :: ndata = 8, ndim = 2
  real :: my_stack(ndata)
  real, allocatable, target:: my_heap(:)
  real, pointer:: my_ptr(:,:,:)
  allocate(my_heap(ndata))
  ! read stuff
  do i=1,ndata
  my_stack(i) = real(i)
  end do
  my_heap = my_stack
  my_ptr(1:ndim,1:ndim,1:ndim) => my_heap
  write(*,*) my_stack
  write(*,*) my_heap
  write(*,*) my_ptr
  end program test

  With gdb from distro (GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7) I get:

  
  Breakpoint 1, test () at test.f90:13
  13write(*,*) my_stack
  (gdb) p my_stack
  $1 = (1, 2, 3, 4, 5, 6, 7, 8)
  (gdb) p my_heap
  $2 = (0)
  (gdb) p my_ptr
  $3 = (( ( 0) ) )
  (gdb) 

  
  With properly compiled gdb on another computer (GNU gdb (GDB) SUSE 
(7.5.1-0.7.29)) i get 

  
  Breakpoint 1, test () at test.f90:13
  13write(*,*) my_stack
  (gdb) p my_stack
  $1 = (1, 2, 3, 4, 5, 6, 7, 8)
  (gdb) p my_heap
  $2 = (1, 2, 3, 4, 5, 6, 7, 8)
  (gdb) p my_ptr
  $3 = (( ( 1, 2) ( 3, 4) ) ( ( 5, 6) ( 7, 8) ) )
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1315634/+subscriptions

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

[Touch-packages] [Bug 1335002] Re: Chinese input method does not work after enable Chinese keyboard in Ubuntu Phone

** Changed in: ubuntu-keyboard
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1335002

Title:
  Chinese input method does not work after enable Chinese keyboard in
  Ubuntu Phone

Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  In Progress

Bug description:
  Reproduce steps:

  1, enable Chinese keyboard in system settings
  2, launch an app can input text like notes
  3, long press global icon and switch Chinese

  Expecting:
  user can input Chinese like press 'n' and 'i' then 你 should show up on 
candidate bar

  Actual:
  no candidate bar, so still input English

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335002/+subscriptions

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

[Touch-packages] [Bug 1347796] Re: Ignore predictions for auto-completion if they're too different from original input

** Changed in: ubuntu-keyboard
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1347796

Title:
  Ignore predictions for auto-completion if they're too different from
  original input

Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  We should measure the Levenshtein distance between the user's input
  and the primary prediction candidate. If this passes a certain
  threshold (meaning that the two are very different) we should disable
  auto-completion and enter the user's word instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1347796/+subscriptions

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

[Touch-packages] [Bug 1385518] Re: Sliding down from backspace key results in continued backspaces

** Changed in: ubuntu-keyboard
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1385518

Title:
  Sliding down from backspace key results in continued backspaces

Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  Steps to reproduce

  1) Type some text into messaging app

  2) Press backspace key and slide down to return and release

  Expected result

  Backspace stops deleting characters

  Actual result

  Backspace continues to delete until it is tapped again

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1385518/+subscriptions

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

[Touch-packages] [Bug 1377755] Re: keyboard layout flickers and hides on gmail

** Changed in: ubuntu-keyboard
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1377755

Title:
  keyboard layout flickers and hides on gmail

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.2 series:
  Fix Committed
Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  build 83 rtm-proposed on krillin

  1) Run the gmail webapp and compose a new message
  2) The "To:" field has focus and the keyboard is showing (url layout with @ 
and .com key)
  3) Tap in "CC:" field

  Expected results:
  keyboard stays visible with same url layout

  Actual results:
  keyboard switches to normal layout, then switches to url layout, then 
disappears

  4) Tap in the "Bcc:" field and no keyboard is shown, Tap back in To: or CC: 
field and no keyboard is shown
  5) Tap in Subject field and keyboard shown in normal layout
  6) Now when switch to to, cc, or bc it works, but normal layout shown first 
then changes to url layout

  Expected Result:
  - if new layout is same as existing layout it shouldnt' first switch back to 
default layout
  - keyboard should not be disappearing

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1377755/+subscriptions

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

[Touch-packages] [Bug 1382596] Re: [Dash] Launcher home button (BFB) and pinned apps visuals incorrect

** Also affects: unity8 (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1382596

Title:
  [Dash] Launcher home button (BFB) and pinned apps visuals incorrect

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  The orange button (home is incorrect (should have rounded corners) and
  the pinned apps should have a white dot on the top left, they
  shouldn´t be cut

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1382596/+subscriptions

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

[Touch-packages] [Bug 1370609] Re: surface position/height is not calculated properly when the wordRibbon is enabled but not visible

** Changed in: ubuntu-keyboard
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1370609

Title:
  surface position/height is not calculated properly when the wordRibbon
  is enabled but not visible

Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  If you have the wordRibbon enabled in the options, but you are using some 
textField that disables it (or some properties), for example entering a wifi 
password from the indicators, when the keyboard hides the mir surface rectangle 
is not calculated properly, and you can see that when the osk disappears a 
white box starts moving from few pixels on top of the keyboard.
  It could be height, it could be y...

  To reproduce:

  - enable word suggestion/completion
  - open network indicator
  - tap on a wifi where you did not set the password

  [now pay attention to the box around the keyboard before you cancel
  the connection dialog]

  - cancel the connection dialog and see the keyboard disappearing

  Actual result:
  Blank rectangle disappearing from few pixels on top of the keyboard

  Expected result:
  No blank rectangle is visible, keyboard disappears beautifully

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1370609/+subscriptions

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

[Touch-packages] [Bug 1384810] Re: "Next" key is too big for keyboard and doesn't translate well

** Changed in: ubuntu-keyboard
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1384810

Title:
  "Next" key is too big for keyboard and doesn't translate well

Status in Address Book App:
  Fix Committed
Status in Ubuntu Keyboard:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in “address-book-app” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “address-book-app” package in Ubuntu RTM:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  In the address book, we replace the enter button with the text "Next"
  as it automatically navigates you to the next field.

  A better solution would be to use an icon that represents Next (some
  kind of forward arrow).

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1384810/+subscriptions

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

[Touch-packages] [Bug 1341125] Re: Cannot enter floating point (double) numbers

this works for me in 14.10

** Also affects: gdb via
   http://sourceware.org/bugzilla/show_bug.cgi?id=17607
   Importance: Unknown
   Status: Unknown

** Changed in: gdb (Ubuntu)
   Importance: Undecided => Low

** Changed in: gdb (Ubuntu)
   Status: New => Triaged

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1341125

Title:
  Cannot enter floating point (double) numbers

Status in GNU Debugger:
  Unknown
Status in “gdb” package in Ubuntu:
  Fix Released

Bug description:
  (gdb) show version 
  GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  (gdb) p 1.0
  Invalid number "1.0".

  Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b
  from today) recognises 1.0 just fine, as a double

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1341125/+subscriptions

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

[Touch-packages] [Bug 1228067] Re: apt-get autoremove after removing "gdb64" removes libc-bin

checked these steps with a fresh 14.10 installation, and I cannot
reproduce this. libc-bin is not offered for removal. closing the issue.

** Changed in: gdb (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1228067

Title:
  apt-get autoremove after removing "gdb64" removes libc-bin

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  If I install "gdb64" on a 64 bit (x)ubuntu and remove it afterwards,
  "apt-get autoremove" removes "libc-bin" -> the system will be
  unusable.

  (I didn't changed anything in /etc/apt/sources.list)

  Description:  Ubuntu 13.04
  Release:  13.04

  gdb64:i386:
    Installed: (none)
    Candidate: 7.6~20130417-0ubuntu1
    Version table:
   7.6~20130417-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages

  The following packages were automatically installed and are no longer 
required:
    gdb:i386 lib64ncurses5:i386 lib64readline6:i386 lib64tinfo5:i386
    libc6-amd64:i386 libexpat1:i386 libpython2.7:i386 libpython2.7-minimal:i386
    libpython2.7-stdlib:i386 libpython3-stdlib:i386 libpython3.3-minimal:i386
    libpython3.3-stdlib:i386 libreadline6:i386 libsqlite3-0:i386
    libssl1.0.0:i386
  Use 'apt-get autoremove' to remove them.
  The following packages will be REMOVED:
    gdb64:i386

  And "apt-get autoremove" breaks with:
  ..
  Errors were encountered while processing:
   libc6-amd64
   libpython2.7:i386
   libpython2.7-stdlib:i386
   libpython3.3-stdlib:i386
   libreadline6:i386
   libsqlite3-0:i386
   libssl1.0.0:i386
   libexpat1:i386
   libpython2.7-minimal:i386
   libpython3.3-minimal:i386
   man-db
   libc-bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1228067/+subscriptions

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

[Touch-packages] [Bug 1296814] Re: When Unity.Session is available, use its API for logging out

** Changed in: indicator-session (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: indicator-session (Ubuntu Trusty)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1296814

Title:
  When Unity.Session is available, use its API for logging out

Status in The Session Menu:
  Fix Released
Status in Unity:
  New
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  New
Status in “unity8-desktop-session” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  In Progress

Bug description:
  The session indicator always uses gnome-session to end the session
  (log out), but gnome-session is not guaranteed to be available under,
  for example, a Unity8 desktop preview session.  It should use Upstart
  where available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/1296814/+subscriptions

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

[Touch-packages] [Bug 1318980] Re: Translations are not shipped

** Changed in: indicator-session (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: indicator-session (Ubuntu Trusty)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-location in
Ubuntu.
https://bugs.launchpad.net/bugs/1318980

Title:
  Translations are not shipped

Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  In Progress

Bug description:
  The current indicator-location package does not seem to ship the built
  translations (.mo files) from the translation sources (.po files) it
  contains in the source tree. As such, its messages appear in English
  regardless of the locale selected.

  It seems that the installation does not correctly build them and does
  not put them in

  $LOCALE_DIR/LC_MESSAGES/$LANG/$INDICATOR_NAME.mo

  Where $LOCALE_DIR is /usr/share/locale and $LANG is the ISO-639
  language code for each locale.

  Instead, it installs a single .mo file in the wrong location:

  $ dpkg -L indicator-location
  [...]
  /usr/share/locale
  /usr/share/locale/LC_MESSAGES
  /usr/share/locale/LC_MESSAGES/indicator-location.mo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1318980/+subscriptions

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

[Touch-packages] [Bug 1301699] Re: Indicators do not show in Pantheon

** Changed in: indicator-session (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: indicator-session (Ubuntu Trusty)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1301699

Title:
  Indicators do not show in Pantheon

Status in elementary OS:
  Fix Released
Status in Application Indicators:
  New
Status in The Date and Time Indicator:
  New
Status in Network Menu:
  New
Status in The Session Menu:
  New
Status in Sound Menu:
  New
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  In Progress

Bug description:
  It looks like "OnlyShowIn=Unity;GNOME;" has been added to indicator-
  datetime, indicator-session, and indicator-sound

  We should provide a patch to add "Pantheon" to that list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1301699/+subscriptions

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

[Touch-packages] [Bug 1390905] Re: gdb list not from the first line

2014-11-20 Thread herozem

here is a test case:

```c
#include 

int maxsubsum(const int a[], int left, int right) 
{
  int maxleftsum, maxrightsum;
  int maxleftbordersum, maxrightbordersum;
  int leftbordersum, rightbordersum;
  int center, i;

  if (left == right) {
// base case
if (a[left] > 0) {
  return a[left];
} else {
  return (0);
}
  }

  center = (left + right)/2;
  maxleftsum = maxsubsum(a, left, center);
  maxrightsum = maxsubsum(a, center, right);

  maxleftbordersum = 0;
  leftbordersum = 0;
  for (i = center; i >= left; i--) {
leftbordersum += a[i];
if( leftbordersum > maxleftbordersum ) {
  maxleftbordersum = leftbordersum;
}
  }

  maxrightbordersum = 0;
  rightbordersum = 0;
  for (i = center+i; i <= right; i++) {
rightbordersum += a[i];
if (rightbordersum > maxrightbordersum) {
  maxrightbordersum = rightbordersum;
}
  }

  return max_in3(maxleftsum, maxrightsum, maxleftbordersum+maxrightbordersum);
}

int max_subsequence_sum(const int a[], int n)
{
  return maxsubsum(a, 0, n-1);
}

int max_in3(int a, int b, int c)
{
  a = a > b? a: b;
  a = a > c? a: c;
  return a;
}

int main(void)
{
  int nums[] = { 1, 2, 3, -7, 8 };
  max_subsequence_sum(nums, 5);
  return 0;
}
```

first, compile it with -g option: `gcc -g max_sub.c`, and then debug
`gdb ./a.out`

when I type list command in gdb, it will display:

```shell
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./a.out...done.
(gdb) list
49  int max_in3(int a, int b, int c)
50  {
51a = a > b? a: b;
52a = a > c? a: c;
53return a;
54  }
55  
56  int main(void)
57  {
58int nums[] = { 1, 2, 3, -7, 8 };
(gdb) 

```

it's not list from the 1st line.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1390905

Title:
  gdb list not from the first line

Status in “gdb” package in Ubuntu:
  Incomplete

Bug description:
  when I use gdb list command, it does not list source code from the
  first line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1390905/+subscriptions

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

[Touch-packages] [Bug 1296814] Re: When Unity.Session is available, use its API for logging out

** Description changed:

+ [Impact]
+ 
  The session indicator always uses gnome-session to end the session (log
  out), but gnome-session is not guaranteed to be available under, for
  example, a Unity8 desktop preview session.  It should use Upstart where
  available.
+ 
+ [Test Case]
+ 
+ Install unity8-desktop-session and choose to log in to that session from
+ the LightDM login screen.  You should be able to select "log out" from
+ the session-indicator indicator and have it bring you back to the login
+ screen.
+ 
+ [Regression Potential]
+ 
+ In the worst case this change could affect log out operations from
+ regular Unity 7 sessions and potentially other sessions that use the
+ session indicator.  In such a case, the log out operation would fail
+ necessitating a reboot or manual session kill.
+ 
+ [Other Info]
+  
+ This change has been in production use on later releases of Ubuntu (14.10 and 
later) without problems.
+ 
+ Later version of the Unity 8 desktop session do not exit to the LightDM
+ login screen but instead restart Unity 8 and present the Unity 8 login
+ screen.  This is a bug in Unity 8 and not related to indicator-session.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1296814

Title:
  When Unity.Session is available, use its API for logging out

Status in The Session Menu:
  Fix Released
Status in Unity:
  New
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  New
Status in “unity8-desktop-session” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The session indicator always uses gnome-session to end the session
  (log out), but gnome-session is not guaranteed to be available under,
  for example, a Unity8 desktop preview session.  It should use Upstart
  where available.

  [Test Case]

  Install unity8-desktop-session and choose to log in to that session
  from the LightDM login screen.  You should be able to select "log out"
  from the session-indicator indicator and have it bring you back to the
  login screen.

  [Regression Potential]

  In the worst case this change could affect log out operations from
  regular Unity 7 sessions and potentially other sessions that use the
  session indicator.  In such a case, the log out operation would fail
  necessitating a reboot or manual session kill.

  [Other Info]
   
  This change has been in production use on later releases of Ubuntu (14.10 and 
later) without problems.

  Later version of the Unity 8 desktop session do not exit to the
  LightDM login screen but instead restart Unity 8 and present the Unity
  8 login screen.  This is a bug in Unity 8 and not related to
  indicator-session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/1296814/+subscriptions

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

[Touch-packages] [Bug 1388999] Re: gdb is realy slow starting debugging.

is there a standalone test case for this issue? Also is this issue
reported upstream?  I can't see any Ubuntu specific patches which would
affect this.

** Changed in: gdb (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1388999

Title:
  gdb is realy slow starting debugging.

Status in “gdb” package in Ubuntu:
  Incomplete

Bug description:
  On binaries with a lot of symbols a massive performance degradation
  has happened between 14.04 and 14.10

  I have bisected the gdb performance degradation to this gdb commit

  commit 5840bf271c87c3fc14739173fdc91c6a14057130 (refs/bisect/bad)
  Author: H.J. Lu 
  Date:   Wed Jul 16 17:16:24 2014

  Properly match PLT entry against .got.plt relocation
  
  Relocations against .got.plt section may not be in the same order as
  entries in PLT section.  It is incorrect to assume that the Ith reloction
  index against .got.plt section always maps to the (I + 1)th entry in PLT
  section.  This patch matches the .got.plt relocation offset/index in PLT
  entry against the index in .got.plt relocation table.  It only checks
  R_*_JUMP_SLOT and R_*_IRELATIVE relocations.  It ignores R_*_TLS_DESC
  and R_*_TLSDESC relocations since they have different PLT entries.
  
  bfd/
  
  PR binutils/17154
  * elf32-i386.c (elf_i386_plt_sym_val): Only match R_*_JUMP_SLOT
  and R_*_IRELATIVE relocation offset with PLT entry.
  * elf64-x86-64.c (elf_x86_64_plt_sym_val): Likewise.
  (elf_x86_64_plt_sym_val_offset_plt_bnd): New.
  (elf_x86_64_get_synthetic_symtab): Use it.
  
  ld/testsuite/
  
  PR binutils/17154
  * ld-ifunc/pr17154-i386.d: New file.
  * ld-ifunc/pr17154-x86-64.d: Likewise.
  * ld-ifunc/pr17154-x86.s: Likewise.
  * ld-x86-64/bnd-ifunc-2.d: Likewise.
  * ld-x86-64/bnd-ifunc-2.s: Likewise.
  * ld-x86-64/mpx.exp: Run bnd-ifunc-2.
  * ld-x86-64/tlsdesc-nacl.pd: Updated.
  * ld-x86-64/tlsdesc.pd: Likewise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gdb 7.8-1ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-24.32-lowlatency 3.16.4
  Uname: Linux 3.16.0-24-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Nov  3 23:27:53 2014
  InstallationDate: Installed on 2014-07-11 (115 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140710)
  SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1388999/+subscriptions

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

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

2014-11-20 Thread Andrew P.

AccountsService file:
  Background=/usr/share/xfce4/backdrops/xubuntu-wallpaper.png

Lightdm uses this value as user's background at login screen. But 
AccountsService do not support color as "Background" value.
When you change your background to black color the old value is not updated. 
And you will see your old wallpaper at login screen.

Just remove this line or change your wallpaper to desired image.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393846

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+subscriptions

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

[Touch-packages] [Bug 1318980] Re: Translations are not shipped

** Description changed:

+ [Impact]
+ 
  The current indicator-location package does not seem to ship the built
  translations (.mo files) from the translation sources (.po files) it
  contains in the source tree. As such, its messages appear in English
  regardless of the locale selected.
  
  It seems that the installation does not correctly build them and does
  not put them in
  
  $LOCALE_DIR/LC_MESSAGES/$LANG/$INDICATOR_NAME.mo
  
  Where $LOCALE_DIR is /usr/share/locale and $LANG is the ISO-639 language
  code for each locale.
  
  Instead, it installs a single .mo file in the wrong location:
  
  $ dpkg -L indicator-location
  [...]
  /usr/share/locale
  /usr/share/locale/LC_MESSAGES
  /usr/share/locale/LC_MESSAGES/indicator-location.mo
+ 
+ [Test Case]
+ 
+ Change the session locale to a non-English one through System Settings
+ -> Lanuage Support.  Log in to a Unity 7 session and pull down the
+ System Indicator.  The entries should be translated.
+ 
+ [Regression Potential]
+ 
+ It's possible this fix may not fix the translations.
+ 
+ Some locales may have difficulty with the default character rendering
+ engines and subsequently crash the Session Indicator.
+ 
+ [Other Info]
+  
+ The translations already exist for this package, but are being installed 
incorrectly.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-location in
Ubuntu.
https://bugs.launchpad.net/bugs/1318980

Title:
  Translations are not shipped

Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The current indicator-location package does not seem to ship the built
  translations (.mo files) from the translation sources (.po files) it
  contains in the source tree. As such, its messages appear in English
  regardless of the locale selected.

  It seems that the installation does not correctly build them and does
  not put them in

  $LOCALE_DIR/LC_MESSAGES/$LANG/$INDICATOR_NAME.mo

  Where $LOCALE_DIR is /usr/share/locale and $LANG is the ISO-639
  language code for each locale.

  Instead, it installs a single .mo file in the wrong location:

  $ dpkg -L indicator-location
  [...]
  /usr/share/locale
  /usr/share/locale/LC_MESSAGES
  /usr/share/locale/LC_MESSAGES/indicator-location.mo

  [Test Case]

  Change the session locale to a non-English one through System Settings
  -> Lanuage Support.  Log in to a Unity 7 session and pull down the
  System Indicator.  The entries should be translated.

  [Regression Potential]

  It's possible this fix may not fix the translations.

  Some locales may have difficulty with the default character rendering
  engines and subsequently crash the Session Indicator.

  [Other Info]
   
  The translations already exist for this package, but are being installed 
incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1318980/+subscriptions

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

[Touch-packages] [Bug 1390905] Re: gdb list not from the first line

** Changed in: gdb (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1390905

Title:
  gdb list not from the first line

Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  when I use gdb list command, it does not list source code from the
  first line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1390905/+subscriptions

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

[Touch-packages] [Bug 1301699] Re: Indicators do not show in Pantheon

** Description changed:

+ [Impact]
+ 
  It looks like "OnlyShowIn=Unity;GNOME;" has been added to indicator-
  datetime, indicator-session, and indicator-sound
  
  We should provide a patch to add "Pantheon" to that list.
+ 
+ [Test Case]
+ 
+ (1) install the Pantheon desktop sesssion (eg. Elementary OS) and log in
+ (2) verify the appropriate indicator (for this case, session indicator) 
appears
+ (3) install the Unity 7 desktop session and log in
+ (4) verify the indicator still appears
+ 
+ [Regression Potential]
+ 
+ A typo in the modified .desktop file could cause the indicator to not
+ appear in a Ubuntu session such as Unity 7 or Gnome Flashback.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1301699

Title:
  Indicators do not show in Pantheon

Status in elementary OS:
  Fix Released
Status in Application Indicators:
  New
Status in The Date and Time Indicator:
  New
Status in Network Menu:
  New
Status in The Session Menu:
  New
Status in Sound Menu:
  New
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  In Progress

Bug description:
  [Impact]

  It looks like "OnlyShowIn=Unity;GNOME;" has been added to indicator-
  datetime, indicator-session, and indicator-sound

  We should provide a patch to add "Pantheon" to that list.

  [Test Case]

  (1) install the Pantheon desktop sesssion (eg. Elementary OS) and log in
  (2) verify the appropriate indicator (for this case, session indicator) 
appears
  (3) install the Unity 7 desktop session and log in
  (4) verify the indicator still appears

  [Regression Potential]

  A typo in the modified .desktop file could cause the indicator to not
  appear in a Ubuntu session such as Unity 7 or Gnome Flashback.

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1301699/+subscriptions

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

[Touch-packages] [Bug 1394583] Re: evolution-calendar-factory crashed with SIGSEGV in id_hash()

2014-11-20 Thread Apport retracing service

*** This bug is a duplicate of bug 1301120 ***
https://bugs.launchpad.net/bugs/1301120

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 #1301120, 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/1394583/+attachment/4264351/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1394583/+attachment/4264353/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1394583/+attachment/4264355/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1394583/+attachment/4264356/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1394583/+attachment/4264357/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1394583/+attachment/4264358/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1394583/+attachment/4264359/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1301120

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1394583

Title:
  evolution-calendar-factory crashed with SIGSEGV in id_hash()

Status in “evolution-data-server” package in Ubuntu:
  New

Bug description:
  I actually don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  Uname: Linux 3.15.0-031500-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Nov 20 13:33:12 2014
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  InstallationDate: Installed on 2014-01-22 (301 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  SegvAnalysis:
   Segfault happened at: 0x7fa729ad0959 :mov(%rdi),%rdi
   PC (0x7fa729ad0959) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   id_hash (key=0x0) at e-data-cal-view.c:138
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   notify_add_component (comp=0x7fa6d0811770, view=0x7fa6d0020e50) at 
e-data-cal-view.c:728
   e_data_cal_view_notify_components_added (view=view@entry=0x7fa6d0020e50, 
ecalcomponents=ecalcomponents@entry=0x7fa6d400abb0) at e-data-cal-view.c:1180
   e_cal_backend_http_start_view (backend=, 
query=0x7fa6d0020e50) at e-cal-backend-http.c:1171
  Title: evolution-calendar-factory crashed with SIGSEGV in id_hash()
  UpgradeStatus: Upgraded to trusty on 2014-07-01 (142 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1394583/+subscriptions

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

[Touch-packages] [Bug 1353613] Re: webbrowser-app crashed with SIGABRT in __run_exit_handlers()

2014-11-20 Thread Launchpad Bug Tracker

*** This bug is a duplicate of bug 1332800 ***
https://bugs.launchpad.net/bugs/1332800

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1353613

Title:
  webbrowser-app crashed with SIGABRT in __run_exit_handlers()

Status in “webbrowser-app” package in Ubuntu:
  Confirmed

Bug description:
  This app crash and block nouveau driver and freeze the X server, only
  can access to tty console but can't recover graphic mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: webbrowser-app 0.23+14.04.20140428-0ubuntu1
  Uname: Linux 3.6.11 x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Aug  6 12:28:33 2014
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2014-07-30 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f335fe956c8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  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/webbrowser-app/+bug/1353613/+subscriptions

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

[Touch-packages] [Bug 1388887] Re: two cursors instead of one

2014-11-20 Thread Christopher Barrington-Leigh

Thanks! 
I do use external screen rotation when I'm docked.
I hadn't noticed a simple association, but that might be at least one trigger 
for the problem.

Also, trying these steps from the other bug:

xrandr --output LVDS1 --rotate left

# do something, click a few buttons...

xrandr --output LVDS1 --rotate normal

did cause a double cursor for me just now.

So this is likely it. Does that mean we can easily get a fix in  14.10?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  two cursors instead of one

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading from 14.04 to 14.10, I sometimes (not sure what
  triggers or fixes it) have a double cursor. It persists across
  applications and the desktop.  When I do a screen capture, the cursor
  is not visible.

  There is one cursor in the right place, and then below and to the
  right of it is another cursor, pointing at a different angle, that
  follows it around everywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  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
  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: Mon Nov  3 10:44:58 2014
  DistUpgraded: 2014-10-31 16:06:04,383 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.18, 3.13.0-39-generic, x86_64: installed
   virtualbox, 4.3.18, 3.16.0-24-generic, x86_64: installed
  DpkgLog:
   
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2014-08-21 (74 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 34372VU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=5bbcb663-813b-4d47-b431-9d7f27eb691d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-31 (2 days ago)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34372VU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn34372VU:pvrThinkPadX230Tablet:rvnLENOVO:rn34372VU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 34372VU
  dmi.product.version: ThinkPad X230 Tablet
  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 Oct 31 16:14:19 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/137/+subscriptions

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

[Touch-packages] [Bug 1311165] Re: timezone incorrectly modified when editing/creating google calendar event

2014-11-20 Thread Bill Filler

** Also affects: ubuntu-calendar-app
   Importance: Undecided
   Status: New

** Changed in: ubuntu-calendar-app
   Importance: Undecided => High

** Changed in: qtorganizer5-eds (Ubuntu)
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtorganizer5-eds in
Ubuntu.
https://bugs.launchpad.net/bugs/1311165

Title:
  timezone incorrectly modified when editing/creating google calendar
  event

Status in Qt Organizer - EDS plugin:
  Fix Released
Status in Calendar application for Ubuntu devices:
  New
Status in Ubuntu UI Toolkit:
  Fix Released
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed

Bug description:
  We are not preserving the time zone of a calendar event after editing
  it.

  - Create an event in Google Calendar (using browser calendar.google.com), at 
12pm local time, call it "Test"
  - Ensure your timezone on device is set to your correct timezone (UTC -4 in 
my case) by accessing system-settings
  - Import Calendar from Google account (by setting up online account for 
Google)
  - Verify the "Test" event shows up correctly in Calendar app at 12pm
  - Now edit the event and change the description to "Test, 123" and save the 
event.
  - After the sync runs (wait one or two minutes), open your browser and reload 
your google calendar

  Expected result:
  - Event should be called "Test, 123" and still at 12pm local time

  Actual results:
  - Event is correctly updated to show "Test, 123" but time has shifted to 3pm 
local time

  We should not be modifying the timezone when editing the event

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtorganizer5-eds/+bug/1311165/+subscriptions

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

[Touch-packages] [Bug 1311165] Re: timezone incorrectly modified when editing/creating google calendar event

2014-11-20 Thread Bill Filler

This is still broken on rtm and vivid releases. I don't know if the
problem exists on the qtorganizer5-eds side or the calendar app side.

Here is the problem and how to reproduce:


Problem 1:
1) my current timezone on the phone is set for UTC -5 (EST)
2) sync google calendar
3) create a new calendar event in Calendar app for 8am and save it on the 
Google calendar
4) wait for sync to happen
5) open Google calendar in browser

Expected results:
- new event should be seen at 8am on Google calendar in browser

Actual results:
- new event is seen at 1pm on Google calendar in browser

Problem 2:
1) my current timezone on the phone is set for UTC -5 (EST)
2) sync google calendar
3) edit an event in the calendar app that came from google calendar, and change 
it's description
4) wait for sync to happen
5) open Google calendar in browser

Expected results:
- calendar event viewed in Google calendar on browser should remain at original 
time and show an updated description

Actual results:
- calendar event is moved 5 hrs forward in Google calendar

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtorganizer5-eds in
Ubuntu.
https://bugs.launchpad.net/bugs/1311165

Title:
  timezone incorrectly modified when editing/creating google calendar
  event

Status in Qt Organizer - EDS plugin:
  Fix Released
Status in Calendar application for Ubuntu devices:
  New
Status in Ubuntu UI Toolkit:
  Fix Released
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed

Bug description:
  We are not preserving the time zone of a calendar event after editing
  it.

  - Create an event in Google Calendar (using browser calendar.google.com), at 
12pm local time, call it "Test"
  - Ensure your timezone on device is set to your correct timezone (UTC -4 in 
my case) by accessing system-settings
  - Import Calendar from Google account (by setting up online account for 
Google)
  - Verify the "Test" event shows up correctly in Calendar app at 12pm
  - Now edit the event and change the description to "Test, 123" and save the 
event.
  - After the sync runs (wait one or two minutes), open your browser and reload 
your google calendar

  Expected result:
  - Event should be called "Test, 123" and still at 12pm local time

  Actual results:
  - Event is correctly updated to show "Test, 123" but time has shifted to 3pm 
local time

  We should not be modifying the timezone when editing the event

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtorganizer5-eds/+bug/1311165/+subscriptions

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

[Touch-packages] [Bug 1394469] [NEW] "VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct

2014-11-20 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

== Comment: #0 - SONG YANG  - 2014-11-18 22:06:44 ==
---Problem Description---
"VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct 
 
---uname output---
Linux c910f03c05k05 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 
2014 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = P8 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
# apt-file find /etc/os-release 
base-files: /etc/os-release
# cat /etc/os-release  
NAME="Ubuntu"
VERSION="14.04.1 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.1 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";


according to the manpage of /etc/os-release, the "VERSION_ID" should be 
"14.04.1", however it still keeps "14.04",which is confused for the system 
management tool developers. The "VERSION" and "PRETTY_NAME" seems to be 
correct, however, these 2 fields are for presentation to the user, which is not 
suitable for the script parsing.

The following lines are excerpted from the os-release DOC:
ID=
A lower-case string (no spaces or other characters outside of 0-9, a-z, ".", 
"_" and "-") identifying the operating system, excluding any version 
information and suitable for processing by scripts or usage in generated 
filenames. If not set, defaults to "ID=linux". Example: "ID=fedora" or 
"ID=debian".

ID_LIKE=
A space-separated list of operating system identifiers in the same syntax as 
the ID= setting. It should list identifiers of operating systems that are 
closely related to the local operating system in regards to packaging and 
programming interfaces, for example listing one or more OS identifiers the 
local OS is a derivative from. An OS should generally only list other OS 
identifiers it itself is a derivative of, and not any OSes that are derived 
from it, though symmetric relationships are possible. Build scripts and similar 
should check this variable if they need to identify the local operating system 
and the value of ID= is not recognized. Operating systems should be listed in 
order of how closely the local operating system relates to the listed ones, 
starting with the closest. This field is optional. Example: for an operating 
system with "ID=centos", an assignment of "ID_LIKE="rhel fedora"" would be 
appropriate. For an operating system with "ID=ubuntu", an assignment of 
"ID_LIKE=deb
 ian" is appropriate.

VERSION_ID=
A lower-case string (mostly numeric, no spaces or other characters outside of 
0-9, a-z, ".", "_" and "-") identifying the operating system version, excluding 
any OS name information or release code name, and suitable for processing by 
scripts or usage in generated filenames. This field is optional. Example: 
"VERSION_ID=17" or "VERSION_ID=11.04".

 
Install method: ALL
 
Install disk info: NA
 
Install ISO Information: ubuntu-14.04.1-server-ppc64el.iso
 
Userspace tool common name: NA 
 
The userspace tool has the following bit modes: both 

Userspace rpm: NA

Userspace tool obtained from project website:  base-files

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: architecture-all bot-comment bugnameltc-119066 severity-critical 
targetmilestone-inin---
-- 
"VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct
https://bugs.launchpad.net/bugs/1394469
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to base-files in Ubuntu.

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

[Touch-packages] [Bug 1248729] Re: maliit-server doesn't respect the QT_LOAD_TESTABILITY environment variable

** Patch added: "0013-check-testability-environment-variable.patch"
   
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1248729/+attachment/4264373/+files/0013-check-testability-environment-variable.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to maliit-framework in
Ubuntu.
https://bugs.launchpad.net/bugs/1248729

Title:
  maliit-server doesn't respect the QT_LOAD_TESTABILITY environment
  variable

Status in Ubuntu Keyboard:
  Invalid
Status in “maliit-framework” package in Ubuntu:
  In Progress

Bug description:
  For testing we need to restart maliit-server with testability enabled, for 
the likes of unity8 we can do something like:
    $ stop unity8 && start unity8 QT_LOAD_TESTABILITY=1

  Currently this does't work for the maliit-server and I've had to
  resort to writing an override file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1248729/+subscriptions

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

[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope

2014-11-20 Thread Pete Woods

** Changed in: unity-scopes-shell (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1394155

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  In Progress

Bug description:
  On krillin:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap "Tell me more..."
  4) Scroll to the bottom again
  5) Tap "Finished"

  Hard lock / sometimes crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1394155/+subscriptions

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

[Touch-packages] [Bug 1394469] Re: "VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct

2014-11-20 Thread Brian Murray

** Package changed: ubuntu => base-files (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1394469

Title:
  "VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct

Status in “base-files” package in Ubuntu:
  New

Bug description:
  == Comment: #0 - SONG YANG  - 2014-11-18 22:06:44 ==
  ---Problem Description---
  "VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct 
   
  ---uname output---
  Linux c910f03c05k05 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 
2014 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  # apt-file find /etc/os-release 
  base-files: /etc/os-release
  # cat /etc/os-release  
  NAME="Ubuntu"
  VERSION="14.04.1 LTS, Trusty Tahr"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 14.04.1 LTS"
  VERSION_ID="14.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

  
  according to the manpage of /etc/os-release, the "VERSION_ID" should be 
"14.04.1", however it still keeps "14.04",which is confused for the system 
management tool developers. The "VERSION" and "PRETTY_NAME" seems to be 
correct, however, these 2 fields are for presentation to the user, which is not 
suitable for the script parsing.

  The following lines are excerpted from the os-release DOC:
  ID=
  A lower-case string (no spaces or other characters outside of 0-9, a-z, ".", 
"_" and "-") identifying the operating system, excluding any version 
information and suitable for processing by scripts or usage in generated 
filenames. If not set, defaults to "ID=linux". Example: "ID=fedora" or 
"ID=debian".

  ID_LIKE=
  A space-separated list of operating system identifiers in the same syntax as 
the ID= setting. It should list identifiers of operating systems that are 
closely related to the local operating system in regards to packaging and 
programming interfaces, for example listing one or more OS identifiers the 
local OS is a derivative from. An OS should generally only list other OS 
identifiers it itself is a derivative of, and not any OSes that are derived 
from it, though symmetric relationships are possible. Build scripts and similar 
should check this variable if they need to identify the local operating system 
and the value of ID= is not recognized. Operating systems should be listed in 
order of how closely the local operating system relates to the listed ones, 
starting with the closest. This field is optional. Example: for an operating 
system with "ID=centos", an assignment of "ID_LIKE="rhel fedora"" would be 
appropriate. For an operating system with "ID=ubuntu", an assignment of 
"ID_LIKE=debian" is appropriate.

  VERSION_ID=
  A lower-case string (mostly numeric, no spaces or other characters outside of 
0-9, a-z, ".", "_" and "-") identifying the operating system version, excluding 
any OS name information or release code name, and suitable for processing by 
scripts or usage in generated filenames. This field is optional. Example: 
"VERSION_ID=17" or "VERSION_ID=11.04".

   
  Install method: ALL
   
  Install disk info: NA
   
  Install ISO Information: ubuntu-14.04.1-server-ppc64el.iso
   
  Userspace tool common name: NA 
   
  The userspace tool has the following bit modes: both 

  Userspace rpm: NA

  Userspace tool obtained from project website:  base-files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1394469/+subscriptions

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

[Touch-packages] [Bug 1394469] Re: "VERSION_ID" in /etc/os-release does not include point release number

2014-11-20 Thread Brian Murray

This is also true of Ubuntu 12.04 and I image other LTS releases with
point releases.

** Summary changed:

- "VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct
+ "VERSION_ID" in /etc/os-release does not include point release number

** Tags added: precise trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1394469

Title:
  "VERSION_ID" in /etc/os-release does not include point release number

Status in “base-files” package in Ubuntu:
  New

Bug description:
  == Comment: #0 - SONG YANG  - 2014-11-18 22:06:44 ==
  ---Problem Description---
  "VERSION_ID" in /etc/os-release of ubuntu 14.04.1 is not correct 
   
  ---uname output---
  Linux c910f03c05k05 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 
2014 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  # apt-file find /etc/os-release 
  base-files: /etc/os-release
  # cat /etc/os-release  
  NAME="Ubuntu"
  VERSION="14.04.1 LTS, Trusty Tahr"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 14.04.1 LTS"
  VERSION_ID="14.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

  
  according to the manpage of /etc/os-release, the "VERSION_ID" should be 
"14.04.1", however it still keeps "14.04",which is confused for the system 
management tool developers. The "VERSION" and "PRETTY_NAME" seems to be 
correct, however, these 2 fields are for presentation to the user, which is not 
suitable for the script parsing.

  The following lines are excerpted from the os-release DOC:
  ID=
  A lower-case string (no spaces or other characters outside of 0-9, a-z, ".", 
"_" and "-") identifying the operating system, excluding any version 
information and suitable for processing by scripts or usage in generated 
filenames. If not set, defaults to "ID=linux". Example: "ID=fedora" or 
"ID=debian".

  ID_LIKE=
  A space-separated list of operating system identifiers in the same syntax as 
the ID= setting. It should list identifiers of operating systems that are 
closely related to the local operating system in regards to packaging and 
programming interfaces, for example listing one or more OS identifiers the 
local OS is a derivative from. An OS should generally only list other OS 
identifiers it itself is a derivative of, and not any OSes that are derived 
from it, though symmetric relationships are possible. Build scripts and similar 
should check this variable if they need to identify the local operating system 
and the value of ID= is not recognized. Operating systems should be listed in 
order of how closely the local operating system relates to the listed ones, 
starting with the closest. This field is optional. Example: for an operating 
system with "ID=centos", an assignment of "ID_LIKE="rhel fedora"" would be 
appropriate. For an operating system with "ID=ubuntu", an assignment of 
"ID_LIKE=debian" is appropriate.

  VERSION_ID=
  A lower-case string (mostly numeric, no spaces or other characters outside of 
0-9, a-z, ".", "_" and "-") identifying the operating system version, excluding 
any OS name information or release code name, and suitable for processing by 
scripts or usage in generated filenames. This field is optional. Example: 
"VERSION_ID=17" or "VERSION_ID=11.04".

   
  Install method: ALL
   
  Install disk info: NA
   
  Install ISO Information: ubuntu-14.04.1-server-ppc64el.iso
   
  Userspace tool common name: NA 
   
  The userspace tool has the following bit modes: both 

  Userspace rpm: NA

  Userspace tool obtained from project website:  base-files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1394469/+subscriptions

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

[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope

2014-11-20 Thread Pete Woods

** Description changed:

- On krillin:
+ On krillin r165:
  
  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap "Tell me more..."
  4) Scroll to the bottom again
  5) Tap "Finished"
  
- Hard lock / sometimes crash.
+ Crash!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1394155

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  In Progress

Bug description:
  On krillin r165:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap "Tell me more..."
  4) Scroll to the bottom again
  5) Tap "Finished"

  Crash!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1394155/+subscriptions

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

[Touch-packages] [Bug 1394479] Re: [design] Add ability to place text in emblem position

2014-11-20 Thread kevin gunn

** Summary changed:

- Add ability to place text in emblem position
+ [design] Add ability to place text in emblem position

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1394479

Title:
  [design] Add ability to place text in emblem position

Status in Ubuntu UX bugs:
  New
Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Category renders will display an image as the "emblem" at the right
  end of the title.  It should be possible to place text there instead
  of or in addition to the image.  Thus, the emblem should be have like
  the attributes.

  Example use case: The Gmail scope displays the time of an email in the
  emblem position, with the sender as the title.  Currently, this is
  done with an SVG image displaying the text.  However, this means the
  text size and alignment is incorrect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1394479/+subscriptions

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

[Touch-packages] [Bug 1394155] Re: Crash of unity8-dash possible through Today scope

2014-11-20 Thread Pete Woods

** Summary changed:

- Deadlock / crash of the dash possible through Today scope
+ Crash of unity8-dash possible through Today scope

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1394155

Title:
  Crash of unity8-dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  In Progress

Bug description:
  On krillin r165:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap "Tell me more..."
  4) Scroll to the bottom again
  5) Tap "Finished"

  Crash!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1394155/+subscriptions

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

[Touch-packages] [Bug 1390067] Re: Silent mode does not change the icon to the mute icon (or like)

2014-11-20 Thread Ted Gould

** No longer affects: indicator-sound

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1390067

Title:
  Silent mode does not change the icon to the mute icon (or like)

Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  Setting the phone on silent mode, the user should have some feedback
  to whether it is enabled from the panel icon. Currently we still show
  what volume the phone is set to.

  See https://wiki.ubuntu.com/Sound

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1390067/+subscriptions

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

[Touch-packages] [Bug 1394614] [NEW] Cached results stay in scopes even with no internet

2014-11-20 Thread Omer Akram

Public bug reported:

I am testing the latest image and as per the test plan, if internet is
disabled there are cached results in a scope they should vanish as we
refresh the scope but right now that's not the case.

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Thu Nov 20 15:06:59 2014
InstallationDate: Installed on 2014-11-19 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141119-181707)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1394614

Title:
  Cached results stay in scopes even with no internet

Status in “unity8” package in Ubuntu:
  New

Bug description:
  I am testing the latest image and as per the test plan, if internet is
  disabled there are cached results in a scope they should vanish as we
  refresh the scope but right now that's not the case.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 20 15:06:59 2014
  InstallationDate: Installed on 2014-11-19 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141119-181707)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1394614/+subscriptions

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

[Touch-packages] [Bug 1394612] [NEW] apparmor-utils on 14.04 aka trusty is completely unusable

2014-11-20 Thread Peter Maloney

Public bug reported:

The version of apparmor-utils in Ubuntu 14.04 are completely unusable.
(2.8.95~2430-0ubuntu5)

jjohansen on IRC has provided me with this repo instead, which works far
better (2.8.98-0ubuntu2+utopic.backport). So I suggest you review this
or whatever process is normally used, work with the developers, and
update it urgently... apparmor tools are completely broken.

https://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-backports/

Here is the most basic example possible... I have nothing complicated in
this system. It doesn't have any custom profiles, and I have copied
/bin/bash to my home to make a profile. Then I run the bash and run "ls"
to generate some logs. And then hit "s" to search.

# aa-genprof /root/basharmor
Writing updated profile for /root/basharmor.
Setting /root/basharmor to complain mode.

Before you begin, you may wish to check if a
profile already exists for the application you
wish to confine. See the following wiki page for
more information:
http://wiki.apparmor.net/index.php/Profiles

Please start the application to be profiled in
another window and exercise its functionality now.

Once completed, select the "Scan" option below in
order to scan the system logs for AppArmor events.

For each AppArmor event, you will be given the
opportunity to choose whether the access should be
allowed or denied.

Profiling: /root/basharmor

[(S)can system log for AppArmor events] / (F)inish
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
  File "/usr/sbin/aa-genprof", line 150, in 
lp_ret = apparmor.do_logprof_pass(logmark, passno)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2246, in 
do_logprof_pass
read_profiles()
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2564, in 
read_profiles
read_profile(profile_dir + '/' + file, True)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2590, in 
read_profile
profile_data = parse_profile_data(data, file, 0)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2700, in 
parse_profile_data
filelist[file]['profiles'][profile][hat] = True
TypeError: 'bool' object does not support item assignment

aa-logprof doesn't crash the same way with this bash example, but there
are lots of ways to crash it too.

Here is an example of the most ridiculous error I got (which was
probably actually the ppa:apparmor-dev/apparmor-devel version
2.8.96~2541-0ubuntu3+abstract3, which was actually better than
2.8.95~2430-0ubuntu5). Just simply running "aa-logprof" would gtive me
this exception:

root@ganglia:/etc/apparmor.d# aa-logprof
Reading log entries from /var/log/audit/audit.log.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apparmor/severity.py", line 181, in 
load_variables
for line in f_in:
  File "/usr/lib/python3.4/codecs.py", line 704, in __next__
return next(self.reader)
  File "/usr/lib/python3.4/codecs.py", line 635, in __next__
line = self.readline()
  File "/usr/lib/python3.4/codecs.py", line 548, in readline
data = self.read(readsize, firstline=True)
  File "/usr/lib/python3.4/codecs.py", line 494, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb3 in position 41: 
invalid start byte

And then to figure out which file it was trying to read, I added another
exception that contains the name:

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/aa-logprof", line 52, in 
apparmor.do_logprof_pass(logmark)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2261, in 
do_logprof_pass
handle_children('', '', root)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1236, in 
handle_children
sev_db.load_variables(profile)
  File "/usr/lib/python3/dist-packages/apparmor/severity.py", line 207, in 
load_variables
raise Exception("failed reading prof_path = %s, e = %s" % (prof_path, e))
Exception: failed reading prof_path = /usr/sbin/apache2, e = 'utf-8' codec 
can't decode byte 0xb3 in position 41: invalid start byte


It is reading the apache2 binary! not a profile! Of course it can't decode it 
into UTF-8. So the backport is necessary. The newer devel one for Trusty is not 
good enough.

Please please upgrade the tools available there is no reason to
stick with this version. It is not like some "old stable" version... it
is the most bleeding edge possible, right after the conversion from perl
to python without any bug fixes. I use apparmor everywhere, and find
this to be encredibly annoying. (but at least for me, this backports ppa
will do well enough)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s

[Touch-packages] [Bug 1394081] Re: Add manual options for administrators

2014-11-20 Thread Thomas Hood

The proper way for the admin to stop /etc/resolv.conf from being updated
by resolvconf is for him or her to remove the symbolic link
/etc/resolv.conf -> ../run/resolvconf/resolv.conf. The resolvconf
program only ever writes to the target of that symlink. Thus, in the
absence of that link, resolvconf has no effect on resolv.conf.

Yes, Ubuntu's dhclient-enter-hooks.d/resolvconf checks /etc/resolv.conf
and stomps on it if no symbolic link is there. That is different from
what the Debian version of the script does and is a departure from the
Debian convention. That has been complained about in bug #1385010.

Can you please describe more fully what you perceive to be the problem?
That's not clear to me yet.

In advance I will say that it is supposed to be the case that if the
admin has removed the symlink at /etc/resolv.conf then upgrading the
package does not restore the symlink.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1394081

Title:
  Add manual options for administrators

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  
  Currently - trusty LTS - there is no way to turn off the regeneration of 
/etc/resolv.conf that would survive a package upgrade. 

  - you cannot remove resolvconf as it is needed by minimal
  - you cannot disable-upgrades as this flag is removed by reboots
  - if you disable the resolvconf job in upstart package upgrade will reset the 
disable-upgrade flags
  - if you hack the scripts - it will only last until the next upgrade

  There are two ways to ensure that admins willing to turn it off can do
  so:

  First solution: add a run=no to /etc/default/resolvconf and bail out
  if it is set.

  The second solution is more subtile. In /etc/network/if-
  up.d/000resolvconf you will find this line:

  [ -x /sbin/resolvconf ] || exit 0

  While in /etc/dhcp/dhclient-enter-hooks.d/resolvconf it says

  if [ -x /sbin/resolvconf ] && [ -L /etc/resolv.conf ]; then

  Way more clever! So if you do not want to implement the default
  option, why not check if its a link all the way? So at least a conf
  gets not overwritten once the admin wrote his own.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1394081/+subscriptions

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

[Touch-packages] [Bug 1394612] Re: apparmor-utils on 14.04 aka trusty is completely unusable

2014-11-20 Thread Peter Maloney

And here's another fun result. I don't know why it did this. It created
43,000 lines of /usr/sbin/apache2//null-... stuff in the aa-status.

** Attachment added: "aa-status-4M.txt.gz"

https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1394612/+attachment/4264398/+files/aa-status-4M.txt.gz

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1394612

Title:
apparmor-utils on 14.04 aka trusty is completely unusable

Status in “apparmor” package in Ubuntu:
New

Bug description:
The version of apparmor-utils in Ubuntu 14.04 are completely unusable.
(2.8.95~2430-0ubuntu5)

jjohansen on IRC has provided me with this repo instead, which works
far better (2.8.98-0ubuntu2+utopic.backport). So I suggest you review
this or whatever process is normally used, work with the developers,
and update it urgently... apparmor tools are completely broken.

https://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-
backports/

Here is the most basic example possible... I have nothing complicated
in this system. It doesn't have any custom profiles, and I have copied
/bin/bash to my home to make a profile. Then I run the bash and run
"ls" to generate some logs. And then hit "s" to search.

# aa-genprof /root/basharmor
Writing updated profile for /root/basharmor.
Setting /root/basharmor to complain mode.

Before you begin, you may wish to check if a
profile already exists for the application you
wish to confine. See the following wiki page for
more information:
http://wiki.apparmor.net/index.php/Profiles

Please start the application to be profiled in
another window and exercise its functionality now.

Once completed, select the "Scan" option below in
order to scan the system logs for AppArmor events.

For each AppArmor event, you will be given the
opportunity to choose whether the access should be
allowed or denied.

Profiling: /root/basharmor

[(S)can system log for AppArmor events] / (F)inish
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
File "/usr/sbin/aa-genprof", line 150, in
lp_ret = apparmor.do_logprof_pass(logmark, passno)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2246, in
do_logprof_pass
read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2564, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2590, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2700, in
parse_profile_data
filelist[file]['profiles'][profile][hat] = True
TypeError: 'bool' object does not support item assignment

aa-logprof doesn't crash the same way with this bash example, but
there are lots of ways to crash it too.

Here is an example of the most ridiculous error I got (which was
probably actually the ppa:apparmor-dev/apparmor-devel version
2.8.96~2541-0ubuntu3+abstract3, which was actually better than
2.8.95~2430-0ubuntu5). Just simply running "aa-logprof" would gtive me
this exception:

root@ganglia:/etc/apparmor.d# aa-logprof
Reading log entries from /var/log/audit/audit.log.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apparmor/severity.py", line 181, in
load_variables
for line in f_in:
File "/usr/lib/python3.4/codecs.py", line 704, in __next__
return next(self.reader)
File "/usr/lib/python3.4/codecs.py", line 635, in __next__
line = self.readline()
File "/usr/lib/python3.4/codecs.py", line 548, in readline
data = self.read(readsize, firstline=True)
File "/usr/lib/python3.4/codecs.py", line 494, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb3 in position 41:
invalid start byte

And then to figure out which file it was trying to read, I added
another exception that contains the name:

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 52, in
apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2261, in
do_logprof_pass
handle_children('', '', root)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1236, in
handle_children
sev_db.load_variables(profile)
File "/usr/lib/python3/dist-packages/apparmor/severity.py", line 207, in
load_variables
raise Exception("failed reading prof_path = %s, e = %s" % (prof_path, e))
Exception: failed reading prof_path = /usr/sbin/apache2, e = 'utf-8' codec
can't decode byte 0xb3 in position 41: invalid st

[Touch-packages] [Bug 1368774] Re: [design] [Launcher] Make it easier to remove an item from launcher

2014-11-20 Thread kevin gunn

** Summary changed:

- [Launcher] Make it easier to remove an item from launcher
+ [design] [Launcher] Make it easier to remove an item from launcher

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1368774

Title:
  [design] [Launcher] Make it easier to remove an item from launcher

Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  New

Bug description:
  User testing revealed that users expected that icon could be removed
  from the launcher by longpressing an item and dragging it out of the
  launcher.

  One option would be having a trash bin appearing at the bottom of the
  Launcher (in the place normally occupied by the BFB) when a user drags
  and app icon off he launcher (or enters an edit mode to organize
  icons). The problem with this is that because user can also relocate
  an item in this mode dragging an item down to a trash bin causes item
  to go through all  different dropping positions in the actual launcher
  as well.

  Therefore one possible option would be placing the thrash bin outside
  the launcher next to the item in question.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1368774/+subscriptions

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

[Touch-packages] [Bug 1361221] Re: Manage Dash does not notice when the phone comes online

2014-11-20 Thread Launchpad Bug Tracker

** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/unity-scopes-shell
/vivid-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1361221

Title:
  Manage Dash does not notice when the phone comes online

Status in “unity-scope-scopes” package in Ubuntu:
  Invalid
Status in “unity-scopes-api” package in Ubuntu:
  In Progress
Status in “unity-scopes-shell” package in Ubuntu:
  In Progress
Status in “unity-scope-scopes” package in Ubuntu RTM:
  Invalid
Status in “unity-scopes-shell” package in Ubuntu RTM:
  New

Bug description:
  Steps:
  1. Start the phone with no Internet (i.e. no wireless or 2g/3g/4g)
  2. From the Dash, swipe from the bottom to get to Manage Dash
  3. Click "All"
  4. Note there are no internet based scopes available (which makes sense since 
you are not online)
  5. Click Done to go back to the dash
  6. Use the network indicator to get online
  7. After getting online, go back to Manage Dash

  Observed:
  The online scopes are still hidden

  Expected:
  After getting online you can see the online scopes

  Note that after a reboot and being online, the online scopes are
  visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-scopes/+bug/1361221/+subscriptions

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

[Touch-packages] [Bug 1315634] Re: gdb does not show heap arrays in fortran

** Bug watch added: Debian Bug tracker #555890
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555890

** Also affects: gdb (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555890
   Importance: Unknown
   Status: Unknown

** Bug watch added: Sourceware.org Bugzilla #9395
   http://sourceware.org/bugzilla/show_bug.cgi?id=9395

** Also affects: gdb via
   http://sourceware.org/bugzilla/show_bug.cgi?id=9395
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1315634

Title:
  gdb does not show  heap arrays in fortran

Status in GNU Debugger:
  Unknown
Status in “gdb” package in Ubuntu:
  Confirmed
Status in “gdb” package in Debian:
  Unknown

Bug description:
  The problem description can be found in many places over the internet, e.g. 
here:
  
http://numericalnoob.blogspot.fi/2012/08/fortran-allocatable-arrays-and-pointers.html
  When debugging simple program

  program test
  integer, parameter :: ndata = 8, ndim = 2
  real :: my_stack(ndata)
  real, allocatable, target:: my_heap(:)
  real, pointer:: my_ptr(:,:,:)
  allocate(my_heap(ndata))
  ! read stuff
  do i=1,ndata
  my_stack(i) = real(i)
  end do
  my_heap = my_stack
  my_ptr(1:ndim,1:ndim,1:ndim) => my_heap
  write(*,*) my_stack
  write(*,*) my_heap
  write(*,*) my_ptr
  end program test

  With gdb from distro (GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7) I get:

  
  Breakpoint 1, test () at test.f90:13
  13write(*,*) my_stack
  (gdb) p my_stack
  $1 = (1, 2, 3, 4, 5, 6, 7, 8)
  (gdb) p my_heap
  $2 = (0)
  (gdb) p my_ptr
  $3 = (( ( 0) ) )
  (gdb) 

  
  With properly compiled gdb on another computer (GNU gdb (GDB) SUSE 
(7.5.1-0.7.29)) i get 

  
  Breakpoint 1, test () at test.f90:13
  13write(*,*) my_stack
  (gdb) p my_stack
  $1 = (1, 2, 3, 4, 5, 6, 7, 8)
  (gdb) p my_heap
  $2 = (1, 2, 3, 4, 5, 6, 7, 8)
  (gdb) p my_ptr
  $3 = (( ( 1, 2) ( 3, 4) ) ( ( 5, 6) ( 7, 8) ) )
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1315634/+subscriptions

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

[Touch-packages] [Bug 1394614] Re: Cached results stay in scopes even with no internet

2014-11-20 Thread Albert Astals Cid

** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scopes-api (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1394614

Title:
  Cached results stay in scopes even with no internet

Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity-scopes-shell” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  I am testing the latest image and as per the test plan, if internet is
  disabled there are cached results in a scope they should vanish as we
  refresh the scope but right now that's not the case.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 20 15:06:59 2014
  InstallationDate: Installed on 2014-11-19 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141119-181707)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+subscriptions

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

[Touch-packages] [Bug 1171511] Re: seg fault when using auto completion for the condition command

fixed in 14.04 LTS

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1171511

Title:
  seg fault when using auto completion for the condition command

Status in GNU Debugger:
  Fix Released
Status in “gdb” package in Ubuntu:
  Fix Released

Bug description:
  When hunting a bug in libreoffice, gdb crashed with a seg fault. After
  some testing following procedure leads to the crash:

  1. Start gdb with any program you want to debug
  2. set a pending breakpoint, e.g. "b nofile.cxx:54"
  3. type "condition 1" + Tab

  the core dump of the first crash is attached. I have some more core
  dumps, so if they are required I can upload them, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gdb 7.5-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Mon Apr 22 17:13:49 2013
  InstallationDate: Installed on 2012-12-22 (121 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1171511/+subscriptions

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

[Touch-packages] [Bug 318989] Re: gdb dies collecting informations for crash reports

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/318989

Title:
  gdb dies collecting informations for crash reports

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  kubuntu 9.04 Alpha3
  gdb dies unexpectedly collecting informations for crash reports. I 
experienced that behavior after a kernel oop and a kttsd crash.

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gdb
  Package: gdb 6.8-3ubuntu2
  ProcCmdline: gdb --batch --ex file\ /usr/bin/kttsmgr --ex core-file\ 
/tmp/tmpm570CX --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex 
p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex 
p\ -99 --ex x/16i\ $pc
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: gdb
  Uname: Linux 2.6.28-4-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/318989/+subscriptions

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

[Touch-packages] [Bug 631373] Re: gdb crashed with UnicodeDecodeError in decode()

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Information type changed from Private to Public

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/631373

Title:
  gdb crashed with UnicodeDecodeError in decode()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  I was playing Exaile and I was creating a playlist when the player
  froze and crashed. After a while gdb crashed two times with the same
  error (first time)

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: gdb 7.1-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-25.43-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  Architecture: i386
  Date: Mon Sep  6 10:19:03 2010
  ExecutablePath: /usr/bin/gdb
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcCmdline: gdb --batch --ex file\ /usr/bin/python2.6 --ex core-file\ 
/tmp/tmpfFD0T7 --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex 
p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex 
p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ (char*)\ __abort_msg
  ProcEnviron:
   LANGUAGE=eo:eo:eo_US:it:it_IT:it_CH:fi:fi_FI
   LANG=eo.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdb
  Title: gdb crashed with UnicodeDecodeError in decode()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/631373/+subscriptions

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

[Touch-packages] [Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments

apparently fixed in 14.04 LTS

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/691814

Title:
  gdb crashed with SIGSEGV in response to strace command with no
  arguments

Status in GNU Debugger:
  Fix Released
Status in “gdb” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gdb

  gdb (package version 7.2-1ubuntu3 on Maverick amd64) segfaults when
  given the strace command with no arguments:

  ek@Apok:~$ gdb
  GNU gdb (GDB) 7.2-ubuntu
  Copyright (C) 2010 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  .
  (gdb) strace
  Segmentation fault (core dumped)

  strace with arguments does not cause a crash, and appears to work
  correctly. This bug also occurs when gdb is debugging a running
  program and the strace commad is issued without arguments (i.e., it
  does not only happen in the trivial case shown above).

  I am able to reproduce this bug on Maverick i386 (same gdb package
  version as above) and Natty i386 (gdb package version  package version
  7.2-1ubuntu6) as well.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: gdb 7.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic x86_64
  Architecture: amd64
  Date: Sat Dec 18 01:52:11 2010
  ExecutablePath: /usr/bin/gdb
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
  ProcCmdline: gdb
  ProcEnviron:
   SHELL=/bin/bash
   LC_MESSAGES=en_US.utf8
   LANG=en_US.utf8
   LANGUAGE=en_US.utf8
  SegvAnalysis:
   Segfault happened at: 0x4be88a:  repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x004be88a) ok
   source "%es:(%rdi)" (0x0069de12) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gdb
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: gdb crashed with SIGSEGV
  UserGroups: adm admin cdrom lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/691814/+subscriptions

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

[Touch-packages] [Bug 870997] Re: gdb crashed with SIGSEGV in feof()

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Information type changed from Private to Public

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/870997

Title:
  gdb crashed with SIGSEGV in feof()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Crashed during silverlight video playback startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gdb 7.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Oct  8 23:38:08 2011
  ExecutablePath: /usr/bin/gdb
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110830.1)
  ProcCmdline: /usr/bin/gdb -ex attach\ 8830 --ex info\ threads --ex thread\ 
apply\ all\ bt --batch
  ProcEnviron:
   LANGUAGE=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5d35dde030 : mov(%rdi),%ecx
   PC (0x7f5d35dde030) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdb
  StacktraceTop:
   feof () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   _initialize_charset ()
   initialize_all_files ()
   gdb_init ()
  Title: gdb crashed with SIGSEGV in feof()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/870997/+subscriptions

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

[Touch-packages] [Bug 674200] Re: gdb hang with maverick on Amazon ami-c81f4f8d

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/674200

Title:
  gdb hang with maverick on Amazon ami-c81f4f8d

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  Hi, 
When trying to run gdb (7.2-1ubuntu2) on Amazon EC2 with a Maverick AMI 
(Ubuntu 10.10), I am getting a hard hang of the system. Ctrl-c doesn't help. 
Rebooting the instance doesn't help. The only thing that seems to work is to 
terminate the instance and restart a new one.
The attached script is the list of commands that I use on a new EC2 
instance. GDB will run and place me at the gdb prompt. If I type 'run', then 
the instance hangs. Below is a dump of the terminal output.

  Ram

  
  ubuntu@ip-10-166-38-236:~/cutycapt/CutyCapt$ DISPLAY=:1 gdb --args 
  CutyCapt --url=http://www.google.com --out=temp.png 
  GNU gdb (GDB) 7.2-ubuntu 
  Copyright (C) 2010 Free Software Foundation, Inc. 
  License GPLv3+: GNU GPL version 3 or later  
  This is free software: you are free to change and redistribute it. 
  There is NO WARRANTY, to the extent permitted by law.  Type "show 
  copying" 
  and "show warranty" for details. 
  This GDB was configured as "i686-linux-gnu". 
  For bug reporting instructions, please see: 
  ... 
  Reading symbols from /home/ubuntu/cutycapt/CutyCapt/CutyCapt...(no 
  debugging symbols found)...done. 
  (gdb) run 
  Starting program: /home/ubuntu/cutycapt/CutyCapt/CutyCapt --url=http:// 
  www.google.com --out=temp.png 
  [Thread debugging using libthread_db enabled] 
  [New Thread 0xb50e7b70 (LWP 13984)] 
  [New Thread 0xb46f5b70 (LWP 13985)]

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gdb 7.2-1ubuntu2
  ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4
  Uname: Linux 2.6.35-22-virtual i686
  Architecture: i386
  Date: Thu Nov 11 19:37:59 2010
  Ec2AMI: ami-c81f4f8d
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-1a
  Ec2InstanceType: c1.medium
  Ec2Kernel: aki-99a0f1dc
  Ec2Ramdisk: unavailable
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/674200/+subscriptions

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

[Touch-packages] [Bug 841693] Re: gdb crashed with SIGABRT in __kernel_vsyscall()

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/841693

Title:
  gdb crashed with SIGABRT in __kernel_vsyscall()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Gdb crashed i was using virtualbox and while using scale plugin it
  suddenly crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gdb 7.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Mon Sep  5 15:34:39 2011
  ExecutablePath: /usr/bin/gdb
  ProcCmdline: gdb --batch --ex file\ /usr/sbin/modem-manager --ex core-file\ 
/tmp/tmpKUefwL --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex 
p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex 
p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ (char*)\ __abort_msg
  Signal: 6
  SourcePackage: gdb
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? ()
   ?? ()
  Title: gdb crashed with SIGABRT in __kernel_vsyscall()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/841693/+subscriptions

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

[Touch-packages] [Bug 1211412] Re: gdb crashed with SIGSEGV in lookup_objfile_from_block()

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1211412

Title:
  gdb crashed with SIGSEGV in lookup_objfile_from_block()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  I was debugging V8

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gdb 7.6~20130417-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Aug 12 18:38:50 2013
  ExecutablePath: /usr/bin/gdb
  InstallationDate: Installed on 2013-06-25 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: gdb --args out/x64.debug/cctest test-ast
  SegvAnalysis:
   Segfault happened at: 0x5980cd :   mov
0x10(%rax),%rax
   PC (0x005980cd) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdb
  Stacktrace:
   #0  0x005980cd in lookup_objfile_from_block ()
   No symbol table info available.
   Cannot access memory at address 0x7fff1f4ed258
  StacktraceTop: lookup_objfile_from_block ()
  ThreadStacktrace:
   .
   Thread 1 (LWP 1800):
   #0  0x005980cd in lookup_objfile_from_block ()
   No symbol table info available.
   Cannot access memory at address 0x7fff1f4ed258
  Title: gdb crashed with SIGSEGV in lookup_objfile_from_block()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1211412/+subscriptions

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

[Touch-packages] [Bug 1379692] Re: unimplemented command "evaluate" in QtCreator's QML/JS console

2014-11-20 Thread Timo Jyrinki

As per Tim's comment, this would need more exact reproducing steps as
he's not able to see the problem.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1379692

Title:
  unimplemented command "evaluate" in QtCreator's QML/JS console

Status in Ubuntu UI Toolkit:
  Invalid
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Incomplete

Bug description:
  With Qt 5, the QML/JS console in QtCreator is quite useless. It always
  displays 'unimplemented command "evaluate"'. I wonder how the Ubuntu
  Touch developers manage to debug their code under such conditions.
  This bug is reported upstream  and reported to be "fixed by
  6333e0913fc0078c0221a8909ced8df03a568992" in Qt 5.4. I suppose this is
  commit
  
.
  Could you please check if it is possible to backport this commit?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1379692/+subscriptions

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

[Touch-packages] [Bug 469005] Re: GDB: Failed to set controlling terminal

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/469005

Title:
  GDB: Failed to set controlling terminal

Status in Code::Blocks IDE:
  New
Status in GNU Debugger:
  New
Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: netbeans

  Im using Ubuntu 9.10 and Netbeans 6.7 and gdb 7.0, and it keeps
  complaining that gdb couldnt get control of the terminal, it seems tht
  gdb used in ubuntu 9.10 is newer than netbeans can accept. Maybe keep
  a special gdb 6.8 like a dependency for netbeans would solve this
  problem.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Nov  1 14:57:52 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: netbeans 6.7.1-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR.UTF-8
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: netbeans
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/codeblocks/+bug/469005/+subscriptions

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

[Touch-packages] [Bug 544597] Re: gdb crashed with UnicodeDecodeError in decode()

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/544597

Title:
  gdb crashed with UnicodeDecodeError in decode()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  reporting a crash using apport.

  ProblemType: Crash
  Architecture: i386
  CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
  CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
  Date: Mon Mar 22 23:23:25 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gdb
  Package: gdb 7.1-1ubuntu1
  ProcCmdline: gdb --batch --ex file\ /usr/bin/python2.6 --ex core-file\ 
/tmp/tmp5QTUJb --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex 
p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex 
p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ (char*)\ __abort_msg
  ProcEnviron:
   LANGUAGE=fr_FR:fr:en_GB:en
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: gdb
  Title: gdb crashed with UnicodeDecodeError in decode()
  Uname: Linux 2.6.32-16-generic i686
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev pulse pulse-access scanner tape users video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/544597/+subscriptions

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

[Touch-packages] [Bug 151518] Re: gdb cannot break on entry point for statically linked binaries

the upstream link is invalid.

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Triaged => Invalid

** Changed in: gdb
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/151518

Title:
  gdb cannot break on entry point for statically linked binaries

Status in GNU Debugger:
  Invalid
Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  See the following transcript:

  $ gdb /sbin/ldconfig 
  GNU gdb 6.6-debian
  Copyright (C) 2006 Free Software Foundation, Inc.
  GDB is free software, covered by the GNU General Public License, and you are
  welcome to change it and/or distribute copies of it under certain conditions.
  Type "show copying" to see the conditions.
  There is absolutely no warranty for GDB.  Type "show warranty" for details.
  This GDB was configured as "i486-linux-gnu"...
  (no debugging symbols found)
  Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
  (gdb) info files
  Symbols from "/sbin/ldconfig".
  Local exec file:
  `/sbin/ldconfig', file type elf32-i386.
  Entry point: 0x8048110
  0x080480d4 - 0x080480f4 is .note.ABI-tag
  0x080480f4 - 0x0804810b is .init
  0x08048110 - 0x080b84c8 is .text
  [...]
  0x080d9b68 - 0x080d9b7c is __libc_freeres_ptrs
  (gdb) break *0x8048110
  Breakpoint 1 at 0x8048110
  (gdb) run
  Starting program: /sbin/ldconfig 
  warning: shared library handler failed to enable breakpoint
  (no debugging symbols found)
  /sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: 
Permission denied

  Program exited with code 01.
  (gdb) quit

  
  gdb should break after loading the binary, but before executing any 
instructions. It doesn't.

  I am using feisty with gdb 6.6.dfsg-1ubuntu2 on a Samsung X20 XVM 1730
  V laptop (i386 architecture).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/151518/+subscriptions

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

[Touch-packages] [Bug 172311] Re: internal-error: unknown ptrace event 5

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel
free to re-open the issue if the problem persists.

** Changed in: gdb (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/172311

Title:
  internal-error: unknown ptrace event 5

Status in GNU Debugger:
  New
Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  This problem occured while I tried to debug a possible GCC problem.
  For some reason GDB receives an unknown ptrace event as soon as GCC
  crashes.

  The problem seems to be the same as reported in this report (from 2005):
  http://sourceware.org/ml/gdb/2005-05/msg00368.html

  It seems that this problem is reproducable in 100% of the cases (at
  least on my machine).

  The file foo.c used below (to crash GCC) is available at: 
  http://virtual.sysfrog.org/~gst/gccbug/foo.c

  gst@pico:~$ gdb -q gcc
  (no debugging symbols found)
  Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
  (gdb) set follow-fork-mode child
  (gdb) run -Wall -pedantic foo.c
  Starting program: /usr/bin/gcc -Wall -pedantic foo.c
  (no debugging symbols found)
  (no debugging symbols found)
  (no debugging symbols found)
  /build/buildd/gdb-6.6.dfsg/gdb/linux-nat.c:578: internal-error: unknown 
ptrace event 5
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) y
  /build/buildd/gdb-6.6.dfsg/gdb/linux-nat.c:578: internal-error: unknown 
ptrace event 5
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) y
  Aborted

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/172311/+subscriptions

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

[Touch-packages] [Bug 461594] Re: gdb doesn't read user-defined commands from .gdbinit

** Changed in: gdb (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/461594

Title:
  gdb doesn't read user-defined commands from .gdbinit

Status in GNU Debugger:
  New
Status in “gdb” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gdb

  After gdb starts, only the first of about 15 custom commands defined
  in the attached .gdbinit file are actually defined in gdb.  If I
  comment out the first one, then only the second is defined, etc.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Oct 26 19:50:12 2009
  DistroRelease: Ubuntu 9.10
  Package: gdb 7.0-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: gdb
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/461594/+subscriptions

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

[Touch-packages] [Bug 871940] Re: [Upstream] "/usr/bin/localc": not in executable format: File format not recognized

** Changed in: gdb (Ubuntu)
   Importance: Low => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/871940

Title:
  [Upstream] "/usr/bin/localc": not in executable format: File format
  not recognized

Status in GNU Debugger:
  Confirmed
Status in “gdb” package in Ubuntu:
  Triaged

Bug description:
  1)  lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy gdb
  gdb:
    Installed: 7.3-0ubuntu2
    Candidate: 7.3-0ubuntu2
    Version table:
   *** 7.3-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libreoffice-calc
  libreoffice-calc:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen at the Terminal:

  gdb localc 2>&1 | tee gdb-libreoffice.txt

  is LibreOffice Calc opens via gdb for debugging purposes.

  4) What happens instead is Calc is not launched with the following
  shown in the Terminal:

   GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
  Copyright (C) 2011 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "i686-linux-gnu".
  For bug reporting instructions, please see:
  ...
  "/usr/bin/localc": not in executable format: File format not recognized
  (gdb)

  Reproducible in:

  lsb_release -rd
  Description: Ubuntu precise (development branch)
  Release: 12.04

  apt-cache policy gdb
  gdb:
Installed: 7.4-0ubuntu1
Candidate: 7.4-0ubuntu1
Version table:
   *** 7.4-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  WORKAROUND: Attach to the process ID via the Terminal:

  sudo gdb localc 21015 2>&1 | tee ~/Desktop/gdb-libreoffice.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gdb 7.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Mon Oct 10 14:36:49 2011
  EcryptfsInUse: Yes
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/871940/+subscriptions

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

[Touch-packages] [Bug 1359126] Re: qmlscene crashed with SIGSEGV in QQmlDelegateModelItem::destroyObject()

2014-11-20 Thread Timo Jyrinki

This would seem to be gone nowadays in all vivid shorts_app results.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1359126

Title:
  qmlscene crashed with SIGSEGV in
  QQmlDelegateModelItem::destroyObject()

Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Incomplete

Bug description:
  Retracing from
  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/199:20140819:20140811.1/9777/shorts_app/

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: qmlscene 5.3.0-3ubuntu9
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Tue Aug 19 05:23:56 2014
  ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
  ExecutableTimestamp: 1407935103
  InstallationDate: Installed on 2014-08-19 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140819-020204)
  ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene shorts-app.qml
  ProcCwd: /usr/share/click/preinstalled/com.ubuntu.shorts/0.2.289
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: qtdeclarative-opensource-src
  Stacktrace:
   #0  0xb6cbc4ca in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
   No symbol table info available.
   #1  0xb6cc3ae6 in QQmlDelegateModel::cancel(int) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x20
  StacktraceSource:
   #0  0xb6cbc4ca in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
   #1  0xb6cc3ae6 in QQmlDelegateModel::cancel(int) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
  StacktraceTop:
   ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
   QQmlDelegateModel::cancel(int) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1359126/+subscriptions

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

[Touch-packages] [Bug 500691] Re: gdb can't refer to a single element in a two dimension array