[Desktop-packages] [Bug 1315384] Re: python-indicate not showing up in message indictor
libmessaging-menu already comes with python bindings through gobject-
introspection. Unfortunately the online documentation seems to have been
taken down. The libmessaging-menu-dev package contains the C
documentation (viewable with devhelp), which maps 1:1 to the python API.
Here's a simple example:
from gi.repository import GLib, Gio, MessagingMenu
mmapp = MessagingMenu.App(desktop_id='my-app.desktop')
# make the application appear in the messaging menu. The name and icon are
taken from the desktop file above
mmapp.register()
def source_activated(mmapp, source_id):
print('source {} activated'.format(source_id))
# do something when the user clicks on a source. The source will be removed
automatically
mmapp.connect('activate-source', source_activated)
# add a 'source' (a menu item below the application's name) with the name
'Inbox' and a count of 7
icon = Gio.ThemedIcon.new_with_default_fallbacks('my-source-icon')
mmapp.append_source_with_count('inbox', icon, 'Inbox', 7)
# this is not necessary for gtk applications, which start a mainloop in
gtk_main()
GLib.MainLoop().run()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libindicate in Ubuntu.
https://bugs.launchpad.net/bugs/1315384
Title:
python-indicate not showing up in message indictor
Status in Libindicate:
Confirmed
Status in “libindicate” package in Ubuntu:
Confirmed
Bug description:
Install python-indicate and libindicate-doc. Run:
python /usr/share/doc/libindicate/examples/im-client.py
An entry should appear in message indicator, but does not. That worked
in 12.04 but is broken in 14.04.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-indicate 12.10.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 2 15:22:27 2014
InstallationDate: Installed on 2014-05-01 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: libindicate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
This also affects the `gnome-keyring` package. The System76 imaging system (Tribble) uses a tar-based approach similar to the MAAS fast-path installer, and we've had to add a work-around for /usr/bin/gnome- keyring-daemon on our desktop images: $ getcap /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon = cap_ipc_lock+ep I reckon there are other imaging systems out there likewise affected by this. I strongly feel that the correct fix is to fix tar so its --xattrs option works as expected. But in the meantime, it might be good to switch back to using suid on /usr/bin/gnome-keyring-daemon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Confirmed Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1317376] [NEW] Keyboard switching overrides a user specified xmodmap keymap
Public bug reported: I have a configured keyboard input sources switching in the menu: System Settings → Keyboard → Shortcuts → Typing → Switch to next source: Alt + Shift L Switch to previous source: Shift + Meta L Also I have a manually launched command: xmodmap ~/.Xmodmap The ~/.Xmodmap contains settings to remap few numpad buttons: keycode 81 = Prior KP_9 Prior KP_9 keycode 89 = Next KP_3 Next KP_3 keycode 90 = Insert KP_0 Insert KP_0 keycode 91 = Delete KP_Decimal Delete KP_Separator The remapped keys works as expected as long as no keyboard input source switching occurs. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Thu May 8 11:54:11 2014 ExecutablePath: /usr/bin/unity-control-center SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-05-06 (2 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 gnome-control-center 1:3.6.3-0ubuntu56 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1317376 Title: Keyboard switching overrides a user specified xmodmap keymap Status in “unity-control-center” package in Ubuntu: New Bug description: I have a configured keyboard input sources switching in the menu: System Settings → Keyboard → Shortcuts → Typing → Switch to next source: Alt + Shift L Switch to previous source: Shift + Meta L Also I have a manually launched command: xmodmap ~/.Xmodmap The ~/.Xmodmap contains settings to remap few numpad buttons: keycode 81 = Prior KP_9 Prior KP_9 keycode 89 = Next KP_3 Next KP_3 keycode 90 = Insert KP_0 Insert KP_0 keycode 91 = Delete KP_Decimal Delete KP_Separator The remapped keys works as expected as long as no keyboard input source switching occurs. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Thu May 8 11:54:11 2014 ExecutablePath: /usr/bin/unity-control-center SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-05-06 (2 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 gnome-control-center 1:3.6.3-0ubuntu56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1317376/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
William: I installed your packages, logged out and in of Gnome Classic Flashback (Metacity) on 14.04. But it does not work. I tried to set ALT+LSHIFT, LCTRL+LSHIFT, LALT+LCTRL, ALTGR+RCTRL, ALTGR+RSHIFT, RCTRL+RSHIFT, LCTRL+ALTGR, LCTRL+RCTRL, LCTRL+RSHIFT. Is there an easy way to switch back from your packages to the non-ppa packages? I think ALTGR+RCTRL worked before installing your ppa but I want to verify. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Fedora: Unknown Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have
[Desktop-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Description changed: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine, press the Super key Expected Result: the super key acts inside the VM Actual Result: the super key acts in the host and the Unity Dash is displayed [regression Potential] - This patch plays with ket grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does nto invoke the Unity Dash. + This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: New Bug description: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine, press the Super key Expected Result: the super key acts inside the VM Actual Result: the super key acts in the host and the Unity Dash is displayed [regression Potential] This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+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 1317105] Re: USB sound card not detected
Post the output of lsusb - -d 0d8c:01af lsusb - -d 0d8c:0170 Card hw:1 'OnurHeadset'/'Cmedia OnurHeadset at usb-:00:1d.0-1.5.1, full speed' Mixer name: 'USB Mixer' Components: 'USB0d8c:01af' Controls : 9 Simple ctrls : 4 Card hw:3 'OnurHandset'/'Cmedia OnurHandset at usb-:00:1d.0-1.5.2, full speed' Mixer name: 'USB Mixer' Components: 'USB0d8c:0170' Controls : 15 Simple ctrls : 6 do your usb audio devices really support digital input (IEC958) ? device.bus = usb device.vendor.id = 0d8c device.vendor.name = C-Media Electronics, Inc. device.product.id = 0170 device.product.name = OnurHandset device.serial = Cmedia_OnurHandset_2.0.0.6 device.form_factor = handset device.string = 3 device.description = OnurHandset module-udev-detect.discovered = 1 device.icon_name = phone-usb device.intended_roles = phone profiles: input:analog-stereo: Analog Stereo Input (priority 60, available: unknown) input:iec958-stereo: Digital Stereo (IEC958) Input (priority 55, available: unknown) output:analog-stereo: Analog Stereo Output (priority 6000, available: unknown) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: unknown) output:analog-stereo+input:iec958-stereo: Analog Stereo Output + Digital Stereo (IEC958) Input (priority 6055, available: unknown) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5560, available: unknown) output:iec958-stereo+input:iec958-stereo: Digital Stereo Duplex (IEC958) (priority , available: unknown) off: Off (priority 0, available: unknown) ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1317105 Title: USB sound card not detected Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Cmedia USB audio codec CM6571 USB audio device is not recognized in startup. It is recognized after system loads and plugging the usb cableoff and on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: burak 1957 F pulseaudio /dev/snd/controlC2: burak 1957 F pulseaudio /dev/snd/controlC1: burak 1957 F pulseaudio /dev/snd/controlC0: burak 1957 F pulseaudio CurrentDesktop: Unity Date: Wed May 7 16:47:07 2014 InstallationDate: Installed on 2014-03-26 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to trusty on 2014-05-07 (0 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J51 v01.20 dmi.board.asset.tag: CZC209BJTS dmi.board.name: 1587h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC209BJTS dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ51v01.20:bd09/16/2011:svnHewlett-Packard:pnHPZ210Workstation:pvr:rvnHewlett-Packard:rn1587h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z210 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317105/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
** Tags added: 201307-13919 taipei-lab ** Attachment added: xorg.conf and gpu-manager.log - logs.tar.xz https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+attachment/4107835/+files/xorg-gpu.logs.tar.xz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1315285 Title: [AMD Richland + Mars] Unable to switch graphics Status in “fglrx-installer” package in Ubuntu: New Bug description: Unable to switch in between APU and Discrete GPU. Step to reproduce: Oepn AMD Crystal Control Center, $ sudo amdcccle Expected: Switchable graphics settings menu will shown Actual result: Found no switchable graphics settings Currently found effected: APU: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] with GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1562 F pulseaudio /dev/snd/controlC0: ubuntu 1562 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri May 2 15:59:50 2014 HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 Notebook PC dmi.product.version: A201BC1203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1317391] [NEW] ginn error subscribing to gestures
Public bug reported: ginn doesn't work. To solve the problem, see http://askubuntu.com/questions/57586/how-can-i-disable-arbitrary- default-multitouch-gestures-in-unity/90383#90383Answer #9 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 8 09:55:24 2014 InstallationDate: Installed on 2013-10-15 (204 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (20 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1317391 Title: ginn error subscribing to gestures Status in “unity” package in Ubuntu: New Bug description: ginn doesn't work. To solve the problem, see http://askubuntu.com/questions/57586/how-can-i-disable-arbitrary- default-multitouch-gestures-in-unity/90383#90383Answer #9 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 8 09:55:24 2014 InstallationDate: Installed on 2013-10-15 (204 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1317391/+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 1317394] [NEW] spurious ERROR: [...] has no compat file from emacs-package-install
Public bug reported: Seen in trusty on initial installation of a new-style *-el package: ERROR: package-name is broken - called emacs-package-install as a new-style add-on, but has no compat file. Unpacking package-name (version) ... The package does have a compat file. I believe that the error message is issued because the preinst script runs before the compat file is in place. There is no second error message after the Unpacking line. Also, if I subsequently do an apt-get install --reinstall of that package the error message does not appear at all. This is very minor (the exit 1; line in /usr/lib/emacsen-common/lib.pl is commented out) but may worry some users needlessly. ** Affects: emacsen-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacsen-common in Ubuntu. https://bugs.launchpad.net/bugs/1317394 Title: spurious ERROR: [...] has no compat file from emacs-package-install Status in “emacsen-common” package in Ubuntu: New Bug description: Seen in trusty on initial installation of a new-style *-el package: ERROR: package-name is broken - called emacs-package-install as a new-style add-on, but has no compat file. Unpacking package-name (version) ... The package does have a compat file. I believe that the error message is issued because the preinst script runs before the compat file is in place. There is no second error message after the Unpacking line. Also, if I subsequently do an apt-get install --reinstall of that package the error message does not appear at all. This is very minor (the exit 1; line in /usr/lib/emacsen- common/lib.pl is commented out) but may worry some users needlessly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacsen-common/+bug/1317394/+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 1067901] Re: can't configure any accounts in empathy
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect bug # and any other logs that are relevant for this particular issue. ** Changed in: empathy (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1067901 Title: can't configure any accounts in empathy Status in “empathy” package in Ubuntu: Incomplete Bug description: Accounts can't be configured in empathy in 12.10. I think this is because of the online accounts fork (I have the gnome-shell version of online accounts, but not the ubuntu version). I think maybe I should have both? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Wed Oct 17 15:03:54 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to quantal on 2012-10-11 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1067901/+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 1065103] Re: AgManager doesn't emit enabled-events for jabber and salut
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect bug # and any other logs that are relevant for this particular issue. ** Changed in: empathy (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1065103 Title: AgManager doesn't emit enabled-events for jabber and salut Status in “empathy” package in Ubuntu: Incomplete Bug description: AgManager doesn't emit enabled-events for jabber and salut, and possible some others. Google talk and facebook accounts do. This means empathy/mission-control doesn't notice when accounts are disabled/enabled. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: account-plugin-jabber 3.6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 10 11:18:56 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120514) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1065103/+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 1058365] Re: Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect bug # and any other logs that are relevant for this particular issue. ** Changed in: empathy (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1058365 Title: Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN Status in “empathy” package in Ubuntu: Incomplete Bug description: Hi, All! I am on Ubuntu 12.04 amd64 and I connect to my office network using Cisco VPN (network-manager-vpnc). The problem is that Empathy (with telepathy-sofiasip installed) cannot connect to a SIP-server inside VPN (while e.g., Ekiga can). Some traces taken with Wireshark show up that Empathy sends packages into the VPN tunnel with properly resolved destination IP-address but with wrong source IP-address (eth0 instead of tun0). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058365/+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 1051964] Re: empathy-auth-client crashed with SIGABRT in g_assertion_message()
** Information type changed from Private to Public ** Changed in: empathy (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1051964 Title: empathy-auth-client crashed with SIGABRT in g_assertion_message() Status in “empathy” package in Ubuntu: Invalid Bug description: Empathy crashed as soon as I started it. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: empathy 3.5.91.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Mon Sep 17 15:29:44 2012 ExecutablePath: /usr/lib/empathy/empathy-auth-client InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcCmdline: /usr/lib/empathy/empathy-auth-client ProcCwd: / Signal: 6 SourcePackage: empathy StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0 Title: empathy-auth-client crashed with SIGABRT in raise() UpgradeStatus: Upgraded to quantal on 2012-09-10 (7 days ago) UserGroups: adm admin audio cdrom dialout lp lpadmin plugdev sambashare video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1051964/+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 1061892] Re: Internal Error when trying to connect
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect bug # and any other logs that are relevant for this particular issue. ** Changed in: empathy (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1061892 Title: Internal Error when trying to connect Status in “empathy” package in Ubuntu: Incomplete Bug description: Every time I boot up Empathy refuses to connect to my two gTalk accounts for a while. Sometimes it resolves itself within 5 minutes, while other times it takes a lot longer. It doesn't matter if I change my online status to Offline and back to Online, or click the little blue reload button, nothing seems to work. This has been happening since I upgraded to 12.10 and Empathy was tied into the Online Accounts system. What can I do to debug this so it can be fixed? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 07:01:11 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120914) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1061892/+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 1316728] Re: [System Product Name, Realtek ALC887, SPDIF Out, Internal] No sound at all
you have to turn off this switch since it allow signal send to analog device copy to digital device when this switch is on but it also disable you to use digital device Simple mixer control 'IEC958 Default PCM',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1316728 Title: [System Product Name, Realtek ALC887, SPDIF Out, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: system done outomatic upgrade sound works fine before the upgrade. /Jideck ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasiek 1356 F pulseaudio /dev/snd/controlC0: jasiek 1356 F pulseaudio /dev/snd/pcmC0D1p: jasiek 1356 F...m pulseaudio CurrentDesktop: Unity Date: Tue May 6 17:14:32 2014 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasiek 1356 F pulseaudio /dev/snd/controlC0: jasiek 1356 F pulseaudio /dev/snd/pcmC0D1p: jasiek 1356 F...m pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887, SPDIF Out, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-05-04 (2 days ago) dmi.bios.date: 04/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd04/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316728/+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 1272725]
*** Bug 77687 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1272725 Title: [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: New Bug description: Problem description: In Calc, right-clicking on any cell and then selecting Format Cells often produces a dialog box that is unusable as it is almost transparent. Closing and re-opening the dialog has no effect. Calc has to be restarted to clear the problem. Steps to reproduce: 1. Right click on any Calc cell 2. Select Format Cell Current behavior: Dialog is partly transparent or perhaps it would be better to say its contents are mostly missing. Expected behavior: Dialog allows formatting of cell with all contents visible. Please note: This doesn't happen all of the time but has happened often enough for me to report this as a bug. I'm using Kubuntu 14.04, fully updated with LibreOffice loaded from PPA. The previous version, in the Ubuntu archive (4.1.3?) also exhibits this problem. KDE version is 4.12.1. --- ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-01-01 (24 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140101) Package: libreoffice 1:4.2.0~rc2-0ubuntu1~trusty2 [origin: LP-PPA-libreoffice-libreoffice-prereleases] PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Tags: trusty third-party-packages Uname: Linux 3.13.0-5-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1272725/+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 1272725]
I have this problem also, I am running Kubuntu 14.04 on 64 bit. I notice that it does not happen initially when I select format cells, unfortunately I am not certain of the catalyst, but maybe it is saving the file, but not advanced features I am certain. I do this regularly and with a manual click, after a few cells are typed and a little copy- cut and pasting is done the file is saved, and then this transparency problem occurs with the right click format cells menu/dialogue. This problem is not a crash to Desktop, but I must close and re-open Loffice to get the menu to activate. ( I also have encountered a similar sort of time initiated problem with importing pictures into a spreadsheet. After some time generally I have to save before importing a picture as the program will Crash-to-desktop. I only mention this because it will generally work initially. ) I will update if I can narrow the issue to a pinpoint. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1272725 Title: [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: New Bug description: Problem description: In Calc, right-clicking on any cell and then selecting Format Cells often produces a dialog box that is unusable as it is almost transparent. Closing and re-opening the dialog has no effect. Calc has to be restarted to clear the problem. Steps to reproduce: 1. Right click on any Calc cell 2. Select Format Cell Current behavior: Dialog is partly transparent or perhaps it would be better to say its contents are mostly missing. Expected behavior: Dialog allows formatting of cell with all contents visible. Please note: This doesn't happen all of the time but has happened often enough for me to report this as a bug. I'm using Kubuntu 14.04, fully updated with LibreOffice loaded from PPA. The previous version, in the Ubuntu archive (4.1.3?) also exhibits this problem. KDE version is 4.12.1. --- ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-01-01 (24 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140101) Package: libreoffice 1:4.2.0~rc2-0ubuntu1~trusty2 [origin: LP-PPA-libreoffice-libreoffice-prereleases] PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Tags: trusty third-party-packages Uname: Linux 3.13.0-5-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1272725/+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
Re: [Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with PrintScreen key in Unity session in Trusty
As advised by someone above, the temporary solution to remap the screenshot key to Ctrl+M works. On Thu, May 8, 2014 at 1:21 AM, Graeme gra...@sudo.ca wrote: I'm seeing this issue on Trusty but not on a laptop, and with a USB keyboard: KeyRelease event, serial 28, synthetic NO, window 0x401, root 0x296, subw 0x0, time 440656382, (72,58), root:(492,110), state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False That's the key event that doesn't trigger a screenshot on my computer. The keyboard shortcuts dialogue registers it as the Print key when I try and change the screenshot shortcut to it, so it looks like unity sees the key correctly, it just doesn't trigger a printscreen event. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1282649 Title: Unable to make screenshot with PrintScreen key in Unity session in Trusty Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: In Trusty with all installed updates it is not possible to make ScreenShot with Print Screen keyboard button. The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and desired screenshot is not saved in ~/Pictures. Tested in guest and normal sessions. Please fix this bug. Do not forget about Alt+PrintScreen, Ctrl+PrintScreen and Ctrl+Shift+PrintScreen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 20 19:40:24 2014 DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:907a] InstallationDate: Installed on 2013-10-20 (123 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Sony Corporation VPCF13Z1R ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago) dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF13Z1R dmi.product.version: C607OEHZ dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 20 19:32:11 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+subscriptions -- Regards, Aaruni Kaushik -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1282649 Title: Unable to make screenshot with PrintScreen key in Unity session in Trusty Status in “unity-settings-daemon” package in Ubuntu: Fix Released Bug description: In Trusty with all installed updates it is not possible to make
[Desktop-packages] [Bug 1317105] Re: USB sound card not detected
lsusb - -d 0d8c:0170 gives nothing, lsusb - -d 0d8c:01af output is attached. Yes, the devices have digital input channels ** Attachment added: lsusb - -d 0d8c:01af output https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317105/+attachment/4107876/+files/01af.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1317105 Title: USB sound card not detected Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Cmedia USB audio codec CM6571 USB audio device is not recognized in startup. It is recognized after system loads and plugging the usb cableoff and on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: burak 1957 F pulseaudio /dev/snd/controlC2: burak 1957 F pulseaudio /dev/snd/controlC1: burak 1957 F pulseaudio /dev/snd/controlC0: burak 1957 F pulseaudio CurrentDesktop: Unity Date: Wed May 7 16:47:07 2014 InstallationDate: Installed on 2014-03-26 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to trusty on 2014-05-07 (0 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J51 v01.20 dmi.board.asset.tag: CZC209BJTS dmi.board.name: 1587h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC209BJTS dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ51v01.20:bd09/16/2011:svnHewlett-Packard:pnHPZ210Workstation:pvr:rvnHewlett-Packard:rn1587h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z210 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317105/+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 1317105] Re: USB sound card not detected
3.8 also doesn't have problem. 3.11, 3.13 we have problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1317105 Title: USB sound card not detected Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Cmedia USB audio codec CM6571 USB audio device is not recognized in startup. It is recognized after system loads and plugging the usb cableoff and on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: burak 1957 F pulseaudio /dev/snd/controlC2: burak 1957 F pulseaudio /dev/snd/controlC1: burak 1957 F pulseaudio /dev/snd/controlC0: burak 1957 F pulseaudio CurrentDesktop: Unity Date: Wed May 7 16:47:07 2014 InstallationDate: Installed on 2014-03-26 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to trusty on 2014-05-07 (0 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J51 v01.20 dmi.board.asset.tag: CZC209BJTS dmi.board.name: 1587h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC209BJTS dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ51v01.20:bd09/16/2011:svnHewlett-Packard:pnHPZ210Workstation:pvr:rvnHewlett-Packard:rn1587h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z210 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317105/+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 1317105] Re: USB sound card not detected
The problem occurs in some kernels. For example kernel 3.2.0-57 doesn't have problem. It recognizes the CM6571 with the poweron. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1317105 Title: USB sound card not detected Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Cmedia USB audio codec CM6571 USB audio device is not recognized in startup. It is recognized after system loads and plugging the usb cableoff and on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: burak 1957 F pulseaudio /dev/snd/controlC2: burak 1957 F pulseaudio /dev/snd/controlC1: burak 1957 F pulseaudio /dev/snd/controlC0: burak 1957 F pulseaudio CurrentDesktop: Unity Date: Wed May 7 16:47:07 2014 InstallationDate: Installed on 2014-03-26 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to trusty on 2014-05-07 (0 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J51 v01.20 dmi.board.asset.tag: CZC209BJTS dmi.board.name: 1587h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC209BJTS dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ51v01.20:bd09/16/2011:svnHewlett-Packard:pnHPZ210Workstation:pvr:rvnHewlett-Packard:rn1587h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z210 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317105/+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 1317105] Re: USB sound card not detected
When i replug the usb cable of the CM6571 in OS desktop, it is sometimes recognized and the output of lsusb - -d 0d8c:0170 is attached. ** Attachment added: lsusb - -d 0d8c:0170 output https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317105/+attachment/4107893/+files/0170.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1317105 Title: USB sound card not detected Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Cmedia USB audio codec CM6571 USB audio device is not recognized in startup. It is recognized after system loads and plugging the usb cableoff and on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: burak 1957 F pulseaudio /dev/snd/controlC2: burak 1957 F pulseaudio /dev/snd/controlC1: burak 1957 F pulseaudio /dev/snd/controlC0: burak 1957 F pulseaudio CurrentDesktop: Unity Date: Wed May 7 16:47:07 2014 InstallationDate: Installed on 2014-03-26 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to trusty on 2014-05-07 (0 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J51 v01.20 dmi.board.asset.tag: CZC209BJTS dmi.board.name: 1587h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC209BJTS dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ51v01.20:bd09/16/2011:svnHewlett-Packard:pnHPZ210Workstation:pvr:rvnHewlett-Packard:rn1587h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z210 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317105/+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 1224212] Re: Audio on manta/Nexus 10 non-functional on Ubuntu touch.
** Tags added: manta -- 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/1224212 Title: Audio on manta/Nexus 10 non-functional on Ubuntu touch. Status in “alsa-lib” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: affects ubuntu/linux-manta affects ubuntu/pulseaudio I'm filing against the kernel for manta and pulse, because I am not entirely sure where the problem may lie, although based on the logs I've been able to gather, I suspect the kernel moreso than Pulse itself. I'm unable to hear audio either via the internal speakers or the headphone jack when either using paplay on the command-line, or using the music app. In addition, the music app doesn't update the playing position in the UI. I'm using flac files to test with, and I have verified that the UI works as expected on the nexus 7, where audio works without issue. Eventually, the music player appears to stop playing the file as if it were finished, even though no other UI updates of track position are shown. I have attached 2 logs, one with the sink set to the manta-i2s card, and the other with the output set to the manta-spdif card. Incidentaly the spdif device is being chosen as the default device after a fresh image flash, but thats not relevant here. These logs were obtained by following the procedure at https://wiki.ubuntu.com/PulseAudio/Log, with the addition of disabling the pulseaudio user session upstart job. Here are the details from system-image-cli -i re the build number and channel, although its worth noting that I have experienced this bug on standard daily images as well. phablet@ubuntu-phablet:~$ sudo system-image-cli -i current build number: 42 device name: manta channel: daily-proposed last update: 2013-09-11 23:21:24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1224212/+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 1317425] [NEW] compiz crash and window decorator disappear
Public bug reported: Many times everyday, compiz crashes and some applications become fullscreen (e.g.: leafpad, vmplayer, thunderbird especially). I cannot close those applications so I change desktop and kill the process of each. After, I go in .config and change config for thuderbird and remove for leafpad, because else, application start fullscreen the next time? Please find the debug.out information here: http://pastebin.com/L5bnVHzv http://pastebin.com/Q3Vri4ug http://pastebin.com/ppiJZdqq Regards, Marc-Andre! ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: vmplayer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1317425 Title: compiz crash and window decorator disappear Status in “compiz” package in Ubuntu: New Bug description: Many times everyday, compiz crashes and some applications become fullscreen (e.g.: leafpad, vmplayer, thunderbird especially). I cannot close those applications so I change desktop and kill the process of each. After, I go in .config and change config for thuderbird and remove for leafpad, because else, application start fullscreen the next time? Please find the debug.out information here: http://pastebin.com/L5bnVHzv http://pastebin.com/Q3Vri4ug http://pastebin.com/ppiJZdqq Regards, Marc-Andre! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1317425/+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 932177] Re: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11
It's 2014, this bug is already 2 years old, and hasn't been fixed yet, at least on Xubuntu 12.04. Fixing it seems trivial. Possible solutions: 1. If the package gnome-keyring is not needed on Xubuntu (or other affected Ubuntu flavors), it should be considered to be removed from it as a default package so that other applications don't try to connect to it. 2. If the package gnome-keyring is required, it should be fixed so that it runs properly on all the Ubuntu flavors that use it. The problem seems to be in /etc/xdg/autostart/gnome-keyring-pkcs11.desktop which is only enabled for Gnome and Unity. 2.1. Fix the line OnlyShowIn=GNOME;Unity; 2.1.1. by appending XFCE;KDE;LXDE; and any other DE that may need or use pkcs11. 2.1.2. by deleting or commenting out that line so that all DEs may use it (if anything, add a NotShowIn=... blacklist for DEs in which this may cause problems). 2.2. Make XFCE include an identical .desktop file with OnlyShowIn=XFCE; in it, so that the fix for XFCE is independent from other DEs. 2.3. Make XFCE load all Gnome services at startup by default (which may also include some unwanted stuff and thus may not be a good idea). 3. If the package gnome-keyring is required due to dependencies, but the service pkcs11 is not needed for it and other applications to run properly, the warning message it displays should be removed. 3.1. Making gnome-keyring not display that warning. 3.2. Making gnome-keyring inform applications that the service pkcs11 is unavailable. 3.3. Making all applications that use gnome-keyring check whether the service pkcs11 is available before requesting it (which would imply fixing them one by one, which may be a bad idea). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11 Status in GNOME keyring services: Fix Released Status in Xfce4 session manager: Unknown Status in Xubuntu: New Status in “gnome-keyring” package in Ubuntu: Invalid Status in “kde-workspace” package in Ubuntu: Fix Released Status in “xfce4-session” package in Ubuntu: Fix Released Status in “gnome-keyring” package in Debian: New Status in “gnome-keyring” package in Fedora: Unknown Status in “gnome-keyring” package in openSUSE: Fix Released Bug description: precise + fluxbox (without gnome-settings-daemon) Postler when sending a message writes: Failed to send a message WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-rof1VB/pkcs11: No such file or directory In gnome-system-monitor: /usr/bin/gnome-keyring-demon --start --foreground --components=secrets /usr/bin/gnome-keyring-demon --daemonize --login with manual start this: OK /usr/bin/gnome-keyring-daemon --start --components=pkcs11 Is it possible to add a string key '--components=pkcs11', so that the gnome-system-monitor was: /usr/bin/gnome-keyring-demon --start --foreground --components=secrets --components=pkcs11 thanks in advance... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Tue Feb 14 17:47:35 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to precise on 2012-02-10 (3 days ago) mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.secrets.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.ssh.desktop: 2012-02-14T14:17:23.636015 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/932177/+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 1317425] Re: compiz crash and window decorator disappear
** Description changed: - Many times everyday, compiz crashes and some application become + Many times everyday, compiz crashes and some applications become fullscreen (e.g. leafpad, vmplayer, thunderbird especially). I cannot close those applications so I change desktop and kill the process of each. After, I go in .config and change config for thuderbird and remove for leafpad, because else, application start fullscreen the next time? Please find the debug.out information here: http://pastebin.com/L5bnVHzv http://pastebin.com/Q3Vri4ug http://pastebin.com/ppiJZdqq Regards, Marc-Andre! ** Description changed: Many times everyday, compiz crashes and some applications become - fullscreen (e.g. leafpad, vmplayer, thunderbird especially). I cannot + fullscreen (e.g.: leafpad, vmplayer, thunderbird especially). I cannot close those applications so I change desktop and kill the process of each. After, I go in .config and change config for thuderbird and remove for leafpad, because else, application start fullscreen the next time? Please find the debug.out information here: http://pastebin.com/L5bnVHzv http://pastebin.com/Q3Vri4ug http://pastebin.com/ppiJZdqq Regards, Marc-Andre! ** Tags added: vmplayer ** Tags added: leafpad thunderbird -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1317425 Title: compiz crash and window decorator disappear Status in “compiz” package in Ubuntu: New Bug description: Many times everyday, compiz crashes and some applications become fullscreen (e.g.: leafpad, vmplayer, thunderbird especially). I cannot close those applications so I change desktop and kill the process of each. After, I go in .config and change config for thuderbird and remove for leafpad, because else, application start fullscreen the next time? Please find the debug.out information here: http://pastebin.com/L5bnVHzv http://pastebin.com/Q3Vri4ug http://pastebin.com/ppiJZdqq Regards, Marc-Andre! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1317425/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
both GPUs are enabled as I said. I think this is by design. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1315285 Title: [AMD Richland + Mars] Unable to switch graphics Status in “fglrx-installer” package in Ubuntu: New Bug description: Unable to switch in between APU and Discrete GPU. Step to reproduce: Oepn AMD Crystal Control Center, $ sudo amdcccle Expected: Switchable graphics settings menu will shown Actual result: Found no switchable graphics settings Currently found effected: APU: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] with GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1562 F pulseaudio /dev/snd/controlC0: ubuntu 1562 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri May 2 15:59:50 2014 HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 Notebook PC dmi.product.version: A201BC1203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1301708] Re: PCI/internal sound card not detected[ 20.936039] hda-intel 0000:04:01.0: no codecs initialized
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1301708 Title: PCI/internal sound card not detected[ 20.936039] hda-intel :04:01.0: no codecs initialized Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: onboard via VT8237A/VT8251 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matt 1822 F pulseaudio Date: Thu Apr 3 04:40:14 2014 InstallationDate: Installed on 2014-01-30 (62 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to saucy on 2014-03-28 (5 days ago) dmi.bios.date: 11/09/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7318 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/09/2006:svnMEDIONPC:pnMS-7318:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7318:rvr:cvn:ct3:cvr: dmi.product.name: MS-7318 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1301708/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
hello, my workaraound for lubuntu 14.04 32bit on Acer Aspire One d150, others have not worked: download: network-manager-gnome_0.9.4.1-0ubuntu2_i386.deb (network manager Lubuntu 12:04) from https://launchpad.net/ubuntu/precise/amd64/network-manager-gnome/0.9.4.1-0ubuntu2 for safety dowload also Lubuntu-desktop_0.55_i386.deb (desktop settings Lubuntu 14:04) from https://launchpad.net/ubuntu/trusty/i386/lubuntu-desktop/0.55 sudo stop network-manager sudo killall nm-applet sudo apt-get remove network-manager-gnome (also removes Lubuntu-desktop) from dowload directory: sudo dpkg -i network-manager-gnome_0.9.4.1-0ubuntu2_i386.deb sudo dpkg -i Lubuntu-desktop_0.55_i386.deb returns errors sudo start network-manager alt + f2 nm-applet configure: right click on the network icon in systray connect to WIFI, ignoring the certificate request sudo apt-get-f install (fixes the dependencies are not met due to the installation of the network manager 12:04 on 14:04) sudo apt-get update sudo apt-get upgrade everything should be ok even after rebooting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Triaged Status in Gentoo Linux: Fix Released Status in “network-manager” package in openSUSE: Confirmed Bug description: === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
PPA attente/java-non-latin-shortcuts fixed problem in LibreOffice 4.2 in Ubuntu 14.04 (Unity) for Georgian-KA language. Thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “kingsoft-office” package in Ubuntu: Confirmed Status in “openjdk-7” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+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 1317443] [NEW] mute mic button stopped working after nvidia driver installation
Public bug reported: I took a fresh install of Ubuntu 14.04 on Lenovo Thinkpad T420 with Nvidia NVS Mute microphone button works fine. Also muting in the sound settings switches the led indicator on the button on and off as expected. I installed nvidia driver 331 required by CUDA toolkit. Restart. System works fine except the microphone mute button. However, muting the mic in the sound settings dialog switches the led indicator correctly again. It looks like only the button is not sending any event to the sound settings. Switching to nouveau driver solves the problem but CUDA will not work. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1317443 Title: mute mic button stopped working after nvidia driver installation Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: I took a fresh install of Ubuntu 14.04 on Lenovo Thinkpad T420 with Nvidia NVS Mute microphone button works fine. Also muting in the sound settings switches the led indicator on the button on and off as expected. I installed nvidia driver 331 required by CUDA toolkit. Restart. System works fine except the microphone mute button. However, muting the mic in the sound settings dialog switches the led indicator correctly again. It looks like only the button is not sending any event to the sound settings. Switching to nouveau driver solves the problem but CUDA will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1317443/+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 405294] Re: a2dp skips terribly
Same issue here. Weird thing is, it worked flawlessly the first day, but it's been skipping frequently since the second one. Clevo W740SU (rebranded as Schenker S413) notebook with Intel 7260 WiFi/Bluetooth controller Sony SRS-BTX300 Bluetooth loudspeakers Ubuntu 14.04 64 bit Linux kerner v. 3.13.0-24-generic #47-Ubuntu SMP Pulseaudio v. 1:4.0-0ubuntu11 libbluetooth3 v. 4.101-0ubuntu13 Music played by Quod Libet v. 3.0.2-3, configured with alsasink device=pulse Syslog messages: May 8 11:25:42 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 18573 us (= 3276 bytes) in audio stream May 8 11:29:38 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 74848 us (= 13200 bytes) in audio stream May 8 11:30:04 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 72893 us (= 12856 bytes) in audio stream May 8 11:30:20 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 15928 us (= 2808 bytes) in audio stream May 8 11:31:33 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 35423 us (= 6248 bytes) in audio stream May 8 11:32:06 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 207527 us (= 36604 bytes) in audio stream May 8 11:32:16 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 349828 us (= 61708 bytes) in audio stream May 8 11:34:16 twobytwo pulseaudio[2411]: [bluetooth] module-bluetooth-device.c: Skipping 134223 us (= 23676 bytes) in audio stream -- 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/405294 Title: a2dp skips terribly Status in PulseAudio sound server: New Status in “bluez” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 964270] Re: Ubuntu forgets keyboard shortcuts after a restart
I am loosing keyboard shortcuts almost every time after restart. But not all of them. Launchers , Sound and Media sections seems ok, Navigation isn't. (Switch to workspace X for example). Ubuntu 14.04 Very annoying bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/964270 Title: Ubuntu forgets keyboard shortcuts after a restart Status in “compiz” package in Ubuntu: Confirmed Bug description: NOTE: This bug is for Ubuntu 12.04 (precise) only. If you experience something similar on 12.10 (quantal) or later then please refer to bug 1063617 instead. The two releases use completely different settings libraries so should be treated as separate bugs. Note also that if you just have trouble with screen edges, that is bug 858845. ORIGINAL DESCRIPTION: I use Dell XPS 1640. I'm using the latest ubuntu 12 and updated everything as of today. I assign some shortcuts for music to ubuntu keyboard shortcuts such as when i press ALT + X the music plays/pauses. However, after I restart the system, ubuntu forgets them and I have to reconfigure it everytime. I am new to Ubuntu but willing to help on debugging if it is simple and not technical. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Sun Mar 25 09:15:46 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/964270/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
Sorry I posted an incorrect link this is, my workaraound for lubuntu 14.04 32bit on Acer Aspire One d150, others have not worked: download: network-manager-gnome_0.9.4.1-0ubuntu2_i386.deb (network manager Lubuntu 12:04) from https://launchpad.net/ubuntu/precise/i386/network-manager-gnome/0.9.4.1-0ubuntu2 for safety dowload also Lubuntu-desktop_0.55_i386.deb (desktop settings Lubuntu 14:04) from https://launchpad.net/ubuntu/trusty/i386/lubuntu-desktop/0.55 sudo stop network-manager sudo killall nm-applet sudo apt-get remove network-manager-gnome (also removes Lubuntu-desktop) from dowload directory: sudo dpkg -i network-manager-gnome_0.9.4.1-0ubuntu2_i386.deb sudo dpkg -i Lubuntu-desktop_0.55_i386.deb returns errors sudo start network-manager alt + f2 nm-applet configure: right click on the network icon in systray connect to WIFI, ignoring the certificate request sudo apt-get-f install (fixes the dependencies are not met due to the installation of the network manager 12:04 on 14:04) sudo apt-get update sudo apt-get upgrade everything should be ok even after rebooting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Triaged Status in Gentoo Linux: Fix Released Status in “network-manager” package in openSUSE: Confirmed Bug description: === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1301708] Re: PCI/internal sound card not detected[ 20.936039] hda-intel 0000:04:01.0: no codecs initialized
you should file an upstream bug report https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers ** Changed in: alsa-driver (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1301708 Title: PCI/internal sound card not detected[ 20.936039] hda-intel :04:01.0: no codecs initialized Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: onboard via VT8237A/VT8251 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matt 1822 F pulseaudio Date: Thu Apr 3 04:40:14 2014 InstallationDate: Installed on 2014-01-30 (62 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to saucy on 2014-03-28 (5 days ago) dmi.bios.date: 11/09/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7318 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/09/2006:svnMEDIONPC:pnMS-7318:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7318:rvr:cvn:ct3:cvr: dmi.product.name: MS-7318 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1301708/+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 1317454] [NEW] Creative D1: maximum volume is too low
Public bug reported: The maximum volume is significantly lower on 14.04 compare to 12.04 or windows. I can increase it over 100% but the sound gets saturated and distorted. This is evident with the external speakers (Creative BT-D1 speaker system) but I think the same is true also with internal devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: KDE Date: Thu May 8 11:25:45 2014 InstallationDate: Installed on 2014-05-06 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or overdriven sound Title: [U36SD, Realtek ALC269VB, Speaker, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 kernel-sound trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1317454 Title: Creative D1: maximum volume is too low Status in “alsa-driver” package in Ubuntu: New Bug description: The maximum volume is significantly lower on 14.04 compare to 12.04 or windows. I can increase it over 100% but the sound gets saturated and distorted. This is evident with the external speakers (Creative BT-D1 speaker system) but I think the same is true also with internal devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: KDE Date: Thu May 8 11:25:45 2014 InstallationDate: Installed on 2014-05-06 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or overdriven sound Title: [U36SD, Realtek ALC269VB, Speaker, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317454/+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 1317452] [NEW] Ubuntu Software Center install wrong version
Public bug reported: Hi there, I'm under Ubuntu 14.04 LTS. I'm trying to install the package Ryzom from Ubuntu Software Center under Trusty, but instead of downloading the Trusty version (2.1.0.4658-0ubuntu2), it only downloads the Natty one (which is very old). I checked in my /etc/apt/sources.list.d/private-ppa.launchpad .net_commercial-ppa-uploaders_ryzom_ubuntu.list, it specifies natty instead of trusty. To fix the problem, I have to manually edit this file and replace natty by trusty and after refreshing packages list, it detects the new version and install it. I have no idea why it happens so I suspect it's a bug. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1317452 Title: Ubuntu Software Center install wrong version Status in “software-center” package in Ubuntu: New Bug description: Hi there, I'm under Ubuntu 14.04 LTS. I'm trying to install the package Ryzom from Ubuntu Software Center under Trusty, but instead of downloading the Trusty version (2.1.0.4658-0ubuntu2), it only downloads the Natty one (which is very old). I checked in my /etc/apt/sources.list.d/private-ppa.launchpad .net_commercial-ppa-uploaders_ryzom_ubuntu.list, it specifies natty instead of trusty. To fix the problem, I have to manually edit this file and replace natty by trusty and after refreshing packages list, it detects the new version and install it. I have no idea why it happens so I suspect it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1317452/+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
Re: [Desktop-packages] [Bug 1301708] Re: PCI/internal sound card not detected[ 20.936039] hda-intel 0000:04:01.0: no codecs initialized
Raymond, I'm sorry but i can't upload a bug or filereport because I experimented a litte to much to get this done. My system crashed and I've put an older version of Ubuntu back. Matt 2014-05-08 11:39 GMT+02:00 Raymond 1301...@bugs.launchpad.net: you should file an upstream bug report https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers ** Changed in: alsa-driver (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1301708 Title: PCI/internal sound card not detected[ 20.936039] hda-intel :04:01.0: no codecs initialized Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: onboard via VT8237A/VT8251 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matt 1822 F pulseaudio Date: Thu Apr 3 04:40:14 2014 InstallationDate: Installed on 2014-01-30 (62 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to saucy on 2014-03-28 (5 days ago) dmi.bios.date: 11/09/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7318 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/09/2006:svnMEDIONPC:pnMS-7318:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7318:rvr:cvn:ct3:cvr: dmi.product.name: MS-7318 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1301708/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1301708 Title: PCI/internal sound card not detected[ 20.936039] hda-intel :04:01.0: no codecs initialized Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: onboard via VT8237A/VT8251 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matt 1822 F pulseaudio Date: Thu Apr 3 04:40:14 2014 InstallationDate: Installed on 2014-01-30 (62 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to saucy on 2014-03-28 (5 days ago) dmi.bios.date: 11/09/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7318 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/09/2006:svnMEDIONPC:pnMS-7318:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7318:rvr:cvn:ct3:cvr: dmi.product.name: MS-7318 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1301708/+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 1317456] [NEW] ignores Play a sound config in preferences
Public bug reported:
Thunderbird on Ubuntu, since 13.10 or earlier, ignores the Play a
sound options in Preferences - General.
I have had to resort to overwriting the file
/usr/share/sounds/ubuntu/stereo/dialog-question.ogg with a silent ogg
file in order to silence it. (I need system sounds turned on generally
so I can hear incoming skype calls ringing and a few other important
things.)
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: thunderbird 1:24.5.0+build1-0ubuntu0.13.10.1
ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6
Uname: Linux 3.11.0-20-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adam 2797 F pulseaudio
/dev/snd/pcmC0D0p: adam 2797 F...m pulseaudio
BuildID: 20140428201931
Channel: Unavailable
Date: Thu May 8 10:54:26 2014
ExecutablePath: /usr/lib/thunderbird/thunderbird
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationDate: Installed on 2011-09-16 (964 days ago)
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
IpRoute:
default via 192.168.123.254 dev wlan0 proto static
192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.106
metric 9
MarkForUpload: True
PrefSources:
prefs.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
Profiles: Profile0 (Default) - LastVersion=24.5.0/20140428201931 (In use)
RelatedPackageVersions:
gnome-shell 3.8.4-0ubuntu5
gcu-plugin0.14.2-2ubuntu1
totem-mozilla 3.8.2-0ubuntu1
rhythmbox-mozilla 2.99.1-0ubuntu1
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: Upgraded to saucy on 2014-01-30 (97 days ago)
dmi.bios.date: 02/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U36JC.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U36JC
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrU36JC.206:bd02/25/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U36JC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug saucy
** Attachment removed: WifiSyslog.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107989/+files/WifiSyslog.txt
** Attachment removed: IpAddr.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107977/+files/IpAddr.txt
** Attachment removed: ProcEnviron.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107983/+files/ProcEnviron.txt
** Attachment removed: RfKill.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107987/+files/RfKill.txt
** Attachment removed: ProcMaps.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107984/+files/ProcMaps.txt
** Attachment removed: CRDA.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107973/+files/CRDA.txt
** Attachment removed: PciNetwork.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107980/+files/PciNetwork.txt
** Attachment removed: CurrentDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107974/+files/CurrentDmesg.txt
** Attachment removed: IwConfig.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107978/+files/IwConfig.txt
** Attachment removed: BootDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107972/+files/BootDmesg.txt
** Attachment removed: Lspci.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107979/+files/Lspci.txt
** Attachment removed: ProcStatus.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107985/+files/ProcStatus.txt
** Attachment removed: Plugins.txt
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1317456/+attachment/4107981/+files/Plugins.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird
[Desktop-packages] [Bug 1267785] Re: Software Center shows several blank debconf window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-center (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1267785 Title: Software Center shows several blank debconf window Status in Ubuntu Software Center: New Status in “software-center” package in Ubuntu: Confirmed Bug description: Software Center shows several blank debconf window during any installation. I don't know if it is a duplicate of Bug #912708 , because debconf window does not freeze, take a look at the picture. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-center 13.10-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 Date: Fri Jan 10 12:18:00 2014 InstallationDate: Installed on 2014-01-09 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1267785/+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 1305327] Re: Always in visible workspace does not work
** Changed in: unity Status: New = Confirmed ** Changed in: compiz Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1305327 Title: Always in visible workspace does not work Status in Compiz: Confirmed Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Confirmed Bug description: I can enable this option, but doesn't do anything, stays in single workspace. If you go to compiz, general options, and look at desktop size, it doesn't show data for vertical virtual size and number of desktops. Can set them with the unity tweak tool, but does not show up in compiz. Setting these options in compiz won't make them stick. So possibly related: i.e. workspaces don't work, therefore this option doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 337.12 Fri Apr 4 14:51:15 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 10 08:50:44 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-19-generic, x86_64: installed bbswitch, 0.7, 3.13.0-22-generic, x86_64: installed bbswitch, 0.7, 3.13.0-23-generic, x86_64: installed nvidia-337, 337.12, 3.13.0-23-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2119] InstallationDate: Installed on 2014-04-01 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) MachineType: LENOVO 2757CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic root=UUID=52ddc899-ca26-4fe9-b2ba-e7562258b42c ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZET71WW (1.54 ) dmi.board.name: 2757CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7ZET71WW(1.54):bd11/27/2008:svnLENOVO:pn2757CTO:pvrThinkPadW700:rvnLENOVO:rn2757CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2757CTO dmi.product.version: ThinkPad W700 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140408-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140331.ec4b8d16-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140331.ec4b8d16-0ubuntu0ricotz version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.99+git20140317.bdc41204-0ubuntu0sarvatt version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911+git20140331.5c0623b5-0ubuntu0ricotz version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt xserver.bootTime: Thu Apr 10 08:49:38 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory Tablet ISD-V4 stylus: Invalid type 'cursor' for this device. Tablet ISD-V4 stylus: Invalid type 'touch' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305327/+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 1316913] Re: wrong keybord layout at system start
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1316913 Title: wrong keybord layout at system start Status in “lightdm” package in Ubuntu: Confirmed Bug description: my system is set to german by default (De). When starting thunderbird and writing a new mail my keyboard is in qwerty mode. i must click on the De icon in the task bar to set it to qwertz mode. When updates need to be veriyfied with password i get wrong password - clicking the de icon in task bar sets it to german. thanks! ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1316913/+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 1316913] Re: wrong keybord layout at system start
Same problem here on one machine of three. Added layouts : French and French variante. System starts with qwerty. I removed the english layout installed by default in addiction to the one (fr) selected during install, but it doesn't solve the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1316913 Title: wrong keybord layout at system start Status in “lightdm” package in Ubuntu: Confirmed Bug description: my system is set to german by default (De). When starting thunderbird and writing a new mail my keyboard is in qwerty mode. i must click on the De icon in the task bar to set it to qwertz mode. When updates need to be veriyfied with password i get wrong password - clicking the de icon in task bar sets it to german. thanks! ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1316913/+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 1267437] Re: nvidia-331-updates calls DEVICE_ACPI_HANDLE() which got removed in linux-3.13
Its not fixed in Lucid! There we also get the kernel images for 3.13 with linux-generic-lts-trusty. So it need to be fixed there too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1267437 Title: nvidia-331-updates calls DEVICE_ACPI_HANDLE() which got removed in linux-3.13 Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Bug description: Since kernel 3a83f992490f8235661b768e53bd5f14915420ac (14/11/2013), DEVICE_ACPI_HANDLE() got removed in favor of ACPI_HANDLE(). With certain hardware configurations, this results in X failing to detect laptop monitor. Using trusty amd64 with nvidia-331-updates_331.20-0ubuntu9. linux-image-3.12.0-7-generic: [33.986] (--) NVIDIA(0): Valid display device(s) on GeForce 310M at PCI:1:0:0 [33.987] (--) NVIDIA(0): CRT-0 [33.987] (--) NVIDIA(0): Sony Nvidia Defaul (DFP-0) (boot, connected) [33.987] (--) NVIDIA(0): DFP-1 [33.987] (--) NVIDIA(0): DFP-2 linux-image-3.13.0-1-generic: [25.755] (--) NVIDIA(0): Valid display device(s) on GeForce 310M at PCI:1:0:0 [25.755] (--) NVIDIA(0): CRT-0 [25.755] (--) NVIDIA(0): DFP-0 (boot) [25.755] (--) NVIDIA(0): DFP-1 [25.755] (--) NVIDIA(0): DFP-2 [25.755] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock [25.755] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS [25.755] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock [25.755] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS [25.755] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock [25.755] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS [25.755] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock [25.755] (EE) NVIDIA(0): Failed to assign any connected display devices to X screen 0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-1-generic 3.13.0-1.16 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shiba 2314 F pulseaudio /dev/snd/controlC0: shiba 2314 F pulseaudio Date: Thu Jan 9 12:13:21 2014 HibernationDevice: RESUME=UUID=139076d6-04be-4ca0-b2fa-e57b8bb17739 InstallationDate: Installed on 2014-01-03 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140103) MachineType: Sony Corporation VPCS11E7E ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=c00738bd-0907-4a6b-b361-b8878455 ro quiet splash video=uvesafb:mode_option=1360x768-24,mtrr=3,scroll=ywrap RelatedPackageVersions: linux-restricted-modules-3.13.0-1-generic N/A linux-backports-modules-3.13.0-1-generic N/A linux-firmware1.119 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: INSYDE dmi.bios.version: R0310Q3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0310Q3:bd09/30/2010:svnSonyCorporation:pnVPCS11E7E:pvrC103ZTX7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCS11E7E dmi.product.version: C103ZTX7 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1267437/+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 1267437] Re: nvidia-331-updates calls DEVICE_ACPI_HANDLE() which got removed in linux-3.13
Sorry - it need also to be fixed in Precise (not Lucid)! There we also get the kernel images for 3.13 with linux-generic-lts-trusty. So it need to be fixed there too. ** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1267437 Title: nvidia-331-updates calls DEVICE_ACPI_HANDLE() which got removed in linux-3.13 Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Bug description: Since kernel 3a83f992490f8235661b768e53bd5f14915420ac (14/11/2013), DEVICE_ACPI_HANDLE() got removed in favor of ACPI_HANDLE(). With certain hardware configurations, this results in X failing to detect laptop monitor. Using trusty amd64 with nvidia-331-updates_331.20-0ubuntu9. linux-image-3.12.0-7-generic: [33.986] (--) NVIDIA(0): Valid display device(s) on GeForce 310M at PCI:1:0:0 [33.987] (--) NVIDIA(0): CRT-0 [33.987] (--) NVIDIA(0): Sony Nvidia Defaul (DFP-0) (boot, connected) [33.987] (--) NVIDIA(0): DFP-1 [33.987] (--) NVIDIA(0): DFP-2 linux-image-3.13.0-1-generic: [25.755] (--) NVIDIA(0): Valid display device(s) on GeForce 310M at PCI:1:0:0 [25.755] (--) NVIDIA(0): CRT-0 [25.755] (--) NVIDIA(0): DFP-0 (boot) [25.755] (--) NVIDIA(0): DFP-1 [25.755] (--) NVIDIA(0): DFP-2 [25.755] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock [25.755] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS [25.755] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock [25.755] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS [25.755] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock [25.755] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS [25.755] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock [25.755] (EE) NVIDIA(0): Failed to assign any connected display devices to X screen 0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-1-generic 3.13.0-1.16 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shiba 2314 F pulseaudio /dev/snd/controlC0: shiba 2314 F pulseaudio Date: Thu Jan 9 12:13:21 2014 HibernationDevice: RESUME=UUID=139076d6-04be-4ca0-b2fa-e57b8bb17739 InstallationDate: Installed on 2014-01-03 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140103) MachineType: Sony Corporation VPCS11E7E ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=c00738bd-0907-4a6b-b361-b8878455 ro quiet splash video=uvesafb:mode_option=1360x768-24,mtrr=3,scroll=ywrap RelatedPackageVersions: linux-restricted-modules-3.13.0-1-generic N/A linux-backports-modules-3.13.0-1-generic N/A linux-firmware1.119 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: INSYDE dmi.bios.version: R0310Q3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0310Q3:bd09/30/2010:svnSonyCorporation:pnVPCS11E7E:pvrC103ZTX7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCS11E7E dmi.product.version: C103ZTX7 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1267437/+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 1317473] [NEW] wrong results - negative numbers raised to power of two
Public bug reported: type into the calculator -1^2 Expected result: 1 Received result: -1 The bug applies to all negative numbers raised to any even number. The bug is also present in Ubuntu 14.04 Workaround: 1.) put negativ number in parantheses (-1)^2 = 1 2.) insert the power argument with the ctrl key pressed like: -3ctrl8 3.) in scientific or programming mode use the (n↑) button. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gcalctool 6.4.1.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-20.35~precise1-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Thu May 8 12:02:45 2014 InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gcalctool UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcalctool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/1317473 Title: wrong results - negative numbers raised to power of two Status in “gcalctool” package in Ubuntu: New Bug description: type into the calculator -1^2 Expected result: 1 Received result: -1 The bug applies to all negative numbers raised to any even number. The bug is also present in Ubuntu 14.04 Workaround: 1.) put negativ number in parantheses (-1)^2 = 1 2.) insert the power argument with the ctrl key pressed like: -3ctrl8 3.) in scientific or programming mode use the (n↑) button. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gcalctool 6.4.1.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-20.35~precise1-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Thu May 8 12:02:45 2014 InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gcalctool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/1317473/+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 1304866] Re: Notice of expiring password in greeter not really visible
This bug was fixed in the package unity-greeter - 14.04.10-0ubuntu1 --- unity-greeter (14.04.10-0ubuntu1) trusty; urgency=medium * New upstream release: - Require user to acknowledge messages received after authentication is complete, for example if their password is about to expire. (LP: #1304866) -- Robert Ancell robert.anc...@canonical.com Wed, 30 Apr 2014 15:33:19 +1200 ** Changed in: unity-greeter (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1304866 Title: Notice of expiring password in greeter not really visible Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Committed Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Messages that are shown after authentication is complete are not seen as the greeter immediately closes and the session starts. Examples of messages are warnings that the user password will expire soon. [Test Case] 1. Make new user 2. Make user account set to expiring with chage tool. (pick yesterday for the date here) $ sudo chage -d 2014/04/29 -M 2 username 3. Log into this user from the greeter Expected result: User is informed that their password is about to expire. Observed result: Message displayed briefly before greeter closes and session starts. (On fast systems may not be visible at all) [Regression Potential] Since this is a behaviour change in how the UI presents authentication prompts there is a risk that other authentication cases might be adversely affected. Tested manually using the unity-greeter test mode which simulates many of these cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1304866/+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 1304866] Update Released
The verification of the Stable Release Update for unity-greeter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1304866 Title: Notice of expiring password in greeter not really visible Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Committed Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Messages that are shown after authentication is complete are not seen as the greeter immediately closes and the session starts. Examples of messages are warnings that the user password will expire soon. [Test Case] 1. Make new user 2. Make user account set to expiring with chage tool. (pick yesterday for the date here) $ sudo chage -d 2014/04/29 -M 2 username 3. Log into this user from the greeter Expected result: User is informed that their password is about to expire. Observed result: Message displayed briefly before greeter closes and session starts. (On fast systems may not be visible at all) [Regression Potential] Since this is a behaviour change in how the UI presents authentication prompts there is a risk that other authentication cases might be adversely affected. Tested manually using the unity-greeter test mode which simulates many of these cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1304866/+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
Re: [Desktop-packages] [Bug 1222431] Re: disk usage analyzer (baobab) increases Xorg CPU usage during scan
The new version fixes it. Interestingly Baobab 3.4.1 on Debian 7 behaves as expected too. Seems I just discovered some obscure hickup in Ubuntu 12.04 with Baobab 3.6.0. Please close the bug. Thank you. On 04/16/14 09:26, Walter Garcia-Fontes wrote: m-manico, I tested this in 14.04, which brings baobab 3.8.2 and couldn't reproduce what you report. Can you please try this in 14.04, either by trying a life USB or CD or if you decide to upgrade? ** Changed in: baobab (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1222431 Title: disk usage analyzer (baobab) increases Xorg CPU usage during scan Status in “baobab” package in Ubuntu: Incomplete Bug description: Version of Ubuntu: 12.10 Version of Baobab: 3.6.0 Expected behaviour: Baobab scans my hard disc. The scan increases disk I/O but does not influence Xorg's CPU usage. Actual behaviour: When scanning disk, Xorg's CPU usage goes up to about 50% while baobab uses ~25% of the CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1222431/+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 1247366] Re: Evolution is missing bogofilter integration
Missing here as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration Status in “evolution” package in Ubuntu: Confirmed Bug description: On fresh install and after upgrade to Ubuntu 13.10, Evolution is missing bogofilter integration. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution 3.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 2 05:15:42 2013 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2013-10-27 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+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 1317454] Re: Creative D1: maximum volume is too low
amp out values seem not at maximum 0x57 try hda-analyzer to increase you may need to file an upstream bug report by provide alsa-info output if it work when using 12.04 live cd Node 0x02 [Audio Output] wcaps 0x1d: Stereo Amp-Out Control: name=Headphone Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name=ALC269VB Analog, type=Audio, device=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x4b 0x4b] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Node 0x03 [Audio Output] wcaps 0x1d: Stereo Amp-Out Control: name=Speaker Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x4b 0x4b] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1317454 Title: Creative D1: maximum volume is too low Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: The maximum volume is significantly lower on 14.04 compare to 12.04 or windows. I can increase it over 100% but the sound gets saturated and distorted. This is evident with the external speakers (Creative BT-D1 speaker system) but I think the same is true also with internal devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: KDE Date: Thu May 8 11:25:45 2014 InstallationDate: Installed on 2014-05-06 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or overdriven sound Title: [U36SD, Realtek ALC269VB, Speaker, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1317454/+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 70643] Re: Evolution doesn't show Read Receipt requests when asked for by sender
** Changed in: evolution Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/70643 Title: Evolution doesn't show Read Receipt requests when asked for by sender Status in The Evolution Mail Calendaring Tool: Fix Released Status in “evolution” package in Ubuntu: Invalid Bug description: Binary package hint: evolution Steps: 1. start evolution 2. compose a new message 3. from the menu select Insert-'Request Read Receipt' 4. send the e-mail [to yourself] ... 5. open the received mail ... 6. check mail again and you will see that read receipt is missing Expected results: When you open a mail that has been sent with 'read receipt', the mail-client should send back a notification to the sender (by e-mail, of course). Btw, that feature is working at least in the following clients: MSOutlook, mozilla thunderbird, kmail. ( this is my first bug :) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/70643/+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 1286394] Re: Cheese freezes in Xubuntu 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cheese (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1286394 Title: Cheese freezes in Xubuntu 14.04 Status in “cheese” package in Ubuntu: Confirmed Bug description: Fresh install of Xubuntu 14.04 All updates Installed Cheese Took picture, cannot take 2nd pic as program freezes and cannot close, have to right click on bar on top. rebooted, still does it. loaded it in terminal ** (cheese:2684): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-bjDZa9mJGg: Connection refused haven't a clue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1286394/+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 1312457] Re: Python bindings broken due to changes in GObject overrides API
** Changed in: gexiv2 Status: Unknown = Fix Released ** Changed in: gexiv2 Importance: Unknown = Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gexiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1312457 Title: Python bindings broken due to changes in GObject overrides API Status in gexiv2: Fix Released Status in “gexiv2” package in Ubuntu: Fix Released Status in “gexiv2” source package in Trusty: Fix Released Bug description: [Impact] * GExiv2 python bindings are not functional, this means that python applications trying to use GExiv2 do not work. * This worked in Saucy but regressed in Trusty. * The upload fixes the bug by updating GExiv2.py to the new GObject override API. [Test Case] 1. Get an application that uses the python bindings to GExiv2, such as GottenGeography 2. Try to open a photo. Expected behavior: The photo opens. Actual behavior: the program crashes. [Regression Potential] Very little, the changes are confined to GExiv2.py, which is already completely broken. This change can't possibly break it any worse than it already is. [Other Info] I've reported the bug upstream with patch here: https://bugzilla.gnome.org/show_bug.cgi?id=728909 To manage notifications about this bug go to: https://bugs.launchpad.net/gexiv2/+bug/1312457/+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 1303462] Re: [Regression] Window titlebars placed behind panel
** Changed in: unity Milestone: 7.2.1 = None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1303462 Title: [Regression] Window titlebars placed behind panel Status in Compiz: In Progress Status in Unity: Invalid Status in “compiz” package in Ubuntu: In Progress Bug description: Windows with a height of (Display Height - Panel Height) get placed at y=0 (behind the top panel) which means window titlebars are not reachable without alt-moving the window. I assume this happens with windows that want to resize themselves if their height exceeds the display resolution. Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop application I'm working on. TEMPORARY WORKAROUND: Use the Cntrl+SuperKey+Right or Left Arrow Key This will resize your currently focused window to occupy the Right (Left) half of the screen. The Title Bar should now be visible, so you need to drag it and resize it at your prefered position. This will save the new position in place of the previously hidden state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 6 21:45:41 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor
Same behavior here - also using 3rd monitor via kensington display link. Mouse flickering like mentioned above - some information about my config: Ubuntu 14.04 Monitor links: first DVI 1680x1050 second HDMI 1680x1050 third Kensington Displaylink usb 1680x1050 lspci 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 6: Dev 5, If 0, Class=Vendor Specific Class, Driver=udl, 480M dmesg: [2.908713] usb 1-1.6: New USB device found, idVendor=17e9, idProduct=0036 [2.908718] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [2.908721] usb 1-1.6: Product: Kensington M01063 [2.908724] usb 1-1.6: Manufacturer: DisplayLink [2.908727] usb 1-1.6: SerialNumber: 2012C1001134 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in “xorg” package in Ubuntu: Confirmed Bug description: My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I Restore previous settings, after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 683693] Re: tomboy crashed while indenting latex equation
It happened to me when I tried to edit some text within the Latex tag. The note crashed and closed. Opening the note again did not help as it kept crashing on open. However, I disabled the plugin, corrected the latex code and re-enabled the plugin and everything worked like a charm. I'm really enjoying this add-in to tomboy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tomboy in Ubuntu. https://bugs.launchpad.net/bugs/683693 Title: tomboy crashed while indenting latex equation Status in “tomboy” package in Ubuntu: Confirmed Bug description: Binary package hint: tomboy tomboy crashed and won't launch again, when I was trying to indent a rendered latex equation (tomboy-latex ver. 0.6). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: tomboy 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-23.40-generic-pae 2.6.35.7 Uname: Linux 2.6.35-23-generic-pae i686 Architecture: i386 Date: Wed Dec 1 16:21:34 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: tomboy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/683693/+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 1222431] Re: disk usage analyzer (baobab) increases Xorg CPU usage during scan
Thanks for your response. ** Changed in: baobab (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1222431 Title: disk usage analyzer (baobab) increases Xorg CPU usage during scan Status in “baobab” package in Ubuntu: Invalid Bug description: Version of Ubuntu: 12.10 Version of Baobab: 3.6.0 Expected behaviour: Baobab scans my hard disc. The scan increases disk I/O but does not influence Xorg's CPU usage. Actual behaviour: When scanning disk, Xorg's CPU usage goes up to about 50% while baobab uses ~25% of the CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1222431/+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 1317505] [NEW] EmbeddedBitmap for ttf-ms-corefonts
Public bug reported: When opening a mail in gmail that was send by someone with outlook , the font (Verdana) looks really ugly and broken. This is because for small font sizes the embedded bitmap is used. The default behaviour should be to not use the embeddedBitmap for Verdana (and other ttf-ms-corefonts), since that makes them very ugly. Workaround: Add following lines to ~/.config/fontconfig/fonts.conf match target=font edit name=embeddedbitmap mode=assign boolfalse/bool /edit /match ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 8 14:11:32 2014 InstallationDate: Installed on 2014-04-17 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1317505 Title: EmbeddedBitmap for ttf-ms-corefonts Status in “fontconfig” package in Ubuntu: New Bug description: When opening a mail in gmail that was send by someone with outlook , the font (Verdana) looks really ugly and broken. This is because for small font sizes the embedded bitmap is used. The default behaviour should be to not use the embeddedBitmap for Verdana (and other ttf-ms- corefonts), since that makes them very ugly. Workaround: Add following lines to ~/.config/fontconfig/fonts.conf match target=font edit name=embeddedbitmap mode=assign boolfalse/bool /edit /match ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 8 14:11:32 2014 InstallationDate: Installed on 2014-04-17 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317505/+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 1296180] Re: Disable touchpad while typing does not work
Temporary solution: http://askubuntu.com/questions/299868/disable- touchpad-while-typing-does-not-work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1296180 Title: Disable touchpad while typing does not work Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Bug description: I've seen some similar bugreports, but none exactly like this. In my Ubuntu Gnome 14.04 Disable touchpad while typing does not work at all. I can both move the cursor and click with it while typing. But the manual way of turning off the touchpad with the Fn key works fine. Let me know if I can do anything to help the process of tracking down and fixing this bug in any way (except coding, which I can't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1296180/+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 1308515] Re: black screen when enabling rotation on a gpu screen
** Tags added: blocks-hwcert-enablement ** Changed in: hwe-next Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1308515 Title: black screen when enabling rotation on a gpu screen Status in HWE Next Project: Triaged Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server-lts-saucy” package in Ubuntu: Invalid Status in “xorg-server-lts-saucy” source package in Precise: In Progress Status in “xorg-server” source package in Saucy: Fix Committed Status in “xorg-server” source package in Trusty: Fix Released Bug description: Running with the proprietary nvidia drivers in an optimus config works, but enabling reflection or rotation on the intel screen causes a black screen to appear. [Impact] * Causes a black screen if rotation or reflection is enabled. [Test Case] * Run xrandr --output SOMEOUTPUT --rotation left - Expected: Screen should rotate, or the call should fail. - Bad behavior: Succeeds, but causes a black screen. [Regression Potential] * The affected codepaths have reflection and rotation disabled for gpu screens. Another fix could be fixing reflection/rotation, but that will be more involved and likely require driver fixes. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308515/+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 1317512] [NEW] Hardware mute is rekoved when logging in
Public bug reported: I'm using a Thinkpad X230 with Ubuntu 14.04. Sometimes I'm using it in an environment where I want to be certain, my laptop is silent (i.e. a library or a meeting). 1.) So I press the hardware mute button during the boot sequence. 2.) Upon pressing the hardware key a small LED assures me that the device is, in fact, muted. 3.) After logging in via gdm, when the gnome-shell session spawns, the light is turned off automatically and the system is unmuted. The behaviour in 3) is unexpected. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-09-09 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Package: gdm 3.12.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Tags: third-party-packages trusty gnome3-staging gnome3-ppa Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-23 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.init.d.gdm: 2014-03-23T18:28:16.950535 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected gnome3-ppa gnome3-staging third-party-packages trusty ** Tags added: apport-collected gnome3-ppa gnome3-staging third-party- packages trusty ** Description changed: I'm using a Thinkpad X230 with Ubuntu 14.04. Sometimes I'm using it in an environment where I want to be certain, my laptop is silent (i.e. a library or a meeting). 1.) So I press the hardware mute button during the boot sequence. 2.) Upon pressing the hardware key a small LED assures me that the device is, in fact, muted. 3.) After logging in via gdm, when the gnome-shell session spawns, the light is turned off automatically and the system is unmuted. The behaviour in 3) is unexpected. + --- + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 14.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2013-09-09 (240 days ago) + InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) + Package: gdm 3.12.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=de_DE.UTF-8 + SHELL=/bin/zsh + ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 + Tags: third-party-packages trusty gnome3-staging gnome3-ppa + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-03-23 (45 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.init.d.gdm: 2014-03-23T18:28:16.950535 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1317512 Title: Hardware mute is rekoved when logging in Status in “gdm” package in Ubuntu: New Bug description: I'm using a Thinkpad X230 with Ubuntu 14.04. Sometimes I'm using it in an environment where I want to be certain, my laptop is silent (i.e. a library or a meeting). 1.) So I press the hardware mute button during the boot sequence. 2.) Upon pressing the hardware key a small LED assures me that the device is, in fact, muted. 3.) After logging in via gdm, when the gnome-shell session spawns, the light is turned off automatically and the system is unmuted. The behaviour in 3) is unexpected. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-09-09 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Package: gdm 3.12.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Tags: third-party-packages trusty gnome3-staging gnome3-ppa Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-23 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.init.d.gdm: 2014-03-23T18:28:16.950535 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1317512/+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 1316667] Re: 0.1+14.10.20140428-0ubuntu1 does not cross-build on utopic
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/ofono-qt/utopic- proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1316667 Title: 0.1+14.10.20140428-0ubuntu1 does not cross-build on utopic Status in “ofono-qt” package in Ubuntu: In Progress Status in “signon” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: I imagine the underlying cause is not necessarily ubuntu-system- settings's alone (or at all), but it does not currently cross-build under utopic. See the attached sbuild log, but the interesting part is: The following packages have unmet dependencies: libaccountsservice-dev:armhf : Depends: gir1.2-accountsservice-1.0:armhf (= 0.6.35-0ubuntu7) Depends: libaccountsservice0:armhf (= 0.6.35-0ubuntu7) but it is not going to be installed Depends: libpolkit-gobject-1-dev:armhf but it is not going to be installed libnm-glib-dev:armhf : Depends: libnm-glib4:armhf (= 0.9.8.8-0ubuntu9) but it is not going to be installed Depends: gir1.2-networkmanager-1.0:armhf (= 0.9.8.8-0ubuntu9) but it is not going to be installed Depends: libnm-util-dev:armhf but it is not going to be installed libqmenumodel-dev:armhf : Depends: libqmenumodel0:armhf (= 0.2.7+14.04.20140305-0ubuntu2) but it is not going to be installed libubuntu-download-manager-client-dev:armhf : Depends: libudm-common-dev:armhf (= 0.3+14.10.20140430.1-0ubuntu1) but it is not going to be installed Depends: libubuntu-download-manager-common-dev:armhf (= 0.3+14.10.20140430.1-0ubuntu1) but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed libubuntuoneauth-2.0-dev:armhf : Depends: libsignon-qt5-dev:armhf but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed libunity-mir-dev:armhf : Depends: libunity-mir1:armhf (= 0.4+14.10.20140430.3-0ubuntu1) but it is not going to be installed Depends: libmirserver-dev:armhf (= 0.1.8) but it is not going to be installed Depends: libplatform-api1-dev:armhf but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed qt5-default:armhf : Depends: qtbase5-dev:armhf but it is not going to be installed qtbase5-private-dev:armhf : Depends: qtbase5-dev:armhf (= 5.2.1+dfsg-1ubuntu15) but it is not going to be installed qtdeclarative5-dev:armhf : Depends: libqt5quick5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed or libqt5quick5-gles:armhf but it is not installable Depends: libqt5quickparticles5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed or libqt5quickparticles5-gles:armhf but it is not installable Depends: libqt5quicktest5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.1+14.10.20140428-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 6 17:47:16 2014 SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1316667/+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 1317512] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1317512/+attachment/4108039/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1317512 Title: Hardware mute is rekoved when logging in Status in “gdm” package in Ubuntu: New Bug description: I'm using a Thinkpad X230 with Ubuntu 14.04. Sometimes I'm using it in an environment where I want to be certain, my laptop is silent (i.e. a library or a meeting). 1.) So I press the hardware mute button during the boot sequence. 2.) Upon pressing the hardware key a small LED assures me that the device is, in fact, muted. 3.) After logging in via gdm, when the gnome-shell session spawns, the light is turned off automatically and the system is unmuted. The behaviour in 3) is unexpected. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-09-09 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Package: gdm 3.12.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Tags: third-party-packages trusty gnome3-staging gnome3-ppa Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-23 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.init.d.gdm: 2014-03-23T18:28:16.950535 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1317512/+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 1317512] modified.conffile..etc.init.d.gdm.txt
apport information ** Attachment added: modified.conffile..etc.init.d.gdm.txt https://bugs.launchpad.net/bugs/1317512/+attachment/4108040/+files/modified.conffile..etc.init.d.gdm.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1317512 Title: Hardware mute is rekoved when logging in Status in “gdm” package in Ubuntu: New Bug description: I'm using a Thinkpad X230 with Ubuntu 14.04. Sometimes I'm using it in an environment where I want to be certain, my laptop is silent (i.e. a library or a meeting). 1.) So I press the hardware mute button during the boot sequence. 2.) Upon pressing the hardware key a small LED assures me that the device is, in fact, muted. 3.) After logging in via gdm, when the gnome-shell session spawns, the light is turned off automatically and the system is unmuted. The behaviour in 3) is unexpected. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-09-09 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Package: gdm 3.12.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Tags: third-party-packages trusty gnome3-staging gnome3-ppa Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-23 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.init.d.gdm: 2014-03-23T18:28:16.950535 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1317512/+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 1317512] CrashDB.txt
apport information ** Attachment added: CrashDB.txt https://bugs.launchpad.net/bugs/1317512/+attachment/4108038/+files/CrashDB.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1317512 Title: Hardware mute is rekoved when logging in Status in “gdm” package in Ubuntu: New Bug description: I'm using a Thinkpad X230 with Ubuntu 14.04. Sometimes I'm using it in an environment where I want to be certain, my laptop is silent (i.e. a library or a meeting). 1.) So I press the hardware mute button during the boot sequence. 2.) Upon pressing the hardware key a small LED assures me that the device is, in fact, muted. 3.) After logging in via gdm, when the gnome-shell session spawns, the light is turned off automatically and the system is unmuted. The behaviour in 3) is unexpected. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-09-09 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Package: gdm 3.12.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Tags: third-party-packages trusty gnome3-staging gnome3-ppa Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-23 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.init.d.gdm: 2014-03-23T18:28:16.950535 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1317512/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Hi Peter, you can try to remove by: sudo apt-get install ppa-purge sudo ppa-purge ppa:attente/java-non-latin-shortcuts and restarting the session. Sorry I should've been more specific: the PPA is meant for the GNOME Classic from the package gnome-shell- extensions, and not either of the GNOME Flashback sessions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Fedora: Unknown Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center
[Desktop-packages] [Bug 1317517] [NEW] Transparent area background filled with black in pdf
Public bug reported: The attached pdf when viewed in evince looks correct but when run through the print preview or printed, the partially transparent image with a white background has a black background instead. This is with 14.04 release and cairo 1.13.0-20140204-0ubuntu1. ** Affects: cairo (Ubuntu) Importance: Undecided Status: New ** Attachment added: Original pdf https://bugs.launchpad.net/bugs/1317517/+attachment/4108044/+files/test.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1317517 Title: Transparent area background filled with black in pdf Status in “cairo” package in Ubuntu: New Bug description: The attached pdf when viewed in evince looks correct but when run through the print preview or printed, the partially transparent image with a white background has a black background instead. This is with 14.04 release and cairo 1.13.0-20140204-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1317517/+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 1317517] Re: Transparent area background filled with black in pdf
** Attachment added: Print preview pdf https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1317517/+attachment/4108045/+files/previewVJK8EX.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1317517 Title: Transparent area background filled with black in pdf Status in “cairo” package in Ubuntu: New Bug description: The attached pdf when viewed in evince looks correct but when run through the print preview or printed, the partially transparent image with a white background has a black background instead. This is with 14.04 release and cairo 1.13.0-20140204-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1317517/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
gnome-keyring-daemon isn't really a problem because all official images shipping it have installer hooks to restore the flag. Setting the binary setuid would also be completely wrong as we never want this to run as root, we just want it to have extra ipc locking capabilities. My understanding is that those aren't even entirely required and that it has a fallback mode for systems where the capability isn't set. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Confirmed Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1315212] Re: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output
Here is the pulseverbose.log. I started pules and ran speaker-test -C 6 vlad: That is exactly what happens for me, too. ** Attachment added: pulseverbose.log https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1315212/+attachment/4108052/+files/pulseverbose.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1315212 Title: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: This is tested against a Creative Labs Sounblaster live! (sb0410) card and a SoundBlaster Audigy se (sb0570). Both of them behave strangely, output coming through some, but not all speakers, etc. This was working in 13.10 under the sb0410. the ca0106 driver is the same for both cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshp 30385 F pulseaudio /dev/snd/controlC0: joshp 30385 F pulseaudio CurrentDesktop: Unity Date: Thu May 1 21:37:12 2014 InstallationDate: Installed on 2014-04-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed Symptom_Card: Built-in Audio - Intel ICH6 Symptom_Type: None of the above Title: [CA0106 - CA0106, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0G8310 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2006:svnDellInc.:pnOptiPlexGX280:pvr:rvnDellInc.:rn0G8310:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex GX280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1315212/+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 1301708] Re: PCI/internal sound card not detected[ 20.936039] hda-intel 0000:04:01.0: no codecs initialized
Raymond, I have the same symptoms as Matt - I'm also using a Medion PC with MSI 7318 mboard, and have had this problem since I installed Ubuntu 13.xx last year. I have just upgraded to Ubuntu 14.04 but the problem has not changed. The VIA VT8237A/VT8251 chip is not recognised by Ubuntu, but still works fine with Windows Vista - dual boot on the same PC. Are you saying by upstream bug report that this bug should be addressed to the kernel team instead of the ALSA team, or just filed to kernel bug tracker instead of launchpad? Regards Mike Scott -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1301708 Title: PCI/internal sound card not detected[ 20.936039] hda-intel :04:01.0: no codecs initialized Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: onboard via VT8237A/VT8251 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matt 1822 F pulseaudio Date: Thu Apr 3 04:40:14 2014 InstallationDate: Installed on 2014-01-30 (62 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to saucy on 2014-03-28 (5 days ago) dmi.bios.date: 11/09/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7318 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/09/2006:svnMEDIONPC:pnMS-7318:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7318:rvr:cvn:ct3:cvr: dmi.product.name: MS-7318 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1301708/+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 1283826] Re: lightdm hangs after updates
This also happened to me on 3 fresh installs and upgrades from 13.10 combined, both on hardware and VMs. Exact behaviour. Works fine until apt-get upgrade is run for the first time. It disables auto-login if configured and then hangs as soon as the password is entered, staying on the lightdm screen, but blanking out all the password fields. The main menu is still accessible as I can access power functions, and changing VT also works find. All installs tested using Unity, not tested under Gnome or LXDE. On the hardware install, I was able to fix it by reinserting the DVD and choosing to reinstall the OS, however oddly when running in VirtualBox there was no option to reinstall, just to reformat and start from scratch. Also it does show 13.10 on the lightdm greeter rather than 14.04 until the issue is fixed. Once it's fixed, it shows 14.04. Very strange. WORKAROUND: I worked around this by using the following IMMEDIATELY after a clean install: sudo apt-get update sudo apt-get install ubuntu-desktop lightdm libgtk-pixbuf2.0-dev gdk-pixbuf-query-loaders | sudo tee /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache sudo apt-get upgrade Now reboot. This is tested working in the VMs and on hardware machines (not that there SHOULD be a difference) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1283826 Title: lightdm hangs after updates Status in GDM: The Gnome Display Manager: New Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: I've updated today my Trusy Thar installation. I can't login to Unity, with my account, or a guest account. Lightdm hangs after password input, or after I click on the Guest account. Also, I used to auto-login. Now it greets me with the screen where I must input my password. After inputing it, lightdm hangs and I can't login. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Sun Feb 23 23:16:24 2014 InstallationDate: Installed on 2014-01-25 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140115) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=cristi autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1283826/+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 1317528] [NEW] Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1
Public bug reported: The packages don't provide the virtual packages libopencl-1.1-1 and libopencl-1.2-1. This causes problems with the installation of the following packages: python-pyopencl python3-pyopencl wine1.6-i386 (see https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1313123) wine1.6-amd64 starpu-contrib-examples libstarpu-contrib ** Affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: packaging ** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Description changed: - The packages nvidia-libopencl1-304, nvidia-libopencl1-304-updates, - nvidia-libopencl1-331 and nvidia-libopencl1-331-updates don't provide - the virtual packages libopencl-1.1-1 and libopencl-1.2-1. + The packages don't provide the virtual packages libopencl-1.1-1 and + libopencl-1.2-1. This causes problems with the installation of the following packages: - python-pyopencl - python3-pyopencl - wine1.6-i386 (see https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1313123) - wine1.6-amd64 - starpu-contrib-examples - libstarpu-contrib + python-pyopencl + python3-pyopencl + wine1.6-i386 (see https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1313123) + wine1.6-amd64 + starpu-contrib-examples + libstarpu-contrib ** Summary changed: - Packages nvidia-libopencl-... don't provide libopencl-1.1-1 and libopencl-1.2-1 + Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1317528 Title: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1 Status in “nvidia-graphics-drivers-304” package in Ubuntu: New Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: New Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: The packages don't provide the virtual packages libopencl-1.1-1 and libopencl-1.2-1. This causes problems with the installation of the following packages: python-pyopencl python3-pyopencl wine1.6-i386 (see https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1313123) wine1.6-amd64 starpu-contrib-examples libstarpu-contrib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1317528/+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 1304514] Re: Pulseaudio microphone doesn't work after waking up from suspend
Oh, one more thing, it worked perfectly in Saucy, and broke when I upgraded to Trusty. -- 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/1304514 Title: Pulseaudio microphone doesn't work after waking up from suspend Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: When I wake up from suspend my microphones don't work. I need to type pulseaudio -k in terminal and restart apps (for example Skype or Audacity) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: yanpas19734 F pulseaudio /dev/snd/controlC2: yanpas19734 F pulseaudio /dev/snd/controlC1: yanpas19734 F pulseaudio /dev/snd/controlC0: yanpas19734 F pulseaudio Date: Tue Apr 8 20:07:03 2014 InstallationDate: Installed on 2014-01-14 (83 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: 870 Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/14/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn870Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1304514/+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 1315212] Re: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output
I just tried this: ~$ speaker-test -c 6 -t wav -Dhw:CARD=CA0106,DEV=0 speaker-test 1.0.27.2 Playback device is hw:CARD=CA0106,DEV=0 Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Channels count (6) not available for playbacks: Invalid argument Setting of hwparams failed: Invalid argument -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1315212 Title: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: This is tested against a Creative Labs Sounblaster live! (sb0410) card and a SoundBlaster Audigy se (sb0570). Both of them behave strangely, output coming through some, but not all speakers, etc. This was working in 13.10 under the sb0410. the ca0106 driver is the same for both cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshp 30385 F pulseaudio /dev/snd/controlC0: joshp 30385 F pulseaudio CurrentDesktop: Unity Date: Thu May 1 21:37:12 2014 InstallationDate: Installed on 2014-04-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed Symptom_Card: Built-in Audio - Intel ICH6 Symptom_Type: None of the above Title: [CA0106 - CA0106, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0G8310 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2006:svnDellInc.:pnOptiPlexGX280:pvr:rvnDellInc.:rn0G8310:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex GX280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1315212/+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 1315212] Re: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output
here is the puleaudioverbose.log that was the output durring the command: ~$ speaker-test -c 6 -t wav -Dhw:CARD=CA0106,DEV=0 speaker-test 1.0.27.2 Playback device is hw:CARD=CA0106,DEV=0 Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Channels count (6) not available for playbacks: Invalid argument Setting of hwparams failed: Invalid argument ** Attachment added: pulseverbose.log https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1315212/+attachment/4108075/+files/pulseverbose.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1315212 Title: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: This is tested against a Creative Labs Sounblaster live! (sb0410) card and a SoundBlaster Audigy se (sb0570). Both of them behave strangely, output coming through some, but not all speakers, etc. This was working in 13.10 under the sb0410. the ca0106 driver is the same for both cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshp 30385 F pulseaudio /dev/snd/controlC0: joshp 30385 F pulseaudio CurrentDesktop: Unity Date: Thu May 1 21:37:12 2014 InstallationDate: Installed on 2014-04-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed Symptom_Card: Built-in Audio - Intel ICH6 Symptom_Type: None of the above Title: [CA0106 - CA0106, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0G8310 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2006:svnDellInc.:pnOptiPlexGX280:pvr:rvnDellInc.:rn0G8310:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex GX280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1315212/+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 1304514] Re: Pulseaudio microphone doesn't work after waking up from suspend
I have an extremely similar problem, probably the same bug. I have a logitech headset (Wireless Headset H800) with a usb dongle that shows up as: [61307.610747] usb 1-1.1: new full-speed USB device number 21 using ehci-pci [61307.764952] usb 1-1.1: New USB device found, idVendor=046d, idProduct=0a29 [61307.764963] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [61307.764969] usb 1-1.1: Product: Logitech Wireless Headset [61307.764974] usb 1-1.1: Manufacturer: Logitech [61307.764978] usb 1-1.1: SerialNumber: 000D44D3763D [61307.851018] input: Logitech Logitech Wireless Headset as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.3/input/input30 [61307.851408] hid-generic 0003:046D:0A29.0016: input,hiddev0,hidraw3: USB HID v1.11 Device [Logitech Logitech Wireless Headset] on usb-:00:1a.0-1.1/input3 Upon resume, it does show up, but only with profiles Analog stereo output OR Analog mono input. Sometimes one, sometimes the other. So upons resume usually my microphone doesn't work, sometimes sound output doesn't work. alsamixer seems to show both normally. After pulseaudio -k, or after rebooting, all 3 profiles are available: the two above plus Analog stereo output + Analog mono input -- 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/1304514 Title: Pulseaudio microphone doesn't work after waking up from suspend Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: When I wake up from suspend my microphones don't work. I need to type pulseaudio -k in terminal and restart apps (for example Skype or Audacity) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: yanpas19734 F pulseaudio /dev/snd/controlC2: yanpas19734 F pulseaudio /dev/snd/controlC1: yanpas19734 F pulseaudio /dev/snd/controlC0: yanpas19734 F pulseaudio Date: Tue Apr 8 20:07:03 2014 InstallationDate: Installed on 2014-01-14 (83 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: 870 Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/14/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn870Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1304514/+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 1068101] Re: [Upstream] Libreoffice Quicklist menu entries need internationalization
In ubuntu 14.04 the quicklist used only english language -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1068101 Title: [Upstream] Libreoffice Quicklist menu entries need internationalization Status in Ubuntu Translations: Fix Released Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Libreoffice launcher icons have got a New document, New spreadsheet, etc. entry added to their Unity quicklists. This particular entry is not internationalized and appears always in English (see attached screenshot). I can think of two ways of solving this: 1. Marking the strings for translation and providing a .pot file as part of the libreoffice package build, that can be imported into Launchpad for translators to do their work. Translations can then be shipped in the regular language packs. 2. Do a call for translations each cycle, similar to what we do already for the Firefox and Thunderbird desktop files, and manually put the received translations in the libreoffice desktop files. I'd suggest 1., as it's the most automated way and allows us to update translations independently from the libreoffice package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1068101/+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 1283826] Re: lightdm hangs after updates
Sorry, typo: sudo apt-get install ubuntu-desktop lightdm libgdk- pixbuf2.0-dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1283826 Title: lightdm hangs after updates Status in GDM: The Gnome Display Manager: New Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: I've updated today my Trusy Thar installation. I can't login to Unity, with my account, or a guest account. Lightdm hangs after password input, or after I click on the Guest account. Also, I used to auto-login. Now it greets me with the screen where I must input my password. After inputing it, lightdm hangs and I can't login. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Sun Feb 23 23:16:24 2014 InstallationDate: Installed on 2014-01-25 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140115) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=cristi autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1283826/+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 1317528] Re: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1
** Description changed: - The packages don't provide the virtual packages libopencl-1.1-1 and - libopencl-1.2-1. + The packages nvidia-libopencl1-... don't provide the virtual packages + libopencl-1.1-1 and libopencl-1.2-1. This causes problems with the installation of the following packages: python-pyopencl python3-pyopencl wine1.6-i386 (see https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1313123) wine1.6-amd64 starpu-contrib-examples libstarpu-contrib -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1317528 Title: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1 Status in “nvidia-graphics-drivers-304” package in Ubuntu: New Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: New Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: The packages nvidia-libopencl1-... don't provide the virtual packages libopencl-1.1-1 and libopencl-1.2-1. This causes problems with the installation of the following packages: python-pyopencl python3-pyopencl wine1.6-i386 (see https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1313123) wine1.6-amd64 starpu-contrib-examples libstarpu-contrib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1317528/+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 1311965] Re: UI scaling inconsistent when using new display scaling option
Hmm... after experiencing this a few more times, it seems like this is potentially a few different bugs. The tiny widgets is always happening, and seems to just be a flaw with older GTK programs (explaining why it occurs in Firefox). As for the windows not registering the scaling factor, it looks like something under the control of lightdm is breaking. restart lightdm seems to solve the problem whenever it occurs. Another piece of evidence for this is that Firefox's tabs regress to an old unstyled form whenever the issue occurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1311965 Title: UI scaling inconsistent when using new display scaling option Status in “xorg” package in Ubuntu: Confirmed Bug description: Just installed Ubuntu 14.04 on a Lenovo Yoga 2 Pro, which has a 3200x1800 display. Consequently, I need to scale up everything in the system to have anything render at a reasonable size. I found the new Scale for menu and title bars option in the Display Settings, and set it it 2.25. This, for the most part, did what I wanted. * Unity interface is scaled * Text is scaled * Many builtin applications seem to scale correctly However, there's some funky inconsistencies as to what has scaled: * Depending on what the mouse is over, it either renders at the larger (correct) size, or a smaller (incorrect) size. Examples of things which render the mouse incorrectly include the global/window bars, unity application selector, most applications (firefox and most of software center are notable exceptions), and sometimes right-click menus. * Some (GTK provided?) widgets (most notably checkboxes, radio buttons, scroll bars, and ) render too small. This is visible in most third-party applications, which are otherwise correctly sized. Firefox and CompizConfig are examples of this, even after layout.css.devPixelsPerPx was changed in Firefox to match the display setting. * The change occasionally doesn't correctly register with some or all applications (regardless of whether they were open at the time). Adjusting the slider always changes the unity global ui correctly, but sometimes the settings manager or nautillus would not actually render at an increased size, even after a reboot. Other times it would register fine even without a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 23 22:30:31 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-04-24 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=22977ed7-bb41-4448-98c8-bcf44422165e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1256540] Re: Ejecting USB (ex. Camera) doesn't offer to empty Trash
I have this problem in Ubuntu 14.04. Nautilus don't ask Do you want to empty the trash when I unmount an usb stick. In Ubuntu 13.10 when I unmount a usb stick in nautilus it ask me if I want to empty the trash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1256540 Title: Ejecting USB (ex. Camera) doesn't offer to empty Trash Status in “nautilus” package in Ubuntu: Confirmed Bug description: I have Lubuntu 13.10 (originally 12.04). I added Nautilus, so that I could have it show date/time for photos under the thumbnails, so I can easily group them. [The current version does not have the option of selecting the type of date displayed under the thumbnails in the preferences, so I had to install Nemo, which is based on an earlier version of Nautilus, and still can. I retained Nautilus, for some reason, and the bug is true for both apps. ] When I copy photos from my USB-attached camera, I send them to trash when I am satisfied the copy was successful. When I had regular Ubuntu (various versions prior to 12.04) and clicked on Eject or Safely remove drive, or whatever, I was asked whether or not I wished to empty the trash or not. At some point in Nautilus' development, some things changed. Now, there is only one option: Eject (or the equivilent clicking on the eject icon next to the device name). Now, when I select Eject or click on the icon, I am NOT asked if I want to empty the trash. I have repeatedly attached/removed the camera and tried both the context item and icon, but am not asked about the trash. I have to separately select all files in the two Trash sub-directories and click shift-del (and confirm that I wish to permanently delete the files). Why is Nautilus not asking me if I want to empty the trash? [Awhile ago, there was some discussion about the USB removal options that used to be present: Eject, Safely Remove Drive, and I think there might have also been a third one. I imagine the consensus was that having multiple options for essentially (literally?) the same operation was probably confusing to the user, and therefore the options were reduced to Eject. Am I correct? The Trash ought to be emptied, in any case...] --- scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy scott@scott-ASUS-M2N68-AM-PLUS:~$ nautilus --version GNOME nautilus 3.8.2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20~ppa1-generic-tuxonice 3.11.6 Uname: Linux 3.11.0-13-generic-tuxonice i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sat Nov 30 11:48:52 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-10-27 (33 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [deleted] usr_lib_nautilus: evince3.10.0-0ubuntu2 file-roller 3.10.1-0ubuntu1 gnome-mplayer 1.0.8-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1256540/+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 1317012] Re: Firefox 28 doesn't use intl.accept_languages defined in syspref.js
I have to correct something: It seems older Firefox versions had the same problem, but it wasn't obvious, because the default accept_languages of the firefox-locale-de package were already de-de,de,en-us,en. In Firefox 28 the default was changed to de,en-us,en. Nevertheless the problem is still, that Firefox reads the setting from syspref.js and displays this correctly in about:config, but doesn't use this value when constructing the HTTP header. The problem seems to be this test: http://mxr.mozilla.org/mozilla- central/source/modules/libpref/src/nsPrefBranch.cpp#232 So the accept_languages will only be used, when they are set by a user pref, or a locked pref, but not with a simple pref in syspref.js. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1317012 Title: Firefox 28 doesn't use intl.accept_languages defined in syspref.js Status in “firefox” package in Ubuntu: New Bug description: We have system-wide settings defined in /etc/firefox/syspref.js, amongst others the intl.accept_languages option to define the accept languages for our environment. Firefox 28 (28.0+build2-0ubuntu0.12.04.1) doesn't use the accept languages (and maybe others options) defined in syspref.js, when sending the HTTP header, even though the intl.accept_language value shown in about:config is correct (same as in syspref.js). It only works, if the intl.accept_languages is defined as a lockPref in syspref.js, which we don't want, because the users should be able to customize the setting. But we need to explicitly set the de-de accept language. This worked in previous Firefox versions (e.g. 27 or older). the corresponding line in syspref.js is: pref(intl.accept_languages, de-de,de,en-us,en); about:config shows: intl.accept_languages =de-de,de,en-us,en accept languages, which are sent in HTTP Header (this is the default from the firefox-locale-de package) : de,en-us,en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1317012/+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 1256540] Re: Ejecting USB (ex. Camera) doesn't offer to empty Trash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1256540 Title: Ejecting USB (ex. Camera) doesn't offer to empty Trash Status in “nautilus” package in Ubuntu: Confirmed Bug description: I have Lubuntu 13.10 (originally 12.04). I added Nautilus, so that I could have it show date/time for photos under the thumbnails, so I can easily group them. [The current version does not have the option of selecting the type of date displayed under the thumbnails in the preferences, so I had to install Nemo, which is based on an earlier version of Nautilus, and still can. I retained Nautilus, for some reason, and the bug is true for both apps. ] When I copy photos from my USB-attached camera, I send them to trash when I am satisfied the copy was successful. When I had regular Ubuntu (various versions prior to 12.04) and clicked on Eject or Safely remove drive, or whatever, I was asked whether or not I wished to empty the trash or not. At some point in Nautilus' development, some things changed. Now, there is only one option: Eject (or the equivilent clicking on the eject icon next to the device name). Now, when I select Eject or click on the icon, I am NOT asked if I want to empty the trash. I have repeatedly attached/removed the camera and tried both the context item and icon, but am not asked about the trash. I have to separately select all files in the two Trash sub-directories and click shift-del (and confirm that I wish to permanently delete the files). Why is Nautilus not asking me if I want to empty the trash? [Awhile ago, there was some discussion about the USB removal options that used to be present: Eject, Safely Remove Drive, and I think there might have also been a third one. I imagine the consensus was that having multiple options for essentially (literally?) the same operation was probably confusing to the user, and therefore the options were reduced to Eject. Am I correct? The Trash ought to be emptied, in any case...] --- scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy scott@scott-ASUS-M2N68-AM-PLUS:~$ nautilus --version GNOME nautilus 3.8.2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20~ppa1-generic-tuxonice 3.11.6 Uname: Linux 3.11.0-13-generic-tuxonice i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sat Nov 30 11:48:52 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-10-27 (33 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [deleted] usr_lib_nautilus: evince3.10.0-0ubuntu2 file-roller 3.10.1-0ubuntu1 gnome-mplayer 1.0.8-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1256540/+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 1316667] Re: 0.1+14.10.20140428-0ubuntu1 does not cross-build on utopic
This bug was fixed in the package ofono-qt - 1.5+git20120419+bcf0c04-0ubuntu7 --- ofono-qt (1.5+git20120419+bcf0c04-0ubuntu7) utopic; urgency=medium * Changes to enable reverse-deps to be cross-built, since cross-pkg-config no longer looks in /usr/lib/pkgconfig for pcfiles. (LP: #1316667) * debian/patches/11_use_libdir: Install library and pcfile into libdir, which for Ubuntu is a multiarch path. * Mark the library package as Multi-Arch: same. -- Iain Lane iain.l...@canonical.com Thu, 08 May 2014 11:33:37 +0100 ** Changed in: ofono-qt (Ubuntu) Status: In Progress = Fix Released ** Changed in: signon (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1316667 Title: 0.1+14.10.20140428-0ubuntu1 does not cross-build on utopic Status in “ofono-qt” package in Ubuntu: Fix Released Status in “signon” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: I imagine the underlying cause is not necessarily ubuntu-system- settings's alone (or at all), but it does not currently cross-build under utopic. See the attached sbuild log, but the interesting part is: The following packages have unmet dependencies: libaccountsservice-dev:armhf : Depends: gir1.2-accountsservice-1.0:armhf (= 0.6.35-0ubuntu7) Depends: libaccountsservice0:armhf (= 0.6.35-0ubuntu7) but it is not going to be installed Depends: libpolkit-gobject-1-dev:armhf but it is not going to be installed libnm-glib-dev:armhf : Depends: libnm-glib4:armhf (= 0.9.8.8-0ubuntu9) but it is not going to be installed Depends: gir1.2-networkmanager-1.0:armhf (= 0.9.8.8-0ubuntu9) but it is not going to be installed Depends: libnm-util-dev:armhf but it is not going to be installed libqmenumodel-dev:armhf : Depends: libqmenumodel0:armhf (= 0.2.7+14.04.20140305-0ubuntu2) but it is not going to be installed libubuntu-download-manager-client-dev:armhf : Depends: libudm-common-dev:armhf (= 0.3+14.10.20140430.1-0ubuntu1) but it is not going to be installed Depends: libubuntu-download-manager-common-dev:armhf (= 0.3+14.10.20140430.1-0ubuntu1) but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed libubuntuoneauth-2.0-dev:armhf : Depends: libsignon-qt5-dev:armhf but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed libunity-mir-dev:armhf : Depends: libunity-mir1:armhf (= 0.4+14.10.20140430.3-0ubuntu1) but it is not going to be installed Depends: libmirserver-dev:armhf (= 0.1.8) but it is not going to be installed Depends: libplatform-api1-dev:armhf but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed qt5-default:armhf : Depends: qtbase5-dev:armhf but it is not going to be installed qtbase5-private-dev:armhf : Depends: qtbase5-dev:armhf (= 5.2.1+dfsg-1ubuntu15) but it is not going to be installed qtdeclarative5-dev:armhf : Depends: libqt5quick5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed or libqt5quick5-gles:armhf but it is not installable Depends: libqt5quickparticles5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed or libqt5quickparticles5-gles:armhf but it is not installable Depends: libqt5quicktest5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.1+14.10.20140428-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 6 17:47:16 2014 SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1316667/+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 1316667] Re: 0.1+14.10.20140428-0ubuntu1 does not cross-build on utopic
This bug was fixed in the package signon - 8.56+14.04.20140307-0ubuntu3 --- signon (8.56+14.04.20140307-0ubuntu3) utopic; urgency=medium * Changes to enable reverse-deps to be cross-built, since cross-pkg-config no longer looks in /usr/lib/pkgconfig for pcfiles. (LP: #1316667) * Install into Multi-Arch directories and set M-A: Same on library packages. -- Iain Lane iain.l...@canonical.com Thu, 08 May 2014 10:58:12 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1316667 Title: 0.1+14.10.20140428-0ubuntu1 does not cross-build on utopic Status in “ofono-qt” package in Ubuntu: Fix Released Status in “signon” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: I imagine the underlying cause is not necessarily ubuntu-system- settings's alone (or at all), but it does not currently cross-build under utopic. See the attached sbuild log, but the interesting part is: The following packages have unmet dependencies: libaccountsservice-dev:armhf : Depends: gir1.2-accountsservice-1.0:armhf (= 0.6.35-0ubuntu7) Depends: libaccountsservice0:armhf (= 0.6.35-0ubuntu7) but it is not going to be installed Depends: libpolkit-gobject-1-dev:armhf but it is not going to be installed libnm-glib-dev:armhf : Depends: libnm-glib4:armhf (= 0.9.8.8-0ubuntu9) but it is not going to be installed Depends: gir1.2-networkmanager-1.0:armhf (= 0.9.8.8-0ubuntu9) but it is not going to be installed Depends: libnm-util-dev:armhf but it is not going to be installed libqmenumodel-dev:armhf : Depends: libqmenumodel0:armhf (= 0.2.7+14.04.20140305-0ubuntu2) but it is not going to be installed libubuntu-download-manager-client-dev:armhf : Depends: libudm-common-dev:armhf (= 0.3+14.10.20140430.1-0ubuntu1) but it is not going to be installed Depends: libubuntu-download-manager-common-dev:armhf (= 0.3+14.10.20140430.1-0ubuntu1) but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed libubuntuoneauth-2.0-dev:armhf : Depends: libsignon-qt5-dev:armhf but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed libunity-mir-dev:armhf : Depends: libunity-mir1:armhf (= 0.4+14.10.20140430.3-0ubuntu1) but it is not going to be installed Depends: libmirserver-dev:armhf (= 0.1.8) but it is not going to be installed Depends: libplatform-api1-dev:armhf but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed qt5-default:armhf : Depends: qtbase5-dev:armhf but it is not going to be installed qtbase5-private-dev:armhf : Depends: qtbase5-dev:armhf (= 5.2.1+dfsg-1ubuntu15) but it is not going to be installed qtdeclarative5-dev:armhf : Depends: libqt5quick5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed or libqt5quick5-gles:armhf but it is not installable Depends: libqt5quickparticles5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed or libqt5quickparticles5-gles:armhf but it is not installable Depends: libqt5quicktest5:armhf (= 5.2.1-5ubuntu1) but it is not going to be installed Depends: qtbase5-dev:armhf but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.1+14.10.20140428-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 6 17:47:16 2014 SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1316667/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
@William, i have a pure Ubuntu Gnome (3) system --- should I test your PPA? Keyboard switch with key-combos is utterly broken on my system, to the point that the only reliable way to obtain it is using the panel indicator --- which, by the way, is often than not out of sync with the real keymap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Fedora: Unknown Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572)
[Desktop-packages] [Bug 296867]
(In reply to comment #46) Empathy: http://cgit.collabora.com/git/user/xclaesse/empathy.git/log/?h=otr Ok for the first commit. Second commit: + tuple = empathy_gdbus_channel_interface_otr1_get_remote_fingerprint ( + priv-otr_proxy); I have no idea how these new generated API work, but GVariant API are usually 'return: (transfer full)' that's not the case here? + level = empathy_gdbus_channel_interface_otr1_get_trust_level ( + priv-otr_proxy); I guess this returns a cached value (not a blocking call) right? What happens if the proxy is not ready yet? Aren't we going to treat it as a wrong level and update it right after? + g_variant_get (tuple, (s@ay), fp, NULL); What's the 'ay' arg being ignored? Please add at least one comment. What happens if the user doesn't trust the fingerprint. The communication is still crypted? +N_(/otr action: Interact with the Off-The-Record system. Possible actions are:\n Is there a way to check (without changing) the current trust level? + g_variant_get (tuple, (s@ay), NULL, fp_variant); + empathy_gdbus_channel_interface_otr1_call_initialize ( + priv-otr_proxy, NULL, NULL, NULL); How does the user know if the operation succeeded or not? Just wait for the level update message? I think we should explicitely say if it failed so user explicitely know the conversation is not safe. + g_variant_get (tuple, (s@ay), NULL, fp_variant); I think fp_variant is leaked. chat_command_otr() will crash/assert if one of the D-Bus API failed. Also, shouldn't we use async API here? trust_level_to_str(): I'd mention encrypt using OTR to be clearer and avoid confusion my server encryption. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption Status in Chat app, and Telepathy user interface: Confirmed Status in One Hundred Papercuts: Invalid Status in Telepathy framework - library: Confirmed Status in “empathy” package in Ubuntu: Triaged Status in “libtelepathy” package in Ubuntu: Confirmed Status in “empathy” package in Fedora: Won't Fix Bug description: Binary package hint: empathy Hello, I just tried empathy (the Intrepid version) and it looked very solid and stable. There were a few minor things that could be improved (e.g. automatically resizing the contact list), but that is not the topic here. The reason why I won't switch to empathy from pidgin is the missing OTR support (http://www.cypherpunks.ca/otr/ ). This is a really important feature because no one should read your messages. There were others with the same idea (links at the bottom). Would be so great if it could support that important encryption standard. Thanks for helping out! Links: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/253452/comments/2 http://lists.cypherpunks.ca/pipermail/otr-users/2008-September/001479.html http://bugs.freedesktop.org/show_bug.cgi?id=16891 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+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 1293614] Re: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()
*** This bug is a duplicate of bug 1292560 *** https://bugs.launchpad.net/bugs/1292560 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-settings-daemon (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1293614 Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate() Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: I am not sure if this crash is related to the fact, that I continously loose my custom key settings from system settings keyboard shortcuts. The keys there are the ones I set, but they don't work. Setting it to another key enables them again, setting it to the one I want and had set at the beginning does however not work. Only a different one than the one used when booting up works. Other keyboard setting also get mixed up or changed back to it.'s original setting like windows-control-alt + key left (up, down, ..) for moving windows to another desktop, which gets set back to ubuntus original setting. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 unam -a Linux c1g2 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:44:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 15:28:58 2014 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon InstallationDate: Installed on 2014-03-13 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon SegvAnalysis: Segfault happened at: 0x7f355385e583 malloc_consolidate+307: cmp 0x18(%rax),%rbx PC (0x7f355385e583) ok source 0x18(%rax) (0x0018) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-settings-daemon StacktraceTop: malloc_consolidate (av=av@entry=0x7f3553b9e760 main_arena) at malloc.c:4157 _int_malloc (av=av@entry=0x7f3553b9e760 main_arena, bytes=bytes@entry=1056) at malloc.c:3423 __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3219 pa_xmalloc0 () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so pa_hashmap_new () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1293614/+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 1292560] Re: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()
I don't know if this could be of any help, but after this crash all keyboard shortcuts stopped working, even Ctrl+Alt+T for terminal. -- 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/1292560 Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate() Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I booted the system and got this error. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 11:03:04 2014 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcEnviron: PATH=(custom, user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f0b5c9ae583 malloc_consolidate+307: cmp 0x18(%rax),%rbx PC (0x7f0b5c9ae583) ok source 0x18(%rax) (0x7f0b5ccee7e80018) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-settings-daemon StacktraceTop: malloc_consolidate (av=av@entry=0x7f0b5ccee760 main_arena) at malloc.c:4157 _int_malloc (av=av@entry=0x7f0b5ccee760 main_arena, bytes=bytes@entry=1056) at malloc.c:3423 __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3219 pa_xmalloc0 () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so pa_hashmap_new () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: Upgraded to trusty on 2013-12-06 (97 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1292560/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
Same problem over here, using Ubuntu 14.04, nvidia 331.67 and a touchpad on a Lenovo Ideapad U410. When using the Intel graphics nothing happens, but when using nvidia graphics the screen freezes, only when the touchpad is used. When using a mouse nvidia graphics can be used without a freeze. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in “nvidia-graphics-drivers-319” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-prime” package in Ubuntu: Opinion Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+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 1317546] [NEW] 12.04 invisible cursor after screensaver exists
Public bug reported: System is stable Dell workstation with Ubuntu 12.04. It was updated a couple of day ago. After the recent update, sometimes the mouse cursor is not visible after returning from the screensaver. The only way it is useful with the invisible cursor is having the ctrl key make the cursor visible. The problem is not fixed by killing the X server and logging in again. The problem is only fixed by shutting down and rebooting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-61.92-generic-pae 3.2.55 Uname: Linux 3.2.0-61-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 CompizPlugins: (gconftool-2:11718): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Failed to get value for `/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running CompositorRunning: compiz Date: Thu May 8 10:47:07 2014 DistUpgraded: 2012-11-08 16:04:04,695 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: precise DistroVariant: ubuntu DkmsStatus: blcr, 0.8.2: added vboxhost, 4.3.10, 3.2.0-56-generic-pae, i686: installed vboxhost, 4.3.10, 3.2.0-61-generic-pae, i686: installed ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: NVIDIA Corporation C51 [GeForce 6150 LE] [10de:0241] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01ec] InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. OptiPlex 740 Enhanced MarkForUpload: True ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-61-generic-pae root=UUID=6928eccf-9e05-4a27-93d6-0e15b7e34694 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to precise on 2012-11-08 (545 days ago) dmi.bios.date: 05/04/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.6 dmi.board.name: 0YP696 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.6:bd05/04/2008:svnDellInc.:pnOptiPlex740Enhanced:pvr:rvnDellInc.:rn0YP696:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 740 Enhanced dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu3 version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.7 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.7 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.14 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 precise ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1317546 Title: 12.04 invisible cursor after screensaver exists Status in “xorg” package in Ubuntu: New Bug description: System is stable Dell workstation with Ubuntu 12.04. It was updated a couple of day ago. After the recent update, sometimes the mouse cursor is not visible after returning from the screensaver. The only way it is useful with the invisible cursor is having the ctrl key make the cursor visible. The problem is not fixed by killing the X server and logging in again. The problem is only fixed by shutting down and rebooting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-61.92-generic-pae 3.2.55 Uname: Linux 3.2.0-61-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 CompizPlugins: (gconftool-2:11718): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Failed to get value for `/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Romano, I think you can try it as long as you're not using the flashback sessions. I don't expect it'll fix your indicator syncing problems though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Fedora: Unknown Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) * Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637)
[Desktop-packages] [Bug 1298047] Re: Network-manager fails to retrieve VPN secrets when no password was necessary before
I think this bug is a duplicate of #1247682 and #1297849. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1298047 Title: Network-manager fails to retrieve VPN secrets when no password was necessary before Status in “network-manager” package in Ubuntu: Confirmed Bug description: I have several VPN configurations, that used to work some days (wekks ?) ago. Now, most of them fail, using several VPN software (vpnc and openvpn at least). The error seems to be the same in each case: error [1395865654.87082] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 26 21:27:24 2014 InstallationDate: Installed on 2013-02-16 (402 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.10 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-01-22 (63 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-01-18T13:13:34.565032 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1298047/+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 1147600] Re: pidgin crashed with SIGABRT in __libc_message()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pidgin (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1147600 Title: pidgin crashed with SIGABRT in __libc_message() Status in “pidgin” package in Ubuntu: Confirmed Bug description: Pidgin starts normally, then crashes after a few minutes. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.7-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2 Uname: Linux 3.8.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 5 14:43:58 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pidgin MarkForUpload: True ProcCmdline: pidgin --session 2b1b064a5-7292-486d-918b-5d0c90deaa46 --display :0.0 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pidgin StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 _IceFreeConnection () from /usr/lib/x86_64-linux-gnu/libICE.so.6 Title: pidgin crashed with SIGABRT in raise() UpgradeStatus: Upgraded to raring on 2013-02-16 (17 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1147600/+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 1317552] [NEW] usb modem doesn't recognized by system until wired network connected
Public bug reported: I have an usb 3g modem huawei, configured as standalone network device. When I connect it, dmesg shows some error messages, but nothing happens. After connect and futher disconnect wired network (eth0), it succesful recognized by the system as eth1 device and all works fine. Problem is that sometimes I have no wired network to start usb-3g connection this way. Part of dmesg with connect/disconnect manipulations [ 27.606224] init: libvirt-bin main process (979) terminated with status 127 [ 27.606239] init: libvirt-bin main process ended, respawning [ 27.915799] r8169 :01:00.0 eth0: link down [ 27.915869] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 27.916229] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 27.938186] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 27.941688] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.566084] usb 1-1.1: New USB device found, idVendor=0cf3, idProduct=0036 [ 28.566089] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 28.775155] init: plymouth-upstart-bridge main process ended, respawning [ 34.989561] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 55.380263] usb 3-3: new high-speed USB device number 3 using xhci_hcd [ 55.397190] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01 [ 55.397202] usb 3-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 55.397207] usb 3-3: Product: HUAWEI HiLink [ 55.397212] usb 3-3: Manufacturer: HUAWEI [ 55.465739] usb-storage 3-3:1.0: USB Mass Storage device detected [ 55.465795] scsi7 : usb-storage 3-3:1.0 [ 55.465865] usbcore: registered new interface driver usb-storage [ 56.464794] scsi 7:0:0:0: CD-ROMHUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 56.472835] sr1: scsi-1 drive [ 56.472989] sr 7:0:0:0: Attached scsi CD-ROM sr1 [ 56.473080] sr 7:0:0:0: Attached scsi generic sg3 type 5 [ 56.558838] audit_printk_skb: 156 callbacks suppressed [ 56.558842] type=1400 audit(1399561168.962:64): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2017 comm=apparmor_parser [ 56.558850] type=1400 audit(1399561168.962:65): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2017 comm=apparmor_parser [ 56.559369] type=1400 audit(1399561168.962:66): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2017 comm=apparmor_parser [ 56.638660] Buffer I/O error on device sr1, logical block 0 [ 56.638668] Buffer I/O error on device sr1, logical block 0 [ 56.638685] Buffer I/O error on device sr1, logical block 0 [ 56.638693] Buffer I/O error on device sr1, logical block 0 [ 56.638701] Buffer I/O error on device sr1, logical block 1 [ 56.638708] Buffer I/O error on device sr1, logical block 1 [ 56.638716] Buffer I/O error on device sr1, logical block 512 [ 56.640490] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such file or directory [ 56.640501] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such file or directory [ 56.651401] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such file or directory [ 56.651427] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such file or directory [ 107.810564] usb 3-3: USB disconnect, device number 3 [ 116.952712] usb 3-3: new high-speed USB device number 4 using xhci_hcd [ 116.969698] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01 [ 116.969709] usb 3-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 116.969715] usb 3-3: Product: HUAWEI HiLink [ 116.969720] usb 3-3: Manufacturer: HUAWEI [ 116.971391] usb-storage 3-3:1.0: USB Mass Storage device detected [ 116.971653] scsi8 : usb-storage 3-3:1.0 [ 117.969336] scsi 8:0:0:0: CD-ROMHUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 117.971006] sr1: scsi-1 drive [ 117.971389] sr 8:0:0:0: Attached scsi CD-ROM sr1 [ 117.974632] sr 8:0:0:0: Attached scsi generic sg3 type 5 [ 118.063825] quiet_error: 1 callbacks suppressed [ 118.063836] Buffer I/O error on device sr1, logical block 9 [ 118.063849] Buffer I/O error on device sr1, logical block 9 [ 118.063943] Buffer I/O error on device sr1, logical block 0 [ 118.063951] Buffer I/O error on device sr1, logical block 0 [ 118.063970] Buffer I/O error on device sr1, logical block 2 [ 118.063978] Buffer I/O error on device sr1, logical block 2 [ 118.063991] Buffer I/O error on device sr1, logical block 0 [ 118.064004] Buffer I/O error on device sr1, logical block 0 [ 118.064021] Buffer I/O error on device sr1, logical block 0 [ 118.064036] Buffer I/O error on device sr1, logical block 1 [ 118.069131] systemd-udevd[2224]: Failed to apply ACL on /dev/sr1: No such file or directory [ 118.069143] systemd-udevd[2224]: Failed to apply ACL on /dev/sr1: No such file or directory [ 118.073776]
[Desktop-packages] [Bug 1313654] Re: Left click does not work from time to time
I found a workaround that does not imply restarting lightdm: Alt+Control+F1 and then Alt+Control+F7 This is a decent workaround -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1313654 Title: Left click does not work from time to time Status in “xorg” package in Ubuntu: Confirmed Bug description: Hi, from times to times the left click does not work anymore and applications do not get focus. I changed the mouse from the Microsfot mouse I have to a Logitech and it still happened. I have this issue on LinuxMint 16 also so I don't think it's Unity. If I restart lightdm or X.org server it works for some time and the it happenes again. How can I troubleshoot this further? Maybe there is an app that grabs focus or something and it isn't a Ubuntu bug. Do you have a better workaround until this gets fixed? Restarting lightdm is not very plesant. lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: (gconftool-2:9362): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-YM9J4XCMg5: Connection refused Failed to get value for `/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 28 13:55:41 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3397] InstallationDate: Installed on 2014-04-18 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=e482c493-b5ce-48df-af5d-3d266f3f64b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: HI02182 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: HI02182 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq Elite 8300 SFF dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 28 13:39:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12387 vendor HWP xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313654/+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 1316229] Re: cups-filters 1.0.53 security tracking bug
This bug was fixed in the package cups-filters - 1.0.52-0ubuntu1.1 --- cups-filters (1.0.52-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: arbitrary code injection via malicous print servers (LP: #1316229) - debian/patches/CVE-2014-2707-part2.patch: also sanitize remote queue name in utils/cups-browsed.c. - CVE number pending * SECURITY UPDATE: BrowseAllow option fails open (LP: #1316229) - debian/patches/fix_browseallow.patch: Deny access if BrowseAllow option is invalid in utils/cups-browsed.c. - CVE number pending -- Marc Deslauriers marc.deslauri...@ubuntu.com Mon, 05 May 2014 13:02:52 -0400 ** Changed in: cups-filters (Ubuntu Trusty) Status: In Progress = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-2707 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1316229 Title: cups-filters 1.0.53 security tracking bug Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups-filters” source package in Trusty: Fix Released Status in “cups-filters” source package in Utopic: Fix Released Bug description: cups-filters 1.0.53 contains two security issues. CVE numbers have been requested, but are not yet available: http://www.openwall.com/lists/oss-security/2014/04/25/7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1316229/+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
