Bug#696513: PTP_ERROR_IO: failed to open session
Package: mtp-tools Version: 1.1.6-1 Followup-For: Bug #696513 Hi, I'm not entirely sure if this is related, but I managed to make MTP worked to my Android phone by adding my user to 'lp' group (and make sure it is also in 'audio' group as well). Prior to this, I experienced same PTP_ERROR_IO with a lot of message like this in syslog: usbfs: process NNN (mtp) did not claim interface 0 before use Hope this helps. All the best. -arief -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mtp-tools depends on: ii libc62.17-0experimental2 ii libmtp9 1.1.6-1 mtp-tools recommends no packages. mtp-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692554: smstools: Sending sms always segfault
Package: smstools Version: 3.1.14-1.1 Severity: important Dear Maintainer, Sending sms always segfaulted on my amd64 system. Read that upstream already fix this in version 3.1.15, this is their note: -- start upstream note -- When creating a lockfile, main process used incorrect offset -1 with the table of names of processes. This caused segmentation fault when smsd was compiled using latest compilers. -- end upstream note -- Thanks -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smstools depends on: ii adduser 3.113+nmu3 ii debconf 1.5.46 ii libc62.13-36 ii libmm14 1.4.2-4 ii ucf 3.0025+nmu3 smstools recommends no packages. smstools suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674565: Bluetooth activation failed (btusb module)
On Tue, May 29, 2012 at 3:57 AM, Jonathan Nieder wrote: > Arief M Utama wrote: > > > Hit enter too quick, forgot about the dmesg attachment. Here it is. > > Wonderful, thanks. Just for fun, let's parse some unrelated messages. > > > [0.00] DMI: Hewlett-Packard HP ENVY 15 NOTEBOOK PC/1688, BIOS > F.04 11/12/2011 > [...] > > [2.529762] \_SB_.PCI0:_OSC invalid UUID > > [2.529763] _OSC request data:1 8 1f > [...] > > [2.573816] \_SB_.PCI0:_OSC invalid UUID > > [2.573817] _OSC request data:1 1f 1f > > [2.573820] pci:00: Requesting ACPI _OSC control (0x1d) > > [2.573865] \_SB_.PCI0:_OSC invalid UUID > > [2.573866] _OSC request data:1 0 1d > > [2.573869] pci:00: ACPI _OSC request failed (AE_ERROR), > returned control mask: 0x1d > > [2.573871] ACPI _OSC control for PCIe not granted, disabling ASPM > > That's <https://bugzilla.kernel.org/show_bug.cgi?id=36932>, perhaps. > Could be a bug in the BIOS or an ACPI bug in the kernel, or a > misleading message. > > How can I help with this one? Not very familiar with kernel debugging. > [...] > > [ 10.250808] rts_pstor: module is from the staging directory, the > quality is unknown, you have been warned. > > [ 10.251583] Initializing Realtek PCIE storage driver... > [...] > > [ 11.452078] rts_pstor: device scan complete > > [ 11.452316] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S. > 1.00 PQ: 0 ANSI: 0 CCS > > [ 11.452417] Bad LUN (0:1) > > [ 11.452607] Bad target number (1:0) > > [ 11.452746] Bad target number (2:0) > > [ 11.452878] Bad target number (3:0) > > [ 11.452998] Bad target number (4:0) > > [ 11.453141] Bad target number (5:0) > > [ 11.453257] Bad target number (6:0) > > [ 11.453353] Bad target number (7:0) > > [ 11.453724] sd 6:0:0:0: [sdb] Attached SCSI removable disk > > <http://bugs.debian.org/637813>. I get the impression that Realtek > has abandoned this driver and is working on a new version (not > published yet) that follows a different approach. > > And how about this one? Do you happen to know where I can check the new drivers? I tried to read the bug comments, but I got lost in the woods there. > [...] > > [ 77.448484] atkbd serio0: Unknown key pressed (translated set 2, code > 0xab on isa0060/serio0). > > [ 77.448494] atkbd serio0: Use 'setkeycodes e02b ' to make it > known. > > If this is the brightness key, sounds like > <https://bugzilla.redhat.com/804285>. There is a related upstream > report at <https://bugzilla.kernel.org/show_bug.cgi?id=43280>. > > Yep it's brightness key, used setkeycodes to ignore it. What is the debian-way to put in some customs boot-time scripts? All that is not working in this laptop now are HP's Wireless Audio usb device (snd-usb-audio module?) I had to blacklist it, since it keep sending messages to the console and prevent pulseaudio from running which in turn prevent gnome-shell to run, and the other one is the presence-censor that activates keyboard light whenever it detect objects in-front of the screen, but since I can pressed function key to activate the keyboard light this is not much of a hassle. > Thanks, > Jonathan > All the best. -arief
Bug#674565: Bluetooth activation failed (btusb module)
On Tue, May 29, 2012 at 2:07 AM, Jonathan Nieder wrote: > Arief M Utama wrote: > > On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder > wrote: > > >> Will look around and then submit these > >> for inclusion in 3.2.y from kernel.org if they seem to be well tested. > > > > I can test the other patches if needed, just to make sure about it :-) > > Yeah, no need. > > For the future: it now occurs to me that you might have been applying > the patches with the test-patches script one at a time, which would > explain why some of them didn't apply. The command takes a list of > patches as arguments to apply in order. But it's not important: I was > asking to test them together just as a "while at it" extra in the same > boot. I don't think it's worth the time to compile and boot yet > again. :) > Noted :-) > > I need to finish gathering a list of people who tested the driver > using hardware with the other USB ids and then I'll send the patches > as a batch to stable@. Thanks for your help and sorry to be so slow > at this. > > You're very helpful and prompt already, I'm being a bit slow here. > Sincerely, > Jonathan > All the best. -arief
Bug#674565: Bluetooth activation failed (btusb module)
On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder wrote: > Arief M Utama wrote: > > > This is the output from lsusb: > > > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > > Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > > Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp. > > Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp. > > Bus 004 Device 004: ID 064e:e258 Suyin Corp. > > > > More details from lsusb output on the bluetooth device attached. > > Thanks. > > > I can confirm that patch number 4 > > [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working > on > > my laptop. Haven't tested other patches, although I can report that only > > patches 1, 4, 6 and 8 that applied successfully. > > Ok. What kernel are you applying these to? Could you attach "dmesg" > output from the patched kernel? > > The source package was called this: linux-2.6-3.2.18, the image is this: linux-image-3.2.0-2-amd64. dmesg output attached here. I was hoping to get a quick sanity check that the other patches at > least didn't cause the kernel to explode :), but answers to more > important questions about them would indeed require info from people > with the matching hardware. Will look around and then submit these > for inclusion in 3.2.y from kernel.org if they seem to be well tested. > > I can test the other patches if needed, just to make sure about it :-) > Hope that helps, > Jonathan > All the best. -arief
Bug#674565: Bluetooth activation failed (btusb module)
Hi Jonathan, First, thanks for the reply. On Fri, May 25, 2012 at 11:20 PM, Jonathan Nieder wrote: > # hardware support > severity 674565 important > tags 674565 + upstream patch moreinfo > quit > > Hi Arief, > > Arief M Utama wrote: > > > This is a minor but annoying bug, > > btusb on my HP Envy 15 laptop failed to activate bluetooth, > > since it lacks the appropriate usb_device_id entry. > > > > I would propose adding the entry for more convinience and usability. > > Currently I have to use some commands to activate the bluetooth module > > by adding the ID entry on related sysfs file. > > > > Err, upon examining the code I found that the entry already existed in > > current 3.2 kernel source file (drivers/bluetooth/btusb.c) but looks > > like it is a typo error. > > Thanks. Please attach "lsusb" output. > > If you have time to test the attached patch series following > instructions from [1], that would also be very useful. > > This is the output from lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp. Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp. Bus 004 Device 004: ID 064e:e258 Suyin Corp. More details from lsusb output on the bluetooth device attached. I can confirm that patch number 4 [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working on my laptop. Haven't tested other patches, although I can report that only patches 1, 4, 6 and 8 that applied successfully. All the best. -arief Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 1 bDeviceProtocol 1 bMaxPacketSize064 idVendor 0x0a5c Broadcom Corp. idProduct 0x21e1 bcdDevice1.12 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 218 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x0
Bug#674565: Bluetooth activation failed
Sorry for the repeating lines, Just to highlight, the typo-error is on the 0x05ac part, it is supposed to be 0x0a5c All the best. -arief
Bug#674565: linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module)
Package: linux-2.6 Version: 3.2.18-1
Severity: normal
Tags: patch
Dear Maintainer,
This is a minor but annoying bug,
btusb on my HP Envy 15 laptop failed to activate bluetooth,
since it lacks the appropriate usb_device_id entry.
I would propose adding the entry for more convinience and usability.
Currently I have to use some commands to activate the bluetooth module
by adding the ID entry on related sysfs file.
Err, upon examining the code I found that the entry already existed in
current 3.2 kernel source file (drivers/bluetooth/btusb.c) but looks
like it is a typo error.
--- this is the original line ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x05ac, 0x21e1) },
--- it supposed to be like this (checked in 3.4 source) ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x0a5c, 0x21e1) },
--- this is the original line ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x05ac, 0x21e1) },
--- it supposed to be like this (checked in 3.4 source) ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x0a5c, 0x21e1) },
Thanks, hope it helps.
All the best.
-arief
-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.18-1) (
debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1
SMP Mon May 21 17:45:41 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64
root=UUID=bebd9c63-74ba-43e2-a2fc-5e42f29a0a78 ro quiet
** Tainted: C (1024)
* Module from drivers/staging has been loaded.
Bug#636137: network-manager: Might found the problem
On 08/09/2011 12:09 AM, Arief M Utama wrote: > From latest git pull, On line 3281-3283 in src/nm-manager.c : Sorry, this is wrong, I mean from apt-get source network-manager -t experimental The line numbers are correct though. All the best. -arief -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636137: network-manager: Might found the problem
Package: network-manager
Version: 0.8.9997-1
Followup-For: Bug #636137
(note: this is a copy of the same notes I wrote in redhat's bugzilla
#713006, adjusted to Debian's version of network-manager)
I think I might found the problem,
>From latest git pull, On line 3281-3283 in src/nm-manager.c :
old_enabled = radio_enabled_for_rstate (rstate, TRUE);
rstate->user_enabled = enabled;
new_enabled = radio_enabled_for_rstate (rstate, FALSE);
When disabling a wifi, old_enabled != new_enabled and new_enabled == 0;
Which in turn will run the following lines:
if (new_enabled != old_enabled) {
manager_update_radio_enabled (self, rstate, new_enabled);
/* For WiFi only (for now) set the actual kernel rfkill state */
if (rstate->rtype == RFKILL_TYPE_WLAN)
rfkill_change_wifi (rstate->desc, new_enabled);
}
But when re-enabling wifi, the case will be: old_enabled == new_enabled
and new_enabled == 0; which in that case the enabling code will never
get ran.
I "fix" it by moving around the check and enabling code and hackishly set
new_enabled=1 when old_enabled == new_enabled == 0.
Seems to work, but it also throwing out some funny messages that might
just wanna kill my device :)
Here's hoping for a _real_fix_soon (tm) :)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.113 add and remove users and groups
ii dbus 1.5.6-1 simple interprocess messaging syst
ii isc-dhcp-client 4.1.1-P1-17 ISC DHCP client
ii libc62.13-14 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.5.6-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.94-4 simple interprocess messaging syst
ii libgcrypt11 1.4.6-9 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.28.6-2GLib library of C routines
ii libgnutls26 2.12.7-4GNU TLS library - runtime library
ii libgudev-1.0-0 172-1 GObject-based wrapper library for
ii libnl1 1.1-7 library for dealing with netlink s
ii libnm-glib4 0.8.9997-1 network management framework (GLib
ii libnm-util2 0.8.9997-1 network management framework (shar
ii libpolkit-gobject-1-00.102-1 PolicyKit Authorization API
ii libuuid1 2.19.1-5Universally Unique ID library
ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip
ii udev 172-1 /dev/ and hotplug management daemo
ii wpasupplicant0.7.3-3.1 client support for WPA and WPA2 (I
Versions of packages network-manager recommends:
ii dnsmasq-base 2.57-1 A small caching DNS proxy and DHCP
ii iptables 1.4.12-1 administration tools for packet fi
ii modemmanager 0.4.997-1 D-Bus service for managing modems
ii policykit-1 0.102-1framework for managing administrat
ii ppp 2.4.5-5Point-to-Point Protocol (PPP) - da
Versions of packages network-manager suggests:
pn avahi-autoipd (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#622664: [Possibly RESOLVED] gnome-bluetooth: Confirmed crashes when called from gnome-control-center
Hi again, I think I've found the culprit. When installing network-manager, it pulled network-manager-gnome which in turn pulled in libgnome-bluetooth7. While we are installing gnome-bluetooth 3.0.0 which depends on libgnome-bluetooth8 Unfortunately I cant purge/remove libgnome-bluetooth7 just like that as it would pulled out network-manager and etc. So what I did for now is just: dpkg --purge --force-all libgnome-bluetooth7 Everything, err... I mean gnome-bluetooth 3.0 settings, is working fine after that. Hope it helps. Now I'll be looking forward to removal of libgnome-bluetooth7 from network-manager-gnome dependencies :) Thanks. All the best. -arief -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#622664: gnome-bluetooth: Confirmed crashes when called from gnome-control-center
Hi, Did a backtrace for the problem, these are the last few lines: --- start bt --- #0 0xb7e50f8f in gtk_tree_path_copy () from /usr/lib/libgtk-3.so.0 #1 0xb7e54137 in gtk_tree_row_reference_get_path () from /usr/lib/libgtk-3.so.0 #2 0xaf3da7a8 in bluetooth_client_get_discoverable () from /usr/lib/control-center-1/panels/libbluetooth.so #3 0xaf3d4c75 in ?? () from /usr/lib/control-center-1/panels/libbluetooth.so #4 0xaf3d6246 in ?? () from /usr/lib/control-center-1/panels/libbluetooth.so #5 0xb7946581 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 #6 0xb7922d05 in ?? () from /usr/lib/libgobject-2.0.so.0 #7 0xb7925dbc in g_object_newv () from /usr/lib/libgobject-2.0.so.0 #8 0xb79270d8 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 #9 0xb79271f7 in g_object_new () from /usr/lib/libgobject-2.0.so.0 #10 0x0804ecaf in ?? () #11 0xb7fc2512 in cc_shell_set_active_panel_from_id () from /usr/lib/libgnome-control-center.so.1 #12 0x0804e168 in ?? () --- end bt --- Will try to investigate this further deeper. All the best. -arief -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#622664: gnome-bluetooth: Confirmed crashes when called from gnome-control-center
Subject: gnome-bluetooth: Confirmed crashes when called from gnome-control-center Followup-For: Bug #622664 Package: gnome-bluetooth Version: 3.0.0-1 *** Please type your report below this line *** Hi, I can confirm that this is happening to my system also. When doing strace and using en_US locale, I can see the last syscall is opening /usr/share/locale/en_US/LC_MESSAGES/gnome-bluetooth2.mo which does not exist but even when changing to en_GB locale it's still crashed. Oh, for more info, running bluetooth-wizard or bluetooth-sendto directly worked just fine. All the best. -arief -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-bluetooth depends on: ii bluez4.91-1 Bluetooth tools and daemons ii consolekit 0.4.5-1 framework for defining and trackin ii dconf-gsettings-backend [gse 0.7.5-1 simple configuration storage syste ii gir1.2-atk-1.0 2.0.0-1 The ATK accessibility toolkit (GOb ii gir1.2-freedesktop 0.10.8-1Introspection data for some FreeDe ii gir1.2-gdkpixbuf-2.0 2.23.3-3GDK Pixbuf library - GObject-Intro ii gir1.2-glib-2.0 0.10.8-1Introspection data for GLib, GObje ii gir1.2-gnomebluetooth-1.03.0.0-1 Introspection data for GnomeBlueto ii gir1.2-gtk-3.0 3.0.8-1 The GTK+ graphical user interface ii gir1.2-pango-1.0 1.28.3-6Layout and rendering of internatio ii libatk1.0-0 2.0.0-1 The ATK accessibility toolkit ii libc62.13-4 Embedded GNU C Library: Shared lib ii libcairo-gobject21.10.2-6The Cairo 2D vector graphics libra ii libcairo21.10.2-6The Cairo 2D vector graphics libra ii libdbus-1-3 1.4.8-3 simple interprocess messaging syst ii libdbus-glib-1-2 0.92-1 simple interprocess messaging syst ii libdconf00.7.5-1 simple configuration storage syste ii libfontconfig1 2.8.0-2.2 generic font configuration library ii libfreetype6 2.4.4-1 FreeType 2 font engine, shared lib ii libgdk-pixbuf2.0-0 2.23.3-3GDK Pixbuf library ii libglib2.0-0 2.28.6-2GLib library of C routines ii libgnome-bluetooth8 3.0.0-1 GNOME Bluetooth tools - support li ii libgnome-control-center1 1:3.0.1.1-1 utilities to configure the GNOME d ii libgtk-3-0 3.0.8-1 The GTK+ graphical user interface ii libnotify4 0.7.1-2 sends desktop notifications to a n ii libpango1.0-01.28.3-6Layout and rendering of internatio ii obex-data-server 0.4.5-1+b1 D-Bus service for OBEX client and ii obexd-client 0.40-2 D-Bus OBEX client ii udev 169-1 /dev/ and hotplug management daemo Versions of packages gnome-bluetooth recommends: ii gvfs-backends 1.8.0-1userspace virtual filesystem - bac Versions of packages gnome-bluetooth suggests: ii gnome-user-share 2.30.1-1 User level public file sharing via ii nautilus-sendto 3.0.0-1integrates Evolution and Pidgin in -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#626955: libgl1-mesa-dri: Version 7.10.2 does not work with gnome-shell, 7.10-4 works ok
On 05/17/2011 11:38 AM, Cyril Brulebois wrote: Hi, Arief M Utama (17/05/2011): Not sure how to start gnome-shell with all the exports override, so I just did a make install. Result is, gnome-shell works ok, as it was before in 7.10-4. alright; what if you build r600c instead? It's good to see that current r600g is alright (as was 7.10), but knowing if r600c is still buggy was my point, so that you could report a bug upstream to possibly get that fixed. Hi KiBi, I'll do that, but honestly, mesa is still a new thing for me, could you please let me know how to build r600c instead of r600g ? Is it --disable-gallium ? All the best. -arief -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#626955: libgl1-mesa-dri: Version 7.10.2 does not work with gnome-shell, 7.10-4 works ok
On 05/17/2011 12:53 AM, Sven Joachim wrote: On 2011-05-16 19:26 +0200, Cyril Brulebois wrote: I guess you're in the case where r600g (gallium) works OK, while r600c (classic) doesn't. It would be nice to figure out whether mesa master is showing the same bugs. You could try the following instructions to test that: http://pkg-xorg.alioth.debian.org/howto/build-mesa.html But beware: those haven't been updated yet to the new options/flags for radon hardware, so you'll probably have to specify some other radeon or r* options/flags. FWIW, "--enable-gallium-radeon" has been renamed to --enable-gallium-r300"¹, and since commit 0fecb928² requires LLVM to be installed. So Arief should pass "--enable-gallium-r600 --disable-gallium-r300" to `configure'. Thanks Cyril and Sven, Just finished compiling upstream mesa from git with the steps as you've mentioned. Not sure how to start gnome-shell with all the exports override, so I just did a make install. Result is, gnome-shell works ok, as it was before in 7.10-4. All the best. -arief -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#626955: libgl1-mesa-dri: Version 7.10.2 does not work with gnome-shell, 7.10-4 works ok
Package: libgl1-mesa-dri Version: 7.10.2-2 Severity: important With gnome-shell and xorg radeon driver (card: Radeon HD3470), version 7.10.2 keeps crashing when mouse is clicking panel icons (top right). With version 7.10-4 it works ok. -- Package-specific info: glxinfo: DISPLAY is not set. X server symlink status: lrwxrwxrwx 1 root root 13 May 16 16:05 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2018824 May 1 17:21 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4] /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 2.6.38-2-686 (Debian 2.6.38-5) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Sun May 8 14:49:45 UTC 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 36437 May 16 22:58 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [97.525] X.Org X Server 1.10.1 Release Date: 2011-04-15 [97.525] X Protocol Version 11, Revision 0 [97.525] Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian [97.525] Current Operating System: Linux mawar 2.6.38-2-686 #1 SMP Sun May 8 14:49:45 UTC 2011 i686 [97.525] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-686 root=UUID=c3f83111-3988-464a-9b3e-b19938bb781f ro quiet [97.525] Build Date: 01 May 2011 10:14:44AM [97.525] xorg-server 2:1.10.1-2 (Julien Cristau ) [97.525] Current version of pixman: 0.21.8 [97.525]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [97.525] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [97.525] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 16 22:48:03 2011 [97.525] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [97.526] (==) No Layout section. Using the first Screen section. [97.526] (==) No screen section available. Using defaults. [97.526] (**) |-->Screen "Default Screen Section" (0) [97.526] (**) | |-->Monitor "" [97.526] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [97.526] (==) Automatically adding devices [97.526] (==) Automatically enabling devices [97.526] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [97.526]Entry deleted from font path. [97.526] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [97.526]Entry deleted from font path. [97.526] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [97.526]Entry deleted from font path. [97.526] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [97.526]Entry deleted from font path. [97.526] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [97.526]Entry deleted from font path. [97.526] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [97.526]Entry deleted from font path. [97.526] (WW) `fonts.dir' not found (or not valid) in "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType". [97.526]Entry deleted from font path. [97.526](Run 'mkfontdir' on "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"). [97.526] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [97.526] (==) ModulePath set to "/usr/lib/xorg/modules" [97.526] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [97.526] (II) Loader magic: 0x8232ac0 [97.526] (II) Module ABI versions: [97.526]X.Org ANSI C Emulation: 0.4 [97.526]X.Org Video Driver: 10.0 [97.526]X.Org XInput driver : 12.2 [97.526]X.Org Server Extension : 5.0 [97.527] (--) PCI:*(0:1:0:0) 1002:95c4:104d:9033 rev 0, Mem @ 0xc000/268435456, 0xd002/65536, I/O @ 0x9000/256, BIOS @ 0x/131072 [97.527] (II) Open ACPI successful (/var/run/acpid.socket) [97.527] (II) LoadModule: "extmod" [97.528] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [97.528] (II) Module extmod: vendor="X.Org Foundation" [97.528]compiled for 1.10.1, module version = 1.0.0 [97.528]Module class: X.Org Server Extension [97.528]ABI class: X.Org Server Extension, version 5.0 [97.528] (II) Loading extensio
Bug#622405: gnome-shell: Crashes when notification icons clicked
On 04/13/2011 11:47 PM, Björn Heide wrote: Am Mittwoch, den 13.04.2011, 03:07 +0700 schrieb Arief M Utama: gnome-shell from experimental always crashes (and restarted) whenever any icons in the notification area clicked. Clicking the icons again will force log-out since it detected something due to small window between crashes/restarts. Same here, but I only see this crashes with latest Mesa (7.10.2-1) from unstable, which uses the classic r600 driver again. There are no crashes with Mesa 7.10-4, currently in testing, which uses the new r600 gallium driver. Thanks Björn! It worked by downgrading to Mesa 7.10-4 in testing. Yay! :-) Now I do wonder why we have 7.10.2-1 in unstable? All the best. -arief -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#622405: gnome-shell: Crashes when notification icons clicked
Package: gnome-shell Version: 3.0.0.2-1 Severity: important gnome-shell from experimental always crashes (and restarted) whenever any icons in the notification area clicked. Clicking the icons again will force log-out since it detected something due to small window between crashes/restarts. Step to repeat: 1. Enter Gnome 3 session with gnome-shell 2. Click any of the notification icon: Can be volume control, bluetooth, network-manager or power indicator icons. 3. Crashed Syslog gave this info: Apr 13 02:16:35 mawar kernel: [ 1327.514126] gnome-shell[2557]: segfault at 0 ip (null) sp bf926bbc error 4 in gnome-shell[8048000+3000] My video card is Radeon HD3470, using open source radeon driver from sid (unstable). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.37-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings- 0.7.3-4 Simple key-based configuration sys ii gconf2 2.32.1-2GNOME configuration database syste ii gir1.2-atk-1.0 2.0.0-1 The ATK accessibility toolkit (GOb ii gir1.2-clutter-1 1.6.10-3GObject introspection data for the ii gir1.2-freedeskt 0.10.7-1Introspection data for some FreeDe ii gir1.2-gconf-2.0 2.32.1-2GNOME configuration database syste ii gir1.2-gdkpixbuf 2.23.3-3GDK Pixbuf library - GObject-Intro ii gir1.2-gkbd-3.0 2.91.91-2 GObject introspection data for the ii gir1.2-glib-2.0 0.10.7-1Introspection data for GLib, GObje ii gir1.2-gnomeblue 3.0.0-1 Introspection data for GnomeBlueto ii gir1.2-gtk-3.0 3.0.8-1 The GTK+ graphical user interface ii gir1.2-json-glib 0.12.0-3GLib JSON manipulation library (do ii gir1.2-mutter-3. 3.0.0-2 GObject introspection data for Mut ii gir1.2-networkma 0.8.998-1 GObject introspection data for Net ii gir1.2-pango-1.0 1.28.3-6Layout and rendering of internatio ii gir1.2-polkit-1. 0.101-3 GObject introspection data for Pol ii gir1.2-telepathy 0.14.3-2GLib Telepathy connection manager ii gir1.2-telepathy 0.2.8-2 Telepathy logger service - introsp ii gir1.2-upowergli 0.9.9-4 GObject introspection data for upo ii gjs 0.7.13-2Mozilla-based javascript bindings ii gnome-bluetooth 3.0.0-1 GNOME Bluetooth tools ii gnome-control-ce 1:3.0.0.1-1 utilities to configure the GNOME d ii gnome-icon-theme 3.0.0-1 GNOME Desktop icon theme (symbolic ii gnome-settings-d 3.0.0.1-1 daemon handling the GNOME session ii gsettings-deskto 3.0.0-1 GSettings deskop-wide schemas ii libatk1.0-0 2.0.0-1 The ATK accessibility toolkit ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libcairo-gobject 1.10.2-6The Cairo 2D vector graphics libra ii libcairo21.10.2-6The Cairo 2D vector graphics libra ii libcamel1.2-19 2.32.2-4The Evolution MIME message handlin ii libcanberra0 0.26-3 a simple abstract interface for pl ii libclutter-1.0-0 1.6.10-3Open GL based interactive canvas l ii libcroco30.6.2-1 a generic Cascading Style Sheet (C ii libdbus-1-3 1.5.0-1 simple interprocess messaging syst ii libdbus-glib-1-2 0.92-1 simple interprocess messaging syst ii libdconf00.7.3-4 Simple key-based configuration sys ii libdrm2 2.4.24-2Userspace interface to kernel DRM ii libebook1.2-10 3.0.0-1 Client library for evolution addre ii libecal1.2-8 3.0.0-1 Client library for evolution calen ii libedataserver1. 3.0.0-1 Utility library for evolution data ii libedataserverui 3.0.0-1 GUI utility library for evolution ii libffi5 3.0.9-3 Foreign Function Interface library ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.4-1 FreeType 2 font engine, shared lib ii libgconf2-4 2.32.1-2GNOME configuration database syste ii libgdk-pixbuf2.0 2.23.3-3GDK Pixbuf library ii libgirepository- 0.10.7-1Library for handling GObject intro ii libgjs0b 0.7.13-2Mozilla-based javascript bindings ii libgl1-mesa-glx 7.10.2-1A free implementation of the OpenG
