[Desktop-packages] [Bug 1225809] Re: empathy crashed with SIGSEGV in folks_persona_store_get_is_primary_store()
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 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/1225809 Title: empathy crashed with SIGSEGV in folks_persona_store_get_is_primary_store() Status in “empathy” package in Ubuntu: Incomplete Bug description: Adding account in app account online and activate the chat option. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Sun Sep 15 20:55:11 2013 ExecutablePath: /usr/bin/empathy InstallationDate: Installed on 2013-07-07 (70 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130704) MarkForUpload: True ProcCmdline: empathy SegvAnalysis: Segfault happened at: 0x7fd8e9b65899 : mov0x18(%rax),%eax PC (0x7fd8e9b65899) ok source "0x18(%rax)" (0xaac2) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: folks_persona_store_get_is_primary_store () from /usr/lib/x86_64-linux-gnu/libfolks.so.25 ?? () from /usr/lib/x86_64-linux-gnu/libfolks.so.25 ?? () from /usr/lib/x86_64-linux-gnu/libfolks.so.25 g_closure_invoke (closure=0x2197490, return_value=0x0, n_param_values=2, param_values=0x7fff2d79a7c0, invocation_hint=0x7fff2d79a760) at /build/buildd/glib2.0-2.37.7/./gobject/gclosure.c:777 signal_emit_unlocked_R (node=node@entry=0x1af8d00, detail=detail@entry=2323, instance=instance@entry=0x206a7a0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff2d79a7c0) at /build/buildd/glib2.0-2.37.7/./gobject/gsignal.c:3586 Title: empathy crashed with SIGSEGV in folks_persona_store_get_is_primary_store() 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/empathy/+bug/1225809/+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 1252646] Re: Empathy showing me as sender of new message in message notification applet instead of original sender
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 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/1252646 Title: Empathy showing me as sender of new message in message notification applet instead of original sender Status in “empathy” package in Ubuntu: Incomplete Bug description: I've configured Google talk account in Empathy. Sometimes when new message is received, it shows sender as myself in the message notification applet in systembar(I do not know the exact terminology) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 19 13:55:51 2013 ExecutablePath: /usr/bin/empathy MarkForUpload: True 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/1252646/+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 1223022] Re: Empathy requires authorisation for Facebook repeatedly
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 and any other logs that are relevant for this particular issue. ** Changed in: empathy (Ubuntu) Status: Confirmed => Incomplete ** Changed in: empathy Status: New => 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/1223022 Title: Empathy requires authorisation for Facebook repeatedly Status in Chat app, and Telepathy user interface: Incomplete Status in “empathy” package in Ubuntu: Incomplete Bug description: I am running Ubuntu 13.04 since June. There seems to be a persistent problem with Empathy and Ubuntu Online Accounts. On a clean installation of the OS, you can authenticate your Facebook account normally. After about half a month, you usually need to re-authorise your Online Accounts. In the old Gnome Online Accounts, everything worked well. At the moment, random authorisation requests emerge. Most of them are reset after a Computer restart; in some cases, though, Empathy seems to stuck even after the User performs an authorisation. The Plugin for the Unity Menu that displays posts from the News Feed works fine, so does Shotwell. Only Empathy refuses to show the Contact list and connect to Facebook. To be more specific it displays this message: "Facebook account requires authorisation". However, when you open the Online Accounts, there is no relevant notice! I have tried removing and resetting the Account, I removed Ubuntu app from Facebook, I reinstalled (apt-get purge, apt-get install) Empathy, Facebook Account Plugin, Ubuntu Online Accounts and cleaned up all data using Bleachbit! Even deleting the account doesn't fix the problem. I noticed through Seahorse that every time you authorise an account, the Authorisation Token Name changes (e.g. from "Ubuntu Online Account: id 3-1" to "Ubuntu Online Account: id 4-1). What is more, there are two entries for Facebook! One that contains my Password, and another one that what seems to be a generated Key. Maybe Empathy mixes up the names, because the problem occurs only after a re-authorisation. I'm running Empathy 3.6.4 on Ubuntu 13.04 32bit. The problem occurs on both 32bit and 64bit versions of Ubuntu. I did some research and found out that Ubuntu Online Accounts and Empathy has been unstable for some time now. It is not very easy to reproduce the issue, as it may take some time. However, once it occurs, there seems to be no return. Simply use a Facebook Account in UOA with 2-Step Verification enabled. Originally, you will be able to connect normally, after entering your password and generated code. After some time (usually right after 15 days, when a re-authorisation is normally needed) you will not be able to access Facebook Chat from Empathy with that account again, no matter how many times you re-authorise it or even if you delete it and re-add it! As I've seen on the Web, similar problems affect a significant number of Users! Please, spend some time in fixing the UOA; its being so annoying acts as a deterrent from Ubuntu... And this is a pity, because - in my opinion - it is currently the best Linux Distribution out there. Thanks in Advance!!! :D To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1223022/+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 1231916] Re: AMD A6-5400k APU with Radeon HD 8600 - Failed to start X after Installation
Also, this issue cannot be reproduced with 12.04.4 on 201305-13489, which is not a hybrid-graphic system ([1002:6600] only) And cannot be reproduced with 201307-13919, a hybrid-graphic system ([1002:9995] + [1002:6600]) Thus I think this might be a system-specific issue (or the combination of video controllers) -- 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/1231916 Title: AMD A6-5400k APU with Radeon HD 8600 - Failed to start X after Installation Status in “xorg-server” package in Ubuntu: Confirmed Bug description: On this hardware system, user can only see graphic installer using UEFI mode, in the other hand legacy mode can only see black screen during when booting installer. After installation successfully by using UEFI mode, it can't boot into X desktop. It's blocking user to use jockey-gtk to install fglrx driver. --- .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: fglrx-updates, 12.104, 3.8.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2af6] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8750M] [1002:6600] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2af6] InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) JockeyStatus: xorg:fglrx_experimental_13 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Enabled, Not in use) MachineType: Hewlett-Packard DVT-ys002 MarkForUpload: True NonfreeKernelModules: fglrx Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic.efi.signed root=UUID=600f7c05-868f-479d-80a1-a96c33ce8ca5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/07/2013 dmi.bios.vendor: AMI dmi.bios.version: 3.13H dmi.board.asset.tag: 4CS247000Z dmi.board.name: 2AF6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 011 dmi.chassis.asset.tag: 4CS247000Z dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr: dmi.product.name: DVT-ys002 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu2 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1231916/+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 1246996] Re: New messages: alert, but not shown in message window, when logging disabled
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 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/1246996 Title: New messages: alert, but not shown in message window, when logging disabled Status in “empathy” package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 13.10 recently, the behaviour of Empathy has changed. Before, when I received an alert about a new message and subsequently opened the message window, the new message that I saw in the alert would also be found in the message window. Now, this is not the case. The message window is blank until a second message is sent. Note that I have logging disabled. If I enable logging, then I will see the message, but without the proper CSS formatting: the message and timestamp just appear with unformatted black text. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Fri Nov 1 15:31:59 2013 InstallationDate: Installed on 2011-01-05 (1030 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MarkForUpload: True ProcEnviron: LANGUAGE=en_AU:en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to saucy on 2013-10-28 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1246996/+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 1235466] Re: Previous chats from Hangouts aren't imported
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** 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/1235466 Title: Previous chats from Hangouts aren't imported Status in “empathy” package in Ubuntu: Incomplete Bug description: When I am signed into my Google account using the Gnome accounts feature on not just Ubuntu GNOME 13.10, but any other variant or version of Ubuntu, I get the same thing... I open up a new conversation thread with a friend whom I have previously talked to using Google's official Hangouts application for Android or Chrome, and what I find is that all the old contents, so the texts, pictures, threads, everything... Are just not there. I sign into my Google account on Empathy for the simplicity that synchronization makes, but I come to realize that it doesn't even correctly synchronize those conversations. Please fix this problem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 4 17:02:13 2013 InstallationDate: Installed on 2013-10-04 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 (20130926) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= 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/1235466/+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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
If you open more than one tab, if one of the tabs point to home it will working as expected(raise existing window), if all tabs point to another drive location then it's open new window. -- 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/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+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 296867]
Disturbingly that applies as much to Monsanto as it does to Ubuntu or FOSS. On 30 Apr 2014 07:15, "James Cuzella" wrote: > Complaints show fear, anger & ungratefulness while calm feature requests > show peace, gratefulness & understanding of a problem. > > Community giving of FOSS shows kindness & compassion, while taking & > complaining shows an unsatisfied desire for control. > > True control lies in harmonising with the community, and paradoxically > involves letting go of your need for control while also giving the part > which is under your control. > > Heartbleed shows inherent insecurity of a house divided against itself > yet it also shows the speed of the Whole to heal itself. > > Privacy is an illusion... security built on deterministic Laws has little > room for true randomness without hiding within Complexity. The appearance > of randomness is Chaos, yet within the chaos lies a higher Order. > > No matter which side you think you are on... you're actually on both, and > they are not truly opposed when undivided. > > > On Mon, Apr 28, 2014 at 12:31 PM, Sam Liddicott > wrote: > > > I'm feed up of people complaining about people complaining about wilful > bad > > security. > > > > This is doubly so considering all the criticism that has gone the way of > > the OpenSSL people in the wake of Heartbleed. > > > > A little more discussion there might have helped, but here it obviously > > hasn't! > > > > When someone gives their time and experience to improve software designs > > from fatal flaws, often in the evenings with other distractions, they get > > next to no gratitude and a whole heap of criticism as if their drawing > > attention to the flaw is worse than the flaw itself. > > > > Free software doesn't stop people talking about the naked emperor. > > > > If they are not government spies and but just play at spies in their > > evenings (with other distractions) then that is fine, but if they then > make > > a public gift of it can they really expect people to not talk about it? > > > > They don't buy our silence with their wooden horse! > > > > We don't use it and we warn others. We actually care about their users! > > > > Sam > > On 28 Apr 2014 18:55, "Chris Kerr" wrote: > > > > > I'm fed up of people complaining about developers. It's *free > software*, > > > and if you get anything more than you paid for then you should be > > > grateful (I certainly am). > > > > > > This is doubly so considering all the criticism that has gone the way > of > > > the OpenSSL people in the wake of Heartbleed. When someone gives their > > > best effort to produce software as a gift to the community, often > > > working in spare evenings with lots of other distractions which prevent > > > them giving their full focus to the task, they get next to no praise > > > when it works and a whole heap of criticism when they make a tiny > > > mistake. People even accuse them of deliberately inserting the mistake > > > as a government spy. > > > > > > I'm currently writing up my PhD thesis. When I finish, I will have some > > > free time while waiting for my viva voce, and would be willing to spend > > > some of that time trying to fix this, as it is something I would find > > > useful myself and potentially also a helpful addition to my CV. However > > > there are probably plenty of people out there who would do a better job > > > than I, especially since I have mainly used Fortran and Python for the > > > last 4 years so my C/C++ is rather rusty. > > > > > > -- > > > You received this bug notification because you are subscribed to the > bug > > > report. > > > https://bugs.launchpad.net/bugs/296867 > > > > > > Title: > > > empathy needs to support OTR encryption > > > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions > > > > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/296867 > > > > Title: > > empathy needs to support OTR encryption > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/296867 > > Title: > empathy needs to support OTR encryption > > To manage notifications about this bug go to: > https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions > -- 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” pack
[Desktop-packages] [Bug 1313283] Re: gedit always prints in black and white on color printer
** Attachment added: "error_log" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313283/+attachment/4101068/+files/error_log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1313283 Title: gedit always prints in black and white on color printer Status in “cups” package in Ubuntu: Incomplete Bug description: gedit shows syntax highlighting (with default Classic color scheme) properly, yet prints/previews text as black-and-white for a color printer (Xerox Phaser 6180DN in this case). Before 14.04 it used to print properly in color. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 27 03:47:14 2014 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-04-03 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313283/+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 1253096] Re: Cannot add IRC account with NickServ password
I think this is a problem in ubuntu-system-settings-online-accounts , not in empathy. If anybody can confirm the bug should probably be assigned to Ubuntu Online Accounts and not to empathy. -- 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/1253096 Title: Cannot add IRC account with NickServ password Status in Chat app, and Telepathy user interface: New Status in One Hundred Papercuts: Confirmed Status in “empathy” package in Ubuntu: Confirmed Bug description: In accounts settings: 1. Add new IRC account (I tested Freenode), input nick and hit done. 2. Things seem ok, it connects in Empathy (even though the Empathy connection button in accounts dialog isn't enabled yet, which is surprising.) 3. I have a registered nick at Freenode, so I need to provide password for NickServ at login. Hit "edit options" in accounts dialog and input a password, then hit done. 4. Now the access trouble starts (and Empathy disconnects). See attached screencast which demonstrates the problem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: account-plugin-irc 3.8.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 20 15:13:45 2013 InstallationDate: Installed on 2013-11-02 (18 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1253096/+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 1314499] [NEW] Problems with login after starting laptop
Public bug reported: Problems with login after starting laptop - it shows only black screen with cursor. After restart lightdm service it shows login screen and then works normaly. This laptop has only 250 GB SSD disk. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.4 ProcVersionSignature: Ubuntu 3.5.0-49.73~precise1-generic 3.5.7.32 Uname: Linux 3.5.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Apr 30 09:10:03 2014 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: LC_TIME=en_GB.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/1314499 Title: Problems with login after starting laptop Status in “lightdm” package in Ubuntu: New Bug description: Problems with login after starting laptop - it shows only black screen with cursor. After restart lightdm service it shows login screen and then works normaly. This laptop has only 250 GB SSD disk. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.4 ProcVersionSignature: Ubuntu 3.5.0-49.73~precise1-generic 3.5.7.32 Uname: Linux 3.5.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Apr 30 09:10:03 2014 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: LC_TIME=en_GB.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1314499/+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 1313283] Re: gedit always prints in black and white on color printer
** Attachment added: "phaser.ppd" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313283/+attachment/4101070/+files/phaser.ppd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1313283 Title: gedit always prints in black and white on color printer Status in “cups” package in Ubuntu: Incomplete Bug description: gedit shows syntax highlighting (with default Classic color scheme) properly, yet prints/previews text as black-and-white for a color printer (Xerox Phaser 6180DN in this case). Before 14.04 it used to print properly in color. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 27 03:47:14 2014 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-04-03 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313283/+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 1313283] Re: gedit always prints in black and white on color printer
** Attachment added: "printout" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313283/+attachment/4101069/+files/printout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1313283 Title: gedit always prints in black and white on color printer Status in “cups” package in Ubuntu: Incomplete Bug description: gedit shows syntax highlighting (with default Classic color scheme) properly, yet prints/previews text as black-and-white for a color printer (Xerox Phaser 6180DN in this case). Before 14.04 it used to print properly in color. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 27 03:47:14 2014 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-04-03 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313283/+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 1313488] Re: cups multiple usb printers hangs after job sent
gohulu, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1313488 Title: cups multiple usb printers hangs after job sent Status in “cups” package in Ubuntu: New Status in “libusb-1.0” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: I have four printers: An Epson Photo Stylus T50 with the gutenprint driver An Epson Stylus T1110 with the gutenprint driver A Samsung ML 1860 with the ULD Samsung Proprietary Driver A Samsung ML 2160 wirh the ULD Samsung Proprietary Driver Everything works fine when I try to print to any of these printers, however, let's say I wanna print a picture on any of the epson printers, I just send the job, rigth?, but at the same time I want to print something on any of the Samsung Printers, I just send the job too, well the job sent to the samsung printer will print but the job sent to the epson printer hangs with the message "Unable to send data to printer" and won't print, I have to cancel the Epson job and send it again, this is the debug information I consider important to describe the problem, in this case [Job 684] is the job sent to the Epson Printer and [Job 685] is the job sent to the Samsung printer. [Job 684] Wrote 8192 bytes of print data... D [27/Apr/2014:21:28:21 -0500] [Job 684] Read 8192 bytes of print data... D [27/Apr/2014:21:28:21 -0500] [Job 685] Printing on printer with URI: usb://Samsung/ML-1860%20Series?serial=Z5SXBKDB400399N. D [27/Apr/2014:21:28:21 -0500] [Job 685] libusb_get_device_list=13 D [27/Apr/2014:21:28:21 -0500] [Job 685] STATE: +connecting-to-device D [27/Apr/2014:21:28:21 -0500] Discarding unused printer-state-changed event... E [27/Apr/2014:21:28:21 -0500] [Job 684] Unable to send data to printer. D [27/Apr/2014:21:28:21 -0500] [Job 684] Set job-printer-state-message to "Unable to send data to printer.", current level=ERROR D [27/Apr/2014:21:28:21 -0500] [Job 684] libusb write operation returned fffc. D [27/Apr/2014:21:28:21 -0500] [Job 684] Sent 204800 bytes... D [27/Apr/2014:21:28:21 -0500] Discarding unused job-progress event... D [27/Apr/2014:21:28:21 -0500] Discarding unused printer-state-changed event... D [27/Apr/2014:21:28:21 -0500] [Job 685] STATE: -connecting-to-device ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu8.2 ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Sun Apr 27 21:51:56 2014 InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) Lpstat: device for Epson_Stylus_Office_T1110: usb://EPSON/Stylus%20Office%20T1110?serial=4C4E56593031393355 device for Epson_Stylus_Photo_T50: usb://EPSON/Stylus%20Photo%20T50?serial=4C434C4B3138343743 device for Samsung_ML-1860_Series: usb://Samsung/ML-1860%20Series?serial=Z5SXBKDB400399N. device for Samsung_ML-2160_Series: usb://Samsung/ML-2160%20Series?serial=Z2VJBFAZ232311P MachineType: CLEVO Co. M550SE MarkForUpload: True Papersize: letter PpdFiles: Samsung_ML-1860_Series: Samsung ML-1860 Series Samsung_ML-2160_Series: Samsung ML-2160 Series Epson_Stylus_Office_T1110: Epson Stylus Office T1110 - CUPS+Gutenprint v5.2.8-pre1 Epson_Stylus_Photo_T50: Epson Stylus T50 - CUPS+Gutenprint v5.2.8-pre1 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: M550SE/M660SE dmi.board.vendor: CLEVO Co. dmi.board.version: VT6363A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: VIA dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/12/2007:svnCLEVOCo.:pnM550SE:pvrVT6363A:rvnCLEVOCo.:rnM550SE/M660SE:rvrVT6363A:cvnVIA:ct1:cvrN/A: dmi.product.name: M550SE dmi.product.version: VT6363A dmi.sys.vendor: CLEVO Co. mtime.conffile..etc.cups.cupsd.conf: 2014-04-27T21:05:44.373803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscri
[Desktop-packages] [Bug 1313283] Re: gedit always prints in black and white on color printer
All three files (error_log, printout, ppd) are attached as requested. printout appears to be a PDF file, and it shows the output as I get it: black and white, while on the screen it is colored. I double-checked printer and gedit settings --- color is on in both of them. Printing to PDF directly leads to the same result: black and white. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1313283 Title: gedit always prints in black and white on color printer Status in “cups” package in Ubuntu: Incomplete Bug description: gedit shows syntax highlighting (with default Classic color scheme) properly, yet prints/previews text as black-and-white for a color printer (Xerox Phaser 6180DN in this case). Before 14.04 it used to print properly in color. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 27 03:47:14 2014 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-04-03 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1313283/+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 1261060] Re: sometime empathy chat dialogs open empty/with a negative unread count
Hi Chris, Thanks for your efforts. I've installed 3.8.6-0ubuntu9.1, and unfortunately it's inconclusive. For me (as with others), the error occurs when I have no chat window open with the correspondent and I am sent a new message. In this case, the main list of contacts shows the "flashing light" (there's also no integration with desktop notifications, so I don't get the "blue envelope", but that might be an unrelated bug). When I click on the contact with the flashing light, I still see the "(-1 unread)" in the title bar. However, whether the message shows up seems to be a bit random. The first time I tried it, the messages appeared. This was with three messages, so maybe the later ones had some kind of "flush" action that caused the earlier ones to appear. The second time I tried it, I saw nothing in the window. The name of the contact showed a "white speech bubble" showing that there was an unread message, but there was no message. The title bar said "(-1 unread)". The third time I tried it, it worked (I saw the new message). However, the (presumably) previous message was visible. Interestingly, it's not "styled" in the same way: it doesn't appear in a little speech bubble with colours, but is instead plain unstyled black and white text. Hope this is useful. -- 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/1261060 Title: sometime empathy chat dialogs open empty/with a negative unread count Status in Chat app, and Telepathy user interface: Confirmed Status in “empathy” package in Ubuntu: Confirmed Status in “empathy” source package in Trusty: Fix Committed Bug description: * Impact: sometime messages are not displayed when opening the chat view after receiving one * Test Case: - open the empathy contact list - select the contact that is going to send you a message - clear the history - send the message - open it by clicking the buddy list entry -> the message should be listed in the chat view * Regression potential: check that messages are correctly listed in chat view, in correct order and the scrolling is done correct when adding new ones Whenever i get a message in empathy (google talk account) and i open the message via the blue indicator symbol, only an empty window opens, swallowing the message, with title (-X unread) See screenshot: https://dl.dropboxusercontent.com/u/27087995/ubuntubugs/unread.png desired behaviour: have the message appear in the window ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-messages 13.10.1+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Dec 15 02:02:26 2013 InstallationDate: Installed on 2013-12-13 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1261060/+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 1314506] [NEW] Black screen when running System Parameters
Public bug reported: Step to reproduce: start gnome-control-center (either from UI or command line) Expected result: System Settings screen will open Actual result: 1) Black screen 2) Had to restart (soft reboot) Supppose that the same problem could be related to random black screen start: computer will boot into black screen. Had to restart it once again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu56 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: Wed Apr 30 10:31:46 2014 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-04-25 (4 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1314506 Title: Black screen when running System Parameters Status in “gnome-control-center” package in Ubuntu: New Bug description: Step to reproduce: start gnome-control-center (either from UI or command line) Expected result: System Settings screen will open Actual result: 1) Black screen 2) Had to restart (soft reboot) Supppose that the same problem could be related to random black screen start: computer will boot into black screen. Had to restart it once again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu56 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: Wed Apr 30 10:31:46 2014 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-04-25 (4 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1314506/+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 1308895] Re: Huawei E3531 does not automatically switches to modem mode (no udev rules for this modem in /etc/udev/rules.d.)
Jaki postęp w tym kierunku będzie w Ubuntu 14.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1308895 Title: Huawei E3531 does not automatically switches to modem mode (no udev rules for this modem in /etc/udev/rules.d.) Status in “usb-modeswitch” package in Ubuntu: Confirmed Bug description: The operating system does not see the modem maybe because usb- modeswitch not automatically switches the device mode the modem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: usb-modeswitch 2.1.1+repack0-1ubuntu1 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: Thu Apr 17 11:34:11 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140415) SourcePackage: usb-modeswitch UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1308895/+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 1283397] Re: videos only take up 1/4 (one quarter/fourth) of the window
Problem probably lies in hidpi scaling. Im using x2 dpi scaling factor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1283397 Title: videos only take up 1/4 (one quarter/fourth) of the window Status in Sushi (GNOME): New Status in Totem Movie Player: New Status in “gnome-sushi” package in Ubuntu: New Status in “totem” package in Ubuntu: New Status in “gnome-sushi” package in Fedora: New Status in “totem” package in Fedora: New Bug description: On Lenovo Yoga 2 Pro To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-sushi/+bug/1283397/+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 1161854] Re: System Notification Warning: flashplugin-installer could not be processed
I ran into this problem again. Removing the file /var/lib/update-notifier/user.d/data-downloads-failed-permanently seems to stop the occurence of the notification. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1161854 Title: System Notification Warning: flashplugin-installer could not be processed Status in “flashplugin-nonfree” package in Ubuntu: Confirmed Bug description: Upgrading the flashplugin-installer had a problem with downloading the flash-tar-file. Because it took very long I have interrupted it and retried again with AFAIR "apt-get -f install". The plugin was successfully updated then. But: Everytime I log into KDE I see a system notification "Update Information": "Data files for some packages could not be downloaded The following packages requested additional data downloads after package installation, but the data could not be downloaded or could not be processed...flashplugin-installer... This is a permanent failure that leaves the packages unusable on your system. You may need to fix your internal connection, then remove and reinstall the packages to fix this problem". So I tried to "apt-get purge flashplugin-installer" and reinstalled it again "apt-get install flashplugin-installer". But the warning still persists. (Although flash does work fine in e.g. firefox.) How can I get rid of this warning? Thanks, Gert ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: flashplugin-installer 11.2.202.275ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Mar 29 13:13:40 2013 InstallationDate: Installed on 2012-11-03 (146 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: flashplugin-nonfree UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1161854/+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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
I had the problem in Ubuntu 13.04 but not anymore in Ubuntu 14.04. I believe it could related to the way how you mount it. I will check the fstab as soon as I will be back at home. -- 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/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+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 1013881] Re: Right-Ctrl key broken on French OSS keyboard
> is there generic popular Linux-oriented site in France? Like slashdot.org or smth... LinuxFr.org -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Bug description: Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key of the keyboard has ceased to work. The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 2.5-1ubuntu1.2. If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Sat Jun 16 00:16:09 2012 Dependencies: DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader MachineType: LENOVO 4243E69 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243E69 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4243E69 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 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.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+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 1013881] Re: Right-Ctrl key broken on French OSS keyboard
> is there generic popular Linux-oriented site in France? Like slashdot.org or smth... LinuxFr.org -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Bug description: Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key of the keyboard has ceased to work. The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 2.5-1ubuntu1.2. If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Sat Jun 16 00:16:09 2012 Dependencies: DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader MachineType: LENOVO 4243E69 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243E69 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4243E69 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 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.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+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 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot
I played a bit more time with indep_hp, but looks like it does not fix the problem. Screenshots from alsamixer: http://imgur.com/goorPt5,pDmikVT Tried the utility from your link but it crashes: http://pastebin.com/CCbLuQnf -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot Status in “alsa-driver” package in Ubuntu: New Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313904/+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 1304404] Re: The inability to create a connection through Huawei E3531
** Bug watch added: GNOME Bug Tracker #729243 https://bugzilla.gnome.org/show_bug.cgi?id=729243 ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=729243 Importance: Unknown Status: Unknown -- 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/1304404 Title: The inability to create a connection through Huawei E3531 Status in NetworkManager: Unknown Status in “network-manager” package in Ubuntu: Confirmed Bug description: If you create access to the Internet using usb modem ZTE MF667 then the network periodically breaks. Usb Modem Huawei E3531 network- manager doesn't see, so you cannot create any connection. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 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 CurrentDesktop: Unity Date: Tue Apr 8 16:49:01 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-06 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140405) IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 10.39.225.164 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: ** (process:23293): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/2: uid 1000 has no permission to perform this operation ** (process:23293): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceModem. RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1304404/+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 1309971] Re: other workspaces are blank with no way to switch back
As you seem to be not able to reproduce it anymore, I am closing it. ** Changed in: gnome-panel (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1309971 Title: other workspaces are blank with no way to switch back Status in “gnome-panel” package in Ubuntu: Invalid Bug description: What I did; - upgraded to 14.04 trusty - installed gnome-session-flashback - logged out; logged in with gnome flashback (compiz) - in the lower left corner, right click to bring up preferences; change number of workspaces to 4 - click on workspace 3 What I expected: - a panel (with clock etc.) above and a (mostly) blank taskbar below with a workspace switcher - or at least the ability to get back to workspace 1 using ALT-arrow What I saw instead: - a screen completely blank except for the background - no way to change workspaces, launch programs log out, etc. I had to CTRL-ALT-F1 and loging and `sudo /etc/init.d/lightdm restart` to log in again. Of course, I lose my session state. The symptoms are very much like #156502. That bug was closed as as invalid with an explanation of "This particular bug has already been reported into our bug tracking system" but no reference to the bug that was already reported. If it was already reported, shouldn't the status be something like duplicate? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session-flashback 1:3.8.0-1ubuntu11 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: Sat Apr 19 08:29:31 2014 GsettingsChanges: InstallationDate: Installed on 2013-04-12 (372 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) PackageArchitecture: all SourcePackage: gnome-panel UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1309971/+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 1313378] Re: [hsw mesa] Intel 4000 video crashes on play
** Summary changed: - Intel 4000 video crashes on play + [hsw mesa] Intel 4000 video crashes on play -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1313378 Title: [hsw mesa] Intel 4000 video crashes on play Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: try to play some steam games, or simple random screen crashes... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 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: Sun Apr 27 10:29:27 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: Dell Device [1028:05f3] InstallationDate: Installed on 2014-04-26 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 3437 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-24-generic.efi.signed root=/dev/sdb2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0FYRW0 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0FYRW0:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. 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: Sun Apr 27 10:21:53 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5238 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1313378/+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 1310976] Re: LTS 14.04 after change desktop - cant control system
When you change workspace, your apps are left on previous workspace. To return to that workspace, you should click on the workspace indicator or use Ctrl+Alt+Arrow key combination. You also say that you can't open any apps. Can you please run "gnome- panel --replace" in the terminal, trigger this bug and paste here the terminal output? ** Changed in: gnome-panel (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1310976 Title: LTS 14.04 after change desktop - cant control system Status in “gnome-panel” package in Ubuntu: Incomplete Bug description: I start gnome-panel under UBUNTU 14.04 LTS. I have 4 desktops. When I click by mouse any desktop on gnome-panel, new desktop appear but whole overlay of system goes to background -> on small 2x2 panel icon I can see open apps, but all desktops where empty. Also when I click any icon it doesn to anything. SUPER+S works - I can change desktops, but I didnt see any previous open application //and cant do nothing in X. CTRL+ALT+Backspace also doesnt work. Only way how to solve that problem is go to terminal and restart system. I really need gnome panel for fast switchng between apps &&& To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1310976/+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 1286552] Re: No wifi after suspend
Seems solution in #68 solved the problem for me. I installed 14.04 recently and suffered from this problem along with the other (often my Xubuntu failed to suspend/reboot/shutdown at all). So the following steps let me comepletely get rid of these problems: 1. turn off Light Locker 2. uncheck All Settings -> Power Manager -> Extended -> Lock screen when going for suspend/hibernate 3. reboot After all it looks to me like all the problems have the same roots related to Light Locker and screwed permissions. -- 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/1286552 Title: No wifi after suspend Status in “linux” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: After suspending ubuntu the wifi doesn't work. The solution given here (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re- connecting-after-suspend) worked for me but when I have updated my Ubuntu now it won't work. I have tried to test mainline kernel but it won't to boot with it. To reproduce the bug : just suspend the computer and then power it. There's no wifi network until you restart the computer. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CrashDB: ubuntu Date: Sat Mar 1 15:20:39 2014 InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradi 1503 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) MachineType: Hewlett-Packard HP Compaq 6830s MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 Tags: saucy Uname: Linux 3.11.0-15-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Mar 1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] perf samples too long (5002 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 dmi.bios.date: 03/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0C dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1C dmi.chassis.asset.tag: CNU91609Y2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6830s dmi.product.version: F.0C dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+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 1267293] Re: chromium-browser doesn't start; crashes wich SIGSEGV in libprotobuf.so
After updating to 14.04, this problem doesn't reproduce. I would like to close this. Thanks, Chad. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1267293 Title: chromium-browser doesn't start; crashes wich SIGSEGV in libprotobuf.so Status in “chromium-browser” package in Ubuntu: Fix Released Bug description: chromium-browser doesn't start at all. It crashed with SEGSIGV. The backtrace is as follows: --- #0 0x7fff57d4df27 in ?? () from /usr/lib/libprotobuf.so.7 #1 0x77de9856 in call_init ( l=, argc=1, argv=0x7fffdd58, env=0x5717b890) at dl-init.c:84 --- This symptom started some months ago after a certain upgrade. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 ChromiumPrefs: can't open profile /home/kato/.config/chromium/Default/Preferences Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DistroRelease: Ubuntu 13.10 DmesgChromium: [ 859.445224] chromium-browse[5435]: segfault at 7f031b890f0c ip 7f0286823f27 sp 7fffb47b1528 error 6 in libprotobuf.so.7.0.0[7f02867e5000+ed000] [ 1332.395415] chromium-browse[7518]: segfault at 7f0236e9ef0c ip 7f01a1bf0f27 sp 7fff8245d5f8 error 6 in libprotobuf.so.7.0.0[7f01a1bb2000+ed000] [14067.080241] chromium-browse[11940]: segfault at 7f66dde14f0c ip 7f664cde4f27 sp 7fff67211e58 error 6 in libprotobuf.so.7.0.0[7f664cda6000+ed000] [88576.082314] chromium-browse[30534]: segfault at 7fdaf49c8f0c ip 7fda57863f27 sp 7fff15d6d108 error 6 in libprotobuf.so.7.0.0[7fda57825000+ed000] [88687.684083] chromium-browse[31394]: segfault at 7f6cd52a3f0c ip 7f6c4449df27 sp 7fff81b0fca8 error 6 in libprotobuf.so.7.0.0[7f6c4445f000+ed000] Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = /usr/local/lib: InstallationDate: Installed on 2013-05-20 (234 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True Package: chromium-browser 31.0.1650.63-0ubuntu0.13.10.1~20131204.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-22 (79 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1267293/+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 1313188] Re: chromium forgets opened tabs between sessions
*** This bug is a duplicate of bug 1312601 *** https://bugs.launchpad.net/bugs/1312601 ** This bug has been marked a duplicate of bug 1312601 Chromium is reordering and losing tabs acroos restarts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1313188 Title: chromium forgets opened tabs between sessions Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: I have chromium remember my tabs between sessions. Since chromium 24 it forgets some of them from one session to another. I use multiple chromium profile/users and frequently leave multiple tabs open in one (work) profile and close it over the weekend, leaving another (personal) profile open. When Monday morning comes around I open the work profile and discover tabs missing. I just tested it and had more than 20 tabs open previously, closed and re-opened and found 18, next I had 15 then 10 on each restart. To reproduce Open chromium and set settings to "On start-up" -> "Continue where you left off" open a bunch of tabs, noting how many are open. close chromium Re-open chromium Note fewer tabs open. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu2 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: Sat Apr 26 21:19:46 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2012-06-29 (665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-01-20 (96 days ago) chromium-default: CHROMIUM_FLAGS="" . /usr/lib/pepflashplugin-installer/pepflashplayer.sh gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-01-12T14:42:24.250431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1313188/+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 1231857] Re: [DPMS] Display backlight turns back on almost immediately after being turned off
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) 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/1231857 Title: [DPMS] Display backlight turns back on almost immediately after being turned off Status in Mir: Fix Released Status in The Ubuntu Power Consumption Project: Fix Committed Status in XMir: Triaged Status in “mir” package in Ubuntu: Triaged Status in “xorg-server” package in Ubuntu: Triaged Bug description: Display backlight turns back on almost immediately after being turned off. In theory DPMS support has landed in XMir, but it's not really working. TEST CASE: xset dpms force off Expected: Screen turns off and stays off Observed: Screen turns off and then immediately either: (a) turns back on fully; or (b) the backlight turns back on but the screen remains black. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-xmir 2:1.14.2.901-2ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Sep 27 16:25:33 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-06-11 (107 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO 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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Sep 27 16:45:50 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-0 DP-1DP-2 HDMI-0 HDMI-1 HDMI-2 VGA-0 xserver.version: 2:1.14.2.901-2ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1231857/+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 1252646] Re: Empathy showing me as sender of new message in message notification applet instead of original sender
apport information ** Tags added: apport-collected trusty ** Description changed: I've configured Google talk account in Empathy. Sometimes when new message is received, it shows sender as myself in the message notification applet in systembar(I do not know the exact terminology) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 19 13:55:51 2013 ExecutablePath: /usr/bin/empathy MarkForUpload: True SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + NonfreeKernelModules: wl + Package: empathy 3.8.6-0ubuntu9 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 + Tags: trusty + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-04-07 (23 days ago) + UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1252646/+attachment/4101148/+files/Dependencies.txt -- 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/1252646 Title: Empathy showing me as sender of new message in message notification applet instead of original sender Status in “empathy” package in Ubuntu: New Bug description: I've configured Google talk account in Empathy. Sometimes when new message is received, it shows sender as myself in the message notification applet in systembar(I do not know the exact terminology) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 19 13:55:51 2013 ExecutablePath: /usr/bin/empathy MarkForUpload: True SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 NonfreeKernelModules: wl Package: empathy 3.8.6-0ubuntu9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-07 (23 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1252646/+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 1252646] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1252646/+attachment/4101149/+files/ProcEnviron.txt ** Changed in: empathy (Ubuntu) Status: Incomplete => New -- 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/1252646 Title: Empathy showing me as sender of new message in message notification applet instead of original sender Status in “empathy” package in Ubuntu: New Bug description: I've configured Google talk account in Empathy. Sometimes when new message is received, it shows sender as myself in the message notification applet in systembar(I do not know the exact terminology) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 19 13:55:51 2013 ExecutablePath: /usr/bin/empathy MarkForUpload: True SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 NonfreeKernelModules: wl Package: empathy 3.8.6-0ubuntu9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-07 (23 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1252646/+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 1314551] [NEW] Font corruption
Public bug reported: I see the occasional corrupted letters as described in the xserver-xorg- video-intel bugs Bug #1098334 and Bug #1227569 in 14.04 using AMD Radeon R7 graphics hardware with the radeon driver. 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: None CurrentDesktop: GNOME Date: Wed Apr 30 11:09:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0123] InstallationDate: Installed on 2014-04-14 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper A88X-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperA88X-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. 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: Tue Apr 29 09:17:41 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty 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/1314551 Title: Font corruption Status in “xorg” package in Ubuntu: New Bug description: I see the occasional corrupted letters as described in the xserver- xorg-video-intel bugs Bug #1098334 and Bug #1227569 in 14.04 using AMD Radeon R7 graphics hardware with the radeon driver. 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: None CurrentDesktop: GNOME Date: Wed Apr 30 11:09:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0123] InstallationDate: Installed on 2014-04-14 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper A88X-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.as
[Desktop-packages] [Bug 1098334] Re: [gen4 sna] Font corruption
I opened Bug #1314551 for the current AMD version of this behaviour and subscribed Christopher to it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1098334 Title: [gen4 sna] Font corruption Status in X.org xf86-video-intel: In Progress Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Bug description: After enabling the SNA acceleration method and rebooting, I noticed that graphical glitches appeared in the letters on Chromium's tab bar during the mouse hover animation. I've attached a screenshot illustrating this, particularly with the letter "g" in the screenshot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 10 16:00:55 2013 InstallationDate: Installed on 2012-09-24 (107 days ago) InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.2) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2012-09-25 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1098334/+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 1055874] Re: Automatic sleep settings are not followed precisely
This bug was fixed in the package gnome-settings-daemon - 3.4.2-0ubuntu0.6.6 --- gnome-settings-daemon (3.4.2-0ubuntu0.6.6) precise; urgency=low * debian/patches/fix-suspend-and-blanking-time.patch - Make suspend and blanking time followed gsettings precisely, fix suspend and blanking time related to idle-dim-time issue. (LP: #1055874) -- Jian-Ding Chen (timchen119)Mon, 11 Nov 2013 14:12:28 +0800 ** Changed in: gnome-settings-daemon (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Precise: Confirmed Status in “gnome-settings-daemon” source package in Precise: Fix Released Bug description: [Impact] According to the current design in Ubuntu Precise, users can choose the suspend time and blank time in the gnome control center (system settings). However, there's another gsetting called "org.gnome .settings-daemon.plugins.power idle-dim-time" which controls the screen dim time. The default value of idle-dim-time in Ubuntu is 30 secs and this makes the screen dim after idle for 30 secs. This part (idle-dim-time) is not accessible to users in the default UI but can only be accessed by using the CLI. This two categories of values (dim time/suspend&blank time) should not be related at all, however, the current Ubuntu Precise (12.04)'s gnome settings daemon (3.4.2) it actually suspend or blank the screen on "user set time plus the dim time", which added additional 30 secs by default. Since dim time is not accessible by users in default UI, this confusing users why extra 30 secs is added to the total time on top of the selected suspend/blank time. In some OEM projects, in order to fulfill the OEM requests for Energy Star standard, the dim time is set to 5 minutes default (instead of 30 secs), and this make the suspend time and screen blank time very inaccurate, because user will have additional 5 minutes to wait before the screen blank or system suspend. (Inactive time to suspend is about 5 minutes more than setting.) * User do not need modify anything for this patch. [Test Case] * Please use Ubuntu Precise (12.04) to test, this issue is already fixed in Ubuntu Raring (13.04) * Set idle-dim-time to 300 first (5 minutes), it's much easier to find out this issue. (the default is 30 secs and it's somehow not as easy to observe, but the result should be same.) Command: #gsettings set org.gnome.settings-daemon.plugins.power idle-dim-time 300 *In settings: Turn screen off: 10 minutes Suspend: 10 minutes on battery power, 30 minutes when plugged in. Actual: On battery: Screen turned off after 10 minutes, suspend after about 5 more minutes(15 minutes total). When plugged in: Screen turned off after 10 minutes, suspend after about 25 more minutes(35 minutes total). Steps: 1. Check power settings and brightness settings 2. Leave the system inactive Expected results: Inactive time to suspend is same as setting Actual results: Inactive time to suspend is about 5 minutes more than setting [Regression Potential] * This do not need to modify any user settings. * The impact should be minimal for an inaccurate timing of suspend/blanking. [Other Info] Original bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion
[Desktop-packages] [Bug 1055874] Update Released
The verification of the Stable Release Update for gnome-settings-daemon 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 gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Precise: Confirmed Status in “gnome-settings-daemon” source package in Precise: Fix Released Bug description: [Impact] According to the current design in Ubuntu Precise, users can choose the suspend time and blank time in the gnome control center (system settings). However, there's another gsetting called "org.gnome .settings-daemon.plugins.power idle-dim-time" which controls the screen dim time. The default value of idle-dim-time in Ubuntu is 30 secs and this makes the screen dim after idle for 30 secs. This part (idle-dim-time) is not accessible to users in the default UI but can only be accessed by using the CLI. This two categories of values (dim time/suspend&blank time) should not be related at all, however, the current Ubuntu Precise (12.04)'s gnome settings daemon (3.4.2) it actually suspend or blank the screen on "user set time plus the dim time", which added additional 30 secs by default. Since dim time is not accessible by users in default UI, this confusing users why extra 30 secs is added to the total time on top of the selected suspend/blank time. In some OEM projects, in order to fulfill the OEM requests for Energy Star standard, the dim time is set to 5 minutes default (instead of 30 secs), and this make the suspend time and screen blank time very inaccurate, because user will have additional 5 minutes to wait before the screen blank or system suspend. (Inactive time to suspend is about 5 minutes more than setting.) * User do not need modify anything for this patch. [Test Case] * Please use Ubuntu Precise (12.04) to test, this issue is already fixed in Ubuntu Raring (13.04) * Set idle-dim-time to 300 first (5 minutes), it's much easier to find out this issue. (the default is 30 secs and it's somehow not as easy to observe, but the result should be same.) Command: #gsettings set org.gnome.settings-daemon.plugins.power idle-dim-time 300 *In settings: Turn screen off: 10 minutes Suspend: 10 minutes on battery power, 30 minutes when plugged in. Actual: On battery: Screen turned off after 10 minutes, suspend after about 5 more minutes(15 minutes total). When plugged in: Screen turned off after 10 minutes, suspend after about 25 more minutes(35 minutes total). Steps: 1. Check power settings and brightness settings 2. Leave the system inactive Expected results: Inactive time to suspend is same as setting Actual results: Inactive time to suspend is about 5 minutes more than setting [Regression Potential] * This do not need to modify any user settings. * The impact should be minimal for an inaccurate timing of suspend/blanking. [Other Info] Original bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25
[Desktop-packages] [Bug 1048131] 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/1048131 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Released Status in “unity-greeter” source package in Quantal: Triaged Status in “unity-greeter” source package in Saucy: Triaged Bug description: [Impact] Unity Greeter can crash when X clients create X windows. This results in Ubuntu going to failsafe mode. When an X window appears Unity Greeter receives a Map event. Unity Greeter attempts to get a GdkWindow object for the window in the event. If the window was destroyed before it does this it gets a NULL pointer. Unity Greeter did not check for this case. [Test Case] This is a bug that only occurs if windows rapidly appear and disappear. Can be verified on machines that are exhibiting the problem (perhaps linked to indicators failing to start). Check errors.ubuntu.com shows problem does not occur when fix applied. [Errors Bucket] https://errors.ubuntu.com/bucket/?id=/usr/sbin/unity-greeter%3A11%3Agdk_window_get_type_hint%3Aunity_greeter_focus_upon_map%3A_unity_greeter_focus_upon_map_gdk_filter_func%3Agdk_event_apply_filters%3Agdk_event_source_translate_event [Regression Potential] Low, the change just checks for the NULL pointer and ignores the map event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1048131/+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 1048131] Re: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()
This bug was fixed in the package unity-greeter - 0.2.9-0ubuntu1.3 --- unity-greeter (0.2.9-0ubuntu1.3) precise; urgency=medium * debian/patches/dont-focus-destroyed-window.patch: - Handle a window being destroyed after we get the map event and try and focus it (LP: #1048131) -- Robert AncellWed, 09 Apr 2014 13:58:13 +1200 ** Changed in: unity-greeter (Ubuntu Precise) 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/1048131 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Released Status in “unity-greeter” source package in Quantal: Triaged Status in “unity-greeter” source package in Saucy: Triaged Bug description: [Impact] Unity Greeter can crash when X clients create X windows. This results in Ubuntu going to failsafe mode. When an X window appears Unity Greeter receives a Map event. Unity Greeter attempts to get a GdkWindow object for the window in the event. If the window was destroyed before it does this it gets a NULL pointer. Unity Greeter did not check for this case. [Test Case] This is a bug that only occurs if windows rapidly appear and disappear. Can be verified on machines that are exhibiting the problem (perhaps linked to indicators failing to start). Check errors.ubuntu.com shows problem does not occur when fix applied. [Errors Bucket] https://errors.ubuntu.com/bucket/?id=/usr/sbin/unity-greeter%3A11%3Agdk_window_get_type_hint%3Aunity_greeter_focus_upon_map%3A_unity_greeter_focus_upon_map_gdk_filter_func%3Agdk_event_apply_filters%3Agdk_event_source_translate_event [Regression Potential] Low, the change just checks for the NULL pointer and ignores the map event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1048131/+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 1314549] [NEW] USB-headset undetected by Phonon
You have been subscribed to a public bug: A previously working USB-headset, which has been working flawlessly on Kubuntu 12.04 has ceased to work consistently on 14.04, whenever I try to connect it. While lsusb lists the device as being present and recognised, the Device Preference pane in the Audio and Video Settings of KDE keeps displaying the device in a greyed out state. In other words, it would appear that phonon thinks the device is still missing. Thus, it cannot be used. This problem occurs most of the times when I connect the headset to any USB port, even directly to the motherboard. Only rarely does Phonon wake up to the returned device. What I expected to happen was that, after the low-level handshake on the USB bus, Phonon would pop up a notification that it is switching to the headset because it´s higher on my preferences. (As it did consistently, prior to the upgrade from 12.04.) Instead, there is no announcement whatsoever. Also, the Select Master Channel window of KMix does not list the headset. I am running Kubuntu 14.04 LTS. The package is version 4:4.13.0-0ubuntu1, which is the current package available from the repositories. Please note that I am not entirely sure at this time wether kde-runtime is the correct package. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: kde-runtime 4:4.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 30 10:58:25 2014 ExecutablePath: /usr/bin/kcmshell4 InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Kubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140205) ProcEnviron: LANGUAGE=en_GB PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: kde-runtime UpgradeStatus: Upgraded to trusty on 2014-04-27 (2 days ago) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- USB-headset undetected by Phonon https://bugs.launchpad.net/bugs/1314549 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. -- 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 1314556] [NEW] Unable to mount Android MTP device
Public bug reported: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) ** Affects: gvfs (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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device Status in “gvfs” package in Ubuntu: New Bug description: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+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 1313885] Re: lock screen bypass
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.1 --- unity (7.2.0+14.04.20140423-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: lock screen bypass (LP: #1313885) - debian/patches/lp1313885.patch: improve lockscreen logic in lockscreen/LockScreenController.cpp, lockscreen/LockScreenShield.*, plugins/unityshell/src/unityshell.*. -- Marc DeslauriersMon, 28 Apr 2014 22:29:13 -0400 ** Changed in: unity (Ubuntu Utopic) Status: In Progress => Fix Released -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: Fix Released Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.1 --- unity (7.2.0+14.04.20140423-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: lock screen bypass (LP: #1313885) - debian/patches/lp1313885.patch: improve lockscreen logic in lockscreen/LockScreenController.cpp, lockscreen/LockScreenShield.*, plugins/unityshell/src/unityshell.*. -- Marc DeslauriersMon, 28 Apr 2014 22:29:13 -0400 ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1290717]
Hi ! (sorry for my bad english)
it'sn't solved forum after upgrade 4.12 to 4.13.
these is the konsole result :
jajax@portable:~$ akonadictl start
Starting Akonadi Server...
done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
jajax@portable:~$ search paths: ("/usr/lib/lightdm/lightdm",
"/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin",
"/usr/games", "/usr/local/games", "/usr/sbin", "/usr/local/sbin",
"/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec",
"/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontableOK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelationOK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
mysql.columns_priv OK
mysql.db OK
mysql.eventOK
mysql.func OK
mysql.general_log OK
mysql.help_categoryOK
mysql.help_keyword OK
mysql.help_relationOK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.servers OK
mysql.slow_log OK
mysql.tables_priv OK
mysql.time_zoneOK
mysql.time_zone_leap_secondOK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_typeOK
mysql.user OK
MySQL version OK (required "5.1" , available "5.5" )
Database "akonadi" opened using driver "QMYSQL"
DbInitializer::run()
checking table "SchemaVersionTable"
checking table "ResourceTable"
checking table "CollectionTable"
checking table "MimeTypeTable"
checking table "PimItemTable"
checking table "FlagTable"
checking table "PartTypeTable"
checking table "PartTable"
checking table "CollectionAttributeTable"
checking table "TagTable"
checking table "TagAttributeTable"
checking table "TagRemoteIdResourceRelationTable"
checking table "PimItemFlagRelation"
checking table "PimItemTagRelation"
checking table "CollectionMimeTypeRelation"
checking table "CollectionPimItemRelation"
DbInitializer::run() done
skipping update 2
skipping update 3
skipping update 4
skipping update 8
skipping update 10
skipping update 12
skipping update 13
skipping update 14
skipping update 15
skipping update 16
skipping update 17
skipping update 18
skipping update 19
skipping update 20
skipping update 21
skipping update 22
skipping update 23
skipping update 24
skipping update 25
skipping update 26
Adding new foreign key constraints
"ALTER TABLE CollectionTable ADD FOREIGN KEY (parentId) REFERENCES
CollectionTable(id) ON UPDATE CASCADE ON DELETE CASCADE"
Updating index failed:
Sql error: Cannot add or update a child row: a foreign key constraint fails
(`akonadi`.`#sql-a49_1b`, CONSTRAINT `#sql-a49_1b_ibfk_1` FOREIGN KEY
(`parentId`) REFERENCES `collectiontable` (`id`) ON DELETE CASCADE ON UPDATE
CASCADE) QMYSQL: Unable to execute query
Query: ALTER TABLE CollectionTable ADD FOREIGN KEY (parentId) REFERENCES
CollectionTable(id) ON UPDATE CASCADE ON DELETE CASCADE
""
Unable to initialize database.
"[
0: akonadiserver() [0x805d455]
1: akonadiserver() [0x805d6e1]
2: [0xb76fc400]
3: [0xb76fc424]
4: /lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb6d99aff]
5: /lib/i386-linux-gnu/libc.so.6(abort+0x143) [0xb6d9d083]
6:
/usr/lib/i386-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x123)
[0xb7448d53]
7: akonadiserver() [0x805f524]
8: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xc8)
[0xb74ed
[Desktop-packages] [Bug 1290717]
jajaX, your problem is unrelated to this one, please open a new report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1290717 Title: akonadi 1.11.80 fails to start Status in Akonadi - The PIM Storage Service: Fix Released Status in “akonadi” package in Ubuntu: Triaged Status in “akonadi” source package in Trusty: Fix Released Status in “akonadi” source package in Utopic: Fix Committed Bug description: [Impact] installations that used to be trusty and went through akonadi 1.11.80 (early beta upgrades to 14.04) have a broken database adding a fix for these broken setups as per upstream request. [Test Case] * have a broken akonadi and upgrade OR * install 14.04 alpha * login and setup mails * upgrade akonadi to [1] * logout and login again, observe akonadi being broken * upgrade to final+proposed * akonadi should be repaired [1] https://launchpad.net/ubuntu/+source/akonadi/1.11.80-0ubuntu3 [Regression Potential] N/A [Other Info] N/A -- akonadi fails to start since the update from 1.11.0 to 1.11.80 Full description in upstream bug report: https://bugs.kde.org/show_bug.cgi?id=331867 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1290717/+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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.1 --- unity (7.2.0+14.04.20140423-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: lock screen bypass (LP: #1313885) - debian/patches/lp1313885.patch: improve lockscreen logic in lockscreen/LockScreenController.cpp, lockscreen/LockScreenShield.*, plugins/unityshell/src/unityshell.*. -- Marc DeslauriersMon, 28 Apr 2014 22:29:13 -0400 ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been "locked to launcher", (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including "Files". To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select "Lock to Launcher" Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+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 1290717]
ok, no problem. sorry ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1290717 Title: akonadi 1.11.80 fails to start Status in Akonadi - The PIM Storage Service: Fix Released Status in “akonadi” package in Ubuntu: Triaged Status in “akonadi” source package in Trusty: Fix Released Status in “akonadi” source package in Utopic: Fix Committed Bug description: [Impact] installations that used to be trusty and went through akonadi 1.11.80 (early beta upgrades to 14.04) have a broken database adding a fix for these broken setups as per upstream request. [Test Case] * have a broken akonadi and upgrade OR * install 14.04 alpha * login and setup mails * upgrade akonadi to [1] * logout and login again, observe akonadi being broken * upgrade to final+proposed * akonadi should be repaired [1] https://launchpad.net/ubuntu/+source/akonadi/1.11.80-0ubuntu3 [Regression Potential] N/A [Other Info] N/A -- akonadi fails to start since the update from 1.11.0 to 1.11.80 Full description in upstream bug report: https://bugs.kde.org/show_bug.cgi?id=331867 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1290717/+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 1314549] Re: USB-headset undetected by Phonon
device states are used from pulseaudio IIRC. ** Package changed: kde-runtime (Ubuntu) => pulseaudio (Ubuntu) -- 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/1314549 Title: USB-headset undetected by Phonon Status in “pulseaudio” package in Ubuntu: New Bug description: A previously working USB-headset, which has been working flawlessly on Kubuntu 12.04 has ceased to work consistently on 14.04, whenever I try to connect it. While lsusb lists the device as being present and recognised, the Device Preference pane in the Audio and Video Settings of KDE keeps displaying the device in a greyed out state. In other words, it would appear that phonon thinks the device is still missing. Thus, it cannot be used. This problem occurs most of the times when I connect the headset to any USB port, even directly to the motherboard. Only rarely does Phonon wake up to the returned device. What I expected to happen was that, after the low-level handshake on the USB bus, Phonon would pop up a notification that it is switching to the headset because it´s higher on my preferences. (As it did consistently, prior to the upgrade from 12.04.) Instead, there is no announcement whatsoever. Also, the Select Master Channel window of KMix does not list the headset. I am running Kubuntu 14.04 LTS. The package is version 4:4.13.0-0ubuntu1, which is the current package available from the repositories. Please note that I am not entirely sure at this time wether kde-runtime is the correct package. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: kde-runtime 4:4.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 30 10:58:25 2014 ExecutablePath: /usr/bin/kcmshell4 InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Kubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140205) ProcEnviron: LANGUAGE=en_GB PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: kde-runtime UpgradeStatus: Upgraded to trusty on 2014-04-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1314549/+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 133921] Re: Evolution address book has no place for SIP number
** Changed in: evolution Status: New => Invalid -- 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/133921 Title: Evolution address book has no place for SIP number Status in The Evolution Mail & Calendaring Tool: Invalid Status in “evolution” package in Ubuntu: Invalid Bug description: The address book in Evolution has no placeholder for a SIP number. As it is, the closest thing to a SIP number placeholder is "Video Chat" on the "Personal information" tab. I can't see that surviving well during syncs with devices which support a proper "SIP" or "Internet telephone" field. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/133921/+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 1304404] Re: The inability to create a connection through Huawei E3531
** Changed in: network-manager Status: Unknown => Incomplete ** Changed in: network-manager Importance: Unknown => Medium -- 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/1304404 Title: The inability to create a connection through Huawei E3531 Status in NetworkManager: Incomplete Status in “network-manager” package in Ubuntu: Confirmed Bug description: If you create access to the Internet using usb modem ZTE MF667 then the network periodically breaks. Usb Modem Huawei E3531 network- manager doesn't see, so you cannot create any connection. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 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 CurrentDesktop: Unity Date: Tue Apr 8 16:49:01 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-06 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140405) IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 10.39.225.164 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: ** (process:23293): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/2: uid 1000 has no permission to perform this operation ** (process:23293): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceModem. RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1304404/+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 1304404] Re: Periodic breaks in communication (modem ZTE MF 667)
** Summary changed: - The inability to create a connection through Huawei E3531 + Periodic breaks in communication (modem ZTE MF 667) ** Description changed: If you create access to the Internet using usb modem ZTE MF667 then the - network periodically breaks. Usb Modem Huawei E3531 network-manager - doesn't see, so you cannot create any connection. + network periodically breaks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 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 CurrentDesktop: Unity Date: Tue Apr 8 16:49:01 2014 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2014-04-06 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140405) IpRoute: - default via 10.64.64.64 dev ppp0 proto static - 10.64.64.64 dev ppp0 proto kernel scope link src 10.39.225.164 + default via 10.64.64.64 dev ppp0 proto static + 10.64.64.64 dev ppp0 proto kernel scope link src 10.39.225.164 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=false - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=false + WWANEnabled=true + WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: - ** (process:23293): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/2: uid 1000 has no permission to perform this operation - - ** (process:23293): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceModem. - RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN - running 0.9.8.8connected enabled enabled disabled enabled enabled + ** (process:23293): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/2: uid 1000 has no permission to perform this operation + + ** (process:23293): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceModem. + RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN + running 0.9.8.8connected enabled enabled disabled enabled enabled -- 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/1304404 Title: Periodic breaks in communication (modem ZTE MF 667) Status in NetworkManager: Incomplete Status in “network-manager” package in Ubuntu: Confirmed Bug description: If you create access to the Internet using usb modem ZTE MF667 then the network periodically breaks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 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 CurrentDesktop: Unity Date: Tue Apr 8 16:49:01 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-06 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140405) IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 10.39.225.164 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: ** (process:23293): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/2: uid 1000 has no permission to perform this operation ** (process:23293): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceModem. RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1304404/+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 1308105] Re: Xfce resets TV mode to NULL when power cycled
This issue also affects Gigabyte GA-EG45M-UD2H motherboard with Intel GMA X4500HD integrated graphics. Fresh install of mythbuntu 14.04. 13.10 was not affected. -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “xfce4-settings” package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1013881] Re: Right-Ctrl key broken on French OSS keyboard
Bonjour, moi aussi je préfère que ma touche rctrl (Control R) se comporte comme une touche Control, et non comme level5_machin_chose. Merci d'avance, alex Hello, so would I rather my rctrl key to behave as a control key. Thanks, alex -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Bug description: Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key of the keyboard has ceased to work. The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 2.5-1ubuntu1.2. If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Sat Jun 16 00:16:09 2012 Dependencies: DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader MachineType: LENOVO 4243E69 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243E69 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4243E69 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 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.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+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 1313283] Re: gedit always prints in black and white on color printer
Moving to gedit, as gedit sends the job data already in black and white regardless of that the printer is color. ** Package changed: cups (Ubuntu) => gedit (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1313283 Title: gedit always prints in black and white on color printer Status in “gedit” package in Ubuntu: Incomplete Bug description: gedit shows syntax highlighting (with default Classic color scheme) properly, yet prints/previews text as black-and-white for a color printer (Xerox Phaser 6180DN in this case). Before 14.04 it used to print properly in color. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 27 03:47:14 2014 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-04-03 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1313283/+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 1297421] Re: Sound stops working occasionally on Latitude E7440
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1297421 Title: Sound stops working occasionally on Latitude E7440 Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Sound stops(and starts) working from time to time with no definitive cause, it usually doesn't happen while something is playing so this makes it harder to find the cause. It happened once after resume from suspend(STR), restarting fixed it. Another time it happened after unplugging the AC adapter and turning on the hardware WiFi button, suspending to RAM and resuming fixed it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.219 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 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Mar 25 19:23:29 2014 InstallationDate: Installed on 2014-03-18 (6 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1297421/+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 1310976] Re: LTS 14.04 after change desktop - cant control system
Im using linux since 1998 asshole ! After using GNOME PANEL all desktops are empty and all desktops are "glass desks". There is only one possibility - go to terminal and reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1310976 Title: LTS 14.04 after change desktop - cant control system Status in “gnome-panel” package in Ubuntu: Incomplete Bug description: I start gnome-panel under UBUNTU 14.04 LTS. I have 4 desktops. When I click by mouse any desktop on gnome-panel, new desktop appear but whole overlay of system goes to background -> on small 2x2 panel icon I can see open apps, but all desktops where empty. Also when I click any icon it doesn to anything. SUPER+S works - I can change desktops, but I didnt see any previous open application //and cant do nothing in X. CTRL+ALT+Backspace also doesnt work. Only way how to solve that problem is go to terminal and restart system. I really need gnome panel for fast switchng between apps &&& To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1310976/+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 1310976] Re: LTS 14.04 after change desktop - cant control system
gnome-panel --replace *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1310976 Title: LTS 14.04 after change desktop - cant control system Status in “gnome-panel” package in Ubuntu: Incomplete Bug description: I start gnome-panel under UBUNTU 14.04 LTS. I have 4 desktops. When I click by mouse any desktop on gnome-panel, new desktop appear but whole overlay of system goes to background -> on small 2x2 panel icon I can see open apps, but all desktops where empty. Also when I click any icon it doesn to anything. SUPER+S works - I can change desktops, but I didnt see any previous open application //and cant do nothing in X. CTRL+ALT+Backspace also doesnt work. Only way how to solve that problem is go to terminal and restart system. I really need gnome panel for fast switchng between apps &&& To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1310976/+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 1297421] Re: Sound stops working occasionally on Latitude E7440
I've been suffering with this problem too, though I've also been suffering with it in 13.10. -- 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/1297421 Title: Sound stops working occasionally on Latitude E7440 Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Sound stops(and starts) working from time to time with no definitive cause, it usually doesn't happen while something is playing so this makes it harder to find the cause. It happened once after resume from suspend(STR), restarting fixed it. Another time it happened after unplugging the AC adapter and turning on the hardware WiFi button, suspending to RAM and resuming fixed it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.219 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 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Mar 25 19:23:29 2014 InstallationDate: Installed on 2014-03-18 (6 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1297421/+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 1292398] Re: multi-monitor : second screen position isn't saved from one session to another
Same Problem on Gubuntu 14.04 64 bits. Also change with nvidia x server settings (safe to xorg.conf) does not help. -- 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/1292398 Title: multi-monitor : second screen position isn't saved from one session to another Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 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: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1292398/+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 1314539] Re: gs crashed with SIGSEGV in TrioWriteDouble()
Please follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems. Also attach your printer's PPD file (from /etc/cups/ppd/) to this bug report. Attach all files one by one, do not compress them and do not package them together. ** Information type changed from Private to Public ** Changed in: ghostscript (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1314539 Title: gs crashed with SIGSEGV in TrioWriteDouble() Status in “ghostscript” package in Ubuntu: Incomplete Bug description: Since Trusty i have problems with my printer. I is attached to my second machine, public shared and added at this machine. But every time i want to print there is an second printer (the same=duplicate) and only this one works/prints! I do not know if this is interesting for the bug report or not... Today, i got this crash while using "the wrong" (installed) printer, switching to the other=same it works... ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ghostscript 9.10~dfsg-0ubuntu10 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 Date: Wed Apr 30 10:42:18 2014 ExecutablePath: /usr/bin/gs InstallationDate: Installed on 2014-03-16 (44 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225) Lpstat: device for FS-1030D: dnssd://Kyocera%20FS-1030D%20%40%20xubuntu2._printer._tcp.local/ device for Kyocera-FS-1030D: ipps://xubuntu2.local:631/printers/Kyocera-FS-1030D MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H Papersize: a4 PpdFiles: FS-1030D: Kyocera FS-1030D ProcCmdline: gs -q -dNOPAUSE -dBATCH -dSAFER -sDEVICE=ps2write -sOUTPUTFILE=%stdout -dLanguageLevel=3 -r600 -dCompressPages=false -dCompressFonts=false -dNoT3CCITT -dNOINTERPOLATE -c save\ pop -f /tmp/00f425365c86f ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=325b49b2-158d-45a6-81b1-2d4351757330 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fad0470c1fe:movsbl 0x0(%rbp,%rdx,1),%esi PC (0x7fad0470c1fe) ok source "0x0(%rbp,%rdx,1)" (0x7fac84825f00) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ghostscript StacktraceTop: ?? () from /usr/lib/libgs.so.9 trio_vsprintf () from /usr/lib/libgs.so.9 gs_sprintf () from /usr/lib/libgs.so.9 pprintg1 () from /usr/lib/libgs.so.9 pprintg2 () from /usr/lib/libgs.so.9 Title: gs crashed with SIGSEGV in trio_vsprintf() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1314539/+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 1314539] Re: gs crashed with SIGSEGV in TrioWriteDouble()
And make sure to do the tests with the print queue with which Ghostscript crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1314539 Title: gs crashed with SIGSEGV in TrioWriteDouble() Status in “ghostscript” package in Ubuntu: Incomplete Bug description: Since Trusty i have problems with my printer. I is attached to my second machine, public shared and added at this machine. But every time i want to print there is an second printer (the same=duplicate) and only this one works/prints! I do not know if this is interesting for the bug report or not... Today, i got this crash while using "the wrong" (installed) printer, switching to the other=same it works... ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ghostscript 9.10~dfsg-0ubuntu10 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 Date: Wed Apr 30 10:42:18 2014 ExecutablePath: /usr/bin/gs InstallationDate: Installed on 2014-03-16 (44 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225) Lpstat: device for FS-1030D: dnssd://Kyocera%20FS-1030D%20%40%20xubuntu2._printer._tcp.local/ device for Kyocera-FS-1030D: ipps://xubuntu2.local:631/printers/Kyocera-FS-1030D MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H Papersize: a4 PpdFiles: FS-1030D: Kyocera FS-1030D ProcCmdline: gs -q -dNOPAUSE -dBATCH -dSAFER -sDEVICE=ps2write -sOUTPUTFILE=%stdout -dLanguageLevel=3 -r600 -dCompressPages=false -dCompressFonts=false -dNoT3CCITT -dNOINTERPOLATE -c save\ pop -f /tmp/00f425365c86f ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=325b49b2-158d-45a6-81b1-2d4351757330 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fad0470c1fe:movsbl 0x0(%rbp,%rdx,1),%esi PC (0x7fad0470c1fe) ok source "0x0(%rbp,%rdx,1)" (0x7fac84825f00) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ghostscript StacktraceTop: ?? () from /usr/lib/libgs.so.9 trio_vsprintf () from /usr/lib/libgs.so.9 gs_sprintf () from /usr/lib/libgs.so.9 pprintg1 () from /usr/lib/libgs.so.9 pprintg2 () from /usr/lib/libgs.so.9 Title: gs crashed with SIGSEGV in trio_vsprintf() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1314539/+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 1222970] Re: layout options gone from keyboard preferences
** Changed in: gnome-control-center Status: New => Won't Fix -- 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/1222970 Title: layout options gone from keyboard preferences Status in GNOME Control Center: Won't Fix Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: The icon that looks like it might mean "keyboard options" is greyed out (the one with the screwdriver icon). See screenshot ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu34 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 9 21:35:04 2013 MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1222970/+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 1314581] [NEW] package libcuda1-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package
Public bug reported: i was just trying to change GPU driver from noveau to nVidia one cause of system freezes ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libcuda1-331-updates (not installed) 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 Date: Wed Apr 30 12:36:58 2014 DuplicateSignature: package:libcuda1-331-updates:(not installed):trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 ErrorMessage: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 InstallationDate: Installed on 2014-04-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: nvidia-graphics-drivers-331-updates Title: package libcuda1-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check package-conflict trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1314581 Title: package libcuda1-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux- gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: i was just trying to change GPU driver from noveau to nVidia one cause of system freezes ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libcuda1-331-updates (not installed) 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 Date: Wed Apr 30 12:36:58 2014 DuplicateSignature: package:libcuda1-331-updates:(not installed):trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 ErrorMessage: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 InstallationDate: Installed on 2014-04-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: nvidia-graphics-drivers-331-updates Title: package libcuda1-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1314581/+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 1311263] Re: shortcut key does not work after rehabilitation
1) Pretty much for the bug of "shortcut" I went to change the settings in system setup, keyboard shortcuts, audio, and media and I changed the shortcuts in the Volume Down button lowers audio volume to F11, then I changed the shortcut volume up key and the F12 key and change succeeded! after I tried to get back with before and I returned the keys F11 and F12 in previous years but no longer worked ... after a request to the forum recommended me a command and is back to normal, then I have not changed keys. 2) I just wanted to come back as before and I did it with the command "gsettings reset-recursively org.gnome.settings- daemon.plugins.media-keys" 3) I have succeeded with the command gsettings reset-recursively org.gnome.settings-daemon.plugins.media-keys -- 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/1311263 Title: shortcut key does not work after rehabilitation Status in “unity-control-center” package in Ubuntu: Incomplete Bug description: to make a test I changed the shortcut keys from the volume up and volume down to F11 and f12 but when I reset the first buttons they have not worked more ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 22 20:33:03 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-20 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: PATH=(custom, no user) LANGUAGE=it_IT XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) 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/1311263/+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 1246272] Re: Keyboard layout changing randomly
The workaround from #21 does not work for me too. I think I found a way to reproduce the bug. - I use two layouts, US and TR - other layout options: - - `switch to next source using: Shift + Super L` - - `switch to previous source using: Shift + Ctrl + Super L` - - `allow different sources for each window` - - `new windows use the default source` (EN is the default source) - I change layout to secondary layout ( TR in my case ) - everything is normal until I `alt+tab` to another window - then the layout goes back to US - If i rapidly press `alt + tab` between two windows the keyboard layout randomly switches between US and TR -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1246272 Title: Keyboard layout changing randomly Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps changing from pt_br to what I think is en_us. It seems random so I don't know what trigger this, but sometimes just alt-tabbing is enough to mess with keyboard layout in one of the windows. I already removed the en_us from my keyboard sources, double checked the use of one source for all windows, and even removed accelerators to switch between layouts but none have worked. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 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 Architecture: amd64 Date: Wed Oct 30 09:12:48 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-20 (163 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 1311263] Re: shortcut key does not work after rehabilitation
There is another problem, however, a second problem: the pop-up sound that should come out when I raise the volume does not come out as well as those of twitter and facebook ... I will in this case I just upgraded from the cd version to version 12:04 14:04 and is updated when these pop-ups do not appear right, are those of this photo https://encrypted-tbn2.google.com/images?q=tbn:ANd9GcTBuicYUPqlyVgdHC648uIdbgjnayadGQbZzHIxcA1uxlzbOGDt but then again this is another problem! if I have to open another bug that I have to add messages to "ubuntu-bug "? I have no idea. -- 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/1311263 Title: shortcut key does not work after rehabilitation Status in “unity-control-center” package in Ubuntu: Incomplete Bug description: to make a test I changed the shortcut keys from the volume up and volume down to F11 and f12 but when I reset the first buttons they have not worked more ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 22 20:33:03 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-20 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: PATH=(custom, no user) LANGUAGE=it_IT XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) 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/1311263/+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 1314582] [NEW] Missing definition of N5321GW in 77-mm-ericsson-mbm.rules
Public bug reported:
Lenovo thinkpad X240 (and as far as i know, t440, t540 and so on) has a
new(er?) wwan card.
i need to add this to /lib/udev/rules.d/77-mm-ericsson-mbm.rules to get it
working.
ATTRS{idVendor}=="0bdb", ATTRS{idProduct}=="193e", ENV{ID_MM_ERICSSON_MBM}="1"
Without that line it's brought up with a ppp interface instead of using
the "wwan0" directly (and the modem seems to crash).
I'm reporting this bug over 3g now, has been stable for about an hour
since the change.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: modemmanager 1.0.0-2ubuntu1 [modified:
lib/udev/rules.d/77-mm-ericsson-mbm.rules]
Uname: Linux 3.13.5-031305-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 30 12:39:35 2014
InstallationDate: Installed on 2014-02-20 (68 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to trusty on 2014-04-30 (0 days ago)
** Affects: modemmanager (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 modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1314582
Title:
Missing definition of N5321GW in 77-mm-ericsson-mbm.rules
Status in “modemmanager” package in Ubuntu:
New
Bug description:
Lenovo thinkpad X240 (and as far as i know, t440, t540 and so on) has
a new(er?) wwan card.
i need to add this to /lib/udev/rules.d/77-mm-ericsson-mbm.rules to get it
working.
ATTRS{idVendor}=="0bdb", ATTRS{idProduct}=="193e", ENV{ID_MM_ERICSSON_MBM}="1"
Without that line it's brought up with a ppp interface instead of
using the "wwan0" directly (and the modem seems to crash).
I'm reporting this bug over 3g now, has been stable for about an hour
since the change.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: modemmanager 1.0.0-2ubuntu1 [modified:
lib/udev/rules.d/77-mm-ericsson-mbm.rules]
Uname: Linux 3.13.5-031305-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 30 12:39:35 2014
InstallationDate: Installed on 2014-02-20 (68 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to trusty on 2014-04-30 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1314582/+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 1314581] Re: package libcuda1-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package l
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1314581 Title: package libcuda1-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux- gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: i was just trying to change GPU driver from noveau to nVidia one cause of system freezes ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libcuda1-331-updates (not installed) 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 Date: Wed Apr 30 12:36:58 2014 DuplicateSignature: package:libcuda1-331-updates:(not installed):trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 ErrorMessage: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 InstallationDate: Installed on 2014-04-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: nvidia-graphics-drivers-331-updates Title: package libcuda1-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libcuda.so.331.38', which is also in package libcuda1-331 331.38-0ubuntu7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1314581/+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 1013881] Re: Right-Ctrl key broken on French OSS keyboard
By the way, with this modification, the drawing around line 120 in/usr/share/X11/xkb/symbols/fr is wrong because it shows a keyboard with a Ctrl key on the right, not a Level5 thing... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Bug description: Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key of the keyboard has ceased to work. The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 2.5-1ubuntu1.2. If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Sat Jun 16 00:16:09 2012 Dependencies: DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader MachineType: LENOVO 4243E69 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243E69 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4243E69 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 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.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+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 1013881] Re: Right-Ctrl key broken on French OSS keyboard
Give us back - please - the right control key acting the same as left control key. http://forum.ubuntu-fr.org/viewtopic.php?id=1563071 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Bug description: Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key of the keyboard has ceased to work. The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 2.5-1ubuntu1.2. If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Sat Jun 16 00:16:09 2012 Dependencies: DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader MachineType: LENOVO 4243E69 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243E69 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4243E69 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 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.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+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 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card
first of all, make sure to remove the bumblebee packages with sudo apt- get --purge remove Then please attach your /var/log/Xorg.0.log, dmesg, and your /var/log /gpu-manager.log. ** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Incomplete -- 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/1310023 Title: 14.04: Nvidia Prime is unable to switch to the Nvidia card Status in “nvidia-prime” package in Ubuntu: Incomplete Bug description: I did a fresh install of 14.04 the day it was released. I use a XPS 15z laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia Geforce GT 525M). Booting doesn't work out of the box, but by setting GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor dell_laptop.backlight=0 quiet splash" in /etc/default/grub it works. acpi=off when installing, removed that from the grub file when installed. I expected that the Prime feature introduced in kernel 3.12 (kernel 3.13.x here) would let me switch between the Intel and Nvidia cards as i like, instead of using Bumblebee, which doesn't work properly with everything. I've installed and tried both the nvidia-331 and nvidia-304 drivers. Exactly the same result from both. Attempting to switch to the Nvidia card in nvidia-settings (tried on almost all of the drivers available, including 331.38) resulted in an error message, in a new window, with no text. prime-switch in terminal gives this output: Segmentation fault (core dumped) Sudoing the process gives no output at all. No graphical performance boost either, still the Intel card... sudo prime-select nvidia gives this output: Error: alternatives are not set up properly Error: nvidia mode can't be enabled I've also tried Bumblebee (not PPA) a few times, but it's also unable to switch. I'm able to use the Intel card temporary, but I would really like to be able to use the full power of my computer... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-prime 0.6.2 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: Sat Apr 19 20:52:42 2014 InstallationDate: Installed on 2014-04-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+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 1310568] Re: ubuntu-drivers-common fails to find any Drivers for my graphics card (jockey-text does)
Please attach the output of the following command: lspci -n ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310568 Title: ubuntu-drivers-common fails to find any Drivers for my graphics card (jockey-text does) Status in “ubuntu-drivers-common” package in Ubuntu: Incomplete Bug description: Had this problem since I change motherboards recently, the system gui and the terminal fail to find drivers to use with my system. On the old motherboard this worked without issue. I did have an Asus P8Z77-V Pro to an AsRock Z77 Extreme4 (same chipset and general features) I see that jockey-common is an old package in 14.04 so I am stuck on 13.10 until I can use ubuntu-drivers-common to find my system drivers. 'jockey-text -l' output: noki@grandslam:~$ jockey-text -l kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in use) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) noki@grandslam:~$ 'ubuntu-drivers list' output: noki@grandslam:~$ ubuntu-drivers list noki@grandslam:~$ This all works fine on my second PC, and my laptop using the same various version of Ubuntu (from 13 to 14) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-drivers-common 1:0.2.83 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 Date: Mon Apr 21 11:59:39 2014 InstallationDate: Installed on 2014-03-05 (46 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310568/+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 1304404] Re: Periodic breaks in communication (modem ZTE MF 667)
Created a separate report on Huawei E3531 here - https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1308895 -- 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/1304404 Title: Periodic breaks in communication (modem ZTE MF 667) Status in NetworkManager: Incomplete Status in “network-manager” package in Ubuntu: Confirmed Bug description: If you create access to the Internet using usb modem ZTE MF667 then the network periodically breaks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 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 CurrentDesktop: Unity Date: Tue Apr 8 16:49:01 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-06 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140405) IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 10.39.225.164 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: ** (process:23293): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/2: uid 1000 has no permission to perform this operation ** (process:23293): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceModem. RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1304404/+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 1309773] Re: Nameless error when switching to NVidia graphics card from Nvidia settings using PRIME profiles on Lenovo IdeaPad y580
Please attach the output of dmesg and your /var/log/gpu-manager.log ** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Incomplete -- 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/1309773 Title: Nameless error when switching to NVidia graphics card from Nvidia settings using PRIME profiles on Lenovo IdeaPad y580 Status in “nvidia-prime” package in Ubuntu: Incomplete Bug description: Hello, Y580 is an optimus laptop. I have installed nvidia prime and are using binary driver 331.38. I open NVidia settings and choose to switch from Intel card to NVidia one. When I do so (and enter my password), I get an empty error message box and the display gets back to Intel card. The console prints just this: "astral@Lenovo-IdeaPad-Y580:~$ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ERROR: " ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-prime 0.6.2 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: Sat Apr 19 00:08:37 2014 InstallationDate: Installed on 2014-04-05 (13 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140405) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1309773/+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 1314587] [NEW] Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04
Public bug reported: Steps to reproduce: * Minimize current window or alt-tab between windows * Reveal launcher to click on application * Click `Super` to bring up Dash * Hold `Super` to bring up Keyboard Shortcuts What should happen: Action completes smoothly and quickly. What happens instead: * Action may be slow / animation jerky. * Action may stall (animation frozen on given frame, e.g. window partially minimized) - initiating another action cancels first action and second action may succeed (most often calling Guake with F12 seems to solve the issue) * Action may freeze - cursor no longer moves - a soft reboot (Alt+PrtScr+REISUB) usually works, otherwise a hard reboot Notes: * Not application specific. Minimizing is reliably slow/stalls with minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, but I use those programs more often. * I am using an Nvidia Optimus machine with the default Nouveau driver - no `nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia driver (including `nvidia-prime`) and it made no difference. * I did not experience this issue on the same machine running 13.10 (with Bumblebee). * I am running Maximus. 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 30 12:53:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. 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: Wed Apr 30 12:03:43 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) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Windows slow/stall/freeze when minimizing/restoring/etc + Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. Matching subscriptions: dp-unity
[Desktop-packages] [Bug 1310233] Re: prime-select failing to switch due to error: /usr/lib32/nvidia-331/vdpau/libvdpau_nvidia.so.1 does not exists
Those are just warnings. It must be something else. Please reproduce the problem and attach the following: 1) the tarball created by "sudo nvidia-bug-report.sh" 2) your /var/log/gpu-manager.log ** Changed in: nvidia-prime (Ubuntu) Status: New => Incomplete -- 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/1310233 Title: prime-select failing to switch due to error: /usr/lib32/nvidia-331/vdpau/libvdpau_nvidia.so.1 does not exists Status in “nvidia-prime” package in Ubuntu: Incomplete Bug description: Updated from 13.10 to 14.04 then did "apt-get purge nvidia-* bumblebee* primus* bbswitch-dkms". Then installed "apt-get install nvidia-331 nvidia-prime" Now getting this trying to switch to nvidia with prime-select :~$ sudo prime-select nvidia update-alternatives: using /usr/lib/nvidia-331/ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode update-alternatives: warning: skip creation of /usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file /usr/lib32/nvidia-331/vdpau/libvdpau_nvidia.so.1 (of link group i386-linux-gnu_gl_conf) doesn't exist update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so because associated file /usr/lib32/nvidia-331/vdpau/libvdpau_nvidia.so (of link group i386-linux-gnu_gl_conf) doesn't exist update-alternatives: using /usr/lib/nvidia-331/alt_ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode If I use nvidia-settings to switch, then Xorg fails to start with this: (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please (EE) NVIDIA(0): check your system's kernel log for additional error (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the (EE) NVIDIA(0): README for additional information. (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! Info: :~$ dpkg -l | grep -i nvidia ii bbswitch-dkms 0.7-2ubuntu1i386 Interface for toggling the power on nVidia Optimus video cards ii libcuda1-331 331.38-0ubuntu7 i386 NVIDIA CUDA runtime library rc libcuda1-331-updates 331.38-0ubuntu7 i386 NVIDIA CUDA runtime library ii nvidia-331 331.38-0ubuntu7 i386 NVIDIA binary driver - version 331.38 ii nvidia-libopencl1-331 331.38-0ubuntu7 i386 NVIDIA OpenCL Driver and ICD Loader library ii nvidia-opencl-icd-331 331.38-0ubuntu7 i386 NVIDIA OpenCL ICD ii nvidia-prime 0.6.2 i386 Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 i386 Tool for configuring the NVIDIA graphics driver :~$ uname -a Linux plankton 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310233/+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 1309716] Re: ubuntu-drivers list returns nothing
What should it return? (any particular device I should be looking at?) Also please attach the output of "lspci -vvv" ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1309716 Title: ubuntu-drivers list returns nothing Status in “ubuntu-drivers-common” package in Ubuntu: Incomplete Bug description: ╭─quintasan@frelia ~ ‹ruby-2.1.1› ╰─$ ubuntu-drivers list ╭─quintasan@frelia ~ ‹ruby-2.1.1› ╰─$ ╭─quintasan@frelia ~ ‹ruby-2.1.1› ╰─$ ubuntu-drivers debug === log messages from detection === DEBUG:root:Loading custom detection plugin /usr/share/ubuntu-drivers-common/detect/open-vm-dkms.py DEBUG:root:plugin /usr/share/ubuntu-drivers-common/detect/open-vm-dkms.py return value: None DEBUG:root:Loading custom detection plugin /usr/share/ubuntu-drivers-common/detect/sl-modem.py DEBUG:root:plugin /usr/share/ubuntu-drivers-common/detect/sl-modem.py return value: None DEBUG:root:Loading custom detection plugin /usr/share/ubuntu-drivers-common/detect/arm-gles.py DEBUG:root:plugin /usr/share/ubuntu-drivers-common/detect/arm-gles.py return value: None === modaliases in the system === usb:v8087p0024ddc09dsc00dp01ic09isc00ip00in00 acpi:LNXPOWER: acpi:ACPI0003: usb:v04F2pB2DAd0518dcEFdsc02dp01ic0Eisc02ip00in01 input:b0019vp0006e-e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw platform:dock input:b0011v0001p0001eAB54-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D,7E,7F,80,8C,8E,8F,9B,9C,9D,9E,9F,A3,A4,A5,A6,AC,AD,B7,B8,B9,D9,E2,ram4,l0,1,2,sfw wmi:2651D9FD-911C-4B69-B94E-D0DED5963BD7 input:b0011v0002p0007e01B1-e0,1,3,k110,111,145,14A,14D,14E,ra0,1,18,1C,2F,35,36,39,mlsfw platform:thinkpad_hwmon pci:v8086d0166sv17AAsd21F4bc03sc00i00 input:b0011v0002p000Ae-e0,1,2,k110,111,112,r0,1,amlsfw acpi:PNP0C02: acpi:PNP0200: usb:v1949p0004d0100dc00dsc00dp00ic08isc06ip50in00 acpi:PNP: pci:v8086d0154sv17AAsd21F3bc06sc00i00 pci:v8086d1502sv17AAsd21F3bc02sc00i00 acpi:LNXSYSTM: platform:iTCO_wdt acpi:PNP0103: pci:v8086d1E3Asv17AAsd21F3bc07sc80i00 acpi:LNXIOBAY: pci:v8086d0085sv8086sd1311bc02sc80i00 wmi:74F1EBB6-927A-4C7D-95DF-698E21E80EB5 serio:ty01pr00id00ex00 acpi:PNP0C04: usb:v0A5Cp21E6d0112dcFFdsc01dp01icFFisc01ip01in01 wmi:8ADB159E-1E32-455C-BC93-308A7ED98246 wmi:E2BE5EE3-42DA-49DB-8378-1F5247388202 wmi:7FF47003-3B6C-4E5E-A227-E979824A85D1 wmi:98479A64-33F5-4E33-A707-8E251EBBC3A1 x86cpu:vendor::family:0006:model:003A:feature:,,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0075,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0093,0094,0095,0097,0098,0099,009A,009B,009C,009D,009E,00C0,00E0,00E1,00E3,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104,0120,0127,0129 input:b0019v17AAp5054e4101-e0,1,4,5,k71,72,73,8E,94,98,BE,BF,C2,CD,D4,E0,E1,E3,E4,EC,EE,F0,174,1D2,1DB,1DC,ram4,lsfw3, pci:v1180dE822sv17AAsd21F3bc08sc80i01 acpi:LNXVIDEO: acpi:LEN0015:PNP0F13: wmi:6A4B54EF-A5ED-4D33-9455-B0D9B48DF4B3 acpi:SMO1200:PNP0C31: input:bvpe-e0,5,kramlsfw2, platform:regulatory usb:v0A5Cp21E6d0112dcFFdsc01dp01icFEisc01ip01in03 wmi:FCB424F1-075A-4E0E-BFC4-62F3E71771FA platform:vboxdrv pci:v8086d1E03sv17AAsd21F3bc01sc06i01 hid:b0003g0001v09DAp000E pci:v8086d1E31sv17AAsd21F3bc0Csc03i30 input:b0019vp0003e-e0,1,k8E,ramlsfw usb:v1D6Bp0002d0313dc09dsc00dp01ic09isc00ip00in00 acpi:PNP0303:PNP0303: acpi:PNP0B00: usb:v1D6Bp0002d0313dc09dsc00dp00ic09isc00ip00in00 usb:v0A5Cp21E6d0112dcFFdsc01dp01icFFiscFFipFFin02 input:b0003v04F2pB2DAe0518-e0,1,kD4,ramlsfw input:b0019vp0001e-e0,1,k74,ramlsfw platform:microcode wmi:7364651A-132F-4FE7-ADAA-40C6C7EE2E3B acpi:PNP0C0F: acpi:LNXCPU: platform:pcspkr acpi:PNP0A08:PNP0A03: usb:v09DAp000Ed0001dc00dsc00dp00ic03isc01ip02in00 dmi:bvnLENOVO:bvrG1ET99WW(2.59):bd11/13/2013:svnLENOVO:pn234452G:pvrThinkPadT430:rvnLENOVO:rn234452G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: wmi:7EEF04FF-4328-447C-B5BB-D449925D538D wmi:05901221-D566-11D1-B2F0-00A0C9062910 usb:v04F2pB2DAd0518dcEFdsc02dp01ic0Eisc01ip00in00 pci:v8086d1E20sv17AAsd21F3bc04sc03i00 wmi:51F5230E-9677-46CD-A1CF-C0B23EE34DB7 serio:ty05pr00id00ex00 acpi:PNP0800: platform:thinkpad_acpi usb:v147Ep2020d0001dc00dsc00dp00icFFisc00ip00in00 input:b0003v09DAp000Ee0110-e0,1,2,4,k110,111,112,113,114,115,116,117,r0,1,8,9,am4,lsfw platform:coretemp wmi:7430019A-DCE9-4548-BAB0-9FDE0935CAFF usb:v0A
[Desktop-packages] [Bug 1292209] Re: Locking screen does not work in case of fullscreen gnome-terminal
It happened again now (up-to-date 14.04 LTS now): screen started to fade out after pressing CTRL-ALT-L, then it stuck in the middle of process, I can move the mouse, but I can't do anything neither with mouse or keyboard. What helped: switching to text console (CTRL-ALT-F1) login, then killing gnome-terminal. After that, I can switch back to X.org (ALT-F7) and I see the unlock screen now. However of course this is not an ideal solution, and I lost all of my (tons of ...) gnome-terminal windows. Again: it seems it happens sometimes, if I press CTRL-ALT-L when I have a fullscreen (not maximized, but full screen) gnome-terminal on the current workspace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292209 Title: Locking screen does not work in case of fullscreen gnome-terminal Status in “gnome-screensaver” package in Ubuntu: New Bug description: Somewhat odd situation. If I use CTRL-ALT-L to lock my session, it normally works as expected. However if there is a fullscreen gnome- terminal (F11) was on the screen, CTRL-ALT-L does something interesting: it begins fade the screen but it's left in a middle state, no way to unlock but also it's not locked visually though I can't type anymore. More interestingly: it seems the screen IS locked, since if I type my password "blindly" (I still see the half faded session ...) I get back my desktop in a usable state! Interesting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 21:25:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292209/+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 1304285] Re: nm-connection-editor crashed with SIGSEGV while importing OpenVPN settings
** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => High ** Changed in: network-manager-applet (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1304285 Title: nm-connection-editor crashed with SIGSEGV while importing OpenVPN settings Status in “network-manager-applet” package in Ubuntu: Confirmed Status in “network-manager-applet” source package in Trusty: Confirmed Bug description: While trying to import OpenVPN parameters for new connection, nm- connection-editor crashes, even trying to import just exported parameters. $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ LANG=C apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu5 Candidate: 0.9.8.8-0ubuntu5 Version table: *** 0.9.8.8-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status $ LANG=C apt-cache policy network-manager-openvpn network-manager-openvpn: Installed: 0.9.8.2-1ubuntu4 Candidate: 0.9.8.2-1ubuntu4 Version table: *** 0.9.8.2-1ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Apr 8 13:14:44 2014 ExecutablePath: /usr/bin/nm-connection-editor InstallationDate: Installed on 2014-04-02 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326) IpRoute: default via 10.0.0.254 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.20 metric 1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/bin/nm-connection-editor --show --type vpn SegvAnalysis: Segfault happened at: 0x96d01e0: add%eax,(%eax) PC (0x096d01e0) in non-executable VMA region: 0x09598000-0x09962000 rw-p [heap] source "%eax" ok destination "(%eax)" (0x096d01e0) ok SegvReason: executing writable VMA [heap] Signal: 11 SourcePackage: network-manager-applet Stacktrace: #0 0x096d01e0 in ?? () No symbol table info available. #1 0x6168732f in ?? () No symbol table info available. StacktraceTop: ?? () ?? () Title: nm-connection-editor crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Проводное соединение 28d297b58-66f3-43d3-9e86-f01c083fabbf 802-3-ethernet1396939672 Вт. 08 апр. 2014 10:47:52 yes no /org/freedesktop/NetworkManager/Settings/2 Проводное соединение 13834e2d7-deba-4471-9794-288cc0878c2d 802-3-ethernet1396948373 Вт. 08 апр. 2014 13:12:53 yes no /org/freedesktop/NetworkManager/Settings/1 ADWL 92f9a2f5-d071-486a-a659-16ea4d0fdf0b 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless disconnected /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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1304285/+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 1314335] Re: duplicity backup reports an unknown failure during backup
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1314335
Title:
duplicity backup reports an unknown failure during backup
Status in “duplicity” package in Ubuntu:
Confirmed
Bug description:
Ubuntu 14.04 (freshly installed).
The backup (continous backup from my 12.04 installation) did not finish
correctly
and reported the following unknown error.
I deleted all existing backup files and restarted a fresh backup in another
location -> i receive the same error message.
My backup destination is a local FTP server (NAS)
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1337, in main
do_backup(action)
File "/usr/bin/duplicity", line 1458, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 542, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 424, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
145, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
171, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 423, in
async_waiters.append(io_scheduler.schedule_task(lambda tdp,
dest_filename, vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 314, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 145, in put
self.copy_file('put', source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 321, in
iterate
% (n, e.__class__.__name__, str(e)))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 26:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: duplicity 0.6.23-1ubuntu4
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: Tue Apr 29 20:12:59 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-04-18 (11 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1314335/+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 1314551] Re: Font corruption
Florian Hars, did this problem not occur in a release prior to Trusty? ** Tags added: bios-outdated-f7 ** Summary changed: - Font corruption + 1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption ** Description changed: - I see the occasional corrupted letters as described in the xserver-xorg- - video-intel bugs Bug #1098334 and Bug #1227569 in 14.04 using AMD Radeon - R7 graphics hardware with the radeon driver. + I see the occasional corrupted letters in 14.04 using AMD Radeon R7 + graphics hardware with the radeon driver. 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: None CurrentDesktop: GNOME Date: Wed Apr 30 11:09:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller]) -Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0123] + Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller]) + Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0123] InstallationDate: Installed on 2014-04-14 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper A88X-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperA88X-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. 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: Tue Apr 29 09:17:41 2014 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu1 xserver.video_driver: radeon ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1314551 Title: 1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption Status in “xorg” package in Ubuntu: Incomplete Bug description: I see the occasional corrupted letters in 14.04 using AMD Radeon R7 graphics hardware with the radeon driver. 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: None CurrentDesktop: GNOME Date: Wed Apr 30 11:09:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0123] InstallationDate: Installed on 2014-04-14 (15 days ago) InstallationMedia: Ub
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot
the independent headphone control and device 2 would not be created if you disable it by hint or revert this patch https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_via.c?id=139611705ad5ce7b35b8b7957c5ca406deb3ff9b your screen capture indicate that your hint apply to wrong controller -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot Status in “alsa-driver” package in Ubuntu: New Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313904/+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 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04
Issue still occurs when Maximus is not running. -- 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/1314587 Title: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04 Status in “unity” package in Ubuntu: New Status in “xorg” package in Ubuntu: New Bug description: Steps to reproduce: * Minimize current window or alt-tab between windows * Reveal launcher to click on application * Click `Super` to bring up Dash * Hold `Super` to bring up Keyboard Shortcuts What should happen: Action completes smoothly and quickly. What happens instead: * Action may be slow / animation jerky. * Action may stall (animation frozen on given frame, e.g. window partially minimized) - initiating another action cancels first action and second action may succeed (most often calling Guake with F12 seems to solve the issue) * Action may freeze - cursor no longer moves - a soft reboot (Alt+PrtScr+REISUB) usually works, otherwise a hard reboot Notes: * Not application specific. Minimizing is reliably slow/stalls with minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, but I use those programs more often. * I am using an Nvidia Optimus machine with the default Nouveau driver - no `nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia driver (including `nvidia-prime`) and it made no difference. * I did not experience this issue on the same machine running 13.10 (with Bumblebee). * I am running Maximus. 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 30 12:53:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. 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: Wed Apr 30 12:03:43 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) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1304285] Re: nm-connection-editor crashed with SIGSEGV while importing OpenVPN settings
** Also affects: network-manager-applet (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: network-manager-applet (Ubuntu Trusty) Importance: Undecided => High ** Changed in: network-manager-applet (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1304285 Title: nm-connection-editor crashed with SIGSEGV while importing OpenVPN settings Status in “network-manager-applet” package in Ubuntu: Confirmed Status in “network-manager-applet” source package in Trusty: Confirmed Bug description: While trying to import OpenVPN parameters for new connection, nm- connection-editor crashes, even trying to import just exported parameters. $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ LANG=C apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu5 Candidate: 0.9.8.8-0ubuntu5 Version table: *** 0.9.8.8-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status $ LANG=C apt-cache policy network-manager-openvpn network-manager-openvpn: Installed: 0.9.8.2-1ubuntu4 Candidate: 0.9.8.2-1ubuntu4 Version table: *** 0.9.8.2-1ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Apr 8 13:14:44 2014 ExecutablePath: /usr/bin/nm-connection-editor InstallationDate: Installed on 2014-04-02 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326) IpRoute: default via 10.0.0.254 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.20 metric 1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/bin/nm-connection-editor --show --type vpn SegvAnalysis: Segfault happened at: 0x96d01e0: add%eax,(%eax) PC (0x096d01e0) in non-executable VMA region: 0x09598000-0x09962000 rw-p [heap] source "%eax" ok destination "(%eax)" (0x096d01e0) ok SegvReason: executing writable VMA [heap] Signal: 11 SourcePackage: network-manager-applet Stacktrace: #0 0x096d01e0 in ?? () No symbol table info available. #1 0x6168732f in ?? () No symbol table info available. StacktraceTop: ?? () ?? () Title: nm-connection-editor crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Проводное соединение 28d297b58-66f3-43d3-9e86-f01c083fabbf 802-3-ethernet1396939672 Вт. 08 апр. 2014 10:47:52 yes no /org/freedesktop/NetworkManager/Settings/2 Проводное соединение 13834e2d7-deba-4471-9794-288cc0878c2d 802-3-ethernet1396948373 Вт. 08 апр. 2014 13:12:53 yes no /org/freedesktop/NetworkManager/Settings/1 ADWL 92f9a2f5-d071-486a-a659-16ea4d0fdf0b 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless disconnected /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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1304285/+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 1314028] Re: Graphical glitches with SNA enabled on Intel graphics
** Package changed: pidgin (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1314028 Title: Graphical glitches with SNA enabled on Intel graphics Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Operating System: Xubuntu 14.04 (Update from 13.10) CPU: Intel Celeron 847 1,1GHz RAM: 4GB Graphics: Intel HD Graphics 2000 Steps to reproduce the issue: - Open multiple windows on seperate workspaces. - Switch between windows via Alt+Tab. Expected Result: Application windows are rendered correctly, there are no visible graphical glitches. Actual Result: There are graphical glithes where the active window is only rendered partially, e.g. switching from Thunderbird to Chromium leads to a mixture of both applications. When hovering the mouse pointer over elements, those are updated and rendered correctly. The same effect may happen when minimizing / maximizing windows. Workaraound: Instead of using SNA, fall back to UXA rendering mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1314028/+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 1314588] [NEW] [Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is distorted/glitchy (works fine on Ubuntu)
Public bug reported:
In a relatively new update I was able to get perfect sound - apart from
the small problem at start-up entering in the terminal sudo modprobe
snd-hda-intel (but I'm not dealing with this at hand - it's the fact on
Linux I am unable to get the same result and unsure as to what the
differences could be between the 2 OSs.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-39.57~precise1-generic 3.8.13.20
Uname: Linux 3.8.0-39-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-39-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: click 1776 F xfce4-volumed
click 1840 F xfce4-mixer-plu
click 9057 F pulseaudio
/dev/snd/pcmC0D0p: click 9057 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd83a irq 22'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,102802c6,0014'
Controls : 20
Simple ctrls : 9
CheckboxSubmission: b28292d9736b63e07bf0e621c9299c39
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Wed Apr 30 12:17:08 2014
InstallationMedia: Linux Lite 1.0.8 32-bit - Release i386
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: **
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.asset.tag: **
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd10/27/2009:svnDellInc.:pnInspiron1010:pvrA11:rvnDellInc.:rn**:rvrA11:cvnDellInc.:ct8:cvrA11:
dmi.product.name: Inspiron 1010
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-30T11:54:34.233547
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise
--
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/1314588
Title:
[Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is
distorted/glitchy (works fine on Ubuntu)
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
In a relatively new update I was able to get perfect sound - apart
from the small problem at start-up entering in the terminal sudo
modprobe snd-hda-intel (but I'm not dealing with this at hand - it's
the fact on Linux I am unable to get the same result and unsure as to
what the differences could be between the 2 OSs.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-39.57~precise1-generic 3.8.13.20
Uname: Linux 3.8.0-39-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-39-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: click 1776 F xfce4-volumed
click 1840 F xfce4-mixer-plu
click 9057 F pulseaudio
/dev/snd/pcmC0D0p: click 9057 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd83a irq 22'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,102802c6,0014'
Controls : 20
Simple ctrls : 9
CheckboxSubmission: b28292d9736b63e07bf0e621c9299c39
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Wed Apr 30 12:17:08 2014
In
[Desktop-packages] [Bug 1041790]
*** Bug 77974 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 xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0" run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1311176] Re: crash deja-dup backup ascii' codec can't decode byte 0xc3
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => Fix Committed
** Changed in: duplicity
Milestone: None => 0.6.24
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1311176
Title:
crash deja-dup backup ascii' codec can't decode byte 0xc3
Status in Duplicity - Bandwidth Efficient Encrypted Backup:
Fix Committed
Status in “duplicity” package in Ubuntu:
Confirmed
Bug description:
I didn't change anything, it worked fine. I updated to Ubuntu 14.04 from
13.10 where this backup worked without problem.
I didn't write or erase any data in the backuped folder.
Here is the output :
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1337, in main
do_backup(action)
File "/usr/bin/duplicity", line 1469, in do_backup
check_last_manifest(col_stats) # not needed for full backup
File "/usr/bin/duplicity", line 1170, in check_last_manifest
last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 190,
in check_manifests
remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224,
in get_remote_manifest
manifest_buffer = self.backend.get_data(self.remote_manifest_name)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 646, in
get_data
fin = self.get_fileobj_read(filename, parseresults)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 607, in
get_fileobj_read
self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 151, in get
self.copy_file('get', source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 321, in
iterate
% (n, e.__class__.__name__, str(e)))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3:
ordinal not in range(128)
I don't understand : I'm saving datas from a ext4 to a ext4. Maybe a
problem while crypting it ? Sorry I don't know many things about it.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: duplicity 0.6.23-1ubuntu4
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.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 22 17:04:10 2014
InstallationDate: Installed on 2014-04-10 (11 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140410)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1311176/+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 1314592] [NEW] System Settings window is too small, cannot resize
Public bug reported: After system upgrade to Ubuntu 14.04, this problem has happened: System Settings window is too small. I cannot see any options in this window, no icons, nothing. I cannot adjust any settings right now. Moreover, the window cannot be re-sized or maximized. I cannot even see "About ubuntu" window, because it is the same "System Settings" window which is too small. "lsb_release -rd" gave me output: Description:Ubuntu 14.04 LTS Release:14.04 "apt-cache policy unity-control-center" gave me this output: unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 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: Wed Apr 30 13:25:38 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-10 (19 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-04-22 (7 days ago) modified.conffile..etc.xdg.menus.unitycc.menu: [deleted] 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: amd64 apport-bug trusty ** Attachment added: "This is how the window looks like" https://bugs.launchpad.net/bugs/1314592/+attachment/4101279/+files/Screenshot%20from%202014-04-30%2013%3A33%3A57.png -- 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/1314592 Title: System Settings window is too small, cannot resize Status in “unity-control-center” package in Ubuntu: New Bug description: After system upgrade to Ubuntu 14.04, this problem has happened: System Settings window is too small. I cannot see any options in this window, no icons, nothing. I cannot adjust any settings right now. Moreover, the window cannot be re-sized or maximized. I cannot even see "About ubuntu" window, because it is the same "System Settings" window which is too small. "lsb_release -rd" gave me output: Description: Ubuntu 14.04 LTS Release: 14.04 "apt-cache policy unity-control-center" gave me this output: unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 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: Wed Apr 30 13:25:38 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-10 (19 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-04-22 (7 days ago) modified.conffile..etc.xdg.menus.unitycc.menu: [deleted] 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/1314592/+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 1314588] Re: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is distorted/glitchy (works fine on Ubuntu)
I just looked at the problem for what I posted and it may be a slight
unclear.
Cracking/stuttering/glitchy audio on Linux Lite
Ubuntu 12.04 update fixed the same problem
Unable to transfer success to Linux.
--
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/1314588
Title:
[Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is
distorted/glitchy (works fine on Ubuntu)
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
In a relatively new update I was able to get perfect sound - apart
from the small problem at start-up entering in the terminal sudo
modprobe snd-hda-intel (but I'm not dealing with this at hand - it's
the fact on Linux I am unable to get the same result and unsure as to
what the differences could be between the 2 OSs.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-39.57~precise1-generic 3.8.13.20
Uname: Linux 3.8.0-39-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-39-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: click 1776 F xfce4-volumed
click 1840 F xfce4-mixer-plu
click 9057 F pulseaudio
/dev/snd/pcmC0D0p: click 9057 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd83a irq 22'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,102802c6,0014'
Controls : 20
Simple ctrls : 9
CheckboxSubmission: b28292d9736b63e07bf0e621c9299c39
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Wed Apr 30 12:17:08 2014
InstallationMedia: Linux Lite 1.0.8 32-bit - Release i386
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: **
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.asset.tag: **
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd10/27/2009:svnDellInc.:pnInspiron1010:pvrA11:rvnDellInc.:rn**:rvrA11:cvnDellInc.:ct8:cvrA11:
dmi.product.name: Inspiron 1010
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-30T11:54:34.233547
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1314588/+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 1289288] Re: duplicity crashed with UnicodeDecodeError in done_with_mount(): 'ascii' codec can't decode byte 0xc3 in position 4: ordinal not in range(128)
** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Status: New => Fix Committed ** Changed in: duplicity Milestone: None => 0.6.24 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1289288 Title: duplicity crashed with UnicodeDecodeError in done_with_mount(): 'ascii' codec can't decode byte 0xc3 in position 4: ordinal not in range(128) Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Committed Status in “duplicity” package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy duplicity duplicity: Installiert: 0.6.23-1ubuntu2 Installationskandidat: 0.6.23-1ubuntu2 Versionstabelle: *** 0.6.23-1ubuntu2 0 500 http://ftp-stud.hs-esslingen.de/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Expected behaviour: Exit gracefully when no network connection to the storage server can be established. Actual behaviour: duplicity crashes ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: duplicity 0.6.23-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 7 07:18:14 2014 ExecutablePath: /usr/bin/duplicity InstallationDate: Installed on 2011-06-21 (989 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python2.7 ProcCmdline: /usr/bin/python /usr/bin/duplicity cleanup --force smb://user@10.3.2.1/data/backup/torfbook2 --gio --no-encryption --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/home/username/.cache/deja-dup --tempdir=/home/username/.cache/deja-dup/tmp --log-fd=13 PythonArgs: ['/usr/bin/duplicity', 'cleanup', '--force', 'smb://user@10.3.2.1/data/backup/torfbook2', '--gio', '--no-encryption', '--verbosity=9', '--gpg-options=--no-use-agent', '--archive-dir=/home/username/.cache/deja-dup', '--tempdir=/home/username/.cache/deja-dup/tmp', '--log-fd=13'] SourcePackage: duplicity Title: duplicity crashed with UnicodeDecodeError in done_with_mount(): 'ascii' codec can't decode byte 0xc3 in position 4: ordinal not in range(128) Traceback: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", line 107, in done_with_mount % str(e), log.ErrorCode.connection_failed) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 4: ordinal not in range(128) UpgradeStatus: Upgraded to trusty on 2014-01-30 (36 days ago) UserGroups: adm admin audio cdrom dialout dip disk fax fuse libvirtd lpadmin netdev plugdev pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1289288/+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 1313966] Re: duplicity cannot back up files from Russian file directory
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Milestone: None => 0.6.24
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1313966
Title:
duplicity cannot back up files from Russian file directory
Status in Duplicity - Bandwidth Efficient Encrypted Backup:
Fix Committed
Status in “duplicity” package in Ubuntu:
New
Bug description:
[Impact]
Any user of the gio backend in duplicity (used by Deja Dup) backing up
to a directory with utf8 characters in it is unable to complete a
single backup.
[Test Case]
mkdir /tmp/source
echo test > /tmp/source/test
mkdir /tmp/Ж
duplicity --gio --no-encryption /tmp/source file:///tmp/Ж
[Regression Potential]
The patch to fix this mostly affects various exception code paths.
But each one is pretty simple change (just upgrading ascii to
unicode).
[Original Report]
After upgrading to Ubuntu 14.04 from 13.10, Duplicity cannot backup
files. The location it will backup and the location to backup have
both Russian characters in path. I believe this is the reason of the
problem.
After failure, duplicity shows this log:
--
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1337, in main
do_backup(action)
File "/usr/bin/duplicity", line 1470, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 637, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 424, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
145, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
171, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 423, in
async_waiters.append(io_scheduler.schedule_task(lambda tdp,
dest_filename, vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 314, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 145, in put
self.copy_file('put', source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 330, in
iterate
return fn(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 130, in copy_file
log.Info(_("Writing %s") % target.get_parse_name())
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 36:
ordinal not in range(128)
---
I believe the related script shall be fixed with "u" prefix, as explained
here:
http://stackoverflow.com/questions/9644099/python-ascii-codec-cant-decode-byte
Ozgur
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: duplicity 0.6.23-1ubuntu4
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
CurrentDesktop: Unity
Date: Tue Apr 29 01:37:39 2014
SourcePackage: duplicity
UpgradeStatus: Upgraded to trusty on 2014-04-18 (10 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1313966/+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 1247736] Re: nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd
** Summary changed: - package ocl-icd-libopencl1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 + nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd ** Also affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-cuda-toolkit (Ubuntu) Status: Confirmed => Invalid ** Changed in: ocl-icd (Ubuntu) Status: Confirmed => Invalid -- 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/1247736 Title: nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd Status in “nvidia-cuda-toolkit” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ocl-icd” package in Ubuntu: Invalid Status in “ocl-icd” package in Debian: New Bug description: Don't know. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: ocl-icd-libopencl1 (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 14:03:41 2013 DpkgTerminalLog: Unpacking ocl-icd-libopencl1:amd64 (from .../ocl-icd-libopencl1_2.0.2-1ubuntu1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/ocl-icd-libopencl1_2.0.2-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 DuplicateSignature: package:ocl-icd-libopencl1:(not installed):trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 InstallationDate: Installed on 2013-10-28 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: ocl-icd Title: package ocl-icd-libopencl1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1247736/+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 1224575] Re: gnome-control-center keyboard no longer has way to modify caps lock key behavior
** Changed in: gnome-control-center Status: New => Won't Fix -- 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/1224575 Title: gnome-control-center keyboard no longer has way to modify caps lock key behavior Status in GNOME Control Center: Won't Fix Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: Up until Raring, it was trivial to use the gnome-control-center to modify caps lock key behavior. In earlier versions you could do the following: - Launch System Settings - Click on Keyboard Layout - Click on Options - These options allow one to modify Caps Lock Key behavior (for example swap it with ESC) In newer versions of Saucy I try to do the following: - Launch System Settings - Click on Keyboard - Click on Layout Settings - Cannot find a location similar to these older options These older 'Keyboard Layout Options' made it very easy to do things like swaping Caps Lock for ESC which make vim users much happier. WORKAROUND == Use gnome-tweak-tool -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Thu Sep 12 11:33:58 2013 InstallationDate: Installed on 2013-09-12 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130912) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224575/+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 1314028] Re: Graphical glitches with SNA enabled on Intel graphics
Can you please attach your Xorg.0.log for reference and a screenshot if possible? Are you still using a plain xfce4 desktop? Compositing settings? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1314028 Title: Graphical glitches with SNA enabled on Intel graphics Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Operating System: Xubuntu 14.04 (Update from 13.10) CPU: Intel Celeron 847 1,1GHz RAM: 4GB Graphics: Intel HD Graphics 2000 Steps to reproduce the issue: - Open multiple windows on seperate workspaces. - Switch between windows via Alt+Tab. Expected Result: Application windows are rendered correctly, there are no visible graphical glitches. Actual Result: There are graphical glithes where the active window is only rendered partially, e.g. switching from Thunderbird to Chromium leads to a mixture of both applications. When hovering the mouse pointer over elements, those are updated and rendered correctly. The same effect may happen when minimizing / maximizing windows. Workaraound: Instead of using SNA, fall back to UXA rendering mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1314028/+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 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot
Finally got it works, thank you! To achive this I had to add a comma to kernel module parameters: options snd-hda-intel patch=,clevo Big thanks to you. -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot Status in “alsa-driver” package in Ubuntu: New Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313904/+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 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot
I filed upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=75151 -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot Status in “alsa-driver” package in Ubuntu: New Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313904/+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 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot
The patch file for my laptop. ** Attachment added: "clevo" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313904/+attachment/4101300/+files/clevo ** Bug watch added: Linux Kernel Bug Tracker #75151 http://bugzilla.kernel.org/show_bug.cgi?id=75151 -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot Status in “alsa-driver” package in Ubuntu: New Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313904/+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 1314592] Re: System Settings window is too small, cannot resize
Sounds like one or more packages are missing. Try sudo apt-get install ubuntu-desktop -- 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/1314592 Title: System Settings window is too small, cannot resize Status in “unity-control-center” package in Ubuntu: New Bug description: After system upgrade to Ubuntu 14.04, this problem has happened: System Settings window is too small. I cannot see any options in this window, no icons, nothing. I cannot adjust any settings right now. Moreover, the window cannot be re-sized or maximized. I cannot even see "About ubuntu" window, because it is the same "System Settings" window which is too small. "lsb_release -rd" gave me output: Description: Ubuntu 14.04 LTS Release: 14.04 "apt-cache policy unity-control-center" gave me this output: unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 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: Wed Apr 30 13:25:38 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-10 (19 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-04-22 (7 days ago) modified.conffile..etc.xdg.menus.unitycc.menu: [deleted] 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/1314592/+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
