[Bug 1222341] [NEW] [keyboard]: gnome-control-center crashed with SIGSEGV in g_hash_table_foreach() while closing the window
Public bug reported: Opened the keyboard configuration (via the new Text entry setting... menu option), went a bit through the different configurations, closed the window, and boom. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu33 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 09:14:52 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2012-03-14 (542 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MarkForUpload: True ProcCmdline: gnome-control-center region layouts SegvAnalysis: Segfault happened at: 0x7f7b21595fa6: cmp%rax,(%rdx) PC (0x7f7b21595fa6) ok source %rax ok destination (%rdx) (0x2) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_hash_table_foreach (hash_table=0x306a180, func=0x7f7b5342b4f0, user_data=0x7fffe55d4a10) at /build/buildd/glib2.0-2.37.6/./glib/ghash.c:1526 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: [keyboard]: gnome-control-center crashed with SIGSEGV in g_hash_table_foreach() UpgradeStatus: Upgraded to saucy on 2013-09-07 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash keyboard need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1222341 Title: [keyboard]: gnome-control-center crashed with SIGSEGV in g_hash_table_foreach() while closing the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1222341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1024912] Re: Totem refuses to decode videos not supported by vaapi, Nautilus crashes
This should be fixed in gstreamer-vaapi version 0.5.3, released 18 April 2013. It contains the patch Fix fallback to sofware decoding if no hardware decoder is available. Also, gstreamer-vaapi version 0.3.7, released 26 June 2012, contained the patch Fix vaapidecode to report unsupported codec profiles. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1024912 Title: Totem refuses to decode videos not supported by vaapi, Nautilus crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1024912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222248] Re: regression: scroll areas on touchpad do not work any more
For me touchpad scroll stopped working because the setting was changed to Two finger scroll during upgrade. Edge scrolling started to work after unticking the two finger scroll checkbox. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/148 Title: regression: scroll areas on touchpad do not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222248] Re: regression: scroll areas on touchpad do not work any more
Two finger scroll is selected, but disabled (cannot be changed!). As far as I can tell this two finger scroll does not work either. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/148 Title: regression: scroll areas on touchpad do not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1191565] Re: show OSD all skipped tracks, showing wrong thumbnails, repeating, very annoying
** Branch linked: lp:~sjakthol/notify-osd/fix-1191565 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1191565 Title: show OSD all skipped tracks, showing wrong thumbnails, repeating, very annoying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1191565/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222053] Re: per-session gsettings overrides
Compiling schemas on every login is a waste of both CPU time and also disk space. Perhaps instead of /usr/share/glib-2.0/schemas/gschemas.compiled glib could first look into /usr/share/glib-2.0/schemas/$SESSION/gschemas.compiled and if that doesn't exist, fall back to the standard path? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1222053 Title: per-session gsettings overrides To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1222053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222053] Re: per-session gsettings overrides
Worth noting that it's already possible to add new directories to the schema search path via GSETTINGS_SCHEMA_DIR. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1222053 Title: per-session gsettings overrides To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1222053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222435] [NEW] Does not apply changes to all pictures
Public bug reported: I've rotated several images during one session of the eog. When I decided to close eog, then I've got dialog window with question if I want to save changes of the picture with list of changed pictures. But only the last picture is really changed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: eog 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 8 17:08:49 2013 ExecutablePath: /usr/bin/eog InstallationDate: Installed on 2013-03-28 (163 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: LANGUAGE=pl:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to raring on 2013-05-01 (129 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1222435 Title: Does not apply changes to all pictures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1222435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 473735] Re: empathy keeps showing network error on facebook account
Yes, I also have this error ... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/473735 Title: empathy keeps showing network error on facebook account To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/473735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1096311] Re: totem should support High 4:2:2 High 4:4:4 Predictive@L3.2 decoding
The sample video attached to comment #1 plays fine in Totem here on Ubuntu 13.04 with kernel Linux 3.8.0-19-generic i686. In addition to libgstreamer0.10-0 0.10.36-1ubuntu2, libgstreamer1.0-0 1.0.6-1and gstreamer1.0-plugins-good 1.0.6-1ubuntu1, I have installed gstreamer1.0 -plugins-bad 1.0.6-1ubuntu1 and gstreamer1.0-plugins-ugly 1.0.6-1. Are you still able to reproduce this on an up to date Ubuntu 13.04? ** Changed in: gstreamer0.10 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1096311 Title: totem should support High 4:2:2 High 4:4:4 Predictive@L3.2 decoding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1096311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1029412] Re: Bring back the old 'compact' format, coz the latest one is (a) not compact and (b) not compact and (c) has a teenie zoom level
What version of Ubuntu and Nautilus are you using? I think this bug no longer applies, since the current Nautilus (version 3.8.2 in Ubuntu 13.10) has no compact view at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1029412 Title: Bring back the old 'compact' format, coz the latest one is (a) not compact and (b) not compact and (c) has a teenie zoom level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1029412/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1057019] Re: No format option for devices in Nautilus
I think this bug no longer applies to the current version of Nautilus (3.8.2 in Ubuntu 13.10). In that version, the Computer page lists files in the root directory of my hard drive. Devices are shown only in the sidebar. If I right click a device there, there is a Format... option in the context menu. I recommend marking this bug invalid. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1057019 Title: No format option for devices in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1057019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222446] [NEW] Format... does nothing
Public bug reported: I'm running Nautilus 3.8.2 on Ubuntu 13.10 To see the problem: 1. Insert a removable drive such as a USB flash drive. It will appear in the Nautilus sidebar. 2. Right click the drive and choose Format... 3. Nothing happens. If you run Nautilus from a terminal, then you'll see this message as this problem occurs: (gnome-disks:13712): GLib-GIO-CRITICAL **: This application can not open files. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1222446 Title: Format... does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1222446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069235] Re: Cannot format disk with new partition table
I'm running gnome-disk-utility 3.6.1 on Ubuntu 13.10. I see this same error whenever I try to format any USB drive at all. Perhaps all of my USB drives already have partition tables. In any case, the format command should be able to format any disk, no matter what is on it already. ** Summary changed: - Cannot format disk with new partition table + Cannot format disk with existing partition table: Error synchronizing after initial wipe: Timed out waiting for object -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1069235 Title: Cannot format disk with existing partition table: Error synchronizing after initial wipe: Timed out waiting for object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1069235/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
On 13-09-04 10:19 AM, Mark Smith wrote: This allows administrative users travelling with laptops to change the timezone without getting an authentication prompt. Why is saving the traveling admin from typing their password a couple of times a day worth compromising security for everyone else? No, seriously. Why? It only compromises security for people who use sudo on their workstation, and don't add the -k flag to the command line when they do. I suspect there are more users who travel with their laptops than there are people who use sudo on them. Your attack vector assumes that an administrative user is going to leave an open session unattended. Yes, my assumption is that users will forget to lock their machines, because it happens all the time. This is especially true if it's a personal machine, and they are the ONLY user. If you can't rely on admins to properly lock their session, you can't rely on them to not leave a console open with sudo rights either. At some point a minimum is required. Locking their console, or using sudo with -k is the minimum. If that is the case, there are a whole slew of attacks that are possible, and don't require changing the date. For example, creating scripts in ~/bin that are higher in the path then system binaries. Even if that number is high, that's no excuse. Is your stance really Well, they could compromise security 100 ways, so what's one more? Plus, how many of those attacks require 0 external resources, and creating 0 additional files on the system, and would leave little trace beyond a hiccup in the time/date? I'm saying preventing the admin user from modifying the system clock is security theatre if the system is configured to use ntp, or doesn't prevent access to changing the clock in the system firmware. Even if the admin user needs a password to change the clock, anyone can step up to the workstation and plug in a network cable to a fake ntp server. If you want to be able to trust the system time, you need to harden a lot more than simply requiring a password prompt. Since your local security policy is different than what is shipped in a general purpose operating system... Wanting a slightly more secure system is more of an edge case than changing the time zone repeatedly? REALLY? Does Windows 8 count as general purpose to you? It requires escalation to change the date and time. Maybe their escalation system isn't very good, but it's still better than blithely letting admins change the system time without so much as a prompt. Also, their security system doesn't rely on file timestamps, so it's less likely to grant someone root access. There's a fine balance between security and usability, and not everyone is comfortable with the same level of security. As I've mentioned before, it is trivial to modify the defaults to achieve the level of security that is appropriate for your environment. 1- Requiring your administrative users to lock their workstation when they are left unattended. People make mistakes. Are you telling me you've NEVER forgotten to lock your workstation? You've NEVER seen another admin forget to lock theirs? Yes, this happens, and is quite unfortunate. What I'm saying is being able to change the system clock is only one of a whole series of possible attacks if the session is left unattended. 2- Requiring your administrative users to use sudo -k to forcibly invalidate cached credentials. That only works on a per pty/tty basis on ubuntu. It only invalidates one of the sessions, and it invalidates it by changing the timestamp to a date to Dec. 31, 1969 or Jan. 1, 1970. You could try sudo -K, which deletes the file, but again only on a per pty/tty basis. Sudo considers cached credential files with epoch timestamps to be invalid, even if you do set the clock to epoch. (Unless you're vulnerable to CVE-2013-1775). Adding -k to your sudo commands will prevent caching. 3- Removing the policykit-desktop-privileges package, or overriding the policy with a local one. Oh good, more administrative work, all to save typing a password! Pity about all the users who don't know what policykit-desktop-privileges is or does though... 4- Disabling ntp, or setting up ntp authentication. Disabling ntp wouldn't help, since the whole point is that the user can change the time to anything manually anyhow. Disabling ntp is a required part of the process if you don't want an attacker to be able to alter the system clock. 5- Setting a firmware password on local machines. This doesn't help if they walked away and forgot to lock their machines. Again, it is a required part of the process if you don't want an attacker to simply reboot and change the clock in the firmware. I especially love how #2 requires the user to remember to execute a command before they close their terminal, and adds an extra 7 keystrokes PER TTY/PTY. All this to save a
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-1775 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
** CVE removed: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-1775 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222481] [NEW] Rhythmbox crashes with segfault when track changes.
Public bug reported: OS: Xubuntu 13.10 Saucy Salamander Steps to reproduce the issue: - Start Rhythmbox - Play song - Wait for track to change or skip tracks by pressing Next Expected result: Rhythmbox doesn't crash. Actual Result: Rhythmbox crashes with segmention fault. martin@AspireONE:~$ rhythmbox ** (rhythmbox:4123): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-yY9FOsn9sC: Verbindungsaufbau abgelehnt (rhythmbox:4123): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (rhythmbox:4123): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed (rhythmbox:4123): Gtk-CRITICAL **: gtk_application_inhibit: assertion 'application-priv-sm_proxy != NULL' failed Speicherzugriffsfehler ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: rhythmbox saucy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1222481 Title: Rhythmbox crashes with segfault when track changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1222481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 903422] Re: Ubuntu does not work with Samsung Galaxy phones (Unable to open raw device 0)
Nexus S Android 4.1.2 Build JZO54K Ubuntu 13.04 Error: Unable to Mount Nexus S Unable to open MTP device '[usb:001,005]' $ gmtp Device 0 (VID=18d1 and PID=4e21) is a Google Inc (for Samsung) Nexus S. LIBMTP PANIC: Unable to find interface endpoints of device Detect: Unable to open raw device? LIBMTP PANIC: Trying to dump the error stack of a NULL device! LIBMTP PANIC: Trying to clear the error stack of a NULL device! $ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.5 Listing raw device(s) Device 0 (VID=18d1 and PID=4e21) is a Google Inc (for Samsung) Nexus S. Found 1 device(s): Google Inc (for Samsung): Nexus S (18d1:4e21) @ bus 1, dev 5 Attempting to connect device(s) LIBMTP PANIC: Unable to find interface endpoints of device Unable to open raw device 0 OK. $ lsusb -vs 001:006 Bus 001 Device 006: ID 18d1:4e21 Google Inc. Nexus S Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x18d1 Google Inc. idProduct 0x4e21 Nexus S bcdDevice2.31 iManufacturer 2 samsung iProduct3 Nexus S iSerial 4 37351D bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 1 Mass Storage Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0001 Self Powered -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/903422 Title: Ubuntu does not work with Samsung Galaxy phones (Unable to open raw device 0) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/903422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1201128] Re: .directory files contain references to inappropriate icons
** Branch linked: lp:ubuntu/saucy-proposed/gnome-menus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1201128 Title: .directory files contain references to inappropriate icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1201128/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
There's a fine balance between security and usability, and not everyone is comfortable with the same level of security. As I've mentioned before, it is trivial to modify the defaults to achieve the level of security that is appropriate for your environment. If that's the case, why are you defaulting to a level that Debian, Fedora, Mint, and Windows all feel is too lax? Why not let the very few users who need this, change it to be less secure? Based on my discussions, it seems that this is actually a *sudo* bug, since it uses the non-monotonic clock, rather than using other system features. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
If that's the case, why are you defaulting to a level that Debian, Fedora, Mint, and Windows all feel is too lax? Why not let the very few users who need this, change it to be less secure? Because those desktop environments don't provide automatic geoip-based timezone updating. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1201128] Re: .directory files contain references to inappropriate icons
This bug was fixed in the package gnome-menus - 3.8.0-1ubuntu4 --- gnome-menus (3.8.0-1ubuntu4) saucy; urgency=low * Update some of the directory icon names (LP: #1201128) -- Jeremy Bicha jbi...@ubuntu.com Sun, 08 Sep 2013 14:31:02 -0400 ** Changed in: gnome-menus (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1201128 Title: .directory files contain references to inappropriate icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1201128/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222522] [NEW] Upgrade evolution-data-server to 3.8.5
Public bug reported: We should update evolution-data-server from 3.8.4 to 3.8.5 https://git.gnome.org/browse/evolution-data-server/tree/NEWS?h=gnome-3-8 However I have not been able to get e-d-s 3.8.5 to run without crashing here. I tried rebuilding e-d-s 3.8.4 in case something elsewhere in Ubuntu broke but 3.8.4 works fine. The Evolution maintainers are now using tighter dependencies, apparently because they don't guarantee ABI compatibility even for stable release updates. Therefore this is blocking us from being able to upgrade the rest of the evolution stack to 3.8.5. We should be able to just sync evolution-mapi and evolution-ews from Debian when we're ready though. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1222522 Title: Upgrade evolution-data-server to 3.8.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1222522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1201128] Re: missing icons for .directory files
** Summary changed: - .directory files contain references to inappropriate icons + missing icons for .directory files ** Changed in: gnome-menus (Ubuntu) Importance: Undecided = Wishlist ** Changed in: gnome-menus (Ubuntu) Status: Fix Released = Confirmed ** Also affects: gnome-icon-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-icon-theme (Ubuntu) Importance: Undecided = Wishlist ** Changed in: gnome-icon-theme (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1201128 Title: missing icons for .directory files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1201128/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
Looks like upstream GNOME is now also allowing this too, so presumably the other distros will have a similar policy: https://git.gnome.org/browse/gnome-control-center/commit/panels/common /gnome-control-center.rules?id=88eeb8cb2d28d75610b1fa39839e69388ceb4eca https://bugzilla.gnome.org/show_bug.cgi?id=646185 ** Bug watch added: GNOME Bug Tracker #646185 https://bugzilla.gnome.org/show_bug.cgi?id=646185 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222538] [NEW] Unable to encrypt or sign files with current glib
Public bug reported: since commit ce0022933c255313e010b27f977f4ae02aad1e7e can no longer encrypt or sign local files (https://git.gnome.org/browse/glib/commit/?id=ce0022933c255313e010b27f977f4ae02aad1e7e Ex. seahorse-tool -e /home/doug/Documents/test ** (seahorse-tool:14708): WARNING **: couldn't load all the keys (1/2) from GPGME (seahorse-tool:14708): GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly. Also affects seahorse-nautilus plugin, nothing happens exact same warning shows in either~/.xsession-errors or ~/.cache/upstart/gnome- session.log The commit mentioned was partially reverted though no effect for seahorse, ect. Mentioned here but not to extent of what's seen in Ubuntu (seahorse-tool also failing https://bugzilla.redhat.com/show_bug.cgi?id=981580 Know nothing about glib but if I extend the revert as seen in diff here - https://launchpad.net/~mc3man/+archive/saucy-prop/+files/glib2.0_2.37.6-1ubuntu1_2.37.6-1ubuntu1%2Bmc3man1.diff.gz Then seahorse-tool nautilus work, still get a similar warning but encryption, signing work Ex. $ seahorse-tool -e '/home/doug/Documents/test1' ** (seahorse-tool:12017): WARNING **: couldn't load all the keys (1/2) from GPGME ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: seahorse 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 15:41:32 2013 InstallationDate: Installed on 2013-08-07 (31 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803) MarkForUpload: True SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages ** Description changed: since commit ce0022933c255313e010b27f977f4ae02aad1e7e can no longer encrypt or sign local files (https://git.gnome.org/browse/glib/commit/?id=ce0022933c255313e010b27f977f4ae02aad1e7e Ex. seahorse-tool -e /home/doug/Documents/test ** (seahorse-tool:14708): WARNING **: couldn't load all the keys (1/2) from GPGME (seahorse-tool:14708): GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly. Also affects seahorse-nautilus plugin, nothing happens exact same - warning shows in either~/.xsession-errors or ~.cache/upstart/gnome- + warning shows in either~/.xsession-errors or ~/.cache/upstart/gnome- session.log The commit mentioned was partially reverted though no effect for seahorse, ect. Mentioned here but not to extent of what's seen in Ubuntu (seahorse-tool also failing https://bugzilla.redhat.com/show_bug.cgi?id=981580 - Know nothing about glib but if I extend the revert as seen in diff here - + Know nothing about glib but if I extend the revert as seen in diff here - https://launchpad.net/~mc3man/+archive/saucy-prop/+files/glib2.0_2.37.6-1ubuntu1_2.37.6-1ubuntu1%2Bmc3man1.diff.gz Then seahorse-tool nautilus work, still get a similar warning but encryption, signing work Ex. - $ seahorse-tool -e '/home/doug/Documents/test1' + $ seahorse-tool -e '/home/doug/Documents/test1' ** (seahorse-tool:12017): WARNING **: couldn't load all the keys (1/2) from GPGME ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: seahorse 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 15:41:32 2013 InstallationDate: Installed on 2013-08-07 (31 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803) MarkForUpload: True SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1222538 Title: Unable to encrypt or sign files with current glib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1222538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
** Also affects: sudo Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1222522] Re: Upgrade evolution-data-server to 3.8.5
To anyone in interested in this, it's already in debian unstable. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1222522 Title: Upgrade evolution-data-server to 3.8.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1222522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
** Bug watch added: Sudo Bugzilla #616 http://www.sudo.ws/bugs/show_bug.cgi?id=616 ** Changed in: sudo Importance: Undecided = Unknown ** Changed in: sudo Status: New = Unknown ** Changed in: sudo Remote watch: None = Sudo Bugzilla #616 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
GNOME 3.10 will indeed allow local admins (not standard users) to change time settings without typing a password. It also introduces automatic geolocation-based timezone updating. :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
Michael: But again, this totally ignores the question: Why on earth do we need that? How many times per day are you changing your clock that this is necessary?! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
Todd C Miller is working on it from the sudo side upstream, potentially using CLOCK_MONOTONIC. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
oh, that would be great! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219188] Re: FFe: Add support for separate background on lock screen
** Branch linked: lp:~ubuntu-desktop/gnome-control-center/ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219188 Title: FFe: Add support for separate background on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1219188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219188] Re: FFe: Add support for separate background on lock screen
** Branch linked: lp:ubuntu/saucy-proposed/gnome-control-center -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219188 Title: FFe: Add support for separate background on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1219188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219188] Re: FFe: Add support for separate background on lock screen
This bug was fixed in the package gnome-control-center - 1:3.6.3-0ubuntu34 --- gnome-control-center (1:3.6.3-0ubuntu34) saucy; urgency=low * debian/patches: - git-background-remove-unused-widget.patch - git-background-lock-screen.patch: Allow setting a different background for the GNOME Shell lock screen (LP: #1219188) -- Tim Lunn t...@feathertop.org Mon, 09 Sep 2013 11:17:34 +1000 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219188 Title: FFe: Add support for separate background on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1219188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 413553] Re: Cannot write offline journal for folder 'INBOX': Success
I had the same problem using Evolution 3.2.3. Solved the problem by deleting the affected file in dir .local/share/evolution/mail/..@loginname/FILE. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/413553 Title: Cannot write offline journal for folder 'INBOX': Success To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/413553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
Hi, This bug is reported against Ubuntu 12.04. Could we also apply this patch on Ubuntu 12.04? (Maybe on 12.10 and 13.04 too?) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1199554] Re: somrthing wrong
[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.] ** Changed in: file-roller (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1199554 Title: somrthing wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1199554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 447799] Re: no sound on hp dv6-1030ef
yml, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux replace-with-bug-number Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.11 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** This bug is no longer a duplicate of bug 427670 hp dv6 no sound hda Intel ** Package changed: gst0.10-python (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst0.10-python in Ubuntu. https://bugs.launchpad.net/bugs/447799 Title: no sound on hp dv6-1030ef To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/447799/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219486] Re: FFe: Update gnome-settings-daemon to 3.8.4
No need to build from source now as Tim's PPA has been updated again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1219486 Title: FFe: Update gnome-settings-daemon to 3.8.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1219486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
