[Desktop-packages] [Bug 1442312] Re: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build have had problem using Ubuntu recommended Nividia module
This is a persistent problem with a standard graphics driver. I experienced it with previous versions. However, this is the most dramatic so far. Get the manufacturer to make the changes. -- 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/1442312 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build have had problem using Ubuntu recommended Nividia module Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: This has been an ongoing problem. I use two displays. I have seen this problem dozens of times. I was hoping you would have come up with a solution by recommending a compatible Nividia driver. My system hangs at times. This is a real pain. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 DKMSKernelVersion: 3.16.0-34-generic Date: Thu Apr 9 11:12:42 2015 InstallationDate: Installed on 2015-02-27 (41 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm 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/1442312/+subscriptions -- Mailing list: https://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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: New Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://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 1442170] [NEW] Ubuntu 14.10 not work with Kernel 3.19
Public bug reported: Ubuntu 14.10 not work with kernel 3.19. When computer started, the system tightly hangs. The system does not respond to mouse and keyboard. I'am using videodriver nvidia-304. but with Novuau driver system not work too. I'am download kernel with http://kernel.ubuntu.com Ubuntu 14.10 Video: Nvidia GeForce 8100 (720a) videodriver: nvidia-304 ** Affects: software-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1442170 Title: Ubuntu 14.10 not work with Kernel 3.19 Status in software-center package in Ubuntu: New Bug description: Ubuntu 14.10 not work with kernel 3.19. When computer started, the system tightly hangs. The system does not respond to mouse and keyboard. I'am using videodriver nvidia-304. but with Novuau driver system not work too. I'am download kernel with http://kernel.ubuntu.com Ubuntu 14.10 Video: Nvidia GeForce 8100 (720a) videodriver: nvidia-304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1442170/+subscriptions -- Mailing list: https://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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
I am a little puzzled as to why this bug affected me as I don't have nvidia hardware. -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://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 1425447] Re: pulseaudio crashed with SIGABRT in core_free() at login
That issue is ranked high enough on e.u.c, Luke, could you have a look and upstream it at least? ** Changed in: pulseaudio (Ubuntu) Importance: Medium = High ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Luke Yelavich (themuso) -- 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/1425447 Title: pulseaudio crashed with SIGABRT in core_free() at login Status in PulseAudio sound server: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Fedora: Unknown Bug description: When I login, I get no sound, a Dummy Output device which is not functional, and then an error report about this. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Wed Feb 25 03:14:39 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2013-09-29 (513 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1425447/+subscriptions -- Mailing list: https://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 1442207] Re: Wrong (work-)week start for pt_PT
Hi Gunnar. (Congratulations on your membership by the way!) I have not used Ubuntu in a couple of years over irreconcilable design-related differences. During this time I distro-hopped around Debian, Fedora and perhaps two Ubuntu derivatives, and as far as I could tell, this issue was present in all these distributions (and upstream). In the newer (hehe) Debian sources I could find a first_weekday but no first_workday. (via http://sources.debian.net) And I could not find these entries in Ubuntu's glibc 2.21 sources... Could you tell me where are these definitions stored in the latest sources? Sorry for the trouble. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to langpack-locales in Ubuntu. https://bugs.launchpad.net/bugs/1442207 Title: Wrong (work-)week start for pt_PT Status in langpack-locales package in Ubuntu: Invalid Bug description: According to the default pt_PT definitions, the (work-)week start is set at Sunday, which is incorrect. The correct (work-)week start is Monday, because Portugal abides by EN 28601:1992, since it became an European Union member 6 years prior to issue of that norm. pt_PT was the only European Union locale that did not get the needed correction in these definitions. Therefore I request to have the first_weekday and first_workday entries entries set at LC_TIME with the default value of 2 (which stands for Monday) for the pt_PT locale. Thank you. Post Scriptum: There is no need for Ubuntu/package version information because this bug is quite ancient (20+ years?) and precedes the birth of the Ubuntu distribution. I opened a bug-report entry upstream at the following location: https://sourceware.org/bugzilla/show_bug.cgi?id=17565 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1442207/+subscriptions -- Mailing list: https://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 1442336] [NEW] package joystick 1:1.4.7-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: contacted original writer of the emudev, jstest, etc. packages probably a problem with the gameport to usb adaptor he said. MS Sidewinder 3d pro has an analog switch tho but it still didn't work. :( ProblemType: Package DistroRelease: Ubuntu 14.10 Package: joystick 1:1.4.7-2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Thu Apr 2 19:26:46 2015 DuplicateSignature: package:joystick:1:1.4.7-2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-12 (87 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: joystick Title: package joystick 1:1.4.7-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2015-01-16 (83 days ago) ** Affects: joystick (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to joystick in Ubuntu. https://bugs.launchpad.net/bugs/1442336 Title: package joystick 1:1.4.7-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in joystick package in Ubuntu: New Bug description: contacted original writer of the emudev, jstest, etc. packages probably a problem with the gameport to usb adaptor he said. MS Sidewinder 3d pro has an analog switch tho but it still didn't work. :( ProblemType: Package DistroRelease: Ubuntu 14.10 Package: joystick 1:1.4.7-2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Thu Apr 2 19:26:46 2015 DuplicateSignature: package:joystick:1:1.4.7-2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-12 (87 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: joystick Title: package joystick 1:1.4.7-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2015-01-16 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/joystick/+bug/1442336/+subscriptions -- Mailing list: https://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 1416081] Re: (FreeNX/X2Go) gnome-session crashed with SIGSEGV in gnome_idle_monitor_get_idletime()
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1416081 Title: (FreeNX/X2Go) gnome-session crashed with SIGSEGV in gnome_idle_monitor_get_idletime() Status in gnome-desktop3 package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Committed Status in unity-settings-daemon source package in Trusty: Invalid Status in gnome-desktop3 source package in Utopic: Invalid Status in unity-settings-daemon source package in Utopic: Fix Committed Status in gnome-desktop3 source package in Vivid: Invalid Status in unity-settings-daemon source package in Vivid: Fix Released Bug description: SRU justification: [Impact] * The NX server (and derivatives e.g. FreeNX, X2Go) and Xvnc server (and derivatives e.g. tightvncserver, xrdp) do not support the IDLETIME counter. Violating the assumption that this is available leads to gnome-session (in trusty) or unity-settings-daemon (in utopic) crashing when trying to set up an idle monitor. * This bug renders GNOME Flashback unusable on the mentioned X servers. Per the justification in bug 1251281, these collectively affect quite a few users, particularly on the LTS which tends to be chosen when setting up a terminal server. * The proposed patch adds missing precondition checks to gnome_idle_monitor_get_idletime, avoiding the crash. Other public entry points to the idle monitor library already have similar checks. [Test Case] * Install gnome-session-flashback, tightvncserver, and vncviewer. * If bug 1251281 is not fixed in -updates yet: install gnome-session- bin from -proposed (needed for --disable-acceleration-check). * Create ~/.vnc/xstartup with the following content (3 lines): #!/bin/sh export STARTUP=gnome-session --session=gnome-flashback --disable-acceleration-check exec /etc/X11/Xsession * Make it executable: chmod +x ~/.vnc/xstartup * Log out from the desktop, log in on a tty, and run: vncserver :1 * Log in to the desktop as a guest, and run: vncviewer :1 Expected results: a GNOME Flashback VNC session is started. Actual results: - trusty: gnome-session crashes on startup. - utopic: gnome-session starts, but unity-settings-daemon crashes, so gnome-session gives up shortly after (because it's a required component). [Regression Potential] * The patch was accepted in unity-settings-daemon for vivid and there were no regression reports so far. * There should be no changes observed under a conventional local (Xorg) session. [Other Info] * Packages for testing are available in ppa:rtandy/flashback. So far at least one user reported success using those packages in comment 68 on bug 1251281. Original description: The X server used by FreeNX and X2Go does not support the IDLETIME counter. This eventually leads to a NULL pointer dereference by gnome- session due to a missing parameter check in gnome_idle_monitor_get_idletime. This renders GNOME Flashback unusable via FreeNX/X2Go in Trusty. Utopic and newer are not affected and the patch is not applicable as the GnomeIdleMonitor implementation was rewritten. Saucy is also affected but is EOL, however I would like to fix this in Trusty as the patch is tiny and IMO obviously correct. This and bug #1251281 are the only bugs preventing GNOME Flashback being used via FreeNX/X2Go in Trusty; and the latter has an easy workaround (divert the acceleration-check helper and replace it with /bin/true) and may be fixed properly soon. I would be happy to prepare a debdiff and fill out the SRU template if a sponsor agrees that the patch is SRUable. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-session-bin 3.9.90-0ubuntu12 [modified: usr/lib/gnome-session/gnome-session-check-accelerated usr/lib/gnome-session/gnome-session-check-accelerated-helper] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CasperVersion: 1.340 Date: Thu Jan 29 19:28:42 2015 ExecutablePath: /usr/bin/gnome-session ExecutableTimestamp: 1394758239 LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: /usr/bin/gnome-session --session=gnome-flashback ProcCwd: /home/ubuntu ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash LD_LIBRARY_PATH=set SegvAnalysis: Segfault happened at: 0x7fb690b29196 gnome_idle_monitor_get_idletime+6: mov0x18(%rdi),%rax PC (0x7fb690b29196) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rax ok
[Desktop-packages] [Bug 1442169] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1442169 Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() Status in cups package in Ubuntu: New Bug description: ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-daemon 2.0.2-1ubuntu3 ProcVersionSignature: Error: [Errno 2] File o directory non esistente: '/proc/version_signature' Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CupsErrorLog: W [09/Apr/2015:15:58:06 +0200] CreateProfile failed: org.freedesktop.DBus.Error.NoReply: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. Date: Sat Apr 4 11:48:06 2015 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2014-10-23 (167 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) Lpstat: device for Canon-LBP-5975: socket://192.168.1.130 device for EPSON-Epson-Stylus-Photo-P50: usb://EPSON/Stylus%20Photo%20P50?serial=4C43514B3031353929 MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: EPSON-Epson-Stylus-Photo-P50: Epson Stylus Photo P50 - CUPS+Gutenprint v5.2.10 Canon-LBP-5975: Canon LBP-3460 Foomatic/pxlmono (recommended) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fca89173984 avahi_entry_group_free+4: cmpq $0x0,(%rdi) PC (0x7fca89173984) ok source $0x0 ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() UpgradeStatus: Upgraded to vivid on 2015-03-31 (8 days ago) UserGroups: dmi.bios.date: 05/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0307 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0307:bd05/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1442169/+subscriptions -- Mailing list: https://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 1441975] [NEW] have not shadows
Public bug reported: nautilus and desktop have not shadows on context menus ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 08:54:22 2015 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 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2015-03-05T22:46:49.143864 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- 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/1441975 Title: have not shadows Status in nautilus package in Ubuntu: New Bug description: nautilus and desktop have not shadows on context menus ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 08:54:22 2015 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 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2015-03-05T22:46:49.143864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1441975/+subscriptions -- Mailing list: https://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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
The 2nd window on low-dpi laptop. ** Attachment added: 20150409-202.jpg https://bugs.launchpad.net/oem-priority/+bug/1382291/+attachment/4370103/+files/20150409-202.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in gnome-desktop3 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in gnome-desktop3 source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Bug description: [Impact] The ubiquity window size display in HiDPI screens is small. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. [Test Case] 1. Install image on a system with HiDPI panel 2. Check the ubiquity window size displayed on screen Expected Result: The window size should be reasonable for user to read the content. Actual Result: The window size is small and user is hard to read the content. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+subscriptions -- Mailing list: https://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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
Dpkg-reconfigure does not seem to work. From dmesg: [ 46.42] nvidia :01:00.0: irq 85 for MSI/MSI-X [ 46.935467] NVRM: Your system is not currently configured to drive a VGA console [ 46.935469] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver [ 46.935470] NVRM: requires the use of a text-mode VGA console. Use of other console [ 46.935471] NVRM: drivers including, but not limited to, vesafb, may result in [ 46.935471] NVRM: corruption and stability problems, and is not supported. [ 47.136998] Bridge firewalling registered [ 47.296399] ip_tables: (C) 2000-2006 Netfilter Core Team [ 47.313931] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 47.330843] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 47.338417] init: plymouth-upstart-bridge main process ended, respawning [ 47.340651] init: plymouth-upstart-bridge main process (2013) terminated with status 1 After this, trying to login on gdm (gnome-session and system-default-session), a black screen appears. After logging on tty0, I got: Failed to start unit user@1000.service From there, I restarted gdm service and I was able to loggin. However the problem persists after rebooting. Dmesg after gdm restart: [ 47.434555] systemd-logind[2143]: Failed to start unit user@116.service: Unknown unit: user@116.service [ 47.434559] systemd-logind[2143]: Failed to start user service: Unknown unit: user@116.service [ 47.436677] systemd-logind[2143]: New session c1 of user gdm. [ 47.436688] systemd-logind[2143]: Linked /tmp/.X11-unix/X0 to /run/user/116/X11-display. [ 51.028511] audit_printk_skb: 36 callbacks suppressed [ 51.028513] audit: type=1400 audit(1428492782.685:39): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/etc/dconf/profile/gdm pid=2589 comm=mission-control requested_mask=r denied_mask=r fsuid=116 ouid=0 [ 97.512439] traps: gnome-shell[2886] trap int3 ip:7fa8dccf8d30 sp:7fff31d7e670 error:0 [ 98.281156] systemd-logind[2143]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 98.281186] systemd-logind[2143]: Failed to start user service: Unknown unit: user@1000.service [ 98.283358] systemd-logind[2143]: New session c2 of user . [ 113.017032] systemd-logind[2143]: New session c3 of user gdm. [ 113.923759] traps: gnome-shell[3502] trap int3 ip:7f07ab6e7d30 sp:7fff9e673d80 error:0 [ 115.792429] audit: type=1400 audit(1428492847.393:40): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/etc/dconf/profile/gdm pid=4205 comm=mission-control requested_mask=r denied_mask=r fsuid=116 ouid=0 [ 120.230229] systemd-logind[2143]: New session c4 of user . -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9
[Desktop-packages] [Bug 1440501] Re: Can not load mysql-akonadi apparmor profile
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: akonadi (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1440501 Title: Can not load mysql-akonadi apparmor profile Status in akonadi package in Ubuntu: Confirmed Status in apparmor package in Ubuntu: Confirmed Bug description: Apparmor fails to start witch exit code 123, because it can not load the mysql-akonadi profile: % sudo systemctl status apparmor -l ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since So 2015-04-05 12:29:33 CEST; 55s ago Docs: man:systemd-sysv-generator(8) Process: 13906 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: ...fail! Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service: control process exited, code=exited status=123 Apr 05 12:29:33 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor initialization. Apr 05 12:29:33 benediktZ50-70 systemd[1]: Unit apparmor.service entered failed state. Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service failed. However Apparmor loaded successfully: % sudo aa-status apparmor module is loaded. 17 profiles are loaded. 17 profiles are in enforce mode. /sbin/dhclient /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/libvirt/virt-aa-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/libvirtd /usr/sbin/tcpdump docker-default 0 profiles are in complain mode. 5 processes have profiles defined. 5 processes are in enforce mode. /sbin/dhclient (11821) /usr/lib/telepathy/mission-control-5 (2008) /usr/sbin/cups-browsed (840) /usr/sbin/cupsd (12783) /usr/sbin/libvirtd (971) 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. It is really necessary to set Apparmor as failed if one profile could not be loaded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1440501/+subscriptions -- Mailing list: https://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 1410932] Re: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/40-libs
*** This bug is a duplicate of bug 1186715 *** https://bugs.launchpad.net/bugs/1186715 ** This bug has been marked a duplicate of bug 1186715 package libsane 1.0.23-0ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1410932 Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 Status in sane-backends package in Ubuntu: Confirmed Bug description: ?? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Jan 14 20:09:27 2015 DuplicateSignature: package:libsane:1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules]:tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 InstallationDate: Installed on 2014-07-26 (172 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: sane-backends Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2014-08-05T12:06:04.541136 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1410932/+subscriptions -- Mailing list: https://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 1293252] Re: gnome-panel crashed with signal 5 in _XReply()
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1293252 Title: gnome-panel crashed with signal 5 in _XReply() Status in libwnck3 package in Ubuntu: Fix Released Status in libwnck3 source package in Trusty: Fix Committed Status in libwnck3 source package in Utopic: Fix Committed Status in libwnck3 source package in Vivid: Fix Released Bug description: [Impact] * Games using the Unity engine (like KSP) cause gnome-panel to crash, making things like flashback unusable. [Test Case] * Run gnome-panel (like in gnome flashback). * Launch Kerbal Space Program. Not sure whether there's a simpler test case for those without KSP. [Regression Potential] * The patch for the bug suggests the possibility of weirdly colored icons where crashes used to occur. [Other Info] * libwnck3 (3.14.0-1) allows gnome-panel to continue running in 14.10. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 16 23:53:20 2014 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: InstallationDate: Installed on 2014-02-28 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) ProcCmdline: gnome-panel ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1293252/+subscriptions -- Mailing list: https://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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Branch linked: lp:~mathieu-tl/network-manager/scanlist-pruning -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://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 1437639] Re: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsa
*** This bug is a duplicate of bug 1186715 *** https://bugs.launchpad.net/bugs/1186715 ** This bug has been marked a duplicate of bug 1186715 package libsane 1.0.23-0ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1437639 Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist Status in sane-backends package in Ubuntu: New Bug description: The problem was detected while installing wine by Terminal ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Sat Mar 28 15:57:58 2015 DuplicateSignature: package:libsane:1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules]:Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist InstallationDate: Installed on 2015-03-20 (7 days ago) InstallationMedia: Edubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: sane-backends Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2015-03-26T19:17:52.598078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1437639/+subscriptions -- Mailing list: https://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 1442145] Re: soffice.bin crashed with SIGSEGV in cppu::WeakComponentImplHelper_query()
** Information type changed from Private to Public -- 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/1442145 Title: soffice.bin crashed with SIGSEGV in cppu::WeakComponentImplHelper_query() Status in libreoffice package in Ubuntu: New Bug description: I was working with a macro, used the Xray tool, and this crash happened. I was trying to inspect a listener created with this the following VBA code: oListener = createUnoListener(OOOS1A2_,com.sun.star.chart.XChartDataChangeEventListener) The crash was created by: Xray oListener ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: libreoffice-core 1:4.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 14:55:11 2015 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2010-10-25 (1627 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=5 SegvAnalysis: Segfault happened at: 0x7fed5734b5aa cppu::WeakComponentImplHelper_query(com::sun::star::uno::Type const, cppu::class_data*, void*, cppu::WeakComponentImplHelperBase*)+42: mov %rdi,0x8(%rsp) PC (0x7fed5734b5aa) ok source %rdi ok destination 0x8(%rsp) (0x7ffcb27a0fa8) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: libreoffice Title: soffice.bin crashed with SIGSEGV in cppu::WeakComponentImplHelper_query() UpgradeStatus: Upgraded to vivid on 2015-03-09 (31 days ago) UserGroups: adm admin audio cdrom dialout kismet lp lpadmin plugdev sambashare scanner video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1442145/+subscriptions -- Mailing list: https://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 1123578] Re: [USB-Audio - Jabra PRO 930, recording] Recording problem
Hello , I've a jabra pro 930 on my computer Ubuntu 14.10 Same problem as description i use a sflphone for information hope it's better on 15.04 :-) -- 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/1123578 Title: [USB-Audio - Jabra PRO 930, recording] Recording problem Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am having a problem with my Jabra PRO 930 USB headset working with Ubuntu. I thought there might be issues when under Sound Settings, the headset is listed under the Output Tab but is not listed under the Input tab. See attached pictures. However, the headset does seem to work briefly, as long as audio is being played out. I have noticed that as long as the other side is talking or audio is coming in for at least 5 secs, the headset works perfectly. But if the other side mutes or stops talking (like listening to me talk), the headset cuts off completely until audio is detected again. This is not a problem with the headset. My wife bought the same headset and is using it with her Windows 7 system. I swapped headsets and the problem persisted on my Ubuntu 12.10 system. I use Google Talk, Google+ Hangouts and Skype and have the issue with all applications. Please let me know if there is anything else I can do to help or what information I can provide. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob2464 F pulseaudio /dev/snd/pcmC0D0p: bob2464 F...m pulseaudio /dev/snd/controlC1: bob2464 F pulseaudio Date: Tue Feb 12 18:21:46 2013 InstallationDate: Installed on 2011-11-25 (445 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:J930 successful Symptom_Card: Jabra PRO 930 - Jabra PRO 930 Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:J930 failed Symptom_Type: Only some of inputs are working Title: [USB-Audio - Jabra PRO 930, recording] Recording problem UpgradeStatus: Upgraded to quantal on 2012-10-27 (108 days ago) dmi.bios.date: 11/29/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.2D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F4 dmi.board.vendor: Compal dmi.board.version: 99.B6 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.2D:bd11/29/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.2D:rvnCompal:rn30F4:rvr99.B6:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: F.2D dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1123578/+subscriptions -- Mailing list: https://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 1441975] Re: have not shadows
** Package changed: nautilus (Ubuntu) = ubuntu-themes (Ubuntu) -- 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/1441975 Title: have not shadows Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: nautilus and desktop have not shadows on context menus ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 08:54:22 2015 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 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2015-03-05T22:46:49.143864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1441975/+subscriptions -- Mailing list: https://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 1434782] Re: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.
*** This bug is a duplicate of bug 1186715 *** https://bugs.launchpad.net/bugs/1186715 ** This bug has been marked a duplicate of bug 1186715 package libsane 1.0.23-0ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1434782 Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 Status in sane-backends package in Ubuntu: Confirmed Bug description: no more information about the crash ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Sat Mar 21 09:21:01 2015 DuplicateSignature: package:libsane:1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules]:tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 ErrorMessage: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 InstallationDate: Installed on 2015-03-19 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: sane-backends Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2015-03-19T21:09:02.880202 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1434782/+subscriptions -- Mailing list: https://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 1441960] Re: Update to upstream version 41 in Precise for security fixes
** Also affects: chromium-browser (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu Precise) Assignee: (unassigned) = Chad Miller (cmiller) ** Changed in: chromium-browser (Ubuntu Precise) Status: New = In Progress ** Changed in: chromium-browser (Ubuntu) Status: In Progress = Invalid ** Changed in: chromium-browser (Ubuntu) Assignee: Chad Miller (cmiller) = (unassigned) -- 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/1441960 Title: Update to upstream version 41 in Precise for security fixes Status in chromium-browser package in Ubuntu: Invalid Status in chromium-browser source package in Precise: In Progress Bug description: This morning Gmail notified me that my browser is unsupported, which made me realize Chromium for Precise hasn't been updated since September 2014 and is currently at version 37 (37.0.2062.120-0ubuntu0.12.04.1~pkg917) whereas more recent versions of Ubuntu are already at Chromium version 41. The unsupported version messages are of course harmless and easy enough to dismiss, but I'm guessing the newer Chromium releases also have important security fixes that should warrant an update – unless there are compatibility issues blocking it from happening? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917 ProcVersionSignature: Ubuntu 3.13.0-49.81~precise1-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CheckboxSubmission: 09ae689090491ca53449589269e4bfd8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Thu Apr 9 07:52:26 2015 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2014-07-11 (271 days ago) modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-01-13T17:30:56.028907 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1441960/+subscriptions -- Mailing list: https://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 1437639] Re: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsa
** This bug is no longer a duplicate of bug 1434782 package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1437639 Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist Status in sane-backends package in Ubuntu: New Bug description: The problem was detected while installing wine by Terminal ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Sat Mar 28 15:57:58 2015 DuplicateSignature: package:libsane:1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules]:Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist InstallationDate: Installed on 2015-03-20 (7 days ago) InstallationMedia: Edubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: sane-backends Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2015-03-26T19:17:52.598078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1437639/+subscriptions -- Mailing list: https://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 1441119] Re: akonadi-backend-mysql confict when installing mariadb
** Branch linked: lp:ubuntu/vivid-proposed/akonadi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1441119 Title: akonadi-backend-mysql confict when installing mariadb Status in akonadi package in Ubuntu: In Progress Bug description: I'm testing Kubuntu 15.04 beta 2 When I tried to: sudo apt-get install mariadb-client mariadb-server It comes that there's a dependency error: No se pudieron instalar algunos paquetes. Esto puede significar que usted pidió una situación imposible o, si está usando la distribución inestable, que algunos paquetes necesarios aún no se han creado o se han sacado de «Incoming». La siguiente información puede ayudar a resolver la situación: Los siguientes paquetes tienen dependencias incumplidas: mariadb-client : Depende: mariadb-client-10.0 (= 10.0.16-2~exp1~ubuntu1) pero no va a instalarse mariadb-server : Depende: mariadb-server-10.0 (= 10.0.16-2~exp1~ubuntu1) pero no va a instalarse E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos. Then I tried not to use the metapackage and go for v10.0: sudo apt-get install mariadb-client-10.0 mariadb-server-10.0 Se instalarán los siguientes paquetes extras: akonadi-backend-sqlite libhtml-template-perl mariadb-client-core-10.0 mariadb-common mariadb-server-core-10.0 Paquetes sugeridos: libipc-sharedcache-perl mariadb-test tinyca Los siguientes paquetes se ELIMINARÁN: akonadi-backend-mysql mysql-client mysql-client-5.6 mysql-client-core-5.6 mysql-server-core-5.6 Se instalarán los siguientes paquetes NUEVOS: akonadi-backend-sqlite libhtml-template-perl mariadb-client-10.0 mariadb-client-core-10.0 mariadb-common mariadb-server-10.0 mariadb-server-core-10.0 0 actualizados, 7 nuevos se instalarán, 5 para eliminar y 0 no actualizados. Se necesita descargar 11,5 MB de archivos. Se utilizarán 30,8 MB de espacio de disco adicional después de esta operación. ¿Desea continuar? [S/n] So it seems there's a dependency problem on replacing mysql-client-5.6 mysql-client-core-5.6 mysql-server-core-5.6 I can't find a workaround to prevent this situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1441119/+subscriptions -- Mailing list: https://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 1442312] [NEW] nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build have had problem using Ubuntu recommended Nividia module
Public bug reported: This has been an ongoing problem. I use two displays. I have seen this problem dozens of times. I was hoping you would have come up with a solution by recommending a compatible Nividia driver. My system hangs at times. This is a real pain. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 DKMSKernelVersion: 3.16.0-34-generic Date: Thu Apr 9 11:12:42 2015 InstallationDate: Installed on 2015-02-27 (41 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- 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/1442312 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build have had problem using Ubuntu recommended Nividia module Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: This has been an ongoing problem. I use two displays. I have seen this problem dozens of times. I was hoping you would have come up with a solution by recommending a compatible Nividia driver. My system hangs at times. This is a real pain. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 DKMSKernelVersion: 3.16.0-34-generic Date: Thu Apr 9 11:12:42 2015 InstallationDate: Installed on 2015-02-27 (41 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm 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/1442312/+subscriptions -- Mailing list: https://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 1430828] Re: scopes dont load pictures
** Changed in: canonical-devices-system-image Milestone: ww13-ota = ww17-2015 ** Tags added: bq -- 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/1430828 Title: scopes dont load pictures Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: The phone (krillin) is clearly connected and you can retrive text data but pictures do not updated see, attached pictures. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1430828/+subscriptions -- Mailing list: https://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 1434396] Re: Xserver does not start on boot (low-graphics mode)
For me, it's kinda odd. It seem to work (and worked even some day ago), then trying again (boot again) and it does not work again then ... Recently it seems to be quite unpredictable. But it can be a reason that sometimes I attach external monitor via the VGA D-SUB connector, but sometimes I don't. I'll check both cases out soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 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:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://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 1442207] Re: Wrong (work-)week start for pt_PT
Hi Tiago, and thanks for your report. This was fixed a few years ago in Ubuntu and Debian via a patch. $ export LC_TIME=pt_PT.UTF-8 $ locale first_weekday 2 $ locale first_workday 2 Path to the locale definition file: /usr/share/i18n/locales/pt_PT So I close this bug report. Your upstream bug report is motivated, though. ** Changed in: langpack-locales (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to langpack-locales in Ubuntu. https://bugs.launchpad.net/bugs/1442207 Title: Wrong (work-)week start for pt_PT Status in langpack-locales package in Ubuntu: Invalid Bug description: According to the default pt_PT definitions, the (work-)week start is set at Sunday, which is incorrect. The correct (work-)week start is Monday, because Portugal abides by EN 28601:1992, since it became an European Union member 6 years prior to issue of that norm. pt_PT was the only European Union locale that did not get the needed correction in these definitions. Therefore I request to have the first_weekday and first_workday entries entries set at LC_TIME with the default value of 2 (which stands for Monday) for the pt_PT locale. Thank you. Post Scriptum: There is no need for Ubuntu/package version information because this bug is quite ancient (20+ years?) and precedes the birth of the Ubuntu distribution. I opened a bug-report entry upstream at the following location: https://sourceware.org/bugzilla/show_bug.cgi?id=17565 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1442207/+subscriptions -- Mailing list: https://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 1442207] [NEW] Wrong (work-)week start for pt_PT
Public bug reported: According to the default pt_PT definitions, the (work-)week start is set at Sunday, which is incorrect. The correct (work-)week start is Monday, because Portugal abides by EN 28601:1992, since it became an European Union member 6 years prior to issue of that norm. pt_PT was the only European Union locale that did not get the needed correction in these definitions. Therefore I request to have the first_weekday and first_workday entries entries set at LC_TIME with the default value of 2 (which stands for Monday) for the pt_PT locale. Thank you. Post Scriptum: There is no need for Ubuntu/package version information because this bug is quite ancient (20+ years?) and precedes the birth of the Ubuntu distribution. I opened a bug-report entry upstream at the following location: https://sourceware.org/bugzilla/show_bug.cgi?id=17565 ** Affects: langpack-locales (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to langpack-locales in Ubuntu. https://bugs.launchpad.net/bugs/1442207 Title: Wrong (work-)week start for pt_PT Status in langpack-locales package in Ubuntu: New Bug description: According to the default pt_PT definitions, the (work-)week start is set at Sunday, which is incorrect. The correct (work-)week start is Monday, because Portugal abides by EN 28601:1992, since it became an European Union member 6 years prior to issue of that norm. pt_PT was the only European Union locale that did not get the needed correction in these definitions. Therefore I request to have the first_weekday and first_workday entries entries set at LC_TIME with the default value of 2 (which stands for Monday) for the pt_PT locale. Thank you. Post Scriptum: There is no need for Ubuntu/package version information because this bug is quite ancient (20+ years?) and precedes the birth of the Ubuntu distribution. I opened a bug-report entry upstream at the following location: https://sourceware.org/bugzilla/show_bug.cgi?id=17565 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1442207/+subscriptions -- Mailing list: https://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 1442314] [NEW] crash when CLOSING lid: in INTEL profile
Public bug reported: Perhaps it is a known bug? When I run my t440p ubuntu/mate 14.04 and switch to the intel (power saving mode), then there is instant death when I close the lid. As far as log files go, there is no output to any of them. NB: In the Nvidia (performance mode) sleep and wakeup work perfectly. NB: It is NOT the bug of crashing at wakeup. Let me know what to test, send,... ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1442314 Title: crash when CLOSING lid: in INTEL profile Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: Perhaps it is a known bug? When I run my t440p ubuntu/mate 14.04 and switch to the intel (power saving mode), then there is instant death when I close the lid. As far as log files go, there is no output to any of them. NB: In the Nvidia (performance mode) sleep and wakeup work perfectly. NB: It is NOT the bug of crashing at wakeup. Let me know what to test, send,... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1442314/+subscriptions -- Mailing list: https://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 1431128] Re: screen remains blank after waking up from suspend
** No longer affects: oem-priority/trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1431128 Title: screen remains blank after waking up from suspend Status in lightdm package in Ubuntu: New Status in lightdm source package in Trusty: New Bug description: Steps: 1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here) 2. Press any key on the keyboard or the Power button to wake the device up Expected results: 1. The system suspends and the Power button LED blinks 2. The system wakes up and user can log in. Actual results: 1. The system suspends and the Power button LED blinks (OK) 2. The login screen appears and the screen is immediately turned off (NOK). User needs to move the mouse or enter a key to turn the screen on. Additional information: - In a few additional occasions, after performing this action several times (pressing the Sleep key to suspend the system, then wake it up), the system freezes at log in screen just before going to suspend mode. It has to be force-stopped and restarted. - Please note that this problem does NOT happen when suspending from the User Menu or using the Power button and selecting Suspend. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Mar 12 11:19:32 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2 InstallationDate: Installed on 2015-02-10 (29 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20150205-07:08 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin #autologin-user=u SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431128/+subscriptions -- Mailing list: https://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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
The 4th window on low-dpi laptop. ** Attachment added: 20150409-204.jpg https://bugs.launchpad.net/oem-priority/+bug/1382291/+attachment/4370105/+files/20150409-204.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in gnome-desktop3 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in gnome-desktop3 source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Bug description: [Impact] The ubiquity window size display in HiDPI screens is small. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. [Test Case] 1. Install image on a system with HiDPI panel 2. Check the ubiquity window size displayed on screen Expected Result: The window size should be reasonable for user to read the content. Actual Result: The window size is small and user is hard to read the content. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+subscriptions -- Mailing list: https://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 1431179] Re: usb_modeswitch@.service fails sometimes
** Attachment added: udev_before_manual_switch.txt https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+attachment/4370385/+files/udev_before_manual_switch.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1431179 Title: usb_modeswitch@.service fails sometimes Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: I lack the technical knowledge to know if this is a bug in udev, systemd or another component. After the switch to systemd, my 4G Huawei USB modem no longer functions as a modem unless I run usb_modeswitch to flip its state from USB mass storage. The command I issue and its output is below, which also show the Vendor and Product ID. Strangely, it does not do this every time. Yesterday when I updated using apt-get dist-upgrade upon reboot the modem worked as expected. But from a cold boot this morning it did not. $ sudo usb_modeswitch -v 0x12d1 -p 0x1f01 -J [sudo] password for damon: Look for default devices ... product ID matched Found devices in default mode (1) Access device 003 on bus 003 Current configuration number is 1 Use interface number 0 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) - Manufacturer: HUAWEI Technology Product: HUAWEI Mobile Serial No.: - Using standard Huawei switching message Looking for active driver ... OK, driver detached Set up interface 0 Use endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... OK, message successfully sent Reset response endpoint 0x81 Could not reset endpoint (probably harmless): -99 Reset message endpoint 0x01 Could not reset endpoint (probably harmless): -99 Device is gone, skip any further commands - Run lsusb to note any changes. Bye! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Thu Mar 12 11:37:06 2015 InstallationDate: Installed on 2015-02-05 (34 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205) MachineType: LENOVO 427637U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic root=UUID=eb18ef51-a2d0-4372-8eb9-ae009a05d4f6 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET62WW (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 427637U 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:bvr8BET62WW(1.42):bd07/26/2013:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 427637U dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+subscriptions -- Mailing list: https://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 1431179] Re: usb_modeswitch@.service fails sometimes
** Attachment added: usb_modeswitch.log https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+attachment/4370388/+files/usb_modeswitch.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1431179 Title: usb_modeswitch@.service fails sometimes Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: I lack the technical knowledge to know if this is a bug in udev, systemd or another component. After the switch to systemd, my 4G Huawei USB modem no longer functions as a modem unless I run usb_modeswitch to flip its state from USB mass storage. The command I issue and its output is below, which also show the Vendor and Product ID. Strangely, it does not do this every time. Yesterday when I updated using apt-get dist-upgrade upon reboot the modem worked as expected. But from a cold boot this morning it did not. $ sudo usb_modeswitch -v 0x12d1 -p 0x1f01 -J [sudo] password for damon: Look for default devices ... product ID matched Found devices in default mode (1) Access device 003 on bus 003 Current configuration number is 1 Use interface number 0 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) - Manufacturer: HUAWEI Technology Product: HUAWEI Mobile Serial No.: - Using standard Huawei switching message Looking for active driver ... OK, driver detached Set up interface 0 Use endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... OK, message successfully sent Reset response endpoint 0x81 Could not reset endpoint (probably harmless): -99 Reset message endpoint 0x01 Could not reset endpoint (probably harmless): -99 Device is gone, skip any further commands - Run lsusb to note any changes. Bye! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Thu Mar 12 11:37:06 2015 InstallationDate: Installed on 2015-02-05 (34 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205) MachineType: LENOVO 427637U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic root=UUID=eb18ef51-a2d0-4372-8eb9-ae009a05d4f6 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET62WW (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 427637U 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:bvr8BET62WW(1.42):bd07/26/2013:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 427637U dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+subscriptions -- Mailing list: https://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 1441986] Re: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher garbled after resuming from suspend
** Tags added: 201407-15335 taipei-lab ** Tags added: blocks-hwcert ** Description changed: Launcher does not display correctly after suspend, there is other different corruption in different application scenario, most of them can be recover by switch between VT. Steps to reproduce: 1. suspend the system in the middle of using 2. resume from suspend Expected result: Desktop screen display correctly. Actual result: Some parts of the screen corrupted. Workaround: Switching from X to VT may temporary fix these corruptions. + + Additional information: + Installing driver downloading from nvidia.com the screen garbled/corruption does not happen again. + version: NVIDIA-Linux-x86_64-346.59.run + + + + - + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-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.113 Mon Dec 1 21:08:13 PST 2014 - GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 + GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 9 02:09:23 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Device [103c:079c] + NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Device [103c:079c] InstallationDate: Installed on 2015-04-02 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Z820 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=d8280bec-e0b3-4b37-8f6b-aa899731f110 ro rootdelay=60 quiet splash initcall_debug SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J63 v03.69 dmi.board.asset.tag: 2UA4242K12 dmi.board.name: 158B dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.01 dmi.chassis.asset.tag: 2UA4242K12 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z820 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 8 09:39:05 2015 xserver.configfile: default 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.7 -- 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/1441986 Title: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher garbled after resuming from suspend Status in xorg package in Ubuntu: New Bug description: Launcher does not display correctly after suspend, there is other different corruption in different application scenario, most of them can be recover by switch between VT. Steps to reproduce: 1. suspend the system in the middle of using 2. resume from suspend Expected result: Desktop screen display
[Desktop-packages] [Bug 912729] Re: [Unity-2D] Alt+tilde does not work
Fixed in 15.04 - will be released in 23 april. ** Changed in: metacity (Ubuntu) Status: New = Fix Released -- 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/912729 Title: [Unity-2D] Alt+tilde does not work Status in metacity package in Ubuntu: Fix Released Bug description: When pressing Alt+tilde it's supposed to change between the windows of the same application. However it does not do it if there are more than 2 windows of the same application are open. It's broken in both Oneiric and Precise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 4.12.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5 Uname: Linux 3.2.0-4-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Fri Jan 6 13:08:30 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110921.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-2d UpgradeStatus: Upgraded to precise on 2011-12-13 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/912729/+subscriptions -- Mailing list: https://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 1440570] Re: VNC'ing into gnome-session-flashback (Metacity) in non-shared desktop mode causes Super+KEY pressed behavior
This bug was fixed in the package metacity - 1:3.14.3-1ubuntu7 --- metacity (1:3.14.3-1ubuntu7) vivid; urgency=medium * Brown paper bag upload. * Fix the previous upload to use the function name from metacity 3.14 (keysym_name, not keysym_to_string). -- Dmitry Shachnev mity...@ubuntu.com Thu, 09 Apr 2015 14:50:18 +0300 ** Changed in: metacity (Ubuntu) Status: In Progress = Fix Released -- 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/1440570 Title: VNC'ing into gnome-session-flashback (Metacity) in non-shared desktop mode causes Super+KEY pressed behavior Status in metacity package in Ubuntu: Fix Released Bug description: When VNC'ing into gnome-session-flashback (Metacity) with either tightvncserver or vnc4server configured for non-shared desktop mode, when one opens a terminal for example, and types the s key, it acts as if the Super key is also pressed along with it. Hence, this appears to be a gnome-* issue. Vivid new install setup for tightvncserver: sudo apt-get update sudo apt-get -y dist-upgrade sudo apt-get -y install xrdp gnome-session-flashback sudo apt-get -y remove vino nano .xsession #START export XDG_CURRENT_DESKTOP='GNOME-Flashback:Unity' exec gnome-session --session=gnome-flashback-metacity --disable-acceleration-check #END sudo nano /etc/xrdp/xrdp.ini change to: #START [globals] bitmap_cache=yes bitmap_compression=yes port=3389 crypt_level=high channel_code=1 max_bpp=24 #black=00 #grey=d6d3ce #dark_grey=808080 #blue=08246b #dark_blue=08246b #white=ff #red=ff #green=00ff00 #background=626c72 [xrdp1] name=sesman-Xvnc lib=libvnc.so username=ask password=ask ip=127.0.0.1 port=-1 #END Log out, log back in, and RDP in via either Windows Remote Desktop Connection or Remmina. WORKAROUND: Applications System Tools System Settings Keyboard Shortcuts Disable all shortcuts containing the Super key. WORKAROUND: Don't use the .xsession file with tightvncserver, but this then creates a shared desktop experience, instead of ones own, not seen by the user at the local console. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: vnc4server 4.1.1+xorg4.3.0-37.3ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Apr 5 13:10:40 2015 InstallationDate: Installed on 2014-12-14 (112 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141213) SourcePackage: vnc4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1440570/+subscriptions -- Mailing list: https://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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Changed in: indicator-network (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Confirmed -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://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 1441893] Re: Can't connect to my wi-fi: authentication timed out
** Description changed: I can't connect to my wi-fi with my laptop. I get this error message in the syslog. Apr 8 22:25:35 ubuntu kernel: [ 793.89] wlan0: authentication with 10:bf:48:e5:d1:b8 timed out ubuntu@ubuntu:~$ lshw -c network WARNING: you should run this program as super-user. - *-network -description: Ethernet interface -product: Ethernet Connection I217-V -vendor: Intel Corporation -physical id: 19 -bus info: pci@:00:19.0 -logical name: eth0 -version: 05 -serial: 00:90:f5:f8:ef:86 -size: 1Gbit/s -capacity: 1Gbit/s -width: 32 bits -clock: 33MHz -capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation -configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s -resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff ioport:f080(size=32) - *-network -description: Wireless interface -product: Wireless 3160 -vendor: Intel Corporation -physical id: 0 -bus info: pci@:03:00.0 -logical name: wlan0 -version: 83 -serial: a0:88:69:39:ae:d6 -width: 64 bits -clock: 33MHz -capabilities: bus_master cap_list ethernet physical wireless -configuration: broadcast=yes driver=iwlwifi driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn -resources: irq:32 memory:f7c0-f7c01fff + *-network + description: Ethernet interface + product: Ethernet Connection I217-V + vendor: Intel Corporation + physical id: 19 + bus info: pci@:00:19.0 + logical name: eth0 + version: 05 + serial: 00:90:f5:f8:ef:86 + size: 1Gbit/s + capacity: 1Gbit/s + width: 32 bits + clock: 33MHz + capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation + configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s + resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff ioport:f080(size=32) + *-network + description: Wireless interface + product: Wireless 3160 + vendor: Intel Corporation + physical id: 0 + bus info: pci@:03:00.0 + logical name: wlan0 + version: 83 + serial: a0:88:69:39:ae:d6 + width: 64 bits + clock: 33MHz + capabilities: bus_master cap_list ethernet physical wireless + configuration: broadcast=yes driver=iwlwifi driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn + resources: irq:32 memory:f7c0-f7c01fff Attached is the full syslog. - This machine has been working more or less ok on vivid for at least three months. Sometimes it refused to connect to the wi-fi, but after a restart it started working. - Recently I changed the network from N to G, and recently did an upgrade to the latest vivid. I had some problems booting, so I also recently fully removed upstart. It boots fine with systemd, and everything else seem to be working. + This machine has been working more or less ok on vivid for at least three months. Sometimes it refused to connect to the wi-fi, but after a restart it started working. + Recently I changed the network from G to N, and recently did an upgrade to the latest vivid. I had some problems booting, so I also recently fully removed upstart. It boots fine with systemd, and everything else seem to be working. I've just tested with a daily vivid live USB, and the same problem happened. I'm connecting to the same network using the same password with my other machine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CasperVersion: 1.356 CurrentDesktop: Unity Date: Wed Apr 8 22:20:03 2015 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback IpRoute: - default via 192.168.2.1 dev eth0 proto static metric 1024 - 169.254.0.0/16 dev eth0 scope link metric 1000 - 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.208 + default via 192.168.2.1 dev eth0 proto static metric 1024 + 169.254.0.0/16 dev eth0 scope link metric 1000 +
[Desktop-packages] [Bug 1440501] Re: Can not load mysql-akonadi apparmor profile
Putting a file in /etc/apparmor.d/local/usr.sbin.mysqld-akonadi (like the other examples already there) resolves the issue. Maybe the packaging for akonadi-backend-mysql forgot to generate an empty configuration file there? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1440501 Title: Can not load mysql-akonadi apparmor profile Status in akonadi package in Ubuntu: Confirmed Status in apparmor package in Ubuntu: Confirmed Bug description: Apparmor fails to start witch exit code 123, because it can not load the mysql-akonadi profile: % sudo systemctl status apparmor -l ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since So 2015-04-05 12:29:33 CEST; 55s ago Docs: man:systemd-sysv-generator(8) Process: 13906 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: ...fail! Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service: control process exited, code=exited status=123 Apr 05 12:29:33 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor initialization. Apr 05 12:29:33 benediktZ50-70 systemd[1]: Unit apparmor.service entered failed state. Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service failed. However Apparmor loaded successfully: % sudo aa-status apparmor module is loaded. 17 profiles are loaded. 17 profiles are in enforce mode. /sbin/dhclient /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/libvirt/virt-aa-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/libvirtd /usr/sbin/tcpdump docker-default 0 profiles are in complain mode. 5 processes have profiles defined. 5 processes are in enforce mode. /sbin/dhclient (11821) /usr/lib/telepathy/mission-control-5 (2008) /usr/sbin/cups-browsed (840) /usr/sbin/cupsd (12783) /usr/sbin/libvirtd (971) 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. It is really necessary to set Apparmor as failed if one profile could not be loaded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1440501/+subscriptions -- Mailing list: https://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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
The resolution of the low-dpi laptop. ** Attachment added: 20150409-205.jpg https://bugs.launchpad.net/oem-priority/+bug/1382291/+attachment/4370110/+files/20150409-205.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in gnome-desktop3 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in gnome-desktop3 source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Bug description: [Impact] The ubiquity window size display in HiDPI screens is small. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. [Test Case] 1. Install image on a system with HiDPI panel 2. Check the ubiquity window size displayed on screen Expected Result: The window size should be reasonable for user to read the content. Actual Result: The window size is small and user is hard to read the content. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+subscriptions -- Mailing list: https://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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
The 3rd window on low-dpi laptop. ** Attachment added: 20150409-203.jpg https://bugs.launchpad.net/oem-priority/+bug/1382291/+attachment/4370104/+files/20150409-203.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in gnome-desktop3 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in gnome-desktop3 source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Bug description: [Impact] The ubiquity window size display in HiDPI screens is small. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. [Test Case] 1. Install image on a system with HiDPI panel 2. Check the ubiquity window size displayed on screen Expected Result: The window size should be reasonable for user to read the content. Actual Result: The window size is small and user is hard to read the content. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+subscriptions -- Mailing list: https://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 1373136] Re: nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed to build [nvidia-modules-common.mk: No such file or directory]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: New = Confirmed -- 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/1373136 Title: nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed to build [nvidia-modules-common.mk: No such file or directory] Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Bug description: Automatically-generated bug report. Software Updater completed despite this issue. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-uvm 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 DKMSBuildLog: DKMS make.log for nvidia-331-uvm-331.38 for kernel 3.13.0-36-generic (x86_64) Wed Sep 24 09:14:59 NZST 2014 Makefile:215: /var/lib/dkms/nvidia-331/331.38/build/nvidia-modules-common.mk: No such file or directory make: *** No rule to make target `/var/lib/dkms/nvidia-331/331.38/build/nvidia-modules-common.mk'. Stop. DKMSKernelVersion: 3.13.0-36-generic Date: Wed Sep 24 09:15:06 2014 InstallationDate: Installed on 2014-07-31 (54 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm 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/1373136/+subscriptions -- Mailing list: https://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 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out
I could connect to the G network on utopic, so this is a regression. ** Summary changed: - Can't connect to my wi-fi N network: authentication timed out + Can't connect to my wi-fi N network on vivid: authentication timed out -- 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/1441893 Title: Can't connect to my wi-fi N network on vivid: authentication timed out Status in network-manager package in Ubuntu: New Bug description: I can't connect to my wi-fi with my laptop. I get this error message in the syslog. Apr 8 22:25:35 ubuntu kernel: [ 793.89] wlan0: authentication with 10:bf:48:e5:d1:b8 timed out ubuntu@ubuntu:~$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: Ethernet Connection I217-V vendor: Intel Corporation physical id: 19 bus info: pci@:00:19.0 logical name: eth0 version: 05 serial: 00:90:f5:f8:ef:86 size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff ioport:f080(size=32) *-network description: Wireless interface product: Wireless 3160 vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: wlan0 version: 83 serial: a0:88:69:39:ae:d6 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn resources: irq:32 memory:f7c0-f7c01fff Attached is the full syslog. This machine has been working more or less ok on vivid for at least three months. Sometimes it refused to connect to the wi-fi, but after a restart it started working. Recently I changed the network from G to N, and recently did an upgrade to the latest vivid. I had some problems booting, so I also recently fully removed upstart. It boots fine with systemd, and everything else seem to be working. I've just tested with a daily vivid live USB, and the same problem happened. I'm connecting to the same network using the same password with my other machine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CasperVersion: 1.356 CurrentDesktop: Unity Date: Wed Apr 8 22:20:03 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.2.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.208 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 cf5cb021-0df1-4f13-b74c-c3e9c6749a30 /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1441893/+subscriptions -- Mailing list: https://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 1442304] [NEW] when accessibility tools such as orca are run on the loggin screen, lightdm crashes
Public bug reported: when I launch gnome-orca from the lightdm loggin screen and I enter my password, lightdm crashes. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-12.12~lp1440848v1-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Thu Apr 9 19:00:27 2015 InstallationDate: Installed on 2015-04-07 (2 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Beta i386 (20150326) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1442304 Title: when accessibility tools such as orca are run on the loggin screen, lightdm crashes Status in lightdm package in Ubuntu: New Bug description: when I launch gnome-orca from the lightdm loggin screen and I enter my password, lightdm crashes. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-12.12~lp1440848v1-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Thu Apr 9 19:00:27 2015 InstallationDate: Installed on 2015-04-07 (2 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Beta i386 (20150326) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1442304/+subscriptions -- Mailing list: https://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 729979] Re: [nvidia] Windows appear blank white
This fix is already in Vivid, but not in Utopic. -- 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/729979 Title: [nvidia] Windows appear blank white Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome- terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc. HOW TO REPRODUCE: [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not reliably be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly. 1. Minimize a window 2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal) 3. Click the window icon on the launcher to maximize it again. 4. The window contents will be white, black, or transparent depending on the Ubuntu version [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions -- Mailing list: https://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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
I tested vivid daily image vivid-desktop-amd64-20150408.iso on a hi-dpi Lenovo laptop. It was failed, because the Installation Type window was too large, some options was not shown. ** Attachment added: 1st window https://bugs.launchpad.net/oem-priority/+bug/1382291/+attachment/4370097/+files/20150409-101.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in gnome-desktop3 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in gnome-desktop3 source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Bug description: [Impact] The ubiquity window size display in HiDPI screens is small. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. [Test Case] 1. Install image on a system with HiDPI panel 2. Check the ubiquity window size displayed on screen Expected Result: The window size should be reasonable for user to read the content. Actual Result: The window size is small and user is hard to read the content. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+subscriptions -- Mailing list: https://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 118605] Re: [fglrx] freezes upon Logout or Switch user [patch]
Rolf Чтобы Вы узнали кол-во переплаченных денег, высылаем на вашу электронную почту выписку. Всю нужную информацию Вы найдете в прикрепленном документе. Воскресенье, 23 ноября 2014, 15:22 UTC от Rolf Leggewie 118...@bugs.launchpad.net: Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: linux-restricted-modules-envy-2.6.24 (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are subscribed to the bug report. Title: [fglrx] freezes upon Logout or Switch user [patch] Status in “fglrx-installer” package in Ubuntu: Invalid Status in “gdm” package in Ubuntu: Invalid Status in “linux-restricted-modules-2.6.24” package in Ubuntu: Invalid Status in “linux-restricted-modules-envy-2.6.24” package in Ubuntu: Won't Fix Status in “fglrx-installer” source package in Hardy: Won't Fix Status in “gdm” source package in Hardy: Invalid Status in “linux-restricted-modules-2.6.24” source package in Hardy: Invalid Status in “linux-restricted-modules-envy-2.6.24” source package in Hardy: Won't Fix Status in Mandriva Linux: Unknown Bug description: Using Feisty, Gnome and GDM: 1) log in as any user 2) Log out or Switch user on the Quit screen The screen goes black, Ctrl+Alt+Backspace does not work, nor does the Ctrl+Alt+F1-12. Interestingly, Numlock LED is still responsive. The only way out is hard reboot. I looked for the solution on forums. One advice was to turn on Restart the X server with each login, however, it did not help. I am not aware of any non-default configuration, I can supply my gdm .conf-custom if needed. To manage notifications about this bug go to: ** Attachment added: =?UTF-8?B?MDQ0OTU0ODM1OGJhbGFuYy56aXA=?= https://bugs.launchpad.net/bugs/118605/+attachment/4370451/+files/%3D%3FUTF-8%3FB%3FMDQ0OTU0ODM1OGJhbGFuYy56aXA%3D%3F%3D -- 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/118605 Title: [fglrx] freezes upon Logout or Switch user [patch] Status in fglrx-installer package in Ubuntu: Invalid Status in gdm package in Ubuntu: Invalid Status in linux-restricted-modules-2.6.24 package in Ubuntu: Invalid Status in linux-restricted-modules-envy-2.6.24 package in Ubuntu: Won't Fix Status in fglrx-installer source package in Hardy: Won't Fix Status in gdm source package in Hardy: Invalid Status in linux-restricted-modules-2.6.24 source package in Hardy: Invalid Status in linux-restricted-modules-envy-2.6.24 source package in Hardy: Won't Fix Status in Mandriva Linux: Unknown Bug description: Using Feisty, Gnome and GDM: 1) log in as any user 2) Log out or Switch user on the Quit screen The screen goes black, Ctrl+Alt+Backspace does not work, nor does the Ctrl+Alt+F1-12. Interestingly, Numlock LED is still responsive. The only way out is hard reboot. I looked for the solution on forums. One advice was to turn on Restart the X server with each login, however, it did not help. I am not aware of any non-default configuration, I can supply my gdm .conf-custom if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/118605/+subscriptions -- Mailing list: https://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 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
I loaded Ubuntu-MATE 15.04 Beta2 again. This time I added these to my boot parameters drm.debug=14 log_buf_len=14M and pulled the dmesg and journalctl log off. Will be attaching them. Here is a sample of what I am seeing Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.Accounts.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.ColorManager.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.DisplayManager.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.PackageKit.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.PolicyKit1.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.RealtimeKit1.conf: Error retrieving chunk extents: Operation not supported Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.SystemToolsBackends.conf: Error retrieving chunk extents: Operation not supported -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in X.org XServer - ATI gfx chipset driver: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager.
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Attachment added: journalctl.log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1434036/+attachment/4370608/+files/journalctl.log -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in X.org XServer - ATI gfx chipset driver: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information:
[Desktop-packages] [Bug 1442053] [NEW] eog crashes opening a certain png file (attached)
Public bug reported: I open eog file.png from terminal, and this is what I get: ** Gdk:ERROR:/build/buildd/gtk+3.0-3.10.8/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted (core dumped) The image is made from a pdf file using convert: convert -density 5000 TUM_IAS_logo.pdf TUM_IAS_logo.png Also, nautilus also crashes when trying to make the thumbnail. So as Unity dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: pax ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 11:57:41 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2015-03-10 (29 days ago) ** Affects: eog (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 eog in Ubuntu. https://bugs.launchpad.net/bugs/1442053 Title: eog crashes opening a certain png file (attached) Status in eog package in Ubuntu: New Bug description: I open eog file.png from terminal, and this is what I get: ** Gdk:ERROR:/build/buildd/gtk+3.0-3.10.8/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted (core dumped) The image is made from a pdf file using convert: convert -density 5000 TUM_IAS_logo.pdf TUM_IAS_logo.png Also, nautilus also crashes when trying to make the thumbnail. So as Unity dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: pax ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 11:57:41 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2015-03-10 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1442053/+subscriptions -- Mailing list: https://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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
Anyone knows if this erro happens in fedora? Sent from my Windows Phone De: fgr1986mailto:1268...@bugs.launchpad.net Enviada em: 09/04/2015 04:11 Para: samucabertol...@hotmail.commailto:samucabertol...@hotmail.com Assunto: [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Dpkg-reconfigure does not seem to work. From dmesg: [ 46.42] nvidia :01:00.0: irq 85 for MSI/MSI-X [ 46.935467] NVRM: Your system is not currently configured to drive a VGA console [ 46.935469] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver [ 46.935470] NVRM: requires the use of a text-mode VGA console. Use of other console [ 46.935471] NVRM: drivers including, but not limited to, vesafb, may result in [ 46.935471] NVRM: corruption and stability problems, and is not supported. [ 47.136998] Bridge firewalling registered [ 47.296399] ip_tables: (C) 2000-2006 Netfilter Core Team [ 47.313931] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 47.330843] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 47.338417] init: plymouth-upstart-bridge main process ended, respawning [ 47.340651] init: plymouth-upstart-bridge main process (2013) terminated with status 1 After this, trying to login on gdm (gnome-session and system-default-session), a black screen appears. After logging on tty0, I got: Failed to start unit user@1000.service From there, I restarted gdm service and I was able to loggin. However the problem persists after rebooting. Dmesg after gdm restart: [ 47.434555] systemd-logind[2143]: Failed to start unit user@116.service: Unknown unit: user@116.service [ 47.434559] systemd-logind[2143]: Failed to start user service: Unknown unit: user@116.service [ 47.436677] systemd-logind[2143]: New session c1 of user gdm. [ 47.436688] systemd-logind[2143]: Linked /tmp/.X11-unix/X0 to /run/user/116/X11-display. [ 51.028511] audit_printk_skb: 36 callbacks suppressed [ 51.028513] audit: type=1400 audit(1428492782.685:39): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/etc/dconf/profile/gdm pid=2589 comm=mission-control requested_mask=r denied_mask=r fsuid=116 ouid=0 [ 97.512439] traps: gnome-shell[2886] trap int3 ip:7fa8dccf8d30 sp:7fff31d7e670 error:0 [ 98.281156] systemd-logind[2143]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 98.281186] systemd-logind[2143]: Failed to start user service: Unknown unit: user@1000.service [ 98.283358] systemd-logind[2143]: New session c2 of user . [ 113.017032] systemd-logind[2143]: New session c3 of user gdm. [ 113.923759] traps: gnome-shell[3502] trap int3 ip:7f07ab6e7d30 sp:7fff9e673d80 error:0 [ 115.792429] audit: type=1400 audit(1428492847.393:40): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/etc/dconf/profile/gdm pid=4205 comm=mission-control requested_mask=r denied_mask=r fsuid=116 ouid=0 [ 120.230229] systemd-logind[2143]: New session c4 of user . -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to
[Desktop-packages] [Bug 1442163] [NEW] NumLock turned off on layout switch
Public bug reported: When switching the keyboard layout using a shortcut (such as Alt+Shift), NumLock functionality is (mostly) turned off. Ubuntu 14.10 amd64 Kernel 3.16.0-33 ** Affects: software-center (Ubuntu) Importance: Undecided Assignee: catvlad (catvlad98) Status: New ** Changed in: software-center (Ubuntu) Assignee: (unassigned) = catvlad (catvlad98) ** Changed in: software-center (Ubuntu) Assignee: catvlad (catvlad98) = (unassigned) ** Changed in: software-center (Ubuntu) Assignee: (unassigned) = catvlad (catvlad98) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1442163 Title: NumLock turned off on layout switch Status in software-center package in Ubuntu: New Bug description: When switching the keyboard layout using a shortcut (such as Alt+Shift), NumLock functionality is (mostly) turned off. Ubuntu 14.10 amd64 Kernel 3.16.0-33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1442163/+subscriptions -- Mailing list: https://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 1442354] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: i dont know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 DKMSKernelVersion: 3.13.0-49-generic Date: Thu Apr 9 21:27:16 2015 InstallationDate: Installed on 2011-11-02 (1254 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-08-26 (225 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1442354 Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 DKMSKernelVersion: 3.13.0-49-generic Date: Thu Apr 9 21:27:16 2015 InstallationDate: Installed on 2011-11-02 (1254 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-08-26 (225 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1442354/+subscriptions -- Mailing list: https://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 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm-gtk-greeter (Ubuntu) Status: New = Confirmed -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in X.org XServer - ATI gfx chipset driver: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322
[Desktop-packages] [Bug 1375598] Re: Some options have not been translated in system setting- safety and privacy
This bug was fixed in the package activity-log-manager - 0.9.7-0ubuntu19 --- activity-log-manager (0.9.7-0ubuntu19) vivid; urgency=medium * debian/patches/19_untranslated_menus.patch: - Mark some menu entries for translation (LP: #1375598) -- Robert Ancell robert.anc...@canonical.com Thu, 09 Apr 2015 16:58:50 +1200 ** Changed in: activity-log-manager (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to activity-log-manager in Ubuntu. https://bugs.launchpad.net/bugs/1375598 Title: Some options have not been translated in system setting- safety and privacy Status in Privacy Manager for Zeitgeist: Fix Committed Status in Ubuntu Kylin: Confirmed Status in activity-log-manager package in Ubuntu: Fix Released Bug description: steps: 1. enter System Setting. 2. click Safety and Privacy. 3. click 'file and application' tab page 4.click + at the bottom of the interface. 5.check the options. 6. the options( Add folder; Add Application) are in English. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/1375598/+subscriptions -- Mailing list: https://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 1439923] Re: GTK does not build because gtk_menu_tracker_item_get_menu_item does not always return a value
This bug was fixed in the package gtk+3.0 - 3.14.11-0ubuntu2
---
gtk+3.0 (3.14.11-0ubuntu2) vivid; urgency=medium
* Patch from Steve Dodier-Lazaro (thanks!) to always return a value from
gtk_menu_tracker_item_get_{menu_item,action_namespace}. (LP: #1439923)
-- Iain Lane iain.l...@canonical.com Wed, 08 Apr 2015 17:28:36 +0100
** Changed in: gtk+3.0 (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1439923
Title:
GTK does not build because gtk_menu_tracker_item_get_menu_item does
not always return a value
Status in gtk+3.0 package in Ubuntu:
Fix Released
Bug description:
Tested version: 3.14.11-0ubuntu1
Bug most likely introduced in: 3.10.6-0ubuntu1
gtk_menu_tracker_item_get_menu_item and
gtk_menu_tracker_item_get_action_namespace both have return types, but
use g_return_if_fail instead of g_return_val_if_fail.
Attached is a diff of the change I made to make my Clang build the
package, although you might want to verify whether returning NULL is
correct (I have no idea what GtkMenuTrackerItem is).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1439923/+subscriptions
--
Mailing list: https://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 1434396] Re: Xserver does not start on boot (low-graphics mode)
Interesting - another Thinkpad X240 _wasn't_ fixed by today's update, but when I checked the configuration it also had sddm installed (thought it wasn't using it as the default login display manager). Removing sddm, which still allows the kubuntu desktop package to remain, gives a functioning systemd+lightdm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 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:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://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 1442292] [NEW] the candidate frame of ibus was covered with dash when i search something in Chinese
Public bug reported: ubuntu 15.04 beta2 IBus 1.5.9 thanks. ** 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/1442292 Title: the candidate frame of ibus was covered with dash when i search something in Chinese Status in ibus package in Ubuntu: New Bug description: ubuntu 15.04 beta2 IBus 1.5.9 thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1442292/+subscriptions -- Mailing list: https://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 1441958] Re: Screen is shaking after installing 14.01
** 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/1441958 Title: Screen is shaking after installing 14.01 Status in xorg package in Ubuntu: New Bug description: I just installed 14.01 and had installed all updates and doing a backup half way through everything froze. when I rebooted the mouse pointer was flashing and everthing was shaking, there was no internet conection or side/top bars. I'm using a usb boot for now. Any Idea's on how to fix this bug??? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CasperVersion: 1.340 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 Apr 9 04:28:15 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:0102] LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity quiet splash oem-config/enable=true -- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H61M-HVS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd12/09/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-HVS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 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.1 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 Apr 9 03:07:53 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6642 vendor ACI xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1441958/+subscriptions -- Mailing list: https://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 1364785] Re: package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New = Confirmed -- 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/1364785 Title: package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 Status in libreoffice package in Ubuntu: Confirmed Bug description: Stop system upgrade, moving to 14.04.1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Tue Sep 2 15:28:35 2014 DuplicateSignature: Unpacking libreoffice-common (1:4.2.4-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a4.2.4-0ubuntu2_all.deb (--unpack): tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 ErrorMessage: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 UpgradeStatus: Upgraded to trusty on 2014-09-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1364785/+subscriptions -- Mailing list: https://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 1442159] [NEW] Add a configuration option to keep terminals opened by apport opened
Public bug reported: `gnome-terminals` which are opened by `apport` to monitor the installation of necessary deb packages for local investigation, production of `gdb` backtraces, etc. are closed immediately after success, but after failure as well (e.g. if `apt-get` can't get its global lock, or another issue occurs). For debugging `apport` it'd be very useful to have a configuration option which allows the terminals opened by `apport` to stay opened after a failure. Some details and workarounds have been discussed at (this askubuntu.com question)[http://askubuntu.com/questions/600875/how-to-keep-terminal- for-installation-of-debugging-symbols-of-apports-local-inv]. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17-0ubuntu1 Uname: Linux 4.0.0-04rc7-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 15:24:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (6 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1442159 Title: Add a configuration option to keep terminals opened by apport opened Status in apport package in Ubuntu: New Bug description: `gnome-terminals` which are opened by `apport` to monitor the installation of necessary deb packages for local investigation, production of `gdb` backtraces, etc. are closed immediately after success, but after failure as well (e.g. if `apt-get` can't get its global lock, or another issue occurs). For debugging `apport` it'd be very useful to have a configuration option which allows the terminals opened by `apport` to stay opened after a failure. Some details and workarounds have been discussed at (this askubuntu.com question)[http://askubuntu.com/questions/600875/how-to- keep-terminal-for-installation-of-debugging-symbols-of-apports-local- inv]. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17-0ubuntu1 Uname: Linux 4.0.0-04rc7-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 15:24:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (6 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1442159/+subscriptions -- Mailing list: https://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 299330] Re: Alt+Tab - switching applications delay. slow
** Changed in: metacity (Ubuntu) Status: Confirmed = Fix Released -- 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/299330 Title: Alt+Tab - switching applications delay. slow Status in The Metacity Window Manager: Fix Released Status in metacity package in Ubuntu: Fix Released Bug description: After hitting Alt+Tab it takes about .5 second before the application switch applet will be displayed. on windows XP this application switching window comes up instantly. In Ubuntu I would consider it annoyingly slow My config. Ubuntu 8.10, plain Gnome Another issue, it that Shift+Alt+Tab does not navigate the applications in reverse order, the way it works in XP. That would be nice if it's fixed too. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/299330/+subscriptions -- Mailing list: https://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 1440570] Re: VNC'ing into gnome-session-flashback (Metacity) in non-shared desktop mode causes Super+KEY pressed behavior
** Package changed: gnome-flashback (Ubuntu) = metacity (Ubuntu) ** Changed in: metacity (Ubuntu) Status: Triaged = In Progress ** Changed in: metacity (Ubuntu) Assignee: (unassigned) = Dmitry Shachnev (mitya57) -- 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/1440570 Title: VNC'ing into gnome-session-flashback (Metacity) in non-shared desktop mode causes Super+KEY pressed behavior Status in metacity package in Ubuntu: In Progress Bug description: When VNC'ing into gnome-session-flashback (Metacity) with either tightvncserver or vnc4server configured for non-shared desktop mode, when one opens a terminal for example, and types the s key, it acts as if the Super key is also pressed along with it. Hence, this appears to be a gnome-* issue. Vivid new install setup for tightvncserver: sudo apt-get update sudo apt-get -y dist-upgrade sudo apt-get -y install xrdp gnome-session-flashback sudo apt-get -y remove vino nano .xsession #START export XDG_CURRENT_DESKTOP='GNOME-Flashback:Unity' exec gnome-session --session=gnome-flashback-metacity --disable-acceleration-check #END sudo nano /etc/xrdp/xrdp.ini change to: #START [globals] bitmap_cache=yes bitmap_compression=yes port=3389 crypt_level=high channel_code=1 max_bpp=24 #black=00 #grey=d6d3ce #dark_grey=808080 #blue=08246b #dark_blue=08246b #white=ff #red=ff #green=00ff00 #background=626c72 [xrdp1] name=sesman-Xvnc lib=libvnc.so username=ask password=ask ip=127.0.0.1 port=-1 #END Log out, log back in, and RDP in via either Windows Remote Desktop Connection or Remmina. WORKAROUND: Applications System Tools System Settings Keyboard Shortcuts Disable all shortcuts containing the Super key. WORKAROUND: Don't use the .xsession file with tightvncserver, but this then creates a shared desktop experience, instead of ones own, not seen by the user at the local console. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: vnc4server 4.1.1+xorg4.3.0-37.3ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Apr 5 13:10:40 2015 InstallationDate: Installed on 2014-12-14 (112 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141213) SourcePackage: vnc4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1440570/+subscriptions -- Mailing list: https://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 1442283] [NEW] double mouse cursor
*** This bug is a security vulnerability *** Private security bug reported: These posts describe my problem: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361 But in my case, only when using multiple monitors it happens. I use one monitor rotated and one not. Like: https://bugs.freedesktop.org/show_bug.cgi?id=81886 The only way I've found to remove the extra mouse cursor is to drag an image in Chrome (?). It doesn't work with an image in Firefox nor in another program. Anyway, the extra mouse coursor appears again at any time, so I have no solution for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 9 13:53:03 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0552] NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0552] InstallationDate: Installed on 2015-03-21 (18 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Alienware M14xR2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic root=UUID=2c30fb16-00b6-47fa-b592-c1f1a4fc163c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2012 dmi.bios.vendor: Alienware dmi.bios.version: A03 dmi.board.name: M14xR2 dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A03 dmi.modalias: dmi:bvnAlienware:bvrA03:bd03/07/2012:svnAlienware:pnM14xR2:pvrA03:rvnAlienware:rnM14xR2:rvrA03:cvnAlienware:ct8:cvrA03: dmi.product.name: M14xR2 dmi.product.version: A03 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Apr 9 11:48:50 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Information type changed from Public to Private Security ** Description changed: These posts describe my problem: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361 + But in my case, only when using multiple monitors it happens. - The only way I've found to remove the extra mouse cursor is to drag an image in Chrome (?). It doesn't work with an image in Firefox nor in another program. + The only way I've found to remove the extra mouse cursor is to drag an image in Chrome (?). It doesn't work with an image in Firefox nor in another program. Anyway, the extra mouse coursor appears again at any time, so I have no solution for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 9 13:53:03 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0552] - NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0552] +
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@Paula Thomas: there are some pathetic packages which needlessly require certain nvidia driver packages regardless of what graphics hardware you have. A while back some bitcoin mining software did this to my desktop, putting it into text mode until I found the culprit. -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://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 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm
This bug was fixed in the package xdiagnose - 3.7.2 --- xdiagnose (3.7.2) vivid; urgency=medium * Only fallback to xdiagnose on systemd if an installed default display manager is configured. Do not fail graphical.target without any dm. (LP: #1441883) -- Didier Roche didro...@ubuntu.com Thu, 09 Apr 2015 10:38:15 +0200 ** Changed in: xdiagnose (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1441883 Title: 15.04 Vivid Vervet won't boot after uninstalling lightdm Status in lightdm package in Ubuntu: Triaged Status in xdiagnose package in Ubuntu: Fix Released Bug description: We've been trying to figure out how to disable the login screen on 15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall lightdm. If we do this on 15.04, however, the system won't boot. :( The main error seems to be: Failed to isolate default target, freezing. (I have a picture of this, if there is a way to upload one.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441883/+subscriptions -- Mailing list: https://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 1442050] [NEW] (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
You have been subscribed to a public bug: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 package-from-proposed vivid -- (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 https://bugs.launchpad.net/bugs/1442050 You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord 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 1440501] Re: Can not load mysql-akonadi apparmor profile
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1440501 Title: Can not load mysql-akonadi apparmor profile Status in akonadi package in Ubuntu: Confirmed Status in apparmor package in Ubuntu: Confirmed Bug description: Apparmor fails to start witch exit code 123, because it can not load the mysql-akonadi profile: % sudo systemctl status apparmor -l ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since So 2015-04-05 12:29:33 CEST; 55s ago Docs: man:systemd-sysv-generator(8) Process: 13906 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: ...fail! Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service: control process exited, code=exited status=123 Apr 05 12:29:33 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor initialization. Apr 05 12:29:33 benediktZ50-70 systemd[1]: Unit apparmor.service entered failed state. Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service failed. However Apparmor loaded successfully: % sudo aa-status apparmor module is loaded. 17 profiles are loaded. 17 profiles are in enforce mode. /sbin/dhclient /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/libvirt/virt-aa-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/libvirtd /usr/sbin/tcpdump docker-default 0 profiles are in complain mode. 5 processes have profiles defined. 5 processes are in enforce mode. /sbin/dhclient (11821) /usr/lib/telepathy/mission-control-5 (2008) /usr/sbin/cups-browsed (840) /usr/sbin/cupsd (12783) /usr/sbin/libvirtd (971) 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. It is really necessary to set Apparmor as failed if one profile could not be loaded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1440501/+subscriptions -- Mailing list: https://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 1430828] Re: scopes dont load pictures
My comment #23 is probably a red herring, as it looks like in the end all DNS servers are registered in dnsmasq, and it sends queries to all available servers. So I am hiding it. -- 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/1430828 Title: scopes dont load pictures Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: The phone (krillin) is clearly connected and you can retrive text data but pictures do not updated see, attached pictures. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1430828/+subscriptions -- Mailing list: https://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 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm
Didier kindly offered to work on the xdiagnose part. It's not yet clear whether we also need to change lightdm. ** Changed in: xdiagnose (Ubuntu) Assignee: (unassigned) = Didier Roche (didrocks) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1441883 Title: 15.04 Vivid Vervet won't boot after uninstalling lightdm Status in lightdm package in Ubuntu: Triaged Status in xdiagnose package in Ubuntu: Triaged Bug description: We've been trying to figure out how to disable the login screen on 15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall lightdm. If we do this on 15.04, however, the system won't boot. :( The main error seems to be: Failed to isolate default target, freezing. (I have a picture of this, if there is a way to upload one.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441883/+subscriptions -- Mailing list: https://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 1385709] Re: network-manager service doesn't start at boot time
I may have another look at the problem. I was experiencing the same waiting for network configuration issue after installing sendmail. I looked at my /var/log/upstart/network-interface-lo.log and network-manager.log log files and I found this. /etc/network/if-up.d/sendmail: 44: .: Can't open /usr/share/sendmail/dynamic run-parts: /etc/network/if-up.d/sendmail exited with return code 2 Indeed, the line 44 of the script /etc/network/if-up.d/sendmail calls another script /usr/share/sendmail/dynamic that does not exists. My (bad) patch was to comment line 44 of /etc/network/if-up.d/sendmail which solved the waiting for network configuration issue at startup. Hope it helps ! -- 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/1385709 Title: network-manager service doesn't start at boot time Status in network-manager package in Ubuntu: Confirmed Status in sendmail package in Ubuntu: Confirmed Bug description: I just completed the upgrade from Kubuntu 14.04 to 14.10. Haven't had any network trouble before the upgrade. After the upgrade, the network-manager service does not start when the computer boots up - the Kubuntu splash screen says 'waiting for network configuration', then 'waiting another 60 seconds for network configuration' (or something like that), then finally boots up without a network connection. Also the Network Management tray icon tooltip says that the network-manager service is not running. However if I then manually open the terminal and run 'sudo service network-manager start', then it starts ok and the network connects within a few seconds and everything works ok until the next reboot. I'm on a desktop PC with a wired LAN connection and no wifi adapter. network-manager version is 0.9.8.8-0ubuntu28. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1385709/+subscriptions -- Mailing list: https://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 1375598] Re: Some options have not been translated in system setting- safety and privacy
.po files have not been updated -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to activity-log-manager in Ubuntu. https://bugs.launchpad.net/bugs/1375598 Title: Some options have not been translated in system setting- safety and privacy Status in Privacy Manager for Zeitgeist: Fix Committed Status in Ubuntu Kylin: Confirmed Status in activity-log-manager package in Ubuntu: Fix Released Bug description: steps: 1. enter System Setting. 2. click Safety and Privacy. 3. click 'file and application' tab page 4.click + at the bottom of the interface. 5.check the options. 6. the options( Add folder; Add Application) are in English. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/1375598/+subscriptions -- Mailing list: https://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 1441423] Re: printers not listed
Please attach the following files: /etc/cups/printers.conf /etc/cups/classes.conf /etc/cups/client.conf /etc/cups/cupsd.conf /etc/cups/cups-files.conf /etc/cups/cups-browsed.conf Please attach the files one by one, do not compress them and do not package them together. Please also post the output of the following commands: lpstat -v ls -l /etc/cups/ppd ls -l /etc/cups/interfaces ** Changed in: system-config-printer (Ubuntu) Status: New = Incomplete -- 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/1441423 Title: printers not listed Status in system-config-printer package in Ubuntu: Incomplete Bug description: 1. system-config-printer is not showing all printers listed in cups web interface. 2. print dialog of applications not showing all printers listed in cups web interface. 3. lpstat -a (same result as in 1., 2.) === system-config-printer v1.5.6 cups v2.0.2 Linux zzz 3.19.0-12-generic #12-Ubuntu SMP Fri Apr 3 04:03:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1441423/+subscriptions -- Mailing list: https://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 1441960] Re: Update to upstream version 41 in Precise for security fixes
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) = Chad Miller (cmiller) ** Changed in: chromium-browser (Ubuntu) Status: New = In Progress -- 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/1441960 Title: Update to upstream version 41 in Precise for security fixes Status in chromium-browser package in Ubuntu: In Progress Bug description: This morning Gmail notified me that my browser is unsupported, which made me realize Chromium for Precise hasn't been updated since September 2014 and is currently at version 37 (37.0.2062.120-0ubuntu0.12.04.1~pkg917) whereas more recent versions of Ubuntu are already at Chromium version 41. The unsupported version messages are of course harmless and easy enough to dismiss, but I'm guessing the newer Chromium releases also have important security fixes that should warrant an update – unless there are compatibility issues blocking it from happening? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917 ProcVersionSignature: Ubuntu 3.13.0-49.81~precise1-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CheckboxSubmission: 09ae689090491ca53449589269e4bfd8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Thu Apr 9 07:52:26 2015 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2014-07-11 (271 days ago) modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-01-13T17:30:56.028907 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1441960/+subscriptions -- Mailing list: https://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 875676] Re: Backing up fails with 'IOError CRC check failed'.
Every time I start a backup I get the following error:
Failed to read
/home/user/.cache/deja-dup/tmp/duplicity-7EsAky-tempdir/mktemp-hqHmHI-63:
(type 'exceptions.IOError', IOError('CRC check failed 0x6ae5ab23 !=
0x78b803e5L',), traceback object at 0x7f4f3cfa06c8)
Deleting the cace dir does not help.
This issue showed up since some weeks but apparently I didn't change settings.
I'm using Ubuntu 14.10 with kernel 3.16.0-34-generic
deja-dup 32.0-0ubuntu1.1
duplicity 0.6.23-1ubuntu5
Any clue on solving and debugging?
--
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/875676
Title:
Backing up fails with 'IOError CRC check failed'.
Status in Déjà Dup Backup Tool:
New
Status in Duplicity - Bandwidth Efficient Encrypted Backup:
New
Status in deja-dup package in Ubuntu:
New
Bug description:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (type
'exceptions.IOError', IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), traceback object at 0x9fe0554)
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
--
System information:
Ubuntu 11.10
deja-dup 20.0-0ubuntu3
duplicity 0.6.15-0ubuntu2
Logs:
deja-dup.log: http://pastie.org/2705320
deja-dup.gsettings: http://pastie.org/2705322
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions
--
Mailing list: https://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 1441449] Re: [HP Z820] external microphone does not work, only records noises
** Tags added: 201407-15335 taipei-lab ** Tags added: blocks-hwcert -- 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/1441449 Title: [HP Z820] external microphone does not work, only records noises Status in HWE Next Project: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Records with a lot noises, barely can heard the sound. Step to reproduce: 1. plug your microphone to the front/rear micrphone jack 2. turn up the microphone volume in the system sound settings 3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt when you finish Expected result: when playing the recordings it should plays recognizable sound. Actual results: A lot noise in the recordings. Additional information: In the attached recording file, you should hear, Testing, One, Two, Three, Four, Five . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1696 F pulseaudio /dev/snd/controlC0: ubuntu 1696 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 8 01:32:46 2015 InstallationDate: Installed on 2015-04-02 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J63 v03.69 dmi.board.asset.tag: 2UA4242K12 dmi.board.name: 158B dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.01 dmi.chassis.asset.tag: 2UA4242K12 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z820 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1441449/+subscriptions -- Mailing list: https://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 1357682] Re: package postgresql-client-9.3 9.3.5-0ubuntu0.14.04.1 failed to upgrade: alternative pg_basebackup.1.gz can't be slave of psql.1.gz
I ran the test case with version 154 from trusty and get the failure. I re-ran it with 154ubuntu1 from trusty-proposed and both -9.1 and -9.4 now succeed. This is self-verification, but as nobody else verified this in the past 50 days and the next point release will come at some point, let's get this out there to avoid further hassle. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1357682 Title: package postgresql-client-9.3 9.3.5-0ubuntu0.14.04.1 failed to upgrade: alternative pg_basebackup.1.gz can't be slave of psql.1.gz Status in postgresql-common package in Ubuntu: Fix Released Status in postgresql-common source package in Precise: Invalid Status in postgresql-common source package in Trusty: Fix Committed Status in postgresql-common source package in Vivid: Fix Released Bug description: Error while do-release-upgrade from 12.04 to 14.04 SRU TEST CASE: # Run these commands in a precise schroot: apt-get install -y postgresql-9.1 man-db echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' /etc/apt/sources.list.d/pgdg.list apt-get update apt-get install -y --force-yes postgresql-9.4 man pg_basebackup # this should be for 9.4 # this will fail with current postgresql-common (backport of 166), but ought to succeed with a fixed package dpkg-reconfigure postgresql-9.1 man pg_basebackup # this should still be for 9.4 # after that, this should also succeed dpkg-reconfigure postgresql-9.4 SRU FIX: https://alioth.debian.org/scm/loggerhead/pkg-postgresql /postgresql-common/trunk/revision/1591 SRU REGRESSION POTENTIAL: Errors in the p-common maintainer script can potentially lead to complete installation failure of any postgresql-X.Y and postgresql-client-X.Y package. The postgresql-X.Y autopkgtests will cover this for one version, but for multiple versions in parallel this should be manually verified. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: postgresql-client-9.3 9.3.5-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sat Aug 16 11:41:04 2014 DuplicateSignature: package:postgresql-client-9.3:9.3.5-0ubuntu0.14.04.1:ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück ErrorMessage: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück InstallationDate: Installed on 2014-03-09 (159 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.2) SourcePackage: postgresql-9.3 Title: package postgresql-client-9.3 9.3.5-0ubuntu0.14.04.1 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück UpgradeStatus: Upgraded to trusty on 2014-08-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1357682/+subscriptions -- Mailing list: https://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 1400206] Re: Chromium hangs: GPU process hung
Possible related bugs: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1377220 https://code.google.com/p/chromium/issues/detail?id=293008 https://code.google.com/p/chromium/issues/detail?id=418858 https://code.google.com/p/chromium/issues/detail?id=389816 https://code.google.com/p/chromium/issues/detail?id=427909 https://code.google.com/p/chromium/issues/detail?id=400043 ** Bug watch added: code.google.com/p/chromium/issues #293008 http://code.google.com/p/chromium/issues/detail?id=293008 ** Bug watch added: code.google.com/p/chromium/issues #418858 http://code.google.com/p/chromium/issues/detail?id=418858 ** Bug watch added: code.google.com/p/chromium/issues #389816 http://code.google.com/p/chromium/issues/detail?id=389816 ** Bug watch added: code.google.com/p/chromium/issues #427909 http://code.google.com/p/chromium/issues/detail?id=427909 ** Bug watch added: code.google.com/p/chromium/issues #400043 http://code.google.com/p/chromium/issues/detail?id=400043 -- 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/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+subscriptions -- Mailing list: https://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 1037774] Re: colord crashed with SIGSEGV in cd_profile_register_object()
showed up at startup on precise ** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1037774 Title: colord crashed with SIGSEGV in cd_profile_register_object() Status in colord package in Ubuntu: Confirmed Bug description: I did nothing special. Resume from suspend, perhaps. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Thu Aug 16 20:12:00 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40ea42 cd_profile_register_object+98: mov 0x8(%rax),%rbx PC (0x0040ea42) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_profile_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_profile_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1037774/+subscriptions -- Mailing list: https://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 1434782] Re: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1434782 Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 Status in sane-backends package in Ubuntu: Confirmed Bug description: no more information about the crash ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Sat Mar 21 09:21:01 2015 DuplicateSignature: package:libsane:1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules]:tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 ErrorMessage: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 InstallationDate: Installed on 2015-03-19 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: sane-backends Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2015-03-19T21:09:02.880202 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1434782/+subscriptions -- Mailing list: https://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 1437639] Re: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsa
** This bug has been marked a duplicate of bug 1434782 package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentata sovrascrittura di /lib/udev/rules.d/40-libsane.rules (condiviso), diverso da altre istanze del pacchetto libsane:i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1437639 Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist Status in sane-backends package in Ubuntu: New Bug description: The problem was detected while installing wine by Terminal ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Sat Mar 28 15:57:58 2015 DuplicateSignature: package:libsane:1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules]:Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist InstallationDate: Installed on 2015-03-20 (7 days ago) InstallationMedia: Edubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: sane-backends Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/rules.d/40-libsane.rules« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2015-03-26T19:17:52.598078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1437639/+subscriptions -- Mailing list: https://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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
I just did security update Linux Image 3.16.0.34-generic. It seems as if every time that I do the next security update there is a problem as is evident by this bug report: nvidia-331-updates kernel module failed to build. I use this fix (This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) and the update completes and I restart. I'm not an advanced Ubuntu tech but something must be wrong with the nvidia driver or the kernel that does not allow for security updates to complete. What is causing this problem? I'm about to have an old friend put Ubuntu15.04 on his computer and I hope that this bug is fixed before that update. By convincing him that WIN is more problem for him, I suggested Ubuntu. -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://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 1442044] [NEW] Ordering processes: networkmanager should wait for kernel'module been activated first before starting
You have been subscribed to a public bug: Get that journalctl log showing networkmanager starting before the related kernel'module been ready: systemd[1]: Starting Network. systemd[1]: Starting /etc/rc.local Compatibility... NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: info (lo): link connected NetworkManager[724]: info (lo): carrier is ON NetworkManager[724]: info (lo): new Generic device (driver: 'unknown' ifindex: 1) NetworkManager[724]: info (lo): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: info (eth0): carrier is OFF NetworkManager[724]: info (eth0): new Ethernet device (driver: 'sky2' ifindex: 2) NetworkManager[724]: info (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[724]: info (eth0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] NetworkManager[724]: info (eth0): preparing device NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: info (eth1): carrier is OFF NetworkManager[724]: info (eth1): new Ethernet device (driver: 'sky2' ifindex: 3) NetworkManager[724]: info (eth1): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager[724]: info (eth1): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] kernel: sky2 :04:00.0 eth0: enabling interface kernel: sky2 :03:00.0 eth1: enabling interface NetworkManager[724]: info (eth1): preparing device NetworkManager[724]: info urfkill disappeared from the bus that mobo have eth0 eth1 ports, but only eth1 is used. As the last lines logged, networworkmanager is able to be loaded when the module sky2 is enabled. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:41:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 package-from-proposed vivid -- Ordering processes: networkmanager should wait for kernel'module been activated first before starting https://bugs.launchpad.net/bugs/1442044 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager 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 1442113] [NEW] package thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thu
Public bug reported: brokencount 0 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robbins2301 F pulseaudio BuildID: 20150223201856 Channel: Unavailable Date: Sat Apr 4 22:41:47 2015 DuplicateSignature: package:thunderbird:1:31.5.0+build1-0ubuntu0.14.04.1:cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-02-07 (61 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev eth0 proto static 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.102 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Title: package thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: CF94510J.15A.0038.2007.0226.1646 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCL dmi.board.vendor: Intel Corporation dmi.board.version: AAD75361-301 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrCF94510J.15A.0038.2007.0226.1646:bd02/26/2007:svnGateway:pnGT5428:pvr:rvnIntelCorporation:rnD945GCL:rvrAAD75361-301:cvn:ct3:cvr: dmi.product.name: GT5428 dmi.sys.vendor: Gateway ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1442113 Title: package thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so .dpkg-new': unexpected end of file or stream Status in thunderbird package in Ubuntu: New Bug description: brokencount 0 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robbins2301 F pulseaudio BuildID: 20150223201856 Channel: Unavailable Date: Sat Apr 4 22:41:47 2015 DuplicateSignature: package:thunderbird:1:31.5.0+build1-0ubuntu0.14.04.1:cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-02-07 (61 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev eth0 proto static 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.102 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Title: package thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version:
[Desktop-packages] [Bug 1442111] [NEW] Scanner is correctly identified but scan fails with sane_start: Invalid argument as root, and rebooting the computer sometimes makes things work, sometimes not
Public bug reported:
OS/Kernel: Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-80-generic x86_64)
Scanner: Epson Stylus Office BX305FW, USB 2.0, id 0x04b8/0x0863
SANE: libsane_1.0.22-7ubuntu1, libsane-common_1.0.22-7ubuntu1,
sane-utils_1.0.22-7ubuntu1 (up-to-date 12.04 LTS)
Epson IScan: iscan_2.30.1-1, iscan-data_1.36.0-1 (latest versions, 2015-03-23)
The scanner is correctly identified, when logged in as root:
# sane-find-scanner
found USB scanner (vendor=0x04b8, product=0x0863) at libusb:001:004
# lsusb
Bus 001 Device 004: ID 04b8:0863 Seiko Epson Corp.
# scanimage -L
device `epkowa:usb:001:004' is a Epson Stylus Office BX305F/BX305FW/TX320F/ME
OFFICE 620F/WorkForce 320 Series flatbed scanner
But scan fails with scanimage: sane_start: Invalid argument (scanimage
frontend) or Échec de la numérisation: Impossible de démarrer la
numérisation (simple-scan frontend):
# scanimage -d epkowa:usb:001:004 -v -T
scanimage: sane_start: Invalid argument
The permissions of the device seem nominal:
# ls -l /dev/bus/usb/001/004
crw-rw-r--+ 1 root lp 189, 1 avril 9 12:32 /dev/bus/usb/001/004
And the following line is present in /lib/udev/rules.d/40-iscan.rules:
ATTRS{idVendor}==04b8, ATTRS{idProduct}==0863,
ENV{libsane_matched}=yes
When this problems appears, it stays so for the whole session, but
rebooting the computer sometimes makes the problem go away, sometimes
not. The only thing I can see that a reboot changes is the USB device
ID, all the rest stays the same in the previous commands output.
For instance right now the USB device ID was 001:004 and scan wasn't
working, I rebooted and it's 001:002 and scan is working. I don't know
if it is relevant, I don't understand what is causing the problem, and I
don't know how to investigate further.
SANE support for this scanner with external backend epkowa is normally
complete, and everything runs smoothly on the reboots when the problem
does not appear. Any help is appreciated. Should I report the bug
upstream, or against a different package, perhaps a USB-related or boot-
related one?
** Affects: sane-backends (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1442111
Title:
Scanner is correctly identified but scan fails with sane_start:
Invalid argument as root, and rebooting the computer sometimes makes
things work, sometimes not
Status in sane-backends package in Ubuntu:
New
Bug description:
OS/Kernel: Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-80-generic x86_64)
Scanner: Epson Stylus Office BX305FW, USB 2.0, id 0x04b8/0x0863
SANE: libsane_1.0.22-7ubuntu1, libsane-common_1.0.22-7ubuntu1,
sane-utils_1.0.22-7ubuntu1 (up-to-date 12.04 LTS)
Epson IScan: iscan_2.30.1-1, iscan-data_1.36.0-1 (latest versions, 2015-03-23)
The scanner is correctly identified, when logged in as root:
# sane-find-scanner
found USB scanner (vendor=0x04b8, product=0x0863) at libusb:001:004
# lsusb
Bus 001 Device 004: ID 04b8:0863 Seiko Epson Corp.
# scanimage -L
device `epkowa:usb:001:004' is a Epson Stylus Office
BX305F/BX305FW/TX320F/ME OFFICE 620F/WorkForce 320 Series flatbed scanner
But scan fails with scanimage: sane_start: Invalid argument
(scanimage frontend) or Échec de la numérisation: Impossible de
démarrer la numérisation (simple-scan frontend):
# scanimage -d epkowa:usb:001:004 -v -T
scanimage: sane_start: Invalid argument
The permissions of the device seem nominal:
# ls -l /dev/bus/usb/001/004
crw-rw-r--+ 1 root lp 189, 1 avril 9 12:32 /dev/bus/usb/001/004
And the following line is present in /lib/udev/rules.d/40-iscan.rules:
ATTRS{idVendor}==04b8, ATTRS{idProduct}==0863,
ENV{libsane_matched}=yes
When this problems appears, it stays so for the whole session, but
rebooting the computer sometimes makes the problem go away, sometimes
not. The only thing I can see that a reboot changes is the USB device
ID, all the rest stays the same in the previous commands output.
For instance right now the USB device ID was 001:004 and scan wasn't
working, I rebooted and it's 001:002 and scan is working. I don't know
if it is relevant, I don't understand what is causing the problem, and
I don't know how to investigate further.
SANE support for this scanner with external backend epkowa is normally
complete, and everything runs smoothly on the reboots when the problem
does not appear. Any help is appreciated. Should I report the bug
upstream, or against a different package, perhaps a USB-related or
boot-related one?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442111/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1442113] Re: package thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thund
** Tags removed: need-duplicate-check -- 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/1442113 Title: package thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so .dpkg-new': unexpected end of file or stream Status in thunderbird package in Ubuntu: New Bug description: brokencount 0 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robbins2301 F pulseaudio BuildID: 20150223201856 Channel: Unavailable Date: Sat Apr 4 22:41:47 2015 DuplicateSignature: package:thunderbird:1:31.5.0+build1-0ubuntu0.14.04.1:cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-02-07 (61 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev eth0 proto static 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.102 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Title: package thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: CF94510J.15A.0038.2007.0226.1646 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCL dmi.board.vendor: Intel Corporation dmi.board.version: AAD75361-301 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrCF94510J.15A.0038.2007.0226.1646:bd02/26/2007:svnGateway:pnGT5428:pvr:rvnIntelCorporation:rnD945GCL:rvrAAD75361-301:cvn:ct3:cvr: dmi.product.name: GT5428 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1442113/+subscriptions -- Mailing list: https://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 386860] Re: Metacity + compositing cause display corruption and artifact
** Changed in: metacity (Ubuntu) Status: Incomplete = Invalid -- 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/386860 Title: Metacity + compositing cause display corruption and artifact Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity When using Metacity + compositing in Ubuntu Jaunty, I can't manage to work more than 1 hours without getting display corruption or artifact. Those artifact seams to appear randomly and disappear when the windows or screen are invalidate. The following attachment file present a screenshot of the screen. I guess it's the best way to explain the problem. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: metacity 1:2.25.144-0ubuntu2.1 ProcEnviron: SHELL=/bin/bash LANG=en_CA.UTF-8 SourcePackage: metacity Uname: Linux 2.6.29-02062903-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/386860/+subscriptions -- Mailing list: https://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 1442027] [NEW] after kernel upgrade the nvidia binary drivers stop working correctly
Public bug reported: This issue happened the second time to me: A regular update required a reboot since kernel components where changed. After the reboot the X11 display comes up without the second monitor and only the upper half of the screen is displayed (screen seems to be double as tall as the usual screen, looks like stretched). Switching to the console view, this issue can be solved by installing the needed kernel headers: aptitude install linux-generic installs linux-headers-generic (= 3.13.0.49.56) Now both (!!) NVIDIA driver module packages can be recompiled / relinked: dpkg-reconfigure nvidia-331 dpkg-reconfigure nvidia-331-uvm After reboot the X11 displays works as expected in a dual-screen setup on two monitors side-by-side. To me this looks like a dependency issue with drastic consequences: critical, but probably easy to solve. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty # dpkg -l |grep nvidia ii nvidia-331 331.113-0ubuntu0.0.4amd64NVIDIA binary driver - version 331.113 ii nvidia-331-uvm 331.113-0ubuntu0.0.4amd64NVIDIA Unified Memory kernel module ii nvidia-libopencl1-331 331.113-0ubuntu0.0.4amd64NVIDIA OpenCL Driver and ICD Loader library ii nvidia-opencl-icd-331 331.113-0ubuntu0.0.4amd64NVIDIA OpenCL ICD ii nvidia-prime0.6.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64Tool for configuring the NVIDIA graphics driver # dpkg -s linux-generic Package: linux-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 29 Maintainer: Ubuntu Kernel Team kernel-t...@lists.ubuntu.com Architecture: amd64 Source: linux-meta Version: 3.13.0.49.56 Depends: linux-image-generic (= 3.13.0.49.56), linux-headers-generic (= 3.13.0.49.56) Description: Complete Generic Linux kernel and headers This package will always depend on the latest complete generic Linux kernel and headers. ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1442027 Title: after kernel upgrade the nvidia binary drivers stop working correctly Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: This issue happened the second time to me: A regular update required a reboot since kernel components where changed. After the reboot the X11 display comes up without the second monitor and only the upper half of the screen is displayed (screen seems to be double as tall as the usual screen, looks like stretched). Switching to the console view, this issue can be solved by installing the needed kernel headers: aptitude install linux-generic installs linux-headers-generic (= 3.13.0.49.56) Now both (!!) NVIDIA driver module packages can be recompiled / relinked: dpkg-reconfigure nvidia-331 dpkg-reconfigure nvidia-331-uvm After reboot the X11 displays works as expected in a dual-screen setup on two monitors side-by-side. To me this looks like a dependency issue with drastic consequences: critical, but probably easy to solve. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty # dpkg -l |grep nvidia ii nvidia-331 331.113-0ubuntu0.0.4amd64NVIDIA binary driver - version 331.113 ii nvidia-331-uvm 331.113-0ubuntu0.0.4amd64NVIDIA Unified Memory kernel module ii nvidia-libopencl1-331 331.113-0ubuntu0.0.4amd64NVIDIA OpenCL Driver and ICD Loader library ii nvidia-opencl-icd-331 331.113-0ubuntu0.0.4amd64NVIDIA OpenCL ICD ii nvidia-prime0.6.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64
[Desktop-packages] [Bug 1442281] [NEW] double mouse cursor
Public bug reported: These posts describe my problem: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361 The only way I've found to remove the extra mouse cursor is to drag an image in Chrome (?). It doesn't work with an image in Firefox nor in another program. Anyway, the extra mouse coursor appears again at any time, so I have no solution for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 9 13:53:03 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0552] NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0552] InstallationDate: Installed on 2015-03-21 (18 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Alienware M14xR2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic root=UUID=2c30fb16-00b6-47fa-b592-c1f1a4fc163c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2012 dmi.bios.vendor: Alienware dmi.bios.version: A03 dmi.board.name: M14xR2 dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A03 dmi.modalias: dmi:bvnAlienware:bvrA03:bd03/07/2012:svnAlienware:pnM14xR2:pvrA03:rvnAlienware:rnM14xR2:rvrA03:cvnAlienware:ct8:cvrA03: dmi.product.name: M14xR2 dmi.product.version: A03 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Apr 9 11:48:50 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1442281 Title: double mouse cursor Status in xorg package in Ubuntu: New Bug description: These posts describe my problem: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361 The only way I've found to remove the extra mouse cursor is to drag an image in Chrome (?). It doesn't work with an image in Firefox nor in another program. Anyway, the extra mouse coursor appears again at any time, so I have no solution for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 9 13:53:03 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0552] NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0552] InstallationDate: Installed on 2015-03-21 (18 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Alienware M14xR2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic
[Desktop-packages] [Bug 1419533] Re: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/40-libs
*** This bug is a duplicate of bug 1186715 *** https://bugs.launchpad.net/bugs/1186715 ** This bug is no longer a duplicate of bug 1410932 package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 ** This bug has been marked a duplicate of bug 1186715 package libsane 1.0.23-0ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1419533 Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 Status in sane-backends package in Ubuntu: New Bug description: I don't realy know what happened ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sun Feb 8 15:53:31 2015 DuplicateSignature: package:libsane:1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules]:tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 InstallationDate: Installed on 2015-01-31 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: sane-backends Title: package libsane 1.0.23-3ubuntu3.1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/40-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2015-01-30T23:14:37.490460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1419533/+subscriptions -- Mailing list: https://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 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Attachment added: dmesg-drm_debug.log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1434036/+attachment/4370607/+files/dmesg-drm_debug.log -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in X.org XServer - ATI gfx chipset driver: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information:
[Desktop-packages] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm
Done, now xdiagnose only triggers if an installed display manager is configured as default but couldn't start. This should fix your boot issue. We won't fail graphical.target anymore if the only available dm was uninstalled, however, I do recommend you set then your default target to multi-user.target (case on a server system for instance). The lightdm part would be interesting to ensure /e/X/d-d-m is empty, but not required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1441883 Title: 15.04 Vivid Vervet won't boot after uninstalling lightdm Status in lightdm package in Ubuntu: Triaged Status in xdiagnose package in Ubuntu: Triaged Bug description: We've been trying to figure out how to disable the login screen on 15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall lightdm. If we do this on 15.04, however, the system won't boot. :( The main error seems to be: Failed to isolate default target, freezing. (I have a picture of this, if there is a way to upload one.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441883/+subscriptions -- Mailing list: https://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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
Hello, same problem. I noticed this bug affect VirtualBox stability too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://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 1423040] Re: REISUB required on resume after suspend kernel regression 3.11
Moved the hard disk inside the PC case (it was a standard hard disk plugged in a USB mobile disk enclosure) and suspend/resume is ok. So there is a bug (kernel regression), but only if the OS is installed on an external hard disk. ** Package changed: nvidia-graphics-drivers-331 (Ubuntu) = ubuntu ** Changed in: ubuntu Status: New = Confirmed -- 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/1423040 Title: REISUB required on resume after suspend kernel regression 3.11 Status in Ubuntu: Confirmed Bug description: System: Ubuntu 14.04 64 bit (actually mint 17.1 xfce cinnamon or zorin 9) or Ubuntu 12.04 with trusty-lts kernel Nvidia proprietary driver (tested with 304, 331 and 346 versions) Geforce GT430 (may be related to nvidia but no bug on another system with Geforce 9400M) Expected behaviour: This system suspends/resumes very well on Ubuntu 12.04 with stock kernel (3.2) What happened instead: Unusable desktop after resume, nothing can be launched (often black desktop and/or dead mouse). The exact behaviour depends on the kernel version and is not always the same. Sometimes, the desktop is restored (after CTRL-ALT-F8) with a live mouse pointer, but even in these case, nothing can be launched (file not found errors or vanishing desktop after a click or simply no action). Sometimes, (with CTRL-ALT-F1), ext4-fs errors are reported. Investigation: All these tests are done on an external usb disk installation, but the exact same configuration is ok with Ubuntu 12.04. I tried usbcore.autosuspend=-1 kernel option at boot without success. The bug can be reproduced if I update the kernel from a fresh (and functional) 12.04 install. Even on Manjaro, the bug appears with (at least) kernel 3.12.36-1 and 3.16.7.4-1 (but not with 3.10). I tried various kernels/nvidia combinations on 14.04 without any success (3.13/3.16). It seems I can't get trace in log files after suspend. The bug is similar to https://bugs.launchpad.net/ubuntu/+source /nvidia-graphics-drivers-331/+bug/1210077. However, 1210077 is supposed to be fixed so this one is different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1423040/+subscriptions -- Mailing list: https://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 729979] Re: [nvidia] Windows appear blank white
So any chance this fix will also make it into newer versions of Ubuntu? -- 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/729979 Title: [nvidia] Windows appear blank white Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome- terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc. HOW TO REPRODUCE: [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not reliably be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly. 1. Minimize a window 2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal) 3. Click the window icon on the launcher to maximize it again. 4. The window contents will be white, black, or transparent depending on the Ubuntu version [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions -- Mailing list: https://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 1441986] [NEW] NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher garbled after resuming from suspend
Public bug reported: Launcher does not display correctly after suspend, there is other different corruption in different application scenario, most of them can be recover by switch between VT. Steps to reproduce: 1. suspend the system in the middle of using 2. resume from suspend Expected result: Desktop screen display correctly. Actual result: Some parts of the screen corrupted. Workaround: Switching from X to VT may temporary fix these corruptions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-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.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 9 02:09:23 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:079c] InstallationDate: Installed on 2015-04-02 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Z820 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=d8280bec-e0b3-4b37-8f6b-aa899731f110 ro rootdelay=60 quiet splash initcall_debug SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J63 v03.69 dmi.board.asset.tag: 2UA4242K12 dmi.board.name: 158B dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.01 dmi.chassis.asset.tag: 2UA4242K12 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z820 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 8 09:39:05 2015 xserver.configfile: default 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.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption trusty ubuntu ** Attachment added: Launcher Garbled.png https://bugs.launchpad.net/bugs/1441986/+attachment/4370135/+files/Launcher%20garbled%202%20-%20Screenshot%20from%202015-04-07%2004%3A29%3A57.png -- 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/1441986 Title: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher garbled after resuming from suspend Status in xorg package in Ubuntu: New Bug description: Launcher does not display correctly after suspend, there is other different corruption in different application scenario, most of them can be recover by switch between VT. Steps to reproduce: 1. suspend the system in the middle of using 2. resume from suspend Expected result: Desktop screen display correctly. Actual result: Some parts of the screen corrupted. Workaround: Switching from X to VT may temporary fix these corruptions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a
[Desktop-packages] [Bug 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out
sorry, scratch that last comment. It should have been: I could connect to the N network on utopic, so this is a regression. -- 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/1441893 Title: Can't connect to my wi-fi N network on vivid: authentication timed out Status in network-manager package in Ubuntu: New Bug description: I can't connect to my wi-fi with my laptop. I get this error message in the syslog. Apr 8 22:25:35 ubuntu kernel: [ 793.89] wlan0: authentication with 10:bf:48:e5:d1:b8 timed out ubuntu@ubuntu:~$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: Ethernet Connection I217-V vendor: Intel Corporation physical id: 19 bus info: pci@:00:19.0 logical name: eth0 version: 05 serial: 00:90:f5:f8:ef:86 size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff ioport:f080(size=32) *-network description: Wireless interface product: Wireless 3160 vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: wlan0 version: 83 serial: a0:88:69:39:ae:d6 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn resources: irq:32 memory:f7c0-f7c01fff Attached is the full syslog. This machine has been working more or less ok on vivid for at least three months. Sometimes it refused to connect to the wi-fi, but after a restart it started working. Recently I changed the network from G to N, and recently did an upgrade to the latest vivid. I had some problems booting, so I also recently fully removed upstart. It boots fine with systemd, and everything else seem to be working. I've just tested with a daily vivid live USB, and the same problem happened. I'm connecting to the same network using the same password with my other machine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CasperVersion: 1.356 CurrentDesktop: Unity Date: Wed Apr 8 22:20:03 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.2.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.208 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 cf5cb021-0df1-4f13-b74c-c3e9c6749a30 /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1441893/+subscriptions -- Mailing list: https://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 1441914] Re: lua:socket settimeout does not work
** Package changed: unity (Ubuntu) = luasocket (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/1441914
Title:
lua:socket settimeout does not work
Status in luasocket package in Ubuntu:
New
Bug description:
Ubuntu Version: Ubuntu 14.04.2 LTS
package lua-socket:i386 3.0~rc1-3
On Ubuntu 14.04, lua socket settimeout does not work as expected. On a tcp
socket, it causes the next receive to close the connection immediately.
It works correctly on Ubuntu 12.04 and debian 7.
To reproduce:
install packages lua5.1 and lua-socket
Take the echo server example from the introduction to luasocket:
http://w3.impa.br/~diego/software/luasocket/introduction.html
Put it in a file echo.lua and run it with lua echo.lua
From another window, use telnet localhost {port} to connect to the echo server
Result: Immediately after connecting, the server closes the connection.
Expected Result: The server should wait 10 seconds for input, then close the
connection.
package version that works correctly in debian 7: lua-socket:i386 2.0.2-8
-
A copy of the example (echo.lua):
-- load namespace
local socket = require(socket)
-- create a TCP socket and bind it to the local host, at any port
local server = assert(socket.bind(*, 0))
-- find out which port the OS chose for us
local ip, port = server:getsockname()
-- print a message informing what's up
print(Please telnet to localhost on port .. port)
print(After connecting, you have 10s to enter a line to be echoed)
-- loop forever waiting for clients
while 1 do
-- wait for a connection from any client
local client = server:accept()
-- make sure we don't block waiting for this client's line
client:settimeout(10)
-- receive the line
local line, err = client:receive()
-- if there was no error, send it back to the client
if not err then client:send(line .. \n) end
-- done with client, close the object
client:close()
end
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/luasocket/+bug/1441914/+subscriptions
--
Mailing list: https://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 658306] Re: GTK crash with 10.10 LiveCD after 5 clicks
** Changed in: metacity (Ubuntu) Status: New = Invalid -- 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/658306 Title: GTK crash with 10.10 LiveCD after 5 clicks Status in metacity package in Ubuntu: Invalid Bug description: Just tested the official 10.10 release on a Virtualbox machine with 512MB memory. Desktop boots up fine but if I add Universe repo, it gets downloaded and then GTK gets all messed up: loosing title window, unable to resize... I've recorded a screencast of the problem. http://is.gd/fWPeA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/658306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
