[Desktop-packages] [Bug 868677] Re: remmina assert failure: remmina: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

2013-09-27 Thread Boris Baelen
Same problem for me in ubuntu 13.04.

This is my output.
If any more debugging is nessecary please let me know, i really want to fix 
this.

boris@werk-laptop:~$ remmina 
Remmina plugin VNC (type=Protocol) registered.
Remmina plugin VNCI (type=Protocol) registered.
Remmina plugin RDP (type=Protocol) registered.
Remmina plugin RDPF (type=File) registered.
Remmina plugin RDPS (type=Preference) registered.
Remmina plugin SFTP (type=Protocol) registered.
Remmina plugin SSH (type=Protocol) registered.
connected to 10.160.25.33:3389
null server certificate
*** Error in `remmina': free(): invalid next size (normal): 0x7ff0bc0e01c0 
***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7ff0f9db5a46]
/usr/lib/x86_64-linux-gnu/libfreerdp-gdi.so.1.0(gdi_DeleteObject+0x3e)[0x7ff0ecfd494e]
/usr/lib/x86_64-linux-gnu/libfreerdp-gdi.so.1.0(gdi_Bitmap_Free+0x28)[0x7ff0ecfd58e8]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(Bitmap_Free+0xc)[0x7ff0ed2006fc]
/usr/lib/x86_64-linux-gnu/libfreerdp-cache.so.1.0(update_gdi_cache_bitmap_v2+0xa5)[0x7ff0ec32e625]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(update_recv_secondary_order+0xb8)[0x7ff0ed1ffd28]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(fastpath_recv_updates+0x3eb)[0x7ff0ed208a7b]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(+0x2a98a)[0x7ff0ed20698a]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(+0x2abd0)[0x7ff0ed206bd0]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(transport_check_fds+0x122)[0x7ff0ed209e52]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(freerdp_check_fds+0x13)[0x7ff0ed2003f3]
/usr/lib/remmina/plugins/remmina-plugin-rdp.so(+0x7cc1)[0x7ff0ed427cc1]
/usr/lib/remmina/plugins/remmina-plugin-rdp.so(+0x801a)[0x7ff0ed42801a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7f8e)[0x7ff0faa71f8e]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff0f9e2ee1d]
=== Memory map: 
0040-00449000 r-xp  08:01 3146747
/usr/bin/remmina
00649000-0064a000 r--p 00049000 08:01 3146747
/usr/bin/remmina
0064a000-0064d000 rw-p 0004a000 08:01 3146747
/usr/bin/remmina
0070f000-00c0a000 rw-p  00:00 0  [heap]
7ff0b3816000-7ff0b400 rw-p  00:00 0 
7ff0b400-7ff0b4021000 rw-p  00:00 0 
7ff0b4021000-7ff0b800 ---p  00:00 0 
7ff0b800-7ff0b8021000 rw-p  00:00 0 
7ff0b8021000-7ff0bc00 ---p  00:00 0 
7ff0bc00-7ff0bc0e8000 rw-p  00:00 0 
7ff0bc0e8000-7ff0c000 ---p  00:00 0 
7ff0c03de000-7ff0c03df000 ---p  00:00 0 
7ff0c03df000-7ff0c0bdf000 rw-p  00:00 0  
[stack:9628]
7ff0c0bdf000-7ff0c0be ---p  00:00 0 
7ff0c0be-7ff0c13e rw-p  00:00 0  
[stack:9627]
7ff0c13e-7ff0c9a8a000 r--p  08:01 4344349
/usr/share/icons/hicolor/icon-theme.cache
7ff0c9a8a000-7ff0d2134000 r--p  08:01 4344349
/usr/share/icons/hicolor/icon-theme.cache
7ff0d2134000-7ff0d709a000 r--p  08:01 4349759
/usr/share/icons/gnome/icon-theme.cache
7ff0d709a000-7ff0dc00 r--p  08:01 4349759
/usr/share/icons/gnome/icon-theme.cache
7ff0dc00-7ff0dc022000 rw-p  00:00 0 
7ff0dc022000-7ff0e000 ---p  00:00 0 
7ff0e000-7ff0e0022000 rw-p  00:00 0 
7ff0e0022000-7ff0e400 ---p  00:00 0 
7ff0e41db000-7ff0e41e1000 r-xp  08:01 3410571
/usr/lib/x86_64-linux-gnu/freerdp/disk.so
7ff0e41e1000-7ff0e43e ---p 6000 08:01 3410571
/usr/lib/x86_64-linux-gnu/freerdp/disk.so
7ff0e43e-7ff0e43e1000 r--p 5000 08:01 3410571
/usr/lib/x86_64-linux-gnu/freerdp/disk.so
7ff0e43e1000-7ff0e43e2000 rw-p 6000 08:01 3410571
/usr/lib/x86_64-linux-gnu/freerdp/disk.so
7ff0e43e2000-7ff0e43e3000 ---p  00:00 0 
7ff0e43e3000-7ff0e53cd000 rw-p  00:00 0  
[stack:9626]
7ff0e53cd000-7ff0e53d r-xp  08:01 3410577
/usr/lib/x86_64-linux-gnu/freerdp/rdpdr.so
7ff0e53d-7ff0e55cf000 ---p 3000 08:01 3410577
/usr/lib/x86_64-linux-gnu/freerdp/rdpdr.so
7ff0e55cf000-7ff0e55d r--p 2000 08:01 3410577
/usr/lib/x86_64-linux-gnu/freerdp/rdpdr.so
7ff0e55d-7ff0e55d1000 rw-p 3000 08:01 3410577
/usr/lib/x86_64-linux-gnu/freerdp/rdpdr.so
7ff0e55d1000-7ff0e55d4000 r-xp  08:01 3410570
/usr/lib/x86_64-linux-gnu/freerdp/cliprdr.so
7ff0e55d4000-7ff0e57d3000 ---p 3000 08:01 3410570
/usr/lib/x86_64-linux-gnu/freerdp/cliprdr.so
7ff0e57d3000-7ff0e57d4000 r--p 2000 08:01 3410570
/usr/lib/x86_64-linux-gnu/freerdp/cliprdr.so
7ff0e57d4000-7ff0e57d5000 rw-p 3000 08:01 

[Desktop-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets

2013-03-21 Thread Boris Baelen
Hi,

I would like to say that this problem is still there and is the reason
why I am not able to stream audio using RTP.

I have all other options disbaled, discover network audio, etc...

When I turn on RTP sender this happens:
21:52:26.935440 IP 192.168.0.235.48718  224.0.0.56.46234: UDP, length 1292
21:52:26.942691 IP 192.168.0.235.48718  224.0.0.56.46234: UDP, length 1292
21:52:26.949926 IP 192.168.0.235.48718  224.0.0.56.46234: UDP, length 1292
21:52:26.957141 IP 192.168.0.235.48718  224.0.0.56.46234: UDP, length 1292
21:52:26.964376 IP 192.168.0.235.48718  224.0.0.56.46234: UDP, length 1292
21:52:26.971580 IP 192.168.0.235.48718  224.0.0.56.46234: UDP, length 1292
21:52:26.978862 IP 192.168.0.235.48718  224.0.0.56.46234: UDP, length 1292
.. NON STOP.

IT will flood my entire network!

Is there a fix already? I am running Ubuntu 12.10 64bit.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Debian:
  Incomplete

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232  224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       

[Desktop-packages] [Bug 860600] Re: Media keys aren't working (Ubuntu 11.10, Pithos latest daily)

2012-04-05 Thread Boris Baelen
Can someone please tell me in which version of gnome-settings-daemon
this is fixed? I'm running 3.2.2-0ubuntu2 and still have the problem

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/860600

Title:
  Media keys aren't working (Ubuntu 11.10, Pithos latest daily)

Status in Gnome Settings Daemon:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “guayadeque” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” source package in Oneiric:
  Fix Released
Status in “guayadeque” source package in Oneiric:
  Fix Released
Status in “guayadeque” package in Debian:
  Fix Released

Bug description:
  When I press a media key a circle with a diagonal line appears instead
  of the standard play/pause/next, etc. Using the DBUS API directly does
  work.

  I have a Logitech G110 keyboard, Ubuntu 11.10, and I'm using the
  latest Pithos from the daily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/860600/+subscriptions

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


[Desktop-packages] [Bug 820709] Re: Burn Several Disks' button doesn't work.

2011-10-22 Thread Boris Baelen
Same here!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/820709

Title:
  Burn Several Disks' button doesn't work.

Status in “brasero” package in Ubuntu:
  Confirmed

Bug description:
  I created a playlist of 42 songs in Rhythmbox and want to burn it. I
  click on the 'Burn' button and Brasero opens. Brasero warns me that
  there isn't enough room on the disk and asks if I want to burn on
  multiple disks. I expected this. So i click on the 'Burn Several
  Disks' button and nothing happens. I found out that this happens with
  all the Linux versions, not just Ubuntu, so it's not an OS bug.

  1. OS = Ubuntu 11.04
  2. Brasero ver = 2.32.1-0ubuntu2 
  3. I expected the button to work.
  4. It didn't!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: brasero 2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic i686
  Architecture: i386
  Date: Wed Aug  3 18:20:41 2011
  ExecutablePath: /usr/bin/brasero
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brasero
  UpgradeStatus: Upgraded to natty on 2011-04-30 (96 days ago)

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

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