[Desktop-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Ass
Looking at the stacktrace, the assertion error happens inside dbus-cpp worker thread that has called core::dbus::Bus::run(). Some quick googling: http://stackoverflow.com/questions/1105745/pthread-mutex-assertion-error ** Also affects: dbus-cpp Importance: Undecided Status: New ** Changed in: dbus-cpp Status: New = Confirmed ** Also affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** Also affects: dbus-cpp (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: dbus-cpp (Ubuntu) Status: New = Confirmed ** Changed in: dbus-cpp (Ubuntu RTM) Status: New = Confirmed ** Changed in: dbus-cpp (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: dbus-cpp (Ubuntu RTM) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: indicator-network (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. Status in DBus C++: Confirmed Status in “dbus-cpp” package in Ubuntu: Confirmed Status in “indicator-network” package in Ubuntu: Invalid Status in “dbus-cpp” package in Ubuntu RTM: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20141015-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988 contains more details. steps to reproduce: (need to trigger race condition) 1. pull down network indicator 2. toggle flight mode on and off quickly a few times 3. click sim card 1 and 2 4. toggle flight mode 5. swipe up close indicators 6. repeat steps 1-5 until crash occurs expected results: no crash happens actual results: Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes. additional info: eventually the bluetooth indicator appears stable in the indicators at the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+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 1181651] Re: ldconfig problem with 64-bit nvidia driver packages
** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Confirmed = Invalid -- 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/1181651 Title: ldconfig problem with 64-bit nvidia driver packages Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Bug description: On Ubuntu 13.04 64-bit, the nvidia-319 package as well as other nvidia driver pakcages (including nvidia-current and nvidia-current-updates from the main ubuntu package repositories) don't play nice with applications that use 32-bit OpenGL libraries. When such an application tries to load the nvidia 32-bit libGL.so library, they don't load the nvidia libGL.so but some other non-nvidia libGL.so. This means a 32-bit application running on Ubuntu Raring 64-bit will never use the nvidia libGL.so library. After a lot of monkey business, I figured out what the problem is. Which libGL.so a 32-bit application uses on a 64-bit system is controlled by the file /etc/ld.so.conf.d/i386-linux-gnu_GL.conf which is just a symlink to /etc/alternatives/i386-linux-gnu_gl_conf which is another symlink to /usr/lib/nvidia-319/alt_ld.so.conf or something similar for other versions of the nvidia drivers. This file is blank in a clean install, so ldconfig doesn't know that 32-bit applications asking for libGL.so should get linked with the version in /usr/lib32/nvidia-319, so it links them with some other version. This breaks 32-bit programs like Steam (which throws a warning about not using direct rendering when it starts up) and 32-bit games like Team Fortress 2 (which fails to start altogether). Of course, this isn't specific to Steam and Team Fortress 2 but will affect any 32-bit program trying to use libGL.so and its associated libraries on a 64-bit machine. fortunately, the fix for this is pretty simple: in the file /usr/lib/nvidia-319/alt_ld.so.conf in the nvidia-319 package add the lines: /usr/lib32/nvidia-319 /usr/lib/nvidia-319 This will tell ldconfig to use the nvidia libGL.so and associated libraries for 32-bit applications. For the other versions of the nvidia driver (such as nvidia-304 and nvidia-304-updates in the main ubuntu repositories) it's a simple matter of replacing nvidia-319 with nvidia-304, nvidia-304-updates, nvidia-313, etc. in the directory names. Although I reported this bug for the nvidia-319 package, I have checked and this bug applies at least to the nvidia-304 and nvidia-304-updates packages for Ubuntu 13.04 amd64 in the main ubuntu package repositories as well. It probably also applies to other nvidia driver packages as well, but I haven't checked those. I suppose all you'd have to look for is a blank /usr/lib/nvidia driver package name/alt_ld.so.conf file to check for the bug. The file I've included is the output of ldd (which prints the dynamic library dependencies of a program) when it's used on a 32-bit program that needs the 32-bit libGL.so on an Ubuntu 13.04 64-bit machine. In this case, the program I used ldd on is the 32-bit version of glxinfo from mesa-utils:i386. The nvidia driver version I had installed when I did this is nvidia-319. However, you will get a very similar result for other nvidia driver versions/packages. Also, I said I don't know for the package because 1.) it affects multiple packages and 2.) it didn't accept the package name nvidia-319. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1181651/+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 1310489] Re: xorg.conf overwritten by booting system
This bug is still affecting me. I have a desktop with two nVidia cards in an SLI configuration. I need a custom xorg.conf to support my 1440p monitor, but my xorg.conf gets renamed to xorg.conf.mmdd almost every reboot. -- 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/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1985
[Desktop-packages] [Bug 610981] Re: Chat not available on Facebook site
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/610981 Title: Chat not available on Facebook site Status in “firefox” package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Normally when I browse Facebook site with Firefox/WinXP I see the chat button in the low right corner of the browser. With FireFox/Lucid I can't see any chat related component. It's a Facebook problem or rendering issue in FF? Gnome 2.30.2 FireFox 3.6.9pre and FireFox 4.03bpre ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.9~hg20100727r34466+nobinonly-0ubuntu1~umd1~lucid ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 CrashDB: ubuntu Date: Wed Jul 28 19:32:17 2010 FirefoxPackages: firefox 3.6.9~hg20100727r34466+nobinonly-0ubuntu1~umd1~lucid firefox-gnome-support 3.6.9~hg20100727r34466+nobinonly-0ubuntu1~umd1~lucid firefox-branding 3.6.9~hg20100727r34466+nobinonly-0ubuntu1~umd1~lucid abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: firefox ThirdParty: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/610981/+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 1373928]
Yesterday, I downloaded LibreOffice from the PPA to test this problem on a 32 bit laptop using Ubuntu 14.04. (Mine was associated with the possibility of the mysql native connector might be the cause of this problem when using MySQL with LibreOffice. (Stefan Gruber and I have been on the LibreOffice user mailing list about it.) Today he gave me a link to this bug. So this evening, I have down the example database and opened it using LibreOffice from the PPA. I saw the following results: 0 foo 42 1 bar 4711 LibreOffice information: Version: 4.3.2.2 Build ID: 430m0(Build: 2) Have they fixed the problem with a newer version of the download file? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1373928 Title: Numeric values are not shown and displayed as 0 Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Bug description: See upstream bug for details: https://bugs.freedesktop.org/show_bug.cgi?id=84315 Numeric are not correctly display and either an empty field or 0 is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1373928/+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 1373928]
I encountered this bug on my opensuse 13.1 system with LO 4.3.2.2 from factory-repo/OBS. Therefore it is not only ubuntu and might be an upstream issue. BTW if I create a simple form within the example database, it will not show any data at all. On an another similar machine the table view of a mysql database showed all text values wrong as 0 (the other way round!) when the form displayed only text fields correctly... LO 4.3.1.2 as it comes with opensuse 13.2 RC1 works properly here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1373928 Title: Numeric values are not shown and displayed as 0 Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Bug description: See upstream bug for details: https://bugs.freedesktop.org/show_bug.cgi?id=84315 Numeric are not correctly display and either an empty field or 0 is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1373928/+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 1373928]
(In reply to Dan Lewis from comment #27) Yesterday, I downloaded LibreOffice from the PPA to test this problem on a 32 bit laptop using Ubuntu 14.04. (Mine was associated with the possibility of the mysql native connector might be the cause of this problem when using MySQL with LibreOffice. (Stefan Gruber and I have been on the LibreOffice user mailing list about it.) Today he gave me a link to this bug. So this evening, I have down the example database and opened it using LibreOffice from the PPA. I saw the following results: 0 foo 42 1 bar 4711 LibreOffice information: Version: 4.3.2.2 Build ID: 430m0(Build: 2) Have they fixed the problem with a newer version of the download file? That display looks correct to me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1373928 Title: Numeric values are not shown and displayed as 0 Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Bug description: See upstream bug for details: https://bugs.freedesktop.org/show_bug.cgi?id=84315 Numeric are not correctly display and either an empty field or 0 is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1373928/+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 1270610] Re: Restore test keeps asking for password even though it is entered properly
I had the same issue in 14.04 last week, too. I am certain that I did not misspell my password as I could decrypt a file from the backup just fine using GPG in Terminal. This week Déjà Dup asked for the password again and this time it worked just fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1270610 Title: Restore test keeps asking for password even though it is entered properly Status in “deja-dup” package in Ubuntu: Confirmed Bug description: See bug report 1270592 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: deja-dup 27.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Sun Jan 19 10:30:03 2014 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2013-10-31 (79 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1270610/+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 657094] Re: Evince when printing a pdf creates strange gapping.
This happens because cairo is putting newline \n characters into the
stream when creating PDF files (before compressing the stream), in an
attempt to do word-wrapping to keep the line size short (I think 72
columns?).
PDFs created like this appear ok on screen in evince, ghostscript etc,
but some printers don't like this - our institution has big Fuji Xerox
machines and these newline characters get turned into several spaces,
which screws up the horizontal spacing at what looks like random
character positions.
For example, here is an extract of a deflated stream from one such PDF
file:
[(M358)-10( )]TJ
-13.196 -1.15 Td
[(The Univ)-6(er)3(s)-4(i)-4(t)-8(y)11( of)-9( W)-3(es)-4(tern Aus)-4(tra\
li)-5(a )]TJ
on screen it looks like
M358
The University of Western Australia
but printed it becomes
M358
The University of Western Australia
The original PDF file doesn't have this, but evince uses libcairo to
create the print data, so the file sent to CUPS has the \\\n added to
the middle of strings in the stream. Printing the original PDF file
directly with lpr does not have this problem.
The code that is doing this is the
_word_wrap_stream_count_string_up_to() function in src/cairo-pdf-
operators.c
} else if (stream-column stream-max_column) {
newline = TRUE;
break;
}
...
if (newline) {
_cairo_output_stream_printf (stream-output, \\\n);
stream-column = 0;
}
if either of these bits of code is disabled, then the problem is fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/657094
Title:
Evince when printing a pdf creates strange gapping.
Status in “cairo” package in Ubuntu:
Confirmed
Bug description:
When trying to print a pdf file with Evince Document Viewer 2.30.3 in Ubuntu
10.04 it creates strange gapping that seems to be due to Courier font.
These gaps show up when I print this file to pdf. Example file is attached.
They do not show when I print to pdf from within Acrobat Reader.
I never had this problem before, but I recently upgraded to Ubuntu 10.04 from
8.04, and I can't recall which version
of Evince I was using before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/657094/+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 1318119] Re: 14.04 corrupted graphics on cirrus (in qemu) [PATCH available]
** Changed in: xserver-xorg-video-modesetting (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: xserver-xorg-video-modesetting (Ubuntu) Status: New = Incomplete ** Changed in: xserver-xorg-video-modesetting (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-modesetting in Ubuntu. https://bugs.launchpad.net/bugs/1318119 Title: 14.04 corrupted graphics on cirrus (in qemu) [PATCH available] Status in “xserver-xorg-video-modesetting” package in Ubuntu: Incomplete Bug description: Running 14.04 LTS inside of qemu-kvm with its emulated cirrus gpu that uses 24bpp frontbuffers causes broken rendering. 12.04 LTS worked fine with no corruption on the same qemu-kvm host. RHEL7 public beta had the same problem (https://bugzilla.redhat.com/show_bug.cgi?id=1074106). RHEL7 Release Candidate applied this patch: http://patchwork.freedesktop.org/patch/18244/ From the patch: So we have 2 places where gpus with 24bpp frontbuffers are still in use, cirrus (in qemu) and some early variants of the mgag200 server chips. Currently we seem to get a lot of broken rendering in qt, mesa, gnome if we expose the frontbuffer as 24bpp, nobody seems to test this anymore upstream so client side apps are constantly broken, so lets just make -modesetting expose a 24/32 shadow frontbuffer, and use the shadow update hook to convert down to the actual 24bpp front, this might be slower, but its correct and really anyone that wants this already has enough problems. Ubuntu version: 14.04 LTS Effected version: xserver-xorg-video-modesetting-0.8.1-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-modesetting/+bug/1318119/+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 1031718] Re: Obscure error messages caused by ubuntu patch
So. Apparently this has been fixed somewhere along the road to Ubuntu 14.04. The patch is commented out in the debian/patches/series file in version 1.3.0-0ubuntu2. However, the debian/changelog doesn't tell me when that happened (or when it was added, for that matter). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1031718 Title: Obscure error messages caused by ubuntu patch Status in “libjpeg-turbo” package in Ubuntu: Confirmed Bug description: Environment: Description:Ubuntu 12.04 LTS Release:12.04 libjpeg-turbo8 1.1.90+svn733-0ubuntu4.1 Ubuntu's own patch (FixLibraryStartup.patch) causes obscure Error opening file for reading: Permission denied error messages. The patch adds some auxv related stuff to the library init that attempt to read /proc/self/auxv. If it fails the above error is printed usually ending up to application's log that's using the library. Looking at the log it's completely unclear where that error came from and what file was it trying to read. The /proc/self/auxv has 0400 permissions and is owned by the user who started the process. If the process drops privileges and setuid()'s to another user, the file is no longer readable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1031718/+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 1384289] Re: mesa 10.3.1 required for mir
** Changed in: mesa (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu) Importance: Undecided = High ** Changed in: mesa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1384289 Title: mesa 10.3.1 required for mir Status in “mesa” package in Ubuntu: Confirmed Bug description: There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So we would like to see the newest minor release of mesa, which is 10.3.1 This will fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and basically enable i915 devices to run mir. [Impact] * The bug leads to crashes in unity8 on i915 and to crashes or 'black buffers' on mir clients. * This is not a request for back porting but a request to pick the next minor bugfix release of mesa. [Test Case] * Install mir-demos on a intel atom netbook or a pentium d system * sudo mir_demo_server_basic --vt 2 --file /tmp/mir_socket * sudo chmod 666 /tmp/mir_socket * mir_demo_client_eglplasma -m /tmp/mir_socket * then vt switch to vt 1 * expected yellowish plasma animation, error: eglplasma crashing or just showing a black buffer [Regression Potential] * Instead of immediately crashing unity8s desktop session it will make the primary client of unity8: unity8-dash fail to start due to insufficient GL support on the mesa driver - but that is a different error. * 10.3.1 introduces the bespoke i915 bug fix, and further driver local fixes to nouveau for the kepler ir, shutdown leak fixes for radeon and a division by zero fix for llvmpipe. A fix to glsl that first manifested in i965. Apart from that build system cleanups for building mesa for android and detecting LLVM. * the fix to glsl has impact on i965 * fixes for intel are local to i915 and will not cause regression * fixes to radeon should only touch shutdown code * fixes to nouveau should be local to kepler gpus [Other Info] * The switch to this mesa release will not enable mir. But it will not enable unity8 on pentium D and atom, but it will be a step towards that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1384289/+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 1020001] Re: [OptiPlex 380, Realtek ALC269VB, Green Line Out, Rear] Pulseaudio fails to detect card
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=b46882b6eb713245916100ac5b58664cd242a08d
seem your desktop have line out, headphone and speaker
Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
Control: name=Speaker Playback Switch, index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x00010014: OUT EAPD Detect
EAPD 0x2: EAPD
Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
Conn = ATAPI, Color = Unknown
DefAssociation = 0x1, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x00:
Unsolicited: tag=00, enabled=0
Connection: 2
0x0c* 0x0d
Node 0x1a [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Control: name=Headphone Playback Switch, index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x003c: IN OUT HP Detect
Pin Default 0x0221402f: [Jack] HP Out at Ext Front
Conn = 1/8, Color = Green
DefAssociation = 0x2, Sequence = 0xf
Pin-ctls: 0xc0: OUT HP
Unsolicited: tag=04, enabled=1
Connection: 2
0x0c 0x0d*
Node 0x1b [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Control: name=Front Playback Switch, index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x0034: IN OUT Detect
Pin Default 0x01014020: [Jack] Line Out at Ext Rear
Conn = 1/8, Color = Green
DefAssociation = 0x2, Sequence = 0x0
Pin-ctls: 0x00:
Unsolicited: tag=01, enabled=1
Connection: 2
0x0c 0x0d*
--
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/1020001
Title:
[OptiPlex 380, Realtek ALC269VB, Green Line Out, Rear] Pulseaudio
fails to detect card
Status in “pulseaudio” package in Ubuntu:
Confirmed
Bug description:
Audio stopped working. My user is a ldap user, but it is locally in
user audio.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: pulseaudio 1:1.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
Uname: Linux 3.0.0-20-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/timer'] failed with exit
code 1:
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe6fc000 irq 43'
Mixer name : 'Realtek ALC269VB'
Components : 'HDA:10ec0269,10280400,00100100'
Controls : 20
Simple ctrls : 14
Date: Mon Jul 2 11:01:47 2012
InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
ProcEnviron:
PATH=(custom, user)
LANG=ca_ES.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel
Symptom_Jack: Green Line Out, Rear
Title: [OptiPlex 380, Realtek ALC269VB, Green Line Out, Rear] Pulseaudio
fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 0F0TGN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA00:bd10/23/2009:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn0F0TGN:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 380
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1020001/+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 657094] Re: Evince when printing a pdf creates strange gapping.
I should have mentioned that this was happening for me on Ubuntu 14.04, with libcairo2_1.13.0~20140204-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/657094 Title: Evince when printing a pdf creates strange gapping. Status in “cairo” package in Ubuntu: Confirmed Bug description: When trying to print a pdf file with Evince Document Viewer 2.30.3 in Ubuntu 10.04 it creates strange gapping that seems to be due to Courier font. These gaps show up when I print this file to pdf. Example file is attached. They do not show when I print to pdf from within Acrobat Reader. I never had this problem before, but I recently upgraded to Ubuntu 10.04 from 8.04, and I can't recall which version of Evince I was using before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/657094/+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 1310489] Re: xorg.conf overwritten by booting system
On 23-10-14 06:29:51, Mark Duncan wrote: This bug is still affecting me. I have a desktop with two nVidia cards in an SLI configuration. I need a custom xorg.conf to support my 1440p monitor, but my xorg.conf gets renamed to xorg.conf.mmdd almost every reboot. That's a separate case. Can you attach your working xorg.conf and the file that the sudo nvidia-bug-report.sh command creates, please? -- 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/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present
Re: [Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
On 22-10-14 20:34:24, Joakim wrote: According to that page, it should be rated as high importance. * Has a severe impact on a small portion of Ubuntu users (estimated) Yes, all users who wants to use fglrx and wine. * A problem with an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse) Yes, package conflict for the video card driver. * Prevents the application or any dependencies from functioning correctly at all Yes, both wine and fglrx. * Renders essential features or functionality of the application or dependencies broken or ineffective Yes, both wine and fglrx. * Impacts accessibility of a core application Yes, fglrx. You can't even get build-dep for wine. Nevertheless, fixing this bug should be done before the final release of Ubuntu 14.10. If it can not be fixed easily, it would be better to remove the conflicting dependency from wine. Only a few users would be effected and they can fix it themselves by installing the necessary packages manually. The wine package lives in the universe repository, and this excludes it from the essential and core packages (that usually live in main or restricted). The graphics driver provides core functionalities, wine does not. The bug priority is right. It was/is too late to fix this bug report for fglrx in 14.10, which also depended on LP: #1382086 and LP: #1382091 (both fixed only a few hours ago). I'll have to fix this in 15.04 (the next development release) first, only then will it be reasonable to backport the fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in “boinc” package in Ubuntu: Fix Released Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Status in “nvidia-cuda-toolkit” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-310-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-313-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pycuda” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “starpu-contrib” package in Ubuntu: Fix Released Status in “viennacl” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1384629] [NEW] Connections over TLS1 and newer fail, tested patch available
*** This bug is a security vulnerability *** Public security bug reported: For SSL encryption on a dedicated port evolution supports only SSLv3. After POODLE we disabled SSLv3 on server and Evolution could no longer connect. Proper TLS support is available after patching with https://bugzilla.redhat.com/show_bug.cgi?id=1153052#c5 I patched, built and installed and SSL/TLS now working in Ubuntu 14.04 with evolution-data-server-3.10.4 Please consider distributing this as a standard software update. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: ssl tls ** Patch added: By Milan Crha, original at https://bugzilla.redhat.com/show_bug.cgi?id=1153052#c5; https://bugs.launchpad.net/bugs/1384629/+attachment/4242280/+files/patch.txt ** Information type changed from Private Security to Public Security -- 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/1384629 Title: Connections over TLS1 and newer fail, tested patch available Status in “evolution” package in Ubuntu: New Bug description: For SSL encryption on a dedicated port evolution supports only SSLv3. After POODLE we disabled SSLv3 on server and Evolution could no longer connect. Proper TLS support is available after patching with https://bugzilla.redhat.com/show_bug.cgi?id=1153052#c5 I patched, built and installed and SSL/TLS now working in Ubuntu 14.04 with evolution-data-server-3.10.4 Please consider distributing this as a standard software update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1384629/+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 1268771] Re: NVIDIA Prime fails with Linux 3.13
This problem is fixed. Feel free to file a separate bug report by using the following command: ubuntu-bug nvidia-331 (or nvidia-331-updates, if that is what you use). -- 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/1268771 Title: NVIDIA Prime fails with Linux 3.13 Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Bug description: When I select the Nvidia® graphics card from control panel using nvidia-prime, after logging out, the screen goes black and the only way to approach it is in text mode. I also used the nvidia-prime 4.2 in Ubuntu 13.10 but I have never encountered such problems. Specifications --- Operative System : Ubuntu 14.04LTS 64bit (Daily Build) Package: nvidia-prime 0.5.3 Driver: nvidia-331-updates Graphics: Nvidia® GeForce® 610M Processor: Intel® Core™ i7-2670QM --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268771/+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 1366284] Re: Failed to issue method call: Unit nvidia-prime.service failed to load: No such file or directory.
nvidia-prime doesn't support systemd yet. This will require a systemd equivalent. ** Changed in: nvidia-prime (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu) Importance: Undecided = Medium ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Confirmed = Invalid -- 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/1366284 Title: Failed to issue method call: Unit nvidia-prime.service failed to load: No such file or directory. Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “nvidia-prime” package in Ubuntu: Confirmed Bug description: Utopic i386 with gtx 750 and q9550 (no builtin gpu here) using systemd-boot Follow up lp:1365336 nvidia-331 package error about nvidia-prime at build time: oem@u32:~$ sudo apt-get install --reinstall nvidia-331 [sudo] password for oem: Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/27,7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 216738 files and directories currently installed.) Preparing to unpack .../nvidia-331_331.89-0ubuntu3_i386.deb ... Removing all DKMS Modules Done. Unpacking nvidia-331 (331.89-0ubuntu3) over (331.89-0ubuntu3) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... Setting up nvidia-prime (0.6.6) ... Failed to issue method call: Unit nvidia-prime.service failed to load: No such file or directory. invoke-rc.d: initscript nvidia-prime, action start failed. dpkg: error processing package nvidia-prime (--configure): subprocess installed post-installation script returned error exit status 6 Setting up nvidia-331 (331.89-0ubuntu3) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-331-331.89 DKMS files... Building only for 3.16.0-13-generic Building for architecture i686 Building initial module for 3.16.0-13-generic Done. nvidia_331: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-13-generic/updates/dkms/ depmod DKMS: install completed. Processing triggers for initramfs-tools (0.103ubuntu8) ... update-initramfs: Generating /boot/initrd.img-3.16.0-13-generic Errors were encountered while processing: nvidia-prime E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Sat Sep 6 10:52:02 2014 SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) Note: uninstalling the faulty nvidia-prime package does not let booting with nvidia (jockey fails to find nvidia driver) and then 'nouveau' is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1366284/+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 139067] Re: Openning gif file with causes the system freezing
** Changed in: gtk Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/139067 Title: Openning gif file with causes the system freezing Status in GTK+ GUI Toolkit: Invalid Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: Ubuntu 7.10 Eye of gnome 2.19.92 When I use eog to view this gif file, the whole system is freezing. Both mouse and keyboard do not response either. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/139067/+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 1384636] [NEW] Spurious characters on some keys
Public bug reported: Xubuntu 14.04.1 on ASUS S400C laptop, since updates at the end of September I have been getting problems with some keys using En-GB with extended WinKeys. Specifically 'p', which sends something like 'p~~' and in Chrome opens either the print dialog or the debug console, and 'Esc' which started sending '0sen' particularly in vi. Removing ibus seems to have resolved the problem but if it's going to be the default keyboard manager there's something odd there. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1384636 Title: Spurious characters on some keys Status in “ibus” package in Ubuntu: New Bug description: Xubuntu 14.04.1 on ASUS S400C laptop, since updates at the end of September I have been getting problems with some keys using En-GB with extended WinKeys. Specifically 'p', which sends something like 'p~~' and in Chrome opens either the print dialog or the debug console, and 'Esc' which started sending '0sen' particularly in vi. Removing ibus seems to have resolved the problem but if it's going to be the default keyboard manager there's something odd there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1384636/+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
#92 seems to have solved this bug for me. Thanks nknico. My Dad has the same bug on OSX... -- 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 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN
I've used xl2tpd for many years. If this thing (#37) isn't still a part of Ubuntu - I do not understand why! Blocking Internet is actually critical importance, not wishlist! -- 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/264691 Title: Please add NM option for connecting to L2TP IPSEC VPN Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” package in Debian: Invalid Bug description: Binary package hint: network-manager Missing feature: You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network Manager. The server I want to connect to expects a login / password and a PSK. When you do a connection in XP you can see the following details on a connection: Device name: L2TP Server type: PPP Authentication: MS CHAP v2 IPSEC Encryption: IPSEC ESP 3DES Compression: MPPC To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264691/+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
Sorry spoke too soon, it worked with a brief period of suspend (screen did go blank) but is not working again. Tried #93 for what I thought might be the equivalent file no joy. -- 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 1241972] Re: Drag and drop from Dash to Desktop doesn't work
I am also affected by this bug. However, the main issue is that it is not ONLY desktop but basically EVERYWHERE, so I also cannot drag drop launcher icons to e.g. start programs. -- 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/1241972 Title: Drag and drop from Dash to Desktop doesn't work Status in Chromium Browser: New Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.1 series: Won't Fix Status in Unity 7.2 series: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When you try to drag and drop an app from Dash (both from app lens and home lens) to Desktop, system display an error and the shortcut isn't created. The error is: Error while copying - There was an error getting information about /. More details: The specified location is not supported Then there are four buttons: Cancel - Skip all - Skip - Retry. Way to reproduce: - Open the dash - Drag an app icon and drop on desktop What happend: - An error is raised What expected: - A shortcut is created With file, music and photo is all ok. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1241972/+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 1241972] Re: Drag and drop from Dash to Desktop doesn't work
forgot to mention: using Ubuntu 14.04.1 -- 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/1241972 Title: Drag and drop from Dash to Desktop doesn't work Status in Chromium Browser: New Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.1 series: Won't Fix Status in Unity 7.2 series: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When you try to drag and drop an app from Dash (both from app lens and home lens) to Desktop, system display an error and the shortcut isn't created. The error is: Error while copying - There was an error getting information about /. More details: The specified location is not supported Then there are four buttons: Cancel - Skip all - Skip - Retry. Way to reproduce: - Open the dash - Drag an app icon and drop on desktop What happend: - An error is raised What expected: - A shortcut is created With file, music and photo is all ok. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1241972/+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 1384629] Re: Connections over TLS1 and newer fail, tested patch available
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evolution (Ubuntu) Status: New = Confirmed -- 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/1384629 Title: Connections over TLS1 and newer fail, tested patch available Status in “evolution” package in Ubuntu: Confirmed Bug description: For SSL encryption on a dedicated port evolution supports only SSLv3. After POODLE we disabled SSLv3 on server and Evolution could no longer connect. Proper TLS support is available after patching with https://bugzilla.redhat.com/show_bug.cgi?id=1153052#c5 I patched, built and installed and SSL/TLS now working in Ubuntu 14.04 with evolution-data-server-3.10.4 Please consider distributing this as a standard software update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1384629/+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 1384455] Re: Fail to be Transperant or Translucent
** Package changed: xorg (Ubuntu) = tilda (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/1384455 Title: Fail to be Transperant or Translucent Status in “tilda” package in Ubuntu: New Bug description: It occurs on Kubuntu 14.04 and Kubuntu 14.10 also When I tried to modify tilda to be Tranperant or Translucent It didn't work please see the screenshot It happened to be created box in the middle of the tilda ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: KDE Date: Thu Oct 23 05:55:20 2014 InstallationDate: Installed on 2014-10-22 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) ProcEnviron: LANGUAGE=ko PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ko_KR.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tilda/+bug/1384455/+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 214366]
(In reply to :aceman from comment #144) See comment 142. If you see the problem on IMAP, please open a new bug. We knowingly fixed it only for POP3/Local accounts in this bug. Ok, will do... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/214366 Title: Can't delete a folder if Trash already contains a folder of the same name Status in Mozilla Thunderbird Mail and News: Fix Released Status in “thunderbird” package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird 1. Create a new folder, eg. Temp 2. Delete it, OK 3. Create the same folder again 4. Delete it, OK I expect it to be moved to my Trash folder, perhaps with a suffix appended (it being the second instance of that folder in the trash). Thunderbird popped up an error message. On an imap host: The current command did not succeed. The mail server responded: Mailbox already exists. In the local folders: A folder with that name already exists. Please enter a different name (!) Workarounds: 1. Empty the trash 2. Rename the folder before deletion 3. Rename the folder already in the trash 4. Delete (permanently) the folder that is already in the trash Ubuntu 7.10 Gutsy thunderbird 2.0.0.12+nobinonly-0ubuntu0.7.10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/214366/+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 913839] Re: tether over bluetooth - regression in precise
I'm muting this bug for myself. In the two years since I reported it, I've moved on from Blackberry phones and no longer have a device with which to test. I'm sure one of the other 29 people who marked it as affecting them can help with testing, if a fix for the regression is ever created. -- 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/913839 Title: tether over bluetooth - regression in precise Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” package in Fedora: Unknown Bug description: I've had dial-up networking via bluetooth working between my CR-48 and Blackberry 9800 for several months. Recent Precise update (sometime around the last couple of weeks of 2011) appear to have broken the ability to tether over bluetooth in this manner. I have completely removed the bluetooth connection and re-paired the devices from scratch, but it does not work. Other bluetooth functionality appears to work fine. i.e. I can send files from the laptop to the phone without issue. Here's what I see in syslog: Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) starting connection 'ATT MEdia Net (phones)' Jan 9 09:02:28 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: disconnected - prepare (reason 'none') [30 40 0] Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) scheduled... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) started... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) scheduled... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) complete. Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) starting... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: prepare - config (reason 'none') [40 50 0] Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) complete. Jan 9 09:02:48 chrombuntu NetworkManager[516]: warn Error connecting with bluez: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Jan 9 09:02:48 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: config - failed (reason 'bluetooth-failed') [50 120 44] Jan 9 09:02:48 chrombuntu NetworkManager[516]: warn Activation (CC:55:AD:DF:60:A9) failed. Jan 9 09:02:48 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: failed - disconnected (reason 'none') [120 30 0] Jan 9 09:02:48 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): deactivating device (reason 'none') [0] Jan 9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_routes: assertion `ifindex 0' failed Jan 9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_addresses: assertion `ifindex 0' failed Jan 9 09:03:11 chrombuntu bluetoothd[1268]: Connection refused (111) dmesg is devoid of any errors during the attempt to connect. The only messages I see related to the device is: [ 6567.470098] Bluetooth: TIOCGSERIAL is not supported ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.2.0+git201112151936.6b31828-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Mon Jan 9 09:09:39 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110913) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.206 metric 2 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 CC:55:AD:DF:60:A9 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED
[Desktop-packages] [Bug 1380270] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug has been marked a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1380270 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: error when trying to purge* nvidia 331 after having a broken pipe during statup due to upgrading from 14.04 to 14.10. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 AptOrdering: nvidia-331-uvm: Purge nvidia-331: Purge Architecture: amd64 Date: Sun Oct 12 13:39:25 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück ErrorMessage: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück InstallationDate: Installed on 2014-08-23 (49 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück UpgradeStatus: Upgraded to utopic on 2014-10-11 (1 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1380270/+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 1378423] Re: Virtualbox boots to black screen or corrupted screen with daily
Kubuntu Plasma 5 23.10.2014 image here. Boots to a corruped screen as seen in http://people.ubuntu.com/~quintasan/disco.webm -- 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/1378423 Title: Virtualbox boots to black screen or corrupted screen with daily Status in “xorg” package in Ubuntu: Confirmed Bug description: Boot the daily image. Get a black screen. Go to tty1 - lightdm has started - running sudo service lightdm status echoes start/waiting Return to tty7 and the login dialogue has now appeared ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.344 Date: Tue Oct 7 15:53:54 2014 LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006) ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1378423/+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 1372786] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug has been marked a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1372786 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 8 Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: while updating to sudo apt-get install nvidia-343 via ppa: ppa:xorg- edgers/ppa ubuntu 14.10 pre release MATE ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 23 09:01:35 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:el subproceso instalado el script post-removal devolvió el código de salida de error 8 ErrorMessage: el subproceso instalado el script post-removal devolvió el código de salida de error 8 InstallationDate: Installed on 2014-09-19 (3 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - pre-beta2.26207 amd64 (20140919) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 8 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1372786/+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 1374821] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug has been marked a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1374821 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: nvidia-graphics-drivers-331 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Sat Sep 27 22:41:01 2014 ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 InstallationDate: Installed on 2014-09-27 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 UpgradeStatus: Upgraded to utopic on 2014-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1374821/+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 1380270] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug is no longer a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug has been marked a duplicate of bug 1369398 package nvidia-331 331.89-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1380270 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: error when trying to purge* nvidia 331 after having a broken pipe during statup due to upgrading from 14.04 to 14.10. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 AptOrdering: nvidia-331-uvm: Purge nvidia-331: Purge Architecture: amd64 Date: Sun Oct 12 13:39:25 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück ErrorMessage: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück InstallationDate: Installed on 2014-08-23 (49 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück UpgradeStatus: Upgraded to utopic on 2014-10-11 (1 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1380270/+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 1374821] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug is no longer a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug has been marked a duplicate of bug 1369398 package nvidia-331 331.89-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1374821 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: nvidia-graphics-drivers-331 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Sat Sep 27 22:41:01 2014 ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 InstallationDate: Installed on 2014-09-27 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 UpgradeStatus: Upgraded to utopic on 2014-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1374821/+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 1372786] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug is no longer a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug has been marked a duplicate of bug 1369398 package nvidia-331 331.89-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1372786 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 8 Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: while updating to sudo apt-get install nvidia-343 via ppa: ppa:xorg- edgers/ppa ubuntu 14.10 pre release MATE ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 23 09:01:35 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:el subproceso instalado el script post-removal devolvió el código de salida de error 8 ErrorMessage: el subproceso instalado el script post-removal devolvió el código de salida de error 8 InstallationDate: Installed on 2014-09-19 (3 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - pre-beta2.26207 amd64 (20140919) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 8 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1372786/+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 1380580] Re: package nvidia-331-updates 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Invalid = Confirmed ** This bug has been marked a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug is no longer a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug has been marked a duplicate of bug 1369398 package nvidia-331 331.89-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1380580 Title: package nvidia-331-updates 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: while sudo apt-get install nvidia-331-uvm --reinstall as noted Tiago Carrondo ti...@ubuntu-pt.org for [Bug 1268257] ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 Date: Mon Oct 13 15:12:21 2014 ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 InstallationDate: Installed on 2013-06-08 (491 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nvidia-graphics-drivers-331-updates Title: package nvidia-331-updates 331.89-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 8 UpgradeStatus: Upgraded to utopic on 2014-08-24 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1380580/+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 1374757] Re: package nvidia-331-updates 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug has been marked a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug is no longer a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug has been marked a duplicate of bug 1369398 package nvidia-331 331.89-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1374757 Title: package nvidia-331-updates 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: May have also been a suspend on laptop close issue. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Sat Sep 27 08:14:12 2014 DuplicateSignature: package:nvidia-331-updates:331.89-0ubuntu5:subprocess installed post-removal script returned error exit status 8 ErrorMessage: subprocess installed post-removal script returned error exit status 8 InstallationDate: Installed on 2014-09-27 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) SourcePackage: nvidia-graphics-drivers-331-updates Title: package nvidia-331-updates 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1374757/+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 1378949] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: New = Confirmed ** This bug has been marked a duplicate of bug 1369398 package nvidia-331 331.89-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1378949 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: Tried to switch to using NVIDIA binary driver - version 331.89 from nvidia-331-updates (proprietary) ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 Date: Wed Oct 8 12:05:05 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:subprocess installed post-removal script returned error exit status 8 ErrorMessage: subprocess installed post-removal script returned error exit status 8 InstallationDate: Installed on 2012-04-02 (919 days ago) InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1378949/+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 1382770] Re: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8
*** This bug is a duplicate of bug 1369398 *** https://bugs.launchpad.net/bugs/1369398 ** This bug has been marked a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug is no longer a duplicate of bug 1378949 package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 ** This bug has been marked a duplicate of bug 1369398 package nvidia-331 331.89-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 -- 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/1382770 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: le sous- processus script post-removal installé a retourné une erreur de sortie d'état 8 Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Occured while upgrading to nvidia-340 in apt-get ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu7 Architecture: amd64 Date: Sat Oct 18 11:36:33 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 InstallationDate: Installed on 2014-10-10 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140923) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1382770/+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 1378423] Re: Virtualbox boots to black screen or corrupted screen with daily
Kubuntu Plasma 5 23.10.2014 image here. Boots to a corruped screen as seen in attachment ** Attachment added: Video that shows what exactly happens https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1378423/+attachment/4242337/+files/disco.webm -- 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/1378423 Title: Virtualbox boots to black screen or corrupted screen with daily Status in “xorg” package in Ubuntu: Confirmed Bug description: Boot the daily image. Get a black screen. Go to tty1 - lightdm has started - running sudo service lightdm status echoes start/waiting Return to tty7 and the login dialogue has now appeared ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.344 Date: Tue Oct 7 15:53:54 2014 LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006) ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1378423/+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 1379765] Re: package nvidia-opencl-icd-331 (not installed) failed to install/upgrade: Versuch, »/etc/OpenCL/vendors/nvidia.icd« zu überschreiben, welches auch in Paket nvidia-o
*** This bug is a duplicate of bug 1328762 *** https://bugs.launchpad.net/bugs/1328762 ** This bug has been marked a duplicate of bug 1328762 package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-331 331.79-0ubuntu1 -- 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/1379765 Title: package nvidia-opencl-icd-331 (not installed) failed to install/upgrade: Versuch, »/etc/OpenCL/vendors/nvidia.icd« zu überschreiben, welches auch in Paket nvidia-opencl-icd-331-updates 331.38-0ubuntu7.1 ist Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: I've tried to update this package via aptitude. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-331 (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Oct 10 13:34:32 2014 DuplicateSignature: package:nvidia-opencl-icd-331:(not installed):Versuch, »/etc/OpenCL/vendors/nvidia.icd« zu überschreiben, welches auch in Paket nvidia-opencl-icd-331-updates 331.38-0ubuntu7.1 ist ErrorMessage: Versuch, »/etc/OpenCL/vendors/nvidia.icd« zu überschreiben, welches auch in Paket nvidia-opencl-icd-331-updates 331.38-0ubuntu7.1 ist InstallationDate: Installed on 2014-04-19 (173 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-opencl-icd-331 (not installed) failed to install/upgrade: Versuch, »/etc/OpenCL/vendors/nvidia.icd« zu überschreiben, welches auch in Paket nvidia-opencl-icd-331-updates 331.38-0ubuntu7.1 ist 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/+bug/1379765/+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 1374644] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: próba nadpisania /etc/OpenCL/vendors/nvidia.icd, który istnieje także w pakiecie
*** This bug is a duplicate of bug 1328762 *** https://bugs.launchpad.net/bugs/1328762 ** This bug has been marked a duplicate of bug 1328762 package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-331 331.79-0ubuntu1 -- 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/1374644 Title: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: próba nadpisania /etc/OpenCL/vendors/nvidia.icd, który istnieje także w pakiecie nvidia-opencl-icd-331 331.89-0ubuntu1~xedgers14.04.2 Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: when install from official repository ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-331-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 AptOrdering: nvidia-opencl-icd-331-updates: Install nvidia-opencl-icd-331-updates: Configure Architecture: amd64 Date: Sat Sep 27 00:55:58 2014 DpkgTerminalLog: Preparing to unpack .../nvidia-opencl-icd-331-updates_331.38-0ubuntu7.1_amd64.deb ... Unpacking nvidia-opencl-icd-331-updates (331.38-0ubuntu7.1) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-opencl-icd-331-updates_331.38-0ubuntu7.1_amd64.deb (--unpack): próba nadpisania /etc/OpenCL/vendors/nvidia.icd, który istnieje także w pakiecie nvidia-opencl-icd-331 331.89-0ubuntu1~xedgers14.04.2 DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not installed):próba nadpisania /etc/OpenCL/vendors/nvidia.icd, który istnieje także w pakiecie nvidia-opencl-icd-331 331.89-0ubuntu1~xedgers14.04.2 ErrorMessage: próba nadpisania /etc/OpenCL/vendors/nvidia.icd, który istnieje także w pakiecie nvidia-opencl-icd-331 331.89-0ubuntu1~xedgers14.04.2 InstallationDate: Installed on 2014-07-25 (63 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: nvidia-graphics-drivers-331-updates Title: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: próba nadpisania /etc/OpenCL/vendors/nvidia.icd, który istnieje także w pakiecie nvidia-opencl-icd-331 331.89-0ubuntu1~xedgers14.04.2 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/1374644/+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 to be working intermittently... -- 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 1299604] Re: evolution keeps asking for password
today evolution is no more asking for password and work well. I do not know if any update has solved the problem. regards -- 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/1299604 Title: evolution keeps asking for password Status in “evolution” package in Ubuntu: Confirmed Bug description: Hi, I have connected my evolution to mail server (imap) and it asks EVERY time after login for password to that email account. It do not remember it, even when I tick remember using keyring. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 23:00:38 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317) ProcEnviron: LANGUAGE=cs PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1299604/+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 139067] [NEW] Openning gif file with causes the system freezing
You have been subscribed to a public bug: Ubuntu 7.10 Eye of gnome 2.19.92 When I use eog to view this gif file, the whole system is freezing. Both mouse and keyboard do not response either. ** Affects: gtk Importance: Medium Status: Invalid ** Affects: gdk-pixbuf (Ubuntu) Importance: Medium Status: Fix Committed -- Openning gif file with causes the system freezing https://bugs.launchpad.net/bugs/139067 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf 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 1382774] Re: Postgresql installation for MAAS fails on locales missing language packs
I just tried this scenario (de_DE.UTF-8 locally, ssh into machine with just en_US.UTF-8 available), and apt install postgresql succeeds and creates a cluster successfully which runs with en_US.UTF-8. But the more I look at the bug description (which isn't particularly clear) I have the feeling that we aren't talking about the postgresql package installation, but instead maas directly calls pg_createcluster? If so, how exactly does it do that? The disregard environment and only look at /etc/default/locale workaround is done in postgresql-X.Y's postinst, i. e. it only applies to package installation time. If you call pg_createcluster directly as root in a broken environment it won't help you. Now, in theory that hackish workaround from postinst time could be moved direclty into pg_createcluster, but I veto that as this is established behaviour and I don't want to break cases where people call LANG=xx_YY pg_createcluster (see the help of --locale in help output and manpage). So if in MAAS you also can't rely on the environment, a similar hack like https://alioth.debian.org/scm/loggerhead/pkg-postgresql/postgresql- common/trunk/view/head:/debian/maintscripts-functions#L40 might be required? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1382774 Title: Postgresql installation for MAAS fails on locales missing language packs Status in MAAS: New Status in “postgresql-common” package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 with all updates as of time of the writing. MAAS - 1.5.4+bzr2294-0ubuntu1.1 # apt-get install maas ... Setting up maas-dns (1.5.4+bzr2294-0ubuntu1.1) ... * Stopping domain name service... bind9 waiting for pid 29580 to die [ OK ] * Starting domain name service... bind9 [ OK ] Setting up maas-region-controller (1.5.4+bzr2294-0ubuntu1.1) ... locale: Cannot set LC_ALL to default locale: No such file or directory Considering dependency proxy for proxy_http: Module proxy already enabled Module proxy_http already enabled Module expires already enabled Module wsgi already enabled rsyslog stop/waiting rsyslog start/running, process 32763 squid-deb-proxy stop/waiting squid-deb-proxy start/running, process 349 * Restarting message broker rabbitmq-server [ OK ] Creating user maas_longpoll ... ...done. Creating vhost /maas_longpoll ... ...done. Setting permissions for user maas_longpoll in vhost /maas_longpoll ... ...done. Creating user maas_workers ... ...done. Creating vhost /maas_workers ... ...done. Setting permissions for user maas_workers in vhost /maas_workers ... ...done. * No PostgreSQL clusters exist; see man pg_createcluster dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf Creating config file /etc/dbconfig-common/maas-region-controller.conf with new version unable to connect to postgresql server. error encountered creating user: psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket /var/run/postgresql/.s.PGSQL.5432? /usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory Here's the environment: # export declare -x HOME=/root declare -x LANG=en_US.UTF-8 declare -x LANGUAGE=en_US:en declare -x LC_ADDRESS=hr_HR.UTF-8 declare -x LC_IDENTIFICATION=hr_HR.UTF-8 declare -x LC_MEASUREMENT=hr_HR.UTF-8 declare -x LC_MONETARY=hr_HR.UTF-8 declare -x LC_NAME=hr_HR.UTF-8 declare -x LC_NUMERIC=hr_HR.UTF-8 declare -x LC_PAPER=hr_HR.UTF-8 declare -x LC_TELEPHONE=hr_HR.UTF-8 declare -x LC_TIME=hr_HR.UTF-8 declare -x LESSCLOSE=/usr/bin/lesspipe %s %s declare -x LESSOPEN=| /usr/bin/lesspipe %s declare -x LOGNAME=root declare -x
[Desktop-packages] [Bug 139067] Re: Openning gif file with causes the system freezing
** Package changed: gtk+2.0 (Ubuntu) = ubuntu ** Changed in: ubuntu Status: Triaged = Fix Committed ** Changed in: ubuntu Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) ** Package changed: ubuntu = gdk-pixbuf (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/139067 Title: Openning gif file with causes the system freezing Status in GTK+ GUI Toolkit: Invalid Status in “gdk-pixbuf” package in Ubuntu: Fix Committed Bug description: Ubuntu 7.10 Eye of gnome 2.19.92 When I use eog to view this gif file, the whole system is freezing. Both mouse and keyboard do not response either. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/139067/+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 1310489] Re: xorg.conf overwritten by booting system
I also still have the same problem - xorg.conf is randomly overwritten by gpu-manager. ** Attachment added: nvidia-bug-report.log.gz https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4242349/+files/nvidia-bug-report.log.gz -- 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/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset
[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
** Attachment added: xorg.conf https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4242350/+files/xorg.conf -- 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/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1985 dmi.board.vendor: Hewlett-Packard dmi.board.version: 01.13 dmi.chassis.type: 10
[Desktop-packages] [Bug 1384629] Re: Connections over TLS1 and newer fail, tested patch available
The attachment By Milan Crha, original at https://bugzilla.redhat.com/show_bug.cgi?id=1153052#c5; seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch ** Bug watch added: Red Hat Bugzilla #1153052 https://bugzilla.redhat.com/show_bug.cgi?id=1153052 -- 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/1384629 Title: Connections over TLS1 and newer fail, tested patch available Status in “evolution” package in Ubuntu: Confirmed Bug description: For SSL encryption on a dedicated port evolution supports only SSLv3. After POODLE we disabled SSLv3 on server and Evolution could no longer connect. Proper TLS support is available after patching with https://bugzilla.redhat.com/show_bug.cgi?id=1153052#c5 I patched, built and installed and SSL/TLS now working in Ubuntu 14.04 with evolution-data-server-3.10.4 Please consider distributing this as a standard software update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1384629/+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 913839] Re: tether over bluetooth - regression in precise
Actually, on recent versions (trusty/utopic) tethering works and IP obtained via bnep0. I think this bug should be or closed, or restricted to some versions. My nm package version is 0.9.8.8-0ubuntu28 and it works. -- 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/913839 Title: tether over bluetooth - regression in precise Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” package in Fedora: Unknown Bug description: I've had dial-up networking via bluetooth working between my CR-48 and Blackberry 9800 for several months. Recent Precise update (sometime around the last couple of weeks of 2011) appear to have broken the ability to tether over bluetooth in this manner. I have completely removed the bluetooth connection and re-paired the devices from scratch, but it does not work. Other bluetooth functionality appears to work fine. i.e. I can send files from the laptop to the phone without issue. Here's what I see in syslog: Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) starting connection 'ATT MEdia Net (phones)' Jan 9 09:02:28 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: disconnected - prepare (reason 'none') [30 40 0] Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) scheduled... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) started... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) scheduled... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) complete. Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) starting... Jan 9 09:02:28 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: prepare - config (reason 'none') [40 50 0] Jan 9 09:02:28 chrombuntu NetworkManager[516]: info Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) complete. Jan 9 09:02:48 chrombuntu NetworkManager[516]: warn Error connecting with bluez: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Jan 9 09:02:48 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: config - failed (reason 'bluetooth-failed') [50 120 44] Jan 9 09:02:48 chrombuntu NetworkManager[516]: warn Activation (CC:55:AD:DF:60:A9) failed. Jan 9 09:02:48 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): device state change: failed - disconnected (reason 'none') [120 30 0] Jan 9 09:02:48 chrombuntu NetworkManager[516]: info (CC:55:AD:DF:60:A9): deactivating device (reason 'none') [0] Jan 9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_routes: assertion `ifindex 0' failed Jan 9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_addresses: assertion `ifindex 0' failed Jan 9 09:03:11 chrombuntu bluetoothd[1268]: Connection refused (111) dmesg is devoid of any errors during the attempt to connect. The only messages I see related to the device is: [ 6567.470098] Bluetooth: TIOCGSERIAL is not supported ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.2.0+git201112151936.6b31828-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Mon Jan 9 09:09:39 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110913) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.206 metric 2 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 CC:55:AD:DF:60:A9 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0
[Desktop-packages] [Bug 1310140] Re: nvidia-331 kernel module failed to install lubuntu 14.04 [cc: error trying to exec 'as': execvp: No such file or directory]
*** This bug is a duplicate of bug 1311104 *** https://bugs.launchpad.net/bugs/1311104 In my case, was helped previously switched up bumblebee: sudo tee /proc/acpi/bbswitch ON -- 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/1310140 Title: nvidia-331 kernel module failed to install lubuntu 14.04 [cc: error trying to exec 'as': execvp: No such file or directory] Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: got bbswitch-dkms error while installing ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 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 DKMSKernelVersion: 3.13.0-24-generic Date: Sun Apr 20 09:55:43 2014 DuplicateSignature: dkms:nvidia-331:331.38-0ubuntu7:/var/lib/dkms/nvidia-331/331.38/build/conftest/macros.h:1:2: error: #error INIT_WORK() conftest failed! PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build 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/+bug/1310140/+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 168610] Re: Exporting patterns and gradients doesn't work for PDF / EMF
I have this issue with Inkscape 0.91pre2 r13516 some times pattern displays incorrectly in pdf, sometimes not at all. tried with pdf reader and sumatra pdf on windows 7. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/168610 Title: Exporting patterns and gradients doesn't work for PDF / EMF Status in Inkscape: A Vector Drawing Tool: Fix Released Status in Poppler: Fix Released Status in “cairo” package in Ubuntu: Triaged Bug description: Create a pattern in Inkscape. Fill a shape with it Save the file as PDF or EMF The pattern doesn't show up in the resulting file. See attached SVG for an example. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/168610/+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 1310489] Re: xorg.conf overwritten by booting system
@Alistair: please also include your /var/log/gpu-manager.log after your xorg.conf is overwritten. -- 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/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1985 dmi.board.vendor: Hewlett-Packard dmi.board.version: 01.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard
[Desktop-packages] [Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors
Present in 14.10RC -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors Status in “at-spi2-core” package in Ubuntu: Confirmed Bug description: Sometimes I get the following messages in .xsession-errors init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode. Can perhaps have a relation with bug 1227173. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+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 1368303] Re: Enhanced Zoom Desktop only works if mouse pointer is over the active window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1368303 Title: Enhanced Zoom Desktop only works if mouse pointer is over the active window Status in “compiz” package in Ubuntu: Confirmed Bug description: I have my Enhanced Zoom Desktop enabled and setup as follows: Zoom In Button: ControlSuperButton4 Zoom Out Button: ControlSuperButton5 Enable focus tracking: Disabled I've noticed that since upgrading to 14.04, I can only use the zoom functionality if my mouse cursor sits above the currently focused window. If, for example, I move my cursor to another monitor without clicking to activate the window in that area, I cannot use my defined shortcut to increase or decrease the magnification level. The same is true if I move my cursor outside the bounds of the currently focused window within the same display. I would expect that I should be able to increase or decrease the magnification level of the display regardless of the mouse position within it. This appeared to be the case at least on 12.04. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy compiz compiz: Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1 Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1368303/+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 1384629] Re: Connections over TLS1 and newer fail, tested patch available
*** This bug is a duplicate of bug 1382133 *** https://bugs.launchpad.net/bugs/1382133 ** This bug has been marked a duplicate of bug 1382133 Issue with servers with SSLv3 disabled due to Poodle -- 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/1384629 Title: Connections over TLS1 and newer fail, tested patch available Status in “evolution” package in Ubuntu: Confirmed Bug description: For SSL encryption on a dedicated port evolution supports only SSLv3. After POODLE we disabled SSLv3 on server and Evolution could no longer connect. Proper TLS support is available after patching with https://bugzilla.redhat.com/show_bug.cgi?id=1153052#c5 I patched, built and installed and SSL/TLS now working in Ubuntu 14.04 with evolution-data-server-3.10.4 Please consider distributing this as a standard software update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1384629/+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 1368303] Re: Enhanced Zoom Desktop only works if mouse pointer is over the active window
Same here (using just SuperButton4/5). The problem only occurs when using Button4 and 5 (mouse wheel). Using other buttons works fine. Using the mouse wheel is quite intuitive for this feature so not being able to use this mapping completely is a bit of a pitty… I'm also on 14.04, fresh install from beginning of October. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1368303 Title: Enhanced Zoom Desktop only works if mouse pointer is over the active window Status in “compiz” package in Ubuntu: Confirmed Bug description: I have my Enhanced Zoom Desktop enabled and setup as follows: Zoom In Button: ControlSuperButton4 Zoom Out Button: ControlSuperButton5 Enable focus tracking: Disabled I've noticed that since upgrading to 14.04, I can only use the zoom functionality if my mouse cursor sits above the currently focused window. If, for example, I move my cursor to another monitor without clicking to activate the window in that area, I cannot use my defined shortcut to increase or decrease the magnification level. The same is true if I move my cursor outside the bounds of the currently focused window within the same display. I would expect that I should be able to increase or decrease the magnification level of the display regardless of the mouse position within it. This appeared to be the case at least on 12.04. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy compiz compiz: Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1 Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1368303/+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 1274779] Re: [ivb] hang on pageflip (IPEHR: 0x0a000001 or 0x0a080001 depending on pipe)
It would be great to know if there are any plans to backport this, and if so to which releases. Thanks. -- 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/1274779 Title: [ivb] hang on pageflip (IPEHR: 0x0a01 or 0x0a080001 depending on pipe) Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Committed Bug description: False GPU lockup IPEHR: 0x0a01 ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 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 Date: Wed Jan 29 23:32:19 2014 DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: GPU lockup IPEHR: 0x0a01 Ubuntu 14.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-30 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 2342CTO ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu7 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.907-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x0a01 UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago) UserGroups: dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2342CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2342CTO dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Thu Jan 30 20:19:46 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 id8510 vendor AUO xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1274779/+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 1310489] Re: xorg.conf overwritten by booting system
Available here: https://launchpadlibrarian.net/186397248/gpu-manager.log -- 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/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1985 dmi.board.vendor: Hewlett-Packard dmi.board.version: 01.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version
[Desktop-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Ass
https://bugs.launchpad.net/ubuntu/+source/location- service/+bug/1337613/comments/2 ** Also affects: location-service (Ubuntu) Importance: Undecided Status: New ** Changed in: location-service (Ubuntu) Status: New = Confirmed ** Changed in: location-service (Ubuntu) Importance: Undecided = Critical ** Changed in: location-service (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. Status in DBus C++: Confirmed Status in “dbus-cpp” package in Ubuntu: Confirmed Status in “indicator-network” package in Ubuntu: Invalid Status in “location-service” package in Ubuntu: Invalid Status in “dbus-cpp” package in Ubuntu RTM: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20141015-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988 contains more details. steps to reproduce: (need to trigger race condition) 1. pull down network indicator 2. toggle flight mode on and off quickly a few times 3. click sim card 1 and 2 4. toggle flight mode 5. swipe up close indicators 6. repeat steps 1-5 until crash occurs expected results: no crash happens actual results: Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes. additional info: eventually the bluetooth indicator appears stable in the indicators at the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+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 1383468] Re: Windows in non-focused workspaces have not decorations in expo
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) -- 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/1383468 Title: Windows in non-focused workspaces have not decorations in expo Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: 1. Open multiple windows and put them in different workspaces 2. Hit Super+S to open the expo 3. Notice that windows that are not in the focused workspaces have no decorations To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1383468/+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 1383202] Re: Left touch pad button not working on Ubuntu (Gnome) 14.10 and kernel above 3.16.0-20
It seems using 3.16.0-24 from this PPA fixes the issue - https://launchpad.net/~ubuntu-kernel-test/+archive/ubuntu/devel -- 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/1383202 Title: Left touch pad button not working on Ubuntu (Gnome) 14.10 and kernel above 3.16.0-20 Status in “xorg” package in Ubuntu: Confirmed Bug description: So, I've this Lenovo B50 laptop that runs Ubuntu Gnome 14.10 and for some reason kernels: 3.16.0-23 3.16.0-22 3.16.0-21 Don't seem to recognise my left touchpad button, however it worked up to kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have installed just in case) and the touchpad is perfectly functional and the left button works like a charm. I am willing to provide any info you guys need. Oh and - left clicking works with a mouse. Also - xorg edgers PPA and using 3.17 mainline kernel don't seem to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1383202/+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 1384289] Re: mesa 10.3.1 required for mir
Removed mention of eglplasma and changed it to egltriangle. I think eglplasma has separate bugs that prevent it from working on i915. ** Description changed: There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So we would like to see the newest minor release of mesa, which is 10.3.1 This will fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and basically enable i915 devices to run mir. [Impact] - * The bug leads to crashes in unity8 on i915 and to crashes or 'black + * The bug leads to crashes in unity8 on i915 and to crashes or 'black buffers' on mir clients. - * This is not a request for back porting but a request to pick the next + * This is not a request for back porting but a request to pick the next minor bugfix release of mesa. [Test Case] - * Install mir-demos on a intel atom netbook or a pentium d system - * sudo mir_demo_server_basic --vt 2 --file /tmp/mir_socket - * sudo chmod 666 /tmp/mir_socket - * mir_demo_client_eglplasma -m /tmp/mir_socket - * then vt switch to vt 1 - * expected yellowish plasma animation, error: eglplasma crashing or just showing a black buffer + * Install mir-demos on a intel atom netbook or a pentium d system + * sudo mir_demo_server_basic --vt 2 --file /tmp/mir_socket + * sudo chmod 666 /tmp/mir_socket + * mir_demo_client_egltriangle -m /tmp/mir_socket + * then vt switch to vt 1 + Expected: Animation + Observed: Crashing or just showing a black buffer [Regression Potential] - * Instead of immediately crashing unity8s desktop session it will make + * Instead of immediately crashing unity8s desktop session it will make the primary client of unity8: unity8-dash fail to start due to insufficient GL support on the mesa driver - but that is a different error. - * 10.3.1 introduces the bespoke i915 bug fix, and further driver local fixes to nouveau for the kepler ir, shutdown leak fixes for radeon and a division by zero fix for llvmpipe. A fix to glsl that first manifested in i965. Apart from that build system cleanups for building mesa for android and detecting LLVM. - * the fix to glsl has impact on i965 - * fixes for intel are local to i915 and will not cause regression - * fixes to radeon should only touch shutdown code - * fixes to nouveau should be local to kepler gpus + * 10.3.1 introduces the bespoke i915 bug fix, and further driver local fixes to nouveau for the kepler ir, shutdown leak fixes for radeon and a division by zero fix for llvmpipe. A fix to glsl that first manifested in i965. Apart from that build system cleanups for building mesa for android and detecting LLVM. + * the fix to glsl has impact on i965 + * fixes for intel are local to i915 and will not cause regression + * fixes to radeon should only touch shutdown code + * fixes to nouveau should be local to kepler gpus [Other Info] - - * The switch to this mesa release will not enable mir. But it will not enable unity8 on pentium D and atom, but it will be a step towards that + + * The switch to this mesa release will not enable mir. But it will not + enable unity8 on pentium D and atom, but it will be a step towards that -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1384289 Title: mesa 10.3.1 required for mir Status in “mesa” package in Ubuntu: Confirmed Bug description: There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So we would like to see the newest minor release of mesa, which is 10.3.1 This will fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and basically enable i915 devices to run mir. [Impact] * The bug leads to crashes in unity8 on i915 and to crashes or 'black buffers' on mir clients. * This is not a request for back porting but a request to pick the next minor bugfix release of mesa. [Test Case] * Install mir-demos on a intel atom netbook or a pentium d system * sudo mir_demo_server_basic --vt 2 --file /tmp/mir_socket * sudo chmod 666 /tmp/mir_socket * mir_demo_client_egltriangle -m /tmp/mir_socket * then vt switch to vt 1 Expected: Animation Observed: Crashing or just showing a black buffer [Regression Potential] * Instead of immediately crashing unity8s desktop session it will make the primary client of unity8: unity8-dash fail to start due to insufficient GL support on the mesa driver - but that is a different error. * 10.3.1 introduces the bespoke i915 bug fix, and further driver local fixes to nouveau for the kepler ir, shutdown leak fixes for radeon and a division by zero fix for llvmpipe. A fix to glsl that first manifested in i965. Apart from that build system cleanups for building mesa for android and detecting LLVM. * the fix to glsl has impact on i965 * fixes for intel are local to i915 and will not cause regression *
[Desktop-packages] [Bug 1378423] Re: Virtualbox boots to black screen or corrupted screen with daily
Ubuntu GNOME Utopic Unicorn 20141022.1 RC amd64 and it is happening with me - same as the video on comment #9 I am running Xubuntu 12.04.5 and Oracle VM version 4.1.12_Ubuntu and found this one while I was testing the RC of Ubuntu GNOME. i386 of the same build works just fine and couldn't produce that on i386. -- 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/1378423 Title: Virtualbox boots to black screen or corrupted screen with daily Status in “xorg” package in Ubuntu: Confirmed Bug description: Boot the daily image. Get a black screen. Go to tty1 - lightdm has started - running sudo service lightdm status echoes start/waiting Return to tty7 and the login dialogue has now appeared ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.344 Date: Tue Oct 7 15:53:54 2014 LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006) ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1378423/+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
Wouldn't recommend the course of action in 92, I've broken wifi after reboot it won't connect, I'm going to have to reinstall the operating system. -- 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 1384741] [NEW] Lenovo X1 TouchPad intermittent/corrupt
Public bug reported: Since upgrade yesterday on 14.10 - touchpad on my Lenovo X1 Carbon is corrupted. After a reboot, it works for about 30 seconds then degrades rapidly, where cursor jumps around screen and does not follow touchpad movements. Two finger scrolling can cause right click events. cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name=Lid Switch P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name=Sleep Button P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab54 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name=SynPS/2 Synaptics TouchPad P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 I: Bus=0019 Vendor=17aa Product=5054 Version=4101 N: Name=ThinkPad Extra Buttons P: Phys=thinkpad_acpi/input0 S: Sysfs=/devices/platform/thinkpad_acpi/input/input7 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=33 B: KEY=1804 0 10 0 1501b02102004 c80021104000 10e 0 B: MSC=10 B: SW=a I: Bus=0019 Vendor= Product=0006 Version= N: Name=Video Bus P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name=HDA Intel PCH Mic P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name=HDA Intel PCH Headphone P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name=HDA Intel PCH HDMI/DP,pcm=3 P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=0eef Product=790a Version=0210 N: Name=eGalax Inc. eGalaxTouch EXC7903-66v03_T1 P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:0EEF:790A.0001/input/input12 U: Uniq= H: Handlers=mouse1 event10 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=2608003 I: Bus=0003 Vendor=5986 Product=0266 Version=1412 N: Name=Integrated Camera P: Phys=usb-:00:1a.0-1.6/button S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input14 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0011 Vendor=0002 Product=000a Version= N: Name=TPPS/2 IBM TrackPoint P: Phys=synaptics-pt/serio0/input0 S: Sysfs=/devices/platform/i8042/serio1/serio2/input/input6 U: Uniq= H: Handlers=mouse2 event12 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1384741 Title: Lenovo X1 TouchPad intermittent/corrupt Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: Since upgrade yesterday on 14.10 - touchpad on my Lenovo X1 Carbon is corrupted. After a reboot, it works for about 30 seconds then degrades rapidly, where cursor jumps around screen and does not follow touchpad movements. Two finger scrolling can cause right click events. cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name=Lid Switch P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name=Sleep Button P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P:
[Desktop-packages] [Bug 1378416] Re: [krillin] disable WiFi, Mobile Data not available
Changed ofono status to Incomplete as well until we're able to reliably reproduce. ** Changed in: network-manager (Ubuntu) Importance: Undecided = High ** Changed in: ofono (Ubuntu) Status: In Progress = Incomplete -- 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/1378416 Title: [krillin] disable WiFi, Mobile Data not available Status in “network-manager” package in Ubuntu: Incomplete Status in “ofono” package in Ubuntu: Incomplete Bug description: STEPS: 1. Install RTM88 on krillin 2. Use the system a litlle on wifi 3. Pull down the indicator network 4. Disable Wifi EXPECTED: I expect the system to seemless flip over to using 3g ACTUAL: I got no page (see screen shot) I tried pinging google and got ping: unknown host google.com ip route gave no feedback phablet@ubuntu-phablet:~$ nmcli dev DEVICE TYPE STATE /ril_1 gsm disconnected /ril_0 gsm connected wlan0 802-11-wireless unavailable Devices is correct. The debug.txt in comment #3 clearly shows that mobile data is connected via the list-modems output and list-contexts output. This output also agrees with the nmcli output which shows /ril_0 as connected. The smoking gun here looks to be the routing table, which is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1378416/+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 1384636] Re: Spurious characters on some keys
** Description changed: Xubuntu 14.04.1 on ASUS S400C laptop, since updates at the end of September I have been getting problems with some keys using En-GB with - extended WinKeys. Specifically 'p', which sends something like 'p~~' and - in Chrome opens either the print dialog or the debug console, and 'Esc' - which started sending '0sen' particularly in vi. Removing ibus seems to - have resolved the problem but if it's going to be the default keyboard - manager there's something odd there. + extended WinKeys. Specifically 'p', which sends something like '~q~-' + and in Chrome opens either the print dialog or the debug console, and + 'Esc' which started sending '0scn' particularly in vi. Removing ibus + seems to have resolved the problem but if it's going to be the default + keyboard manager there's something odd there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1384636 Title: Spurious characters on some keys Status in “ibus” package in Ubuntu: New Bug description: Xubuntu 14.04.1 on ASUS S400C laptop, since updates at the end of September I have been getting problems with some keys using En-GB with extended WinKeys. Specifically 'p', which sends something like '~q~-' and in Chrome opens either the print dialog or the debug console, and 'Esc' which started sending '0scn' particularly in vi. Removing ibus seems to have resolved the problem but if it's going to be the default keyboard manager there's something odd there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1384636/+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 1310489] Re: xorg.conf overwritten by booting system
@Alistair: the gpu-manager detected a change in the number of the available graphics cards: How many cards? 1 The number of cards has changed! It detects the following card: Vendor/Device Id: 10de:1004 BusID PCI:1@0:0:0 The gpu-manager reconfigures your xorg.conf when you physically remove, add, or disable a graphics card from the BIOS. Did you do any of this? -- 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/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Desktop-packages] [Bug 1384636] Re: Spurious characters on some keys
This is odd as it seems only to be 'p' and Esc that are affected. It has started happening again after using Skype but has not recovered after a reboot, so it may not be ibus after all. Onboard has crashed after starting in the desktop but works in LightDM. I will investigate more. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1384636 Title: Spurious characters on some keys Status in “ibus” package in Ubuntu: New Bug description: Xubuntu 14.04.1 on ASUS S400C laptop, since updates at the end of September I have been getting problems with some keys using En-GB with extended WinKeys. Specifically 'p', which sends something like '~q~-' and in Chrome opens either the print dialog or the debug console, and 'Esc' which started sending '0scn' particularly in vi. Removing ibus seems to have resolved the problem but if it's going to be the default keyboard manager there's something odd there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1384636/+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 1302885] Re: Media keyboard shortcuts not working
Sure, we will work on getting this in a Trusty SRU. ** Also affects: unity/7.2 Importance: Undecided Status: New -- 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/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Committed Status in Unity 7.2 series: New Status in “unity” package in Ubuntu: Fix Released Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 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-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.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-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+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 1295670] Re: Nautilus doesn't save items view
Any progress on this subject? The saving of the folder/items view is essential to me, so I hope there will be some action. Thanks in advance! -- 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/1295670 Title: Nautilus doesn't save items view Status in Nautilus: New Status in “nautilus” package in Ubuntu: Triaged Bug description: Nautilus Files doesn't save items view style (List or Icons view) after closing window and opening it again. Previous Nautilus release does it. The following screencast shows the bug “in action”: http://www.youtube.com/watch?v=EdrsO5Kwtlgfeature=youtu.be ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 21 17:06:24 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-03-18 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1295670/+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 1382677] Re: Xorg crashed with SIGABRT in __GI___libc_free()
The succesfull workaround for Xorg crashing on Intel GM45 integrated graphics on Lenovo T400 was to create the the following file /usr/share/X11/xorg.conf.d/20-intel-gm45.conf Section Device Identifier Intel Graphics Driver intel Option AccelMethod uxa EndSection Swtiching from SNA to UXA alleviated all the problems. As a side note, gtkperf tool is very reliable to reproduce SNA Xorg crashes. -- 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/1382677 Title: Xorg crashed with SIGABRT in __GI___libc_free() Status in “xorg-server” package in Ubuntu: New Bug description: For some reason easily triggered by Firefox 31 to 33. Chromium and other graphical applications work without problems. Firefox 28 from the live Ubuntu 14.04 usb drive, does not trigger Xorg crash. The crashes occur with the stock Xorg as well as Xorg-edgers. One of the previous crashes was slightly different. sudo gdb /usr/bin/Xorg /etc/X11/core Reading symbols from /usr/bin/Xorg...Reading symbols from /usr/lib/debug//usr/bin/Xorg...done. done. [New LWP 8247] [New LWP 8248] [New LWP 8246] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Core was generated by `/usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt'. Program terminated with signal SIGBUS, Bus error. #0 memset () at ../sysdeps/x86_64/memset.S:114 114 ../sysdeps/x86_64/memset.S: No such file or directory. (gdb) bt #0 memset () at ../sysdeps/x86_64/memset.S:114 #1 0x7f6ca68cd306 in ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so #2 0x in ?? () ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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 CrashCounter: 1 Date: Fri Oct 17 13:57:51 2014 DistUpgraded: 2014-08-19 14:00:57,964 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2012-06-22 (847 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 647341U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=cc4e5011-50ff-4db4-856e-d1ef85ab4327 ro crashkernel=384M-:128M Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI___libc_free (mem=0x) at malloc.c:2929 xf86CursorUnrealizeCursor (pDev=0x0, pScreen=0x7fdb1a212b70, pCurs=0x7fdb1a534a90) at ../../../../hw/xfree86/ramdac/xf86Cursor.c:294 AnimCurUnrealizeCursor (pDev=optimized out, pScreen=0x7fdb1a212b70, pCursor=optimized out) at ../../render/animcur.c:282 FreeCursor (value=0x7fdb1a534a90, cid=optimized out) at ../../dix/cursor.c:124 ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so Title: Xorg crashed with SIGABRT in __GI___libc_free() UpgradeStatus: Upgraded to trusty on 2014-08-19 (58 days ago) UserGroups: dmi.bios.date: 10/10/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7VET95WW (3.25 ) dmi.board.name: 647341U 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:bvr7VET95WW(3.25):bd10/10/2012:svnLENOVO:pn647341U:pvrThinkPadT400:rvnLENOVO:rn647341U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 647341U dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git20141006.00847fa4-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0~git20141017.9ebfb301-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.0~git20141017.9ebfb301-0ubuntu0ricotz~trusty
[Desktop-packages] [Bug 1383449] Re: Xorg crashed with signal 7 in start_thread()
*** This bug is a duplicate of bug 1382677 *** https://bugs.launchpad.net/bugs/1382677 The succesfull workaround for Xorg crashing on Intel GM45 integrated graphics on Lenovo T400 was to create the the following file /usr/share/X11/xorg.conf.d/20-intel-gm45.conf Section Device Identifier Intel Graphics Driver intel Option AccelMethod uxa EndSection Swtiching from SNA to UXA alleviated all the problems. As a side note, gtkperf tool is very reliable to reproduce SNA Xorg crashes. ** This bug has been marked a duplicate of bug 1382677 Xorg crashed with SIGABRT in __GI___libc_free() -- 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/1383449 Title: Xorg crashed with signal 7 in start_thread() Status in “xorg-server” package in Ubuntu: New Bug description: Tried to use gdb to catch it, however the virtual ttys are blacked out, not frozen, thus could not do anything with it. If someone can give me a practical advice on how to back-trace Xorg, I could help to troubleshoot it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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 CrashCounter: 1 Date: Mon Oct 20 12:28:56 2014 DistUpgraded: 2014-08-19 14:00:57,964 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2012-06-22 (850 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 647341U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=cc4e5011-50ff-4db4-856e-d1ef85ab4327 ro crashkernel=384M-:128M Signal: 7 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so start_thread (arg=0x7f5a1f2ac700) at pthread_create.c:312 Title: Xorg crashed with signal 7 in start_thread() UpgradeStatus: Upgraded to trusty on 2014-08-19 (61 days ago) UserGroups: dmi.bios.date: 10/10/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7VET95WW (3.25 ) dmi.board.name: 647341U 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:bvr7VET95WW(3.25):bd10/10/2012:svnLENOVO:pn647341U:pvrThinkPadT400:rvnLENOVO:rn647341U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 647341U dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Oct 20 12:29:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16437 vendor LEN xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1383449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1384250] [NEW] Issue with windows not displaying in Ubuntu Trusty 14.04
You have been subscribed to a public bug: I've got a Lenovo All-in-One pc and recently upgraded from the previous long term distribution. I've hit on the following problem. When a sub-window of say Firefox is called up, the window loads, and I can see it in the quick scroll function that it has loaded. However, I can't then access this new window. I can close it down using the open window tab function. With Gimp, this means that I can't currently use it. With Librecalc when I tried to do a pivot table I can't access the options window that loads up with the command options, although I can see it scrolling through the open windows with Alt+Tab. Seems to be an issue irrespective of the programme I'm trying to use. Grateful for any help you can offer. I did try to use apport but that crashed when I was trying to submit it. ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Issue with windows not displaying in Ubuntu Trusty 14.04 https://bugs.launchpad.net/bugs/1384250 You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity 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 1384250] Re: Issue with windows not displaying in Ubuntu Trusty 14.04
** Package changed: ubuntu = metacity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1384250 Title: Issue with windows not displaying in Ubuntu Trusty 14.04 Status in “metacity” package in Ubuntu: New Bug description: I've got a Lenovo All-in-One pc and recently upgraded from the previous long term distribution. I've hit on the following problem. When a sub-window of say Firefox is called up, the window loads, and I can see it in the quick scroll function that it has loaded. However, I can't then access this new window. I can close it down using the open window tab function. With Gimp, this means that I can't currently use it. With Librecalc when I tried to do a pivot table I can't access the options window that loads up with the command options, although I can see it scrolling through the open windows with Alt+Tab. Seems to be an issue irrespective of the programme I'm trying to use. Grateful for any help you can offer. I did try to use apport but that crashed when I was trying to submit it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1384250/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Any news on a fix ?!? this is critical, not being able to use WINE in a deployment setting is a big NO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in “boinc” package in Ubuntu: Fix Released Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Status in “nvidia-cuda-toolkit” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-310-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-313-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pycuda” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “starpu-contrib” package in Ubuntu: Fix Released Status in “viennacl” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1384802] [NEW] [USB-Audio - DigiHug USB Audio, playback] No sound at all
Public bug reported: Since apt-get upgrading, my USB Fiio E10 Olympus outputs no sound on Ubuntu 14.10. However, I was able to hear the two signals from ubuntu-bug -s audio. Another USB audio device (a logitech headphone) works fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhajduk2814 F pulseaudio /dev/snd/controlC1: bhajduk2814 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 23 18:05:59 2014 InstallationDate: Installed on 2012-05-03 (903 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: DigiHug USB Audio - DigiHug USB Audio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhajduk2814 F pulseaudio /dev/snd/controlC1: bhajduk2814 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - DigiHug USB Audio, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-04-22 (184 days ago) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1384802 Title: [USB-Audio - DigiHug USB Audio, playback] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Since apt-get upgrading, my USB Fiio E10 Olympus outputs no sound on Ubuntu 14.10. However, I was able to hear the two signals from ubuntu-bug -s audio. Another USB audio device (a logitech headphone) works fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhajduk2814 F pulseaudio /dev/snd/controlC1: bhajduk2814 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 23 18:05:59 2014 InstallationDate: Installed on 2012-05-03 (903 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: DigiHug USB Audio - DigiHug USB Audio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhajduk2814 F pulseaudio /dev/snd/controlC1: bhajduk2814 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - DigiHug USB Audio, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-04-22 (184 days ago) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1384802/+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 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN
Switched to a MacBook Pro with OS X 10.9 and that solved the issue very nicely for me (also a big number of other Ubuntu-bugs). So that is my best tips to anyone still hoping to see this get fixed, switch away from Ubuntu because this bug is from 2008! -- 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/264691 Title: Please add NM option for connecting to L2TP IPSEC VPN Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” package in Debian: Invalid Bug description: Binary package hint: network-manager Missing feature: You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network Manager. The server I want to connect to expects a login / password and a PSK. When you do a connection in XP you can see the following details on a connection: Device name: L2TP Server type: PPP Authentication: MS CHAP v2 IPSEC Encryption: IPSEC ESP 3DES Compression: MPPC To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264691/+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 1384802] Re: [USB-Audio - DigiHug USB Audio, playback] No sound at all
I close this. The bug disappeared after several shutdowns (not the two first ones). ** Changed in: alsa-driver (Ubuntu) Status: New = Invalid -- 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/1384802 Title: [USB-Audio - DigiHug USB Audio, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Invalid Bug description: Since apt-get upgrading, my USB Fiio E10 Olympus outputs no sound on Ubuntu 14.10. However, I was able to hear the two signals from ubuntu-bug -s audio. Another USB audio device (a logitech headphone) works fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhajduk2814 F pulseaudio /dev/snd/controlC1: bhajduk2814 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 23 18:05:59 2014 InstallationDate: Installed on 2012-05-03 (903 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: DigiHug USB Audio - DigiHug USB Audio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhajduk2814 F pulseaudio /dev/snd/controlC1: bhajduk2814 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - DigiHug USB Audio, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-04-22 (184 days ago) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1384802/+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 1384823] [NEW] [wifi] Enable the use of nl80211 power save mode when available
Public bug reported: NetworkManager should enable power save on wireless devices that support it. This is done by the NL80211_CMD_SET_POWER_SAVE command. Note; ideally powersave should not be enabled while doing an association, since it can interfere (cause delays) in things like DHCP requests/responses, etc. Best might be to enable it once the device is fully activated, and remove it once we're in a disconnected state. ** Affects: network-manager (Ubuntu) Importance: High Assignee: Mathieu Trudel-Lapierre (mathieu-tl) Status: In Progress ** Changed in: network-manager (Ubuntu) Status: New = In Progress ** Changed in: network-manager (Ubuntu) Importance: Undecided = High ** Changed in: network-manager (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 in Ubuntu. https://bugs.launchpad.net/bugs/1384823 Title: [wifi] Enable the use of nl80211 power save mode when available Status in “network-manager” package in Ubuntu: In Progress Bug description: NetworkManager should enable power save on wireless devices that support it. This is done by the NL80211_CMD_SET_POWER_SAVE command. Note; ideally powersave should not be enabled while doing an association, since it can interfere (cause delays) in things like DHCP requests/responses, etc. Best might be to enable it once the device is fully activated, and remove it once we're in a disconnected state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384823/+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 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Ass
To clarify: The message router likely resolves to an already dead object, and the access to the associated mutex is undefined behavior as the member has been freed when the respective object died away before. I'm proposing a change to dbus-cpp to robustify handling of such situations. However, downstream projects should make sure that they clean up correctly dynamically created objects. ** Branch linked: lp:~thomas-voss/dbus-cpp/robustify-against-dead- objects-hanging-around ** Changed in: location-service (Ubuntu) Status: Invalid = Confirmed ** Changed in: location-service (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. Status in DBus C++: Confirmed Status in “dbus-cpp” package in Ubuntu: Confirmed Status in “indicator-network” package in Ubuntu: Invalid Status in “location-service” package in Ubuntu: Confirmed Status in “dbus-cpp” package in Ubuntu RTM: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20141015-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988 contains more details. steps to reproduce: (need to trigger race condition) 1. pull down network indicator 2. toggle flight mode on and off quickly a few times 3. click sim card 1 and 2 4. toggle flight mode 5. swipe up close indicators 6. repeat steps 1-5 until crash occurs expected results: no crash happens actual results: Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes. additional info: eventually the bluetooth indicator appears stable in the indicators at the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+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 1384823] Re: [wifi] Enable the use of nl80211 power save mode when available
Marked as High since it's a critical on the phone, to reduce power consumption in deep sleep. Related to bug 1367745. -- 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/1384823 Title: [wifi] Enable the use of nl80211 power save mode when available Status in “network-manager” package in Ubuntu: In Progress Bug description: NetworkManager should enable power save on wireless devices that support it. This is done by the NL80211_CMD_SET_POWER_SAVE command. Note; ideally powersave should not be enabled while doing an association, since it can interfere (cause delays) in things like DHCP requests/responses, etc. Best might be to enable it once the device is fully activated, and remove it once we're in a disconnected state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384823/+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 1355041] Re: [SRU] fglrx dependencies had conflicts in 12.04.5(kernel 3.13)
This bug was fixed in the package fglrx-installer-updates - 2:13.350.1-0ubuntu0.0.1 --- fglrx-installer-updates (2:13.350.1-0ubuntu0.0.1) precise-proposed; urgency=medium * debian/control, debian/fglrx-amdcccle-updates.install.in: - Use pkexec for amdcccle when running Unity, and add a dependency on polkit-1. * debian/dkms.conf.in, debian/dkms/patches/buildfix_kernel_3.15.patch, debian/dkms/patches/buildfix_kernel_3.14.patch: - Add support for Linux 3.14 (LP: #1355041). - Add support for Linux 3.15. * debian/patches/call-amdcccle-with-full-path.diff: - Pass amdxdg the full path. * debian/substvars: - Add support for X ABI 15 and for lts-trusty. -- Alberto Milone alberto.mil...@canonical.com Wed, 08 Oct 2014 08:55:08 +0200 ** Changed in: fglrx-installer-updates (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1355041 Title: [SRU] fglrx dependencies had conflicts in 12.04.5(kernel 3.13) Status in HWE Next Project: Invalid Status in HWE Next precise series: Confirmed Status in “fglrx-installer” package in Ubuntu: Invalid Status in “fglrx-installer-updates” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: Fix Released Status in “fglrx-installer-updates” source package in Precise: Fix Released Bug description: [Impact] fglrx cannot be installed on 12.04.5 as it has a new X and dependency cannot be satisfied. [Test case] To test the installation of fglrx on a 12.04.5 machine if it succeeds or not, if it does check if the driver performs correctly. [Regression potential] -- Trying to install fglrx from console but got following message: ubuntu@201209-11726:~$ sudo apt-get install fglrx Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fglrx : Depends: xorg-video-abi-11 or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 or xorg-video-abi-14 E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 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 Date: Mon Aug 11 03:32:26 2014 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-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 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:184c] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=c1336d4c-028e-4d9c-975a-152b6183a869 ro quiet splash initcall_debug vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 184C dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.34 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr089D1100501020100:rvnHewlett-Packard:rn184C:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g7 Notebook PC dmi.product.version: 089D1100501020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu4 version.ia32-libs: ia32-libs N/A
[Desktop-packages] [Bug 1378423] Re: Virtualbox boots to black screen or corrupted screen with daily
** Changed in: xorg (Ubuntu) Status: Confirmed = Fix Released -- 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/1378423 Title: Virtualbox boots to black screen or corrupted screen with daily Status in “xorg” package in Ubuntu: Fix Released Bug description: Boot the daily image. Get a black screen. Go to tty1 - lightdm has started - running sudo service lightdm status echoes start/waiting Return to tty7 and the login dialogue has now appeared ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.344 Date: Tue Oct 7 15:53:54 2014 LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006) ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1378423/+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 1384852] [NEW] nvidia error
Public bug reported: nvidia driver error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Oct 23 19:11:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed nvidia-331, 331.89, 3.13.0-36-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83b5] InstallationDate: Installed on 2014-06-03 (142 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: System manufacturer P5K Deluxe ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=0949e2ad-fe03-4f55-9c3a-3df0afeed354 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1005 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd12/16/2008:svnSystemmanufacturer:pnP5KDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K Deluxe dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git20141006.00847fa4-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0~git20141023.065256df-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.0~git20141023.065256df-0ubuntu0ricotz~trusty version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141016.6b98f162-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20140904.3cd4c849-0ubuntu0sarvatt~trusty xserver.bootTime: Thu Oct 23 19:00:44 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMOSART Semi. 2.4G Wireless Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages 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/1384852 Title: nvidia error Status in “xorg” package in Ubuntu: New Bug description: nvidia driver error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Oct 23 19:11:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu
[Desktop-packages] [Bug 1156398] Re: scp-dbus-service creates 100s of thousands symlinks to the ppd-file in /tmp untill the root filesystem runs out of inodes everytime I print something
** Changed in: system-config-printer (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1156398 Title: scp-dbus-service creates 100s of thousands symlinks to the ppd-file in /tmp untill the root filesystem runs out of inodes everytime I print something Status in “system-config-printer” package in Ubuntu: Confirmed Status in “system-config-printer” package in Debian: Fix Released Bug description: When I print e.g. a webpage in Firefox, shortly after the printing finished, the root filesystem is running out of available inodes. /tmp/ is populated with hundreds of thousands of symlinks to /etc/cups/ppd/Hewlett-Packard-hp-LaserJet-4350.ppd which are all named like 51465 (where x is a hexadecimal digit) and are created at a rate of aprox. 1500 new symlinks per second. The filenames are not counted up but seem to appear in random order. During this time the process /usr/bin/python /usr/share/system- config-printer/scp-dbus-service.py is using ~130% CPU. As soon as I kill this process, no more symlinks are created. When I wait for the inodes to run out, this process's CPU usage drops to ~7% for a few seconds before the process suddenly disapears from the process list. This indicates that all the symlinks are created by this one process. If I delete the symlinks now and print another document, things start over again. ---+ Furher notes This does not happen when printing with lpr gv It does happen when printing with Firefox Chromium LibreOffice An unpriviledged user could break down the system by filling up all free inodes on the root fs, so this might be security relevant. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: system-config-printer-common 1.3.11+20120807-0ubuntu10 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: openafs fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 18 00:45:56 2013 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Transport endpoint is not connected MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H MarkForUpload: True PackageArchitecture: all Papersize: letter PpdFiles: Hewlett-Packard-hp-LaserJet-4350: HP LaserJet 4350 pcl3, hpcups 3.12.2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-25-generic root=/dev/mapper/hostname-root ro splash quiet vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-A75M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/03/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1156398/+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 1373802] Re: Regression: chromium-browser no longer loads policies in 37.0.2062.120-0ubuntu0.14.04.1~pkg1049
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New = Confirmed -- 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/1373802 Title: Regression: chromium-browser no longer loads policies in 37.0.2062.120-0ubuntu0.14.04.1~pkg1049 Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Release: Ubuntu 14.04 Package: chromium-browser_37.0.2062.120-0ubuntu0.14.04.1~pkg1049 After updating to the latest version indicated above this morning I found out that this version no longer loads my configured policies from /etc/chromium-browser/policies/*. Running 'strings /usr/lib/chromium-browser/chromium-browser|grep policies' I noticed that in the new version the path vor policies changed to /etc/chromium/policies. After creating a symlink /etc/chromium - chromium-browser and restarting the browser my policies were loaded again. I think this is a serious regression from the previous version (37.0.2062.94-0ubuntu0.14.04.1~pkg1042) for enterprise users where we want to lock down certain features in the browser and after this security update suddenly all policies are not loaded/enforced anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1373802/+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 1373802] Re: Regression: chromium-browser no longer loads policies in 37.0.2062.120-0ubuntu0.14.04.1~pkg1049
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) = Chad Miller (cmiller) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided = Critical -- 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/1373802 Title: Regression: chromium-browser no longer loads policies in 37.0.2062.120-0ubuntu0.14.04.1~pkg1049 Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Release: Ubuntu 14.04 Package: chromium-browser_37.0.2062.120-0ubuntu0.14.04.1~pkg1049 After updating to the latest version indicated above this morning I found out that this version no longer loads my configured policies from /etc/chromium-browser/policies/*. Running 'strings /usr/lib/chromium-browser/chromium-browser|grep policies' I noticed that in the new version the path vor policies changed to /etc/chromium/policies. After creating a symlink /etc/chromium - chromium-browser and restarting the browser my policies were loaded again. I think this is a serious regression from the previous version (37.0.2062.94-0ubuntu0.14.04.1~pkg1042) for enterprise users where we want to lock down certain features in the browser and after this security update suddenly all policies are not loaded/enforced anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1373802/+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 1384860] Re: reconfiguring Ubuntu
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1384860 Title: reconfiguring Ubuntu Status in “xorg” package in Ubuntu: New Bug description: System got into critical failure after I have download some apps from Ubuntu Software Centre 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 Date: Thu Oct 23 19:13:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:18fa] InstallationDate: Installed on 2014-10-23 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion Sleekbook 14 PC ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash 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: 08/10/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 18FA dmi.board.vendor: Hewlett-Packard dmi.board.version: 82.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.00:bd08/10/2012:svnHewlett-Packard:pnHPPavilionSleekbook14PC:pvr087E103B590320100:rvnHewlett-Packard:rn18FA:rvr82.10:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Sleekbook 14 PC dmi.product.version: 087E103B590320100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Oct 23 15:28:52 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 831 vendor LGD xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1384860/+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 1214066] Re: phoronix benchmarks on nouveau is 4 times slower today than it was last thursday
** Changed in: xorg (Ubuntu) Status: In Progress = Fix Committed -- 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/1214066 Title: phoronix benchmarks on nouveau is 4 times slower today than it was last thursday Status in “xorg” package in Ubuntu: Fix Committed Bug description: Description phoronix benchmarks on nouveau is 4 times slower today than it was last thursday * this is with both xmir and plain xorg steps: 1. install saucy from 20130815 on system using nvidia card (I am using two different systems nvidia gt640 and nvidia gt440) 2. sudo apt-get install phoronix-test-suite 3 phoronix-test-suite install openarena 4 phoronix-test-suite run openarena 5. install saucy from 20130819 6. sudo apt-get install phoronix-test-suite 7 phoronix-test-suite install openarena 8 phoronix-test-suite run openarena expected results test results from 20130819 image are about the same or better than 20130815 image actual results: test results from 20130819 image are about 4 times worse ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Aug 19 17:49:00 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:838a] InstallationDate: Installed on 2013-08-19 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130818) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=47d5d3bb-9722-4bd4-8d63-e13352d65c1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904 dmi.board.name: DZ77BH-55K dmi.board.vendor: Intel Corporation dmi.board.version: AAG39008-400 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr: version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu1 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-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3 xserver.bootTime: Mon Aug 19 16:39:23 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRaritan D2CIM-DVUSB KEYBOARD, id 8 inputRaritan D2CIM-DVUSB MOUSE, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2.901-2ubuntu1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214066/+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 1102001] Re: CUPS recommends incorrect driver for Samsung ML-1670
** Also affects: splix (Unity Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/1102001 Title: CUPS recommends incorrect driver for Samsung ML-1670 Status in “splix” package in Ubuntu: Incomplete Status in “splix” package in Unity Linux: New Bug description: STR: 1) From the Printers dialogue, select Add Printer. 2) Select Samsung ML-1670 from the devices list (connected via USB) 3) Select Select printer from database and Samsung (recommended) 4) Select ML-1660 (recommended) from the Models, and Samsung ML-1660, 2.0.0 [en] (recommended) from Drivers 5) Click through and Apply 6) Print a test page The test page isn't printed. Instead a plain text page is printed that says: INTERNAL ERROR - Please use the proper driver. POSITION : 0x0 (0) SYSTEM : h6fw_5.49/xl_op LINE : 180 VERSION : SPL 5.49 10-20-2010 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CheckboxSubmission: dd3689fa6394f60ec14dbe98d0bab891 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Sun Jan 20 10:25:54 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (880 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) KernLog: Jan 20 09:59:31 sixtymilesmile kernel: [54885.307388] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 20 09:59:31 sixtymilesmile kernel: [54885.308453] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Lpstat: device for Phaser-6100: usb://Xerox/Phaser%206100?serial=REP167734... device for Samsung-ML-1670-Series: usb://Samsung/ML-1670%20Series?serial=Z6GEBKFB502893V. device for Xerox-Phaser-6100: ipps://xerox/printers/raw device for Xerox-Xerox-Phaser-6100DN: dnssd://Xerox%20Phaser%206100DN%20(XRXf0ae4d08)._printer._tcp.local/ MachineType: Sony Corporation VPCF11J0E MarkForUpload: True Papersize: a4 PpdFiles: Samsung-ML-1670-Series: Samsung ML-1660, 2.0.0 Xerox-Xerox-Phaser-6100DN: Xerox Phaser 6100, 2.0.0 Phaser-6100: Xerox Phaser 6100 Foomatic/Postscript Xerox-Phaser-6100: Xerox Phaser 6100, 2.0.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/hostname-root ro acpi_sleep=nonvs splash quiet nomodeset xbmc=autostart,nodiskmount loglevel=0 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-11-05 (75 days ago) dmi.bios.date: 02/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0260Y6 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0260Y6:bd02/26/2010:svnSonyCorporation:pnVPCF11J0E:pvrC604LLNJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF11J0E dmi.product.version: C604LLNJ dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/1102001/+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 929967] Re: compiz crashed with SIGSEGV in unity::panel::Style::GetStyleContext() from unity::PanelIndicatorEntryView::Refresh() from sigc::internal::slot_call0::call_it() fr
** Changed in: unity Status: Confirmed = Incomplete ** Changed in: unity (Ubuntu) Status: Confirmed = Incomplete ** Changed in: unity Status: Incomplete = Fix Released ** Changed in: unity (Ubuntu) Status: Incomplete = 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/929967 Title: compiz crashed with SIGSEGV in unity::panel::Style::GetStyleContext() from unity::PanelIndicatorEntryView::Refresh() from sigc::internal::slot_call0::call_it() from unity::indicator::Entry::setLabel() Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Crashed while surfing the Internets. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5 Uname: Linux 3.2.0-15-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Thu Feb 9 23:23:24 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110921.2) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0xb49f6d04 _ZN5unity5panel5Style15GetStyleContextEv+4: mov0x8(%eax),%eax PC (0xb49f6d04) ok source 0x8(%eax) (0x0008) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: unity::panel::Style::GetStyleContext() () from /usr/lib/compiz/libunityshell.so unity::PanelIndicatorEntryView::Refresh() () from /usr/lib/compiz/libunityshell.so sigc::internal::slot_call0sigc::bound_mem_functor0void, unity::PanelIndicatorEntryView, void::call_it(sigc::internal::slot_rep*) () from /usr/lib/compiz/libunityshell.so unity::indicator::Entry::setLabel(std::string const, bool, bool) () from /usr/lib/libunity-core-5.0.so.5 ?? () from /usr/lib/libunity-core-5.0.so.5 Title: compiz crashed with SIGSEGV in unity::panel::Style::GetStyleContext() UpgradeStatus: Upgraded to precise on 2012-01-13 (27 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/929967/+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 932748] Re: compiz crashed with SIGSEGV in compute_image_info() from ... from cairo_fill() from PlacesVScrollBar::UpdateTexture() from PlacesVScrollBar::PostLayoutManagement()
** No longer affects: nux ** No longer affects: unity/5.0 ** No longer affects: unity/6.0 ** Changed in: unity Status: Confirmed = Invalid ** No longer affects: nux (Ubuntu) ** No longer affects: unity (Ubuntu) -- 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/932748 Title: compiz crashed with SIGSEGV in compute_image_info() from ... from cairo_fill() from PlacesVScrollBar::UpdateTexture() from PlacesVScrollBar::PostLayoutManagement() from nux::View::ComputeContentSize() Status in Unity: Invalid Bug description: it happens just after starting session (login). I was trying to open dash with keyboard and then it crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: libnux-2.0-0 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Wed Feb 15 16:25:19 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64+mac (20120112) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7232690c22:mov0x18(%rdx),%r11d PC (0x7f7232690c22) ok source 0x18(%rdx) (0x0079) not located in a known VMA region (needed readable region)! destination %r11d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nux StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 pixman_image_composite32 () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in pixman_image_composite32() 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/unity/+bug/932748/+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 1159724] Re: Error setting extended attribute 'xdg.origin.url' while saving a duplicate
Definitely not a duplicate of that evince bug. The two bugs don't seem remotely related. I clicked to remove the linked duplicate, thinking it wouldn't work since I'm not an admin or anything and it removed! This needs reporting to Xfce bug tracker. I will do so if no-one else has by next week. ** This bug is no longer a duplicate of bug 1096837 [apparmor] Evince does not save files to external disks unless I rename them with the .pdf extension -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1159724 Title: Error setting extended attribute 'xdg.origin.url' while saving a duplicate Status in Thunar file manager: New Status in “evince” package in Ubuntu: Confirmed Bug description: When I download a file from Chromium by choosing the open option (so the file is saved in /tmp AFAIK), when I do a file-save copy... I get this error in the red ribbon: Error setting extended attribute 'xdg.origin.url': Operation not supported The file seems to save fine, though, so there seems to be no reason for this error notification. Don't know if it makes a difference, but my /tmp is set to mount in memory, since I run a SSD. This is my fstab entry: tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 Expected behaviour - no error notification. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 11:43:48 2013 InstallationDate: Installed on 2012-10-19 (156 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1159724/+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 1384776] Re: Occasional hang in unity 8 dash on the phone
Added a network-manager task, as we need it to export a PrimaryConnectionType property which unity8 could then use... ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New = In Progress ** Changed in: network-manager (Ubuntu) Importance: Undecided = High ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Ryan Lortie (desrt) -- 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/1384776 Title: Occasional hang in unity 8 dash on the phone Status in “network-manager” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: New Bug description: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+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 1384878] [NEW] package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed'
Public bug reported: NVIDIA aditional drivers 338 install , after theres is only a color screen with no menu, nothing at all ? Ubuntu 14.10 amd64 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Thu Oct 23 21:09:31 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2014-10-23 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade utopic -- 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/1384878 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: NVIDIA aditional drivers 338 install , after theres is only a color screen with no menu, nothing at all ? Ubuntu 14.10 amd64 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Thu Oct 23 21:09:31 2014 DuplicateSignature: package:nvidia-331:331.89-0ubuntu5:package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2014-10-23 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.89-0ubuntu5 failed to install/upgrade: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1384878/+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
